Looking for a lead

The Core Contributor Handbook is live here, and has a lot of great content from a number of contributors already:


What we’re looking for is someone to “own” the CCH and be responsible for:

  • Expanding and editing it, getting feedback from devs.
  • Walking people through it to get ideas on how to improve it (and get people involved with WP!).
  • Soliciting other contributors (don’t want a one-person show) and keeping an eye on all the changes.
  • Figure out a cool way to package and print the handbook.

Let me know if you’re interested in taking on this role, a comment on this post is fine.

This also reminds me — it would be great to be able to see a feed of changes on a site, like edits to a page. Anyone have a favorite plugin there?


Write a tutorial for setting up a local dev environment

A section of the core contributor handbook will be about how to set up a local test install, including a web server, Subversion, and WordPress. Because of the various operating systems and software packages out there, we’re going to need a few different tutorials.

I need some people willing to write up procedures for a number of standard setups. This includes:

  • WordPress on XAMPP (both Windows and Mac) MAMP, and MacPorts
  • TortoiseSVN and a tutorial on command-line Subversion usage, including co, up, revert, diff; patch; conflicts, etc.
  • Whatever you Linux guys use 🙂

I’d also love an article on getting the test suite up and running. Anything I’m missing?

So, for these procedures, people can volunteer (probably for their current setup). Once steps are written, others will need to test them. Many procedures may heavily borrow from or link to outside resources (such as the vendor sites themselves) — this is fine. And, there may already be some good things in the Codex or on other sites about getting WordPress running. Again, fine. (There are SVN articles by both @westi and @markjaquith, and those are probably great to start from.) Gather links, screenshots, further reading, whatever will help.

So, who is in?


A glossary for contributors

As part of the core contributor handbook, there’s going to be a glossary. Here’s what I’ve put together so far.

Something missing? Leave a comment. Feel free to also weigh in on new and existing definitions, examples, and the like.

a11y: Accessibility, or the act of ensuring that user interfaces are accessible for persons of all abilities and disabilities.

back compat: Backwards compatibility — a desire to ensure that plugins and themes do not break under new releases — is a driving philosophy of WordPress. While it is a commonly accepted software development practice to break compatibility in major releases, WordPress strives to avoid this at all costs. Any backwards incompatible change is carefully considered by the entire core development team and announced, with affected plugins often contacted. It should be noted that external libraries such as jQuery do have backwards incompatible changes between major releases, which is often going to be a greater concern for developers.

backport: A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.
Continue reading


What do core contributors need to know?

I’ll be working on an outline for the core contributor handbook in the coming weeks, so I figured I would start a brainstorming session here. Some potential questions to ask yourself:

  • What do core contributors need to know?
  • What would have been great to know when you first started getting involved?
  • What resources (such as pages on the Codex) have you found useful?
  • What do people (including/especially non-contributors) need to know about the development process/cycle/philosophies?

#3-org, #core-contributor-handbook