# How to grow a healthy Open-Source community? {% embed url="" %} Video {% endembed %} ## Summary: * Structuring the project with ***promotion paths*** * ***Hierarchy of advancement*** in open source projects * ***Holding yourself accountable*** for the communities and making sure you start initiatives to stay interested. * Setting ***clear paths for learning*** and advancement. * ***Establishing your intentions, boundaries, and interests*** — and communicating that (or being open to hearing this is so important! ## Scribbles: ### **Characteristics of a good open-source community...** * structure * knowing ***who*** to talk to * documentation * steps how to contribute * the architecture * structuring the project with promotion paths ### Ladder Model for Open Source * hierarchy of advancement in open source projects * allows for buying and learning * setting clear paths for learning and advancement #### *Share your work with the community, do not hide behind your code and work.* * Have your readme at the bare minimum. Make it easier for the newbies! * Holding yourself accountable for the communities and making sure you start initiatives to stay interested. * Make sure your community shares the same goal as you. * Not accepting contributions in open-source == respectfully drawing a line about how much and what kind of engagement you want from the community, * Documentation (blog posts, guides, etc) and paying attention to the little details including down to social cards is super helpful especially in telling stories and intention. ### Tackling imposter syndrome...? #### Here's how Brian approaches impostor syndrome and making open source accessible - * Intentionally you're going to have a solution written in the issue, provide an easy win. * Providing mentorship and help. * Giving credit where you can. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://scribbles.devrel.page/community-management/growing-open-source-community.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.