Am 16.01.2016 um 14:36 schrieb Konstantin Tokarev:


16.01.2016, 13:45, "Peter Kümmel" <[email protected]>:
Am 15.01.2016 um 15:46 schrieb Hunger Tobias:
  In essence Qt Creator will be GPL (with exception) from here on out. This
  effects the master branch of the Qt Creator repository. The stable branches 
are
  not going to get updated to the new licensing scheme.

Strange; change from LGPL to GPL without any discussions.

Peter,

If you read contributor agreement carefully, in 3.1 you grant non-exlusive rights to the 
code you've contributed to The Qt Company "under license terms of The Qt Company's 
choosing including any Open Source Software license".

Thanks for the reminder: I forgot I already sold my soul ;)



Is this again the idea, "if we don't GPL our code someone else earns MY
money" misbelief?

  Please take a bit of time and check whether the patches change the copyright 
in
  unintended ways, especially if you have contributed code to Qt Creator. I 
think
  I managed to keep all information in the headers intact, but please help to 
make
  sure. Checking and double-checking all this information is tedious work and I
  might have done some unintended changes.

  Please also check your license template: Please use the one we ship with Qt
  Creator in dist/copyright_template.txt (after adapting the copyright 
information
  of course)! This file is already updated in git (master branch).

  The first patch of the set is here:
  https://codereview.qt-project.org/#/c/146218/

  Please help reviewing the patches!

  The commercial plugins that are effected by the agreement are currently 
getting
  a similar license update and will get merged into the master branch once that 
is
  complete.

  Best Regards,
  Tobias

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to