It does get slightly more complicated since those are project level features. I don't know how many users exist that don't have Developer access on at least one repository.
Enforcement of that seems less than ideal. You would have to have GitLab check the number of Reporters and Developers any time someone gets Developer access to a repo. Which means that the repo owner gets the error when you run out of licenses, which is less than ideal. As opposed to a user limit, where presumably whatever team owns Gitlab gets the error when they add the user.
Re:GitLab 13.0
by harrisonjackson on Saturday May 23, 2020 @08:02PM
(#23287801)
110 users account is going to be one of the enterprise-y/gold/ultimate tier plans. They're going to get the enterprise-y price and subsidize the free and less-expensive tiers.
I would guess that most startups or small devshops using gitlab are going to have 5-6 devs to a maybe 1 reporter user.
Edit - I'm not disagreeing with you that a reporter user needs less features and in theory has a lower cost to gitlab. I think the target customer for the gold/ultimate tier that has reporter users won't blink at paying for it.
There are a lot of companies with 10 developers but 100 reporters. Why should those two groups of people cost the same? The interaction is easy - GitLab already works on the permissions with the different user types. And calculating cost is just as easy - how many reporters vs how many other types.