New Docs Team Rep

The votes are in and the new docs 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. is Kim Parsell (@kpdesign)!

Congratulations Kim! I’m sure you’ll do a wonderful job of representing the docs team.

Kim will be taking over from @sewmyheadon next week.

#team-rep

Docs Team Rep Nominations

So far no one has nominated themselves for being the rep of the doc team. The responsibility of the rep is:

  • to report back on the Updates blog about what’s happening in the docs team
  • to write the weekly update on the docs blog about what’s going on
  • to read the updates blog and report back on anything that’s relevant to the docs team
  • to ask the group about any decisions that we need to make and report back to the rest of the project
  • to represent the docs team at any 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. meetings

I’ve created a survey – please nominate the person you wish to be team rep (it can be yourself) and we can go from there.

#team-rep

New Team Rep (also, do we need one?)

It’s time for someone else to take on the role of team rep! What is the 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.?

The team rep is responsible for posting weekly updates and liaising with the different teams, when necessary. Note that is not a leadership role (though someone who is leading a specific project can hold it).

We should also discuss the following:

  • is the team rep thing working out? Do we need one? Jen has asked us to reflect on this and report back on it. Please do share all of your opinions.
  • if we decide that yes, team reps are awesome, how shall we elect one? I can set up a poll if people want to vote. or people can suggest their names and we can discuss amongst ourselves who we think would be best.

Please keep discussion of this on the P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/., rather than having it solely in the IRC chat. This ensures that everyone who has a stake can participate.

#team-rep

Eric Amundson = Docs Team Rep

Am officially passing the baton of docs 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. from Drew and I, to @sewmyheadon.

#team-rep

Team Reps Proposal

The team reps have been asked to propose new team reps. As Support & Docs are really one mega-team we’re going to have one support person and one docs person. I’m going to recommend Eric Amundson a.k.a. @sewmyheadon. He’s been doing great work on the Theme Developer Handbook, he’s has been running doc sprints and documentation days under his own steam, and has generally been very involved and hard working.

Responsibilities.

  1. Posting weekly update – NOTE: Support and Docs will SHARE a post on Fridays. Each rep will be responsible for their half, but are expected to keep up to date with the other group.
  2. Representing the team in interactions with other teams
  3. Putting together the agenda for weekly meetings
  4. Moderating IRC weekly meetings
  5. Posting on make/docs the outcomes of meetings as needed.

In all cases, it’s fine for the rep to delegate to someone else when any of these cannot be met for whatever reason.

I’m currently unsure if the position is for 3 or 6 months. Soon we’ll know!

Please comment with your approval or if you want to nominate yourself or someone else, now’s the time to do it.

#team-rep

Team Reps

Siobhan McKeown and Drew Jaynes. Congrats! The term starts with the new year, so I’ll be in touch before then to make sure everyone is on the same page regarding expectations.

Here are the voters:

Please describe your role with the docs team.

  • 4 – I am an active member of the doc team, and contributed within the last 3 months
  • 3 – I have not yet contributed to docs, but I plan to start soon
  • 1 – I do not plan to contribute to docs
  • 0 – I didn’t contribute within the past three months, but I have been a docs contributor in the past

To which documentation efforts have you contributed?

  • 7 – Codex
  • 5 – Handbooks, to teach the public (users, theme developers, etc)
  • 3 – CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Help Tabs
  • 3 – Handbooks, to teach new contributors (core contrib hb, etc)
  • 0 – Other Option

8 people voted, so not a big increase since last time, which was one reason we merged docs with forums to create the support group earlier this year. Of note, Siobhan received enough votes in the support team vote to be a rep there as well, despite focusing on docs. The group vs project divisions are coming up in a few other areas as well, so when June rolls around, we may want to look at rearranging some of our groups based on activity and areas of focus. For now, though, docs remains separate.

#team-rep

Team Reps

Time to vote for docs team reps! You get to vote for 2 team reps. These folks will be responsible for reporting on the progress of the group to the other team reps via weekly updates, as well as occasional chats and such. If you haven’t seen the spiel on one of the other team blogs about how team reps/voting/terms work, the longer explanation is after the jump.

When we did voting last time around, the docs team (as reached through the wp-docs mailing list) had fewer responses than I could count on one hand, and most of the votes were for people already designated as support team reps, so we merged the groups until there was more of a cohesive action happening around docs. At the team reps summit just over a month ago, we agreed it was time to break docs back out, and tapped Siobhan McKeown as the acting rep for this team. She’s really taken the bull by the horns, and I’d recommend voting for Siobhan as one of the team reps so the current progress doesn’t lose any momentum.

Note: It should be folks who want the responsibility, but are not reps for another team. Anyone interested in being a docs 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. should leave a comment saying as much so people know who they can/should vote for. Voting is open until December 15, and results will be posted here once voting closes.

Go vote!

Continue reading

#team-rep

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!

#team-rep