Introduction to Contribution

  • Published on
    28-Jan-2015

  • View
    105

  • Download
    1

Embed Size (px)

DESCRIPTION

Introduction to Contribution talk from WordCamp Orange Country 2012. Walkthrough of how to get started with contributions to the WordPress project, common pitfalls, and suggestions to move forward. Presented by Mike Schroder (@GetSource/DH-Shredder)

Transcript

<ul><li> 1. Introduction to ContributionWordCamp Orange Country 2012Mike Schroder (DH-Shredder)@GetSource - http://www.getsource.net</li></ul> <p> 2. Who Am I? Mike Schroder, a.k.a DH-Shredder, a.k.a. @GetSource Third Culture Kid, enjoy Coffee &amp; Sailing WordPress Core and Plugin Contributor Happy DreamHost Employee 3. If you havent read ... http://codex.wordpress.org/Contributing_to_WordPress Andrew Nacins in-progress handbook: http://nacin.com/projects/core-contributor-handbook/ 4. Who Contributes? Theme Review Team Polyglots Plugin Review Team .org Systems Core Code Mobile Applications UI/UX Group Documentation Support Forums Accessibility 5. Im going to focus onCore Codecontribution. 6. Core Team? 7. Contributors. 8. Contributors. 9. OKAY.How can I get on this listof AWESOME? 10. Your First Contribution 11. Release Cycle http://wpdevel.wordpress.com foreach ($releases as $release) Planning Development Cycles/Sprints Beta RC 12. Planning:Choose the Scope. 13. Development Cycles: Teamwork. 14. Beta:No More Features. 15. Release Candidate: Just the Regressions. 16. Okay. I understand the release cycle. Whats next? 17. Start Small. 18. Look for a Need. 19. If its not on Trac, itdoesnt exist.-Pretty much the entire Core Team.http://core.trac.wordpress.org 20. Reports are your friend. http://core.trac.wordpress.org/report Next Major Release:http://core.trac.wordpress.org/report/6 Needs Patch:http://core.trac.wordpress.org/report/16 Has Patch, Needs Testing:http://core.trac.wordpress.org/report/13 View Tickets -&gt; Custom Query (i.e. needs-refresh) 21. Okay. I found a bug.Now What? Get the WordPress.org source from trunk. http://codex.wordpress.org/SVN svn co http://core.svn.wordpress.org/trunk/ https://github.com/WordPress/WordPress 22. Apply the Patch, if any. Right-click on patch download link, copy URL From root of trunk: wget http://core.trac.wordpress.org/raw-attachment/ticket/20000/20000.diff(or curl -OL http://core ...) patch -p0 &lt; 20000.diff 23. Now, create a patch. Create all patches from the WordPress root within yourtrunk checkout. svn diff &gt; bugNumber[.patchNumber].diff e.g. svn diff &gt; 20000.2.diff 24. Attach a patch. Attach it to the ticket. Add a note to the ticket, so that everyone ccd isnotified. 25. No one has responded. What now? 26. Bother the crowd. 27. Learn to love IRC.#wordpress-dev on FreeNode 28. Ask for help. 29. Ping those who arehandling your ticket! 30. Dont rely on wp-hackers. 31. Twitter is your friend. 32. Be prepared for rejection. 33. Iteration is key.Its okay if someone else has a better idea. 34. Lets work together tomake a better WordPress. 35. Any Questions? https://irclogs.wordpress.org/ http://lists.automattic.com/ http://core.trac.wordpress.org/ http://codex.wordpress.org/Contributing_to_WordPress http://nacin.com/projects/core-contributor-handbook/ http://aaron.jorb.in/blog/2010/03/commit-the-story-of-writing-a-wordpress-patch/ http://patcheswelcome.wordpress.com/Mike Schroder (DH-Shredder)@GetSource - http://www.getsource.net </p>