Nov 09 2015
Nov 09

(Stretching the definition of "core" a bit here, but this is important to Drupal 8, so hopefully this is ok. :))

Now that Drupal 8.0.0 is nearing its final release, the next task in front of the Drupal community is porting ALL the contributed projects! Luckily, this effort is very much underway, but the faster the majority of big modules are at least usable (ideally with stable releases), the faster Drupal 8 adoption will take off.

After talking to numerous project maintainers, including those with multiple Drupal 8 core commits, it seems like many would find value in having dedicated times during which to collaborate with other people porting projects to D8, get questions answered, get advice on sticky problems, and figure out where best to help.

If you'd like to help mentor these sorts of office hours, please add your name to the issue summary at and fill in the Doodle.


Mar 16 2012
Mar 16

Thanks to everyone who voted on ideas! Based on that, as well as a few conversations with some key infrastructure maintainers, here's a draft of the proposal for the board meeting next week, for your review!

How the Drupal Association is going to make rock for developers and site builders

In December 2011, the Drupal Association board held a two-day retreat to decide its strategic priorities for 2012. Two of the six priorities identified by the board were “Improve the collaboration tools on and make it rock for developers” and “Make awesome for site builders.” (Of course, this also means an un-specified third priority of “Make  awesome for businesses” so they can help us pay for this. :))

Board members Angela Byron () and Donna Benjamin () embarked on some initial brainstorming and research:

  1. Interviews were conducted with members of’s infrastructure and webmasters teams to determine their priorities (since that’s what keeps the plumbing running).
  2. Drupal Association Executive Director Jacob Redding () was consulted regarding sponsors’ needs (since that’s what *pays* for the plumbing :)).
  3. And finally, a public voting site was put up at  to get community feedback on the roadmap. (Huge thanks to  for ENORMOUS help in gathering up and organizing an initial list of ideas to populate the site).

Through this process, we’ve developed the following plan for improving in 2012 that helps fulfill the needs of these distinct groups. And we will need your help to make it happen!

