> For the complete documentation index, see [llms.txt](https://scribbles.devrel.page/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scribbles.devrel.page/community-management/growing-open-source-community.md).

# How to grow a healthy Open-Source community?

{% embed url="<https://youtu.be/qdGNyh7cwxk>" %}
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.&#x20;
* 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:

### &#x20;**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&#x20;
* 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!&#x20;
* Holding yourself accountable for the communities and making sure you start initiatives to stay interested.&#x20;
* Make sure your community shares the same goal as you.&#x20;
* Not accepting contributions in open-source == respectfully drawing a line about how much and what kind of engagement you want from the community,&#x20;
* 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.

### &#x20;Tackling imposter syndrome...?

#### Here's how Brian approaches impostor syndrome and making open source accessible -&#x20;

* 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.