Editor Experience Survey

As you’re well aware, a project is underway with the focus on redesigning the editing experience in the wp-admin. As the project moves forward, a better understanding of how WordPress users actually feel about the editing experience is needed. Please take a few minutes to fill out this survey and help influence the future of your favorite CMS, WordPress.

Survey Link:

http://wordpressdotorg.polldaddy.com/s/editor-survey

+make.wordpress.org/design

 

#core-editor, #design, #survey

Howdy everyone There’s been a lot of discussion…

Howdy everyone! There’s been a lot of discussion over the last week or two around widgets for 3.8. Inspired by @lessbloat, I’ve made a short survey with a few basic questions about widgets and how you use them. It you could, please take a few minutes to share your thoughts:

Take the Widgets Survey

Thanks!

#3-8, #survey, #widgets

I’m doing some quick research into the wp…

I’m doing some quick research into the wp-admin dashboard (which I plan to look at for 3.8). I’d like to learn more about how you use the dashboard, and how you think it could be better. Please take a few moments and fill out this 5 question survey:

Take the survey

Thanks so much for your help!

#3-8, #dashboard, #survey

Team Reps

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!

#collaboration, #survey, #team-reps

Organizing Our Contributor Groups

Hi there, core contributors (and those who follow them). One of the things I’ve been meaning to do in the contributor community for the last 3-4 years is organize it so that when we say “contributor” it doesn’t just mean core code and the different contributing groups can all be on the same page. You may have seen some surveys sent/posted to the forums/docs/theme review teams etc. Your turn!

In order to create a closer relationship between all the contributor groups, ensure our policies and agendas don’t conflict, recognize outstanding contributors, and just generally level up, we need some organization. To wit:

  • I’d like to identify who the active contributors are in each group.
  • I’d like to appoint someone from each group (based on votes from the active group participants) as a group liaison to the rest of the WP project and any cross-team initiatives to improve communication.
  • I’d like to set up a central P2 for communicating project-wide things so that no contributor group ever has to hear important announcements after the fact and we can discuss any issues that come up that could use the help/attention of people from other groups (including core).
  • I’d like to try and set up a monthly IRC chat and/or Google hangout for the liaisons to have some real-time communication.
  • I’d like to organize an annual contributor summit. Similar to the core team meetup concept, but more inclusive.

The core code contributor team is the most in the know right now, but I’d like to make things a little more equal. Even within core, sometimes I hear people saying they wish they had more of a voice. The way the survey is set up, first you’ll pick how many reps you think core needs to have in the game (just one for core, or a couple, with each representing a different level of experience/seniority to make sure more issues/concerns are heard?), then you’ll vote on who you think the rep(s) should be. Note that inclusion in the survey does not mean that person has agreed to be a rep… I just pulled from our credits list and teams page for 3.4. Once the votes are in, I’ll contact people to see if they’re up for it.

The survey is at http://wordpressdotorg.polldaddy.com/s/core-contributors
and is password protected to help reduce spam responses: core2012

If you could fill it in before the weekend is over (or right now… it’s only a few multiple choice questions), that would be great.

Thanks!

#contributors, #survey

I’m doing a talk at Open Source bridge…

I’m doing a talk at Open Source bridge tomorrow/today on encouraging younger contributors. Can any/all contributors do me a favor and

so we can get an idea of the average age of our current contributors, and how old people were when they got bitten by the open source bug? Thanks much!

#survey