Download to read offline
![How to submit a Patch.
• Create/Comment on an issue.
• Attach the patch.
• [description]-[issue-number]-[comment-number].patch
• Revise based on testing/reviews.](https://image.slidesharecdn.com/topatchorwritecustomnerd2014-140913110520-phpapp02/75/To-Patch-or-Custom-How-to-decide-when-to-patch-a-contrib-module-or-go-custom-NerdSummit-2014-37-2048.jpg)
Uploaded byMichael Miles
To Patch or Custom: How to decide when to patch a contrib module or go custom @NerdSummit 2014
The document provides a guide on how to effectively decide between using existing Drupal modules or creating custom solutions through a process called R.E.A.D: research, evaluate, analyze, and determine effort. It includes scenarios illustrating how to handle specific requirements using existing solutions or developing new modules while emphasizing the importance of community resources and proper documentation. Additionally, it outlines the steps for submitting patches and contributing to the Drupal ecosystem.
More Related Content
Similar to To Patch or Custom: How to decide when to patch a contrib module or go custom @NerdSummit 2014
To Patch or Custom: How to decide when to patch a contrib module or go custom @NerdSummit 2014
- 1. To Patch orCustom How to select the right path. #PatchOrCustom, #justREAD
- 2. Who You Are. • Site Builder • Developer • Decision Maker • New to Drupal ! • Want to re-enforce habits
- 3. What’s it allabout. How to quickly make smart, informed decisions.
- 4. Michael Miles •Associate Director of PHP @ Genuine Interactive. • Drank the Drupal Kool-aid in 2008. (it’s grape flavored) ! • Twitter: @mikemiles86 • D.o: mikemiles86 @WeAreGenuine
- 5. A lover ofmemes.
- 6. How to R.E.A.D! (yay acr!onyms!)
- 7. R.E.A.D • Researchwhat exists. • Evaluate the options. • Analyze the gap. • Determine amount of effort. #justREAD
- 8.
- 9. Research what exists. • Isolate key functionality needs. • Search for existing modules. • Use the community.
- 11.
- 12. Evaluate the options. • Read the module description. • Look at community adoption. • Look at maintainer activity.
- 14.
- 15. Analyze the gap. • Download and test the module. • Discover missing functionality. • Check issue queue for solutions.
- 16.
- 17. Determine amount ofeffort.
- 18. Determine amount ofeffort. • Review the module code. • Estimate how much has to be changed. • Do changes extend or alter module?
- 19. Let’s review. Likedevelopers…
- 20. Research.! Find modules? Evaluate.! find best fit? Analyze.! is there a gap? Use community solutions. Determine.! big change? Build a custom module. Use existing module. Community solutions exist? Patch. YES YES YES YES NO NO NO NO YES NO …Flow Chart FTW!
- 21.
- 22.
- 23. The Requirements. WHENSAVING A FILE AND IT IS A JPEG IMAGE THEN THE EXIF META DATA NEEDS TO BE CAPTURED AND MAPPED TO CUSTOM FIELDS AND THESE MAPPINGS NEED TO BE EXPORTABLE USING FEATURES !
- 24. WHEN SAVING AFILE Research what exists. AND IT IS A JPEG IMAGE THEN THE EXIF META DATA NEEDS TO BE CAPTURED AND MAPPED TO CUSTOM FIELDS AND THESE MAPPINGS NEED TO BE EXPORTABLE USING FEATURES. ! Isolate key functionality needs.
- 25. Research what exists. Search for existing modules.
- 26. Research what exists. Find possible existing solutions • The Exif module • The Exif custom module
- 27. Evaluate the options Read the module description.
- 28. Evaluate the options Look at community adoption. Exif Exif Custom
- 29. Evaluate the options Look at maintainer activity.
- 30. Evaluate the options Determine best fit.
- 31. Analyze the gap. Download and test the module.
- 32. Analyze the gap. Discover missing functionality.
- 33. Analyze the gap. Check issue queue for solutions.
- 34. Which path tochoose? • Patch Exif Custom module ! • Write own Exif module
- 35.
- 36. What is aPatch? • drupal.org/patch • A structured list of changes to a file. • Used to re-create changes to a files. • Focus on a single change.
- 37. How to submita Patch. • Create/Comment on an issue. • Attach the patch. • [description]-[issue-number]-[comment-number].patch • Revise based on testing/reviews.
- 38.
- 40.
- 41. The Requirements. WHENSITE USES WORKBENCH TO MODERATE CONTENT THEN CAN CREATE MULTIPLE TRANSITIONS BETWEEN STATES AND TRANSITIONS ARE EXPORTABLE USING FEATURES ! WHEN EDITNG A CONTENT REVISION THEN CAN SCHEDULE A TRANSITION AND CAN SELECT DATE FOR FIRST STATE AND CAN SELECT DATE FOR SECOND STATE
- 42. Research what exists. Isolate key functionality needs. WHEN SITE USES WORKBENCH TO MODERATE CONTENT THEN CAN CREATE MULTIPLE TRANSITIONS BETWEEN STATES AND TRANSITIONS ARE EXPORTABLE USING FEATURES ! WHEN EDITNG A CONTENT REVISION THEN CAN SCHEDULE A TRANSITION AND CAN SELECT DATE FOR FIRST STATE AND CAN SELECT DATE FOR SECOND STATE
- 43. Research what exists. Search for existing modules.
- 44. Evaluate the options Read the module description.
- 45. Analyze the gap. Download and test the module.
- 46. Analyze the gap. Discover missing functionality. • Unable to create different transition schedules • Unable to select different transitions for revisions • No features integration.
- 47. Determine amount ofeffort. Estimate how much has to be changed. • Will need to change how schedules are created. • Will need to change how schedules are stored. • Will need to add features integration.
- 48. Which path tochoose? • Patch Scheduler workbench module ! • Write own scheduler module
- 49.
- 50. Module Writing Guidelines. • drupal.org/developing/modules • Follow Drupal coding standards. • Make use of hooks and APIs. • Test your code.
- 51. Contributing a module. • Is it functionality other could use? • Name appropriately. • Provide accurate description. • Be an active maintainer.
- 52. Wrote a custommodule.
- 53. Be an activemaintainer.
- 55. Remember R.E.A.D. •Research what exists. • Evaluate the options. • Analyze the gap. • Determine amount of effort. #justREAD
- 56.