As the Wikipedia link you gave says:
> Clean room design is usually employed as best practice, but not strictly required by law. In NEC Corp. v Intel Corp. (1990), NEC sought declaratory judgment against Intel's charges that NEC's engineers simply copied the microcode of the 8086 processor in their NEC V20 clone. A US judge ruled that while the early, internal revisions of NEC's microcode were indeed a copyright violation, the later one, which actually went into NEC's product, although derived from the former, were sufficiently different that they could be considered free of copyright violations.
As another example, BSD Unix evolved sufficiently away from AT&T Unix that only a couple of files needed to be replace to get away from AT&T's copyright.
Both derive from someone else's works, but that's a different sense of "derivative" than what copyright law cares about.
could he just remove the BSD license from all subsequent commits to the code base? The existing code base will still continue to be BSD licensed of course.
I can take any BSD code, close source it, develop it further inside my company, then sell it as a proprietary, closed source app.
Or re-license to GPL.
Forfeiting copyright is not possible in some jurisdictions.
I'm not sure what is unclear about a refutation of a single sentence.
Moral rights are generally impossible to forfeit and assign. Economic rights usually (I don't know of any jurisdictions where assigning economic rights to the project maintainer would be impossible - are you?) are possible to assign.
In common law systems, the two are usually traditionally much more closely tied, and when we talk about copyright in English, it is usually the economic rights we're referring to.
I know to contribute to Clojure/ClojureScript-proper, I had to sign http://clojure.org/contributing
The short version is assign FSF copyright, or put it in the public domain.
https://en.wikipedia.org/wiki/Oracle_v._Google https://en.wikipedia.org/wiki/SCO%E2%80%93Linux_controversie...
There are tons and tons of cases in this area.
Aside: Isn't is possible to revoke a license?
http://ifosslawbook.org/france/ ("Moral Rights" heading)
All rights granted under this License are granted for the
term of copyright on the Program, and are irrevocable
provided the stated conditions are met.
How does France work against this?If that's the law in France, it trumps the license text.
Just as the law trumps any clause requiring the sacrifice of the licensee's firstborn on an altar.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all.
Since allowing the licensor to revoke the licence would be an extra condition.I don't know how this affects the GPL specifically, but you can be pretty sure that if the GPL doesn't contain France-specific French-language legalese to work around it, then it's likely to be revokable whatever the license says. Of course this only affects you if you're in France or have French contributors.
> Nevertheless, the Intellectual Property Code provides some specific rules regarding moral rights over software. It provides that the author may not oppose modifications of the software, in as far as such modifications do not affect his honor or reputation, and exercise his right of withdrawal.
The remaining issue is that you can still forbid modifications that "affect your honor or reputation".
[1] http://legifrance.gouv.fr/affichCodeArticle.do?cidTexte=LEGI...
Assuming he holds the copyright for the entirety of the program, he could change the license for all future versions, and he also could stop distributing old versions under the old license (putting a new license on it, or simply discontinuing distribution). But, the old license has already granted thousands, or millions, of people, the right to distribute it under those terms.
If you give someone the right to do something and don't specify how you can take it away, you can't take it away again. Without termination clauses a license is a contract thats valid indefinitely.
In software, the license is what you sell. I don't buy MS Windows or Photoshop, I buy a license for it. If you sell me a 3-seat license of software v1.0 allowing me to install it on up to 3 computers, you can't come back 2 years later and change the terms to only 1 computer. Now, in 2 years, you might have v2.0 and require a new license for that. But the license you sold me for v1.0 remains in place.
By releasing the software under the BSD license, he basically sold us a license (price immaterial) granting permission to redistribute and alter the code, provided that new code includes the BSD license.
I understand that wasn't his intention. Another commenter pointed out that the author gave permission to another project which was being released under the BSD license. Now anyone that was "sold" the software with that license has been granted those redistribution rights.
If I pay money in return for a license to use Photoshop, there is a reasonable expectation that I can use that indefinitely. I give then money, they give me permission.
If I simply download a piece of open source software from the internet, that isn't the same thing. There's no transaction. There's no anything. If the author subsequently tells me "I hereby revoke all previous licenses", I don't see how that wouldn't have legal weight.
Money has nothing to do with it, all reproduction of bits is automatically covered by copyright law, and has a legal presumption of "all rights reserved" unless explicitly delineated in a license.
Even when paying money, it isn't a reasonable expectation to expect to be able to use it forever for all software. With shrink-wrap or click-through agreements, perhaps, by convention, but plenty of software is sold on subscription for example, or may have revocation clause without refund which is common with MMO games for example.
Some software also may naturally break some day due to incompatibility or disinterest by the author. Other than limited warranty protections by law, there's not much a buyer can do about it. This is of course subject to local laws which may allow moral revocation (France) or stricter warranties.
With regards to downloading a piece of open source, the downloader is consenting to the copyright license it is offered under: it's the same as a click through.
If there is no license, you technically have no right to use or redistribute the software (all rights are reserved).
If there is a license, usually that will explain the author's intentions for fees, redistribution rights, and rights of revocability.
The OSI exists to approve licenses as "open source" when they (among other clauses) explicitly denounce revocability. The only recourse is that an author can refuse to OSI license future modifications or releases of the software (basically making a private fork).
These licenses are explicit about what they do/do not grant. p
If you want a non-derivative work you need to do something like a clean room implementation where the one writing the code doesn't have access to the code of the existing implementation: https://en.wikipedia.org/wiki/Clean_room_design
BTW this guy can not stop derivative works once he has released it as BSD.