I was there in #wordpress-sfd this morning, but no one else was. Last week I was unable to make the meeting but @trishasalas was able to step in in my stead to keep the band playing. There were a few things I wanted to talk about this week, so I’ll post them for discussion here. I should be at or around my desk for most of the day and/or week, so feel free to hit me on IRC or you can email or GTalk me at chris at jazzsequence dot com.
WordPress 3.8 is closer than you think
I’ve been monitoring the #wordpress-dev chatter and 3.8 is only a couple weeks away. Barring any horrible blockers, it will drop on the
18th meaning that 3.9 feature plugins need to be presentable immediately following the 3.8 release because they will start to be integrated into core at that point.
**If we want this to be included in WordPress 3.9, we need to have something to present.**
Not only presentable, it needs to be tested. There are some things — like accessibility or internationalization or backwards-compatibility concerns that wouldn’t necessarily be blockers for integrating into core, but we need to have our stuff together. Which means, if the
18th is when 3.8 drops, that should be our deadline for having the plugin done, ready to go and be tested by actual humans. If we can’t make that deadline this time around, we can continue to work on this for 4.0 (or whatever the release following 3.9 will be), but since developer resources have been our main weak point up to now, we’re going to need to do some serious recruiting.
So where are we?
I would like to start merging the stuff that @ninnypants has been working on into my repo so there’s a single repository that we’re using and go from there. Since I haven’t looked at his changes, or tested any of that stuff, I’d like for someone to let me know what the latest is on that front and whether we can start building on that. Also, I’m not sure how much time I’ll have to spare on that this week, so anyone’s help in this process and/or pull requests would be greatly appreciated.
Having a code name is something that was proposed over here that we haven’t ever had and thus far the meetings and p2 posts have been tagged with “admin help”. This is somewhat boring. @ubermaut suggested Lifebuoy. Help2 is another idea I just came up with (see, it’s squared — because some of our ideas came from how Squarespace handles help/documentation — and it can also be read as Help 2 — as in the second version of help…). Any other ideas are welcome. It seems a little late to be figuring this out now, but then, if we’re gearing for a 4.0 release, maybe having a code name will make us more distinctive and noticeable.
Last call for 3.9
If this week goes by with no real progress on the plugin, we should again expect this to be punted and focus on getting something ready for the next release of WordPress. It can be done if we are all able to make sprint to get it to happen, but if feature plugins are being merged into core as soon as 3.8 hits the virtual shelves, we’ll already have missed the boat.
If there are any other folks out there interested in helping make this feature a part of core, meetup organizers, folks who just want to start contributing to WordPress core, please hit me up and let me know in what way(s) you are able to help & I can get you up to speed. This could be done in a matter of hours at a hack day or some such thing if someone was inclined to start one up.
Thanks to everyone who has helped to get us this far. We’ll get there.