Differences between revisions 1 and 24 (spanning 23 versions)
Revision 1 as of 2013-04-05 15:27:11
Size: 1942
Editor: ?IntRigeri
Comment: Import content from the main AppArmor page.
Revision 24 as of 2015-01-22 16:39:57
Size: 2715
Editor: UlrikeUhlig
Comment: correct link
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Navigation(siblings)>>
----
<<TableOfContents>>

This page explains how to contribute to !AppArmor in Debian.

== Infrastructure ==

 * [[http://anonscm.debian.org/gitweb/?p=collab-maint/apparmor-profiles-extra.git;a=summary|Git repository for extra profiles]]
 * [[https://alioth.debian.org/projects/pkg-apparmor/|Alioth project]]
 * [[https://udd.debian.org/bugs.cgi?release=jessie&merged=ign&fnewerval=7&flastmodval=7&apparmor=1&sortby=id&sorto=asc|Bugs in the packages we maintain]]

<<Anchor(contactteam)>>
== Interacting with the team ==

 * '''Email''': pkg-apparmor-team@lists.alioth.debian.org
 * '''IRC''': ''#apparmor'' on irc.oftc.net (general AppArmor discussion channel)
Line 4: Line 22:
 * Some of us test a few AppArmor profiles, mainly grabbed from Ubuntu.
 * Patches to add profiles to Debian packages are being filed: [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=new-profile;users=apparmor@packages.debian.org|Bugs tagged with "new-profile" (used for adding profiles to packages)]].
 * See the [[AppArmor/Progress|progress tracking page]].
Line 7: Line 24:
== Next goals == == Goals ==
Line 9: Line 26:
For Jessie, we'd like AppArmor enabled by default and more enforced profiles; specifically For Jessie, we'd like more enforced profiles; specifically
Line 16: Line 33:
The general workflow wrt. profiles is to find existing profiles, test them in the context of Debian sid, adapt them if needed, and propose them to Debian package maintainers. The general workflow wrt. profiles is to find existing profiles, test them in the context of Debian sid, adapt them if needed, and either include them into apparmor-profiles-extra, or propose them to Debian package maintainers.
Line 22: Line 39:
 * '''Test''': [[AppArmor/HowTo|enable AppArmor]], enforce a bunch of profiles, report bugs and/or happiness.
 * '''Fix bugs''' tagged "new-profile".
 * '''Fix bugs''' in the apparmor source package.
 * '''Import''' profiles from Ubuntu: get the latest version, test, prepare Debian patch, file bug tagged "new-profile".
 * '''Documentation''': write documentation about the user side of things.
 * '''Test''': [[AppArmor/HowToUse|enable AppArmor]], enforce a bunch of profiles, report bugs and/or happiness.
 * '''Fix usertagged''' [[https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-apparmor-team@lists.alioth.debian.org|bugs]].
 * '''Fix bugs''' in [[https://udd.debian.org/bugs.cgi?release=jessie&merged=ign&fnewerval=7&flastmodval=7&apparmor=1&sortby=id&sorto=asc|the packages we maintain]]
 * '''Fix bugs''' in the DebianPts:apparmor package.
 * '''Import''' profiles from Ubuntu: [[AppArmor/Contribute/Import|get the latest version, test, prepare Debian patch against apparmor-profiles-extra, submit patch to the BTS or push a branch to collab-maint]].
 * '''Create''' or patch profiles: [[AppArmor/Contribute/Upstream|Contribute to Upstream]].
 * '''Documentation''': improve the [[AppArmor/HowToUse|documentation about the user side of things]].
Line 28: Line 47:

== Contact Information ==

We have no mailing-list yet, but once you and others tell us you want to join the dance, it may be worth creating one;
in the meantime:

 * intrigeri (intrigeri@debian.org)
 * AppArmor maintainers (apparmor@packages.debian.org)
 * '''Organize''' by keeping the [[AppArmor/Progress|progress tracking page]] up-to-date.


This page explains how to contribute to AppArmor in Debian.

Infrastructure

Interacting with the team

Current status

Goals

For Jessie, we'd like more enforced profiles; specifically (in decreasing order of priority):

  1. some of the Usual Suspects™ on the Desktop: evince, iceweasel, isc-dhcp-client, pidgin;
  2. some software that is particularly important in the context of Tails and other privacy-sensitive contexts: Tor, Vidalia;
  3. some low-hanging fruits from Ubuntu's Supported profiles in main list: apache2, libvirt, ntp...

The general workflow wrt. profiles is to find existing profiles, test them in the context of Debian sid, adapt them if needed, and either include them into apparmor-profiles-extra, or propose them to Debian package maintainers.

At some point, it would be great to share the profiles maintenance e.g. with Ubuntu.

How to help