Project

General

Profile

Wt for GPL 3 and AGPL 3 development?

Added by Andy Tai over 11 years ago

Can Wt be used in GPL v3 and AGPL v3 software development? Licensing under GPL v2/v3 and AGPL v3 should not impact the business model of Wt, that of dual licensing...


Replies (6)

RE: Wt for GPL 3 and AGPL 3 development? - Added by Pau Garcia i Quiles over 11 years ago

As of now, no, you cannot. Wt is GPLv2, which is incompatible with GPLv3 and AGPLv3:

http://en.wikipedia.org/wiki/GNU_General_Public_License#Compatibility_and_multi-licensing

I think it would make a lot of sense to release Wt under GPLv3, especially given the nature of Wt. With the current GPLv2 license, if you want to develop a website (something small, say, Facebook :-) ) and not pay for Wt, contribute back to Wt, or release the source for your application, you have no obligation to do so. Under GPLv3, you would need to either pay the Emweb folks, or release the source.

RE: Wt for GPL 3 and AGPL 3 development? - Added by Andy Tai over 11 years ago

Yes, I agree. I do not know if the Wt code copyright is being held by one party instead of spreading out among a number of parties. If everything is copyrighted by one party, it should be straightforward to give license Wt under both GPL2 and GPL3... And it should benefit the usage of Wt further in the open source fashion without risks to commercial licensing of Wt.

RE: Wt for GPL 3 and AGPL 3 development? - Added by Koen Deforche over 11 years ago

Hey,

An update on this: we are currently investigating whether changing our License to "GPLv2 or later" makes sense.

Regards,

koen

RE: Wt for GPL 3 and AGPL 3 development? - Added by Pau Garcia i Quiles over 11 years ago

I never license my code "GPLv2 or later" unless that means I cannot contribute to the project. Why? Because "later" is unknown. What if later means BSD? What if later means you have to make your code public and sacrifice your first son? :-)

It's your code, your company and your decision, but I always prefer to explicitly and concisely say what I allow. Leaving it too open may be a decision you regret in 10 years (or not, but you never know). If you license Wt under GPLv2 and GPLv3, and later decide you want to go with GPLv4, great, you can do that. If you license Wt under "GPLv2 or later" but in the future you decide GPLv4 is not in your best interest, well, you can only do that for newer versions, which may lead to undesired (for you) forks.

My 2 cents :-)

RE: Wt for GPL 3 and AGPL 3 development? - Added by Andy Tai over 11 years ago

This is great. Thanks

Koen Deforche wrote:

Hey,

An update on this: we are currently investigating whether changing our License to "GPLv2 or later" makes sense.

Regards,

koen

RE: Wt for GPL 3 and AGPL 3 development? - Added by Floyd Mason over 4 years ago

Hi, I am having issues integrating Wt into my application. In Wt's current licensing terms, the application has to be GPLv2 licensed, this causes problems when using other libraries licensed as GPLv3+ or Apache 2.0.

I propose the license to be changed to include GPLv3 by licensing as GPLv2+ or explicitly mentioning GPLv2 and GPLv3. According to https://www.gnu.org/licenses/rms-why-gplv3.html, there are no downsides to changing the license, by doing so, Wt could expand the scope of application and libraries it can be incorporated into.

    (1-6/6)