16 Comments

  1. Tammy Hart

    Everything you described as reasons you weren’t contributing are exactly my reasons, and I work for a world class WordPress Development company with like 20 other contributors and even a core committer (Helen). I wasn’t aware of the “good-first-bug” tag, though, so that gives me some hope that I might be able to try it out. It really helps to know I’m not alone in my fears; thanks for sharing your thoughts!

    Report

    • Jeffro

      Actually, I should be thanking you for helping to confirm I’m not crazy and that my fears are shared by someone else. The Good First Bug tag is only a week or two old. I don’t know if any tickets are actually tagged with that label just yet.

      There was also discussion on how a ticket or bug would qualify for that tag. Obviously, what’s an easy good first bug for someone will be difficult for someone else. However, I think the core devs will do a good job labeling bugs with that tag if they are specific, don’t touch a lot of components and are not deep into core.

      Report

  2. Kartoffel

    Contributing to WordPress would be so much easier if they moved away from Subversion/Trac over to Git/Github.

    Report

  3. Edward R. Jenkins

    Ditto. I too have been weary of contributing to core.

    Report

  4. Stephen

    I also saw a great new footnote on Trac this morning on #26849

    “Make sure evilpepe receives a warm welcome — it᾿s their first bug report!”

    Report

  5. trishasalas

    You’re not alone, I’ve had the same thoughts, feelings and perceived experiences. I’ve found a niche of sorts but it can still be intimidating. I don’t mind being new, nor do I mind writing bad code and having it criticized (I welcome it, in fact…how else to get better?) but I’ve found at times it’s easier to just back off than risk comments I don’t know how to interpret. +1 to needing a thick skin…I’m not quite there yet.

    Report

  6. The Weekly WordPress News, Tutorials & Resources Roundup No.55

    […] Why You Shouldn’t Be Worried About Screwing Up When Contributing To WordPress […]

    Report

  7. Mike Jordan

    So well-written Jeffr0. I’ve only recently been testing the waters of Trac and you’ve very accurately detailed my own first impressions and insecurities.

    I have never met a WordPress developer who did not want to contribute; it always comes down to either lack of time or not knowing how.

    The latter is something that can be fixed, however, and it’s great to see so many pros like Helen and Nacin making this a priority!

    Report

  8. Stephen

    FYI: As all the new Trac changes are also on bbPress & BuddyPress Tracs, the “good-first-bug” tag is also available, we’ll try to remember to add it and leave a few hanging around for new contributors.

    https://bbpress.trac.wordpress.org/query?status=!closed&keywords=~good-first-bug
    https://buddypress.trac.wordpress.org/query?status=!closed&keywords=~good-first-bug

    Report

  9. Macs and More Den Haag

    OK, I made my first comment in trac regarding the twitter api blowing up embedding.

    I chose for the status, “works for me” since that’s exactly what the patch did.
    Little did I know that closed the ticket??
    So yes, someone did get pissed off at me, but to hell with that! LOL
    Why does “works for me” close the ticket?

    Anyway Mr Nacin came along afterwards and did indeed close the ticket after a few bits of house keeping.

    Report

    • Stephen

      Maybe a link to an FAQ would have been helpful, should one be added you think?

      Basically all of those ‘status’ messages revolve around the details of what, why and where code will actually be merged into the main WordPress codebase, a ticket typically won’t be closed until the code is ‘committed’ into WordPress’ core codebase.

      I’m quite sure @ocean90 wasn’t pissed off at you, he was just trying to give a tip on what ‘worksforme’ actually means.

      Nacin only closed the ticket after the code had been ‘committed’ into the main codebase (See comments 10, 11 & 12) where you see eg “In 26967:” they link to actual code changes that were made.

      Here is that definition in full from the ‘Trac Handbook’

      http://make.wordpress.org/core/handbook/trac/

      “worksforme: The bug reported in the ticket cannot be reproduced. Sometimes, an existing plugin, hook, or feature may render the ticket moot, so the ticket can be closed without further action.”

      Hopefully this clears things up for you a little as to the context of that tickets ‘workflow’ and I’m quite sure no one there meant you any harm, and though it wasn’t explicitly added as a comment the ’19 watchers’ on that ticket most likely found your comment “the problem and this fix now works” helpful, as I know I did. :)

      Report

  10. The Weekly WordPress News, Tutorials & Resources Roundup No.56

    […] Why You Shouldn’t Be Worried About Screwing Up When Contributing To WordPress […]

    Report

  11. Paul

    Jeffro, can you please add a example trac query somewhere to the “good-first-bug” thing: https://core.trac.wordpress.org/query?keywords=~good-first-bug

    I think it will make it more easy to understand this keyword ;)

    Report

  12. Kakoma

    With an article this compelling, what am I waiting for to make my contribution? *runs off* *returns* Thanks Jeff! *runs off again*

    Report

Comments are closed.

%d bloggers like this: