Successfully reported this slideshow.

Contributing to WordPress - #WCNYC

0

Share

Loading in …3
×
1 of 32
1 of 32

Contributing to WordPress - #WCNYC

0

Share

Download to read offline

One of the greatest benefits of using WordPress is that it’s open source and is constantly being improved by the community. However, few people know exactly what that process looks like.

When you identify a bug in WordPress, where does that information need to be reported? Who fixes it? And how does it eventually get sent out to 25% of the web in the next WordPress Core release?

In this talk, we’ll look at the progression of a bug ticket from beginning to end and see how the software we use every day is continually improved.

One of the greatest benefits of using WordPress is that it’s open source and is constantly being improved by the community. However, few people know exactly what that process looks like.

When you identify a bug in WordPress, where does that information need to be reported? Who fixes it? And how does it eventually get sent out to 25% of the web in the next WordPress Core release?

In this talk, we’ll look at the progression of a bug ticket from beginning to end and see how the software we use every day is continually improved.

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Contributing to WordPress - #WCNYC

  1. 1. Contributing toWordPress: From Beginning to Closed Ticket Keanan Koppenhaver CTO,AlphaParticle @kkoppenhaver http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  2. 2. Open source is eating software http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  3. 3. Some examples of open Source http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  4. 4. And the big one… http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  5. 5. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com https://www.hastac.org/blogs/barrypeddycordiiiandelizabethapitts/2013/08/01/chapter-two-open-programming- open-learning
  6. 6. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com https://www.hastac.org/blogs/barrypeddycordiiiandelizabethapitts/2013/08/01/chapter-two-open-programming- open-learning
  7. 7. HowdoesWordPress manage this process? http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  8. 8. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  9. 9. Managed through SVN http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  10. 10. Ticket-> Discussion -> Patch -> commit http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  11. 11. Getstarted usingan svn client http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  12. 12. Getstarted usingan svn client http://alphaparticle.com AlphaParticle keanan@alphaparticle.com ( Oryou can “cheat”and use Git/GitHub ) http://scribu.net/wordpress/contributing-to-wordpress-using-github.html
  13. 13. So Howexactly doesabug in WordPress getfixed? http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  14. 14. Step 1: File a ticketin Trac http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  15. 15. https://core.trac.wordpress.org/ticket/37980 http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  16. 16. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  17. 17. Step 1.5: Discussion ensues http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  18. 18. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  19. 19. Step 2:Actually fixing the bug http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  20. 20. Localenvironmentsetup http://alphaparticle.com AlphaParticle keanan@alphaparticle.com https://make.wordpress.org/core/handbook/tutorials/installing-a-local-server/
  21. 21. Make theactualfix http://alphaparticle.com AlphaParticle keanan@alphaparticle.com (And do lots of testing )
  22. 22. Generate apatch http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  23. 23. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  24. 24. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  25. 25. Step 2.5: More discussion ensues http://alphaparticle.com AlphaParticle keanan@alphaparticle.com ( Slackand Trac )
  26. 26. Testingacross browsers/platforms http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  27. 27. (eventually) Slated toareleaseand committed byacore Committer http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  28. 28. Where to start? http://alphaparticle.com AlphaParticle keanan@alphaparticle.com
  29. 29. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com https://make.wordpress.org/chat/
  30. 30. http://alphaparticle.com AlphaParticle keanan@alphaparticle.com https://make.wordpress.org/
  31. 31. Firsttime? http://alphaparticle.com AlphaParticle keanan@alphaparticle.com https://core.trac.wordpress.org/tickets/good-first-bugs
  32. 32. Questions? http://alphaparticle.com AlphaParticle keanan@alphaparticle.com @kkoppenhaver

×