4 ms·

They have an agreement to allow all contributors' work to be relicensed as closed-cource.

by milliams 12y ago

DSMan195276 12y ago
Do you have to 'sign' or agree to something before they accept your code then?
- milliams 12y ago
  Yes. In order to submit a patch though Gerrit, you must agree to https://codereview.qt-project.org/static/cla_individual.html https://codereview.qt-project.org/static/cla_individual.html Key is: Subject to the terms and conditions of this Agreement, Licensor hereby grants, in exchange for good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, to Digia a sublicensable, irrevocable, perpetual, worldwide, non-exclusive, royalty-free and fully paid-up copyright and trade secret license to reproduce, adapt, translate, modify, and prepare derivative works of, publicly display, publicly perform, sublicense, make available and distribute Licensor Contribution(s) and any derivative works thereof under license terms of Digia’s choosing including any Open Source Software license. I should note that one further reason for this is to conform with the KDE Free Qt Agreement (http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php http://www.kde.org/community/whatiskde/kdefreeqtfoundation.p...).
- kyrra 12y ago
  Google does the same thing[0] whenever you contribute code to any of their open source projects. [0] https://developers.google.com/open-source/cla/individual https://developers.google.com/open-source/cla/individual
  - hdevalence 12y ago
    One difference is that the Qt source code is also covered by the KDE Free Qt agreement (linked in a sibling comment), which basically acts as a poison pill to ensure that no future owner of Qt can pull an Oracle and close off development. For this reason, it's my opinion that the Qt CLA is much, much, less onerous than other CLAs, like Google's or Canonical's, in the sense of how much control is actually given away.

They have an agreement to allow all contributors' work to be relicensed as closed-cource.

DSMan195276 12y ago

Do you have to 'sign' or agree to something before they accept your code then?

milliams 12y ago
Yes. In order to submit a patch though Gerrit, you must agree to https://codereview.qt-project.org/static/cla_individual.html https://codereview.qt-project.org/static/cla_individual.html Key is: Subject to the terms and conditions of this Agreement, Licensor hereby grants, in exchange for good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, to Digia a sublicensable, irrevocable, perpetual, worldwide, non-exclusive, royalty-free and fully paid-up copyright and trade secret license to reproduce, adapt, translate, modify, and prepare derivative works of, publicly display, publicly perform, sublicense, make available and distribute Licensor Contribution(s) and any derivative works thereof under license terms of Digia’s choosing including any Open Source Software license. I should note that one further reason for this is to conform with the KDE Free Qt Agreement (http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php http://www.kde.org/community/whatiskde/kdefreeqtfoundation.p...).
kyrra 12y ago
Google does the same thing[0] whenever you contribute code to any of their open source projects. [0] https://developers.google.com/open-source/cla/individual https://developers.google.com/open-source/cla/individual
- hdevalence 12y ago
  One difference is that the Qt source code is also covered by the KDE Free Qt agreement (linked in a sibling comment), which basically acts as a poison pill to ensure that no future owner of Qt can pull an Oracle and close off development. For this reason, it's my opinion that the Qt CLA is much, much, less onerous than other CLAs, like Google's or Canonical's, in the sense of how much control is actually given away.