Our Issue Queue Philosophy

We’ve heard many questions since our acquisition of Open Atrium. Amongst other things, the acquisition means we have a great responsibility to maintain and innovate on its Feature stack.

Frank Febbraro, Chief Technology Officer
#Drupal | Posted

We’ve heard many questions since our acquisition of Open Atrium. Amongst other things, the acquisition means we have a great responsibility to maintain and innovate on its Feature stack. We also know that many developers (including ourselves) rely heavily on these foundational elements for building innovative Drupal sites, which is why our developers at Phase2 have already have been tackling a variety of issues that had been submitted in the various module’s issues queues. Moving forward, we want to be transparent about how we’re addressing the issue queue so developers (and others) who’ve submitted issues and/or patches will know how we’re addressing the to-do list. We want to tap into the expertise of the community to prioritize and plan new features, as well, so here’s how we’re approaching each aspect:

  • Security issues first. Period. ‘Nuff said.
  • We’re prioritizing patches. By vetting the patches already created by developers who are trying to fix a known gap, we’re more likely to arrive at a workable solution quickly and efficiently. We also want to show folks how much we appreciate actually putting the time in to debug a problem and arrive at a potential solution.
  • We’re addressing issues with leg work put in. As these prioritized patches are increasingly resolved, we’ll start folding in issue requests that might not have an accompanying patch, but folks have put in a significant amount of debugging and sleuthing to determine what the problems might be.
  • We’ll be digging further into critical issues. Related to 2. above, we’ll be reviewing your patches, asking questions, and providing feedback necessary to reach commit-level solutions. We’ll also be reviewing critical issues to determine if they really are critical, how vital they are, and then we’ll prioritize them accordingly.
  • We’ll be forthright. We’ll do our very best to be up-front about our line of thinking in both fixing known issues and prioritizing feature requests. And although we may not always see eye-to-eye, we will always work to have an open, pragmatic, and completely respectful dialogue with you.
  • We’re being proactive and responsive. Whenever we’re actively working with you directly on a patch or feature, we’ll keep the dialogue going without radio silence. Even if we’re stumped, we’ll loop in another brain to pick up the challenge and keep the conversation going with you.

We know that this might be common sense to many of you actively working on contrib or core, but we wanted to let everyone know we’ll be doing our best in our expanded role of module and distribution management. We’ve been a part of the Drupal community for a long time, and we know tons of smart people are regularly contributing to it — and to Open Atrium. So we’re excited to be a part of facilitating solid extensions and new innovative features to this distribution and working with its most active users. It might take us some time to get fully up to speed, so we truly appreciate your patience as we work to integrate this incredible distribution and essential module set into our organizational culture. We hope you’ll find that we’re jumping in feet-first and making Open Atrium and it’s platform even stronger, and we encourage you to collaborate with us to make that happen.

 

Frank Febbraro

Frank Febbraro

Chief Technology Officer