From 3a731d4ab6407d6d4539ca2af3126f0ca6f38373 Mon Sep 17 00:00:00 2001 From: 5unekku <@5unekku> Date: Fri, 12 Jun 2026 12:51:30 -0400 Subject: [PATCH] better relicensing attempt --- license | 5 ----- license-mit0 | 16 ++++++++++++++++ license-wtfpl | 11 +++++++++++ notice | 7 +++++++ readme.md | 4 ++++ 5 files changed, 38 insertions(+), 5 deletions(-) delete mode 100644 license create mode 100644 license-mit0 create mode 100644 license-wtfpl create mode 100644 notice diff --git a/license b/license deleted file mode 100644 index 0b8ae76..0000000 --- a/license +++ /dev/null @@ -1,5 +0,0 @@ -Copyright (C) YEAR by AUTHOR EMAIL - -Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. - -THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. diff --git a/license-mit0 b/license-mit0 new file mode 100644 index 0000000..a4e9dc9 --- /dev/null +++ b/license-mit0 @@ -0,0 +1,16 @@ +MIT No Attribution + +Copyright + +Permission is hereby granted, free of charge, to any person obtaining a copy of this +software and associated documentation files (the "Software"), to deal in the Software +without restriction, including without limitation the rights to use, copy, modify, +merge, publish, distribute, sublicense, and/or sell copies of the Software, and to +permit persons to whom the Software is furnished to do so. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, +INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A +PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT +HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION +OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. diff --git a/license-wtfpl b/license-wtfpl new file mode 100644 index 0000000..7a3094a --- /dev/null +++ b/license-wtfpl @@ -0,0 +1,11 @@ +DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE +Version 2, December 2004 + +Copyright (C) 2004 Sam Hocevar + +Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed. + +DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. You just DO WHAT THE FUCK YOU WANT TO. diff --git a/notice b/notice new file mode 100644 index 0000000..2791fdd --- /dev/null +++ b/notice @@ -0,0 +1,7 @@ +The Ly project transitioned its primary license from the WTFPL to the MIT0 license in June 2026 to introduce a standard liability disclaimer and resolve downstream packaging friction. + +As a result, copyright ownership and licensing are split by project history: + +1. Contributions made prior to June 2026 remain licensed under the Do What The Fuck You Want To Public License (WTFPL). See `LICENSE-WTFPL` for the full text. + +2. All modifications, refactors, and new contributions from June 2026 onward are licensed under the MIT No Attribution License (MIT0). See `LICENSE-MIT-0` for the full text. diff --git a/readme.md b/readme.md index 79c3a63..f76adb0 100644 --- a/readme.md +++ b/readme.md @@ -269,3 +269,7 @@ Also, Ly wouldn't be there today without [ashametrine](https://github.com/ashame If you like Ly and wish to support my work further, feel free to donate via my [Liberapay link](https://liberapay.com/ShiningLea)! + +## License + +This project is licensed under the **MIT0** license for all current and future development. Historical contributions made prior to June 2026 remain under the **WTFPL**. For explicit details regarding the transition and historical code boundaries, please review the `notice` file.