4776
Comment: moving user stories to a dedicated page
|
4952
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
These user stories have been set up to check our documentation asnwers all possible probably issues Users, contributors, maintainers might face with AppArmor in Debian. | #language en ~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: none-~ <<Navigation(siblings,1)>> ---- <<TableOfContents>> These user stories have been set up to check our documentation answers all possible probably issues which users, contributors, maintainers might face with AppArmor in Debian. |
Line 4: | Line 10: |
Feature: Ship an existing AppArmor profile in the same Debian package as the confined software | Feature: Ship an existing AppArmor profile confining software S in the Debian package that ships S |
Line 23: | Line 29: |
→ Documentation [[AppArmor/PackageMaintainers#Testing]] | → Documentation [[AppArmor/Debug]] |
Line 39: | Line 45: |
→ Documentation [[AppArmor/PackageMaintainers#Testing]] | → Documentation [[AppArmor/Debug]] |
Line 55: | Line 61: |
→ Documentation: [[AppArmor/Contribute/Import|Updating a profile in Debian’s apparmor-profiles-extra package]] | → Documentation: [[AppArmor/Contribute/MergeProfileFromUpstream|Updating a profile in Debian’s apparmor-profiles-extra package]] |
Line 95: | Line 101: |
→ Documentation: [[AppArmor/PackageMaintainers#Debugging]] | → Documentation: [[AppArmor/Reportbug]] → Documentation: [[AppArmor/Debug]] |
Line 109: | Line 117: |
→ Documentation: Debugging/Providing useful logs | → Documentation: [[AppArmor/Debug]] |
Line 124: | Line 132: |
→ Documentation: [[AppArmor/Reportbug]] |
Translation(s): none
/Contribute /Debug /HowToUse /OutReachyRound9 /Progress /Reportbug /UserStories |
Contents
These user stories have been set up to check our documentation answers all possible probably issues which users, contributors, maintainers might face with AppArmor in Debian.
1 Feature: Ship an existing AppArmor profile confining software S in the Debian package that ships S
2 Scenario:
3 As a Debian package maintainer,
4 When I want to ship an AppArmor profile in package P,
5 Given this profile exists upstream or in the apparmor-profiles-extra package
6 Then I need to be told how to do that.
7
→ Documentation: ?AppArmor/PackageMaintainers
1 Feature: Testing AppArmor confinement before uploading a new version of a package
2 Scenario:
3 As a Debian package maintainer,
4 Given I ship an AppArmor profile in package P,
5 When I prepare an upload for a new upstream release,
6 Then I want to check that it still works under AppArmor confinement.
7
→ Documentation AppArmor/Debug
1 Feature: New AppArmor profile
2 Scenario:
3 As a Debian package maintainer or as a Debian contributor,
4 Given that I have written or found an AppArmor profile for package P,
5 And this profile does not exist in apparmor-profiles-extra nor upstream,
6 Then I need to be taught how to test the profile
7 And I need to be taught to ask for a review of this profile
8 And I need to be taught how to upstream this profile
9
→ Usertag "new-profile"
→ Documentation AppArmor/Debug
→ Documentation: ?AppArmor/ContributeUpstream
→ Usertag "merge-from-upstream"
→ Usertag "patch" with attached patch
→ Documentation: Updating a profile in Debian’s apparmor-profiles-extra package
→ Usertag "modify-profile"
→ Usertag "merge-to-upstream"
Documentation ?AppArmor/ContributeUpstream
1 Feature: Find out if a problem with a confined software is AppArmor related
2 Scenario:
3 As a Debian user,
4 Given I use a program that comes with an AppArmor profile,
5 When this software does not behave as it should or crashes,
6 Then I want to be taught how to diagnose whether AppArmor is involved
7 And if that is the case, I want to be taught what to include in a bugreport and how I could fix the problem myself.
8
→ Usertag "help-needed", to request help for initial diagnosis
→ Usertag "buggy-profile" if AppArmor has been identified as culprit
→ Documentation: AppArmor/Reportbug
→ Documentation: AppArmor/Debug
1 Feature: Find out if a bug is AppArmor related
2 Scenario:
3 As a Debian package maintainer,
4 Given I ship an AppArmor profile in package P I am maintaining,
5 When I receive a bug report that might be caused by AppArmor,
6 Then I want to be taught how to diagnose whether AppArmor is involved
7 And if that is the case, I want to be taught how to put the problem under the pkg-apparmor team's radar.
8
→ Usertag "help-needed", to request help for initial diagnosis
→ Documentation: AppArmor/Debug
→ Usertag "buggy-profile" if AppArmor has been identified as culprit
→ Usertags: will be refined as we go
→ Documentation: AppArmor/Reportbug
→ Currently, there is a usertag called "ux" for a bug related to auditd's formatting of AppArmor related messages and "platform" for #775331