To select a license form for an application/project. lazarus / 8-Other ---------------------------------------------------------------------- lgrfbs · 2020-11-13 06:24 How do you choose a software license for a project or program? The reason I ask is that I've gotten to the point that 70-80% of an open source project needs to get a license and I really dislike license texts that feel like it's 5,000 pages long and no one will have the urge to read. I am in Sweden so I guess it will be Europe laws that will apply if there are legal problems. ---------------------------------------------------------------------- lucamar · 2020-11-13 06:38 First, you have to decide what you want your users and or developers to be able to do (legally speaking) with your code: *) If you don't really care whether someone else might take parts or the whole and use/expand it into a closed-source program, then select a permissive license, like MIT, BSD, MPL, etc. *) If you do care and you want your code to keep being free/open source, then select a more strict license like the GPL or, since you're in Europe, the EUPL (European Union Public License). In the first case, if you really want a very simple license with just a few statements, then select MIT, BSD-3-clause or alike; otherwise select one "made by lawyers" like MPL or Apache. The Open Source Initiative has several lists of "aproved" licenses, like for example: Licenses by Category, which might come in handy for selecting the more appropriate one. ---------------------------------------------------------------------- lgrfbs · 2020-11-13 06:44 Thanks for the link, now I have some to go through. ---------------------------------------------------------------------- avra · 2020-11-13 08:02 Quote from: lgrfbs on November 13, 2020, 07:24:26 amI really dislike license texts that feel like it's 5,000 pages long and no one will have the urge to read.You might want to use this plain english license simplification site: https://tldrlegal.com ---------------------------------------------------------------------- dbannon · 2020-11-13 08:15 Quote from: lgrfbs on November 13, 2020, 07:24:26 am... and I really dislike license texts that feel like it's 5,000 pages long and no one will have the urge to read. I have this at the top of all my file, its short, very clear, allows almost anything but the copyright statement must remain - Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i {   Copyright (C) 2017-2020 David Bannon    License:    This code is licensed under BSD 3-Clause Clear License, see file License.txt    or https://spdx.org/licenses/BSD-3-Clause-Clear.html} I reproduce the actual license text in the file, License.txt but even it is short and sweet. I strongly recommend you use an existing, recognized license. I have just completed a very long and very awkward process with a third party who had a license he wrote himself. Debian in particular would not touch it ! ---------------------------------------------------------------------- Bart · 2020-11-13 12:35 And you can donate your code to the public domain: anyone can do anything with it as they see fit and they have no obligations to you. Bart ---------------------------------------------------------------------- dbannon · 2020-11-13 22:48 Quote from: Bart on November 13, 2020, 01:35:36 pmAnd you can donate your code to the public domain: anyone can do anything with it as they see fit and they have no obligations to you. Bart Indeed. However, recent very long and tedious dicussions with the Debian legal people has surprised me when it comes to 'public domain'. I am sure Tobias will not mind me further posting his comments - QuoteYou write in your README that all files without notice are public domain.    Please note that PublicDomain is not a thing world wide.  For example, here in    Germany, a author _cannot_ legally waive its own copyright, so would you mind    to change this sentence to "If there is none, the code is licensed under CC0."?    (https://choosealicense.com/licenses/cc0-1.0/ ) It's the PublicDomain    equivalent, but written to be legally ok worldwide. I, personally, have found skipping the boring licensing issues early on has come back to bite me now. Davo ---------------------------------------------------------------------- lucamar · 2020-11-14 06:53 He's completely right; we here in Spain have a similar situation in which some rights can't be legally waived or traspased, some even not mortis causa. It was done that way (historically) to somehow protect authors against abusive editors but it has the unwelcome effect that you're not able to do it even if you want to and you're your own editor. That's why with CC0 you waive all the waivable and promise not to sue for the unwaivable; all those clauses ending (or starting) with "to the extent permited by law", etc. ---------------------------------------------------------------------- Bart · 2020-11-14 15:07 OMG. You can of course always deny that you actually wrote the code in question  Bart ---------------------------------------------------------------------- trev · 2020-11-14 21:28 Unless you intend financing the enforcement of your licence (potentially worldwide), there seems little point imposing one. I've resorted to the unlicense of late. It may not be legally effective in jurisdictions which do not allow copyright waivers, but if you are not going to enforce your copyright the issue becomes somewhat academic anyway. ---------------------------------------------------------------------- dbannon · 2020-11-14 22:39 Quote from: trev on November 14, 2020, 10:28:58 pmUnless you intend financing the enforcement of your licence (potentially worldwide), there seems little point imposing one. No, its not about you taking action to defend your copyright, its about another person being able to use your code without worrying about you taking that action.  For huge organisations like Debian, its a risk they just cannot take. So, if something is apparently unlicensed, or licensed with wording that is not totally clear (in a legal sense), its a very firm 'No'. Quote from: trev on November 14, 2020, 10:28:58 pmI've resorted to the unlicense of late. It may not be legally effective in jurisdictions which do not allow copyright waivers, but if you are not going to enforce your copyright the issue becomes somewhat academic anyway. But despite its name, its just another license really, isn't it ?   It would probably be acceptable, as such, to Debian but they do recommend CC0 because it achieves the same thing but is familiar to them. Davo ---------------------------------------------------------------------- trev · 2020-11-15 21:29 Quote from: dbannon on November 14, 2020, 11:39:34 pmBut despite its name, its just another license really, isn't it ?  More of a hybrid - a statement that it's in the public domain followed by a copyright waiver (licence) for those jurisdictions where there is no (legal) notion of the public domain and/or an automatic copyright is imposed. ---------------------------------------------------------------------- Zoran · 2020-11-15 22:04 When choosing the license, this can be helpful: https://choosealicense.com/licenses/ ---------------------------------------------------------------------- trev · 2020-11-15 23:15 Quote from: Zoran on November 15, 2020, 11:04:52 pmWhen choosing the license, this can be helpful: https://choosealicense.com/licenses/ Network Timeout The operation timed out when attempting to contact choosealicense.com. ---------------------------------------------------------------------- Zoran · 2020-11-16 00:11 Quote from: trev on November 16, 2020, 12:15:06 am Network Timeout The operation timed out when attempting to contact choosealicense.com. Works here... ---------------------------------------------------------------------- lucamar · 2020-11-16 00:50 Quote from: trev on November 15, 2020, 10:29:52 pmMore of a hybrid - a statement that it's in the public domain followed by a copyright waiver (licence) for those jurisdictions where there is no (legal) notion of the public domain and/or an automatic copyright is imposed. So basically like a CC0, only with CC0 you also get, if you need it, a nice, fully worded legal document to keep lawyers and politicians happy ---------------------------------------------------------------------- dbannon · 2020-11-16 02:35 Both https://spdx.org/licenses/ and https://choosealicense.com/licenses/ mention unlicense and CCO. I personally find https://spdx.org/licenses/ more comprehensive and a bit easier to read. Not that either are much fun reading .... Davo ---------------------------------------------------------------------- trev · 2020-11-16 04:02 Quote from: lucamar on November 16, 2020, 01:50:35 amQuote from: trev on November 15, 2020, 10:29:52 pmMore of a hybrid - a statement that it's in the public domain followed by a copyright waiver (licence) for those jurisdictions where there is no (legal) notion of the public domain and/or an automatic copyright is imposed. So basically like a CC0, only with CC0 you also get, if you need it, a nice, fully worded legal document to keep lawyers and politicians happy The unlicense has the advantage of being both FSF and OSI approved. It also has nicely worded, simple legalese (IMHO as IAAL).