Setting up a git service + issue tracking for the project

Code:
<SphinxC0re> Since the project is getting bigger and bigger, the single point of failure would be, that Github might drop us. What about our own project git service (git.cuberite.org) ?

<tycho_> That would be pretty big event. I don't think github has ever droped a public repo.

<SphinxC0re> Oh it has

<tycho_> When?

<SphinxC0re> happens all the time

<tycho_> Can you give an example?

<SphinxC0re> Windows 2000, Spigot

<SphinxC0re> try googeling it

<tycho_> Both DCMA, and we have good comebacks.

<tycho_> If microsoft want to actually sue us it would be interesting.

<SphinxC0re> As long as we are not paying for our service on Github, we are in danger of getting dropped

<tycho_> And we have backups of the repo.

<SphinxC0re> All the big OSS projects have own git services

<SphinxC0re> what about issues

<SphinxC0re> prs

<SphinxC0re> all dropped

<rincewind> In theory I could host it, but I couldn't garanty the reliability of the service

<tycho_> PR's would be minor, we'd lose history thats all.

<rincewind> s/couldn't/can't/

<tycho_> issues would be ennoying, but our own git hosting isn't going to solve that, as none of the git hosting solutions handle that.

<SphinxC0re> Gitlab does

<rincewind> But I would happily mirror it for backup

<SphinxC0re> Every develloper is 'mirroring' the repo all the time

<tycho_> Then thats not just git hosting.

<SphinxC0re> that's correct

<tycho_> But if we're going to host it ourselves we might as well use something dedecated to bug tracking.

<SphinxC0re> Why should we split it into two services?

<SphinxC0re> Gitlab is pretty good

<tycho_> Because something that is dedecated to bug tracking is going to focus more on handling bug tracking.

<SphinxC0re> Okay

<SphinxC0re> But we could use Gitlab dedicated to the sourcecode (user access, PRs, etc) and another service like mantis for bt

<tycho_> The project used to use an flyspray instance.

<SphinxC0re> So what do you think?

<tycho_> I think you're overblowing the issue.

<tycho_> The main reason a lot of the big projects don't use github is they predate it.

<SphinxC0re> What does that mean practically?

<tycho_> If you can get an export and host sorted out than it might be considered, but for the moment we're happy with github.

<tycho_> Thats what bearbin did when we migrated to github.

<SphinxC0re> Gitlab can import from Github directly

<tycho_> What about a host?

<tycho_> The thing is that every tae down so far has been DCMA.

<tycho_> And with a DCMA takedown, if you file a counternotice, github has to put the content back up, or risk losing the safe harbour provisons.

<SphinxC0re> I could host it

<SphinxC0re> I have a 200G vps idling around

<SphinxC0re> 200gb

<tycho_> Set it up, and see whether anyone else is interested.

<tycho_> Personally, until github start taking down repo's outside DCMA, or I see a feature worth moving for, I don't see the point.

<SphinxC0re> Okay