Contributing to Drupal - A Guide for New Developers
•Download as PPT, PDF•
0 likes•812 views
![Summary ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (7)
Similar to Contributing to Drupal - A Guide for New Developers
Similar to Contributing to Drupal - A Guide for New Developers (20)
Recently uploaded
Recently uploaded (20)
Contributing to Drupal - A Guide for New Developers
- 1. Contributing to Drupal Christopher Skene
- 26. Control presentation of fields
- 27. Display Suite in Drupal 7 http://www.flickr.com/photos/williamcromar/5345283531
- 28. Display Suite in Drupal 6 http://www.flickr.com/photos/7891209@N04/2586286021/
Editor's Notes
- - Try to reproduce the issue based on the provided information. If you can reproduce the bug, provide detailed steps and describe your configuration and other modules installed on the site where you reproduced it. - If you can't, ask for the steps to reproduce, installed modules and so on - If it's not a bug but just needs something configured differently or another module or ... explain that, switch the issue to "support request" and set it to "fixed". Even better, create a documentation page and point to it in the issue. - Reclassify the issue as necessary, maybe it's not a bug but a missing feature, or not critical but only a normal bug. (See http://drupal.org/node/156119 and http://drupal.org/node/45111 for information about what status/priority means what)
- - Set up a clean environment for the version of the code that is specified for the issue. - If the issue comes with an existing patch, apply the patch now, so you can correct work that was previously done. Work on your fix Test (preferably using the SimpleTest framework) - Be sure that the file has been commented and formatted correctly before creating the patch. - Submit the patch to the appropriate issue and mark it "Needs review”
- Always use an existing solution where one exists Find a balance between sufficiently abstracted to cover multiple use cases, but not too complex as to be unmaintainable Build a proper internal API (you’ll thank yourself later) Use OO where possible, but wrap code in functional wrappers, especially factory functions Pay attention to what version of PHP the Drupal version is written for Learn the Form API and use it properly Learn how to use drupal_alter and work with hooks Use the database API Release before a major code change is committed to the repository, not just after Use the SimpleTest framework
- Not doing anything for two years then writing "I think I have this working" is not a good way to close a thread.
- I became lead 6.x maintainer in September 2011
- Shiny Well-architected Built with a purpose Completely rewritten for Drupal 7 Leverages Entities, Ctools and other Drupal 7 stuff Has only one module Has a very busy issue queue
- Built up over time A mix of styles Not all of it seems to work properly Probably looked completely different at some point Extended many times Difficult to maintain Completely different from the Drupal 7 version Built around disparate internal APIs, across 5 modules, supporting integration of roughly 10 other contributed modules Has a relatively quiet issue queue