This article is the next part in our series about recent changes at the Drupal Association. I'll be focusing on what these changes mean for the Engineering team and the impact that will have on the work we're doing for the Drupal Community.
Look at our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board.
The Drupal.org Engineering team finished out 2015 with some quick wins, some planning for the new year, and some time spent catching our breath. With the December holidays wrapped in as well, this will be a bit of a shorter update. But after a frenetic November supporting the Drupal 8 release, a quieter December was just what the team needed to close the book on the year.
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.
DrupalCon Barcelona Recap
DrupalCon Barcelona was an opportunity for Drupal Association staff to meet with members of the community, attend some critical sessions about upcoming development in Core and Contrib, and to present some sessions of our own.
After a month of planning and organizational introspection in July, the Association spent August getting down to brass tacks. Since May, progress on Drupal 8 criticals has been rapid and we focused on doing our part to clear blockers for the upcoming Drupal 8 release candidate.
July was an action packed month at the Drupal Association - we had our quarterly prioritization with the Working Groups, our annual all-hands summer staff meeting, and mentored two tremendously dedicated interns throughout.
Our primary engineering focus was on DrupalCI and Localize.drupal.org - though we also found time to make some iterative changes to Drupal.org in a few areas, namely: issue credit refinements, performance, groundwork for the new content model.
