Live data from Hacker News

Introducing paid subscriptions on GitLab.com

about.gitlab.com

61–70 of 81 posts

Re: Introducing paid subscriptions on GitLab.com

#61
post #58

Earlier quoted context omitted.

That are a lot of issues, I sorry that you've had all those problems with GitHost.io. GitHost.io is a service we've offered because GitLab.com was not usable for everyone. One of the problems was the latency of GitLab.com. We're making good progress in fixing that. Are there other things that keep you on GitHost.io? We've heard that people want LDAP sync and we're planning to bring this to GitLab.com. Is there anythi…

Not to be snarky but our instance is still non-responsive.

Sorry about that. We'll have a support engineer reach out now and I'll work with our VP of Eng to look into our SLA for all GitHost customers.

Re: Introducing paid subscriptions on GitLab.com

#62

Earlier quoted context omitted.

Super. That's a pretty quick turn around :)

That's live now, thanks for your help. https://about.gitlab.com/gitlab-com/

You're more than welcome and I'm super impressed with the speed with which you take feedback like this and put it to work.

Re: Introducing paid subscriptions on GitLab.com

#63
post #54

Earlier quoted context omitted.

There is a difference between having paying customers and being a profitable business. Now, you have access to the gitlab books and I don't but from where I'm sitting the more revenue streams you have the better I feel (because I really like gitlab...), on the off chance that you weren't profitable yet.

Not always. Often a revenue stream costs more time (money) than you get from it. Note that the above is tricky. There are revenue streams that lose money by the books, but are worth having because they help something else. An example is a store sells milk at (or below) cost because people come for the cheap milk and buy lots of other things.

Yes, there is probably a contrived counter example for every action a company does that allows you to construe that action as a net negative. But on the whole companies are quite smart at allocating their resources, especially scrappy start-ups and given that bit of data you can make the (safe) assumption that they thought this through to make sure that it would not be a negative. For instance, by first asking their customers whether or not they would pay for such a product.

Re: Introducing paid subscriptions on GitLab.com

#65
post #58

Earlier quoted context omitted.

Tickets from the last year excluding application bugs, that resulted in downtime. I did not get any notification of outages on these. Everything has been resolved and I am very happy with the product when it is working. I get that some of these are due to companies you rely on for your infrastructure. #26561 Server Not Responding (No reponse for over a day) #24895 500 on Application Settings (17 hour for response 24…

That are a lot of issues, I sorry that you've had all those problems with GitHost.io. GitHost.io is a service we've offered because GitLab.com was not usable for everyone. One of the problems was the latency of GitLab.com. We're making good progress in fixing that. Are there other things that keep you on GitHost.io? We've heard that people want LDAP sync and we're planning to bring this to GitLab.com. Is there anythi…

Hi. An off topic.

In page https://about.gitlab.com/products/#comparison it says "Community and support forums only" which is applicable only to "Community Edition". It may better be titled as "Community and support forums" and show the tick mark below every Edition. This could of course save you some time (and money).

Re: Introducing paid subscriptions on GitLab.com

#66
Legal at my current and I think any company I have worked at would never approve use because of the terms of service. Issues include but may not be limited to unrestricted use of name and logo for promotional purposes, changes to the terms including material ones are without notice or any time period before they take effect, and binding arbitration in The Netherlands. I would have expected the terms to more closely resemble those of the githost.io service.

Besides the legal issues there is the issue of no availability or performance SLAs. Given Gitlab's performance and availability track record this is a non starter. Especially when combined with the annual billing.

Re: Introducing paid subscriptions on GitLab.com

#67
post #2

Paid subscriptions are a really good reason to start using gitlab because it promises that they'll be around in the long run.

I'd argue this is their own fault for failing to establish a business model and expectation of payment. Once you give things away for free for a long period of time and then begin to charge later the blowback is severe. Howerver, if you set expectations upfront, people are less likely to revolt. Note, I am not one of these people because I appreciate and respect paying companies for products that I use and love. I think this stems from my founder's mentality more than anything though.

Re: Introducing paid subscriptions on GitLab.com

#69
post #2

Paid subscriptions are a really good reason to start using gitlab because it promises that they'll be around in the long run.

I'd argue this is their own fault for failing to establish a business model and expectation of payment. Once you give things away for free for a long period of time and then begin to charge later the blowback is severe. Howerver, if you set expectations upfront, people are less likely to revolt. Note, I am not one of these people because I appreciate and respect paying companies for products that I use and love. I th…

They have a paid tier, just not for this part of their service.

Re: Introducing paid subscriptions on GitLab.com

#70
post #64

The only reason I use GitLab is that they allow me to host private repos for free. Otherwise I'd be using another service, one that's more reliable and has actual users... its name begins with GitHu and ends with b

Seems like this will not change though
Post reply on HN