Live data from Hacker News

Wikimedia is moving to Gitlab

mediawiki.org

21–30 of 408 posts

Re: Wikimedia is moving to Gitlab

#21
post #17

Earlier quoted context omitted.

Wikimedia will self-host Gitlab. They can use whatever limits they want.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

My understanding is you can self host and pay a sub and get access to all the other features. I may be wrong.

Re: Wikimedia is moving to Gitlab

#22
post #17

Earlier quoted context omitted.

Wikimedia will self-host Gitlab. They can use whatever limits they want.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

All of those are self-hosted.

"Core" is the free community edition. The others are not open source/free and require payment.

Core is plenty for most use cases. That table makes it look like it has almost no features, but most items in the list are either advanced or pretty niche.

Re: Wikimedia is moving to Gitlab

#23
post #18
post #6

Earlier quoted context omitted.

Clear mapping of change request == commit, allowing for easy building of multiple in flight change requests, rearranging them by using git rebase, updating with push to refs/for/master. Easy diffing between states of the CR (patch sets), so you can see what changes since the last round of comments, even if it spanned multiple updates. This is the feature I miss the most from other code review systems - be able to eas…

> Clear mapping of change request == commit, was forced to use Gerrit by a client. I could never get the hang of this, I like to do frequent commits on short lived branches and using vanilla git. I never wanted any more features other than a nice UI to encourage people to review.

The nice UI for review works well exactly because it limits the functionality available to users and enforces a particular commit model. If you don't do that, you get the code review mess that are Github/GitLab PRs/MRs - difficult to tell apart how commits relate to the change and how it progresses through review, because the entire branch history is free-form.

Re: Wikimedia is moving to Gitlab

#24
post #18
post #6

Earlier quoted context omitted.

Clear mapping of change request == commit, allowing for easy building of multiple in flight change requests, rearranging them by using git rebase, updating with push to refs/for/master. Easy diffing between states of the CR (patch sets), so you can see what changes since the last round of comments, even if it spanned multiple updates. This is the feature I miss the most from other code review systems - be able to eas…

> Clear mapping of change request == commit, was forced to use Gerrit by a client. I could never get the hang of this, I like to do frequent commits on short lived branches and using vanilla git. I never wanted any more features other than a nice UI to encourage people to review.

One thing one has to get away from that one change request == one issue. Multiple small commits as separate change requests for one story are fine as long as they work standalone (which is generally a good idea, e.g. to enable bisecting)

Re: Wikimedia is moving to Gitlab

#26
post #17

Earlier quoted context omitted.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

All of those are self-hosted. "Core" is the free community edition. The others are not open source/free and require payment. Core is plenty for most use cases. That table makes it look like it has almost no features, but most items in the list are either advanced or pretty niche.

Right, so is Wikimedia going to pay $$$ to GitLab for one of the more advanced licenses?

Re: Wikimedia is moving to Gitlab

#27
post #17

Earlier quoted context omitted.

Wikimedia will self-host Gitlab. They can use whatever limits they want.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

They probably use the free Open Source option, which gives access to the top tiers for free.

https://about.gitlab.com/solutions/open-source/

Re: Wikimedia is moving to Gitlab

#28

it was interesting to read their reasons for not using github, especially related to no control over bans or sanctions. Microsoft could pull the rug out from under them at any time if they got pressure from somebody like China.

I'm not sure how GitLab is a better option. China could pressure them too.

Re: Wikimedia is moving to Gitlab

#29
post #17

Earlier quoted context omitted.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

All of those are self-hosted. "Core" is the free community edition. The others are not open source/free and require payment. Core is plenty for most use cases. That table makes it look like it has almost no features, but most items in the list are either advanced or pretty niche.

[deleted]

Re: Wikimedia is moving to Gitlab

#30

it was interesting to read their reasons for not using github, especially related to no control over bans or sanctions. Microsoft could pull the rug out from under them at any time if they got pressure from somebody like China.

I'm not sure how GitLab is a better option. China could pressure them too.

GitLab is open source and can be self-hosted by Wikimedia.
Post reply on HN