Developing
From LaneWiki
The L’âne website has an entire “Develop” section on the main page.
BY SUBMITTING PATCHES OR OTHER WORK TO THE PROJECT, YOU HAVE AGREED TO THE COPYRIGHT AND OWNERSHIP POLICY LISTED HERE.
Contributors should read and understand the Contribution Directions.
[edit]
Getting Your Patches Included in CVS
Access to the CVS repository is currently limited to a few people. While we intend to open read access to it at some point in the future (it's actually a low priority in the grand scheme of things --Jaybee 10:44, 17 Mar 2006 (EST)), write access will always be more conservative. To get your patches or feature suggestions into L’âne, email them to either the mailing list or User:Jaybee.
[edit]
General Guidelines for Patches
- Don't submit patches which change Perl-layout (as these are not end-user-seen). Brace-style changes are particularly annoying.
- Make sure your patches maintain concurrency/transaction isolation. (This is the single most common reason for patch rejection.)
- Read the notes at Bugzilla -- New features are discussed there. Especially read the release task bugs (there are always at least two: the upcoming release and the release after that release).
- When possible, work with the established inertia of the project rather than writing something from scratch. Don't reinvent the wheel unless it's the most amazing new wheel ever (you'll REALLY have a hard sell there).
- Make patches small and often.
- Discuss changes on the mailing list or with the responsible parties.
- Ask about something on the mailing list before doing it: Many people have likely thought about or implemented your feature. (I have a ton of proof-of-concept code for various things. --Jaybee 10:44, 17 Mar 2006 (EST))
