Hacker News Reader

We considered that but we value having a completely open source version for all projects more. For more information about how we see the difference between CE and EE please see https://about.gitlab.com/about/#stewardship

View on HN

What about having a single product, and charging for a proprietary license + support? This may work better with GPL as many large orgs are allergic to it.

With MIT license, many sites probably just implement the branding changes etc in the CE product on their own.

We want to give large orgs the option to run GitLab without having to pay us. We don't mind having people add features to CE, these are the same people that will send enahancements upstream and make GitLab better for everyone.

Have you ever considered using the AGPLv3 for the Community Edition, rather than the all-permissive MIT license?

I'm pretty sure they take outside contributions for CE, so if that was AGPL3 they wouldn't be able to use it in Gitlab EE, which sounds like shooting themselves in the foot.

They could require a CLA for outside contributions. Many organizations do that.

Reply on news.ycombinator.com