This weekend in Seattle I met up with a few folks to talk about some larger documentation team issues which have come to light as a result of a tumultuous year for me personally, which caused me to withdraw from the community and my role as doc team lead. I realize that as the Drupal community has grown and changed, we have outgrown a model where one person alone can coordinate such a huge area as documentation. I asked several people, who had stepped in to fill leadership gaps and contacted me about general leadership concerns, to help me come up with a better plan for a sustainable doc team organization.
Based on various discussions over the last year, it seems that part of the solution involves improving the channels for communication and another part involves sharing leadership with as many people as possible. I feel that these changes will not only help us get docs back on track, but will make the documentation team stronger and more flexible as we head on down the road.
In the past, this group page (http://groups.drupal.org/documentation-team) was for announcements only. It's now open so that you can join, start discussions, and post events, and it will be the central clearinghouse for news and discussions about the documentation effort. This will make getting involved more discoverable and let us integrate our work with other groups in the Drupal community through cross-posting. Please note that this group only replaces the mailing list and not the documentation issue queue. The RSS feed for this group is http://groups.drupal.org/node/14492/feed
To avoid overlapping channels of communication, the documentation mailing list has been closed.
Roles and responsibilities
As the documentation has grown in size and complexity, more people are needed to coordinate and facilitate documentation activities. In addition to myself, who will continue as the overall documentation coordinator, the following people have volunteered to help with specific areas:
- Issue queue farmer and handbook content/editing coordinator: Ariane Khachatourians (arianek)
- Handbook structure coordinator: Lee Hunter (LeeHunter)
- API and core documentation coordinator: Jennifer Hodgdon (jhodgdon)
This information and a documentation team overview has been added to the handbook on the Documentation team page. There's still a need for more people to take on coordination roles, especially in various content areas. If you have a passion and/or expertise in a particular part of the documentation and you'd like to help make sure that it's current and complete, please contact me or one of the above coordinators directly.
The coordinators' role involves several activities:
- Identifying gaps and troubleshooting problems
- Acting as a resource for people with questions and concerns
- Helping new folks get up to speed and involved
It's important to note that the coordinator role is not a gatekeeper or taskmaster, it is a resource. As always, everyone is encouraged to jump in anywhere and any time you see an opportunity to improve the documentation. What's new is that we now have people who will make themselves available to provide feedback and guidance where needed.
Questions, comments or suggestions? Let's discuss it here!