Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By vyvee on
The GPLv3 has just become available, and many GPL-ed projects out there are debating if they should adopt it or not.
I wonder how the developers and the users of the Drupal look at this issue? Has the development team reached some decision? The change of license may affect the way Drupal is used... but probably not too much.
Personally, I feel that it's ok to use GPLv3. How about others?
Comments
See
There have been some posts
See http://lists.drupal.org/pipermail/development/2007-June/024987.html
And http://buytaert.net/long-live-the-web-services-loophole
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
drupal should adopt
and actually, the final draft of the gplv3 does not close the Saas loophole, because they tool the optional part out. they even defined what to "convey" software is, making SaaS not part of the gpl.
so drupal has no problem adopting gplv3, it provides the project with better protection in other issues and puts no constraint on others.
I think drupal should move because it will have to eventually anyway, and by doing it early it can set an example and serve as a leader, as it did with gophp5. It is however quite a hassle to get every developer for the license change.
i agree. the GPLv3 also
i agree. the GPLv3 also solves annoying issues like the Apache license incompatibility that affects GPLv2
You don't have to ask any
You don't have to ask any developer to release Drupal under GPLv3 because Druapl is currently licensed under GPLv2+. That means you are free to download, reuse, modify, and distribute any files hosted in Drupal.org's Git repositories under the terms of either the GPL version 2 or version 3. So of course drupal.org itself could also switch to GPLv3 immediately.
See also http://groups.drupal.org/node/211698