Githost going away. Choose GitLab.com, Framagit, or self-host?

git
ops

#21

At this point, I don’t see any other option being truly superior. So, I think all the trade-offs point toward going forward with GitLab.com. I see the EE issues as themselves being mixed because while they are proprietary, we will actually benefit from using them.

I think planning the move at this point makes sense. There will be several things to think through.

That said, I’d like to get consent from the rest of the team and hear out any push for framagit (I have sympathies to the idea of going with them if we talk to them and they want us).

P.S. chatted with GitLab folks at OSCON this week

… discussed how I see them as the very best of the projects that are still in the wrong overall club (the most FLO, ethical, ideal of the non-fully-FLO VC-backed stuff). Suggested to them to consider being a Benefit Corp. Person told me that their goal is to have an IPO as their exit for the VC investors and they see a buy-out as the worst case.

Aside from the other various FLO issues (which I acknowledge as a matter of economics), it’s the VC obligations that are the most troublesome. Both an IPO or a buyout (and the influence of the VC investors now) mean pressure for GitLab to sell out their values even if they could be profitable otherwise. If they were a Benefit Corp, they’d be more tied to making profit without compromising their core values… I may contact Sid and push this issue specifically…


#22

Reminder that the first principle of sociocracy is government by assent, not consent. :slight_smile: In other words, if people have an objection, they should let me know. Otherwise the plan shall move forward.


#23

I made a “milestone” in our private ops repo where we can track multiple issues in the process of moving to GitLab.com — those who have access can check that out and potentially add issues there (although we should continue related general discussion here on the forum)


#24

Quick update: we’re potentially proceeding with the GitLab.com migration 2018-12-23T15:00:00Z. This will take a few hours, and we’ll post here again when we’re done.

Drop by our IRC channel/Matrix room if you need help or have any questions. Thanks!


#25

@team We will be starting this very soon, please stop using git.snowdrift.coop, and we’ll update here when we’re set up on gitlab.com


#26

We were able to migrate most repos, but the design and code repos failed to import. So, we are treating today as a test run and will continue using git.snowdrift.coop for the moment; once we’ve figured out the import issues, we’ll run the migration for real.

I suspect that the error has to do with the size of these repos. If that’s true, we should be able to ask the githost people for an export that omits stuff we don’t care about (example of how to do that here). I’ve sent an email to githost support, we’ll see what they say.