Timeline for Can I make my own license?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 27, 2022 at 11:46 | comment | added | IntegralPilot | @MadHatter Thank you for your reply, I found it very helpful! | |
| Sep 27, 2022 at 11:46 | vote | accept | IntegralPilot | ||
| Sep 26, 2022 at 15:24 | comment | added | IMSoP | @MadHatter True, the requirement isn't quite as strict as I wrote there; I still think the point is an important one though: the proposed license wording doesn't acknowledge the possibility of the relicensing breaching someone else's copyright. I would expect a legally drafted license to list much clearer obligations and liabilities placed on contributors who were providing code they did not own the copyright to. | |
| Sep 26, 2022 at 11:25 | comment | added | MadHatter♦ | @IMSoP whilst that is true for copyleft licences, it is thought not to be true for the permissive licences. | |
| Sep 26, 2022 at 11:15 | comment | added | IMSoP | Worth adding on the CLA part that contributors can't relicense "no matter what license you got it under" - they can only relicense contributions for which they are the copyright owner. If I could take code that was licensed to me under the GPL and donate it to someone else under an MIT license, I could just play shell games and "donate" it to myself, avoiding the requirements of the GPL. | |
| Sep 25, 2022 at 19:41 | comment | added | MadHatter♦ | @PyRulez absolutely, but you still can't stop any of them passing it on under Apache2. | |
| Sep 24, 2022 at 16:50 | comment | added | Christopher King | Note also that if your the sole copyright holder, you can choose on a case-by-case basis who gets the apache license, if you prefer. | |
| Sep 24, 2022 at 9:28 | history | edited | MadHatter♦ | CC BY-SA 4.0 | added 16 characters in body |
| Sep 24, 2022 at 7:53 | history | answered | MadHatter♦ | CC BY-SA 4.0 |