How do you intend to offer both commercial-grade support for Acquia distributions while enabling people to benefit from Drupals modularity and flexibility?
We recognize that this is a difficult challenge. On one hand, Drupal’s flexibility is what makes it great. On the other, it’s what makes it hard to swallow when a customer is first getting started, or requires stability above all else. Fortunately, we’re not the first to address this issue, either. RedHat faced the same problem with Linux. What we expect is that following the Acquia distro path will lead customers to make choices about what is most critical on their requirements list and how they can best meet those requirements. In some cases, stability and supportability will outweigh custom theming or use of a great new module. In the long term, these choices will become another set of data points for the Drupal community at large to consider when making development decisions.
Related Questions
- How do you intend to offer both commercial-grade support for Acquia distributions while enabling people to benefit from Drupals modularity and flexibility?
- Why don you offer to support, customize and document any systems besides Joomla, Drupal, WordPress, Serendipity, SMF, phpBB, Menalto Gallery and Coppermine?
- How can African governments help support this technological revolution to benefit their people?
