๐Ÿคฉ 11 days to go until @hacktoberfest ! Here are some ways you can contribute to open-source projects WITHOUT contributing code. A thread ๐Ÿ‘‡.

2:21 PM ยท Sep 18, 2021

9
69
12
197
These are divided into: 1. โœ๏ธ Writing 2. ๐ŸŽจ Designing 3. ๐Ÿง‘โ€๐Ÿ”ฌ Testing/Using 4. ๐Ÿ‘ฅ Mentoring 5. ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Community Managing/Organising
1
1
0
19
1. โœ๏ธ Writing 1.1 Write Documentation Even if you have an amazing project, it is useless without good documentation. So, contributing to docs is really impactful! ๐Ÿค“ Tip: When you start to contribute, try to follow the docs and see if you can find anything missing.
1
1
0
23
1.2 Write Tutorials and Blog Posts Have you been a user of the project for a while? Do you want to contribute to it? Write tutorials and blogs! This will help people who are using the project and you can also share your own insights and tips while writing these.
1
1
0
15
๐Ÿค“ 1.2.navendu's_note I prefer a well-written and up-to-date blog post over reading documentation most of the time.
1
1
0
11
1.3 Translate Documentation There might be users from different parts of the world who are more comfortable in a different language. ใŠ™๏ธ If you know both languages, say English and Mandarin, why not translate? This will open up the project to a whole new user base.
1
0
0
11
1.4 Take Control of the Social Handles ๐Ÿคณ If your project has social media accounts, take control of it and start creating content. This will drive the project's visibility and will help gain more users and contributors.
1
0
0
11
2. ๐ŸŽจ Designing 2.1 Create Art! Create artworks for the project to share on social media, blog posts and even swags. (๐Ÿ˜Ž who doesn't like swags!)
2
0
0
9
2.2 Create a Style Guide With a large and distributed group of contributors, open-source projects may have inconsistent visual designs. As a designer and a contributor, you can create a style guide to ensure consistency.
1
0
0
8
3. ๐Ÿง‘โ€๐Ÿ”ฌ Testing/Using 3.1 ๐Ÿ› Report Bugs Report bugs you find when using the project. This will help code contributors identify and fix them improving the quality of the project.
1
0
0
8
3.2 Become an Advocate/Evangelist Most open-source projects usually do not have a dedicated marketing team to publicise the project. So, as volunteer advocate, you can talk about it in events and social media and also encourage people to use the project.
1
0
0
8
๐Ÿค“ 3.2.navendu's_note Don't even ask the project owners before advocating for the project. ๐Ÿ“ˆ Everyone likes free marketing.
1
0
0
10
3.3 Help Improve the User Experience Most of the open-source project maintainers/code contributors are usually too close to the project to realise bad and unintuitive UX. I am and I know a lot of them. Wear your user hat and report these issues. They are always well received.
1
0
1
9
3.4 Sign Up for Alpha/Beta Testing Alpha/Beta tests are controlled tests of a new feature/release to ensure quality before making it available to the general user base. Feedback from these tests always provide insights that can help in iterating over the features/releases.
1
0
0
8
4. ๐Ÿ‘ฅ Mentoring 4.1 Review Code The more people there is to review code, the better the quality of the code will be. Most projects let anyone review pull requests and comment on it. If you have opinions, this is the place to go.
1
1
0
7
๐Ÿค“ 4.1.navendu's_note Remember to be nice when interacting with other contributors.
1
0
0
6
4.2 Mentor a Contributor If you are skilled in the project's tech stack or you can help contributors make better contributions, become a mentor. Share your experiences and empower them to become a better open-source contributor.
1
0
0
6
๐Ÿค“ 4.2.navendu's_note There are a lot of open-source programs which connect mentors and mentees. I curated some of these. You can find it here:
1
3
0
6
5. ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Community Managing/Organising 5.1 Organise the Project Stale issues? Follow up! Issues without proper labels? Add them! Does this issue still exist? Verify and close them! Unclear issue descriptions? Ask for clarification! Unreviewed pull requests? Request for reviews!
1
0
0
8
๐Ÿค“ 5.1.navendu's_note I can't stress enough how important organising a project is. You will be very well recognised in the community if you start organising things. This goes for other points in this section as well.
1
0
0
10
5.2 Become the Release Manager A release manager keeps track of what everybody is working on and ensures that a project is ready for a release. Checking with teams Ensuring different components are tested Organising the alpha/beta programmes are some of their focus areas.
1
0
0
9
5.3 Organise Events and Meetups Organise project meetings Represent your project in conferences Organise community events This list is note exhaustive. Great community managers go above and beyond and are key players in the success of an open-source project.
1
0
0
8
๐Ÿค“ 5.3.navendu's_note What would we do without community managers? If you are a community manager, you have my gratitude. You guys are awesome!
1
0
0
9
5.4 Get More Chefs to Cook (I mean, non-code contributors) Engineers attract other engineers. But the environment these engineers create are usually not super welcoming to non-code contributors. So, become a steward of the community and make it welcoming to newcomers!
1
0
0
8
๐Ÿ˜… Phew! Did I miss anything? Add it here! I will be posting more content on everything open-source so follow (@sudo_navendu ) to keep me encouraged. (I'm a bass player, I know what it means to be not appreciated. (*๐Ÿฅฒ slaps tears off))
1
0
0
10