The document outlines various ways that anyone can contribute to Drupal, from beginner to advanced levels, in order to become a "Drupal ninja". It encourages advocacy, translations, graphics work, reporting issues, providing feedback, helping with user support, improving documentation, filing bug reports and feature requests, testing and reviewing patches, mentoring others, organizing development efforts, and contributing code, themes and modules. The document emphasizes that contributing can help save time and money for businesses, attract better developers, and allow direct input into the project's direction, while also making individuals better programmers.

1. How to Contribute
to Drupal
(And become a Drupal ninja!)

2. Stand up

3. Can you name this
character?

4. Raphael
(of Teenage Mutant Ninja Turtles)

5. Stand up
(again)

6. Do you contribute to
Drupal?

7. Follow along at
http://tinyurl.com/contribute-drupal

8. Ways that anyone
can contribute...

9. Advocacy

10. Get involved with your
local Drupal community
on groups.drupal.org

11. Translations
http://drupal.org/contribute/translations
http://groups.drupal.org/i18n
translations@drupal.org
http://localize.drupal.org/

12. Graphics

13. $$$ or €€€
http://association.drupal.org

14. Report problems with
documentation.
http://drupal.org/handbook

15. Provide usability
feedback.
http://groups.drupal.org/usability
drupal.org Issue queue

16. E.g.

17. Help out with user
support.

18. Improve
documentation

19. How to help with
documentation
Improve / fix text
Create new pages
Roll-in comments

20. Issue queue house-
cleaning.

21. File feature requests.

22. File bug reports.

23. Bad bug reports
“It’s broke.”
“OMG!1! READ THIS!1!”
“You suck.”
"Make it work"

24. Good bug reports
Search first.
What did you do?
What did you expect to happen?
What happened instead?

25. Search first!

26. Testing and
reviewing patches.

27. What is a “patch?”
Index: modules/node/node.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/node/node.module,v
retrieving revision 1.1117
diff -u -p -r1.1117 node.module
--- modules/node/node.module 31 Aug 2009 17:06:09 -0000 1.1117
+++ modules/node/node.module 2 Sep 2009 08:40:24 -0000
@@ -1898,7 +1898,7 @@ function node_page_default() {
else {
drupal_set_title(t('Welcome to @site-name', array('@site-name' => variable_get
('site_name', 'Drupal'))), PASS_THROUGH);
- $default_message = '<p>' . t('No page content has been created yet.') . '</p>';
+ $default_message = '<p>' . t('No front page content has been created yet.') . '</p>';
$default_links = array();
if (_node_add_access()) {

28. Finding a patch
Issue queues
Novice tag; http://drupal.org/patch/novice
Play patch bingo

29. Bad patch reviews
“+1”
“I haven’t read the issue, but...”
“I haven’t tested the patch, but...”

30. 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 ;)).

31. Tools of the trade
cvs checkout drupal
http://drupal.org/node/320 & 321
patch -p0 < patch.patch
http://drupal.org/patch

32. Demo
Let’s test
a patch!

33. Help with developer
documentation.

34. Contribute (to)
modules & themes

35. Become a code
contributor
Search for existing similar code.
Apply for a CVS account.
Check-in your code.
Create a project.
Maintain your issue queue. ;)

36. Create patches.

37. Tools of the Trade
Coding standards http://drupal.org/coding-standards
Coder module http://drupal.org/project/coder
cvs checkout
cvs diff -up > my.patch
Thick skin ;)

38. Demo: Let’s create a
patch!

39. Mentor new
developers.

40. Get involved with a
specialist group on
groups.drupal.org

41. Organize
development efforts.

42. Wow, this sounds like
an awful lot of work.
Why should I bother?

43. Drupal is a
DO-ocracy
Karma is the official currency.

44. Saves time and
money.

45. Gets you more
business and attracts
better people.
http://buytaert.net/contributing-back-to-drupal

46. More eyes & reviews
on your code
Makes you a better
programmer.

47. Gives you direct input
into the direction of
project.

48. Stand up

49. Do you know a way you can
contribute to Drupal?
(not money)

50. Useful links
These slides http://tinyurl.com/contribute-drupal
How to contribute: http://drupal.org/contribute
User groups: http://groups.drupal.org
Creating patches: http://drupal.org/patch/create
Finding patches: http://drupal.org/patch
Novice issues: http://tinyurl.com/drupalnovice
Contribute to documentation: http://drupal.
org/contribute/documentation

51. Questions?