Pondus license change GPLv3+ - MIT
Hi all, pondus was previously licensed under GPLv3+; now starting from 0.7.0 the license is MIT. -- Jussi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Pondus license change GPLv3+ - MIT
Hi all, pondus was previously licensed under GPLv3+; now starting from 0.7.0 the license is MIT. That's doable? o.O -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Pondus license change GPLv3+ - MIT
Hi. On Sun, 27 Dec 2009 17:43:05 +, Ikem Krueger wrote That's doable? o.O The copyright holder can relicense the code however they see fit. What they cannot do is retroactively remove the GPL license from old versions. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Pondus license change GPLv3+ - MIT
Ralf Ertzinger wrote: Hi. On Sun, 27 Dec 2009 17:43:05 +, Ikem Krueger wrote That's doable? o.O The copyright holder can relicense the code however they see fit. What they cannot do is retroactively remove the GPL license from old versions. Relicensing is complicated when there are a lot of authors (copyright holders), because it is necessary to get the approval of everyone of them, with complications for unreachable people and dead people; in the past discussions on the GPLv2-GPLv3 relicensing for the kernel, there was an additional opinion that this requirement is not as stringent as it appears. In any case, relicensing a small project with a few authors (or just one) is as easy as editing a couple of files (source, webpage, ...). -- Roberto Ragusamail at robertoragusa.it -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
