3 ms·

GitLab CE is not crippled in any way, it is used every single day by hundreds of thousands of companies and millions upon millions of developers. It is and has

by DouweM 11y ago

GitLab CE is not crippled in any way, it is used every single day by hundreds of thousands of companies and millions upon millions of developers. It is and has always been our (GitLab, the company) main focus, we only decide to make new features EE-only when we think that they are mostly interesting to companies with 100+ employees. Besides the company's efforts, contributions from the 1000+ community contributors always go into CE, unless the contributor submits it to the EE repository specifically. As evidence, just look at our Direction page: https://about.gitlab.com/direction/ https://about.gitlab.com/direction/, or compare the CE and EE changelogs: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELO... vs https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CHANGELOG-EE https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CHANGELO.... Note that our free, hosted GitLab.com runs EE, which means that EE features like GitLab Pages ("Hosting static pages straight from GitLab") are available to everyone.

drewcrawford 11y ago
Just yesterday I ended up implementing my own mirroring of GitHub repositories. GitLab supports this in EE (new in 8.3), but not CE. That's not a feature that only large enterprises use–I run an open source GitHub organization and wanted to use GitLab as CI. It works! But I needed to reimplement an EE feature to do it. To be clear, I don't think there is anything sinister about keeping features behind a paid firewall. That is how software developers have paid their rent for decades. I'm just saying that the EE features are not all "mostly interesting to companies with 100+ employees." Several of them are things I needed as a single open-source developer. I've debated about buying EE to fill in the gaps, but you sell licenses in packs of 10, and I only need 2 :-)
- DouweM 11y ago
  > I run an open source GitHub organization and wanted to use GitLab as CI. It works! But I needed to reimplement an EE feature to do it. Is there a reason why you didn't use GitLab.com, which runs EE and thus has Repository Mirroring? > I'm just saying that the EE features are not all "mostly interesting to companies with 100+ employees." Several of them are things I needed as a single open-source developer. Fair enough, I'm not saying our judgment of what is and what isn't interesting to smaller/single-person teams is perfect. If the general feedback of the community is that a certain piece of functionality belongs in CE rather than EE, we will consider bringing it to CE. We have done this in the past.
  - drewcrawford 11y ago
    > Is there a reason why you didn't use GitLab.com, which runs EE and thus has Repository Mirroring? 1. My hosting is way more reliable than yours :-) 2. I need to host the CI runners myself anyway, because you don't have the right config 3. I already have a private GitLab install, so it's no extra trouble 4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly 5. I prefer to have a commercial relationship with important tools. You seem like nice people, let's see what happens when you get acquired. As long as you can't be bothered to sell to 2-person teams, I'll just run CE and have my commercial relationship with AWS instead.
    - DouweM 11y ago
      > 1. My hosting is way more reliable than yours :-) You've got me there :) I'm sure your aware of our intention to greatly improve GitLab.com reliability and performance in Q1 2016: https://gitlab.com/gitlab-com/operations/issues https://gitlab.com/gitlab-com/operations/issues > 4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly Heh, care to share? :) Maybe we can take some pointers from your implementation. How does your repository mirroring know that the upstream repo was updated? Do you use webhooks on GitHub? That would actually be pretty easy to implement, an `update_mirror` GitLab API endpoint that GitHub could call to, hmm... > 5. I prefer to have a commercial relationship with important tools. You seem like nice people, let's see what happens when you get acquired. What are you afraid of? > As long as you can't be bothered to sell to 2-person teams, I'll just run CE and have my commercial relationship with AWS instead. Fair enough!
      - drewcrawford 11y ago
        > Do you use webhooks on GitHub? That would actually be pretty easy to implement, Bingo. Full implementation, in Bash: http://faq.sealedabstract.com/gitlab_mirror/ http://faq.sealedabstract.com/gitlab_mirror/ > What are you afraid of? Mostly, that you'll get bought by the likes of Oracle. In spite of my quibbles about CE features, I think you're doing a (mostly) fine job of CE right now. But your acquirer will see CE as a cost center (there's no revenue) and will want to "streamline" by focusing on enterprise (where your balance sheet is). GitLab.com will also look like a cost center, and will either shut down, turn into a datamining opportunity, or go through the bad PR of no longer being free. I fully anticipate, in 5-10 years time, that I will be running a CE fork to get out from under your acquirer, just like StarOffice, MySQL, Hudson, etc. Contrast with GitHub, who makes a silly amount of money from people like me. Their acquirer would be mad to screw up a winning formula. The good news is, GitLab is such a good product that I still hugely prefer it even after "pricing in" the risk (cough, certainty) that my days are numbered. It is an amazing tool, it really shows that you care about it. For now.

