Differences between revisions 41 and 42
Revision 41 as of 2015-02-02 12:35:29
Size: 3154
Editor: UlrikeUhlig
Revision 42 as of 2015-02-02 16:04:37
Size: 3253
Editor: UlrikeUhlig
Comment: add mailing list link
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 * '''Email''': pkg-apparmor-team@lists.alioth.debian.org  * '''Email''': pkg-apparmor-team@lists.alioth.debian.org (see https://lists.alioth.debian.org/mailman/listinfo/pkg-apparmor-team for mailing list archives)

This page explains how to contribute to AppArmor in Debian.


Interacting with the team

Current status

How to participate

Ship an AppArmor profile in "your" package

  • ?Import a profile from upstream

  • ?Import a profile from apparmor-profiles-extra to the package to the package you maintain

  • ?Learn how to package using dh_apparmor, ie. if your upstream provides an AppArmor profile for the packaged software

  • To create a completely new profile, see section "Create new profiles" on this page.
  • Debug and test

Improve quality of AppArmor profiles

Use AppArmor

Enable AppArmor, enforce a bunch of profiles, test and report and triage bugs and/or happiness.

Upstream Debian changes to AppArmor profiles

We want to keep our delta with upstream as low as possible. That is why we encourage you to patch profiles upstream: Contribute to Upstream.

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. Create or patch profiles: Contribute to Upstream.

Import Upstream changes to Debian

Update profiles shipped in apparmor-profiles-extra to the latest upstream version

Debug, report triage and fix bugs