On Fri, 2017-01-06 at 00:51 -0800, Bryce Harrington wrote:
"The time has come," the Walrus said, "To talk of many things: Of shoes — and ships — and sealing-wax— Of cabbages — and kings — And why the sea is boiling hot—
And whether Inkscape should switch to gitlab or github or entirely other things."
We need a requirement that all e-mail threads are started with poetry ;-)
In github's favor is that it holds the greater mindshare. Where we to go with it we'd potentially tap into a larger community of developers, which potentially could translate into a greater level of new participation in the project. github also seems like it's received a greater amount of polish and has some feature advantages (github's CI was seen as a huge pro last time we looked).
I think where this mindshare comes into play is less with drive-by contributions as much as integrations with other services. There are a lot of cool tools built that "just work" with Github. Some only support that as a backend (even though they probably just grab git and work on it, they just don't have an option in the UI) What I'm not sure about is whether we'd end up using any of those services anyway.
Since we last discussed it Gitlab's CI has really stepped up the game. I'd say that if we're just looking at the core services Gitlab wins there today. Github/Travis becomes a more interesting discussion.
gitlab is an up-and-comer and is actively acquiring analogous features to github. A big pro for us is that gitlab is FOSS whereas gitlab is free but proprietary. With gitlab we'd also hold the option of self-hosting, which might not matter or might be a huge advantage, it's hard to say.
And they also seem to be pushing for adoption into the FOSS community. They're showing up at our conferences and stuff like that. Easy to get stickers ;-)
We also liked the integration between bzr and the LP bug tracker -- we'll lose this, although github/gitlab provide different integration opportunities that might compensate a bit.
Since the last time we've discussed it LP's Git features have matured a lot. I don't think that they're on par with Github/Gitlab yet, but we should probably put into consideration just moving to Git and sticking with LP, as it might be a simpler transition.
How would we undertake the transition? suv made a good point today that migration of smaller codebases first can be helpful so that the learning curve can be digested in pieces rather than in one big go.
+1, go suv!
Let me know your thoughts, and help us drive towards a consensus for github or gitlab.
For me, right now, my feelings are towards Gitlab. I think that we should stick with a FOSS solution overall and Github doesn't have enough advantages to override that.
Ted