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

[intrigeri]

Hi,

u wrote (16 Jan 2015 14:02:04 GMT) :
> based on our last meeting I've updated the user stories:
> https://wiki.debian.org/AppArmor/Progress#User_Stories

Great stuff.

> Please review them when you can, possibly before our next meeting.

Regarding "Feature: New AppArmor profile", after "And I need to be
taught to ask for a review of that profile", maybe we should add
"And I need to be taught how to upstream this profile". IMO that's how
we should proceed, and we're already linking to
AppArmor/ContributeUpstream so it would make the user story and the
corresponding solution more consistent.

I would rephrase "When I want to request that an existing profile will
be updated with upstream modifications" to "When I want an already
packaged profile to be updated to the latest upstream version".
Clearer to me at least, and possibly more correct English.

The "merge-upstream" usertag name seems unfortunate to me: it doesn't
express the direction of the merge. Maybe "merge-to-upstream"? If we
go this way, correspondingly "update-profile" could become
"merge-from-upstream".

Regarding the debugging documentation, we're now planning to point to
it from various places, meant for different publics. So I'm wondering
if the PackageMaintainers page is the best way to put it. If that
documentation can be written in the same way for all target audiences,
then probably it would be better to extract it into its own,
dedicated page.

Now, once we've refined these, I think we (mostly I ;) should stop
nitpicking => let's implement that and we'll refine stuff as needed
once we get actual experience.

Cheers,
-- 
intrigeri