Looking at our internal chat logs it seems that the announcement got us thinking about pages again. But the decision to open source it was based on what kind of people used it (more small organizations than we thought, fewer large organizations than we thought).
I've asked Job to comment too.
BTW We're not sure if we'll limit GitLab.com Pages at some point, see "GitLab Pages with very high traffic (currently unlimited even in the free plan)" from https://about.gitlab.com/gitlab-com/#free-forever Of course you now always have the option to host your own.
The link you yourself share features many comments, including by GitHub themselves, that this wasn't a new limit. They publicised the change earlier in the year.
Hi sytes. Thanks so much for this. I was active on the thread trying to get it added to CE, and it makes a big difference.
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.
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.
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.
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.
I cannot speak about the licensing, but I can suggest you an alternative: host CE for public access and mirror your repositories there, and have your EE version for internal use only.
The timing is coincidental, at least from my side.
We keep track of all mentions of GitLab on sources such as HN, but also Google+. There I was pointed to this comment [0]. This triggered me to look into the existing issue again [1] and reevaluate.
The data showed that there was no good reason for us to keep GitLab Pages in EE, so it made sense to move it to CE!
As said in https://news.ycombinator.com/item?id=13250414 the decision to open source it was based on what kind of people used it (more small organizations than we thought, fewer large organizations than we thought).
I was looking for this feature a couple of days ago and saw it was in the EE. Which sucked for me and my tiny community- so I'm super pleased to hear this.
One of the things I'm not sure about though, is how does gitlab handle the domain per user? Do I delegate DNS to the gitlab instance itself or something?
Glad to hear we made the right decision. We open sourced it because we learned that small organizations were interested and your comment is another indication of that.
Regarding your question. I assume you're talking about a self hosted instance that offers a FQDN (not domain) in the form of username.yourgitlabhostname.com For documentation about this please see https://docs.gitlab.com/ee/pages/administration.html#dns-con...
BTW For instructions how to use your own domain see https://docs.gitlab.com/ee/pages/README.html "As a last step, you need to configure your DNS and add a CNAME pointing to your user/group page. Click on the Details button of a domain for further instructions."
I lead the "CII Best Practices Badge" project for OSS projects - if you have an OSS project, and you meet certain requirements, you can get a badge. One criterion is that "The project sites (website, repository, and download URLs) MUST support HTTPS using TLS.":
https://github.com/linuxfoundation/cii-best-practices-badge/...
I think making GitLab pages part of the community edition will make it easier to meet this criterion. Congrats, and thanks!
Participate in an Interview on Experience with Different Git Tools
My name is Angela and I do researches on the user experience for different Git tools on the market. I’m kicking off a round of discussions with people who use Git tools. Ideally, I’d like to talk to people that sit on a team of 3 or more. If this is you, I would love to talk to you about your experience with <using> Git tools, or just some of the pain points that are keeping you up at night when doing your jobs.
I’ll just need 30 mins of your time, and as a token of my thanks to those that participate, I’d like to offer a US$50 Amazon gift voucher.
If you’re interested, just shoot me an email with your availability over the next few weeks and we can set up a time to chat for 30 minutes. Please also include your timezone so we can schedule a suitable time (as I’m located in San Francisco). Hope to talk to you soon!
We're thankful that the conversation was data driven and everyone assumed best intentions from each other. In the last few days we released 8.15 with auto deploy and web terminal https://about.gitlab.com/2016/12/22/gitlab-8-15-released/ and the company achieved its monthly, quarterly, and yearly sales goal. I can't think of a better way to celebrate and be amazed at what we did together in 2016.
Participate in an Interview on Experience with Different Git Tools
My name is Angela and I do researches on the user experience for different Git tools on the market. I’m kicking off a round of discussions with people who use Git tools. Ideally, I’d like to talk to people that sit on a team of 3 or more. If this is you, I would love to talk to you about your experience with <using> Git tools, or just some of the pain points that are keeping you up at night when doing your jobs.
I’ll just need 30 mins of your time, and as a token of my thanks to those that participate, I’d like to offer a US$50 Amazon gift voucher.
If you’re interested, just shoot me an email with your availability over the next few weeks and we can set up a time to chat for 30 minutes. Please also include your timezone so we can schedule a suitable time (as I’m located in San Francisco). Hope to talk to you soon!
28 comments
[ 3.1 ms ] story [ 83.6 ms ] threadGood work, and keep it up GitLab Team! Lovely product, and well designed.
[1] - https://help.github.com/articles/what-is-github-pages/#usage...
EDIT: Job has commented in https://news.ycombinator.com/item?id=13250453
The announcement from GitHub might have triggered us. GitHub Pages was limited about 3 days go https://news.ycombinator.com/item?id=13227863
Job asked for votes 3 days ago https://gitlab.com/gitlab-org/gitlab-ce/issues/14605#note_20...
Looking at our internal chat logs it seems that the announcement got us thinking about pages again. But the decision to open source it was based on what kind of people used it (more small organizations than we thought, fewer large organizations than we thought).
I've asked Job to comment too.
BTW We're not sure if we'll limit GitLab.com Pages at some point, see "GitLab Pages with very high traffic (currently unlimited even in the free plan)" from https://about.gitlab.com/gitlab-com/#free-forever Of course you now always have the option to host your own.
As the product manager pointed out https://news.ycombinator.com/item?id=13229461 and as a Quora answer from June also reveals https://www.quora.com/What-are-bandwidth-and-traffic-limits-... the GitHub pages limits were public since at least June.
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.
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.
[0]: https://about.gitlab.com/products/
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...
Github limits are for big high traffic pages, and you open the door for smaller projects/orgs.
Obviously a good thing. Just odd the the GH decision aimed at a different segment of the market provoked this.
In any case, kudos.
We keep track of all mentions of GitLab on sources such as HN, but also Google+. There I was pointed to this comment [0]. This triggered me to look into the existing issue again [1] and reevaluate.
The data showed that there was no good reason for us to keep GitLab Pages in EE, so it made sense to move it to CE!
[0]: https://plus.google.com/u/1/115261498097261634859/posts/EWhA...
[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/14605
As the product manager for GitHub Pages pointed out https://news.ycombinator.com/item?id=13229461 and as a Quora answer from June also reveals https://www.quora.com/What-are-bandwidth-and-traffic-limits-...
It will be interesting if GitLab is making product decisions as a result of HM generating fake news, though ;)
We don't do HNDD (Hacker News Driven Development) but I must admit that I was looking forward to the reception of Auto Deploy in HN https://news.ycombinator.com/item?id=13239604
One of the things I'm not sure about though, is how does gitlab handle the domain per user? Do I delegate DNS to the gitlab instance itself or something?
It depends a bit on what you want, but have a look in the documentation for details I couldn't give you by heart [0].
[0]: https://docs.gitlab.com/ee/pages/administration.html#setting...
Regarding your question. I assume you're talking about a self hosted instance that offers a FQDN (not domain) in the form of username.yourgitlabhostname.com For documentation about this please see https://docs.gitlab.com/ee/pages/administration.html#dns-con...
BTW For instructions how to use your own domain see https://docs.gitlab.com/ee/pages/README.html "As a last step, you need to configure your DNS and add a CNAME pointing to your user/group page. Click on the Details button of a domain for further instructions."
I lead the "CII Best Practices Badge" project for OSS projects - if you have an OSS project, and you meet certain requirements, you can get a badge. One criterion is that "The project sites (website, repository, and download URLs) MUST support HTTPS using TLS.": https://github.com/linuxfoundation/cii-best-practices-badge/...
I think making GitLab pages part of the community edition will make it easier to meet this criterion. Congrats, and thanks!
BTW I love the CII Best Practices project and GitLab is proudly wearing the badge on https://gitlab.com/gitlab-org/gitlab-ce/#gitlab
My name is Angela and I do researches on the user experience for different Git tools on the market. I’m kicking off a round of discussions with people who use Git tools. Ideally, I’d like to talk to people that sit on a team of 3 or more. If this is you, I would love to talk to you about your experience with <using> Git tools, or just some of the pain points that are keeping you up at night when doing your jobs.
I’ll just need 30 mins of your time, and as a token of my thanks to those that participate, I’d like to offer a US$50 Amazon gift voucher.
If you’re interested, just shoot me an email with your availability over the next few weeks and we can set up a time to chat for 30 minutes. Please also include your timezone so we can schedule a suitable time (as I’m located in San Francisco). Hope to talk to you soon!
Cheers, Angela Guo 378496625@qq.com
We're thankful that the conversation was data driven and everyone assumed best intentions from each other. In the last few days we released 8.15 with auto deploy and web terminal https://about.gitlab.com/2016/12/22/gitlab-8-15-released/ and the company achieved its monthly, quarterly, and yearly sales goal. I can't think of a better way to celebrate and be amazed at what we did together in 2016.
My name is Angela and I do researches on the user experience for different Git tools on the market. I’m kicking off a round of discussions with people who use Git tools. Ideally, I’d like to talk to people that sit on a team of 3 or more. If this is you, I would love to talk to you about your experience with <using> Git tools, or just some of the pain points that are keeping you up at night when doing your jobs.
I’ll just need 30 mins of your time, and as a token of my thanks to those that participate, I’d like to offer a US$50 Amazon gift voucher.
If you’re interested, just shoot me an email with your availability over the next few weeks and we can set up a time to chat for 30 minutes. Please also include your timezone so we can schedule a suitable time (as I’m located in San Francisco). Hope to talk to you soon!
Cheers, Angela Guo 378496625@qq.com