5 ms·
Re-writing the code using the original source as a guide means it is a derivative work if you want to get picky. Changing the programming language doesn't make
by bhouston 12y ago
Re-writing the code using the original source as a guide means it is a derivative work if you want to get picky. Changing the programming language doesn't make it non-derivative.
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 https://en.wikipedia.org/wiki/Clean_room_design
BTW this guy can not stop derivative works once he has released it as BSD.
- deleted 12y ago[deleted]
- chii 12y ago> BTW this guy can not stop derivative works once he has released it as BSD. 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.
- Danieru 12y agoProvided no one else has ever contributed yes he can. In fact this is not unique to the BSD, you can do that with any license. Even proprietary licenses do not force the author to continue using the same license since they own the original copyright.
- SolarNet 12y agoUnless the license agreement for contributing specifically says the author forfeits their copyright, but no open source licenses I know of do this.
- Argorak 12y agoThis is impossible in certain jurisdictions.
- pyre 12y agoWhat's impossible? Reassigning copyright to the project maintainer?
- Argorak 12y agoExactly. Forfeiting copyright is not possible in some jurisdictions. I'm not sure what is unclear about a refutation of a single sentence.
- vidarh 12y agoI'm presuming what you are referring to, and which is likely to confuse a predominantly English speaking audience is that a number of countries with legal systems typically based in Germanic or Napoleonic legal systems, copyright consists of the combination of moral rights on one side and economic rights on the other hand. 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.
- stonemetal 12y agoWhile there aren't any software licenses that do that, many projects do it as a condition of accepting contributions. As an example here is GCC's contributor documentation: https://gcc.gnu.org/contribute.html https://gcc.gnu.org/contribute.html The short version is assign FSF copyright, or put it in the public domain.
- sgrove 12y agoIsn't this generally what Contributor Agreements are for - not giving up copyright, but jointly assigning it? E.g. https://www.clahub.com/ https://www.clahub.com/ I know to contribute to Clojure/ClojureScript-proper, I had to sign http://clojure.org/contributing http://clojure.org/contributing
- baddox 12y agoHow would the enforcement of that work? What if I have cloned the version of the repo that was BSD, and I'm working on a yet-unrelated derivative work when the author changes the license? The answer that seems reasonable to me (not that I expect any correlation between that and the actual law) is that any version of the code that was released with a given license is perpetually under that license.
- deleted 12y ago[deleted]
- wooger 12y agoNo, he can do that regardless if it's BSD code, as long as he keeps the copyright notice intact. 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.
- learnstats2 12y ago> BTW this guy can not stop derivative works once he has released it as BSD. Aside: Isn't is possible to revoke a license?
- sparkie 12y agoNo, not unless the original license text contained such a revocation clause, which isn't the case for BSD licenses.
- alextgordon 12y agoHuh? Where does the law say this? It is my impression that the copyright owner has all rights unless he explicitly relaxes them. A license by definition cannot create more rights, it can only relax them.
- nobotty 12y agoIt needs a revocation clause because yes he can revoke it from new versions, but no he cannot edit the original copy some guy downloaded with the BSD clause.
- brazzy 12y agoYes, but by publishing under the BSD license he has relaxed his rights, and he cannot retroactively change that.
- detaro 12y agoA license doesn't "relax" rights, it grants rights to others (and sometimes/in some jurisdictions also can limit how the copyright owner can make use of his rights) 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.
- alextgordon 12y agoAnd why can't you take it away? If I give someone a permit to cross my bridge, I can revoke it at any time. Usually when something is perpetual, you have to write in it: "perpetual" for it to actually be so.
- HackinOut 12y agoThanks for this. I would be interested to know if, in practice (in a court of law), attempt to show something is derivative work when it's not is a more common instance than when it actually is. How easy (or hard) is it to prove something is a derivative work? (i am especially thinking of 2 pieces of code doing basically the same thing with the same algorithm, no patents)
- bhouston 12y agoThere is done of case law regarding derivative works both in general as well as software. Some high profile examples: https://en.wikipedia.org/wiki/Oracle_v._Google https://en.wikipedia.org/wiki/Oracle_v._Google https://en.wikipedia.org/wiki/SCO%E2%80%93Linux_controversies https://en.wikipedia.org/wiki/SCO%E2%80%93Linux_controversie... There are tons and tons of cases in this area.
- dalke 12y agoClean room design is a sufficient but not necessary condition to establish that something is non-derivative. It's possible that enough changes to the source make it non-derivative under copyright law. 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.