Contribute » History » Version 52

Lucile Quirion, 2015-02-23 21:25
Added a link to submitting-a-bug guidelines

1 1 Eric Davis
h1. Contribute
2 2 Eric Davis
5 47 Mischa The Evil
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 message#4325 forum thread for some more specific ideas.
6 2 Eric Davis
7 51 Lucile Quirion
h2. Contributors
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":
13 2 Eric Davis
h2. Code Related
15 4 Mischa The Evil
These require a familiarity with Ruby on Rails development. If you are still new to Rails, Community members can help you if you get stuck with something or have any other questions.
16 2 Eric Davis
17 4 Mischa The Evil
You will need to download a copy of the current development-code. The official code repository is located in Subversion and can be downloaded by following the [[Download]] instructions.
18 2 Eric Davis
19 41 Toshi MARUYAMA
A copy of the source is mirrored to "Bitbucket": (this is maintained by the community) and "GitHub": (this is maintained by the community), if you would like to use Mercurial and Git for development.
20 1 Eric Davis
21 11 Eric Davis
Any questions can be asked in the "Forums": or to the [[Teams|Development Team]] on IRC.
23 1 Eric Davis
h3. Patch checking
24 2 Eric Davis
25 43 Jean-Philippe Lang
Fixing outdated patches so they can apply cleanly to the latest code is very helpful. Many issues will have patches but they will not run on latest version.
26 1 Eric Davis
27 50 Lucile Quirion
See the "Patch Queue": for the list of open patches.
"Patch" is custom [[RedmineIssueTrackingSetup#Trackers|Tracker]] for Issues containing patches
29 49 Lucile Quirion
30 2 Eric Davis
h3. Code documentation
32 11 Eric Davis
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":**
33 2 Eric Davis
h3. Development
35 1 Eric Davis
Patches to fix bugs or add new features are always appreciated. If you are going to work on a specific issue, make a note in the issue details so the developers will know what you're working on.
37 2 Eric Davis
38 9 Eric Davis
h3. Basic process for contributing code:
40 34 Toshi MARUYAMA
# 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).
42 44 Toshi MARUYAMA
If you use mercurial, you can use "graft": or "mercurial queues extension": .
43 38 Toshi MARUYAMA
# Redmine has *tests* (source:trunk/test). Make sure all the existing tests pass. You can check the current build statuses on the [[Continuous integration|Redmine Continuous Integration server]]. You can run "rake test" for entire tests or "ruby test/unit/issue_test.rb" for an each test. For more details, see source:trunk/doc/RUNNING_TESTS
44 9 Eric Davis
# Add tests to show the new functionality and check for bugs
45 32 Toshi MARUYAMA
# Post the patch to the issue.
46 46 Toshi MARUYAMA
*%{color: red}Do not send a pull request on GitHub%*.
47 42 Toshi MARUYAMA
If you use Mercurial or Git, you can create patch series.
See [[How to create patch series on Mercurial and Git]]
49 9 Eric Davis
# Ask for feedback from users and developers. Users will want to to apply the patch and try out the new functionality.  Developers will want to do a code review and run all of the tests.
# Discuss any changes that are proposed and post new patches as needed
52 2 Eric Davis
h2. Non Code Related
53 1 Eric Davis
54 11 Eric Davis
These don't require any software development experience, just time and the desire to help.
55 1 Eric Davis
h3. User support
57 2 Eric Davis
Helping out other users in the "Forums": and the IRC channel (#redmine @ freenode) is always useful. Frequent problems or questions should be brought up so the wiki can be updated to help future users.
59 1 Eric Davis
60 5 Eric Davis
h3. Localization support
61 4 Mischa The Evil
62 7 Eric Davis
[[HowTo_translate_Redmine_in_your_own_language|Translations]] should be kept up-to-date alongside the development of Redmine. You could provide updates of the translations where necessary or proposed to support Redmines I18n-support. **"List of Localization and Translation issues":**
63 4 Mischa The Evil
64 2 Eric Davis
h3. Issue triage
66 52 Lucile Quirion
Sometimes issues are reported without all the [[Submissions#Submitting-a-Bug|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.
67 2 Eric Davis
h3. Design and User interface
70 48 Mischa The Evil
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 [[UX_Team|UI / UX Team]].