Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Introduction to Contribution WordCamp Orange Country 2012Mike Schroder (DH-Shredder)@GetSource - http://www.getsource.net
Who Am I?• Mike Schroder, a.k.a DH-Shredder, a.k.a. @GetSource• Third Culture Kid, enjoy Coffee & Sailing• WordPress...
If you haven’t read ...• http://codex.wordpress.org/Contributing_to_WordPress• Andrew Nacin’s in-progress handbook: ...
Who Contributes?• Theme Review Team • Polyglots• Plugin Review Team • .org Systems• Core Code • ...
I’m going to focus on Core Code contribution.
Core Team?
Contributors.
Contributors.
OKAY.How can I get on this list of AWESOME?
Your First Contribution
Release Cycle• http://wpdevel.wordpress.com• foreach ($releases as $release) • Planning • Development Cycles...
Planning:Choose the Scope.
Development Cycles: Teamwork.
Beta:No More Features.
Release Candidate: Just the Regressions.
Okay. I understand the release cycle. What’s next?
Start Small.
Look for a Need.
“If it’s not on Trac, it doesn’t exist.”-Pretty much the entire Core Team.http://core.trac.wordpress.org
Reports are your friend.• http://core.trac.wordpress.org/report• Next Major Release: http://core.trac.wordpress.org...
Okay. I found a bug. Now What?• Get the WordPress.org source from trunk.• http://codex.wordpress.org/SVN ...
Apply the Patch, if any.• Right-click on patch download link, copy URL• From root of trunk: • wget http://core.tr...
Now, create a patch.• Create all patches from the WordPress root within your trunk checkout. • svn diff > bugNum...
Attach a patch.• Attach it to the ticket.• Add a note to the ticket, so that everyone cc’d is notified.
No one has responded. What now?
Bother the crowd.
Learn to love IRC.#wordpress-dev on FreeNode
Ask for help.
Ping those who arehandling your ticket!
Don’t rely on wp-hackers.
Twitter is your friend.
Be prepared for rejection.
Iteration is key.It’s okay if someone else has a better idea.
Let’s work together tomake a better WordPress.
Any Questions? • https://irclogs.wordpress.org/ • http://lists.automattic.com/ • http://core.trac.wordpress...
Introduction to Contribution
Upcoming SlideShare
Loading in …5
×

Introduction to Contribution

1,395 views

Published on

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)

Published in: Technology, Business
License: CC Attribution-NonCommercial-ShareAlike License
no profile picture user

  • Login to see the comments

  • Be the first to like this

Introduction to Contribution

  1. 1. Introduction to Contribution WordCamp Orange Country 2012Mike Schroder (DH-Shredder)@GetSource - http://www.getsource.net
  2. 2. Who Am I?• Mike Schroder, a.k.a DH-Shredder, a.k.a. @GetSource• Third Culture Kid, enjoy Coffee & Sailing• WordPress Core and Plugin Contributor• Happy DreamHost Employee
  3. 3. If you haven’t read ...• http://codex.wordpress.org/Contributing_to_WordPress• Andrew Nacin’s in-progress handbook: • http://nacin.com/projects/core-contributor-handbook/
  4. 4. Who Contributes?• Theme Review Team • Polyglots• Plugin Review Team • .org Systems• Core Code • Mobile Applications• UI/UX Group • Documentation• Support Forums• Accessibility
  5. 5. I’m going to focus on Core Code contribution.
  6. 6. Core Team?
  7. 7. Contributors.
  8. 8. Contributors.
  9. 9. OKAY.How can I get on this list of AWESOME?
  10. 10. Your First Contribution
  11. 11. Release Cycle• http://wpdevel.wordpress.com• foreach ($releases as $release) • Planning • Development Cycles/Sprints • Beta • RC
  12. 12. Planning:Choose the Scope.
  13. 13. Development Cycles: Teamwork.
  14. 14. Beta:No More Features.
  15. 15. Release Candidate: Just the Regressions.
  16. 16. Okay. I understand the release cycle. What’s next?
  17. 17. Start Small.
  18. 18. Look for a Need.
  19. 19. “If it’s not on Trac, it doesn’t exist.”-Pretty much the entire Core Team.http://core.trac.wordpress.org
  20. 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 -> Custom Query (i.e. needs-refresh)
  21. 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. 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 < 20000.diff
  23. 23. 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
  24. 24. Attach a patch.• Attach it to the ticket.• Add a note to the ticket, so that everyone cc’d is notified.
  25. 25. No one has responded. What now?
  26. 26. Bother the crowd.
  27. 27. Learn to love IRC.#wordpress-dev on FreeNode
  28. 28. Ask for help.
  29. 29. Ping those who arehandling your ticket!
  30. 30. Don’t rely on wp-hackers.
  31. 31. Twitter is your friend.
  32. 32. Be prepared for rejection.
  33. 33. Iteration is key.It’s okay if someone else has a better idea.
  34. 34. Let’s work together tomake a better WordPress.
  35. 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

×