Contributing

If you are interested in working on Reference Policy, feel free to contact the developers on the Reference Policy mailing list. All public development related discussion happens on this mailing list. The IRC channel, #selinux on irc.freenode.net, is also appropriate for development discussions.

Patches

When submitting patches, there are a few things to keep in mind:

• Submit patches to the Reference Policy mailing list.
• It is strongly preferred (but not required) that patches be created by "git format-patch -n -s" and sent via "git send-email". This will ensure the patch can be directly imported into the repository, if accepted. Please ensure that the name and email address are correct on your patches before committing to your local repo.
• For patchsets that consist of many patches, a summary email that describes the set. In addition, a link to a git repo from which the set can be pulled is preferred.
• Patches should be relative to git HEAD.
• Make patches relative to the top of the policy source tree (the directory where the Makefile and build.conf are). This is automatically done when using git format-patch.
• Do not increase the version numbers in the policy_module() lines. These may be different by the time your patch is merged, and this will cause headaches for merging the patch. The policy version will be increased when the patch is committed to the repository.