Team Reps

When we elected team reps last time around, the events contributor group didn’t exist yet. Groups that formed since the last elections had a 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. appointed for them until such time as there were enough group members to vote. You’ve made it, and it’s time to vote for your team reps!

There will be two event team reps. The hope for the role is that every six months when we vote, a new person will get tagged in to learn the responsibilities over the first half of the term, and then take over in the second half while the ‘elder’ steps back into the backup role. Rinse, wash, repeat. This way, we continually invest in the process of growing new community leaders. (This means please vote for two names, not just the same one twice.)

The team rep role is responsible for posting weekly updates to the team reps blog, and participating in team rep chats as needed. Note that this role is mostly administrative; it’s not a role that carries solo decision-making power. More detailed information about the team reps role is available after the jump.

More About Team Reps

Earlier this year, we took a stab at creating a structure for contributor group communication, based on identifying working groups and letting each group elect team reps. All the teams were represented at the community summit at the end of October, which was a huge step forward in recognizing contributors in areas other than coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. That said, once all the reps were together, one of the things we talked about was the idea of team reps, responsibilities, and expectations. As a result, its time for a bit of an update there.

Moving forward, each contributor group will have two team reps. We’ll have voting to choose team reps every six months. The idea is that one person will take the lead for the first half of the term with the other person acting as a backup rep, then about halfway through, they’ll swap roles. This way, there’s always someone ramping up with more responsibility, and someone who’s been there still around to lend a guiding hand, without anyone having to make too significant of a time commitment. If one new person takes on team rep responsibilities with each election, then it will be a constant cycle of mentoring people into more responsible roles, which is better for the project long-term than keeping all the responsibility in the hands of a few indefinitely.

It’s important to understand that “team rep” is a role that handles communication (namely contributor wrangling and posting weekly updates on the team’s activity and plans); it is not called “team lead” for a reason. While the people elected as team reps will generally come from the pool of folks that people think of as the experienced leaders, remember that the team rep role is designed to change hands regularly. For example, if in 6 months Ipstenu was ready to step back from being the support team rep, that would not reduce her leadership role on the support team, it would just mean she wasn’t responsible for team rep duties anymore.

The events team’s current rep is Andrea Middleton. I’d recommend keeping Andrea in one of the spots this time around and electing one new rep to learn the ropes from her. One thing to be sure of is that anyone you vote for is actually interested in having the team rep responsibilities until the next round of voting in June; this role has a time commitment attached to it, and if a team rep fails to meet that commitment (not posting the weekly updates, for example) they will be removed from the role. To that end, it would probably help for anyone who wants to be in the running to declare their interest in the comments.

Ready? Go vote for event team reps!

Voting closes December 15.