Mike Schroder, known as Shredder to most of his colleagues, is a cross-cultural kid, coffee-drinking sailor, and lover of Open Source. He currently works at DreamHost, contributing to the WordPress core and community projects including wp-cli. You can find him blogging on various geeky things at http://www.getsource.net
This liveblog is all about core contributions to WordPress.
Mike works at Dreamhost and Dreamhost donates some of Mike’s time to work on WordPress core
Let’s start with the basics….let’s look at the Credits section of WordPress.
the project leaders usually meet yearly to discuss WordPress.
Project Leaders and Core Developers are all part of the “core team” and have commit access
Contributors are allowed to be in the Recent Rockstars once
The most important page….the exhaustive list of all the contributors.
I noticed how much changed between WordPress 3.5 and WordPress 3.6 .. the difference in contributors is massive, almost double.
It’s so cool to work on software that runs on over 60MM websites around the world
“How do we get on this list [of contributors]?”
Which Contributor Group do you belong to?
* Theme Review Time
* Plugin Review Team
* Core code
* UI/UX Group
* .org Systems
* Mobile applications
the forums is entirely* volunteer driven
the forums is entirely* volunteer driven (Some people get their time “donated” towards the project)
[Mike talks about IRC]
[Talks about #wordpress-contribute on the Freenode IRC network to talk about WordPress core]
Mike talks about the Teamwork and types of groups that help make up the core teams.
Beta: Features are finished.
[Aaron Campbell: “..not this time…”]
Even during Beta, lots of UI that goes into it. When we hit RC, patches and regression, this is held pretty tightly.
All patches that get in during RC, it has to get two project lead approvals before getting in.
There are often some small tasks sitting around that you could work on to get started with contributing.
Look for a Need because a ticket marked with that, it’s a needed feature that should be worked on.
“If it’s not on Trac, it doesn’t exist.”
“We are always happy for additional help, it’s never a bother”
When adding a patch to a ticket in Trac, make sure you say something. People subscribed to the ticket don’t get a notification that there was an update, until there’s a comment.
Sometimes even then, someone still doesn’t look at it.
[Grumpycat comes up because you may be grumpy if no one looks at it…keep trying]
Ask for help.
It’s ok to bug @nacin and ask for help. (except right now, he’s on honeymoon)
Iteration is key.
Let’s all work together to make a better WordPress.
andd that’s it!
[Mike opens it up for questions]
Audience: “do the Ideas get looked at on wordpress.org?”
Audience Jen Mylo and Mika: “…yes…wait..no….well, we don’t look at ideas that are 7 years old and have a bunch of old ratings”
Mike: “so….you really should be submitting ideas through Trac”
Audience: “can you give an example of a small project you worked on to start?”
Mike: “My very first patch was…hmmmm….[Aaron Campbell jumps in] .. he removed some un-used code…some 8-lines of code that were no longer used”
Mike: “Some of the best patches are removing things”
Mike: “fixing typos is great, and they usually get in very fast”
Mike: “Needs-refresh” patches are great too, great way to learn the process.”
that’s a wrap!