Developer Advocacy
How to grow a healthy Open-Source community?
Twitter Spaces fireside chat as we discuss growing healthy open-source communities with Brian Douglas, Developer Advocate at GitHub.
Video

  • 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!

  • structure
  • knowing who to talk to
  • documentation
  • steps how to contribute
  • the architecture
  • structuring the project with promotion paths

  • hierarchy of advancement in open source projects
  • allows for buying and learning
  • setting clear paths for learning and advancement

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

  • 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.
Export as PDF
Copy link
On this page
Summary:
Scribbles:
Characteristics of a good open-source community...
Ladder Model for Open Source
Tackling imposter syndrome...?