Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bringing GitLab Pages to the Community Edition

about.gitlab.com

Post reply on HN
Print view View original

11–20 of 29 posts

Re: Bringing GitLab Pages to the Community Edition

#11

Post by mcintyre1994 »

sytse wrote: post #8
jobvandervoort wrote: post #7

Earlier quoted context omitted.

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! [0]: https://plus.google.com/u/1/115261498097261634859/…

Cool! So the timing was a coincidence. Also see our internal chat log with timestamps https://gitlab.com/snippets/34152

This is pretty awesome transparency, and it's cool to see how you came to changing your mind instead of "post the same answer phrased differently" :)

Re: Bringing GitLab Pages to the Community Edition

#12

Post by impappl »

sytse wrote: post #4
mc42 wrote: post #2

This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...

Thanks for your kind words! 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 ab…

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.

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.

Re: Bringing GitLab Pages to the Community Edition

#13

Post by impappl »

mc42 wrote: post #2

This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...

The GitHub limitation wasn't new:

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 ;)

Re: Bringing GitLab Pages to the Community Edition

#14

Post by sytse »

impappl wrote: post #12
sytse wrote: post #4

Earlier quoted context omitted.

Thanks for your kind words! 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 ab…

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. 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.

Yep, but we only noticed it on Dec 21.

Re: Bringing GitLab Pages to the Community Edition

#15

Post by sytse »

impappl wrote: post #13
mc42 wrote: post #2

This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...

The GitHub limitation wasn't new: 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 ;)

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).

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

Re: Bringing GitLab Pages to the Community Edition

#16

Post by drewcrawford »

sytse wrote: post #4
mc42 wrote: post #2

This also seems to be a direct result of GitHub's move to limiting GitHub Pages [1] Good work, and keep it up GitLab Team! Lovely product, and well designed. [1] - https://help.github.com/articles/what-is-github-pages/#usage...

Thanks for your kind words! 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 ab…

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.

Re: Bringing GitLab Pages to the Community Edition

#17

Post by impappl »

sytse wrote: post #14
impappl wrote: post #12

Earlier quoted context omitted.

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. 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.

Yep, but we only noticed it on Dec 21.

Great, but that's very different to your original statement of "GitHub Pages was limited about 3 days go".

Re: Bringing GitLab Pages to the Community Edition

#18

Post by dwheeler »

sytse wrote: post #6
dijit wrote: post #3

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#dn…

This is great news!

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!

Re: Bringing GitLab Pages to the Community Edition

#19

Post by sytse »

dwheeler wrote: post #18
sytse wrote: post #6

Earlier quoted context omitted.

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#dn…

This is great news! 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 ea…

Cool, I didn't consider that use case but it makes a lot of sense.

BTW I love the CII Best Practices project and GitLab is proudly wearing the badge on https://gitlab.com/gitlab-org/gitlab-ce/#gitlab

Re: Bringing GitLab Pages to the Community Edition

#20

Post by jobvandervoort »

drewcrawford wrote: post #16
sytse wrote: post #4

Earlier quoted context omitted.

Thanks for your kind words! 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 ab…

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. T…

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.

[0]: https://about.gitlab.com/products/

Post reply on HN