Who am I?
What do I know about contributing to Drupal?
- 6 years, 9 months on Drupal.org
- I write the Drupal 8 Core Updates occasionally.
- 48 commit mentions in Drupal 8.0 core, 3 commit mentions in Drupal 7 core
- I (co-)maintain 5 modules (plus a few sandbox projects).
- 244 commits to various modules, including Panopoly, Metatag, Examples, Environment Indicator, Search API Pages, Site Audit, and the Drupal.org theme Bluecheese.
- 6 people list me as a mentor on Drupal.org; I've trained/mentored ~32 co-op students in Drupal for my employers.
Other notable things
- I never completed a degree — no formal education
- I have 19 mentors listed on Drupal.org
- I'm a bit dyslexic
- ... the point is, I'm not really all that special, and probably a lot like you.
Why get involved?
Some motivations for contributing to OSS:
Whatever your motivation(s), keep Drupal's code of conduct in mind!
- You want to save yourself time in the future (i.e.: only spend effort fixing something once),
- You want to help others in the same situation,
- You got all this stuff for free, and now it is paying your bills, and now you feel like you should do something in return,
- You want to get your name out there (gain "community karma") to help you find work in the future,
- You want feedback from others (e.g.: for security),
- You want to be influential / a thought leader / establish an industry standard and gain competitive advantage / loyalty,
- You want to make the world a better place, etc.
How can I help?
You can still contribute to Drupal, even if you don't (or can't) code!
- Support others, encourage contribution, connect people,
- Organize events or help with them,
- Train people, provide support, give demos,
- Documentation, translation (interface, documentation), case studies,
- Help design Drupal's UI,
- Triage issues, help plan work, contribute themes,
- Manually test, improve test coverage,
- Help market Drupal, make a donation, vote in the community elections, write a case study, blog, etc.
When should I contribute?
- Volunteer when you have time.
- Don't burn yourself out! If you run out of time/energy, that's okay: the community can (usually) pick up where you leave off.
- At work?
Documentation on Convincing Senior Management to Give Back to Drupal is out there!
- Easier to sell boss/client on contributing bug fixes.
- Developed something new?
- Ask permission from your boss/client to contribute it.
- Consider splitting some of the work on company time, some on your own time.
- Show off your latest project by writing a case study!
Attributing your contributions
If you happen to be using the issue queue, Drupal.org has a feature to let you attribute your contributions so you can give yourself / your employer / your client credit. There is now even a list of organizations ranked by number of contributions!
Where do I contribute?
- Drupal.org or one of its sub-sites:
- drupal.stackexchange.com — support questions
- On IRC (#drupal-contribute, #drupal-design, etc.) — chat rooms for people working with / contributing to Drupal.
- IRL (at events like this, networking, BoFs, sprints, etc.)
- But I'm not experienced / smart enough / qualified to help!
- You're just as smart / qualified as the rest of us!
- Hard for experienced people to identify UX/DX problems!
- But I don't know where to start!
- Lots of tools/programs to help (mentoring,
- Ask in #drupal-contribute (IRC)!
- But I don't have enough time!
- Maybe your employer does!
- Some contributions are quick.
- You'll get faster with practice.
- But I don't have the "confirmed" role
- Talk to me afterwards (or anyone with community role).