It’s been… approximately forever since we even talked about team reps for the Community Team, but why should that stop us? 🙂
In the WordPress open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project, each team has one or two representatives. Folks who serve as “team 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.” are responsible for communicating on behalf of the group to the other contributor groups via weekly updates, as well as occasional chats and such. If you haven’t seen the explanation on one of the other team blogs about how team reps/voting/terms work, the longer explanation is below.
It’s been a long time since we held elections or posted our activity to the updates blog, and I think that rather than holding elections every 6 months for two reps, we should vote every year. I also think that we can let the two team reps decide on the best way for them to work together — either by trading off every couple of months, or sharing different parts of the job for the whole year.
If you would like to nominate someone (including yourself) to serve as Community team rep for 2017, please comment on this thread.
One thing to be sure of is that anyone you nominate/vote for is actually interested in having the team rep responsibilities for 2017. 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. We’ll keep nominations open for a week and then open a poll for voting on November 23. Voting will close on November 30.
Team Rep Voting Backstory and Detail
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 at some point James Huff was ready to step back from being the support team rep, that would not reduce his leadership role on the support team, it would just mean he wasn’t responsible for team rep duties anymore.
When we started this practice, the idea was for each contributor group to have two team reps and vote to choose team reps every six months. The original idea behind having two reps was 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. That 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.
This time around, I propose that we let the two team reps decide on the best way for them to work together — either by trading off every couple of months, or sharing different parts of the job for the whole year.
As mentioned above, we’ll keep nominations open for a week and then open a poll for voting on November 23. Voting will close on November 30.