How and Why to Patch a Module
Time: 1:30pm - 2:30pm
Ever find a module that does 98% of what you need it to do, and there's no way to make it do that last 2%? Ever need to fix a bug in a module you've run into, but you're the only one who's ever had this problem? You need a patch.
Senior Developer Joshua Turton will cover the hows and whys of patching a module. You will learn:
- When is a patch appropriate?
- How to edit the module's code and what branch to edit against
- How to generate a patch with git diff
- Both on the command line and in a GUI
- How to report an issue in the module issue queue
- and how to name your patch file according to drupal's standards
- How to use drush make to apply your patch automatically.
- What to do if your patch is
- rejected (Oh NO!)
- accepted (WoOt!)
- And most importantly: Why you SHOULD contribute your patch, and don't be shy!
This session may include a live demo on a sandbox module.
About the Presenter
Joshua Turton brings a wide variety of skills to his role as a developer. A programmer comfortable working on both front-end and server-side technologies, he also brings a strong visual sensibility to his work. More than nine years of experience both in agencies and as an in-house developer give him a great flexibility.
Joshua has worked on a wide variety of projects, with an emphasis in the last few years on Drupal work. Highlights include the web site for the Federal Department of Energy and Pac-12 Networks.
A long-time Bay Area resident now living in Costa Rica, Joshua earned an MFA in Computer Arts/New Media from the Academy of Art University. He has also been an instructor there, teaching web technologies. In his spare time, he enjoys coaching Little League, board games, and chocolate.