At the Community Summit it was decided that…

At the Community Summit, it was decided that enough momentum has gathered behind the effort to grow our documentation for it to break off as a separate contributor group (vs being part of the support group as it was set up a while back). All of the contributor groups on the Make network will be voting on their team reps next month, but in the interim, we’ve appointed Siobhan McKeown to spearhead this effort based on her experience and enthusiasm, coupled with her excellent working relationship with the other contributor groups that will be involved in the documentation efforts.

The first task for this group is to identify who will be contributing to it. Introduce yourself in the comments!

The second task will be to come up with a proposed roadmap for documentation. This would include handbooks, the Codex, and even help tab text in WordPress itself.

The way we are structuring official contributor groups these days is with each group’s team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. posting updates on a weekly basis to the team rep updates. If any of the plans proposed by a group cause a red flag for another contributor group, all the team reps will discuss. If the team reps can’t come to agreement, Matt will be there to break the gridlock. Depending on how many contributors want to get involved here, it may make sense to break out subprojects and have specific people be responsible for them/leading subteams (like the Events group is doing, and the community outreach group will be doing as well). Any person should only be assigned to one thing, though… that’s something we are trying to be better about across the entire project.

Take it away, Siobhan!