I think GitHubs issue tracker is bad for Inkscape, but it might just enough for lib2geom. 

Would hosting lib2geom on github, utilizing TravisCI, be an option...? lib2geom is just a support library of Inkscape, so I don't see the "must be on same host" so important. And Krzysztof has already tested out GitHub/TravisCI quite a lot, so we know it works.

I think that combination is really good for productivity, as it's a popular combination in open source world of today.



Mvh


/Olof
-----------------
3-5-åriga småttingar i närheten?
Lek & lär siffror och bokstäver via mobilen m.h.a. Alfamem till Android.


On 12 February 2016 at 07:42, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2016-02-11 21:29 GMT-08:00 Christoffer Holmstedt
<christoffer.holmstedt@...400...>:
> 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.)
>
> 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).

I also think that GitHub's issue tracker is completely inadequate for us.

> 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

These GitHub extensions are geared towards developers and do not solve
two fundamental user-facing problems in the issue tracker: 1. Very
restrictive set of allowed attachments, 2. Not possible to configure
an issue template. These are absolute showstoppers and we can't use
GitHub issues because of this.

GitLab's issue tracker does not have these problems, but it doesn't
integrate with Travis CI. However, Travis CI is open source, so
someone could theoretically add that integration.

Best regards, Krzysztof

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel