WordPress 3.5 mid-week Codex Sprint
This release cycle we’re lucky enough to know the date of the next release – 5th December! All of the core devs will be relaxing with beer, or sleeping, or recuperating in a rest home, and it will be time for us to pick up the slack and get the docs updated.
We had a discussion in chat and agreed that it would be a great idea to get together to plough through as many of the codex updates as possible. With inspiration from Mozilla’s Doc sprints, here’s how it’s going to work:
Start: Thursday 13th December – 3pm UTC
End: Friday 14th December – 5pm UTC
You can get involved at any point. Obviously I’m not planning to be there for 26 hours :), but I will be around as much as possible.
Come to the IRC chat on freenode – #wordpress-sfd or leave a message in the Codex Updates thread to say what you’d like to do. Myself or someone else will assign it to you. If you see someone already assigned then you know that is being taken care of (i.e. @JerrySarcastic is working his magic on the Media pages).
When it’s complete, let myself or another editor (like @DrewAPicture) know, and we’ll tick it off and note that you’ve done it.
The WordPress Support and Docs chatroom on IRC freenode. #wordpress-sfd
If you don’t have an IRC client, or ar unfamiliar with IRC, you can join the chat over the web here: http://webchat.freenode.net/?channels=wordpress-sfd (thanks @mrmist )
You don’t have to come to the chatroom. I’ll be monitoring the Codex Updates master list so just leave a message there if you want something assigned to you.
It sucks to be a user and to get confused because the docs are outdated. Let’s try to avoid that happening.
Because @nacin missed a Bob Dylan concert: https://twitter.com/nacin/status/271003759642034177
Also, because the Codex is important, and helping to update it is a great way to be involved with WordPress.
Any questions? I’ll try to have answers. Also, any suggestions on improvements to workflow or any other suggestions are always appreciated. This is the first time we’ll have done it in this way and if it works it’d be fantastic to do it for each WordPress release.