— with mparker17Slides at mparker17.github.io/reveal.js-drupal_contributing/ Speaker notes at github.com/mparker17/reveal.js-drupal_contributing/blob/gh-pages/speaker-notes.html
|Current employers||Former employers||Qualifications|
|Digital Echidna, Brady's Meat & Deli||Environment Canada,
Myplanet, OpenConcept Consulting
|Acquia Certified Drupal Developer, CS degree not completed at UWaterloo|
People contribute to OSS for many reasons... here are some common ones:
You can still contribute to Drupal, even if you don't write code!
If you can write code (or theme), you can contribute by writing patches to projects that already exist; or starting your own projects.A project is usually a module, theme, distribution, or Drupal Core itself.
The Drupal community collaborates mainly in Drupal.org's "issue queues".
An issue queue is just a list of things that need to be addressed for a given project, like JIRA tickets.
A project is usually a module, theme, distribution, or Drupal Core itself; but there are some "Community" projects that have no code: just a list of issues for people to collaborate on.Community project examples: documentation, mentoring, Drupal.org infrastructure, Drupal.org content.
Issues may be Plans, Tasks, Bug reports, Feature requests, or Support requests; they have a priority and status, can be assigned, and can be tagged with taxonomy.There is a guide at drupal.org/issue-queue
The issues on Drupal.org have metadata which determines which queue they are in, which type, etc.
When you comment on an issue, you have the opportunity to change the issue's metadata at the top of the Add New Comment form.This is what the New Comment form's Issue Metadata section on drupal.org/node/2958021 looked like to me on 2019-08-01.
When collaborating in an issue queue, Drupal.org has a feature to let you attribute your contributions so you can give yourself / your employer / your client credit.
On the Add New Comment form, this is just below the Issue Metadata section.
Resources, references, special thanks: