The Stepping Away of a Team Member  ## Metadata - Author: [[Make WordPress Documentation]] - Full Title: The Stepping Away of a Team Member - Category: #articles - Document Note: --- tags: - #wordpress - #WPDrama - #open_source - #community_governance Author: Make WordPress Documentation Source: Make WordPress Reference: https://make.wordpress.org/docs/2025/09/19/the-stepping-away-of-the-team-member/ date created: 2025-09-19 00:00 --- # Title: The stepping away of a team member ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - Make WordPress Docs post “The stepping away of a team member” ## 📝 Summary: The Docs team announced that leadership asked contributor Jenni McKinnon to step away after she posted comments misaligned with team direction during discussions about release documentation responsibilities. Leadership attempted private de-escalation; when behavior continued, they requested a pause to reassess involvement, with openness to future rejoining. The team apologized to the community and affected individuals, clarifying the comments do not represent Docs team views. ## 📖 Main Content: - Context: Structural changes to the WordPress release squad prompted discussions on the Documentation team’s role in release docs. - Conflict: A team member (Jenni) made public comments calling for broad project changes and removal of certain leaders—seen as misaligned with Docs team intentions. - Process: Leadership engaged privately to de-escalate and asked for the comments to stop. - Outcome: Requested Jenni step away temporarily to reassess involvement; potential future re-entry if aligned with best outcomes. - Accountability: Public apology; clarification that the comments do not reflect official team positions; commitment to prevent misperception. ### 🗒️ Notes - Trigger - Release squad structure change led to role clarification discussions. - Cross-team coordination: Docs, Core, release squad, Mary Hubbard. - Behavior cited - Public comments advocating sweeping changes across the project. - Requests to remove specific leaders. - Viewed as out of alignment with Docs team’s intentions. - Leadership response - Private outreach and de-escalation attempt. - Clear ask to cease certain public comments. - Continued behavior led to temporary step-away request. - Resolution and forward path - Time-limited stepping away to reassess involvement. - Will explore future rejoining if mutually beneficial. - Communication to community - Apology to community and individuals named. - Clarification of official team stance vs. individual comments. - Emphasis on protecting team coherence and project outcomes. ## 📖 References: - The announcement itself: https://make.wordpress.org/docs/2025/09/19/the-stepping-away-of-the-team-member/ ## 🗣️ Paraphrase: - Original idea: Leadership asked Jenni to step away after misaligned public comments during release-docs role discussions; private de-escalation failed. - Paraphrase: Following disagreements over how release documentation should be handled, and after private attempts to resolve tensions, Docs leadership requested that Jenni temporarily pause her participation due to continued posts calling for sweeping changes and leadership removals. - Original idea: Apology and clarification that Jenni’s comments don’t represent the team; openness to future re-engagement. - Paraphrase: The team apologized to both the broader community and those referenced, stressing that the statements were personal, not official, and indicating willingness to consider her return when alignment is restored. ## 📰 Newsletter: WordPress community update: The Docs team shared that, amid recent release squad changes, they’ve asked a contributor to step back following public comments that diverged from the team’s direction, including calls for leadership changes. After private de-escalation attempts, they issued a pause and an apology clarifying the views were not the team’s. What to watch: evolving roles in release documentation and cross-team coordination. Learning corner: brush up your core contribution skills—PHP, JS, Git, and docs standards—to help during release cycles. New and noteworthy plugins: keep an eye on documentation tooling enhancements and editorial workflow plugins to streamline contributor reviews. Community highlights: respectful dialogue and transparent governance remain essential to sustainable open source. Read the announcement for context: Make WordPress Docs’ “The stepping away of a team member.” ## ✅ Action Items: - Draft a balanced contributor engagement prompt highlighting: - Alignment: Tie release-doc responsibilities to clear team charters and cross-team agreements. - Governance: Emphasize constructive escalation paths and codes of conduct. - Education: Offer workshops on “Public discourse in OSS projects,” moderation best practices, and consensus-building. - Transparency: Propose a lightweight decision log for role definitions during releases. - Sustainability: Advocate funding for facilitation/mediation roles to reduce burnout. - OSPO trajectory: Map this case to policies on contributor conduct, conflict resolution, and re-entry pathways. Prompt to use with future articles: “Analyze how this article informs open-source advocacy, contributor onboarding, and sustainable governance within WordPress. Identify: - Where transparent decision-making and inclusive processes are upheld or lacking. - Implications for educator-led interventions (curricula for PHP/JS/docs, Git/GitHub onboarding). - Strategies to increase contributor retention and psychological safety. - Policies an OSPO should formalize (role charters, escalation routes, moderation, re-engagement criteria). - Communications framing that balances individual voice with team representation. Provide a 90-day action roadmap aligning with community health metrics.” ## 🧪 Hypotheses: - Clear role definitions during release cycles reduce public conflicts in contributor communications. - Early, structured mediation decreases the likelihood of escalation to temporary removal. - Public clarification posts paired with re-entry criteria improve trust and contributor return rates. ### 📊 Methodology: - Data sources: Make blogs, Slack logs (public), issue trackers, moderation records, Code of Conduct reports. - Designs: Interrupted time series before/after role charter publication; case-control comparing releases with/without charters. - Analysis: Sentiment analysis of discussions, survival analysis on contributor retention, qualitative coding of conflict episodes. ### ❓ Questions: - What are explicit criteria for “misalignment” and who adjudicates them? - What’s the standard re-entry process and timeline? - How are release-doc responsibilities documented across teams? - What safeguards protect dissent while curbing disruption? ### 🔮 Future Research: - Impact of mediation training for team reps on conflict frequency. - Model re-entry frameworks that balance accountability and inclusion. - Governance patterns for cross-team release documentation. ### 💡 Implications: - Clear charters and mediation protocols can stabilize release cycles. - Re-entry pathways may prevent long-term contributor loss. - Documented escalation routes can serve as policy templates across OSS projects. ### 🧠 Learning Styles Assessment: - Readability: Upper high-school to early college; short, formal announcement. - Visual: Minimal; add a process diagram of escalation and re-entry. - Aural: Provide an audio summary or brief podcast clip. - Verbal: Language is concise; add links to guidelines and examples. - Kinesthetic: Include “try-it” steps for conflict resolut - Summary: The Documentation team’s leadership has asked Jenni McKinnon to step away from the team. Recent changes in the structure of the WordPress release squad started a discussion about the role of the Do… - URL: https://make.wordpress.org/docs/2025/09/19/the-stepping-away-of-the-team-member/ The Documentation team’s leadership has asked Jenni McKinnon to step away from the team. Recent changes in the structure of the WordPress release squad started a discussion about [the role of the Documentation team in documenting the release](https://make.wordpress.org/docs/2025/09/10/docs-team-participation-in-wordpress-releases/). While the team was working with the Core team, the release squad, and Mary Hubbard to find a solution for this and future releases, Jenni posted comments that were out of alignment with the team, including calls for broad changes across the project and requests to remove certain members from leadership roles. This ran counter to the Documentation team’s intentions. Docs leadership reached out privately in an effort to de-escalate the situation and asked Jenni to stop posting such comments, but this behaviour did not stop. As a result, the team has decided to ask her to step away for a period of time to reassess her involvement. We will work with her to explore rejoining the team in the future, if it aligns with the best outcomes for both her and the team. As a team, we apologise to the community and to the individuals mentioned for any inconvenience these comments have caused. These do not reflect the views of the Documentation team, and we are committed to ensuring that they are not perceived as such., The Stepping Away of a Team Member, Make WordPress Documentation, 01k5hhcta0ge92ywqzz2wjcfbw.