On Tue, Oct 03, 2017 at 09:11:47AM +0200, intrigeri wrote: > 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.
Thanks, it's appreciated. > 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. Yes, all the above is all too true. Launchpad has frankly not had the level of development investment to make drive-by or even semi-frequent contributions via git convenient or easy. Even finding a specific git tree you're looking for on launchpad can be problematic. So to be explicit, I'm not aware of anyone seriously suggesting we stay with Launchpad. What I'd personally rather hear are the pros and cons of maintaining a project on github vs gitlab, because I don't have experience doing so with either service. Most of my personal experience with either has been related to tracking down individual commits to cherry-pick for security updates, along with filing PRs. (I personally have a mild bias against github due to it not being open source and seemingly fostering a culture of harassment and abuse.) > 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? There is sadly not, most of the remote bug tracking work done in launchpad was implemented before the rise of github. Really, the only caveat with bug tracking is that we have a non-trivial amount of open issues in Launchpad, that people like Christian have put in a significant amount of work to triage and organize, that will need to be dealt with one way or the other. But it's also a pretty poor outsider experience to have the primary bug reporting location in one place and the rest of the project interaction in another. Thanks again for your feedback! -- Steve Beattie <sbeat...@ubuntu.com> http://NxNW.org/~steve/
signature.asc
Description: PGP signature
-- AppArmor mailing list AppArmor@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
