Last updated April 4, 2012.

Scope of Documentation Team responsibilities

The Documentation Team takes full responsibility for the following types of documentation:

The Documentation Team takes partial responsibility for the following types of documentation:

  • Community Documentation pages on and Communication and marketing pages on The Drupal Community as a whole writes and edits this documentation, and since it's open to anyone to add and edit pages, the Documentation Team cannot take direct responsibility for maintaining its accuracy. The Documentation Team does take responsibility for moderation (spam, inappropriate content), guidelines (style and structure), maintaining How to Contribute pages (instructing contributors on how to contribute), and infrastructure (tools for writing and navigating documentation).
  • Documentation embedded in and distributed with contributed modules and themes: The project maintainers are responsible for documenting their project. The Documentation Team takes responsibility for guidelines and infrastructure to facilitate writing, editing, and navigating this documentation.
  • Externally-hosted documentation (blog posts, etc.), some of which gets posted to Planet Drupal: The individual blog writers are responsible for the documentation they write. We hope in the future that the Documentation Team will maintain a directory of externally-hosted documentation, to assist the Drupal Community in searching and navigating this important source of information.

Documentation Team Leader responsibilities

Given the above scope of responsibilities of the Documentation Team, here are the responsibilities of the Documentation Team Leader(s):

  1. Recruit volunteers to write, edit, and moderate the documentation the Team is responsible for.
  2. Recruit volunteers to manage the documentation issue queues (triage new issues and review patches and new documentation; for the "documentation" component of the Drupal Core issue queue, the Documentation project issue queue, and the curated documentation issue queue if we get that going).
  3. Define priorities and projects for volunteers (writers, editors, mentors, etc.).
  4. Define and communicate the standards for writing documentation (in conjunction with the Drupal community as a whole).
  5. Communicate with the community about what's happening in the Documentation team, and how they can get involved.
  6. Manage the documentation infrastructure (coordinate adding new features to facilitate writing, displaying, navigating, and searching the various types of documentation).
  7. If we get the Curated Documentation going, that will require additional oversight and planning, such as making decisions on what should be included there as the official Drupal user guide and core documentation. A team will need to be organized for that.

A note on sprints and DrupalCons

In the past, there has been an implicit requirement that the Documentation Team Leader attend all/most DrupalCon events and host a Documentation Sprint on the Sprint day (usually the last day of DrupalCon). However, the main goal of the sprints has been to recruit new contributors to Documentation, but in reality, not many of the sprint participants have become long-term contributors. In 2011, the Documentation Team leaders organized several virtual longer-term "sprints" and "meta-issues" that were much more effective in defining tasks that energized volunteers and got them oriented towards longer-term contributions. So in keeping with the Leader responsibilities of recruiting volunteers and defining projects, this seems like a better use of Documentation Leader time and energy.

If Documentation Team leaders or others are attending DrupalCon and would like to host a Documentation sprint, the Documentation Sprint How-To page should be helpful in organizing it.