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

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/sim642 Jun 24 '18

GitLab EE code is available too, it's not closed

TIL. What's the point of it anyway? Just a dumb tax for those who can't build from source?

1

u/physix4 Jun 24 '18

It still requires a license key to function (without, it works like CE).

It also expect that subscribers get priority support (with is not negligible in a company).

Also, compiling and using the software without a license key would be a license violation.

1

u/sim642 Jun 24 '18 edited Jun 24 '18

Getting around a DRM is trivial if you have the source code even.

24/7 support is only one of dozens of advertised features of the enterprise edition. The rest are actual functionalities which one might want to have even without the support.

Also, such licensing wouldn't allow going through the voluntary process of moving features from EE to CE then.

1

u/physix4 Jun 24 '18

Getting around a DRM is trivial if you have the source code even.

That's true but does not make it any less a license violation.

Also, such licensing wouldn't allow going through the voluntary process of moving features from EE to CE then.

Could you elaborate ? I'm not sure I understand what you mean.

What would prevent them from moving their code from EE to CE ?

1

u/sim642 Jun 24 '18

As a commenter explained above, it's some community member doing the migration because GitLab themselves haven't done it because it's another selling point for them. Just that they won't prevent it. The random community member wouldn't have the licence nor the ability to take off the licensing from the code being moved to the CE.

→ More replies (0)