10 ms·
[Fedora-legal-list] Change in classification of CC0
- freemint 4y agoSo we need any american to relicense any CC0 work as 0BSD and then it should be all good.
- draw_down 4y agoI think people are free to license their work as they see fit, and whether Fedora likes that or not is their own business and their own problem.
- tinus_hn 4y agoThe silly part is that the licensor claims he will not assert any patent rights regarding the code. But someone else might still do that.
- mormegil 4y agoThis. The original argument is sideways. When contributing code, you claim to have written it yourself and you grant a copyright license to this work of yours. You don't claim the contributed code does not infringe on any patent. (How could you?? Normal code contributor has no idea how to check that.) So the only evil plan the CC0 prohibition foils (a patent holder contributes code needing patent license under CC0 and later sues for patent infringement) needs only to be slightly modified: the patent holder asks/hires someone to contribute such code. This person grants all rights using BSD0 but obviously cannot grant a patent license to someone else's patent, so the patent holder can still sue.
- mananaysiempre 4y agoSomeone else might do that anyway, don’t they? (Barring the mutually-assured-destruction clause in Apache-2.0, but even that only works if that someone is simultaneously interested in using the code in question.)
- MichaelCollins 4y agoEven if he properly and legally relinquished any and all patent rights, there is nothing to stop him from layering up and suing everybody anyway in direct contradiction to the patent grant. Presumably all the lawsuits would fail, but harassing others with flagrantly horseshit lawsuits is an industry.
- MichaelCollins 4y agoOr they could just bequeath their code to the public domain, and ignore the quirks of foreign legal systems that make that weird in other countries. List of Germans who've been sued for using SQLite without a license: .... [End of list]
- kube-system 4y agoJust because SQLite project hasn't sued any Germans doesn't mean there's not legal risk involved. Build a billion dollar company on some "public domain" software in Germany, and you've given a stranger a gun to your head. They might not exercise their copyright, but they also could.
- naniwaduni 4y agoIf some foreign rightholder actually tries suing a billion-dollar German company in German court on the basis of lack of license to some software dedicated to the public domain, do you really expect them not to get laughed out of court?
- kube-system 4y agoAs I understand, German courts do not recognize public domain dedications, because they recognize “authors rights” which are not fully transferable or licensable.
- naniwaduni 4y agoDo you really think that's going to be the sticking point if someone tries to sue over it?
- MichaelCollins 4y agoYes, if I imagine myself to be a billion dollar corporation instead of Joe Random, then I have to act differently. But I'm not, and so I don't.
- wongarsu 4y agoIn the sense that CC0 work is just public domain in the US, and thus an American can just assign it the 0BSD? Legally that should work, even for non-Americans: the 0BSD doesn't grant anything the CC0 doesn't. But that doesn't work if you assume the 0BSD has a patent grant (by arguing that it gives you permission to use, modify, etc. the software). Then the product of your license reassignment is 0BSD, but doesn't grant permission from all authors, thus preventing its use in Fedora.
- yjftsjthsd-h 4y ago> In the sense that CC0 work is just public domain in the US, and thus an American can just assign it the 0BSD? If I search for CC0, the first hit is https://creativecommons.org/share-your-work/public-domain/cc0/ https://creativecommons.org/share-your-work/public-domain/cc... which already starts to answer from the URL, but let me just quote it: > CC0 enables scientists, educators, artists and other creators and owners of copyright- or database-protected content to waive those interests in their works and thereby place them as completely as possible in the public domain, so that others may freely build upon, enhance and reuse the works for any purposes without restriction under copyright or database law. So yes, IANAL but AFAIK CC0 is just "public domain" but spelled out (the rest of that link explains why this might be needed). > and thus an American can just assign it the 0BSD? The catch, as I understand it, is that yes any American could take something under CC0 and re-release it under 0BSD (probably, again IANAL) but they can only give away the rights they had in the first place so they can't say "and nobody can claim a patent infringement on this", only "and I promise you can use this and I won't sue you for patent infringement". The original authors, if they have a patent, could (as this argument goes) still sue for patent infringement because they never agreed not to (allegedly).
- thrillgore 4y agoWill this exclude just declaring a work as public domain, like some of the Boost libraries?
- gpderetta 4y agoBoost libs are not public domain; they are licensed under the Boost license.
- thrillgore 4y agoI did not know that, I must have confused them for some other library.
- maxk42 4y agoSounds like Fedora is sacrificing good code for ideological purity.
- untitaker_ 4y agoMany Linux distros have been limiting their repos to FOSS from the start. Much of it is ideology, some of it is minimization of legal exposure.
- COGlory 4y agoThey aren't mutually exclusive.
- thaumasiotes 4y ago>> The reason for the change: Over a long period of time a consensus has been building in FOSS that licenses that preclude any form of patent licensing or patent forbearance cannot be considered FOSS. CC0 has a clause that says: "No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document." > Part of the background story is that on patents, we've fought the scenario that a patent holder could offer some FOSS library implementing their patented method, and then come chase you for patent infringement. What are the boundaries for me, FOSS user, to not be ensnared by a submarine license?
- tux1968 4y ago> and then come chase you for patent infringement. Honest question: How could they claim damages from someone to whom they've granted permission? It just doesn't seem like a likely problem. So i'm trying to understand what the actual threat is.
- macintux 4y ago> How could they claim damages from someone to whom they've granted permission? I think that's the key: technically they haven't granted permission, not explicitly, absent a patent waiver. (Disclaimer: not a lawyer, barely paying attention to this.)
- SeanLuke 4y agoIt would seem that complaint would also implicate MIT/X, BSD, and GPL 2.0, would it not?
- nonfamous 4y agoThe issue is that CC0 explicitly reserves trademark and patent rights. Those OSS licenses do not have this issue.
- mcherm 4y agoWhat is the legal difference between a license with this clause: > No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document. and a license with no clause at all addressing trademark or patent rights? Wouldn't both of those documents leave trademark and patent rights unaffected?
- mlinksva 4y agoOne analysis https://opensource.com/article/18/3/patent-grant-mit-license https://opensource.com/article/18/3/patent-grant-mit-license
- deleted 4y ago[deleted]
- slavik81 4y agoI particularly like this bit: > The MIT License unquestionably has an express [patent] license. That license is not limited to the granting of any particular flavor of intellectual property rights. The statement of license does not use the word "patent" or the word "copyright." When was the last time you heard someone expressing concern that the MIT License merely had an implied copyright license?
- SeanLuke 4y agoI do not think this is true. CC0 neither reserves nor waives these rights: instead it just says that the CC0 license (when it says "this document" it's referring to the license, not the licensed material) does not surrender any of these rights. This doesn't introduce anything new at all: it is effectively a reminder to the licensee. MIT, BSD, and GPL 2.0 also do not surrender those rights. They just don't helpfully remind the licensee of this fact in the body of the license itself. The net result is, so far as I can tell, the same. It would seem to me that the complaint is with a license which doesn't surrender rights, particularly patent rights. I think this is proper: MIT, BSD, and GPL 2.0 are awful licenses for exactly this reason. *Edit* A quick mention of MIT. There are people who argue that MIT's "without restriction" clause sort of acts as a patent release. As if that was good. MIT is a bad license because a critical feature of a modern license -- a patent release -- hinges on a strained interpretation of a vague, easily misconstrued statement, and one which was clearly not the intention of the original license authors. A good license would have explicitly spelled things out. It takes just one judge to grind the MIT license into dirt.
- mixedCase 4y agoSounds stupid. If they want to be legally consistent they'd have to ban all FOSS licenses that don't waive patent rights. By default, patent rights aren't waived so explicitly retaining them is just literally stating the obvious. Any lawyer trying to sneak out of patent claims by saying "oh but the FOSS license didn't state they were retaining patent rights..." is just regular legal bullshitting and would not stand long in any half-working justice system.
- kazinator 4y agoI almost agree with you. Except that many FOSS developers who stick a license onto something do not hold any patents, or if they do, not necessarily anything relevant to that code. If you choose a license which explicitly says you're not waiving your patents, it insinuates that you are holding some, and they are used in the project.
- chrismorgan 4y agoIt insinuates nothing of the sort. It just suggests that you’re using a form license that mentions that. In the specific context of CC0, it’s not a license but rather a public domain dedication (with fallback license) and so anything about patents is by definition out of scope—the document is strictly focused on elements of copyright law. The sentence in question here is just reminding you of that fact.
- kazinator 4y agoI'm just trying to guess the reason why CC0 was singled out. Why would Fedora not want to expunge all licenses that doesn't mention patents at the same time? Probably the reasoning is that most licenses that don't mention patents don't actually have any patents behind them. Most CC0 probably don't either, but since CC0 explicitly says patents are not waived, that's where Fedora decided to start cleaning house. As a free software developer, I just want to know whether this is the way the wind is blowing? Do I have to re-license everything with a different BSD license that incorporates a patent waiver? I see this whole thing as pointless, because even if you don't hold any patents, it's almost impossible to write any significant piece of code without infringing on multiple ridiculous software patents that someone filed somewhere. Just because I add a sentence saying I won't enforce any patents against the users of my code doesn't mean that some third party in the world will not do that. That's probably one reason licenses are mum about patents; patents are a threat coming from someone else which your own waiver doesn't dispel.
- yc202207253987 4y agoTime to relicense to WTFPL I guess? Not American and used CC0 for everything. And don't say public domain because a LICENSE.txt file that just says "this is public domain" isn't a valid license, I think.
- MatthiasPortzel 4y agoThe Unlicense is designed to waive all rights while addressing as many of these nitpicks as possible. => https://Unlicense.org https://Unlicense.org It’s what I use for a public-domain-equivalent.
- chrismorgan 4y agoPlease don’t use the Unlicense. It’s at least as bad as CC0. If it works as a public domain dedication (which was its purpose, but lawyerly consensus seems to be that it failed at that and would be interpreted as a license) then it is in exactly the same boat as CC0, and if it works as a license, I see no scope at all for even an implied patent grant, and it explicitly speaks of copyright law as its scope (part of the failed PDD parts of the license), so it should still be in the same boat as CC0. (The only possible argument for any difference is that Unlicense would allow you to slightly more credibly plead ignorance, which seems a fairly absurd argument to me.) See https://chrismorgan.info/blog/unlicense/ https://chrismorgan.info/blog/unlicense/ for some more info and suggestions. (I do need to mull over the specific recommendations, as another point rises against CC0 specifically, and frankly the concept of public domain dedication in general.) As a starting suggestion, go with 0BSD, which is at least better-drafted than Unlicense and legally unambiguous.
- MatthiasPortzel 4y agoThere's a lot of second and third and fourth-hand reports of people who are not lawyers trying to discuss this. Your blog post, for example, cites as a source StackOverflow user "stawberryfields" who claims to have be reiterating something that they read in another StackOverflow answer. I'm not a lawyer, but I also can't afford to hire one. So I'd like to stick to things that actual lawyers have said. For reference, the OSI's comments when approving The Unlicense: > There is general agreement that the document is poorly drafted. It is > an attempt to dedicate a work to the public domain (which, taken > alone, would not be approved as an open source license) but it also > has wording commonly used for license grants.There was some discussion > about the legal effectiveness of the document, in particular how it > would operate in a jurisdiction where one cannot dedicate a work to > the public domain. The lawyers who opined on the issue, both US and > non-US, agreed that the document would most likely be interpreted as a > license and that the license met the OSD. It is therefore recommended > for approval. => https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2020-June/004890.html https://lists.opensource.org/pipermail/license-review_lists.... You seem to interpret "the document would most likely be interpreted as a license" as standing alone, which forms the basis of your critique. I interpret that line in the context of the sentence before. That is to say, I think "the issue" is how the license would be treated in a jurisdiction without a public domain, and I think that the lawyers agree the that it would be treated as a license only in that context. To quickly address some other points: Many people comment that "public domain dedication" is an ill-defined legal term and you shouldn't even try. Okay, fine, whatever. I'll happily use a public-domain-equivalent license. Citing the above, The Unlicense works for this purpose. Your comments on its name are understandable, but as someone who is trying to actually license my code in a public-domain-equivalent way, I can't afford to be picky about that. I don't trust/understand The FSF's "recommendation" for CC0 because in their guidance on CC0, they explicitly do not recommend using CC0 for software. (Not even to mention the thread we're commenting on.) Many people on the OSI mailing list harshly criticized The Unlicense for being written by someone that isn't a lawyer. While I understand their concerns, again, I'm not aware of any licenses written by lawyers to be public-domain equivalent. The BSD 0-clause is just deleting portions of the BSD license. Since neither of these were written by lawyers, I feel like I can speculate by saying that The Unlicense seems to me to cover a lot more cases and is a lot more explicit about its intent than 0BSD. All that is to say, I know that a lot of people don't like The Unlicense. I would love to use a public-domain-equivalent license written by a lawyer with a patent disclaimer. But doesn't exist, and the closest thing in intent is The Unlicense.
- ufo 4y agoWhich packages are potentially affected?
- gojomo 4y agoThe stated reason seems self-refuting within its own text. The quoted section of CC0 doesn't "preclude any form of patent licensing or patent forbearance". It just makes clear that CC0 is silent on those issues, allowing other documents/tradtions to govern. If instead the real reason is Fedora wants all licenses to include explicit "patent licensing or patent forbearance", that's different than the rationale excerpted by LWN here.
- deleted 4y ago[deleted]
- hsn915 4y ago"Please accept this giant wooden horse! We don't preclude the possibility that it's sincere gift given in good faith!".
- josephcsible 4y ago> The quoted section of CC0 doesn't "preclude any form of patent licensing or patent forbearance". But it does do exactly that. > It just makes clear that CC0 is silent on those issues It doesn't do that, because that's impossible to do. Saying "I'm not talking about X" is talking about X.
- gojomo 4y agoIt doesn’t ‘preclude’ anything by disclaiming implications either way. It leaves all possibilities open, which is the opposite of ‘precluding’. Someone can absolutely say “Though some might think my prior words endorse or reject X, let me be clear I don’t endorse or reject X.” You can mention X, especially in a aspires-to-be-rigorous context like law, without committing to a treatment.
- josephcsible 4y agoSure, but that's not what CC0 says. CC0 says "No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.", which is more like saying "I reject X."
- stefanos82 4y agoSQLite is under Public Domain, but not under CC0; I wonder how will this going to affect it...
- dang 4y agoUrl changed from https://lwn.net/Articles/902410/ https://lwn.net/Articles/902410/, which points to this.
- lmc 4y agoSo what they are worried about is an entity that does the following: 1. Quietly patent sexy new algorithm 2. Release CC0 implementation of algorithm without mentioning they hold a patent. 3. ? (sue for infringement) 4. Profit Anyone that tried this should be laughed out of court. If they're not, the law needs an overhaul.
- sodality2 4y agoIs there any license that I can place my code under, that truly does not stop anyone from using it, for any reason? What legalese would I need to tell bespoke legal systems that I want to revoke all rights, in any situation, to anything in that project? Is there a license project that fulfills that need? And I don’t mean the WTFPL: I mean a license that legally stands and does what it is intended to do, and that would satisfy even the most conservative of lawyers that it’s safe to use?
- doublepg23 4y agoIs there anything wrong with MIT or the more succinct ISC license? Is the attribution portion a sticking point?
- sodality2 4y agoYeah, I mean a license without any strings attached at all. I’m just curious if one exists already.
- mlinksva 4y agoYes, 0BSD is ISC with ", provided that the above copyright notice and this permission notice appear in all copies" removed. MIT-0 is MIT with "subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software" removed. Unlicense is a more ideological statement.
- occamrazor 4y agoOther comments provide links to licenses similar to what you are looking for. But I’d like to argue that the MIT/BSD2 licenses are _better_ than a “no strings attached“ license, even when one wants to give the broadest permissions to use and modify a piece of code. The obligation to preserve attribution and license is as unobtrusive as possible, and at the same time gives assurance that the code is actually properly licensed. The typical corporate entity will not trust a piece of code with no license and would have to track copyright and license in some database. Having the same information in the source files makes things easier.
- eikenberry 4y agoGiven software patents are unethical, this means as a software developer I should start considering CC0 for code as it will prevent people/companies that play the software patent game from using that software?
- bawolff 4y agoNo... Its the opposite.
- ninefathom 4y agoIt seems very important to point out something here that I hope is obvious, but may not be: the Fedora project is not representative of, nor does it speak for, the entire Linux ecosystem. Fedora is ultimately stewarded by Red Hat, which (let's not forget)... is now an IBM company. As such, a cynic might be inclined to read this notice more like "IBM doesn't like FOSS licenses that are (or might possibly be construed as) patent-prohibitive." At the risk of sounding churlish... NO $**T! Phrased more delicately, methinks one's motives might be suspect. I find this little more than another pawn moved around the board in the whole "how cozy with big business should FOSS be" debate, and my personal take is that we passed most sane thresholds a decade or more ago. IBM via Red Hat via Fedora can 2>&1>/dev/null .