How To Contribute Drupalcon

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    3 Favorites

    How To Contribute Drupalcon - Presentation Transcript

    1. How to Contribute to Drupal
      • A guide for everyone from “newbie” to “ninja”
    2. Something to keep in mind...
    3. Open source users
    4. Spoiler : You want to be part of that 2%.
      • And we’ll bend over backwards to help you get there.
    5. What’s your sign?
    6. Newbie
    7. Your mission:
      • Help other newbies not bash their heads against the same stuff you had to.
    8. User
    9. Your mission:
      • Guide and mentor the newbies to get them out of the frustrated place.
    10. Site Builder
    11. Your mission:
      • Provide “from the trenches” information to developers.
    12. Developer
    13. Your mission:
      • Make Drupal more awesome!
    14. Ninja
    15. Your mission:
      • Turn developers into fellow ninjas.
    16. How can you help?
    17. Ways that anyone can contribute...
    18. Advocacy
    19. Translations
    20. Graphics
    21. $$$
    22. Ways that newbies can contribute...
    23. Report problems with documentation.
    24. Provide usability feedback.
    25. Example
    26. Module list in 4.7.x
    27. Module list in 5.x
    28. Ways that users can contribute...
    29. Help out with user support.
    30. Improve documentation
    31. How to help with documentation
      • Join the Documentation Team
      • Create new pages
      • Improve/fix text
      • Roll-in comments
    32. Hands-on : Let’s join the docs team! :)
    33. Issue queue house-cleaning.
    34. Ways that site builders can contribute...
    35. File feature requests.
    36. File bug reports.
    37. Bad bug reports
      • “It’s broke.”
      • “OMG!1! READ THIS!1!”
      • “You suck.”
    38. Good bug reports
      • Search first.
      • What did you do?
      • What did you expect to happen?
      • What happened instead?
    39. Testing and reviewing patches.
    40. What is a “patch?” Index: modules/book/book.info =================================================================== RCS file: /cvs/drupal/drupal/modules/book/book.info,v retrieving revision 1.4 diff -u -p -r1.4 book.info --- modules/book/book.info 8 Jun 2007 05:50:53 -0000 1.4 +++ modules/book/book.info 22 Jul 2007 16:54:33 -0000 @@ -1,6 +1,6 @@ ; $Id: book.info,v 1.4 2007/06/08 05:50:53 dries Exp $ name = Book -description = Allows users to collaboratively author a book. +description = Allows users to structure site pages in a hierarchy or outline. package = Core - optional version = VERSION core = 6.x
    41. Bad patch reviews
      • “+1”
      • “I haven’t read the issue, but...”
      • “I haven’t tested the patch, but...”
    42. Good patch reviews
      • Describe what you did.
      • Describe your results.
      • Give your opinion about what this means, based on experience, background, etc.
      • Be as nit-picky as possible (within reason ;)).
    43. Tools of the trade
      • cvs checkout drupal
        • http://drupal.org/node/320 & 321
      • patch -p0 < patch.patch
        • http://drupal.org/patch
    44. Demo : Let’s test a patch!
    45. Ways that developers can contribute
      • Mission: Make Drupal more awesome!
    46. Help with developer documentation.
    47. Contribute modules and themes.
    48. Steps to becoming a code contributor
      • Search first.
      • Apply for a CVS account.
      • Check-in your code.
      • Create a project.
      • Maintain your issue queue. ;)
    49. Create patches.
    50. Tools of the Trade
      • Coding standards
        • http://drupal.org/node/318
      • cvs checkout drupal
      • cvs diff -up > patch.patch
        • drupal-actions-usability-cleanup-172773-81.patch
      • Thick skin ;)
    51. Demo : Let’s create a patch!
    52. Ways that ninjas can contribute
      • Mission: Create more ninjas.
    53. Mentor new developers.
    54. Organize development efforts.
    55. Help maintain drupal.org.
    56. Wow, this sounds like an awful lot of work.
      • Why should I bother?
    57. Open source is a meritocracy .
      • Karma is the official currency.
    58. Saves time and money .
    59. Gets you more business and attracts better people .
    60. It means easier maintenance for your sites.
    61. Makes you a better programmer .
    62. Gives you direct control over the direction of project.
    63. Questions?

    + guestc9344eguestc9344e, 3 years ago

    custom

    2932 views, 3 favs, 0 embeds more stats

    This presentation discusses how anyone from a 'newb more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 2932
      • 2932 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 3
    • Downloads 60
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories