How will Acquia make code contributions to the community and Drupal.org for modules it supports?
If Acquia determines a broad enough customer need to include a module in its distributions, but an available module does not meet Acquia’s standards for functionality, stability, scalability and security, Acquia’s engineering organization will actively add the code we believe is needed to fill any such gaps. Acquia will work with the module’s maintainer to integrate these enhancements and fixes into the drupal.org code repository. Alternately, if a module simply does not exist to meet a need, Acquia will create the needed module, and (of course) contribute it to drupal.org. Acquia is NOT seeking to replace current module maintainers. Acquia seeks to provide help, code, and resources to selected modules and module maintainers to make these selected modules better for everyone.
Related Questions
- Will Acquia support contributed modules, third party themes or custom code that is not included in Acquia Drupal?
- How will Acquia make code contributions to the community and Drupal.org for modules it supports?
- How does Acquia make code contributions to the community and Drupal.org for modules it supports?
