SILC Secure Internet Live Conferencing

Submitting Patches

If you have created a patch or piece of code for SILC software that you would like us to integrate into the SILC CVS tree, please follow these conventions and guidelines on submitting patches.

- Send patches to the silc-devel mailing list. Add those people on CC that should know about it.

- If you can, create the patch against the current CVS tree. If you cannot then create it against the latest release version.

- Test the patch before sending it. Test that is applies correctly and that the code works correctly.

- Use the unified output format for the diff (diff -u)

- Use diff tool, not cvs diff

- Submit ready patches. If they are not ready then sending them to people who are involved in the development is preferred. The patch might face several round trips so sending patches which are ready is preffered. If you don't know where to send it, send it to silc-devel mailing list.

- Include the patch in the body of the email or as attachment. Do not compress the patch.

- Send separate patches for every big feature/bugfix.

- If you think that your work is benefical to the development of the SILC and would like to be listed in the CREDITS file in SILC packages, you can submit patches for the CREDITS file too. Nobody will be added there without a patch, this way those who don't want to see their name there won't get there.