• Testing/Bugtracking
• Code Review
• How to fix an issue using mercurial
• How to submit your patches/contributions

All contributions need to be licensed under the GNU General Public License, version 3

If the contributor has a significant amount of code, he can add himself to the COPYRIGHT file.

Testing/Bugtracking

• Test your issue on the latest development version.

• Create an issue in our issue tracker (Roundup)

• Assign the issue to you (your username on Roundup) with a comment that you are working on it and you will provide a fix.

Code Review

For reviewing patch, we use Rietveld. See the Help

• Submit your patch and assign the maintainer as reviewer.

• Add the Rietveld link on roundup issue.

How to fix an issue using mercurial

Mercurial Setup

To reflect a certain username in changesets put it into your Mercurial configuration.

 [ui]
 username = User Name <mail@some.where.org>

Mercurial Usage

• Update the repository:

  hg pull
  hg update

• Change the files to fix the issue.

• Commit the fix into your local repository with an explicit message:

For well formed and informative comments please have a look at Writing good changeset comments

  hg commit -m "Fix ... for issue12354"

• Find out the revisions created.

  hg log

We don't accept modifications that come from other named branches than "default"

How to submit your patches/contributions

Reassign the issue to nobody ( - no selection - ) to let maintainers handle it and put one of those solutions on it:

• For a text only contribution you just export the changeset:

  hg export [-o OUTFILESPEC] REV

see http://www.selenic.com/mercurial/wiki/index.cgi/Export

• For binary contribution you provide a compressed changegroup file:

  hg bundle FILE

see http://www.selenic.com/mercurial/wiki/index.cgi/Bundle

• For module contribution you provide an url with your own repository

see http://www.selenic.com/mercurial/wiki/index.cgi/CommunicatingChanges

A good free hoster for open-source mercurial repositories is intuxication: see HowToContributeUsingIntuxication

• If you translate, you can ask for a ssh access to repositories. For this, you must provide a ssh public key and a username.

see http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-keygen