by DouweM 11y ago

drewcrawford 11y ago

Just yesterday I ended up implementing my own mirroring of GitHub repositories. GitLab supports this in EE (new in 8.3), but not CE. That's not a feature that only large enterprises use–I run an open source GitHub organization and wanted to use GitLab as CI. It works! But I needed to reimplement an EE feature to do it. To be clear, I don't think there is anything sinister about keeping features behind a paid firewall. That is how software developers have paid their rent for decades. I'm just saying that the EE features are not all "mostly interesting to companies with 100+ employees." Several of them are things I needed as a single open-source developer. I've debated about buying EE to fill in the gaps, but you sell licenses in packs of 10, and I only need 2 :-)

DouweM 11y ago
> I run an open source GitHub organization and wanted to use GitLab as CI. It works! But I needed to reimplement an EE feature to do it. Is there a reason why you didn't use GitLab.com, which runs EE and thus has Repository Mirroring? > I'm just saying that the EE features are not all "mostly interesting to companies with 100+ employees." Several of them are things I needed as a single open-source developer. Fair enough, I'm not saying our judgment of what is and what isn't interesting to smaller/single-person teams is perfect. If the general feedback of the community is that a certain piece of functionality belongs in CE rather than EE, we will consider bringing it to CE. We have done this in the past.
- drewcrawford 11y ago
  > Is there a reason why you didn't use GitLab.com, which runs EE and thus has Repository Mirroring? 1. My hosting is way more reliable than yours :-) 2. I need to host the CI runners myself anyway, because you don't have the right config 3. I already have a private GitLab install, so it's no extra trouble 4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly 5. I prefer to have a commercial relationship with important tools. You seem like nice people, let's see what happens when you get acquired. As long as you can't be bothered to sell to 2-person teams, I'll just run CE and have my commercial relationship with AWS instead.
  - DouweM 11y ago
    > 1. My hosting is way more reliable than yours :-) You've got me there :) I'm sure your aware of our intention to greatly improve GitLab.com reliability and performance in Q1 2016: https://gitlab.com/gitlab-com/operations/issues https://gitlab.com/gitlab-com/operations/issues > 4. My repository mirroring is quite a lot better than yours, as it's instant, not hourly Heh, care to share? :) Maybe we can take some pointers from your implementation. How does your repository mirroring know that the upstream repo was updated? Do you use webhooks on GitHub? That would actually be pretty easy to implement, an `update_mirror` GitLab API endpoint that GitHub could call to, hmm... > 5. I prefer to have a commercial relationship with important tools. You seem like nice people, let's see what happens when you get acquired. What are you afraid of? > As long as you can't be bothered to sell to 2-person teams, I'll just run CE and have my commercial relationship with AWS instead. Fair enough!
    - drewcrawford 11y ago
      > Do you use webhooks on GitHub? That would actually be pretty easy to implement, Bingo. Full implementation, in Bash: http://faq.sealedabstract.com/gitlab_mirror/ http://faq.sealedabstract.com/gitlab_mirror/ > What are you afraid of? Mostly, that you'll get bought by the likes of Oracle. In spite of my quibbles about CE features, I think you're doing a (mostly) fine job of CE right now. But your acquirer will see CE as a cost center (there's no revenue) and will want to "streamline" by focusing on enterprise (where your balance sheet is). GitLab.com will also look like a cost center, and will either shut down, turn into a datamining opportunity, or go through the bad PR of no longer being free. I fully anticipate, in 5-10 years time, that I will be running a CE fork to get out from under your acquirer, just like StarOffice, MySQL, Hudson, etc. Contrast with GitHub, who makes a silly amount of money from people like me. Their acquirer would be mad to screw up a winning formula. The good news is, GitLab is such a good product that I still hugely prefer it even after "pricing in" the risk (cough, certainty) that my days are numbered. It is an amazing tool, it really shows that you care about it. For now.