4 ms·
> He can do that? > Uh… probably? As I mentioned, most of the code is under BSD-style licenses. The command line utility to actually mount the damn thing is un
by dangus 7y ago
> He can do that?
> Uh… probably? As I mentioned, most of the code is under BSD-style licenses. The command line utility to actually mount the damn thing is under the Apple Public Source License, which has a “soft copyleft.” But in theory, if no further changes are made to this part of the code, it already meets the requirements for source code distribution.
Just a note here, my understanding of the legal status of software licenses is that they don’t supersede your own ownership of copyright.
As the nearly-sole contributor, the author can violate his own license for the code he created. Even if the whole thing was GPLv3, I think he could simply remove anyone else’s contributed commits and take the rest as proprietary code. It doesn’t sound like much work was done by other contributors on this project anyway.
Now, if he’s closed sourcing and using/changing someone else’s contributions that were licensed to the public in a copyleft license, that’s a different story.
(IANAL)
- im3w1l 7y agoIt matters because > FUSE for macOS (or, the kernel extension formerly known as osxfuse) is a project dating back to 2011. It in turn is based on even older projects, such as MacFUSE, the Linux FUSE module, and even some code open sourced by Apple.
- matkoniecz 7y ago> As the nearly-sole contributor, the author can violate his own license for the code he created. To be more specific, it is not in a violation of copyright. I am pretty sure that when I publish my code under any standard* licence it is not an exclusive license. I can still sell access on a more business friendly licence, publish it under CC0 and so on. *is there even serious licence that includes "no dual licencing" exclusivity clause that is binding the author? Is it even possible to do as a licence?
- wongarsu 7y ago> Is it even possible to do as a licence? I guess you could draft it as some kind of exclusivity licence "this work will only ever be available under this licence". You would still own the copyright, just contractually bound not to exercise it. But even that wouldn't be very convincing. If the author republishes under another licence this isn't in violation of copyright or any criminal law, it's more like "I gave written agreement not to do something I have the legal right to do, did it anyway, and nobody can demonstrate any damages. Sue me"
- ben509 7y ago> Is it even possible to do as a licence? IANAL, but a license, can't, in itself, restrict anyone's rights because it is a grant of usage, and a more restrictive licenses is really a lesser grant. In the case of software licenses, the rights were already restricted by the claim of copyright. And that's generally the case: you give someone license to enter your home, which they were implicitly restricted from by your holding the right to passage about your property. The legal mechanism that lets you negotiate to restrict your or others rights is a contract, and that's completely different from a license.