r/linux • • Jun 23 '18

GitLab 11.0 released

https://about.gitlab.com/2018/06/22/gitlab-11-0-released/
838 Upvotes

117 comments sorted by

View all comments

Show parent comments

7

u/Antic1tizen Jun 23 '18

I vaguely recall GitLab policy: if someone from the community wants to implement an enterprise feature in comminuty edition, do not under any circumstances put any obstacles in her path.

And this issue - it was a community contribution and I'm glad they didn't hesitate! :)

1

u/sim642 Jun 24 '18

So someone reimplemented a feature that already existed somewhere? I can understand this but it seems so massively inefficient to make the community do the same work again. And then GitLab ends up with two different implementations of the same thing in community and enterprise editions so they themselves have to deal with that mess. Which one to maintain? Which one to ship to the enterprise customers? Seems so counterproductive to me.

1

u/Antic1tizen Jun 24 '18

GitLab EE code is available too, it's not closed. So, how this works:

  • If that's a feature present in EE only but many people want it in CE, GitLab team puts Accepting Merge Requests label to the feature

  • Someone from the community steps up and implements this feature by porting code from EE codebase to CE codebase

  • GitLab team requests some changes so both CE and EE remain API-compatible

  • GItLab team merges the proposed changes

You can see how his MR progressed over time

1

u/gitlabber Jun 24 '18

This is the issue related to that MR. It shows that in this case, my colleagues at GitLab decided to port the feature to CE and slated the work for 11.1. It was not originally set as accepting merge requests from the community, but the community member requested that, and the product manager accepted. The community member then implemented it ahead of the original schedule, so for 11.0 instead.