Rules of the road

This page captures what we hope is a pragmatic and reasonable process for developing freeseer code. We are open to suggestions, and we’ll no doubt refine this process as the project evolves.

Major changes

All user interface changes, changes to APIs, and changes in behaviour should be follow the following process. They will be targeted for the next major release.

1) Capture the proposed change in an issue with the prefix RFC:
2) Please be concise, but include enough detail to communicate your proposal. Include sequence diagrams, mock-ups, and other visual aids as appropriate.
3) Current approval criteria is +2 on the issue vote tracker
4) Follow the commit rules

Minor changes

Bug fixes, trivial user interface improvements, and documentation updates should follow the following process. They will be targeted for the current release and potentially propped to previous releases on a priority basis.

1) Capture relevant details concisely in the code comments & issue details
2) Follow the commit rules

Commit rules
1) Please review your code and get email list approval from least 2 other people. Any disagreement will result in a vote by committers.
2) Please test thoroughly before committing. If you do not have necessary hardware, please use the mailing list to partner with others to cover off testing.