News for hackers. Stuff that matters.
Re:What Have We Learned from This Open Source Project? by kuschku on Sunday February 07, 2016 @06:09PM (#11055443)
But that’s exactly why it’s less free.

With BSD code, the majority of devs can always sell out, and make sure all future modifications are purely proprietary.

We’ve seen that happen on Android.

Nowadays neither the launcher, nor the keyboard, nor the dialer, nor the contacts, nor the calendar, nor the device search is open source anymore.

Re:What Have We Learned from This Open Source Project? by reitanqild on Sunday February 07, 2016 @06:38PM (#11055555)
Could equally well happen if the code was released under GPL as long as all copyright holders agree?
Re:What Have We Learned from This Open Source Project? by cyphar on Sunday February 07, 2016 @08:32PM (#11055950)
In theory yes, in practice you couldn't even hope to get all of the copyright holders' permission. You'd have to surgically remove the code of everyone who didn't consent to the relicensing (good luck) and everybody would hate you for it.
Re:What Have We Learned from This Open Source Project? by reitanqild on Sunday February 07, 2016 @11:11PM (#11056284)
Well, then you have code written for a company on company and code written under a contributor agreement.

A lot of code that ended up under free licenses has been proprietary first and while they cannot revoke the free licenses from already released code they can make their next release non-free as long as they haven't accepted outside contributions without a suitable contributor agreement.

Re:What Have We Learned from This Open Source Project? by cyphar on Monday February 08, 2016 @02:20AM (#11056782)
> Well, then you have code written for a company on company and code written under a contributor agreement.

Not all contributor agreements are equal, and I would recommend choosing which projects you will not contribute to based on their CLAs. If they ask you to give them copyright without good reason, they are preparing to fuck you over. Ironically, this is why I will not contribute to GNU because they require copyright assignment so they have a higher chance of winning conservancy cases (IANAL, but I have one in my family and this is bullshit in my country but may be true in the US, so I feel conflicted about it).

> A lot of code that ended up under free licenses has been proprietary first and while they cannot revoke the free licenses from already released code they can make their next release non-free as long as they haven't accepted outside contributions without a suitable contributor agreement.

The only example I can think of is OpenSolaris (which required contributors to sign a CLA that assigned copyright to Sun/Oracle). Most modern projects don't work like that, and if you have a copyleft license, a company could not legally create a proprietary fork and distribute it.

Besides, if that happens you end up with free software forks (illumos in the OpenSolaris case) and everyone moves to using that.