1) Improve collaboration tools on drupal.org and make it rock for devs

Collaboration tools on drupal.org including Git, the issue queue, development environments, project pages, etc. This objective is designed for developers that are using drupal.org to collaborate, build, and create new modules, themes, or working on Drupal core.

Objectives (Why are we doing this?)

We want drupal.org to be the place where Drupal developers come to collaborate. There is a concern that projects that use external sites such as github may fragment and separate the community. Drupal.org should be the home for all drupal.org developers and a place that they can be proud of.

Program

In 2012 we will work to define a drupal.org development team, which will focus on working with the community to free up blockers and prioritize, develop, and implement modifications to drupal.org to improve the user experience for contributors on drupal.org. A team to coordinate and assist with community contributions, comprised of paid staff augmented by a grant program and budget to hire community contributors. By correctly assigning priorities this team will also work to achieve our 2012 objective of making drupal.org awesome for site builders.

Priorities for the web development team

Background:

Currently if you would like to improve Drupal.org the process involves posting in the Webmaster's queue and then jumping in to get the work done.
You can start here: Webmasters queue
and learn how to get the work done here:
http://drupal.org/node/1018084

Learn more about the community's current processes here:
http://groups.drupal.org/node/180874

Community Initiatives
http://drupal.org/community-initiatives

Code review
http://groups.drupal.org/node/142489

Ideas (add yours!)

Idea #1 Program Coordinators
To complete the Drupal.org Git migration, the Drupal Association hired project managers to help organize and focus volunteer effort on the project. In 2012 we can hire more program coordinators/project managers to provide focus on specific efforts. These folks would not be developers but rather project managers that would assist developers.
Estimated Cost: 50K/yr

Idea #2 Formalize a Drupal.org Web Dev team
It has been suggested that the Association take a stronger leadership role on drupal.org and formally define a web development team - paid or unpaid. This team would include a senior developer, junior developer, designer/themer, and a project manager.
Estimated cost: 200-250K/yr

Idea #3 Funding through targeted grants
Currently the Association is using funds from T-Shirt sales to support specific initiatives on drupal.org. These are chosen by a committee chaired by Angela Byron.
Estimated cost: 100K (100% for grants, volunteer grant committee)

Idea #4 Fund the Prairie initiative
Use the prairie initiative to identify pain points on drupal.org and to create a plan to solve those pain points. The research from that initiative will serve as a basis for defining the future of d.o improvements.
Estimated cost: 50K/yr

Idea #5 Build a voting mechanism for Drupal.org improvements
Build a system wherein the community can nominate an improvement to drupal.org and through a community voting process the most requested improvements will become know. The Association with focus on implementing the most requested improvements.
Estimated cost: 5K (for mechanism) + 100K in funding

Idea #6 drupal.org committee
Define a committee that will decide what is funded
Estimated cost: 100K (in funding, volunteer committee)

Idea #7 Better Support Infrastructure
Move everything to support.drupal.org
Phase out Drupal.org support forums, and the support mailing list. (Only the support related ones, not all forums or mailing lists!)
Build an efficient Q&A-style interface.
Treat posts as long term resources, so they are referenceable and searchable.
Eliminate off-topic chatter and duplication.
Improve/add moderation. Moderation to be done by a team for support.drupal.org.

http://groups.drupal.org/node/133494

Idea #8 Better Support section
Move everything to support.drupal.org
Improve the Support landing page
Phase out Drupal.org support forums, and the support mailing list. (Only the support related ones, not all forums or mailing lists!)
http://drupal.org/node/1113574

Idea #9 Neil Drumm shared with Make d.o awesome for site builders
Neil's time is highly consumed with DrupalCon and other Association business. We can hire a junior developer to work on DrupalCon and a.d.o and put up to 80-95% of Neil's time directly on community initiatives.

He would concentrate on
- Freeing up the bottleneck of reviewing & deploying community contributions
- Help guide other contributions, concentrating on those that help developers, like project applications and tools for managing larger projects.
- Improve infrastructure to make these processes more straightforward

We can measure success by
- What is deployed and who in the community helped planning and development
- Dries's community survey

Idea #10 Create Case studies section
The goal of the showcase it to provide technical details and inspiration for large and complex Drupal sites. The ideas and issues are out there, and have gotten a lot of support from the community but not enough hands on it! All the links in the top section of this page are relevant: http://drupal.org/community-initiatives/drupalorg-content

Idea #11 Content Strategy
Hiring an experienced content strategist should be able to help shape an updated plan for the ways content on d.o. should be created and managed.
2nd section of http://drupal.org/community-initiatives/drupalorg-content