How To Contribute Drupalcon

5,550 views

Published on

This presentation discusses how anyone from a 'newbie' to a 'ninja' can get involved in Drupal.

Original session description:

This topic will be all about how to contribute to the Drupal community, in a number of different areas. While there'll be information for the hackers, even if you have only ever installed Drupal, you can help the project you know and love become even better.

Topics covered will include:
- Participation? Feh. What's in it for me?
- Community philosophy: Whys and Hows, Dos and Donts.
- Documentation: Helping other people not bash their heads against the same stuff you have.
- Helping with user support: Or, how to have a never-ending supply of clients.
- Maneuvering issue queues with speed and finesse.
- Patch review strategies that would make Dries proud.
- Taking control I: How to help get bugs fixed, and features in, even if you're not a coder.
- Taking control II: CVS, Patch, and how to use them to fix all that stuff you wish worked

Published in: Business, Technology
  • Be the first to comment

How To Contribute Drupalcon

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

×