If you have “I need to protect myself” or submarine patent license concerns, just release it under Apache-2.0, and then act like you released it as PD.
You really can’t PD it and “protect yourself”. But if your intent is to let it be widely used, widely read, under terms that are well understood and already approved for use and inclusion by nearly every government, edu, corp, and other project… just use Apache 2.0. ..m -- Mark Atwood atwo...@amazon.com<mailto:atwo...@amazon.com> Principal Engineer, Open Source Program Office, Amazon.com +12066042198 From: License-discuss <license-discuss-boun...@lists.opensource.org> On Behalf Of public final Stvk; Sent: Friday, April 5, 2024 10:59 PM To: license-discuss@lists.opensource.org Subject: [EXTERNAL] [License-discuss] I edited the CC0 license to solve patent issue, need some advice CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. So i just want to release my code to public domain and CC0 are an excellent tool for that (the Unlicense are crayon), but the patent problem of CC0 grant me headache I really don't want me or anyone to be victim of patent submarine so i just edit the CC0 legal code to explictly grant patent and trademark rights then re-name it to "True Zero License" (CC are Creative Commons trademark) Sorry if this worsen license proliferation but i can't find any license for my need I need some advice and review from experienced people, here are the license (plain text file)
_______________________________________________ The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address. License-discuss mailing list License-discuss@lists.opensource.org http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
