I’m going to start a bit of a challenge for myself; I’ll be contributing to WordPress core for an hour a week in the next 10 weeks. I’ve never done it before but i’m done trying to find excuses to not contribute to an open source project I use every day. If anybody wants to join me in this noble quest, your more then welcome! I’ll be posting my findings on this blog.
How to contribute?
So last week was WordCamp Europe. At contributor day loads of WordPress developers, designers and other volunteers gathered to contribute to WordPress, BuddyPress and GlotPress. Now apart from a few plugins, a few english-to-dutch translated lines in WordPress 3.6 and supporting people in the forums I really haven’t contributed anything, so my goal at contributor day was quite simple; learn how to contribute.
Luckily WordPress core-developers Andrew Nacin and Mike Schroder explained the steps required to contribute and what they’d like to see from contributions. I was expecting a guide on how to submit patches, but they where very clear that just testing patches from other contributors and giving it an ‘okay’ was one of the best ways you could start; it saves the more experienced contributors a lot of time and it’s a great way to get to know WordPress trac. So that’s what I’ll be doing at least in my first week.
I’m starting this thursday and making it a rule to contribute at least one hour every thursday evening. I’m curious to see if anybody’s willing to join me? If so there’s two things you are going to need:
1. A WordPress.org account
To get intro participating in WordPress Trac, you’ll need to signup. No big deal
2. The WordPress contributor handbook
Everything you need to know to get started is in here, go check it out.
Leave a note in the comments so we can stay in touch during this period and swap stories / blogposts 🙂