this post was submitted on 03 Jan 2025
48 points (98.0% liked)

Programming

17752 readers
1027 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

id like to ask if there is some guideline/advice for asking for open source contributions.

initially i thought i could just have open source code, documentation and communicate about it, but that doesnt seem to work for gaining contributors.

maybe there is something else im overlooking?

contributors would be using their own valuable time and effort so it could just be that my projects are not interesting enough. it might be worth concluding that i should proceed on this solo.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] starshipwinepineapple 20 points 4 days ago (1 children)

Just some general advice:

  • get regular users. Contributors are going to be a subset of users as another commentor mentioned.
  • make sure to have a CONTRIBUTING.md and that it is clear/ easy to follow. Some projects will link to a separate wiki from the .md which is fine. But make sure your "first time contributor" instructions are easy to follow to set up whatever dev environment needed. The less clear the documentation then the more motivated the contributors will need to be.
  • if you haven't already, make issues with feature requests that you are wanting to add. Include enough details that someone other than you will understand your requirements.
  • consider a label you use to signify "great issue for a first time contribution". These should be relatively simple fixes or simple features but give time for someone else to try them instead of completing it right away. Make sure to reference this label in your contribution documentation as a great starting point. If you're able to get someone to do a simple fix then they will have set up the dev environment and may do other future issues.
  • advertise that you're looking for contributors. Point out your docs, first time contributor label, and any specific features you want/need help with.
[โ€“] xoron 6 points 4 days ago

thanks! i'll make time to create those.