...
It tries to be normative without putting too much bureaucracy in the processes.
General rules
- Be friendly. The IzPack community has always been like that and we don't want that to change!
- A new feature must always be documented, else there is no point in adding it!
- Major enhancements must be proposed and discussed via IzPack Enhancement Proposals.
- Any fix or enhancement must be attached to an issue from our JIRA instance at http://jira.codehaus.org/browse/IZPACK (this allows proper planning of the releases as well as generating complete and meaningful release notes).
Please keep in mind that most IzPack developers are volunteers that are not paid for developing it. We do it for fun on our free time, so please don't expect the same level of support as if we were a company (but we're doing our best to be as close to that as possible 
).
Rules for developers
- Use meaningful comments when doing a Subversion commit.
- When doing a commit based on a patch from a contributor, make sure to mention the contributor name in the comment.
- Never commit incomplete changes (Subversion is not a backup system).
- Working on experimental changes is encouraged, but in this case use a branch.
- Like anybody else, use IzPack Enhancement Proposals and our JIRA instance.
- Don't maintain Versions.txt anymore, we will extract release notes from JIRA starting from IzPack 4.0 and beyond.
- You may do a commit without a related JIRA issue, but make sure you have a very good reason not to do so.
- Subscribe to the SCM mailing-list to get notified of SVN commits and JIRA activity.
- Do not hesitate to pick new JIRA issues: both the other developers and the issue submitter will thank you for the work!
...