🕉️ Community and Outreach WG Charter

🚀 WG 👋 Community & Outreach WG
1

Community growth, partnerships and public outreach.

SUMMARY
Version 1.0
Mission Building a diverse and engaged community through clear communication, transparent governance, and by forging strategic partnerships that accelerate the project’s adoption and success.
Chair(s): @nortse000
Communication: - Discord Channel - GitHub Team - Google Calendar
Documentation: - PRD(Requirements) - Github Project Board - Visuals - Meeting Minutes

Charter Details

1. Mission and Scope

  • Mission: This Wroking Group’s mission is to build a diverse and engaged community through clear communication, transparent governance, and by forging strategic partnerships that accelerate the project’s adoption and success.
    • Example: “To provide a reliable, scalable, and secure infrastructure for project development and deployment.”
  • In Scope: A bulleted list of what this WG is responsible for.
    • Example: Managing the project’s CI/CD systems.
    • Example: Owning and maintaining the project/infra code repository.
    • Example: Defining and enforcing data backup and recovery policies.
  • Out of Scope: A bulleted list of what this WG is explicitly not responsible for, to prevent ambiguity.
    • Example: Managing user-facing application features.
    • Example: Setting the project’s overall strategic direction.

2. Responsibilities and Deliverables

  • Core Responsibilities: A clear, bulleted list of the WG’s ongoing duties.
    • Example: Triage and prioritize bugs and feature requests related to owned assets.
    • Example: Review and merge pull requests against owned repositories.
    • Example: Publish a quarterly status report to the community.
  • Key Deliverables: Tangible services or products the WG provides.
    • Example: A stable and documented build and test environment.
    • Example: Public-facing dashboards for system health and performance.

3. Governance and Decision Making

  • Decision-Making Process: How does the WG make decisions?
    • Example: “Decisions are made by lazy consensus. Proposals are posted to the mailing list for 72 hours. If no objections are raised, the proposal is accepted. If there are objections, a formal vote is held during the next meeting, requiring a simple majority to pass.”
  • Conflict Resolution: How are disagreements handled?
    • Example: “Disagreements are first discussed within the WG. If a consensus cannot be reached, the WG Chair makes the final call. Decisions can be appealed to the project’s Steering Committee.”

4. Membership and Roles

  • Joining: How does someone become a member?
    • Example: “Membership is open to any contributor who has had at least 3 non-trivial pull requests merged within the WG’s owned repositories. Prospective members can be nominated by an existing member at a WG meeting.”
  • Member Responsibilities: What is expected of members?
    • Example: Attend at least 50% of scheduled meetings per quarter.
    • Example: Actively participate in discussions, code reviews, and bug triage.
  • Roles and Responsibilities:
    • Chair/Lead: [Define how the Chair is selected, their term length, and their duties, e.g., running meetings, representing the WG].
    • Tech Lead: [Define how the Tech Lead is selected and their duties, e.g., setting technical direction, approving major architectural changes].
  • Stepping Down: How does a member leave the WG?
    • Example: “Members may step down at any time by notifying the WG Chair. Inactive members who do not meet participation requirements for two consecutive quarters will be moved to emeritus status.”
  • Current Members:

WG Meeting Calendar

  • Meetings: [e.g., 2nd Tuesday of each month, 16:00 UTC]
  • Meeting Minutes: [Link]

Related WGs and Groups

Useful Links