Closed hodgestar closed 2 years ago
One of the reasons I changed to the BSD license is that LGPL is a very odd license to use for a repository of Jupyter notebooks. The reason for the LGPL existing is to allow other projects to link to a library at run time -- which is not something that notebooks can typically do.
It looks like we can't just re-license to BSD -- https://opensource.stackexchange.com/questions/6698/can-i-use-code-from-an-lgpl-v2-licenced-project-in-a-bsd-3-clause-licenced-proje. However, that creates a bit of a mess because QuTiP is not licensed under the LGPL (e.g. we could not use code from the notebooks in QuTiP).
I propose that we attempt to re-license by contacting all the contributors and asking their permission. Most of the contributors are QuTiP admins or affiliates, but there are only 15 of us in total, so it's probably achievable. I will email qutip-admin and ask.
Getting permission from contributors to re-license is being tracked in https://github.com/qutip/qutip-notebooks/issues/146.
Permission obtained from all contributors. Re-licensing complete. We can continue to use the BSD license in this repository. \o/
As noted in #1, the qutip-notebooks repository used LGPL-3.0 but this repository is using BSD-3 for consistency with qutip and qutip-qip. Is this license change permitted, or do we need to keep the old LGPL-3.0 license? We need to check.