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

Choose GitLab for your next open source project

b.agilob.net

Post reply on HN
Print view View original

61–70 of 289 posts

Re: Choose GitLab for your next open source project

#61

Post by sytse »

dudul wrote: post #59
sytse wrote: post #2

GitLab CEO here. Awesome to see this article! Ask me anything.

Great job on GitLab, I really like it and started migrating my projects from GitHub. One thing: I never managed to make GitLab pages work. It may just be me, but I find the existing documentation very confusing, unclear what should be the name of the repo to host the static website, which conventions are used etc. I would appreciate a better tutorial.

I'm sorry to hear you found the exiting documentation for pages http://doc.gitlab.com/ee/pages/README.html confusing.

We are planning to write a blog post about it with a walkthough https://gitlab.com/gitlab-com/blog-posts/issues/39

Re: Choose GitLab for your next open source project

#62

Post by dudul »

sytse wrote: post #61
dudul wrote: post #59

Earlier quoted context omitted.

Great job on GitLab, I really like it and started migrating my projects from GitHub. One thing: I never managed to make GitLab pages work. It may just be me, but I find the existing documentation very confusing, unclear what should be the name of the repo to host the static website, which conventions are used etc. I would appreciate a better tutorial.

I'm sorry to hear you found the exiting documentation for pages http://doc.gitlab.com/ee/pages/README.html confusing. We are planning to write a blog post about it with a walkthough https://gitlab.com/gitlab-com/blog-posts/issues/39

Awesome, thanks for the fast reply :)

Re: Choose GitLab for your next open source project

#63

Post by dineshp2 »

I was wondering what would be the implications of publishing gitlab enterprise edition with an MIT license and make it easy to fork without subscriptions (basically like the community edition).

From what I understand, the real value that you are selling with an enterprise edition is the support, dedicated staff, monitoring services and training.

Re: Choose GitLab for your next open source project

#64

Post by sytse »

samuelantonioli wrote: post #55
sytse wrote: post #2

GitLab CEO here. Awesome to see this article! Ask me anything.

Thanks for building Gitlab! I'm from Germany and worked at Fraunhofer where Gitlab was used extensively for in-house dev. The first thing I did after joining a small startup was to install gitlab using docker - it is literally faster than setting up a new github account. I also use gitlab's nginx configuration combined with cipherli.st ciphers as a template because it uses best practices. Only one question: We want t…

We don't have a Django specific example. Our general quickstart is in http://doc.gitlab.com/ce/ci/quick_start/README.html and an example for PHP is given in http://doc.gitlab.com/ce/ci/languages/php.html

The file we use to test GitLab itself (a Rails app) can be found on https://gitlab.com/gitlab-org/gitlab-ce/blob/master/.gitlab-...

With the rest of the community we're working on more tutorials, I heard one about iOS projects was pretty close https://gitlab.com/gitlab-com/blog-posts/issues/29

I've create an issue to improve the discoverability of the CI examples https://gitlab.com/gitlab-org/gitlab-ce/issues/13410

Re: Choose GitLab for your next open source project

#65

Post by threatofrain »

Github serves two major purposes: (1) one is to be a git repository, and (2) another purpose is to be the central meeting ground for discovery and community participation. GitLab can serve for the purpose of being a git repository.

The problem is that the more competition we have for (2), the less functional any of the competitors are in serving (2).

Given that when Github goes down, a lot of tools and development workflows also go down, I can understand there being a backup repository. But that's not the same as serving purpose (2), that's just redundancy for (1).

The same problem exists for Facebook. The more Facebooks there are, the less functional any Facebook is.

Re: Choose GitLab for your next open source project

#66

Post by generic_user »

sytse wrote: post #2

GitLab CEO here. Awesome to see this article! Ask me anything.

I would like to know that GitLab will not support Socio-Political entry-ism by instituting a so called 'Code of conduct'.

Codes of Conduct are a form of Socio-Political entry-ism by which third party activists try to interject a vaguely defined set of Behavioral, Ideological and Speech codes which participating individuals must accept in order to participate.

Once Instituted activists can try and use these 'Codes' as a pretext to attack there perceived political and social enemies in the project. Attempt to expel developers can spread across all social media, email, and any other information that can be dug up.

Attempts to redefine project goals and redirect resources away from there original purpose towards social and political objectives set by the entrants are also attempted. Generally turning open productive software communities into unproductive, divisive, monoculture, that serve as ideological vehicles.

It is important that FLOSS software development is politically and socially neutral. Open to anyone who wants to contribute and learn and help improve the code. I hope that GitLab will endorse political and ideological neutrality which opens the door for everyone to participate by keeping Codes of Conduct out of your terms of service.

Re: Choose GitLab for your next open source project

#67

Post by zanny »

atulm wrote: post #33
sethherr wrote: post #29

See, here's the thing: I don't want free private repos to exist. What GitHub has done is incentive making things open source, and that's immeasurably valuable.

I'm not so sure I agree with that conclusion, seems like a causation/correlation issue. Also, AFAIK public repository != open source.

A more reasonable conclusion is that developers not involved in open source use github free repos, people find their stuff, start talking to them, they start collaborating, and then they become open source projects.

On gitlab when most stuff is default-private it leads to a lot of potential collaboration being lost, regardless of license.

Re: Choose GitLab for your next open source project

#68

Post by sytse »

dineshp2 wrote: post #63

I was wondering what would be the implications of publishing gitlab enterprise edition with an MIT license and make it easy to fork without subscriptions (basically like the community edition). From what I understand, the real value that you are selling with an enterprise edition is the support, dedicated staff, monitoring services and training.

We tried licensing the enterprise edition under an open source license but asking people nicely to not distribute it. People didn't distribute it but our customer where very confused about this so we changed the license.

The current license https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE is proprietary but it does allow people to see the code, modify it and contribute patches https://gitlab.com/gitlab-org/gitlab-ee/merge_requests

Part of the value of a subscription is our support and training, but the unique features of EE https://about.gitlab.com/features/#compare also are important.

Re: Choose GitLab for your next open source project

#69

Post by semerda »

ramigb wrote: post #57

I've been using Bitbucket for 3 years now and i absolutely love the fact that you can create private repos and have many tools available for free, highly recommended.

Ditto! Bitbucket has served me well for so many years esp with their ondemand integrations. I really don't see why I should move to any other gitxxx. Moving tools is also a pain point so best to choose wisely.

Re: Choose GitLab for your next open source project

#70

Post by dineshp2 »

sytse wrote: post #68
dineshp2 wrote: post #63

I was wondering what would be the implications of publishing gitlab enterprise edition with an MIT license and make it easy to fork without subscriptions (basically like the community edition). From what I understand, the real value that you are selling with an enterprise edition is the support, dedicated staff, monitoring services and training.

We tried licensing the enterprise edition under an open source license but asking people nicely to not distribute it. People didn't distribute it but our customer where very confused about this so we changed the license. The current license https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE is proprietary but it does allow people to see the code, modify it and contribute patches https://gitlab.com/gitlab-org…

If you don't mind me asking, what was confusing to the customer?

Again, I don't mean to be rude, just curiosity, how would you react if people forked the community edition and implemented some of the enterprise edition features and released it under the MIT expat licence?

Post reply on HN