News for hackers. Stuff that matters.
Re:Gitlab's Journey from Azure to GCP by reificator on Thursday May 02, 2019 @09:43PM (#19814760)
Oh god please no. I want to be using Gitlab 5 years from now, not planning a migration back to Github or whatever when Google loses interest in another toy.
Re:Gitlab's Journey from Azure to GCP by jasonvorhe on Friday May 03, 2019 @03:28AM (#19816278)
If Google acquired GitLab, they'd offer it as a managed platform for GCP, which they're unlikely to shut down since contracts and SLA require a heads up of about a year before they can remove a service that is GA from their platform.

Just look at Google+: it still lives on for G-Suite customers while the public version has been shut down.

I don't expect GitLab to be of much interest to Google though: A lot of their stuff competes with services Google has on GCP, Ruby/Rails doesn't fit that well into their Python/Golang/Java stack and a remote-only company wouldn't fit into their office-bound culture.

Re:Gitlab's Journey from Azure to GCP by tinco on Thursday May 02, 2019 @10:26PM (#19814978)
The whole reason I picked Gitlab is that it doesn't matter what Gitlab does, if they pick a weird direction I can just self host and do what I want.

Gitlab is big enough that should they ever be killed by a Google acquisition (I don't think that's likely), a strong enough community would sprout and keep maintaining it.

Re:Gitlab's Journey from Azure to GCP by jrochkind1 on Thursday May 02, 2019 @10:58PM (#19815138)
Do you have examples of open source software in a similar situation (one company providing coordination and final approval in the previous project; similar complexity level to Gitlab, whatever that is), where that happened successfully?

I'm not challenging necessarily, I legitimately am interested in examples.

Re:Gitlab's Journey from Azure to GCP by daxelrod on Thursday May 02, 2019 @11:55PM (#19815380)
It depends on your definition of “kill”.

OpenSolaris -> Illumos

Hudson -> Jenkins

OpenOffice -> LibreOffice

MySQL -> MariaDB (not killed, but forked out of fear it would be)

And a non-Oracle example:

Node.js -> IO.js (arguable - forked because Node dev was stagnant, eventually merged)

Re:Gitlab's Journey from Azure to GCP by oblio on Friday May 03, 2019 @09:54AM (#19818433)
All those had communities outside the main company long before they "moved out". What's the percentage of external contributors to GitLab? 1%?
Re:Gitlab's Journey from Azure to GCP by tinco on Friday May 03, 2019 @05:26AM (#19816810)
Hmm what about the Blender project, would that one count?

I admit it's difficult to come up with examples, though I don't know of any failures either. RethinkDB has been sort of a failure, but it was never very popular to begin with.

Re:Gitlab's Journey from Azure to GCP by hansflying on Friday May 03, 2019 @03:14AM (#19816227)
GitHub can also be self-hosted: https://github.com/enterprise
Re:Gitlab's Journey from Azure to GCP by dewey on Friday May 03, 2019 @03:40AM (#19816342)
You can't compare that as it's a paid enterprise on-prem version not something you can self-host and keep running as long as you want. You won't get community fixes for it like it would be the case if Google were to abandon Gitlab if an acquisition would be the case.
Re:Gitlab's Journey from Azure to GCP by teddyh on Friday May 03, 2019 @05:19AM (#19816775)
That’s not what “self-hosted” means.
Re:Gitlab's Journey from Azure to GCP by SlowRobotAhead on Friday May 03, 2019 @12:04AM (#19815419)
Agreed! I’d drop Gitlab in a hot second or f they were acquired by Google.

If you told me 10 years ago I’d be way more interested in working with Microsoft than Google I wouldn’t have believed you.

Re:Gitlab's Journey from Azure to GCP by emilycook on Friday May 03, 2019 @12:35PM (#19819881)
Hi, GitLab employee! Don't worry, our plan is actually to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy/
Re:Gitlab's Journey from Azure to GCP by emilycook on Friday May 03, 2019 @12:36PM (#19819888)
Hi, GitLab employee! Don't worry, our plan is actually to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy/