Digging into Module Maintenance

It's been about three months since I joined Phase2 as Community Manager, and I have really appreciated getting to know the needs of the community around Phase2's products and contributed modules. Thank you so much to those of you who have offered your honest -- and at times colorful! -- feedback. Truly, this is how we get better, move forward, and work together. In my last post, I talked about how we planned to respond to the community and about our goal to communicate more about our module contributions and product work. So I'm here to fulfill that promise.

Danielle Sheffler
#Drupal | Posted

It's been about three months since I joined Phase2 as Community Manager, and I have really appreciated getting to know the needs of the community around Phase2's products and contributed modules. Thank you so much to those of you who have offered your honest -- and at times colorful! -- feedback. Truly, this is how we get better, move forward, and work together. In my last post, I talked about how we planned to respond to the community and about our goal to communicate more about our module contributions and product work. So I'm here to fulfill that promise. Here's what we've been working on:

1. Collaborative module maintenance: We have recently increased the number of module maintenance jams where our developers sit together and work on the modules we maintain. This helps our newer team members learn the modules, and gives our team the chance to bounce ideas around and come up with the best solutions. We are continuing to contribute code that the community will benefit from and, in turn, are reviewing code that the community has contributed back to our modules. (Thank you for those contributions, by the way!)

2. Straight up increase of module maintenance hours: The entire development team has been working on reviewing and committing patches and responding to issues in the issue queue. In the past month and a half, we have spent over 300 hours on module maintenance. We have released new versions of 11 modules and a new version of 3 of our products:

  • Akamai
  • Embeddables
  • Entity Boxes
  • Features
  • Open Atrium
  • OpenPublic
  • OpenPublish
  • OpenCalais
  • Rubik
  • Static 404
  • Strongarm
  • Test Content Flag
  • Video Embed Field
  • Views Boxes

 

In the past month, the team has also worked on the following 15 modules:

  • Boxes
  • Context
  • Context Field
  • Context HTTP
  • Default Content
  • Feeds
  • Google Analytics Statistics
  • Node Connect
  • Persistent URL
  • Services
  • Static 404
  • Tao
  • Twitter Pull
  • Views Arguments Extra
  • WYSWIYG Tools Plus
  •  

    We are always looking for code and documentation contributions from our community. Code contributions are best submitted in the form of patches in the module issue queue. 

    3. Increasing Documentation: We've started with adding more documentation to the products themselves, and are continuing with more documentation around the modules. If you have suggestions for changes to the documentation on the module project page, please send me an email at dsheffler@phase2technology.com. For changes to additional module documentation, please click on the "Read Documentation" link under Resources on the right side of the module project project page. Anyone with a drupal.org account may edit this documentation.

    Check back as we continue to provide updates of our module maintenance progress in the upcoming months! We look forward to seeing your contributions!

 

Danielle Sheffler