News for hackers. Stuff that matters.
Re:Jepsen: Dgraph 1.0.2 by mrjn on Thursday August 23, 2018 @01:35PM (#17829112)
We changed the references to say liberally licensed. I'll try and write a bigger blog post about the reasoning behind Commons Clause and Dgraph and other companies' adoption of it.
Re:Jepsen: Dgraph 1.0.2 by Sir_Cmpwn on Thursday August 23, 2018 @01:42PM (#17829177)
I think it's disengenuous to say liberally licensed. Liberally licensed might apply to MIT or even Apache alone, but not when you include the Commons Clause. But it's a subjective measure, so you're not making factually incorrect statements even if you are being dishonest.

Your updated statement also says "Dgraph is available under an Apache v2.0 based liberal license", which I think is unfairly using the Apache 2.0 name without clarifying that your license in fact is not open source. The language is still dishonest.

Re:Jepsen: Dgraph 1.0.2 by mrjn on Thursday August 23, 2018 @02:32PM (#17829568)
First, to be clear, we are the authors of this software, so our responsibility is to choose our license terms and clearly communicate them to those who want to use the software. We have done that and we are obviously not trying to mislead anyone. We think our licensing statement is easy to understand. We have not changed the Apache license terms. We have added an additional term (Commons Clause) and clearly stated that we are applying the two together.

If we had changed the Apache license, we would not have referred to it by that name. But given we have not changed the Apache terms, it seems to us more confusing to arbitrarily refer to those terms by a different name.

My take is that Apache + Commons Clause is more liberal than AGPL, something I can expand on in my blog post -- that's clear from our users, who actually appreciated the switch from AGPL to the current license.

Re:Jepsen: Dgraph 1.0.2 by dragonwriter on Thursday August 23, 2018 @03:32PM (#17829982)
> We have not changed the Apache license terms.

Yes, you have.

> We have added an additional term (Commons Clause) and clearly stated that we are applying the two together.

Adding the Commons Clause changes the terms of the Apache license quite substantially, which is obviously the reason you added it.

Re:Jepsen: Dgraph 1.0.2 by openasocket on Thursday August 23, 2018 @02:55PM (#17829715)
The website says "Dgraph is available under an Apache v2.0 based liberal license", and Sir_Cmpwn says it should say "Dgraph is available under an Apache v2.0 + Commons Clause license" to not be misleading. Are you saying you don't want to make that really simple change?
Re:Jepsen: Dgraph 1.0.2 by detaro on Thursday August 23, 2018 @07:14PM (#17831374)
Curious, what did come from your communication with the Apache Foundation after they voiced their concerns about your usage of the label "Apache License"?

https://github.com/dgraph-io/dgraph/issues/2416#issuecomment...

This stuff really sours me on the otherwise fairly reasonable license and its users.

Re:Jepsen: Dgraph 1.0.2 by Sir_Cmpwn on Thursday August 23, 2018 @02:41PM (#17829634)
You are free to license your software as you wish, and I am not questioning your right to. There are three separate issues here.

>our responsibility is to choose our license terms and clearly communicate them to those who want to use the software

You are not doing this. Your website reads "Dgraph is available under an Apache v2.0 based liberal license", which is technically true but also very dishonest. Your software does not use the Apache 2.0 license, and users of it should not expect to enjoy the freedoms granted to them by the Apache 2.0 license.

>We have not changed the Apache license terms

This is not true. The Apache license explicitly grants freedoms which the following

>We have added an additional term

changes. Don't wrangle words into passable lies, you're not talking to idiots. Your wording is misleading and dishonest, which are two qualities you should be trying very hard not to associate with your brand. So far you're not doing well. No one is questioning your right to license the software as you wish. But you are not proud of your choice and are using slimy and dishonest language on your marketing material to hide your shame and trick potential users.

A separate issue is the subjective one, which is whether or not the commons clause is liberal. I think you are being dishonest here. There are widely accepted definitions for "liberal" among the open source community. The main differentiating factor of a liberal license is that it's not viral. Most people informed on this subject can then neatly and objectively file licenses into liberal and restrictive categories, with licenses like MIT, BSD, and Apache in the liberal camp, and the GPL family of licenses in the restrictive camp. However, the distinction has always been subjective, and nothing like the OSD exists. Additionally, the distinction is only ever applied in the comparison of open source licenses, of which yours is not a member. The realm of proprietary licenses masquarading as open source licenses is unexplored territory, and I'm drawing a line: no matter how restrictive a license like AGPL is, a license which is not even open source in the first place is far from liberal.

The third issue is whether or not using the Commons Clause is the right thing for Dgraph to do. In my opinion, it's a slap in the face to everyone who ever used or especially to anyone who ever contributed to Dgraph. In fact, as I was researching dgraph a bit more to see how you approached this issue, it also occurs to me that I can't find any discussion where existing Dgraph contributors were consulted on the matter of relicensing their work, which seems to me that your license change was not only distasteful and harmful to your project, but also illegal. Were all of the contributors consulted and their permission obtained to change the license? I'll certainly be consulting them if not.

Re:Jepsen: Dgraph 1.0.2 by staticassertion on Thursday August 23, 2018 @04:51PM (#17830612)
This is so overdramatic and unfortunate - a company puts code out there, does good work, largely follows OSS, and this topic gets derailed.

They degrade on the 'de facto' definition of OS by saying that others may not sell it.

That's it.

Comments like yours are why I don't interact with open source at all.

Re:Jepsen: Dgraph 1.0.2 by Sir_Cmpwn on Thursday August 23, 2018 @04:56PM (#17830644)
These freedoms are important, and by removing them the whole license is practically undermined. They forgot about the rights of the users and contributors while they were busy thinking about the rights of the maintainers. To quote something I said in a private email:

>The Commons Clause nullifies pretty much any privledge granted by the original license, further rendering it useless. For example, the permission to make and publish changes to the work, or reuse the code elsewhere. Is the Commons Clause viral? If I take a small function from RedisLabs and incorporate it into my project, do my users have to pay RedisLabs to support my project? If RedisLabs decides not to, is my project now illegal to support at all? What if I want to fork the software, does my fork inherit the clause and do the same problems apply? This doesn't sound anything like the "commons" to me. Pretty much all of the rights afforded to users of open source are rendered null and void, and the mention of an open source license in the licensing terms of such software is laughable.

Re:Jepsen: Dgraph 1.0.2 by eropple on Thursday August 23, 2018 @07:21PM (#17831406)
I've had my share of beefs with Sir_Cmpwn but this post is nonsense. You can't "largely" practice an open source model. Either you do or you don't.

Dgraph was interesting to me until they said they wanted to take a vig for me sharing knowledge and practical advice about the software (because that's what consulting, an activity expressly precluded in the dishonestly-named Commons Clause, is). That? That can go straight to hell.

Being a taker of open source (because you certainly "interact with open source") is your right but has absolutely nothing to do with those of us actually expecting those draping themselves in the banner of open source to practice open source principles and to run an open source project as an open source project. That exists between your ears and your ears alone.

Re:Jepsen: Dgraph 1.0.2 by staticassertion on Thursday August 23, 2018 @08:33PM (#17831833)
> I've had my share of beefs with Sir_Cmpwn but this post is nonsense. You can't "largely" practice an open source model. Either you do or you don't.

Well, given that there are like 10 different criteria to meet it very obviously is not black and white.

You can view dgraph's source. You can modify and contribute to it. You can fork it, change it, etc. You just can't make it your own product that you sell.

It is open source in many, many ways, and probably the general, colloquial way. Whining endlessly because they don't want other people to sell it, and to maintain some semblance of ownership, is what's ridiculous.

Re:Jepsen: Dgraph 1.0.2 by eropple on Thursday August 23, 2018 @08:39PM (#17831863)
You can't accept money to talk to somebody about the open-source project. The Commons Clause literally says this! Does the level of bullshit that implies not resonate? Even if there weren't a nigh-universally accepted definition of open source software that precludes it--and it does--in what universe does that suggest openness?
Re:Jepsen: Dgraph 1.0.2 by staticassertion on Thursday August 23, 2018 @09:18PM (#17832033)
The code is open. You can modify the code. You can fork the code. You can do everything you'd normally do with the code.

You can not sell the code, or services that are directly based on the code.

Sounds pretty open and reasonable.

But we'll just have to disagree I think.

Re:Jepsen: Dgraph 1.0.2 by through1234 on Thursday August 23, 2018 @05:25PM (#17830815)
Suppose you need to fix a problem with the source code or want a new feature. With the clause they've got there, you can't find a developer or company and pay them to fix the software for you. So you can't practically get changes made to the product. So, it might as well be closed source.
Re:Jepsen: Dgraph 1.0.2 by eecc on Thursday August 23, 2018 @03:23PM (#17829897)
Can you please stop sanctimoniously sprinkling “dishonest” all over?
Re:Jepsen: Dgraph 1.0.2 by Sir_Cmpwn on Thursday August 23, 2018 @03:26PM (#17829912)
It accurately describes the behavior I'm talking about. Would you prefer I spice it up with some more "disingenous" and "misleading" too?
Re:Jepsen: Dgraph 1.0.2 by dragonwriter on Thursday August 23, 2018 @06:10PM (#17831064)
> In fact, as I was researching dgraph a bit more to see how you approached this issue, it also occurs to me that I can't find any discussion where existing Dgraph contributors were consulted on the matter of relicensing their work, which seems to me that your license change was not only distasteful and harmful to your project, but also illegal. Were all of the contributors consulted and their permission obtained to change the license?

Wait, did they not have a CLA?

Re:Jepsen: Dgraph 1.0.2 by Sir_Cmpwn on Thursday August 23, 2018 @08:48PM (#17831907)
No, I was wrong, and later found out that they've had a CLA for a while (you only find out about this when you submit a pull request, it's not mentioned in the contribution guide).
Re:Jepsen: Dgraph 1.0.2 by reitanqild on Thursday August 23, 2018 @04:56PM (#17830640)
I think liberally licensed makes perfect sense:

You can use it freely for open source and commercial applications with one, single, easy-to-understand catch:

You can't sell it or provide it as a paid service.

Is it open source? No.

Can I and you and almost everyone except Google Gloud, Amazon AWS and Microsoft Azure use it exactly as if it is open source? Yes.

Is it less hassle than the AGPL? IMO, clearly yes.

Re:Jepsen: Dgraph 1.0.2 by Sir_Cmpwn on Thursday August 23, 2018 @04:58PM (#17830660)
>Can I and you and almost everyone except Google Gloud, Amazon AWS and Microsoft Azure use it exactly as if it is open source?

No, definitely not. I elaborated on why "liberal" is inappropriate here in a different comment:

>There are widely accepted definitions for "liberal" among the open source community. The main differentiating factor of a liberal license is that it's not viral. Most people informed on this subject can then neatly and objectively file licenses into liberal and restrictive categories, with licenses like MIT, BSD, and Apache in the liberal camp, and the GPL family of licenses in the restrictive camp. However, the distinction has always been subjective, and nothing like the OSD exists. Additionally, the distinction is only ever applied in the comparison of open source licenses, of which yours is not a member. The realm of proprietary licenses masquarading as open source licenses is unexplored territory, and I'm drawing a line: no matter how restrictive a license like AGPL is, a license which is not even open source in the first place is far from liberal.

I also wrote here about how this affects people like you and I:

https://news.ycombinator.com/item?id=17830644

Re:Jepsen: Dgraph 1.0.2 by dragonwriter on Thursday August 23, 2018 @06:21PM (#17831122)
> You can use it freely for open source and commercial applications with one, single, easy-to-understand catch:

> You can't sell it or provide it as a paid service.

The limitation in the license text is not that narrow; restricting the right to sell any product or service whose value derives “substantially” from the Commons Clause software. In legal context, “substantially” generally is a rough synonym of “nontrivially”.

You seem to be suggesting that he license intended to only restrict sales of software/services which have no substantial source of value besides the upstream software, but that's not how it's actually written.

Re:Jepsen: Dgraph 1.0.2 by reitanqild on Thursday August 23, 2018 @11:35PM (#17832590)
> You seem to be suggesting that he license intended to only restrict sales of software/services which have no substantial source of value besides the upstream software, but that's not how it's actually written

As far as I understand the license clearly permits me to:

-Use the licensed software internally.

-Modify the licensed software.

-Share my modifications.

-Write software that connects direcly to the licensed software, with no restrrictions on my software (unlike AGPL)

-From this it follows that I can license my software that uses the licensed software any way I want.

-I'm not sure if I will be allowed to bundle the licensed software with my software,

-But it should be allowed to say that the user as to install the licensed software and run it for my software to work.

-Sharing the licensed software in a bundle (e.g. Linux distro) seems to be OK as long as I don't charge for it. This probably will need to be sorted out for Redhat etc.

Please correct me if any of the above is incorrect. I might have misunderstood it but this was my best understanding.

Re:Jepsen: Dgraph 1.0.2 by through1234 on Thursday August 23, 2018 @05:29PM (#17830844)
It's liberally licensed in the sense that it's freeware, but you don't get the benefits you'd have from it being open source.
Re:Jepsen: Dgraph 1.0.2 by reitanqild on Friday August 24, 2018 @01:12AM (#17832926)
> but you don't get the benefits you'd have from it being open source.

To me it seems more correct to say:

but you don't get all the benefits you'd have from it being open source.

Again though:

- while I see where this is coming from

- and it won't hurt me directly as far as I understand

- I still have a sketchy feeling about what this will lead to in the future

Re:Jepsen: Dgraph 1.0.2 by porker on Thursday August 23, 2018 @05:19PM (#17830777)
> Is it open source? No.

Yes it is. You can read the source code.

It's not FOSS, or Open Source per the OSI definition.

Re:Jepsen: Dgraph 1.0.2 by reitanqild on Thursday August 23, 2018 @05:25PM (#17830814)
> Yes it is. You can read the source code.

You can read the source of Oracle Java as well. Doesn't make it open source.

Open source has a defined meaning.

Common Clause even points out in their FAQ that it makes the software not open source.

Re:Jepsen: Dgraph 1.0.2 by tomnipotent on Thursday August 23, 2018 @06:17PM (#17831108)
This makes is source available, which is very different from open source.
Re:Jepsen: Dgraph 1.0.2 by marknadal on Thursday August 23, 2018 @01:44PM (#17829203)
Commons Clause, GPL, FSF, etc. are not liberal though.

MIT, BSD, ZLIB, Apache2, etc. are liberal.