Contributing to drupal
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Contributing to drupal

on

  • 805 views

Contributing to drupal session

Contributing to drupal session

Statistics

Views

Total Views
805
Views on SlideShare
805
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Contributing to drupal Presentation Transcript

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