Re:Bringing GitLab Pages to the Community Edition
by jobvandervoort on Saturday December 24, 2016 @04:11PM
(#13251640)
Just to clarify, our pricing [0] is per year. So the cost for 50 users is $1950 a year, $162,50 a month for Enterprise Edition starter.
We have been thinking about a model that would allow us a more smooth ramp from CE to EE, hence the change to EE starter and Premium. However, this doesn't mean certain attractive features might still land in paid tiers.
I'd love to get more feedback on this.
Re:Bringing GitLab Pages to the Community Edition
by drewcrawford on Saturday December 24, 2016 @10:30PM
(#13252739)
Right, but your licensing is per user per year. I add 50 NEW users in a month. Each of them use the product for about 20 minutes, but I believe I would need to license them for an entire year.
Re:Bringing GitLab Pages to the Community Edition
by sytse on Monday December 26, 2016 @09:57AM
(#13258419)
If you disable the accounts of users they no longer count towards your license. So you could consider deactivating accounts that have been inactive for more than a month. Anyway, feel free to get in touch with sales@ our domain to discuss the options.
Re:Bringing GitLab Pages to the Community Edition
by deckar01 on Saturday December 24, 2016 @06:22PM
(#13252068)
It sounds like your issues should be hosted on gitlab.com. I bet you can mirror your repos to gitlab.com and just use it for issues.
Edit: GitLab even has a setting that lets you seamlessly integrate an external issue tracker. [0]
[0] https://docs.gitlab.com/ce/integration/external-issue-tracke...
Re:Bringing GitLab Pages to the Community Edition
by drewcrawford on Saturday December 24, 2016 @10:34PM
(#13252750)
The primary reason I moved things off GitHub was to self-host. If I wanted someone else to host it I would probably go back to GitHub.
One thing GL is still missing in its licensing model is a good story for my usecase. I run a GL install that's open to the public so users can report bugs in my software, but there are only 2 real "internal" users. I picked up 50 "users" last month, who just made an issue or two and drove away.
The current model forces me to choose either CE (no paid features for anyone) or EE ($1950/mo). That is what drives some of the disconnect on features like Pages, I'm not going to pay five figures a year for no matter what's in EE.
But if I could pay $300 a year, and get either some paid features, or paid features for some users, that would be pretty easy. Then there is something to do in this situation besides complain that everything isn't free, and creates more opportunities to get invested into GitLab.
As long as there's a $25,000 gap between price tiers you will have these cases where people are flamewarring about whether some feature makes it into CE.