[pkg-apparmor] Navigation through our wiki pages

[intrigeri]

Hi,

u wrote (06 Feb 2015 14:39:46 GMT) :
>> - Ship an existing AppArmor profile in the same Debian package as the
>>   confined software: [...]

Now looks very good!

>> - Testing AppArmor confinement before uploading a new version of
>>   a package [...]

Good.

>> - New AppArmor profile [...]

Good, both for package maintainers and other contributors.

>> - Update an AppArmor profile to include upstream improvements
[...]
> new path: AppArmor -> Contribute
> -> AppArmor/Contribute/MergeProfileFromUpstream

Great.

>> - Modify an already shipped AppArmor profile
>>   - current path: AA -> AA/Contribute -> "Create or patch profiles: Contribute
>>     to Upstream."; good enough?
>>   - lacks doc for the modify-profile usertag

> Same path: AppArmor/Contribute/Upstream
> Added usertag.

Good.

> Should there be a separate page for this story, which would link to the
> relevant other pages?

I think it's good enough this way.

>> - Upstream Debian changes made on an AppArmor profile we ship [...]
> new path: AA->Contribute->MergeToUpstream

Great.

>> - Find out if a problem with a confined software is AppArmor related (users)

Good.

>> - Find out if a bug is AppArmor related (maintainers)

Good.

>> - Other AppArmor related problems
>>   - current path: mostly likely, AA -> AppArmor/PackageMaintainers
>>     that has a link to AA/Contribute at the very bottom

> new path: AA->Contribute->
> -> Reportbug
> Not sure if that is sufficient

Looks good, except for users. How about adding a section pointing to
ReportBug from HowToUse? e.g. after the Debug one.

Great job! All navigation paths look very good now :)

Note that many user stories are now wrong about what navigation path
we meant to implement, though. Do we care enough to keep it updated,
as an internal design doc?

Cheers,
-- 
intrigeri