This commit is contained in:
Miloslav Ciz 2024-03-14 23:30:14 +01:00
parent 6ac96e5e81
commit a8a438148b
33 changed files with 1816 additions and 1753 deletions

View file

@ -58,7 +58,7 @@ As a next step make sure you clearly **document** your work and the sources you
If you collaborate with someone on the work, it must be clear that ALL contributors to the work follow what we describe here (e.g. that they all agree to the license/waiver you have chosen etc.). It is safer if there are fewer contributors as with more people involved the chance of someone starting to "make trouble" increases.
Finally you need to actually release your work into the public domain. Remember that you want to achieve a **safe, world-wide public domain** (so again you shouldn't try to rely on some weird/obscure laws of your own small country). It must be stressed that it is NOT enough to write *"my work is public domain"*, this is simply legally insufficient (and in many countries you can't even put your work into public domain which is why you need a more sophisticated tool). You need to use a public domain [waiver](waiver.md) (similar to a [license](license.md)) which you just put alongside your work (e.g. into the `LICENSE` file), plus it is also good to explicitly write (e.g. in your readme) a sentence such as **"I, ..., release this work into public domain under CC0 1.0 (link), public domain"**. Keep in mind that the WORDING may be very important here, so try to write this well: we mention the license name AND its version (CC0 1.0, it may even be better to fully state *Creative Commons 1.0*) as well as a link to its exact text and also mention the words *public domain* afterwards to make the intent of public domain yet clearer to any doubters. Here we used what's currently probably the best waiver you can use: [Creative Commons Zero](cc0.md) (CC0) -- this is what we recommend. However note that CC0 only waives copyright and not other things like [trademarks](trademark.md) or [patents](patent.md), so e.g. for [software](software.md) you might need to add an extra waiver of these things as well.
Finally you need to actually release your work into the public domain. Remember that you want to achieve a **safe, world-wide public domain** (so again you shouldn't try to rely on some weird/obscure laws of your own small country). It must be stressed that it is NOT enough to write *"my work is public domain"*, this is simply legally insufficient (and in many countries you can't even put your work into public domain which is why you need a more sophisticated tool). You need to use a public domain [waiver](waiver.md) (similar to a [license](license.md)) which you just put alongside your work (e.g. into the `LICENSE` file), plus it is also good to explicitly write (e.g. in your readme) a sentence such as **"I, ..., release this work into public domain under CC0 1.0 (link), public domain"**. Bear in mind that the WORDING may be very important here, so try to write this well: we mention the license name AND its version (CC0 1.0, it may even be better to fully state *Creative Commons 1.0*) as well as a link to its exact text and also mention the words *public domain* afterwards to make the intent of public domain yet clearer to any doubters. Here we used what's currently probably the best waiver you can use: [Creative Commons Zero](cc0.md) (CC0) -- this is what we recommend. However note that CC0 only waives copyright and not other things like [trademarks](trademark.md) or [patents](patent.md), so e.g. for [software](software.md) you might need to add an extra waiver of these things as well.
{ I personally use the following waiver IN ADDITION to CC0 with my software to attempt waiving of patents, trademarks etc. I made it by taking some standard waiver companies use to steal "rights" of their employees and modifying it to make it a public domain waiver. If you want to use it, make sure you mention it is an EXTRA, additional waiver alongside CC0. The waiver text follows. ~drummyfish