2 ms·
Dual licensing also makes it IMHO less likely that a project "continues as proprietary". Example: Qt. I think "contributor agreements" are the biggest red flag
by cies 2y ago
Dual licensing also makes it IMHO less likely that a project "continues as proprietary". Example: Qt.
I think "contributor agreements" are the biggest red flag. Though I like them for potentially upgrading a license (say from GPLv2 to v3), not that this always is a good thing.
- aragilar 2y agoIt's also worth mentioning the specific agreement between KDE and Qt (https://kde.org/community/whatiskde/kdefreeqtfoundation/ https://kde.org/community/whatiskde/kdefreeqtfoundation/ and https://www.qt.io/faq/3.2.-why-do-you-have-an-agreement-with-kde-about-your-licensing-what-kde-is-and-whats-the-history-of-qt-and-kde https://www.qt.io/faq/3.2.-why-do-you-have-an-agreement-with...), which shifts the incentives as well.
- pxc 2y agoYou don't need contributor license agreements for upgrading to future versions of the GPL. You can just license the code under 'GPL version N or later': https://www.gnu.org/licenses/license-compatibility.html https://www.gnu.org/licenses/license-compatibility.html