markdown guide

Personally, I think an active need and guideline for contributions makes things really nice. If it's easy to clone, get running locally, and run all the tests, then the barrier to entry is lessened for contributing.

Also if you have a history of pleasant, constructive PR comments and history, that is always a good sign of a nice community.

Usually my contributions are need based, and sometimes I've been corrected that it's not within the scope of the project to accept my changes. It really leaves an impression if the owners leave helpful feedback on how to move forward, or explain that it's out of scope.


I totally relate to the "need based" contributions. Thanks for sharing :)


Nice! Had a similar question here:

Also on Reddit:

I brought this up at an OSS meetup I organize in Oregon, and the responses were equally varied. I'm personally drawn to a project with great communication ability and actual encouragement to contribute. A project should be either a learning resource ("this is very specific but you might be interested in how it works") or have broader application for others' use.


Oh wow! Thanks for sharing these resources, I will take a look :)


I will try to ignite the conversation by saying that in my opinion documentation and right labeling of issues are the key. A good open source project helps developers to deep dive into the code, explaining technical decisions and using label to assist other developers choose the right issue for them to solve. It is not an easy task at all but I think it is mandatory to share your knowledge as a project owner with other developers so they can help you out

Classic DEV Post from Apr 4

Design Patterns in Java

I thought it would be a fun to write a series of blog posts looking at differen...

Ido Shamun profile image
Co-Founder The Elegant Monkeys, Co-Maker of Daily and a passionate software developer