Live data from Hacker News

GitLab Isn’t Really Open-Source

akr.am

11–20 of 162 posts

Re: GitLab Isn’t Really Open-Source

#11
post #5

Earlier quoted context omitted.

the enterprise version is not opened source? big deal. gotta support free software somehow and that is a respectable way.

It is open source though: https://gitlab.com/gitlab-org/gitlab-ee/ Open source doesn't mean you can't charge for your work.

Open source doesn't just mean that the source is publicly available, either, though. This definitely isn't an open source license: https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE

Re: GitLab Isn’t Really Open-Source

#12
I cannot disagree more. The open source core is very featureful for its price, it's easy enough to host on premise and UX is very good.

Granted, the paid version has some nice features and there were some problems in the past when people wanted to integrate features found in the paid version to the open core but that's the price of living in current times. Money is still needed to create and maintain something.

Maybe one day when we start living in a Star Trek society.

Re: GitLab Isn’t Really Open-Source

#13
Projects that follow the "open core" model bother me when they gate useful features behind their paid version like Gitlab does. My organization would benefit from the "Rebase merge requests before merge" and "Use fast-forward merges when possible" features quite a bit, and we are an in educational environment with lots of volunteers so using the Enterprise edition isn't viable at all. These features aren't technically difficult to implement, but even if we wrote open source versions of them we'd have to carry our own internal fork of Gitlab since there is no chance upstream would accept them since they've already decided they don't /want/ those features in the "community" edition.

Re: GitLab Isn’t Really Open-Source

#16
post #7
post #2

> Both versions have their sources published on GitLab with the former having an MIT license and the latter a proprietary one which requires a paid subscription with GitLab. So, it is open source? Doesn't this fall under the adage of "free as in free speech, not as in free beer?"

Usually when people speak about open source, they include not only not being able to view the source, but also the possibility to modify, distribute and use it (and modified versions) in the requirements for a license to be labeled an open source license.

Exactly. For instance Windows source code has been "open source" for about 18 years or so via a license anyone can request. This is still not what most people think of when speaking about open source though.

Edit: They call it Shared Source actually: https://www.microsoft.com/en-us/sharedsource/default.aspx

Re: GitLab Isn’t Really Open-Source

#17
post #2

> Both versions have their sources published on GitLab with the former having an MIT license and the latter a proprietary one which requires a paid subscription with GitLab. So, it is open source? Doesn't this fall under the adage of "free as in free speech, not as in free beer?"

Please don't confuse Open Source and Free Software. Open Source' ideals are not "free as in free speech, not as in free beer?". That is something of Free Software. Open Source does not care about the Free Software ideals. Except for that one thing, that source code shall be available.

The Open Source Definition [0] cares about more than just "that source code shall be available". Among other things, it says "The license must allow modifications and derived works" and "The license must not restrict anyone from making use of the program in a specific field of endeavor".

In fact, the OSD is nearly identical to the Debian Free Software Guidelines [1].

[0] https://opensource.org/osd

[1] https://www.debian.org/social_contract#guidelines

Re: GitLab Isn’t Really Open-Source

#18
post #2

> Both versions have their sources published on GitLab with the former having an MIT license and the latter a proprietary one which requires a paid subscription with GitLab. So, it is open source? Doesn't this fall under the adage of "free as in free speech, not as in free beer?"

Please don't confuse Open Source and Free Software. Open Source' ideals are not "free as in free speech, not as in free beer?". That is something of Free Software. Open Source does not care about the Free Software ideals. Except for that one thing, that source code shall be available.

And I can do what I want with it! :)

Re: GitLab Isn’t Really Open-Source

#19
It seems that most of the discussion has been around GitLab and then Gogs/Gitea. I hope folks also give attention to other, possibly less-discussed code collaboration platforms that have arguably more open development than GitLab here.

For example, I believe Fedora is developed via Pagure, which also importantly supports "remote" pull requests. (https://pagure.io/pagure) (Fedora's instance: https://src.fedoraproject.org/)

There's also Kallithea, but I haven't looked at it much. (https://kallithea-scm.org/)

Re: GitLab Isn’t Really Open-Source

#20
post #7
post #2

> Both versions have their sources published on GitLab with the former having an MIT license and the latter a proprietary one which requires a paid subscription with GitLab. So, it is open source? Doesn't this fall under the adage of "free as in free speech, not as in free beer?"

Usually when people speak about open source, they include not only not being able to view the source, but also the possibility to modify, distribute and use it (and modified versions) in the requirements for a license to be labeled an open source license.

From https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE:

> ...and all such modifications and/or patches may only be used, copied, modified, displayed, distributed, or otherwise exploited with a valid GitLab Enterprise Edition subscription for the correct number of user seats.

You can do all that assuming you have a license for your production users. It's not GNU-style Free Software, sure, but it still feels like Open Source to me.

Post reply on HN