18 Comments


  1. Jeff- This is a great post and congrats on getting recognized as a contributor.

    As someone who wants to contribute to core and has submitted some patches that are not really going anywhere, I would love a mentor program for this. The contributors workshop I went to at WordCamp Orlando this year got me started and was awesome, but there is only so much one can learn in a few hours at WordCamp.


    1. Thanks Josh. It was great that I was able to quickly make a patch and have it be part of core but I know a lot of people who’s experience has been to contribute a patch to core but not have it be tested or go anywhere. I can understand how an experience like that can be demoralizing.

      I too was mentored in person at the contributor day at WordCamp San Francisco 2013 where I created my first ever ticket on Trac. I need to have my hand held and go through the process just a few more times before I can get comfortable regularly contributing to WordPress through Trac with easy fixes.


      1. Core trac wasn’t too much of an issue for me after being on the theme review team for awhile and working with theme trac. The through introduction to core tickets Nacin and Marc Jaquith gave at WC Orlando helped too.

        I should say that for my first patch and my revisions of that patch ( for this ticket BTW- http://core.trac.wordpress.org/ticket/25351), Otto was super helpful walking me through what needed to be done. Know I don’t know what to do to get it tested beyond my basic testing and get attention of admins that the issue is fixed. I feel like that second half of the process is what I still need help with.


      2. Yeah, generally it’s up to the patcher to step up, create the ticket, attach the patch and then perform testing, Get others to test and then share your findings and test results within the ticket. That’s how people are encouraged to get the change they want into core.

        However, at the end of the day, a patch can have everything going for it and be denied core because it goes outside of the softwares scope.


  2. I think it’s cool that you contributed, no matter how small. Participation is the key to harmony. Good for you, congrats!


    1. Thank you. As I said, I learned that no contribution is too small.


  3. I should add this to my new year’s resolution: contribute to WordPress projects.


    1. As I’ve demonstrated, it’s incredibly easy to contribute to WordPress. Of course, contributing to WordPress does not always involve code.

  4. Nikhil Vimal

    Great job contributing to core! WordPress core is great like that, anyone (Designers, Developers, etc.) can contribute to many different parts of the core.

  5. Prasad Deshmukh

    First of all, Congratulations!!! Great article. You have really demystified the process of contribution to WordPress core.


  6. Congrats! My first contribution wasn’t even user facing, it was a change in an inline comment, and that’s what got me started.

  7. Evan Herman

    Congratulations! I worked on a few bugs with the 2014 theme, but name didn’t make it on the contributor list. My patch wasn’t selected, but it did help in solving a problem. Rock on Jeff!

    1. Evan Herman

      I have also made contributions to the Codex that went un-noticed… but then again I don’t do it for the recognition!


  8. Jeff, you really made my day! This is so inspiring! I’ve often looked into “Trac” – just now because of changes in 3.8 that affected some plugins I did for my projects. I have to admit: I thought that working on core was reserved only for the “high priests and priestesses” of WordPress :-). I agree with a commenter above: I make it a 2014 resolution to look into core and see what I can contribute.


  9. Hi Jeff,
    First of all I would like to congratulate you for this recognition. I love open source products, using wordpress from last two years and want to contribute to it like you did. Currently learning PHP so that I can contribute.


  10. Thanks Jeff — your post inspired my to actually log my own bug (see http://core.trac.wordpress.org/ticket/26748). Was just wondering if it usually takes a long time before a ticket is reviewed/accepted? I’ve heard reports it could take months.
    Did your bug go through faster because Konstantin knew about it (since he helped you logging it)?


  11. Great job you have done Jeff! All the best for future success.

Comments are closed.