Promet Source's team reviews the importance on giving back to the Drupal 8 project by taking on issues from drupal.org and how anyone can contribute regardless of their experience.

1. Drupal 8 Involvement

2. Why get involved?
● Open source
● Recruitment
● Marketing/promotion
● Increased employee training/benefits
● That warm fuzzy feeling
● Growth in technical and non-technical

3. How To Get Involved
Forums
IRC
Community Initiatives
Modules
Themes
Translations
Groups
Events
Donate
Documentation
Drupal Association

4. Code related requirements
● A drupal.org account and logged in
● A working site set-up on your local
I used DrupalVM for the vagrant box

5. Attribute your contribution
● Specify how you’re contributing
● Specify who’s the organization you’re at
● Specify who’s the customer/end-user

6. Attribute your contribution - Add an organization
Go to Your Profile > Edit

7. Attribute your contribution - Issues

8. Attribute your contribution - View

9. Get an issue

10. Get an issue - Dashboard

11. Get an issue - General

12. Get an issue - Specific

14. Make sure it interests you and
is unassigned

15. Get an issue - Assigning to yourself

16. Get an issue - Assigning to yourself

17. Solve an issue - Get a copy of the code
https://www.drupal.org/project/drupal/git-instructions

18. Solve an issue - Apply a patch
git apply -v <patch-file-name>.patch

19. Solve an issue - The actual thing
Don’t forget to follow Coding and Doxygen and Comment
standards.

20. Solve an issue - CodeSniffer

21. Solve an issue - PhpStorm + Xdebug + DrupalVM

22. Create a patch
1. [description]-[issue-number]-[comment-number]
Any project’s version control page (https://www.drupal.org/project/drupal/git-instructions)
2. [project_name]-[short-description]-[issue-number]-[comment-number]
Advanced patch contributor guide (https://www.drupal.org/node/1054616)
Example:
core-fix_typo_in_node_plugin_class_description-2629712-7-D8.patch

23. Create a patch - Review
● Review coding standards
● Review documentation standards
● Proofread your patch

24. Create a patch - Interdiff
interdiff-[issue_id]-[old_comment_number]-[new_comment_number].txt
Only when you’re adding a new patch after another one.

25. Submit for review

26. Submit for review - Files

27. Issue fixed - Closed (fixed)

29. Dreditor

30. Dreditor

31. Thank you