Create a guide of Public Code Communities

[AlbaRoza]

To be completed. Some ideas so far:

• Several phases: research, write, review and publish.

• Must include:

  • Definition. What is public code, what is open source, what is a community. Minimum people to consider it community, how to start a community, common mistakes to avoid, etc.
  • Why communities in public organizations and the ones in private companies are different, but also their touch points. Specific ideas to run public
  • User personas. Who are you going to find in these communities and how to take care of them. Not only distinguishing in between their roles: project manager, developer, designer, communications, etc., but also in their participation on the specific community: maintainer, lurker, fire soul, etc.
  • Communities of practice: peer to peer conversations. Attach thesis from Barcelona.
  • Resources. Key assets make the community grow, figure out success, checklists with minimum requirements when managing a community, toolkit, how to organize events, meetups, hackathons (at also online ones), importance of social media presence and interactions to grow your community, etc.
  • Tips and tricks. Mentorship program, burnout pre-detection strategy in maintainers, influencers, etc.
  • Lessons learned.

[lscheske]

This guide sounds like a really useful asset, almost like the Standard, but then about communities. Does it focus on communities around a codebase (and would therefore be a kind of guidance document for the "community" pillar of codebase stewardship), or is it intended to be more generically about communities in public code?

Also - cross check the OSOR guidelines for sustainable open source communities, as this might cover a lot of content that you propose. Of course we could make it more actionable and provide more ideas about how things are done.

Would it "live" on the website or on About?

[ElenaFdR]

Rather than publishing this as an all or nothing deal, could you test some of your ideas and get feedback by publishing some of these sections initially as blogposts?

[ElenaFdR]

Re "Would it "live" on the website or on About?"

This is akin to the Standard or the Governance Game - a resource we independently produce for ourselves and others to use. As such, it belongs on neither publiccode.net or about.publiccode.net - it would be its own repo indexed from projects.publiccode.net.

[AlbaRoza]

Rather than publishing this as an all or nothing deal, could you test some of your ideas and get feedback by publishing some of these sections initially as blogposts?

Sure, we can definitely work on something like that

[AlbaRoza]

This guide sounds like a really useful asset, almost like the Standard, but then about communities. Does it focus on communities around a codebase (and would therefore be a kind of guidance document for the "community" pillar of codebase stewardship), or is it intended to be more generically about communities in public code?

I was thinking on making something a bit more generic: Communities that work in the open with Public Code. And if you ask me, yeah, I would love to make it accesible and downloadable from our website!