Mercurial > prosody-modules
comparison CONTRIBUTING @ 1669:a25d137439a7
Add README and CONTRIBUTING files containing the text from https://code.google.com/p/prosody-modules/
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Thu, 09 Apr 2015 14:21:33 +0200 |
| parents | |
| children | e6e45ef1608b |
comparison
equal
deleted
inserted
replaced
| 1668:fc7cd6cbe228 | 1669:a25d137439a7 |
|---|---|
| 1 Contributing | |
| 2 ============ | |
| 3 | |
| 4 Guidelines for developers | |
| 5 ------------------------- | |
| 6 | |
| 7 * Each module should be contained in a folder of its name (e.g. | |
| 8 `mod_ping/mod_ping.lua`) | |
| 9 * Each module should have a wiki page with a description, | |
| 10 usage, configuration and todo sections (feel free to copy an | |
| 11 existing one as a template) | |
| 12 * Commit messages should begin with the name of the plugin they | |
| 13 are for (e.g. `mod_ping: Set correct namespace on pongs`) | |
| 14 | |
| 15 Instructions on cloning the repository are at | |
| 16 http://code.google.com/p/prosody-modules/source/checkout - if you have | |
| 17 commit access you will also see a link on that page to view your Google | |
| 18 Code password (not the same as your Google account password) to push your | |
| 19 changes. |