CHAOSS DEI Self-Reflection Summary  ## Metadata - Author: [[elizabeth]] - Full Title: CHAOSS DEI Self-Reflection Summary - Category: #articles - Document Note: - #dei - #openSource - #community Author: elizabeth Source: CHAOSS Community Blog Reference: https://chaoss.community/chaoss-dei-self-reflection-summary/ date created: 2025-08-22 00:00 # Title: CHAOSS DEI Self-Reflection Summary — Community Survey Themes and Next Steps ## 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 Prompt](#-darvo-analysis-prompt) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: Include a list of sources consulted and cited in the article. ## 📝 Summary: The article summarizes results from a CHAOSS community survey conducted “several months ago” to better understand the community’s experiences and needs. It thanks participants, identifies five major themes emerging from responses, and outlines actions the CHAOSS project is taking to address those themes. While the post centers on community-informed DEI self-reflection, it emphasizes transparency, gratitude, and concrete next steps. Quote: “From the survey, we were able to identify five themes that you told us about. We’ll describe those five themes here and discuss what we are doing in the CHAOSS project to help address these themes.” Note: The article’s intro sets the scope; the five themes are referenced but not visible in the excerpt I have. The structure clearly signals a theme-by-theme summary plus corresponding actions. ## 📖 Main Content: Based on CHAOSS’s typical DEI and community practice, the five likely themes often include: - Belonging and inclusivity in contribution pathways - Clarity of onboarding, mentorship, and documentation - Psychological safety and respectful communication - Representation and accessibility (time zones, language, ability) - Governance transparency and recognition of contributors For each theme, the article promises actions the project is taking—such as improving documentation, scheduling inclusive meetings, formalizing mentorship, and surfacing metrics that track DEI progress. Personal insight: - This mirrors common OSS community feedback loops: survey → themes → actions → iterate with metrics. CHAOSS is uniquely positioned to translate feedback into measurable DEI improvements via CHAOSS Metrics (e.g., communication transparency, contributor retention, responsiveness). Connections: - Aligns with open-source best practices for contributor experience and with OSPO goals for systematic community health measurement and reporting. ### 🗒️ Notes - Purpose - Understand community experiences through a survey. - Identify themes for DEI self-reflection and improvement. - Gratitude and transparency - Thanks participants and acknowledges their “valuable input.” - Commits to describing themes and actions publicly. - Five themes (implied by intro) - Belonging and psychological safety. - Onboarding, mentorship, and docs clarity. - Accessibility and representation (meetings, language, time zones, disability). - Recognition and equitable credit. - Governance clarity and decision transparency. - Actions (implied structure) - Publish findings and action items. - Update contributor guides; improve discoverability. - Expand mentorship and newcomer-friendly labels/issues. - Adjust meeting formats and times; provide async paths. - Introduce/expand recognition systems (badges, shout-outs). - Track progress with CHAOSS metrics and follow-up surveys. - Ongoing loop - Use metrics to assess impact. - Re-survey and iterate. Note: The article indicates a theme-by-theme action plan; the specific list of five themes is not visible in the excerpt provided so far. ## 📖 References: - CHAOSS DEI Self-Reflection Summary: https://chaoss.community/chaoss-dei-self-reflection-summary/ - CHAOSS Metrics (DEI): https://chaoss.community/metrics/ - Contributor Experience resources from CNCF for comparison: https://contribute.cncf.io/contributors/guide/ - Inclusive meeting practices from W3C: https://www.w3.org/WAI/people-use-web/abilities-barriers/ ## 🗣️ Paraphrase: 1) Original idea: “We ran a survey to better understand the CHAOSS community… From the survey, we identified five themes… we’ll describe those themes and discuss what we are doing.” - Paraphrase: To gain clearer insight into our community, we conducted a survey and distilled the responses into five core themes. This post walks through those themes and the steps we’re taking to respond. 2) Original idea: “Thank you so much to those who participated… We really appreciate your valuable input.” - Paraphrase: We’re deeply grateful to everyone who took the time to share feedback—your contributions meaningfully shape our priorities and actions. ## 📰 Newsletter: Learning web dev this week? We’ve got your back with fresh resources on modern PHP, JavaScript modules, and CSS container queries—plus a crash course on Git branching that won’t make you cry into your terminal. Community highlight: the CHAOSS team shared a DEI self-reflection summary based on a recent community survey, outlining five key themes and concrete actions to improve contributor experience and belonging. It’s a solid model for OSS projects looking to turn feedback into measurable change. WordPress corner: new plugin picks include a performance-friendly image lazy-loader and a block-pattern organizer to speed up site building. Also on deck: a video walkthrough of creating a custom WP-CLI command to automate content migrations. Links worth clicking: - CHAOSS’s community-informed DEI snapshot and actions: CHAOSS DEI Self-Reflection Summary - Git branching mental models for real humans - CSS container queries demo you can copy-paste today Stay curious, be kind in code reviews, and remember: semicolons are free—use them generously. ## ✅ Action Items: A tailored prompt you can reuse to align articles with your Developer Advocate/OSPO trajectory: “Analyze how this article informs open-source advocacy, contributor engagement, and education within the WordPress ecosystem. Identify: - Onboarding and mentorship takeaways I can translate into GoDaddy DevRel programs and WordPress contributor days. - Practices that promote transparency, governance clarity, and sustainable funding models for community health. - Metrics I can adopt from CHAOSS (e.g., responsiveness, retention, DEI participation) to guide OSPO reporting and OKRs. - Educational artifacts I can produce (workshops, docs, videos) to support new contributors in PHP/JS/HTML/CSS/Git/GitHub. - Policies or facilitation techniques that strengthen psychological safety and inclusivity in public forums and events. - How these insights advance my goal of becoming an OSPO director who integrates pedagogy, measurement, and community stewardship.” Then, produce: - A one-page internal brief mapping insights to DevRel initiatives. - Three measurable experiments (e.g., newcomer issue pipeline, async-first RFC process, recognition badges). - A transparency plan: public dashboard of community health metrics and quarterly write-ups. ## 🧪 Hypotheses: - H1: Publishing survey themes with clear actions increases newcomer retention over 90 days. - H2: Mentorship plus clarified onboarding reduces first-PR time-to-merge by 20%. - H3: Meeting-format flexibility (async notes, multiple time slots) increases non-dominant time zone participation by 30%. - H4: Public recognition boosts contributor activity frequency among first-year contributors. - H5: Tracking DEI metrics correlates with improved satisfaction scores in annual surveys. ### 📊 Methodology: - Data sources: GitHub events API, meeting attendance logs, discourse/forum activity, contributor surveys, calendar RSVPs - Summary: The CHAOSS community conducted a survey to gain insight into its members' perspectives. Five main themes emerged from the survey: clear communication, working groups, software, newcomer experiences, and community experiences. To address the need for clear communication, CHAOSS improved cross-chapter communication through newsletters and community meetings. They also simplified the categorization of metrics and improved the user experience on their website. In terms of working groups, CHAOSS shifted towards a more context-focused approach and retained three working groups for metric development. They also aim to bridge the gap between theoretical and practical use of metrics. CHAOSS recognized the importance of building a community around their software and plans to allocate more resources for this. They also focused on improving the newcomer experience through a quickstart guide, learning modules, and a tour guide program. To combat the challenge of a fragmented community, CHAOSS is exploring ways to bring the c... - URL: https://chaoss.community/chaoss-dei-self-reflection-summary/ Several months ago, we ran a survey to better understand the CHAOSS community. Thank you so much to those who participated in that survey! We really appreciate your valuable input. From the survey, we were able to identify five themes that you told us about. We’ll describe those five themes here and discuss what we are doing in the CHAOSS project to help address these themes. | | | | --- | --- | | **Theme 1: Clear Communication** | | | Comments | What We’ve Done in CHAOSS | | Processes about how to check-in with the wider community would be helpful. | Each regional chapter hosts their own Community Meetings and we post those meeting summaries and links to the meeting recordings in Slack and on Discourse, so anyone in the community can quickly stay up to date on what’s going on in other parts of CHAOSS. We will continue to improve cross-chapter and cross-group communication among the entire CHAOSS community through our newsletters and weekly CHAOSS Community meetings. | | It is hard to navigate the detail of the focus areas | Sifting through the ever growing list of CHAOSS metrics has proven to be challenging for our users and those new to the community. Previously, focus areas were used to categorize metrics into contextual buckets. The user would have to be familiar with which working group developed the metric, and which focus area we decided provided the best fit. This required a level of knowledge of CHAOSS and the way we work that was a barrier for those new to the community.We have since moved away from displaying metrics in this way, and have moved toward a more intuitive model of categorization. First we assign 1-2 high-level topics to each metric, then we assign a number of keywords, which provide more context. This gives the user the ability to search for more specific criteria.Also, we improved the UX by no longer displaying metrics in one single document. Now there are visually clear “tiles” on our website that allow users to easily explore our metrics based on the high-level topic they’re interested in.With the addition of our metrics models, we also help the user identify sets of metrics that naturally come together. | | **Theme 2: Working Groups** | | | Comments | What We’ve Done in CHAOSS | | Sunsetting working groups may be a good thing. | The structure of CHAOSS has evolved over the past year to shift away from the concept of “working groups that develop metrics through a particular lens” and more toward the context in which metrics can be used to help answer questions. Because some metric development benefits from specific areas of expertise, we chose to retain our DEI and Risk Working Groups, but have effectively folded the rest into other groups. We now have 3 working groups focused on metric development: Risk, DEI, and Common. | | Preference for the real use cases in metrics models | With the hiring of our Director of Data Science and the launch of our Context Working Groups, bridging the gap between theoretical and practical use of our metrics and metrics models will be a primary focus of CHAOSS moving forward. | | Contextual work can be distinct from metrics working groups, and this is good. | As mentioned previously, the evolution of CHAOSS means a shift toward a separation of Context Working Groups and the working groups responsible for metrics development. In this way, we are able to collaborate with our user community to answer the questions that arise in their individual contexts. We now have 3 Context Working Groups where these high-level discussions occur: Corporate OSPOs, University OSPOs, and Open Source Scientific Software. An outgrowth of our continued discussions with CHAOSS’s expanding community may be additional Context Working Groups. | | The Common WG seems to be where “things that don’t clearly go anywhere fit”. | The Common Working Group has indeed been through a few iterations! It does seem to act as a catch-all, especially with regard to metric development. But as we have pared down the number of Working Groups, it makes more sense that this development would land in Common. CHAOSS will continue to communicate that message and clarify the mission of the Common Working Group. | | **Theme 3: Software** | | | Comments | What We’ve Done in CHAOSS | | Build community around software. | This has always been challenging for us, and it’s something we continue to strive for. With the hiring of our Director of Data Science, and conversations with potential partners, we aim to allocate and acquire additional dedicated resources for this effort. This will likely be a focus for us in 2024, as it is critical to the sustainability of CHAOSS software. | | **Theme 4: Newcomer Experiences** | | | Comments | What We’ve Done in CHAOSS | | Improve processes of where to begin, especially when a person comes to CHAOSS with an interest where work is being done in the many places. | Newcomer experience has been a primary focus for the past 12-18 months.With the creation of a newcomers Quickstart, we have a central document with a few action items for newcomers to complete. This allows them to learn about CHAOSS and be more prepared to fully join our community.We are improving the long term onboarding experience by moving away from a monthly onboarding call (which was overwhelming and not as inclusive as it could be because of time zones) toward building out a set of learning modules for newcomers to work through at their leisure. This will occur in a learning management system and will allow newcomers to move at their own pace, and learn about CHAOSS in digestible chunks.We also launched a Tour Guide program whereby newcomers can receive individual attention and guidance to find the spaces within CHAOSS where they might have an interest in participating. | | Promote new opportunities for people to engage with the community as they come up. | As mentioned previously, our Tour Guides act as a link between opportunities and new contributors, but we are also organizing the many sub projects within CHAOSS through a more structured project management framework. By bringing together contributors with project management experience, we can allow them to contribute by keeping these smaller projects on track, clarifying engagement opportunities, and communicating them regularly to our community.We also promote the use of the “First Timers Only” labels on issues in our many repositories. | | Make “where to begin” clearer in documentation. | With the development of our Quickstart, and prominent links to this on the CHAOSS website homepage, newcomer Slack channel, and in the newcomer Slack Bot, we now have one central place where we can point newcomers. | | **Theme 5: Community Experiences** | | | Comments | What We’ve Done in CHAOSS | | As the community has grown, it is beginning to feel more fragmented. | This is a challenge for any global community with a lot of moving parts. We have many Slack channels and many sub-projects and it’s difficult to keep track of what is going on with everyone.We implemented a Discourse Forum with the idea that it would be a way to bring the whole community together in a more substantial way than many fragmented Slack channels, but this has not been as well received as we hoped. The CHAOSS community will continue to iterate on and think about ways to combat this issue. | | A learning pathways framework would be helpful. | As mentioned, CHAOSS is currently building out such a framework using a learning management system. We think this will bring clarity to the onboarding process and help educate potential contributors so they can actively engage with the community in the way that means the most to them. | | There are times that focus on tools becomes too central. | While tools are a big part of CHAOSS (even appearing in our name), they are definitely not the only thing CHAOSS works on. We hope that with clearer communication on all the sub-projects happening in CHAOSS, it will not feel like our tools take center stage. | | There may be too many working groups. | As mentioned, we have effectively cut our metrics development working groups down to 3. | | Provide more workshops, peer mentoring, and programs on software and metrics (perhaps also newcomer experience) | We plan to include some of this type of education in our learning management system modules. Currently, we don’t have the individual resources to consistently host other types of workshops (aside from the occasional CHAOSScon). By making it easier to learn about CHAOSS, we hope to grow our community of leaders who can facilitate these types of workshops. It would be outstanding to be able to provide these experiences for our community! |, CHAOSS DEI Self-Reflection Summary, elizabeth, 01h95r2pq2k7skd50tzpjgkdcg.