[pkg-apparmor] AppArmor user stories to create usertags for Debian BTS

[Christian Boltz]

Hello,

Am Freitag, 16. Januar 2015 schrieb u:
> based on our last meeting I've updated the user stories:
> https://wiki.debian.org/AppArmor/Progress#User_Stories
> 
> Please review them when you can, possibly before our next meeting.

I just had a look at them, and I can say the same as Holger - very 
awesome! :-)

One question/idea:

This one:

Feature: Find out if a bug is AppArmor related
  Scenario:
     As a Debian package maintainer,
     Given I ship an AppArmor profile in package P I am maintaining, 
     When I receive a bug report that might be caused by AppArmor, 
     Then I want to be taught how to diagnose whether AppArmor is involved
     And if that is the case, I want to be taught how to put the problem under the pkg-apparmor team's radar.

also applies to "normal users". However I'm not sure if you should add
a separate user story for "normal users" or if it would duplicate things.

The variant for "normal users" would basically be:

  Scenario:
      As a Debian user,
      Given I use a program that comes with an AppArmor profile,
      When I see some strange permission error,
      Then I want to be taught how to diagnose whether AppArmor is involved
      And if that is the case, I want to be taught what to include in a bugreport and how I can fix the problem myself.


Maybe you should also add a link to 
    https://wiki.debian.org/AppArmor/PackageMaintainers#Debugging
on this user story.


Regards,

Christian Boltz
-- 
> You say our final product doesn't have bugs worth tracking?
No. Your final products are in general known for their bugginess.
This could be a marketing decision to assure your jobs. ;-))
[> Stephan Kulow and Eberhard Mönkeberg in opensuse-factory]