tag-contributor-strategy

tag-contributor-strategy copied to clipboard

working here: https://hackmd.io/wZleAQC2SPCtQoUzZFNOJw

There needs to be a requirement for graduated projects with more than 1k contributors for community support as it's a lasting function that needs continuous support.

There are a number of ways to do community management for an open source project, including cncf services. Let's draw those out in a doc and list what they are, why, benefits, etc. good end goals could be a) a doc for guidance and b)eventually come up with a recommendation for TOC for graduated projects.

examples of graduated project strategies:

• should there be a part time, full time community manager(s)?
• should there be committees, working groups, sigs = some kind of group that would cover community (ex: sig-contributor-experience)
• are community operations are included in all roles or some roles that are defined and have ownership?

working here: https://hackmd.io/wZleAQC2SPCtQoUzZFNOJw

closed the wrong one

Further, a maintainer refresh strategy with clearly defined roles/responsibilities and requirements to become one should exist as part of a robust Sustainment program.