Mercurial > prosody-modules

comparison CONTRIBUTING @ 1808:e6e45ef1608b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
CONTRIBUTING: Update guidelines and URL to hg repo
author Kim Alvefur <zash@zash.se>
date Mon, 31 Aug 2015 17:28:14 +0200
parents a25d137439a7
children 0b7d65b4f576
comparison
equal deleted inserted replaced
1807:11ab901b6fe1 1808:e6e45ef1608b
4 Guidelines for developers 4 Guidelines for developers
5 ------------------------- 5 -------------------------
6 6
7 * Each module should be contained in a folder of its name (e.g. 7 * Each module should be contained in a folder of its name (e.g.
8 `mod_ping/mod_ping.lua`) 8 `mod_ping/mod_ping.lua`)
9 * Each module should have a wiki page with a description, 9 * Each module should have a `README.markdown` page in their
10 usage, configuration and todo sections (feel free to copy an 10 folder with a description, usage, configuration and todo
11 existing one as a template) 11 sections (feel free to copy an existing one as a template)
12 * Commit messages should begin with the name of the plugin they 12 * Commit messages should begin with the name of the plugin they
13 are for (e.g. `mod_ping: Set correct namespace on pongs`) 13 are for (e.g. `mod_ping: Set correct namespace on pongs`)
14 14
15 Instructions on cloning the repository are at 15 Instructions on cloning the repository are at
16 http://code.google.com/p/prosody-modules/source/checkout - if you have 16 <https://prosody.im/doc/installing_modules#prosody-modules>
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.