2016-02-10 20:49 GMT+01:00 Tavmjong Bah <tavmjong@...8...>:

I would like to see an experiment done:

Import inkscape or lib2geom to GitHub and then import from GitHub into
GitLab. This would help answer the question of what we do if GitHub (or
GigLab) goes the way of SourceForge. (In other words... how portable is
code/issues/bugs between one GitXXX and another GitYYY. If it isn't a
problem, then I doen't need to think too hard about which we pick.)

Tav

Moving code is not an issue as shown by Krzysztof, the big elephant in the room is the issue history. As I said in earlier email lp2gh is available but needs some error handling to properly export a big project from Launchpad.

Although, before I start patching up lp2gh, is Github/Gitlab issue tracker really good enough? The more I keep my eyes open for lessons learned on this topic and the more I read I don't think so. Keeping issue tracking at launchpad seems to be the best option (if we don't want to run our own, like phabricator mentioned by Bryce in separate mail thread).

Just now I stumbled on a hackernews discussion about moving away from Github due to poor issue tracker [1] and [2]. Other projects have similar problems with the issue system on Github, [3] and [4]. If we feel that keeping code and issue tracking together at all costs I think HuBoard [5] and ZenHub [6] could be alternatives to "add on top" of github.

[1] https://news.ycombinator.com/item?id=11082745
[2] https://github.com/eslint/eslint/issues/5205
[3] https://github.com/dear-github/dear-github
[4] https://github.com/dear-github/dear-github/issues

[5] https://huboard.com/pricing
[6] https://www.zenhub.io/open-source

Regards

Christoffer Holmstedt