[Pkg-privacy-maintainers] torbrowser-launcher AppArmor profiles maintenance

[intrigeri]

Hi Micah,

ping regarding what follows?

intrigeri (2017-10-26):
> you let us know earlier this year that you're short on time wrt.
> maintaining torbrowser-launcher. We (Debian Privacy Maintainers) are
> sending you quite a few PRs and it takes a while to get them reviewed
> & merged, so we often have to ship the corresponding fixes as a part
> of the Debian delta.

> I've thought of one way to improve the situation a bit: you could
> delegate to me the maintenance of the AppArmor profiles i.e. allow me
> to push changes to the upstream Git repo in the apparmor/ directory.
> I realize it's a big thing to ask. I can take "no" for an answer :)

> This would perhaps save you a little bit of time, allow you to focus
> on non-AppArmor issues and PRs, and smooth things quite a bit for
> downstreams (e.g. Debian & Tails) who could cherry-pick fixes directly
> from the upstream repo instead of having to hunt for them in
> various PRs.

> Another option could be to move the AppArmor profiles out of
> micahflee/torbrowser-launcher: I'd be happy to maintain them
> elsewhere, under the umbrella AppArmor upstream project, and send
> updates to the maintainers of torbrowser-launcher in Debian
> when needed.

> What do you think?

> Thanks for writing torbrowser-launcher in the first place!

Some more context: I want to get content renderer process AppArmor
confinement done in Debian and Tails by the end of February.
https://github.com/micahflee/torbrowser-launcher/pull/280 has been
waiting for 6 months. I'm all for "upstream first" but I can't let
this motto effectively prevent me from improving our users' safety for
much longer.

Cheers,
-- 
intrigeri