Almost Everything We Do Will Be Open • Hacker News Board

Re: Almost Everything We Do Will Be Open

#141

Post by sytse » Fri, Aug 07, 2015, 7:23 PM UTC

superuser2 wrote: post #94

avinassh wrote: post #92

How does the licensing works? Can anyone explain me? [0] > This software and associated documentation files (the "Software") can only be used with a valid GitLab subscription for the correct number of users. You are free to modify this Software and publish patches. It is forbidden to copy, merge, publish, distribute, sublicense, and/or sell copies of the Software. Isn't the third line contradicting with the fourth or…

A patch - literally a file generated by "diff" - only incidentally contains the original code, mostly your new functions and modifications. So you can't distrbute a patched version of the software, only the patch itself.

Exactly, that is how I meant that.

Re: Almost Everything We Do Will Be Open

#142

Post by sytse » Fri, Aug 07, 2015, 7:24 PM UTC

audessuscest wrote: post #56

ojanik wrote: post #48

Coincidentally, I just installed GitLab to try it out for our small team to replace BitBucket + Jira. And while its more than capable filling Bitbucket shoes the issues subsystem is probably worse than github's and nowhere near flexible as jira. Most notably: Missing more sophisticated workflows. Search for issues using multiple labels. Search for issues across multiple projects. We would also love to be able to do s…

I agree, we're using gitlab too and the only problem is the lack of ticket system feature (due date/alert reminder, multiple people assignment, advanced filters, simple markdown text editor for client, time tracking, edit default label for all project,...) otherwise we hightly recommend it.

Thanks, we're looking some of these but we want to keep it light and easy to use at the same time. Please be aware that some scrum tools also integrate with GitLab https://about.gitlab.com/applications/#scrum-boards

Re: Almost Everything We Do Will Be Open

#143

Post by sytse » Fri, Aug 07, 2015, 7:25 PM UTC

mesozoic wrote: post #80

Add a search that isn't terrible and you'll solve most every complaint I have and hear from others about Gitlab.

What search are you talking about, in the issues or in the code?

Re: Almost Everything We Do Will Be Open

#144

Post by sytse » Fri, Aug 07, 2015, 7:26 PM UTC

ausjke wrote: post #68

jobvandervoort wrote: post #58

Earlier quoted context omitted.

What makes you feel GitLab is too heavy for small teams? In terms of load, it can run on a Raspberry Pi.

CPU 1 core works for under 100 users but the responsiveness might suffer 2 cores is the recommended number of cores and supports up to 100 users 4 cores supports about 1,000 users 8 cores supports up to 10,000 users Memory 512MB is too little memory, GitLab will be very slow and you will need 250MB of swap 768MB is the minimal memory size but we advise against this 1GB supports up to 100 users (with individual reposi…

It runs on a RPi2 https://about.gitlab.com/2015/04/21/gitlab-on-raspberry-pi-2...

Re: Almost Everything We Do Will Be Open

#145

Post by sytse » Fri, Aug 07, 2015, 7:28 PM UTC

scrollaway wrote: post #82

sytse wrote: post #13

Earlier quoted context omitted.

The article is about the issues that will almost all be open. The complete quote you refer to is is "In fact, even our proprietary version of GitLab, GitLab Enterprise Edition, has a publicly viewable source code.". Can we be any more clear it is proprietary? We think it is notable that even the source code and issues of out proprietary edition are publicly viewable.

Your wording is fine. Parent is being far too cynical.

Thanks, I don't want to be seen as openwashing. Open core is a tricky thing and we want to find a good balance.

Re: Almost Everything We Do Will Be Open

#146

Post by sytse » Fri, Aug 07, 2015, 7:31 PM UTC

nadams wrote: post #136

antsar wrote: post #125

Earlier quoted context omitted.

In what way does it seem contradictory? It seems to allow one to write and publish patches , while disallowing the redistribution/resale of the original code .

Distributing a patch would require distributing parts of the original code (the patch file will include lines of original and changed code) - which the latter is not allowed per the license. I'm not saying that gitlab would go after you for just distributing a patch - but if anyone gobbled up gitlab cough Oracle cough I'm sure they would summon a swarm of lawyers at your doorstep.

If you have any suggestions how to word this better I'm open to them. We did have a lawyer look at this. It is like sampling, you can use a bit but you can't use it all.

Re: Almost Everything We Do Will Be Open

#147

Post by sytse » Fri, Aug 07, 2015, 7:32 PM UTC

nanny wrote: post #60

vezzy-fnord wrote: post #28

Earlier quoted context omitted.

They are: http://opensource.org/osd The only difference is their argument. Free software uses ethical arguments, open source denies ethics altogether and uses consequentialist arguments related to business value and technical superiority (which are becoming increasingly criticized).

I disagree. Would it be accurate to call The GitLab Enterprise Edition "open source"? If not, what would you call it?

We call it proprietary to prevent any confusion.

Re: Almost Everything We Do Will Be Open

#148

Post by sytse » Fri, Aug 07, 2015, 7:33 PM UTC

KingMob wrote: post #40

nightcracker wrote: post #23

Earlier quoted context omitted.

Well, you are. Let me read to you the definition of Open Source: > Open source software is software that can be freely used, changed, and shared (in modified or unmodified form) by anyone.

But that's the enterprise license, not the community license. When they say "In fact, even our proprietary version of GitLab, GitLab Enterprise Edition, has a publicly viewable source code", I don't think they're implying it's open source.

Indeed, GitLab EE is proprietary, GitLab CE is open source (MIT Expat)

Re: Almost Everything We Do Will Be Open

#149

Post by sytse » Fri, Aug 07, 2015, 7:33 PM UTC

merb wrote: post #22

jobvandervoort wrote: post #10

Earlier quoted context omitted.

It is, we don't intent to be vague about this. I hadn't heard of the term openwashing, but I understand the criticism. See also our license for our proprietary GitLab Enterprise Edition: https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE And the license for our open source GitLab Community Edition (MIT Expat): https://gitlab.com/gitlab-org/gitlab-ce/blob/master/LICENSE

Isn't the copy a little bit vague? I mean if I want to help I need to copy it?

If you want to contribute to EE I think you need a subscription. Otherwise you shouldn't run it.

Re: Almost Everything We Do Will Be Open

#150

Post by cname » Fri, Aug 07, 2015, 8:14 PM UTC

skyraider wrote: post #72

GitLab Enterprise user here. GitLab's open-source policy is one of the major reasons we chose it (along with self-hosting and fairly modern, built-in continuous integration), but the GitLab community could use some additional design and documentation effort. Things that almost make me want to switch back to GitHub: - GitLab is really hard to look at. All of our devs are having trouble visually locating comments in di…

> Even BitBucket looks better.

Slight tangent: I think Bitbucket looks nicer than GitHub in almost every way.