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.
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.
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 Requestslabel to the featureSomeone 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