[apparmor] test git repo

[intrigeri]

Steve Beattie:
> Beyond the immediate conversion landing location, I'm supportive
> of moving code-hosting and merge requests to github or gitlab and
> the integrated CI environments that they enable. The whole point
> of converting to git is to make it easier for people to contribute,
> and choice of code hosting location affects that.

Yes. I'm not sure I'll manage to gather enough energy to join the IRC
meeting (after the loooong day that will be for me), so I'll share my
thoughts here.

Git is still a second-class citizen in Launchpad, which makes the
contributor experience worse than it could be, and worse than it is on
more opinionated (towards Git) platforms. *I* manage to get around it
mostly thanks to browser bookmarks and history. I doubt it offers
a smooth experience for first-time and pass-by contributors.

For example:

1. On https://code.launchpad.net/~intrigeri I see my bzr branches but
   my Git branches are somewhat hidden behind a "View Git
   repositories" link.

2. The AppArmor Profiles repo was migrated to Git a while ago. This
   is great but the only way I manage to find the "Active reviews"
   page every time I need is is… a browser bookmark:
   https://code.launchpad.net/apparmor-profiles/+activereviews

   I've just spent 5 minutes trying to find a link to it, and
   eventually managed to find one to the Git merge requests via
   "Code" → "master" → "Branch merges". But the page I'm landing on
   does not list bzr merge requests.

   In comparison, in GitLab and GitHub pull requests are one click
   away from a project's home page.

OTOH I guess using Launchpad's bug tracking system makes it vastly
easier to track the status of AppArmor issues upstream / in Ubuntu,
compared to what it would be if we moved bug tracking to another
platform. I don't directly benefit from it myself, but it probably
matters. But perhaps there's nice integration available between
Launchpad's bug tracking and {GitHub,GitLab} Git hosting?

Cheers,
-- 
intrigeri