The importance of non-code contributions #58571
Replies: 8 comments 13 replies
-
|
Good project |
Beta Was this translation helpful? Give feedback.
-
|
really good project! |
Beta Was this translation helpful? Give feedback.
-
|
direct link to project download does work only from github CI |
Beta Was this translation helpful? Give feedback.
-
|
belo assunto |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
The ReadME Project's focus on non-code contributions highlights the significant value that these contributions bring to open source projects. While code contributions are often emphasized and celebrated, non-code contributions play a crucial role in project success and sustainability. Various areas such as documentation, tutorials, localization, visual design, support, community management, release coordination, testing, and bug reporting all contribute to the overall health and effectiveness of open source projects. Maintainers have expressed their desire for more non-code contributions, as they recognize the importance of these efforts. To successfully recruit technical writers, designers, and others to their projects, maintainers can take several approaches. Firstly, they can actively communicate the need for non-code contributions, highlighting the impact and value that these contributions bring to the project. Engaging with the community and expressing appreciation for non-code contributions can also encourage individuals to get involved. Additionally, providing clear guidelines, documentation, and resources for non-code contributors can make it easier for them to contribute effectively. Coders who have worked on non-code aspects of open source projects can gain valuable insights and experiences. By participating in non-code tasks, coders can broaden their skill set, deepen their understanding of the project ecosystem, and improve their collaboration and communication skills. They learn to appreciate the multifaceted nature of open source projects and the diverse skills required for their success. Working on non-code projects can also advance one's career, regardless of their background. In the open source community, demonstrating expertise in areas such as documentation, design, or community management can lead to increased visibility, recognition, and networking opportunities. Employers often value individuals who can contribute to non-code aspects, as these skills complement technical proficiency and contribute to a more well-rounded professional profile. In conclusion, non-code contributions are vital to the success and sustainability of open source projects. Both maintainers and coders can benefit from engaging in non-code tasks, and such experiences can advance their careers by broadening their skill set and increasing their visibility in the open source community. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
-
|
That's a great text, but it looks very much like ChatGPT. Did ChatGPT write this? |
Beta Was this translation helpful? Give feedback.
-
|
arch-user-france1 bot. |
Beta Was this translation helpful? Give feedback.
-
|
No, I don't think this account is a bot. There are quite a lot of repositories on it. |
Beta Was this translation helpful? Give feedback.
-
|
nice project |
Beta Was this translation helpful? Give feedback.
-
|
and works good |
Beta Was this translation helpful? Give feedback.
-
|
Thak you |
Beta Was this translation helpful? Give feedback.
-
|
Tacac mee |
Beta Was this translation helpful? Give feedback.
-
|
Good work |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
What have you learned from working on the non-code side? I learned that ReadMe are important! |
Beta Was this translation helpful? Give feedback.
-
The ReadME Project: The value of non-code contributions
Hello, @kevinsundstrom of The ReadME Project here. 👋
Our June edition sees the return of Aaron Francis (@aarondfrancis) with a guide about finishing your projects - something I'm sure we can all use a little help with. And Feross Aboukhadijeh (@feross) explains how you can do your part to secure the open source supply chain, while Aaron Gustafson (@aarongustafson) writes about how progressive enhancement enables accessibility.
@klintron's feature this month dives into the world of non-code contributions. Just about every maintainer we talk with says they wished they got more non-code contributions. Documentation, tutorials, and localization are probably the biggest things we hear about most often, but visual design, support, community management, release coordination, and, of course, testing and bug reports are other big areas. But despite the importance of these things, we often dwell on the importance of code contributions. Worse, non-code contributions are often seen as the realm of the non-programmer. But as Klint learned as he spoke with maintainers and community members, there are good reasons for even the most seasoned coders to pitch in to help with docs, support, release management, and other tasks that don't involve adding new features or fixing bugs.
Give it a read, and/or listen to him talk about non-code contributions on this month's ReadME Podcast.
💬 And tell us your thoughts on the non-code aspects of open source.
Beta Was this translation helpful? Give feedback.
All reactions