Contributing to Drupal
What is Drupal <ul><li>Drupal is Community </li><ul><li>Without the community drupal is nothing
With it is so much more </li></ul></ul>
Ways to Contribute <ul><li>It is NOT just for coders
And it is not just Core
Options for contributing </li><ul><li>Create patches
Review patches
The documentation queue
Contributed modules </li></ul></ul>
The drupal issue queue <ul><li>Can be found at  http://drupal.org/project/issues/drupal?categories=All
Account settings </li><ul><li>Contributor links </li><ul><li>Access areas of interest on the queue quickly </li></ul><li>D...
Alternative to CVS checkouts </li></ul></ul><li>The queue what is where..... </li></ul>
Drupal 7 <ul><li>When does drupal 7 get released </li><ul><li>When critical issues hit 0
Upcoming SlideShare
Loading in...5
×

Contributing to drupal

632

Published on

Contributing to drupal session

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

Contributing to drupal

  1. 1. Contributing to Drupal
  2. 2. What is Drupal <ul><li>Drupal is Community </li><ul><li>Without the community drupal is nothing
  3. 3. With it is so much more </li></ul></ul>
  4. 4. Ways to Contribute <ul><li>It is NOT just for coders
  5. 5. And it is not just Core
  6. 6. Options for contributing </li><ul><li>Create patches
  7. 7. Review patches
  8. 8. The documentation queue
  9. 9. Contributed modules </li></ul></ul>
  10. 10. The drupal issue queue <ul><li>Can be found at http://drupal.org/project/issues/drupal?categories=All
  11. 11. Account settings </li><ul><li>Contributor links </li><ul><li>Access areas of interest on the queue quickly </li></ul><li>Developer links </li><ul><li>Get tarball snapshots of head
  12. 12. Alternative to CVS checkouts </li></ul></ul><li>The queue what is where..... </li></ul>
  13. 13. Drupal 7 <ul><li>When does drupal 7 get released </li><ul><li>When critical issues hit 0
  14. 14. When we have an upgrade patch release candidate comes out </li></ul><li>How are we doing? </li><ul><li>21 critical
  15. 15. http://drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&participant=&priorities%5B%5D=4&issue_tags_op=or&issue_tags=D7+upgrade+path </li></ul></ul>
  16. 16. The documentation team <ul><li>These guys rock </li><ul><li>They make drupal more accessible to users
  17. 17. http://drupal.org/project/documentation </li></ul><li>Focus on 3 areas </li><ul><li>Handbook pages
  18. 18. api.drupal.org – yes this is technical </li><ul><li>Instructions for updating are found here http://drupal.org/node/144223 </li></ul><li>Help review core patches for standards </li></ul></ul>
  19. 19. Standards <ul><li>All code for drupal (core) needs to adhere to these standards </li><ul><li>http://drupal.org/coding-standards
  20. 20. http://drupal.org/project/coder </li><ul><li>This will check standards for you </li></ul><li>If you don't stick to these your patch will not be accepted </li></ul><li>And contributed modules should this as well </li><ul><li>It just makes it easier to read </li></ul></ul>
  21. 21. Reviewing a patch <ul><li>All patches go through the process of peer review </li><ul><li>Cycle </li><ul><li>For Review
  22. 22. Needs work
  23. 23. For Review
  24. 24. Reviewed and tested by the community
  25. 25. Committed – only 2 people can do this currently Dries and Angie Byron (webchick) </li></ul></ul></ul>
  26. 26. How to review a patch <ul><li>Documentation exists to make our lives easier </li><ul><li>Did I say the documentation team rocks
  27. 27. http://drupal.org/patch/review </li></ul><li>Keep concepts </li><ul><li>What issue are we trying solve?
  28. 28. Is it a duplicate?
  29. 29. Does the patch meet standards – code and patch standards?
  30. 30. If there issues communicate them in constructive way </li></ul></ul>
  31. 31. Testing a patch <ul><li>This is done against the head version of drupal you are testing for </li><ul><li>What?????
  32. 32. You need a test environment </li><ul><li>http://drupal.org/node/28245
  33. 33. Summary you need a LAMP stack.
  34. 34. And a CVS checkout of drupal </li></ul><li>Obviously this varies by OS </li><ul><li>Windows I find XAMPP and Eclipse work well </li></ul></ul></ul>
  35. 35. Testing a patch <ul><li>Now you have a development environment </li><ul><li>Down load the patch from the issue
  36. 36. Apply the patch
  37. 37. Test to see if the issue is solved </li><ul><li>Provide feedback and if you feel comfortable mark it RTBC </li></ul></ul><li>The test bot - http://qa.drupal.org/ </li><ul><li>Patches are unit tested by the drupal test bot
  38. 38. Another way to contribute if you have a spare server </li></ul></ul>
  39. 39. Creating a patch <ul><li>Solutions to all issues end with a patch </li><ul><li>Again environment specific </li><ul><li>http://drupal.org/patch/create </li></ul><li>But always makes you roll from root of drupal
  40. 40. Make sure you have unix line ending
  41. 41. Keep patches focused don't add in unrelated fixes create another issue </li></ul><li>Rerolls </li><ul><li>Patches go stale why not reroll to head. </li></ul></ul>
  42. 42. So....... <ul><li>Anyone can contribute </li><ul><li>There are so many areas to get involved in
  43. 43. And I have of course missed one other way </li><ul><li>Thanks to the camp organisers!!!! </li></ul></ul></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×