Re:Security vulnerability in #Drupal contrib module puts 120...
by jpetso on Saturday April 15, 2017 @01:58PM
(#14121878)
Drupal is GPL, so a module written specifically for Drupal must always be redistributable under GPL as well since it's a derived work. That places a natural limit on the feasibility of module purchases, since anyone could buy it and then mirror it for free.
The correct answer here is that if you don't like Drupal's free & community-focused development model, you're likely better off switching to some off-the-shelf software. Alternatively, you can pay a consulting company to maintain the module, which is how many of them get written anyway (and then given away for free). So if you focus on modules with commercial backing, you've got a pretty close approximation without giving up GPL freedoms.
Re:Security vulnerability in #Drupal contrib module puts 120...
by ajsalminen on Friday April 21, 2017 @03:24AM
(#14163684)
If you think going non-free with the modules would help you should take a look at the codebases of some of the most popular premium Wordpress modules. You'll find much worse than in a popular Drupal contrib module.
Also: https://www.lullabot.com/articles/why-paid-drupal-modules-fa...