The Drupal Association wants to hire a development team to focus full-time on, supplemented by subject matter expert consultants where appropriate. We’ll start small (just reallocating existing staff to focusing 100% on and work our way up from there, based on fundraising success.

Here’s the short version of what we plan for that team to work on:

Site builder improvements

  1. Add ratings and reviews to projects, as well as other metrics, in order to help determine module quality and aid in comparing modules to one another.
  2. Create a dedicated support section on in “question and answer” format, to help users get useful help faster.
  1. Improve the case studies page
  2. Revamped events section on  to find user groups and camps in your area.

Developer improvements

  1. Back-link commit messages on issues, to show a full history of code changes within the context of a discussion about the change, as well as a better way to catch bugs.
  2. Improvements to the “Follow” functionality on to make it more usable, and provide additional details such as who is following an issue.
  3. Turn project pages into groups to do per-project documentation, events, announcements, etc.
  4. Drupal 7-based development tools, leveraging modern modules/practices that folks are already using on their “normal” Drupal projects (Entity API, Rules, Organic Groups, etc.), which are much easier to extend.

Business improvements

  1. Improved hosting page
  2. Revamped marketplace
  3. Revamped jobs section
  4. running Drupal 7, with responsive, mobile, HTML5 theme.

In the past, the Drupal Association has made improvements to “big bang” style: pick a near-impossible sounding goal, spend a bunch of money on hiring the community members who know the most about those things, and get ‘er done. We’ve had some huge successes going this route—the redesign and the CVS to Git migration—but this approach also has some major flaws:

  1. These are short-term gigs, which means the Drupal Association is paying contractor rates for the work
  2. When the money runs out (with a few very notable exceptions), the leaders of these initiatives tend to prioritize other things and their contributions to are reduced.
  3. The Drupal Association is left with little institutional knowledge of how various pieces of work and fit together. The knowledge is instead .

Going forward, we want to change how we spend our money on, by building an internal team within the Drupal Association to work on full-time, supplemented by subject matter experts where appropriate. They will attack both big problems and quick wins, as well as support community volunteers who wish to scratch their own itches.

The team, as we envision it, breaks down like this:

Q1 2012:

  1. Volunteer Coordinator / Project Manager
  2. Senior Architect
  3. Junior Developer

Q2-Q3 2012:

  1. Add:
  1. Additional Junior Developer
  2. Allocate funds for 1-2 contractors

Q4 2012:

  1. Add:
  1. Design/UX lead?
  2. DevOps Engineer?
  3. Additional development/contractor resources?

As you can see, this is not a huge team, and it’s going to take time (and funding) to get it up to speed. This means two things:

  1. The more we can fundraise and the earlier/faster we can fundraise, the faster we can hire folks and get rolling on the big things we want to tackle.
  2. Regardless of how fast we can fundraise and hire, we will need the community’s help in resolving these critical issues. Not even the smartest crew of 2-6 people can cover all of the bases on a site as diverse as


  1. #xx = Placement in top 100 in community voting; a lower number is more important.
  2. SB = Site Builder
  3. D = Developer
  4. B = Business

Q1 2012

  1. Bootstrapping: Hiring interns, winding down Neil Drumm’s work on DA priorities so he can focus 100% on community stuff, setting up basic project management processes (issue tags, documentation, reporting, etc.).
  2. Low-hanging fruit: Analyze list of community priorities, identify items that are fairly straightforward and/or already have significant community momentum, and get them finished/deployed as fast as possible. Possible candidates:
  1. #5 - Better showcase of Drupal websites on [B, SB]
  2. #7 - Check for duplicates when posting nodes [D, SB]
  3. #9 - Show user pictures on [B, D]
  4. #21 - Move to new design [B]
  5. Fix broken usage graphs [B, D, SB]
  6. (Sort of #1) Download counts on projects [B, D, SB]
  7. #18 - Improve usability of Follow button
  1. Office hours: Establish “ office hours”: a weekly time when community members can get updated on what’s happening, and those scratching their own itches can get dedicated help from DA resources for reviews, deployment scheduling, etc.

Q2 2012

  1. #2 - to D7 upgrade [D]: Set up dev/staging infrastructure, hold sprint in April with key infrastructure team members to develop crowd-sourceable roadmap and get as much done as possible, bring on key contractor resources and continue working throughout quarter at least 50% of the time on this.
  1. Other things that we could (don’t necessarily have to) couple with this upgrade include:
  1. #4 - Responsive, mobile-friendly HTML5 theme [B, SB, D]
  2. #20 - Enable group functionality for projects [D, SB]
  3. #29 - Full staging environment for [D]
  4. Project* revamp on modern tools [D, SB]
  1. Completely redesigned and improved user experience for collaborating in the issue queues:
  1. better workflow and UI for participating in individual issues
  2. activity stream for individual issues interweaving comments, commits, edits to the summary, etc.
  3. tracking of related issues
  4. tools for organizing larger initiatives
  1. Separate content types for the different types of projects (modules, themes, distributions, apps) that are optimized (with custom fields, UI, etc) for each sort of contribution.  I.e. the “projectness” is a field that you can apply to different node types.
  2. More long-term flexibilty and simplicity by using the Field API for all of our collaboration tools, making them easier to extend and expand in the future.
  1. Plan for Testbot??
  1. TODO after BoF at DrupalCon
  1. Medium-hanging fruit: Pick the next round of improvements once the easier ones are taken care of. Possible candidates:
  1. #1 - Project ratings and reviews [SB, D, B]
  2. #3 - Back-link commits in related issues [D]
  3. #6 - Improved support tools on [SB, D]
  4. #19 - Make events on amazing [B, SB, D]
  5. #36 - Better marketplace for companies [B]
  6. #16 - Dedicated jobs board on [B, SB, D]
  1. Continue incorporating community-driven improvements.

Q3 2012

  1. #2 - to D7 upgrade [D]: Complete the port by DrupalCon Munich. Almost 80% of time gets allocated to this.
  2. Continue work on the “bigger” medium-hanging fruit as needed:
  1. #1 - Project ratings and reviews [SB, D, B]
  2. #3 - Back-link commits in related issues [D]
  3. #6 - Improved support tools on [SB, D]
  1. Continue incorporating community-driven improvements.

Q4 2012

  1. Re-assess community priorities again to see where things are at, and develop plan/staffing accordingly
  2. Finish up other “top 10” stuff that’s still hanging out (e.g. “advanced” things outside of staff’s current skillset, things that are better off waiting until after D7 upgrade, and/or particularly contentious community issues). Possible candidates (I can’t stress enough that these things are not necessarily going to happen [through DA-driven initiatives, at least]):
  1. #8 - Automated Performance testing [D]
  2. #10 - Donations for project maintainers [B, D]
  3. #11 - Reputation/Badges system [D]
  4. #14 / #27 - Better Git collaboration tools [D]
  5. #39 - Topic pages [D, SB]
  1. Continue incorporating community-driven improvements.

It’s only natural that with 80+ ideas submitted (not to mention all of those floating around that haven’t been written down or even thought of yet!) there are going to be some folks disappointed that their pet project isn’t on this list (yet!), or that other itches are being scratched before it. Since there’s so much out there, we really tried to focus staff time on things only the DA could do.

However, fear not! You can make changes to yourself, too! In fact, thanks to the voting site, you have a list of people who also want to see your thing happen. Get in touch with them, form up a team, , and start crankin’!

The Drupal Association will be holding “ office hours” every Monday at 11:00 - 12:00 PT  to support volunteers working on their own community initiatives. This is guaranteed, set-aside time for volunteers to get ahold of someone who can answer any questions you have about development, perform reviews of your work, and get RTBC improvements signed-off on and scheduled for deployment. We’ll use that feedback, balancing with the other priorities of the moment, to populate the  that we’re going to work on.

Hope to see you there! We can’t do this without your help! :)

Mar 01 2012
Mar 01

Two of the Drupal Association's 2012 priorities are to make awesome: both for site builders and for developers. We want to hear from you about what improvements you'd most like to see on

Please let us know your thoughts at You can propose new ideas, vote on existing ideas, and also leave comments. When we have the more discrete list of things we plan to cover in 2012 and when, we'll share it with the community for feedback.

Important things to note:

  1. Please don't limit yourself only to big things. The more high-impact, "low hanging fruit" we can fix, the better! :) All suggestions must have a correlating URL on * with more information.
  2. Voting on an idea here does **not** necessarily mean it will get implemented, even if it's one of the highest (or even *the* highest) thing in the list. We are using this tool as a barometer to find out more about what our contributor community thinks is important, so we can factor this into our prioritization process.
  3. That prioritization process will include needs of the Drupal Association itself (e.g. DrupalCon & membership-related tasks so we can perform our other necessary functions), the needs of the infrastructure team (keeps the servers humming), and the needs of the DA's sponsors (keeps the money flowing so we can fund more improvements!).
  4. Unfortunately, no, this is not a Drupal site. If this fact appalls you, there is an idea in there that you can up-vote. :) It does allow data export capabilities though, so yay!

HUGE kudos to tvn for a tremendous amount of research on existing ideas that are out there, and jredding and kattekrab for several hours of brainstorming. :)

Jan 19 2012
Jan 19


2012-01-18 22:30 - 2012-01-26 00:00 UTC


In case you missed the announcement on Drupal Planet, Drupal Association 2012 elections are on! We're currently accepting nominations from now until January 26 at 00:00 UTC. If you're interested in being part of the Drupal Association leadership and helping to represent your fellow community members, please apply!

Nominees will be vetted publicly starting January 26, with voting finishing up February 7. Stay tuned for further announcements, and hope to see your nomination in the list. :)

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web