Timeline for Open Source project change license from BSD 3 Clause to Lgpl-2.1
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2022 at 19:00 | comment | added | amon | @dev You must keep intact any BSD-3-clause license notices and should include the notice in your license file, but you don't have to tell recipients which specific parts are covered by what license. If they want to use the BSD-3-clause material they can likely use the hint that a BSD version exists to hunt down that version online. | |
| Jan 31, 2022 at 7:39 | comment | added | dev | Wondering if I modifed file A how will ppl know what I changed from BSD-3-clause part? They could diff/see changes in the whole project, but there are maaany files? So I just create new License.txt in the whole being Lgpl-2.1 with Commonsclause and keeping Bsd-3-clause info before it? | |
| Jan 31, 2022 at 7:30 | vote | accept | dev | ||
| Jan 30, 2022 at 20:06 | comment | added | nick012000 | "To be clear, you cannot change the license of other people's code." Without getting the consent of all the other authors, anyway | |
| Jan 30, 2022 at 19:40 | history | answered | amon | CC BY-SA 4.0 |