Open Source Contribution

Open Source is not sustainable unless people contribute back to the project and/or community. Drupal Contribute

Goal and Mission

To ensure we understand the importance of open-source contributions and get actively involved with the community regarding contributions.

Why should you contribute?

1. Quickly learn how to write clean, readable, and maintainable code.

2. Gain community-wide recognition and appreciation.

3. Get a chance to connect with all the like-minded individuals in the community. Build a network of your choice.

4. The best way to understand the technology you are working on is by diving deep into the codebase on which you build your application.

5. Understand how cost-effecti’s reputation.

6. Makes you a very confident developer once you start getting acceptance at a global level.

7. Add a noticeable point to your resume and build an outstanding portfolio.

8. Payback to the community.

9. Turn your ideas into life by deciding to go open source.

Still not convinced? How about your resume? Check your resume and remove all the open-source projects from the skills section, as they wouldn’t exist if nobody were interested in contributing back.

How to contribute?

1. Code Contribution: Fixing bugs, adding features, reviewing PR or patches, and doing integrations.

2. Documentation and Blogging: Helping with documentation, writing about how to use or do something particular.

3. Support Channels: Being very active on Slack, Stack overflow, IRC, or any other forum used by the community.

4. Get Involved: Join Slack, meetups, attend conferences, and organize events.

5. Mentoring: Help the beginners understand the project better.

Guidelines for low-value contribution

How can we prevent low-value contributions?

• To understand issue etiquette, the credit system, and how to contribute, everyone should review how we contribute in the engineering handbook: Drupal Contribution

• Before starting contributions to the Drupal community, everyone needs to complete this Leapsome course: Leapsome

• Once they have gone through these documents and completed the course, they can start contributing to the Drupal community. They can begin with novice issues, which are primarily for new contributors.

• We have a Slack integration with Contrib Tracker that shows all the contributions made by everyone. This allows us to monitor the issues people are working on and provide feedback if they are doing something incorrectly.

If we discover any low-value contributions:

• We will create a Slack channel with the team member, their manager, and other relevant stakeholders.

• Ask the team member to go to those issues, remove the low-value contributions, and provide a detailed explanation of how the mistake was made.

• Enroll them in the Leapsome course (if they have not already completed it) and ask them not to contribute until they have finished the course.

• Guide them with their new contributions. A mentor can be assigned for their next issues (first or second), providing guidance on how to make meaningful contributions.

Getting Help

1. Join #guild-contributions for all the critical updates and collaboration regarding contributions.

2. Check up with Service Area Leads and peers regarding an open-source contribution opportunity.

Useful Resources

• Why contribute to open source?

• 3 reasons to contribute to open source now

• 6 Reasons Why Developers Should Contribute More To Open Source

• Case study by CI&T

• Open Source Guides

• How to Contribute to Open Source

• Starting an Open Source Project

• Finding Users for Your Project

• Building Welcoming Communities

• Best Practices for Maintainers

• Leadership and Governance

• Getting Paid for Open Source Work

• Your Code of Conduct

• Open Source Metrics

• The Legal Side of Open Source