How will Acquia support a module that is included in one of its distributions?
Acquia will maintain an engineering organization capable of actively contributing to any module it adds to its distribution. It also means that the engineering organization will be capable of answering support questions. A module (or other software) will not be added to Acquia’s distribution unless Acquia is satisfied that the module has been reviewed and tested for functionality, stability, scalability and security. Once Acquia elects to include a module in its distribution, Acquia is prepared to become an “expert” in this module and to partner with the module’s current maintainer to advance the module’s capabilities.
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?
- How will updates for Acquia distributions stay in sync with Drupal core/contrib module updates?
- How will Acquia support a module that is included in one of its distributions?
