What this list doesn’t expose is the huge effort that has been put in to gain architectural consensus to ensure wide adoption of these modules. This journey started with a summit we held at BadCamp in October to discuss what modules would be required to build a full authoring experience for Drupal 8. Since then it has played out in ways delightful and unexpected.

Developers have reached out to us from the largest Drupal sites in the world to ask how they can help complete modules. Maintainers and other community members have donated their time to attend discussions and planning meetings. We’ve hosted robust debates on the importance of standards and the merits of tightly coupling functional areas. Again and again we've seen that wide consensus can be reached because we all share the common goal of making Drupal 8 a powerful tool for authors, site builders, and developers.

Poll

Add comment

Comments

I'm a little confused about Token in this list. If you see the last 20 or so commits that have been pushed since Christmas, they were contributed by me among others. Still, I never knew of Acquia involvement or funding for this. The only person I know who is in regular touch is Berdir and he was the one who committed my patches.

You're right to large extent. This team has had far less involvement with Token than the other modules on the list. Juampy had some time in between his work on Pathauto and Workbench Moderation (among others - Juampy has touched a LOT of modules as part of this team) so we asked him to help out a bit in the Token issue queue.

I agree Lee, many need to be thanked, I have directly worked with these people as a part of D8 MAP and I wanted to call them out, but Drupal is full of collaborative fantastic people many of whom have helped us directly and indirectly. One of the main goals of the program is to make use of the good work already completed by the community and release working modules that can be used without intimate knowledge of the code. Hopefully this will magnify the utility of Drupal 8 and recreate the explosive wave of adoption we saw after D7 Views was released.

I think the takeaway is we should always just state that "acceleration" means contributing to the community's efforts, that many others are involved outside Acquia, and that in some of the cases we are helping lead the charge but in others we are merely supporting efforts led by other contributors and organizations.

Our goal and what is true for the vast majority of modules in the program is that we build on the porting work of the community and make modules production ready. The feature additions we have made to some modules are significant, but I think the most important achievement of the program is that we have gotten modules to the point where site builders can use them, which in some cases would have taken an extra 6-12 months.