# Procedures Community Summit Date: 2023 August 22 Tuesday 1:49 pm Attendees: Tags: Blog best comment, RFC, /latest, deadlines impact teams and outside, Who‘s the audience - updates, projects, Does this need: marketing, polyglots, accessibility --- # Goals / agenda 1. # Discussion notes - ## My prep Communicating on Make Team blogs: discussions, proposals, announcementsPart [1](https://communitysummit.wordcamp.org/2023/session/communicating-on-make-team-blogs-discussions-proposals-announcements/) & [2](https://communitysummit.wordcamp.org/2023/session/communicating-on-make-team-blogs-discussions-proposals-announcements-continued/) Noting that some of this, such as action items, will then need to carry over to _[Communication and collaboration: finding your way around WordPress](https://communitysummit.wordcamp.org/2023/session/communication-and-collaboration-finding-your-way-around-wordpress/)_. ## Audience:  - Active Contributors - Primary team communication - Cross-team collaboration - Wider community  - Feedback on proposals - Participation in outcomes ## **Value**:  - Call people in - RFCs - Clear decision shared - Track decision has been implemented and progressing - Cross-team collaboration --- ## Areas of Confusion: 1. What is the Meta team? The Meta team makes WordPress.org, provides support, and builds tools for use by all the contributor groups. If you want to help make [WordPress.org](http://wordpress.org/) better, sign up for updates from the Meta blog. Should all cross-collaboration then happen in Meta? Or should the primary topic of Meta be DevOps, .org, and Systems related?  What posts then belong on Meta, vs Project, vs Sustainability?  2. Who is the intended audience of [/Updates](https://make.wordpress.org/updates)? 1. Should the Team Rep page be revised to include the current requirements of teams to publish on /Updates? (There is a session about team reps happening that can be decision makers on this) 4. How is that different than /[Project](https://make.wordpress.org/project)? "This p2 is for [all-project communications and cross-team collaboration](https://make.wordpress.org/project/2021/06/03/welcome-to-make-wordpress-org-project/). It's a place to host and find discussions that affect all teams, and WordPress' “back-office” work more transparent." 5. Could /[latest](https://make.wordpress.org/latest) help teams with their collaborative efforts? 1. What it helps vs what is not apparent 7. When polished announcement posts appearl on various tram sites without much team awareness before 8. When does it make sense to set a policy to request feedback from  1. Accessibility 2. Design 3. Marketing 4. Polyglots 5. Meta 10. How do prioritize the input of each better? Should one team’s capacity block another from moving forward?  --- ## Tools Less of our focus, but common tools where decisions happen: - Make sites - GitHub - some repos are not attached to teams such as the [5ftF repo](https://app.slack.com/github.com/wordpress/five-for-the-future) - Slack - specific channels for topical help like `github-teams-collab` are great if you know they exist - Trac ## Challenges - How do we elevate these? It can feel overwhelming even within a single team. - How do we provide adequate time for - full time sponsored - part time sponsored - self/non-sponsored - Wider community, news cycle, etc.  --- ## Understanding RFCs in Open Source: Empowering Collaboration and Decision-Making  **Introduction** In the dynamic world of open source projects, collaboration and effective decision-making are paramount. One powerful tool that has emerged to facilitate this process is the "Request for Comments" or RFC. Let's delve into what RFCs are, how they're utilized in the open source realm, and explore why the WordPress project should consider adopting them. **What are RFCs?** A Request for Comments (RFC) is a proposal to modify a particular aspect of a project. RFCs are utilized to propose significant changes that impact various dimensions of the project. These changes may encompass community governance, architectural modifications, legal or financial designations, as well as high-level technical features. **Utilizing RFCs in Open Source** The open source ecosystem thrives on collaboration and inclusivity. RFCs play a crucial role in this environment by offering a structured approach to introduce substantial changes. Let's explore how they're used: - **Proposal Phase** - A community member, like yourself, initiates an RFC proposal, outlining the proposed change. - This proposal is then shared with the community, sparking discussion and feedback. - **Discussion and Collaboration** - The community engages in constructive discussions around the proposal, sharing insights, concerns, and potential improvements. - This phase encourages diverse perspectives, enabling a comprehensive evaluation of the proposal's impact. - **Modification for Refinement** - Taking into account community feedback, the proposer can refine and modify the initial proposal. - This iterative process enhances the proposal's quality and addresses potential pitfalls. - **Final Comment and Vote** - After refining the proposal, a final comment and voting phase commences. - The project steering committee, along with community members, vote to accept or reject the proposal. - **Implementation and Notification** - If the proposal is accepted, the community is notified, and the changes are implemented. - This marks the transition from a shared idea to a tangible reality. **Benefits of RFCs** The adoption of RFCs in open source projects, like The Good Docs Project, brings forth a range of benefits: - **Empowerment and Collaboration** - RFCs empower community members, like you, to actively contribute ideas for project enhancement. - The collaborative nature of RFC discussions taps into the collective wisdom of the community, fostering innovation. - **Transparent Decision-Making** - RFCs provide transparency in decision-making by involving the entire community. - This inclusivity ensures that key decisions are not confined to a select few but are made collectively. - **Reduced Risk and Improved Proposals** - Feedback obtained through RFC discussions enhances the quality of proposals. - Potential risks are identified and mitigated, resulting in more robust changes. - **Democratic Governance** - The RFC process prevents a single individual from becoming a bottleneck or gatekeeper. - This democratic approach aligns with the ethos of open source collaboration. - **Why WordPress Should Adopt RFCs** - **Inclusive Decision-Making** - RFCs would enable WordPress contributors to collectively shape the project's future, embracing diverse perspectives. - **Enhanced Quality** - RFCs ensure that significant changes are thoroughly discussed, resulting in more refined and impactful enhancements. - **Community Engagement** - The collaborative nature of RFC discussions can further engage contributors and enthusiasts, creating a vibrant ecosystem. # Action items - [ ] Meeting Notes Distributed to the Team - [ ] Tasks & Projects Completed, Processed or Delegated - [ ] Key Dates Completed or Scheduled