Your SlideShare is downloading. ×
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Decoding Core Contribution - WordCamp San Diego 2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Decoding Core Contribution - WordCamp San Diego 2013

256

Published on

Decoding Core Contribution talk from WordCamp San Diego 2013 …

Decoding Core Contribution talk from WordCamp San Diego 2013

Want to contribute to core, but unsure how to proceed? No problem! This session will walk you through the contributor groups in WordPress.org, and help you better understand how the project is run. You’ll learn what the process from code changes to patch acceptance looks like, to help your first contribution go more smoothly.

Presented by Mike Schroder (@GetSource/DH-Shredder)

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
256
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Decoding CoreContributionWordCamp San Diego 2013Mike 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?
  • 4. Contributors.
  • 5. Contributors.
  • 6. OKAY.How can I get on this listof AWESOME?
  • 7. Everyone has somethingto contribute.
  • 8. Which Contributor Groupdo you belong to?
  • 9. Contributor Groups?• Docs• Support• Theme Review Team• Plugin Review Team• Events• Core Code• UI/UX Group• Accessibility• Polyglots• .org Systems• Mobile Applications• Community
  • 10. Not sure where to go?Try #wordpress-contribute
  • 11. Let’s focus onCore Codecontribution.
  • 12. Your First Contribution
  • 13. If you haven’t read ...• http://codex.wordpress.org/Contributing_to_WordPress• The official (always in progress) handbook!• http://make.wordpress.org/core/handbook/
  • 14. Release Cycle• http://make.wordpress.org/core• foreach( $releases as $release )• Planning• Feature Development• Beta• RC
  • 15. Planning:Choose the Scope.
  • 16. Feature Development:Teamwork.
  • 17. Beta:Features are Finished.
  • 18. Release Candidate:Just the Regressions.
  • 19. Okay. I understandthe release cycle.What’s next?
  • 20. Start Small.
  • 21. Look for a Need.
  • 22. “If it’s not on Trac,it doesn’t exist.”-Pretty much the entire Core Team.http://core.trac.wordpress.org
  • 23. 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)
  • 24. 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
  • 25. 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
  • 26. Now, create a patch.• Create all patches from the WordPress root within yourtrunk checkout.• svn diff > bugNumber[.patchNumber].diff• e.g. svn diff > 20000.2.diff• git diff --no-prefix master > 20000.2.diff
  • 27. Attach a patch.• Attach it to the ticket.• Add a note to the ticket, so that everyone cc’d isnotified.
  • 28. No one has responded.What now?
  • 29. Be Persistent!
  • 30. Learn to love IRC.#wordpress-dev on FreeNode
  • 31. Ask for help.
  • 32. Ping those who arehandling your ticket!
  • 33. Don’t rely onwp-hackers.
  • 34. Twitter is your friend.
  • 35. Be prepared for rejection.
  • 36. Iteration is key.It’s okay if someone else has abetter idea.
  • 37. Let’s work together tomake a better WordPress.
  • 38. 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

×