3 ms·
Considering that virtually every plugin for Drupal is available on drupal.org, for free, and that all drupal modules are released under the GPL, I think you're
by mixologic 10y ago
Considering that virtually every plugin for Drupal is available on drupal.org, for free, and that all drupal modules are released under the GPL, I think you're going to have a hard time including Drupal in this. Not to mention you'd likely not even get to use the Drupal trademark without Dries' approval, and I strongly doubt this is the kind of thing that would get that approval.
- felicianotech 10y agoThat same thing applies to WordPress. To goal isn't to replace all the free plugins or anything. Have you ever actually dealt with Drupal and it's modules? The process to install and upgrade them is extremely poor. WordPress is much more technology advanced in that area. The only way to sanely deal with modules in Drupal right now is by using Drush. While using Drush is great and CLI tools will always be needed, other options have an opportunity here.
- mixologic 10y agoYes, I have. I am on the drupal.org engineering team. I suggest you look into composer for managing modules. Also there is momentum on building an automatic update system for drupal, (https://www.drupal.org/node/2367319 https://www.drupal.org/node/2367319) so, while things can be improved, there really isn't much business opportunity there.
- felicianotech 10y agoOh that's great. Thanks for all the food work. Composer doesn't provide the same user experience that some people expect coming from the mobile world, which is the intention here. As for as the background updates Drupal Issue opened, that's absolutely great and I think sorely needed. I hope it gets pushed through. That doesn't solve the issue of installing or removing, or handling billing, across multiple sites. Pantheon has some really good tools built-in but outside of that, there's not much available at the moment.