remove siblings macro, link to main apparmor page
|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
|Line 6:||Line 5:|
|This page explains how to contribute to !AppArmor in Debian.||----
This page explains how to contribute to '''AppArmor''' in Debian.
|Line 39:||Line 40:|
|==== Upstream Debian changes to AppArmor profiles ====
Profiles, which have been patched in Debian, should also [[AppArmor/Contribute/MergeToUpstream|be merged upstream]].
This page explains how to contribute to AppArmor in Debian.
Interacting with the team
Email: firstname.lastname@example.org (see https://lists.alioth.debian.org/mailman/listinfo/pkg-apparmor-team for mailing list archives)
IRC: #apparmor on irc.oftc.net (general AppArmor discussion channel)
How to participate
Ship an AppArmor profile in "your" package
Import a profile to a package for the first time, that is learn how to package using dh_apparmor
To create a completely new profile, see the "Create new profiles" section.
Improve quality of AppArmor profiles
Create new profiles
We want to keep our delta with upstream as low as possible. If you want to submit a new profile, this should be done upstream first.
The AppArmor parser silently ignores rules that are not supported by the running kernel. To check which rules are actually enforced, pass the --warn=rules-not-enforced --warn=rule-downgraded options to apparmor_parser.
Import Upstream changes to Debian
Debug, report triage and fix bugs
Report and triage bugs and/or happiness
Fix bugs in the packages we maintain
Fix bugs in the apparmor package
Fix usertagged bugs
Organize by keeping the progress tracking page up-to-date
Documentation: improve the documentation about the user side of things
In order to organize the Debian Wiki documentation about AppArmor, we have set up a set of user stories.