Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal to create a process to become Community Manager #766

Open
benjagm opened this issue Jul 11, 2024 · 2 comments
Open

Proposal to create a process to become Community Manager #766

benjagm opened this issue Jul 11, 2024 · 2 comments

Comments

@benjagm
Copy link
Collaborator

benjagm commented Jul 11, 2024

Hello JSON Schema Community,

As many of you know, our previous model of having a full-time paid Community Manager has benefited our community. However, due to recent changes, we need to establish a new, transparent process for selecting Community Managers. This will allow JSON Schema contributors to take on the role for a designated period, ensuring continuity in this role and also sustainability of the project.

Taking inspiration from the DAPR Community Manager process, I propose the following process:

Proposed Community Manager Selection Process

  1. Eligibility Criteria:
  • Active contributor to JSON Schema for at least the past six months.
  • Demonstrated history of positive engagement with the community.
  • Strong understanding of JSON Schema specifications and ecosystem.
  • Commitment to dedicating a specified number of hours per week to community management activities.
  1. Nomination Process:
  • Self-nominations and peer nominations are both accepted.
  • Nominees must submit a brief application outlining their qualifications, vision for the community, and availability.
  • Applications will be reviewed by the core maintainers team.
  1. Selection and Term:
  • Community Managers will be selected by consensus among the core maintainers.
  • The term for each Community Manager will be six months, with the possibility of renewal based on performance and community feedback.
  • A maximum of two consecutive terms may be served to ensure fresh perspectives and prevent burnout.
  1. Responsibilities:
  • Moderating community discussions and ensuring a welcoming environment.
  • Organizing and facilitating community meetings and events.
  • Acting as a liaison between the community and the core maintainers.
  • Providing regular updates to the community on key developments and initiatives.
  • Managing community resources and documentation.
  1. Accountability and Feedback:
  • Regular check-ins with the core maintainers to discuss progress, challenges, and feedback.
  • Community Managers will solicit feedback from the community regularly and adapt strategies as needed.
  • At the end of each term, a retrospective will be conducted to assess the Community Manager's performance and gather input for future improvements.

Next steps

We invite everyone to provide their thoughts and feedback on this proposed process. Your feedback is so important to ensure we have a fair and effective policy. Please share your comments!!

Thanks!!

@jdesrosiers
Copy link
Member

This is a great idea. Since this is such an important and time consuming role, I wonder if it's possible to offer some compensation even if small from our open collective funds.

@benjagm
Copy link
Collaborator Author

benjagm commented Jul 26, 2024

I wonder if it's possible to offer some compensation even if small from our open collective funds.

That is possible but my personal opinion is Community Management can be managed as just another type of contribution without having to receive monetary compensation like other contributors like maintainers, spec authors or TSC members.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants