Feature #2857
closed[EXAMPLES] Place the MIT license into examples root
0%
Description
The examples code should be licensed very liberally (e.g. MIT, as with "wtwithqt").
Many examples do not contain a license file. The first step would be to place a license file into the root examples folders.
http://opensource.org/licenses/MIT
(Sidenote: as Wt supports windows, the file should be named LICENSE.TXT and not LICENSE)
Updated by Wim Dumon over 10 years ago
- Status changed from New to Rejected
Our examples are licensed under GPL, except if otherwise noted.
Wim.
Updated by I. Lazaridis over 10 years ago
Wim Dumon wrote:
Our examples are licensed under GPL, except if otherwise noted.
I am aware of this.
And the suggestion is to make this more liberal, for reasons that should be obvious.
Updated by Koen Deforche over 10 years ago
Hey,
What's the obvious reason?
The license for the examples is the same as the license for the library.
If you use any of the example code with a GPL version of the library, then automatically the whole work becomes GPL. If you use any of the example code with a commercial licensed version of the library, then everything falls within the terms of your commercial license.
koen
Updated by I. Lazaridis over 10 years ago
Koen Deforche wrote:
Hey,
What's the obvious reason?
I apologize for the use of the term "obvious" (as with licenses nothing is obvious).
The license for the examples is the same as the license for the library.
yes, that's ok, but see below.
If you use any of the example code with a GPL version of the library, then automatically the whole work becomes GPL. If you use any of the example code with a commercial licensed version of the library, then everything falls within the terms of your commercial license.
If so, the why "wtwithqt" has an MIT license? This is a bit missleading.
Updated by Koen Deforche over 10 years ago
Hey,
wtwithqt is MIT licensed because this is the only way we could develop this and make it useful to Qt developers that have either a GPL or a commerical license to Qt.
I do have the following suggestion for you though: why don't you post messages to the discussion forum, with questions that you have, and then we can decide there whether this is something that should be addressed in the library, and thus needs to be added the tracker. This is in fact something that many users do, and is much appreciated.
koen
Updated by I. Lazaridis over 10 years ago
Koen Deforche wrote:
Hey,
wtwithqt is MIT licensed because this is the only way we could develop this and make it useful to Qt developers that have either a GPL or a commerical license to Qt.
I do have the following suggestion for you though: why don't you post messages to the discussion forum, with questions that you have, and then we can decide there whether this is something that should be addressed in the library, and thus needs to be added the tracker. This is in fact something that many users do, and is much appreciated.
You are of course right. That's the process I usually follow, I was just quite sure about this issue (and I'm not perfect). Here's the forum topic: