2015 Contributor Survey

Hi coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team folks! Thanks for all your hard work and contributions in 2015. Could you contribute few more minutes to fill in the 2015 contributor survey? It will help us establish some baselines around the contributor experience so that we can see how things change over time.

**This is being posted to all the Make teams, so if you subscribe to a bunch of p2s and keep seeing this post, know that you only need to fill the survey in once, not once per team.**

The survey is anonymous (so you can be extra honest), all questions are optional (so you can skip any that you don’t want to answer), and we’ll post some aggregate results by the end of January. It took testers 5-10 minutes to complete on average (depends how much you have to say), so I bet you could knock it out right after you read this post! 🙂

There are two sections of the survey. The first has questions about team involvement, recognition, and event involvement, and is pretty much what you’d expect from an annual survey (which teams did you contribute to, how happy are you as a contributor, etc).

The second section is about demographics so we can take a stab at assessing how diverse our contributor base is. All questions are optional, but the more information we have the better we can figure out what we need to improve. If there’s some information you’d rather not identify, that’s okay, but please do not provide false information or use the form to make jokes — just skip those questions.

The survey will be open until January 15, 2016. Whether you have 5 minutes now, or 10 over lunch (or whenever), please take the 2015 contributor survey. Thanks!

#annual-survey, #contributors

Updated Credits

Each release cycle, we try to recognize those core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. who’ve made the greatest impact, ramped up the quickest, and/or been the most reliable.

In the Contributing Developers categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., mainstays Sergey Biryukov, Dominik Schilling (Ocean90), and Cristi Burcă (Scribu) are joined by Aaron Campbell and Helen Hou-Sandi. Aaron has been contributing for several years, but his work this cycle on improvements to custom headers stood out. Helen, who was a Recent Rockstar in 3.3, stepped up with improvements to the theme screen, UIUI User interface/CSSCSS Cascading Style Sheets. fixes, and general helpfulness as fixes of all sorts were made through the later stages of the cycle.

The Recent Rockstars section is mainly aimed at recognizing newer contributors and/or contributors who’ve been around for awhile casually but have recently increased their involvement. In this category, Amy Hendrix worked (with Aaron Campbell) on the improvements to custom headers with great success. George Stephanis worked on css and improving the mobile experience. Stas Sușkov contributed to the thinking behind HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. captions, a feature that has been waiting patiently on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for years. Max Cutler and Marko Heijnen both worked on updating aspects of XML-RPC, and Kurt Payne contributed to dozens of tickets including the refactoring of adminadmin (and super admin)-ajax.php.

Thank you all for your increased efforts, and congratulations on having your picture in the credits!

#3-4, #contributors, #credits

Organizing Our Contributor Groups

Hi there, core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. (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 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved., 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 P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. 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 IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. 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 meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. 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

Contributors are no longer shown a bunch …

Contributors are no longer shown a bunch of things that they can’t use, and Contributors/Authors don’t see delete checkboxes or edit links for posts they can’t delete/edit (poka-yoke).

#contributors, #poka-yoke, #ui