A few weeks ago I put up a survey for each of the contributor teams, with the goal of identifying a rep (or reps) for each contributing group. In most cases I lined up a primary rep and a backup. For core contributors it was a little different, because we have sub-groups within our group (which is also about 5 times larger than the next biggest contributor group, the theme reviewers).
In the survey for core contributors, I asked how many reps you thought core should get to ensure that each core contrib constituency would be represented. Choices ranged from 2 to 4, in varying configurations.¬ There was no overwhelming winner for this question. There were many votes for 4, 3, and 2, though some configurations had more votes than others. I removed the votes from people who have not actually contributed to core, but it was still a pretty even split. That said, across each of the configurations, the same people tending to be chosen for the 1 and 2 spots.
Based on the votes, I propose that the core team rep group be made up of Mark Jaquith, Andrew Nacin, Aaron Campbell, and Helen Hou-Sandi, with their backups being Ryan Boren, Daryl Koopersmith,¬ Cristi Burca (scribu), and¬ Mike Schroder (DH-Shredder) respectively.
The primary responsibility of being a rep will be participating in a monthly chat with other contributor group reps starting in May, and communicating things between that group and this one. Backup reps can attend the chat if they wish but are not obligated to do so, unless the primary rep says they can’t make it. Since the core team will have multiple reps, we can work out details later like who’ll post what where and how to get feedback from the people they’re meant to represent.
Thanks to everyone who participated!