Do not attach patches to JIRA issues.
Attach a link to a pull request on our GitHub repository instead!
Git at Codehaus terminated
All Codehaus services have now been terminated, thus Codehaus GIT, Nexus, JIRA, mailing lists etc. got migrated to other providers.
IzPack on GitHub (lowering the barrier to collaboration)
Our canonical repository is now exclusively hosted at GitHub where a Git repository is hosted:
- GitHub: http://github.com/izpack/izpack
- read-only access:
- organization-member access:
ssh://email@example.com:izpack/izpack.git (SSH is preferred over HTTPS for pushing changes)
How to collaborate on GitHub
This repository acts as a gatekeeper to the canonical repository at Codehaus, and contributions are expected to be performed using pull-requests.
To minimize bureaucracy overhead, we adopt the following soft rules.
If you are an external contributor:
- fork us on GitHub,
- craft your contribution, preferably in a development branch, making self-contained an many small commits,
- send us a pull request.
The barrier to entry is probably lower than you may expect, however keep in mind that :
- a good contribution has a test,
- a new feature needs to be documented in our wiki once an organization members validates your pull-request,
- you are intended to respect the source code format of existing files.
If you are an official developer:
- do not push directly to the
master branch or to a version branch,
- you may push feature development branches at will, just give them an explicit name and/or a JIRA issue identifier,
- send a pull-request from either your own fork or a feature branch,
- a fellow organization member must approve the pull-request,
- if nobody reacts to your pull request within 3 days then you can merge yourself,
- when reviewing an external contribution, do not forget to ask the contributor to edit the wiki documentation if you approve it.
Fun facts by Ohloh