MDN Community: Discussion guidelines

files/en-us/mdn/community/discussions/index.md

@@ -12,9 +12,11 @@ On MDN Web Docs, we encourage our community to start and/or engage in discussion
 If you see something wrong on MDN Web Docs, it's best to open a GitHub issue in the [relevant MDN GitHub repository](https://github.com/mdn/).
 If you're not sure whether to open an issue or start discussion, consider the following guidelines:
 
-- Issues are for reporting a bug or a work item with clearly defined and actionable tasks and outcomes.
-- Discussions are the right place if an issue needs a discussion to agree upon a course of action or define an actionable piece of work.
-  heck out the subject of each discussion category below so that you can start your discussion in the proper place.
+- Issues should be used for reporting a bug or a work item with clearly defined and actionable tasks and outcomes.
+- Use Discussions when an issue requires a dialogue to agree upon a course of action or define an actionable piece of work.
+- If your discussion doesn't progress or you're unsure of the next steps, refer to the [Guidelines for managing and resolving discussions](/en-US/docs/MDN/Community/Discussions/Managing_and_resolving_discussions) for advice on moving forward, including expectations on timelines.
+
+Check out the subject of each discussion category below so that you can start your discussion in the proper place.
 
 <table>
   <thead>

files/en-us/mdn/community/discussions/managing_and_resolving_discussions/index.md

@@ -0,0 +1,53 @@
+---
+title: Managing and resolving discussions
+slug: MDN/Community/Discussions/Managing_and_resolving_discussions
+page-type: mdn-community-guide
+---
+
+{{MDNSidebar}}
+
+The MDN community is encouraged to [initiate, engage in, and resolve discussions](/en-US/docs/MDN/Community/Discussions) related to the MDN Web Docs documentation.
+
+While most discussions reach a broad agreement quickly, some may stall due to an unclear path to a resolution, often because of differing opinions. This document outlines the process and strategies to move discussions toward a resolution within a reasonable timeframe (we'll define what's an acceptable timeline later in this document).
+
+## Moving a discussion to a resolution
+
+Most discussions do not need a formal resolution process. These MDN discussion guidelines are here for the discussions that aren't moving forward toward a conclusion or would otherwise benefit from a formal process:
+
+1. Each discussion is held / rooted in a [discussion on Github](https://github.com/orgs/mdn/discussions), which is the "source of truth" for the topic.
+
+2. Each topic of discussion needs a driver. The driver is responsible for:
+
+   - Guiding the conversation.
+   - Making people aware the discussion exists.
+   - Setting the timeline, informing people of it, changing the timeline as necessary, and sticking to the timeline as appropriate.
+   - Informing all the appropriate channels - Slack, Discord, tagging people on GitHub, and other channels if appropriate - of needed feedback by specific dates.
+   - Bring up the topic in community and weekly meetings.
+   - Organizing a synchronous, online face-to-face meeting if required (if there is disagreement). Face-to-face meetings should be rare and only if required (See #3).
+   - Summarizing face-to-face conclusions in the relevant discussion on [Discussions](https://github.com/orgs/mdn/discussions).
+   - Guiding the implementation of the discussion results or working with the appropriate team lead to ensure that the results are implemented.
+
+3. Face-to-face meetings regarding a discussion should only be called if there is disagreement.
+
+   - Face-to-face meetings must be announced in all relevant [communication channels](/en-US/docs/MDN/Community/Communication_channels), such as Slack, Discord, GitHub discussion, etc.
+   - Conclusions of each face-to-face meeting must be entered into the GitHub discussion, which remains as the source of truth for the discussion.
+   - The driver is responsible for calling the meeting, informing all parties, reporting results back into the GitHub discussion.
+
+Once agreement has been achieved, the discussion can be closed, the resolution announced, and the plan for implementing the resolution can be put it into action!
+
+## Expected turnaround times for discussions
+
+Every discussion will have a different timeline depending on the complexity of the topic and the consensus levels. Ideally, most discussions should be resolved within two months, allowing for the topic to be addressed at various internal meetings. This timeframe ensures diverse viewpoints are considered and everyone interested has the opportunity to contribute to the discussion.
+
+1. Post the discussion and assign a driver.
+2. Identify any key stakeholders and needed approvers (the individuals who need to weigh in on the topic and give their approval), if any.
+3. Inform the approvers and other essential voices of the discussion and your proposed timeline. If needed, reach out to them again after 2 weeks, and weekly thereafter, until they provide feedback.
+4. Add the discussion topic to the agendas of relevant meetings.
+5. After a month, sort through the feedback, discussions, and agreements, and formalate an initial plan merging the feedback into a possible action plan. Re-inform and re-request feedback from all interested parties, including everyone who participated in the discussion in any way.
+6. During the second month, keeping reaching out the the community for feedback on the proposed plan, making updates to the plan in light of any new feedback. Rinse. Repeat.
+7. If there are points of contention, arrange an online, synchronous, face-to-face meeting to resolve any remaining disagreements (as captured in the discussion thread).
+8. Keep the discussion threads alive during the second month as you work with the community towards the resolution.
+9. [Create an issue](/en-US/docs/MDN/Community/Issues) with the final plan for implementing the resolution and put it into action.
+10. Close the discussion.
+
+If the discussion involves reaching out to and receiving feedback from experts, the timeline above can be extended as needed.