-
Notifications
You must be signed in to change notification settings - Fork 169
HowToContribute
Miroslav Grepl edited this page Sep 21, 2015
·
8 revisions
##Contributing If you are interested in Fedora SELinux policy development, feel free to contact us on the
For more detail questions, ideas and bugs, you can use
- Fedora SELinux mailing list
- Red Hat Bugzilla
- #fedora-selinux on irc.freenode.net
or upstream channels
- Reference Policy GitHub
- Reference Policy mailing list
- #selinux on irc.freenode.net
Fedora SELinux policy changes should be submitted by pull requests on GitHub.
##Patches When submitting patches against Fedora Policy Github, try to follow these advices:
- Make sure you create a new pull request against up-to-date repositories.
- Do not increase the version numbers in the policy_module() lines.
- Make logical and small changes per a commit.
- More commits can be a part of one pull request.
- If possible, try to avoid disjoint changes to different modules in a single commit.
- Proposed changes should not break anything.
- Proposed changes should be
- tested
- commented
- compilable
For more details, where/how you could create/test your fixes, see Packaging section on thiw wiki.