• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Contributing to drupal

Contributing to drupal



Contributing to drupal session

Contributing to drupal session



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



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.

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

    Contributing to drupal Contributing to drupal Presentation Transcript

    • Contributing to Drupal
    • What is Drupal
      • Drupal is Community
        • Without the community drupal is nothing
        • With it is so much more
    • Ways to Contribute
      • It is NOT just for coders
      • And it is not just Core
      • Options for contributing
        • Create patches
        • Review patches
        • The documentation queue
        • Contributed modules
    • The drupal issue queue
      • Can be found at http://drupal.org/project/issues/drupal?categories=All
      • Account settings
        • Contributor links
          • Access areas of interest on the queue quickly
        • Developer links
          • Get tarball snapshots of head
          • Alternative to CVS checkouts
      • The queue what is where.....
    • Drupal 7
      • When does drupal 7 get released
        • When critical issues hit 0
        • When we have an upgrade patch release candidate comes out
      • How are we doing?
        • 21 critical
        • http://drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&participant=&priorities%5B%5D=4&issue_tags_op=or&issue_tags=D7+upgrade+path
    • The documentation team
      • These guys rock
        • They make drupal more accessible to users
        • http://drupal.org/project/documentation
      • Focus on 3 areas
        • Handbook pages
        • api.drupal.org – yes this is technical
          • Instructions for updating are found here http://drupal.org/node/144223
        • Help review core patches for standards
    • Standards
      • All code for drupal (core) needs to adhere to these standards
        • http://drupal.org/coding-standards
        • 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
    • Reviewing a patch
      • All patches go through the process of peer review
        • Cycle
          • For Review
          • Needs work
          • For Review
          • Reviewed and tested by the community
          • Committed – only 2 people can do this currently Dries and Angie Byron (webchick)
    • How to review a patch
      • Documentation exists to make our lives easier
        • Did I say the documentation team rocks
        • http://drupal.org/patch/review
      • Keep concepts
        • What issue are we trying solve?
        • Is it a duplicate?
        • Does the patch meet standards – code and patch standards?
        • If there issues communicate them in constructive way
    • Testing a patch
      • This is done against the head version of drupal you are testing for
        • What?????
        • You need a test environment
          • http://drupal.org/node/28245
          • Summary you need a LAMP stack.
          • And a CVS checkout of drupal
        • Obviously this varies by OS
          • Windows I find XAMPP and Eclipse work well
    • Testing a patch
      • Now you have a development environment
        • Down load the patch from the issue
        • Apply the patch
        • 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
        • Another way to contribute if you have a spare server
    • 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
        • Make sure you have unix line ending
        • Keep patches focused don't add in unrelated fixes create another issue
      • Rerolls
        • Patches go stale why not reroll to head.
    • So.......
      • Anyone can contribute
        • There are so many areas to get involved in
        • And I have of course missed one other way
          • Thanks to the camp organisers!!!!