Hacker News Reader

It does feel like Gitlab strategically keeps certain things out of the OSS product, like limiting the issues to two states.

View on HN

We use buyer based tiering to decide which tier a feature will reside in.

https://about.gitlab.com/handbook/ceo/pricing/#buyer-based-t...

> Free is for a single developer, with the purchasing decision led by that same person

> Premium is for team (s) usage, with the purchasing decision led by one or more Directors

Doesn't this conflict with the stewardship promise that "The open source codebase will have all the features that are essential to running a large 'forge' with public and private repositories"?

When the tiering of a feature is being evaluated, the stewardship promise (https://about.gitlab.com/company/stewardship/#promises) will override the guidance on our pricing page (https://about.gitlab.com/company/pricing/#buyer-based-tierin...).

Thanks again for the question.

Edit - I've created an MR to document this on our pricing model page: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...

Thanks for the question. I shared it with @sytse and he's putting some thought into it.

Reply on news.ycombinator.com