Redmine is built and maintained by community volunteers. If you enjoy using Redmine and would like give back to the community, there are several ways to contribute back to the project. Also read the How to contribute forum thread for some more specific ideas.

The Teams page gives an overview of the different roles.Check the Member list in the Overview page to get the complete list of Redmine's current contributors and authors.You can also follow code activity via the Repository Statistics page.

Documenting classes and methods using RDoc will help developers understand how Redmine works better. Once you have a copy of Redmine installed, running rake doc will generate the latest RDoc in doc/app. Patches for methods without documentation or with poor documentation would be helpful and an easy way to contribute. List of documentation issues

Make sure you are working on the svn trunk or mercurial default named branch or git master branch.Patches are not accepted for stable releases because someone would have to port a patch to trunk first and then port it back to stable (i.e. double the work).If you use mercurial, you can use graft or mercurial queues extension .

Sometimes issues are reported without all the information needed by a developer. Getting the details of the bug or feature from the reporter and the community will help everyone understand what is needed. If you can also try to reproduce the bug in your own Redmine, adding a note about your Redmine version and the exact steps you took are extremely useful.

Redmine uses a very basic design and user interface. Any improvements to it including new themes, skinning, or interface adjustments could help every user of Redmine. Get involved with the UI / UX Team.