3 ms·
This I can agree with. The community frowns upon selling modules. This is reflected by the official repository offering no option of purchasing modules, no mark
by devwastaken 10y ago
This I can agree with. The community frowns upon selling modules. This is reflected by the official repository offering no option of purchasing modules, no marketplace. Contributors only make money by being sponsored by hosting sites like Acquia, where usually they're making modules /for/ them. This of course makes Drupal unnattractive for more advanced functionality. But, single developers still try to create that functionality anyways, even if its something that needs constant work and usual updates. This then understandably falls to the way side because life. Some things just need business behind them, they can't survive on openness alone.
Also: https://www.lullabot.com/articles/why-paid-drupal-modules-fail-drupal-as-art https://www.lullabot.com/articles/why-paid-drupal-modules-fa...
- jpetso 10y agoDrupal 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.
- ajsalminen 10y agoIf 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.