Decoding Core Contribution - WordCamp San Diego 2013
1 likeā¢816 views
Mike Schroder's presentation at WordCamp San Diego 2013 outlines how individuals can contribute to WordPress core development. He emphasizes starting small, finding a need, and utilizing resources like Trac for tracking progress, while also encouraging persistence and collaboration in the contributor community. The presentation includes links to official handbooks and resources for guidance on making contributions.
![Now, create a patch.
ā¢ Create all patches from the WordPress root within your
trunk checkout.
ā¢ svn diff > bugNumber[.patchNumber].diff
ā¢ e.g. svn diff > 20000.2.diff
ā¢ git diff --no-prefix master > 20000.2.diff](https://image.slidesharecdn.com/wcsd-2013-decoding-core-contribution-130612174345-phpapp02/85/Decoding-Core-Contribution-WordCamp-San-Diego-2013-30-320.jpg)
Decoding Core Contribution - WordCamp San Diego 2013
- 1. Decoding Core Contribution WordCamp San Diego 2013 Mike Schroder (DH-Shredder) @GetSource - http://www.getsource.net
- 2. Who Am I? ā¢ Mike Schroder, a.k.a DH-Shredder, a.k.a. @GetSource ā¢ Third culture kid, enjoy the art of Coffee & Sailing ā¢ WordPress 3.5 Recent Rockstar and wp-cli Contributor ā¢ WordPress Core Team Rep for 2012 ā¢ Happy DreamHost Employee
- 3. Core Team?
- 7. OKAY. How can I get on this list of AWESOME?
- 8. Everyone has something to contribute.
- 9. Which Contributor Group do you belong to?
- 10. Contributor Groups? ā¢ Docs ā¢ Support ā¢ Theme Review Team ā¢ Plugin Review Team ā¢ Events ā¢ Core Code ā¢ UI/UX Group ā¢ Accessibility ā¢ Polyglots ā¢ .org Systems ā¢ Mobile Applications ā¢ Community
- 13. Not sure where to go? Try #wordpress-contribute
- 14. Letās focus on Core Code contribution.
- 16. If you havenāt read ... ā¢ http://codex.wordpress.org/Contributing_to_WordPress ā¢ The official (always in progress) handbook! ā¢ http://make.wordpress.org/core/handbook/
- 17. Release Cycle ā¢ http://make.wordpress.org/core ā¢ foreach( $releases as $release ) ā¢ Planning ā¢ Feature Development ā¢ Beta ā¢ RC
- 21. Release Candidate: Just the Regressions.
- 22. Okay. I understand the release cycle. Whatās next?
- 23. Start Small.
- 24. Look for a Need.
- 25. āIf itās not on Trac, it doesnāt exist.ā -Pretty much the entire Core Team. http://core.trac.wordpress.org
- 26. 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 -> Custom Query (i.e. needs-refresh)
- 28. Okay. I found a need. 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 ā¢ git clone https://github.com/WordPress/WordPress.git
- 29. 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 < 20000.diff
- 30. Now, create a patch. ā¢ Create all patches from the WordPress root within your trunk checkout. ā¢ svn diff > bugNumber[.patchNumber].diff ā¢ e.g. svn diff > 20000.2.diff ā¢ git diff --no-prefix master > 20000.2.diff
- 31. Attach a patch. ā¢ Attach it to the ticket. ā¢ Add a note to the ticket, so that everyone ccād is notified.
- 32. No one has responded. What now?
- 35. Be Persistent!
- 36. Learn to love IRC. #wordpress-dev on FreeNode
- 37. Ask for help.
- 38. Ping those who are handling your ticket!
- 40. Twitter is your friend.
- 41. Be prepared for rejection.
- 42. Iteration is key. Itās okay if someone else has a better idea.
- 43. Letās work together to make a better WordPress.
- 44. Any Questions? ā¢ http://make.wordpress.org/ ā¢ https://irclogs.wordpress.org/ ā¢ http://make.wordpress.org/core/handbook ā¢ http://core.trac.wordpress.org/ ā¢ http://lists.automattic.com/ ā¢ http://codex.wordpress.org/Contributing_to_WordPress ā¢ 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