How To Contribute
The simplest way to contribute code directly is to make modifications in a recent source revision and send in the patch as soon as possible. You can send the patch to the mailing list, upload it to the developer group file area, attach it to an issue in the Google Project, or email it to me. If you send a diff file, make sure it is done as an attachment as email can mutilate them.
Make changes wherever you want, no one "owns" any part of the project, it's all up for grabs, the most appropriate patches are accepted.
Guidelines
- Make sure your employer, institution, mom, etc. allow you to contribute.
- Do not contribute code which is not public domain or under the MIT license, regardless of size.
- Please make sure if the code is from another project that the license and conditions text are exactly the same, some projects say they use the MIT license but do not use the same text. Please reference the originating project in the contribution.
- By submitting your own code you are automatically agreeing that the code is to be placed under the MIT license and to become part of the project.
What else you can contribute
- Any source code which you think will help the project, in any reasonable form.
- Reference to other public domain or MIT licensed software which may be helpful to the project.
- Behavioral descriptions which supplement the Apple documentation.
What to expect
- All patches are reviewed and put in as soon as possible.
- If the patch has not been integrated into a recent version of the source, expect it to take a long time to get in as someone will have to do work to integrate it. That is OK, just don't expect it to go in quickly.
- There is no guarantee that your contribution will be merged into the repository.
Periodically I will update the credits with contributors who have made a significant quantity of changes, please don't take offense if you don't get credited right away, it'll happen.