search

DevRel-Foundation / governance

DevRel Foundation Governance
Creative Commons Attribution 4.0 International
25 stars 4 forks source link

readme

[!NOTE] Work-in-progress document. People can contribute to its content by submitting a Pull Request or raising an Issue

There is a work-in-progress Frequently Asked Questions document that provides further details about the model, progress, and scope of the Developer Relations Foundation's formation. To learn more, please visit our FAQ section here.

Developer Relations Foundation Governance

Developer Relations Foundation is a community-driven project, with no funding involved. This repo was created with the aim of helping community participants better understand how DevRel Foundation operates.

At this point, part of the community calls are being used as Open Office Hours to reach community consensus on the foundation's next steps and governance process. People can access the APAC, EMEA, and AMER calls to get involved here.

🧭 Volunteer Steering Committee Member Responsibilities
The Volunteer Steering Committee is comprised of the initial group of individuals, all tenured Developer Relations and Developer Marketing leaders, who connected over the shared vision of creating a foundation. The primary responsibilities of the Volunteer Steering Committee are: - Established the initial charter and governance model that contributed to the LF's "intent to form" commitment - Collect input on priorities and interest in getting involved to move forward on processes, policies, and frameworks that will be driven by working groups, as well as forming the initial working groups - Internal project management and operations, including PR, community, website development, and communications Out of the working groups, we anticipate recommendations on governance that will include how to elect Foundation leadership moving forward. At that time, any leadership roles we play (if at all) will be determined through the established election processes.

Our Playbook - Operational Guidelines

The DRF Playbook serves as a hands-on resource for the community. While the Charter provides a general overview of the project’s structure and governance, the Playbook covers specific operational details that ensure smooth participation and collaboration. It includes guidelines on how community participants can submit new proposals, where and how these proposals are discussed via community calls, and the community calls roles and responsibilities.

DRF Community Calls

This group hosts community calls every other week. People can check the times and upcoming calls in the Groups.io calendar: https://lists.dev-rel.org/g/community/calendar

These calls serve two main purposes:

  1. A neutral and safe space to discuss topics important to the community, share ideas, and ask questions aligned with the mission of the DevRel Foundation. If you have a story to share, the recommended process is to open a new issue via GitHub Discussions (more info below) with the topic in mind. This allows the call moderators to bring these topics into sessions, initiate community discussions, and reach a consensus, potentially leading to a concrete action item (e.g., should this become a working group or be included in the foundation, etc.).
  2. Open Office Hours to reach community consensus on the foundation's next phases and to address questions and blockers on DevRel Challenges and Frequently Asked Questions.
📚 How to File Proposals and Discussion Topics The community can file proposals via the DRF Governance repo by [opening a new entry in the GitHub Discussions Forum](https://github.com/DevRel-Foundation/governance/discussions/new/choose). Also, whether you are new to the DRF community calls or a regular participant, you can add your discussion topics as a comment in one of the [meeting note discussions](https://github.com/DevRel-Foundation/governance/discussions/categories/meeting-notes) or bring them up during the call. People can also share DevRel use cases, best practices, frameworks, and more by [opening a new Idea in GitHub Discussions](https://github.com/devrel-foundation/governance/discussions/new?category=ideas), which serves as the Foundation’s public forum. We are always looking for 5-10 minute presentations in future community calls to spark discussion with attendees and asynchronously.
📚 Roles in the DRF Community Calls Roles include facilitator, moderator, scribe, and crier. Anyone can volunteer to take on any of these roles for upcoming community calls. People can volunteer to lead in one of these roles during the next call by contacting steering-committee@dev-rel.org | **Role**| **Responsibilities**|**Notes**|**Recommended Experience**| |---------|---------------------|---------------|---------------| |**Moderator**| (1) Leads the discussion by going through agenda items, ensuring each topic receives the time it needs, and keeping conversations focused AND (2) Opens the call by inviting participants to add their names to the agenda, make group introductions and introduce the concept of Chatham House Rules, LF Antitrust Policies and the DRF Code of Conduct | Volunteering as a Moderator is a great way to develop facilitation skills and play an essential role in shaping community discussions. The Moderator must be on the call while the Crier can skip the call | This person attended some previous community calls and is familiarized with the format | |**Scribe**| (1) Captures and summarizes key points during the call AND (2) share these notes with the community in the dedicated GitHub Discussion afterward| Serving as a Scribe builds attention to detail and provides a vital resource for transparent communication within the community | This person can be new to the community but should have some experience of taking notes in meetings | |**Crier**| (1) Keeps the community informed by announcing the agenda one week in advance in the DRF community mailing list and Discord channel| As the Crier, you enhance community engagement and ensure members are aware of discussion topics and opportunities to participate. The Moderator must be on the call, while the Crier can skip the call | This person can have no experience and be a newcomer |

📚 DRF Community Calls Checklists All participants, including the moderator, crier, and scribe, must be familiar with and agree to follow the [code of conduct](https://github.com/DevRel-Foundation/governance/blob/main/code_of_conduct.md) and [antitrust policies](https://www.linuxfoundation.org/legal/antitrust-policy) when engaging in DRF activities ## Moderator When running a community call, please ensure you go through the following checklist: Pre-Call (5-4 days in advance) 1. Please wait for the Crier to share the agenda. If the agenda hasn’t been announced and only 5 days remain before the call, kindly reach out to the Crier 2. Review new community proposals or announcements shared on GH Discussions and include in the agenda During the Call 3. Welcome Atendees and invite them to write their names in the Google Doc 4. Go through Agenda Topics 5. Assign the roles for the next call 6. Keep teh conversation on track 7. Close the call on time ## Crier Pre-Call (8-6 days in advance) 1. Go to https://github.com/DevRel-Foundation/governance/discussions 2. Open a new entry 3. Copy Agenda template https://github.com/DevRel-Foundation/governance/discussions/114 4. Edit brackets' info [ ] 5. Go to [google doc](https://docs.google.com/document/d/1I5dX4RbvJyt4Z2dTWsS1BjmzRQV8RHOJ5klJ_tZa_eg/edit?usp=sharing) 6. Copy content within `TEMPLATE - YYYY-MM-DD` 7. Paste bellow `Next Meeting`section 8. Edit brackets' info [ ] 9. Announce the GH discussion via Discord #📆weekly-calls channel using @everyone tag 10. Announce via community Mailing List (community@lists.dev-rel.org) https://lists.dev-rel.org/g/community 11. Ping the Moderator when work is finished ## Scribe During the Call 1. Take notes in [google docs](https://docs.google.com/document/d/1I5dX4RbvJyt4Z2dTWsS1BjmzRQV8RHOJ5klJ_tZa_eg/edit?usp=sharing) below the agenda items. Avoid using affiliations, just use initials of participants 2. If there's someone on the call who did not added their name, add it yourself in the Google doc After the Call 3. Syntetize notes and mirror these notes in the GH discussions dedicated entry as a new comment for those who can't access google ## Additional Training If it's your first time taking on one of these roles in an open source project, don’t worry—we’re all learning together! This free course on [Leading High-Performance Working Group Meetings](https://training.linuxfoundation.org/training/leading-high-performance-working-group-meetings-lfc120/) can help beginners navigate through these roles.
📚 How to volunteer to be a moderator, scribe, or crier? - Go to Discussions: https://github.com/DevRel-Foundation/governance/discussions - Leave a comment in the first meeting note issue you see, expressing your interest in volunteering for any of these roles for an upcoming meeting - The project manager will reach out to confirm your availability and assign you for the next call