CHAOSS DEI Badging Meeting, Jan 28. 2026 - CourtneyR.dev's 2nd Brain

CHAOSS DEI Badging Meeting, Jan 28. 2026 ![rw-book-cover](https://img.youtube.com/vi/2LbCq2F2exg/maxresdefault.jpg) 🔗 **Source:** [CHAOSS DEI Badging Meeting, Jan 28. 2026](https://www.youtube.com/watch?v=2LbCq2F2exg) > [!note]+ Document Notes > tags: #open-source #diversity #inclusion #chaoss #badging > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=2LbCq2F2exg > date created: 2026-01-28 12:00 > > # 🏷️ Title: CHAOSS DEI Badging Meeting - Project Badging Process and Outreach Ambassador Program >  ## 🧰 Action Inbox - [H1] Apply for project badge through badging.chaoss.com — DEI documentation required #badging - [H2] Create DEI.md file documenting community practices — root directory placement #documentation - [H3] Join as outreach ambassador to reach 20 badged projects by Q2 2026 — networking opportunity #outreach ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [CHAOSS Badging Website](https://badging.chaoss.com) - [DEI Working Group Documentation](https://github.com/chaoss/wg-dei) ## 📝 Summary - CHAOSS DEI Working Group runs badging programs for open source events and projects to showcase DEI commitment - Project badging involves creating a DEI.md file documenting practices across four metrics: project access, communication transparency, newcomer experiences, and inclusive leadership - The badging bot scans repositories for compliant DEI.md files and awards bronze badges via email - Goal is to grow from 4-5 badged projects to 20 by March/June 2026 through outreach ambassador program - Outreach ambassadors represent CHAOSS to engage communities and guide them through the badging process ## 📖 Main Content The CHAOSS DEI Working Group operates two flagship badging programs: event badging for conferences and project badging for open source communities. Project badging helps maintainers document and showcase their diversity, equity, and inclusion practices through a structured process. The project badging system requires communities to create a DEI.md file in their repository's root directory, documenting practices across four key metrics. An automated badging bot scans submitted repositories and awards bronze badges to compliant projects. The program currently has only 4-5 badged projects since launching in early 2024, with an ambitious goal to reach 20 projects by mid-2026 through a new outreach ambassador initiative. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/2LbCq2F2exg?t=0) — [H1] DEI Working Group Overview - Key idea: CHAOSS DEI working group defines metrics for diversity, equity and inclusion in open source - Evidence: "DEI working group focuses on defining and refining metrics that are concerning diversity, equity and inclusion in open source" #### ⏱️ [02:30](https://youtu.be/2LbCq2F2exg?t=150) — [H2] Two Badging Programs - Key idea: Event badging for conferences and project badging for communities are the two flagship initiatives - Evidence: "we have like two flagship projects that we run to help acknowledge DEI efforts in open source and that's the event bading and the project budgeting" #### ⏱️ [05:45](https://youtu.be/2LbCq2F2exg?t=345) — [H1] Project Badge Purpose - Key idea: Project badges help communities document and showcase their DEI efforts rather than serving as certificates - Evidence: "the badge is not to it's not like it's a certificate or something. It's just like a way for communities to actually take their time to document their DEI effort" #### ⏱️ [08:15](https://youtu.be/2LbCq2F2exg?t=495) — [H2] Outreach Ambassador Role - Key idea: Outreach ambassadors engage communities on behalf of CHAOSS to promote project badging - Evidence: "I am Teresa from Chaos. I am an outrage project an outrage ambassador for project badging which is an initiative of DEI working group" #### ⏱️ [12:20](https://youtu.be/2LbCq2F2exg?t=740) — [H1] Four DEI Metrics - Key idea: Project badging evaluates four core metrics for measuring DEI practices - Evidence: "project access, communication transparency, newcomer experiences, inclusive leadership how inclusive are you" #### ⏱️ [15:30](https://youtu.be/2LbCq2F2exg?t=930) — [H2] DEI.md Template Process - Key idea: Communities document practices using a standardized DEI.md template in their repository - Evidence: "the maintainer or the community manager is then going to document their their process using this" #### ⏱️ [18:45](https://youtu.be/2LbCq2F2exg?t=1125) — [H3] CHAOSS Example Implementation - Key idea: CHAOSS community manager Elizabeth Baron documented their own DEI practices as an example - Evidence: "this is a real one that Elizabeth, our community manager did. So this is the DEI for chaos" #### ⏱️ [22:00](https://youtu.be/2LbCq2F2exg?t=1320) — [H2] Badging Bot Scanning Process - Key idea: Automated bot scans repository root directory for DEI.md file and validates metric compliance - Evidence: "we have a badging bot that goes into the repository of that project, right? Let's say for instance, chaos and then scans for a DEIMD file" #### ⏱️ [25:30](https://youtu.be/2LbCq2F2exg?t=1530) — [H3] GitHub/GitLab Integration - Key idea: Badge application supports GitHub and GitLab authentication for automated scanning - Evidence: "if their community was hosted in GitHub, they log in with GitHub. If it was GitLab, they log in with GitLab" #### ⏱️ [28:15](https://youtu.be/2LbCq2F2exg?t=1695) — [H2] Badge Award and Display - Key idea: Successful communities receive bronze badge via email and display it in their repositories - Evidence: "once it sees that then it comes back with a success message and then send the badge to the email" #### ⏱️ [32:00](https://youtu.be/2LbCq2F2exg?t=1920) — [H1] Growth Goals and Timeline - Key idea: Ambitious goal to grow from 4-5 projects to 20 badged projects by March-June 2026 - Evidence: "by the end of March and then the worst case scenario by the end of June we are able to badge 20 project" #### ⏱️ [35:45](https://youtu.be/2LbCq2F2exg?t=2145) — [H3] Ambassador Benefits and Impact - Key idea: Outreach ambassadors gain networking opportunities and measurable impact in open source DEI - Evidence: "you get to make impact. Honestly big impact... you get to build networks" #### ⏱️ [38:30](https://youtu.be/2LbCq2F2exg?t=2310) — [H2] Resources and Support Structure - Key idea: Playbook, templates, and project manager support available for outreach ambassadors - Evidence: "there is a playbook that we have created that you can sit with and go through... templates for you also like an email" ## 📚 References - [CHAOSS Badging Platform](https://badging.chaoss.com) - [DEI Working Group](https://github.com/chaoss/wg-dei) - [CHAOSS Community](https://chaoss.community/) ## 🗣️ Paraphrase - The CHAOSS DEI Working Group operates badging programs that help open source communities document and showcase their diversity, equity, and inclusion practices through a structured template and automated verification process - Project badging requires communities to create a DEI.md file documenting four key areas: project accessibility, communication transparency, newcomer experience, and inclusive leadership practices - An outreach ambassador program aims to grow participation from 4-5 projects to 20 by mid-2026, providing ambassadors with networking opportunities and templates to engage communities on behalf of CHAOSS ## 📰 Newsletter The CHAOSS DEI Working Group is launching an ambitious outreach initiative to help open source communities document and showcase their diversity, equity, and inclusion efforts. Their project badging system provides a structured way for maintainers to reflect on DEI practices across four key metrics: project access, communication transparency, newcomer experiences, and inclusive leadership. The process involves creating a standardized DEI.md file that gets scanned by an automated badging bot, with successful communities receiving bronze badges to display their commitment. With only 4-5 projects currently badged since the 2024 launch, they're seeking outreach ambassadors to help reach 20 badged projects by mid-2026. This initiative offers WordPress communities a valuable framework for evaluating and improving accessibility and inclusion practices while connecting with the broader open source DEI movement. Resources: [CHAOSS Badging](https://badging.chaoss.com), [DEI Working Group](https://github.com/chaoss/wg-dei), [WordPress Diversity](https://make.wordpress.org/community/handbook/community-deputy/resources/diversity-and-inclusion/) ## ✅ Action Items #### Community - Maintainers: Evaluate DEI practices using CHAOSS four-metric framework, create DEI.md documentation - Contributors: Participate in badging assessment discussions, provide newcomer experience feedback - Sponsors: Support communities pursuing DEI badging, fund inclusive leadership training - Ecosystem: Share badging success stories, cross-reference with accessibility initiatives #### WordPress - Community: Pilot CHAOSS badging for WordCamps and WordPress communities, integrate with existing diversity efforts - Training: Develop DEI documentation workshops based on CHAOSS templates - Marketing: Showcase badged WordPress communities as diversity leaders - Meta: Consider badging for wordpress.org project itself, align with accessibility roadmap ## 🧪 Hypotheses - Structured DEI documentation through badging increases community awareness and improvement of inclusion practices - Automated badging processes reduce barriers to DEI assessment compared to manual evaluation methods - Outreach ambassador programs can significantly accelerate adoption when communities see peer success stories - Bronze-level badging serves as an effective entry point for communities to begin formal DEI measurement ### 📊 Methodology - Track badging adoption rates across different community types and sizes over 6-month periods - Survey badge recipients on practice changes and community impact post-badging - A/B test outreach approaches: direct maintainer contact vs. community event presentations ### ❓ Questions - How do badged communities measure actual DEI improvements beyond documentation compliance? - What prevents the 95% of eligible communities from pursuing badging despite low barriers? - How might WordPress-specific DEI metrics differ from generic open source community measures? ### 🔮 Future Research - Integration between CHAOSS badging and WordPress accessibility team initiatives - Correlation analysis between badged communities and contributor diversity metrics - Cross-platform badging adoption patterns between GitHub, GitLab, and self-hosted projects ### 💡 Implications - Practice: DEI.md files become standard repository documentation alongside README and CONTRIBUTING - Policy: Funding organizations may require or incentivize CHAOSS badging for grant recipients - Security: Inclusive communities may have better security practices through diverse review processes - Education: Badging templates provide concrete DEI curriculum for maintainer training programs ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Screenshots of badging website, badge examples, DEI.md templates - Improve: Process flowcharts, before/after community comparison diagrams #### 🔊 Aural learners - Present: Video walkthrough with detailed verbal explanations - Improve: Podcast-style case studies from badged communities #### 🗣️ Verbal learners - Present: Clear definitions of four DEI metrics, step-by-step process explanations - Improve: Community conversation examples, ambassador talking points #### 🧩 Kinesthetic learners - Present: Hands-on demonstration of badge application process - Improve: Interactive DEI assessment worksheets, badge template customization exercises #### 🧠 Logical learners - Present: Numbered process steps, clear cause-and-effect badging workflow - Improve: Decision trees for metric evaluation, ROI analysis of DEI documentation #### 🧑‍🤝‍🧑 Social learners - Present: Ambassador program structure, community engagement examples - Improve: Badging cohorts, peer review partnerships for DEI.md files #### 🧘‍♀️ Solitary learners - Present: Self-service templates and documentation, individual application process - Improve: Self-assessment rubrics, private reflection prompts for DEI practices #### 🌿 Naturalistic learners - Present: Community ecosystem metaphors, organic growth goals - Improve: DEI practice maturity models, sustainable inclusion frameworks ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in presentation, logical content flow - Improve: Alt text for badge images, ARIA labels for interactive elements #### Keyboard navigation - Present: Standard browser navigation support - Improve: Skip links for long process descriptions, keyboard shortcuts for badge application #### Contrast and readability - Present: Standard video contrast levels - Improve: High contrast badge designs, readable font sizes in templates #### Text resizing and reflow - Present: Responsive video player - Improve: Scalable badge graphics, mobile-friendly application process #### Media and captions - Present: Video content with transcript - Improve: Automated captions, downloadable process guide transcripts #### Forms and interactions - Present: GitHub/GitLab authentication integration - Improve: Form validation messages, accessible error handling in badge application ### 🌍 DEIB Assessment #### Cultural breadth - Present: International CHAOSS community participation, global project examples - Improve: Non-English DEI template translations, region-specific inclusion metrics #### Inclusive language - Present: Consistent use of "communities" rather than exclusionary terms - Improve: Plain language alternatives for technical jargon, cultural context for DEI concepts #### Neurodiversity support - Present: Clear process structure, step-by-step explanations - Improve: Visual process aids, sensory-friendly badge application interface #### Representation - Present: Diverse community examples (GitLab, CHAOSS, Python) - Improve: Showcase badged communities from underrepresented regions and languages #### Psychological safety - Present: Non-punitive badging approach, improvement-focused messaging - Improve: Confidential DEI assessment options, trauma-informed community practices guidance ### ✅ Logical Validity #### Strong reasoning - Deductive strength: If communities document DEI practices systematically, then awareness and improvement follow - Inductive strength: Success patterns from early adopters suggest broader community benefits - Causal reasoning: Structured reflection leads to measurable practice improvements - Analogical strength: Event badging success models applicable to project badging #### Fallacies - Appeal to numbers: "20 badges = success" without quality assessment of actual DEI improvements - False dichotomy: Bronze badging presented as binary achievement rather than continuous improvement spectrum #### Tone of voice - Overall tone: Enthusiastic and motivational with practical, step-by-step guidance and community-focused benefits messaging ### 🛡️ DARVO Analysis - Deny: No denial patterns present in straightforward educational content - Attack: No attacks on critics or alternative approaches observed - Reverse victim/offender: No victim/offender dynamics in community improvement context - Emotional cues and rhetoric: Positive motivation and impact framing without manipulation tactics ## 🎯 Conclusion The CHAOSS DEI badging initiative provides open source communities with a concrete framework for documenting and improving diversity, equity, and inclusion practices through standardized templates and automated verification. The ambitious goal to quintuple participation through outreach ambassadors represents a critical test of whether structured DEI assessment can scale across diverse community types. For WordPress and other open source ecosystems, this --- ## Full Transcript [00:02] All right. Hi everyone. So we were [00:05] talking about the DEI working group and [00:08] what I said was that the DEI working [00:11] group focuses on [00:14] defining and refining [00:17] metrics that are concerning diversity, [00:20] equity and inclusion [00:24] in open source. Okay. And um under the [00:29] DEI working group, we have like two [00:32] flagship projects [00:35] that we run to to um help u acknowledge [00:41] DEI efforts in open source and that's [00:43] the event bading and the project [00:45] budgeting. So I'm showing us the website [00:49] um where all of these things happen the [00:53] the two bad processes. So we have the [00:56] badging.skos.com [00:58] website. [01:00] This is the home. Um gives us the [01:03] overview of the badging initiative that [01:07] what we do is to award badges to open [01:09] source projects and events and then the [01:12] badges are to showcase commitment to [01:15] improving and supporting diversity, [01:17] equity, and inclusion. Now I'm just [01:19] going to quickly run through the event [01:21] badging so that you'll just understand [01:24] um everything about badging. So for the [01:28] event badging what happens here is that [01:32] um it's an award system [01:35] through which opensource event [01:39] organizers hand badges for their event. [01:42] So this one is about event um think um [01:46] jango conference the conference the pyon [01:50] and all that they can apply for this [01:53] type of badge to be able to showcase [01:56] that they are actually supporting [01:58] diversity equity and inclusion in [02:02] opensource and so there is a whole [02:05] process that you have to go through to [02:07] do that it's also very easy [02:10] and um if you look at our batched [02:12] events. These are the list of um events [02:16] that we have batched so far. [02:20] You can see them down there. There are [02:22] some work that still need to be done [02:24] here. But then we can still see Pyouch [02:27] conference [02:28] and all the other events that we have [02:31] batched. Now the project badging [02:36] instead of events. Now the project [02:39] badging is about badging projects [02:41] themselves and the communities [02:43] themselves. So rather than pyon for [02:46] instance you now think about PSF which [02:49] is the Python software foundation. So [02:52] that's just the difference. So the the [02:55] the the project badge is is the badge [02:58] that you get as a project or as a [03:01] community that that showcases your [03:05] effort towards DEI in your community. So [03:10] essentially it says that you really take [03:12] DEI seriously in your project or in your [03:15] community and then you are able to um [03:20] show how you are doing that [03:24] how you are um how how you are um um [03:28] empowering DEI in your community. So the [03:32] badge is not to um it's not like it's a [03:35] certificate or something. It's just like [03:38] um uh a a a a way for communities to [03:43] actually take their time to document [03:45] their DEI effort and then be able to [03:48] showcase it to the world that oh this is [03:50] what we've been doing and um we have a [03:53] badge for it. So there is a way it [03:56] works. There is a process that these [03:59] communities have to go through, right? [04:02] And I'm just going to I'm going to [04:05] demonstrate it to you. so that you have [04:06] an understanding [04:09] >> of what I'm trying to say. [04:13] >> Sorry, I think somebody Okay. Hi. Hi, [04:16] you're coming. Please could you mute [04:20] your phone? [04:31] Please could you mute? Thank you very [04:32] much. All right. [04:35] Okay. So, as I was saying, [04:41] um I I said so you can go through this [04:44] and just um read more so that you can [04:48] understand, but then I'm just going to [04:50] demonstrate it for you so that um you [04:54] have like a high level understanding of [04:57] what the project bad is about and then [05:01] if you have questions then I get to [05:03] answer you. All right. So [05:08] let's say that I'm I'm just going to be [05:11] using um okay let me use chaos community [05:13] so that um we will understand it better. [05:16] All right. So assume assume I am not the [05:19] community manager. Elizabeth Baron is [05:21] I'm just saying assuming I am the [05:24] community manager right for chaos. [05:28] And then Theesa as the outreach [05:31] ambassador maybe met me in a conference [05:34] or even knows me on LinkedIn. [05:37] And then she reach out to me to say um [05:41] hey uh I am Teresa from Chaos. I am an [05:46] outrage project um an outrage ambassador [05:49] for project badging which is an [05:51] initiative of DEI working group. [05:55] um I would like you to badge with us to [05:58] be able to showcase your um DEI effort [06:02] in your community. Do you even have any [06:06] um any form of documentation or any form [06:09] of um um any form of platform whereby [06:14] you are ensuring that your your [06:17] contribution towards DEI in your [06:19] community is is is very strong and all [06:22] that and then um if you if they are open [06:25] to having that conversation then you get [06:29] to engage them and then say oh if you [06:32] don't if you don't have one, I can walk [06:34] you through the process. So, what the [06:37] project badge essentially does for you [06:39] is that it helps you as the project [06:41] admin or maintainer or the community [06:44] manager to take time to reflect about [06:47] your DEI practices in your own [06:49] community. See how you're fairing and [06:53] just document it. And once it's [06:55] documented in in in a standard template [06:59] that I can help you, this is Teresa [07:02] talking right um that I can I can show [07:05] you you know you can just document your [07:07] practices using this template and then [07:11] after you are done you can then apply [07:14] for a badge. So that badge is like um an [07:17] award that just shows the world that oh [07:20] you are really really serious about DEI [07:23] practices in your community and then at [07:26] the cast the community manager says oh [07:28] wow I love that in fact we've been [07:32] wanting to uh like put clarity into our [07:37] DEI practices we just don't know how to [07:39] go about it but um now that you have [07:41] shown me the way um no problem I'm going [07:44] to I'm going to I'm interested. Let's do [07:47] this. And then Teresa shows me this [07:50] particular website [07:53] and then tells me that oh there is a [07:56] DIMD [07:58] file that you can use as a template for [08:04] you to document your DEI practices. [08:07] Right? So this is this is the DEIMD [08:11] template. I'm going to open that for [08:12] you. [08:14] and then uh the DEI.m MD guide that you [08:18] can go through. [08:21] So this is the template. [08:24] Now we have four metrics [08:26] that we use to measure [08:29] um to measure the DEI practices for [08:33] projects and one of it is um one of them [08:37] is project access right [08:41] project access and essentially what that [08:44] says is um how accessible are you to [08:47] contributors [08:49] right and then communication [08:52] transparency [08:54] To what extent do people in your [08:56] community know what is going on in your [09:00] community, right? Um newcomer [09:03] experiences, new contributors, how easy [09:06] how is it um how easy is it for them to [09:11] understand the project, for them to [09:14] belong in the community? Do they have um [09:17] do they see like a contributor ladder [09:20] that they can climb like okay um if I [09:22] start here where will I be in the next [09:25] one year what impact can I measure that [09:28] I've been able to make to this community [09:31] then inclusive leadership [09:34] how inclusive are you um if we look at [09:37] your governing board or your co-chairs [09:41] how diverse are they so those are the [09:44] metrics current that we have currently [09:46] at this level [09:48] for for badging. So the maintainer or [09:53] the community manager is then going to [09:55] document their their process using this. [09:58] So let me show you um the one that [10:01] Elizabeth did for [10:05] chaos. Now this is a real one that [10:07] Elizabeth, our community manager did. So [10:11] this is the DEI for chaos. You can see [10:15] um here that chaos prioritizes and [10:16] reflects on DEI through a regular review [10:19] of project policies and performance. Now [10:22] under project access, you can see that [10:24] she's saying that all virtual meetings [10:26] are transcribed via the zoom annotation [10:29] tool. Our members are able to join via [10:31] their computer or phone. So essentially [10:34] this is how people are able to access [10:36] the project. Right? Then she was able to [10:39] talk about communication transparency, [10:41] what they do in chaos and then the [10:43] newcomer experiences and then the [10:46] inclusive leadership. How is our [10:49] governance like in chaos? And so she [10:52] wrote all that down here. So let's say [10:54] that she's done [10:57] right. She's done here. [11:00] She places this DEI. MD file in the root [11:06] directory of the of their project. So [11:09] this is um a repository under chaos. Now [11:13] I'm just going to show us you can see [11:15] that the DEIMd file is in the root [11:18] directory. This is where our badging bot [11:21] is going to scan and look for the DEI. [11:24] MD file. Okay. So once the community [11:29] manager is done with this file and [11:31] they've placed it in their project then [11:33] they go to our own bad website that the [11:37] razor had shown uh shown the um [11:42] community manager and then she clicks [11:45] apply for badge [11:47] then she clicks project bading. [11:51] So if their community was um hosted in [11:55] GitHub, they log in with GitHub. If it [11:58] was GitLab, they log in with GitLab. And [12:01] then if it's that neither of the two, [12:03] but they hosted it themselves, we don't [12:06] have the capabilities for the bots to do [12:08] that yet. So they have to do that um [12:11] manually. I'm going to show you in a [12:12] bit. So let me let me show you um about [12:16] GitHub first. Now this one I've already [12:18] authenticated. So um the first thing is [12:21] going to do is that let's say she [12:23] clicked on um login with GitHub. [12:27] It's going to um GitHub is going to [12:29] authenticate the the community manager. [12:32] Let's assume that um I am the community [12:34] manager. So I'm being authenticated. Um [12:37] it's going to show you here that oh um [12:41] uh [12:43] uh this particular um badge like bad [12:47] chaos community is trying to um gain [12:51] access to your GitHub account like just [12:54] authorize it to be able to do its job [12:57] and then if you authorize it takes you [12:59] here. So essentially this consists of [13:03] your um selected rep um repositories. [13:07] So let's assume that I am the community [13:10] manager that has like a project [13:13] that I have already put the uh DEIMD [13:17] file. So I have one that I am using for [13:20] test and demos. So um you can see it [13:24] here. Hold on. [13:31] Yeah, you can see this car or test [13:35] project bad. So of all my repositories [13:39] now, this particular repository has the [13:42] DIMD file. So let's just assume that [13:44] it's the chaos um community [13:48] repo that I selected here also. So then [13:52] the person is the maintainer or the [13:54] community manager is going to go ahead [13:56] and click scan project. [14:00] And what um happens in the back end is [14:05] that we have a badging bot that goes [14:08] into the repository of that of that [14:11] project, right? Let's say for instance, [14:13] chaos and then scans for a DEIMD file, [14:20] goes into that DEI. MD file and looks [14:23] for [14:25] the metrics that we are trying to [14:28] measure. Looks for the project assets [14:31] metric. The heading looks for the [14:34] inclusive leadership. Looks for [14:36] communication transparency and um [14:40] project assets, right? And [14:43] once it sees that then it it comes back [14:48] with a success message and then send the [14:52] badge to the email [14:55] of that um particular community manager. [14:58] So currently the project [15:02] uh you can see here it said hello [15:05] you receive an email shortly. Kindly [15:07] check your email. So if I check my email [15:10] now, I'm just going to see the bronze [15:13] badge because we are recording. I will [15:16] not be able to show you my email. So um [15:20] you will just see the bronze badge and [15:24] um that community manager can then take [15:27] that badge and then [15:31] put it in their community um in their [15:35] community directory. So let let's go [15:38] back to the project that have badged [15:40] with us and I'm going to show you where [15:43] they place [15:45] where they placed their own the bad that [15:48] they receive. You can see the badge here [15:49] the bronze. So you the the project [15:52] manager is going to receive this in [15:54] their email. So let's go to um chaos. So [15:58] chaos has badged. [16:04] Okay. [16:15] All right. So, you can see it here. [16:18] The DEI project badge bronze. So, this [16:21] project bad represents our commitment to [16:23] centering DEI in our community as found [16:26] in our DEI. MD file. So if you have any [16:29] questions about our DIMD file, please [16:32] reach out to the community on Slack. Let [16:34] me go ahead and show you the other [16:37] people's own like GitLab. Now [16:41] GitLab also badged with us and um [16:47] let's look and see they have the badge [16:51] here. [17:01] So I don't know if they place their ass [17:04] here but then [17:09] um [17:10] their own DEIMD file will be somewhere [17:13] around this place. [17:17] They have a lot of files in here. [17:21] All right. You can see the DEIMd file. [17:26] Yeah. [17:27] So this is their own documentation of [17:29] how they are [17:33] they are practicing um DEI in GitLab [17:38] community. You can see so the bot scans [17:42] this and then once it can it can [17:48] see um you can see the last reviewed the [17:52] date is different from the one for [17:54] chaos. So that that was the day that [17:57] they the batch. [17:59] So once he sees this metrics, it goes [18:02] ahead and awards them the badge. All [18:05] right. And then [18:08] um once all of that is done, then they [18:12] get displayed on our website. Now what [18:14] happens if the badging board does not [18:17] see any of those metrics? It then gives [18:20] them like a a failure message to say, [18:23] "Sorry, we couldn't badge [18:26] your project because such and such and [18:28] such metric is missing. Would you like [18:31] to include it?" And then run it again. [18:35] And um the maintainer then has to go [18:38] back and um improve on the dock, then [18:40] apply for it again. And so once the [18:42] badging bot um sees what it's looking [18:45] for and all requirements are met, then [18:49] it goes ahead and gives them [18:51] that that badge. [18:54] Okay. So what's your duty as an outreach [18:59] ambassador? I already wrote the [19:01] responsibilities in the call for [19:03] ambassadors. So essentially your work is [19:06] to engage um the open source communities [19:10] around you to say hey this is what we [19:13] are doing at chaos this is why we do it [19:16] and we would like you to be a part of it [19:18] come badge with us and then they go [19:21] through this process that I've discussed [19:23] here and um they get the badge and so [19:27] for us at DEI working group what our [19:31] goal is for the badging project in the [19:33] first quarter [19:36] at least um [19:38] at at least uh is it I'm trying to to [19:43] okay so let me just say that we are [19:46] saying that um at our best best case [19:50] scenario [19:51] the first three months by the end of [19:53] March and then the worst case scenario [19:56] by the end of June we are able to badge [19:59] 20 project right that's our desire to [20:03] T20 projects batched because this is [20:05] just the first level version one of [20:08] project badging. We want to take it up [20:10] to the next level and for us to scale to [20:13] say oh communities can come and have [20:15] another level. Now we want to be able to [20:18] say oh this 20 project that has um this [20:21] this first version that we have even [20:24] rolled out how many communities have [20:26] used it how are they fairing and all. So [20:30] we don't just want to roll out stuff [20:31] that people have not used which is why [20:34] we are saying that let's have 20 [20:36] projects even badged before we then [20:38] begin to think of adding the other [20:41] levels of badges. [20:43] So um yeah you will be engaging on our [20:48] behalf you'll be engaging people in your [20:51] network on your LinkedIn you know just [20:54] reaching out and and getting them to [20:57] badge. So [21:00] um what else? What else do I want to [21:02] say? So I would say that um [21:05] you will um it would be nice for you to [21:08] leverage your network. I know that some [21:10] of us have people um and even [21:14] maintainers that we've met maybe online [21:16] that we can reach out to. And because [21:18] you're not reaching out on behalf of a [21:20] community now like on behalf of chaos, [21:22] it kind of puts weight on your effort. [21:26] So you're not just going by yourself. [21:27] You're going in the name of chaos. [21:29] Right? So uh [21:33] what's in need for you? Of course I've [21:35] told you what's in need for us. We are [21:37] able to get 20 um project right. What's [21:41] in need for you? Uh you get to make [21:44] impact. Honestly big impact. Do you know [21:47] why I said big impact? because uh this [21:50] project was launched in [21:53] was it in 20 early 2024 this is 2026 and [21:58] we have still not moved beyond the five [22:00] projects that badged I I said five [22:02] because I removed chaos chaos actually [22:04] launched it right in fact let me say [22:06] four because GitLab was part of it [22:08] GitLab and GitHub were they were they [22:12] were um collaborators in for for this [22:14] project so if I remove GitLab and chaos [22:17] that's like uh four projects. So if we [22:21] can get it to 20 that's a big deal. That [22:23] means that something was lying follow [22:26] and then a group of people came together [22:28] and then they pushed it to 20 to start [22:31] living again. So that's an impact that [22:34] you can take anywhere with you. That's [22:36] number one. Number two, [22:39] um you get to build networks, right? you [22:43] reaching out to people to say hey um I [22:46] am an attract ambassador for chaos and [22:49] these days this is the work we have been [22:51] doing in the day I woke you girl up blah [22:54] blah and all that you don't know you [22:57] don't know [22:59] where that can take you right you don't [23:01] know who you can be talking to that can [23:03] you don't know where that networking can [23:06] go so yeah I think that's that's enough [23:09] motivation for us to say hey let's Let's [23:12] put in our best, right? And um yeah, [23:16] just for the love of open source, let's [23:18] let's do something great. Um what else? [23:22] Again, [23:23] uh okay, I think that's that for now. If [23:28] you have any questions for me, please [23:30] let me know. [23:48] Sorry, I hope I was not talking to [23:49] myself. [23:54] >> No, not at all. Thank you so much for [23:56] the presentation. [23:59] >> All right. Thank you. [24:03] >> Um, hello. I I do have a question. [24:07] >> Oh, hi. Okay, no problem. [24:10] >> Okay. Uh first of all, uh thank you for [24:12] that detailed explanation. I I [24:14] understand completely what an outreach [24:16] ambassador is um all about. The question [24:19] I have now is u is there a template of [24:24] let's say open source project and maybe [24:27] the community managers so the outreach [24:30] ambassadors could know who to message [24:33] directly. [24:34] >> Thanks. That's a lovely question [24:36] honestly. Thank you so much. So, um, if [24:41] you remember, I made a call out for the [24:44] project manager and outreach [24:46] ambassadors. So, um, the project manager [24:49] is on the call. That's Winner Bright. [24:51] Hi, winner. Say hi to everyone. [24:56] >> So, she [24:59] >> All right. So, she's going to be leading [25:01] the outreach initiative, right? [25:04] Our goal of getting us to 20 [25:07] So um she's going to be following her [25:10] providing um should I say direction for [25:16] this particular goal. So um you're going [25:19] to be hearing from her and then if you [25:21] have any questions you can always reach [25:24] out to her. So her name is Wina Bright [25:28] and that's number one. Then two there [25:30] are resources and um I I think she's [25:32] also going to um be doing more of [25:35] sharing the resource. [25:38] So um but let me just give you something [25:42] here. So I know this is a lot of [25:44] information right um to take in all in [25:47] few minutes and we will even soon be [25:51] leaving but then there is a playbook [25:53] that we have created that you can um sit [25:57] with and go through [26:01] in your spare time that gives you more [26:04] perspective about the project budgeting [26:06] and then how you can be an effective um [26:10] ambassador. So you can see here how to [26:13] be an effective array ambassador your [26:16] key talking points to just help you you [26:19] know it's a guide you don't have to [26:21] follow it the letter but it's something [26:23] that can just serve as a guide we have [26:26] templates for you also like an email [26:30] maybe you want to send it to somebody's [26:32] LinkedIn like a direct message or even [26:34] an email um social media post you know [26:39] then template um checklist for you also [26:44] to help you you know contact points. So [26:49] I'm going to be including let me just [26:51] note that down. I'm going to be [26:52] including um winner in here [26:56] um whoever you want to reach out to. So [26:59] you can always reach out to me or to um [27:02] winner but right now winner is the best [27:04] bet so that um I can always go focus on [27:08] other things. The reason why she's [27:09] leading this is so that I can focus on [27:11] the other things as the co-chair of the [27:14] working group. All right. So, um, what [27:18] else? What else? What else? Yes, let me [27:20] share this with you now. [27:32] All right. [27:46] Hold on. [28:01] That's one. Then two. So there is a list [28:04] that we have prepared by so the working [28:07] group um right now chaos there is chaos [28:11] con going on in Europe right if you've [28:15] been following what's going on there's a [28:17] conference going on and that's why you [28:20] you haven't seen some other members in [28:23] here people are busy a lot of meetings [28:24] was cancelled but I chose not to cancel [28:27] this meeting because of our new [28:29] contributors I don't want us to lose the [28:32] the motivation and the momentum. So [28:36] that's why I said, "Okay, I'm going to [28:37] keep this meeting today." So it's okay. [28:40] We're going to see other members. So [28:43] they prepared this um list already. But [28:48] um if you already have some communities [28:50] in mind also, you can you can then um [28:55] add your own. [28:57] Um although u winner is going to um [29:01] improve on this list you know to give us [29:04] some potential communities that we can [29:06] um follow up and engage. So [29:10] we have a list already. Um you can add [29:14] your um what country is the project in [29:17] the contact person. Then what's the [29:20] status? Have you started conversing with [29:22] them? Who is their outreach ambassador [29:25] for that? Um if you're interested in [29:27] this please you can take it up. I'm [29:30] going to put off my name now because [29:34] I need to really focus on the [29:37] development aspect of the project [29:39] budgeting. Currently, we are refactoring [29:41] the code base and I'm leading that [29:42] project. So, it should be good for me to [29:46] focus on that so that when people start [29:47] to use it, it will not have any problem. [29:51] Okay. So if you are interested in any of [29:54] this and you do not see a name already, [29:56] please feel free to add yours then you [30:00] can start. [30:02] >> All right. So do you have questions for [30:04] me [30:14] again? Am I speaking to myself? [30:18] What am I doing? [30:25] Hello everyone. Can you hear me? [30:29] >> Yes, I can. [30:31] >> Oh, okay. So, do you have questions for [30:39] any other question? [30:44] Okay. [30:46] So if maybe you think about any other [30:50] question um later you're not clear you [30:52] can reach out to me um from the next [30:56] meeting um that's going forward like in [30:59] two weeks time we are meeting again in [31:01] two weeks time let me stop recording [31:04] um so if you want to ask any question [31:08] you can reach out to me but from two [31:10] weeks time um winner will have settled [31:14] in into the role [31:16] And then you can then begin to reach up [31:19] to her from there.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS DEI Badging Meeting, Jan 28. 2026.md|CHAOSS DEI Badging Meeting, Jan 28. 2026 by YouTube]] ## Highlights - badge is not to um it's not like it's a certificate or something. It's just like um uh a a a a way for communities to actually take their time to document their DEI effort and then be able to showcase it to the world that oh this is what we've been doing and um we have a badge for it. So there is a way it works. There is a process that these communities have to go through, right? ([View Highlight](https://read.readwise.io/read/01kpb2vd2pmx43e3nv8qfrm7kd)) - Tags: 👻 ai highlighted - their computer or phone. So essentially this is how people are able to access the project. Right? Then she was able to talk about communication transparency, what they do in chaos and then the newcomer experiences and then the inclusive leadership. How is our governance like in chaos? And so she wrote all that down here. So let's say that she's done right. She's done here. ([View Highlight](https://read.readwise.io/read/01kpb2vd45ssjrd65363wjy5se)) - Tags: 👻 ai highlighted - then if it's that neither of the two, but they hosted it themselves, we don't have the capabilities for the bots to do that yet. So they have to do that um manually. I'm going to show you in a bit. So let me let me show you um about GitHub first. Now this one I've already authenticated. So um the first thing is going to do is that let's say she clicked on um login with GitHub. It's going to um GitHub is going to authenticate the the community manager. ([View Highlight](https://read.readwise.io/read/01kpb2vd60nrppp6rzb8d5rrvf)) - Tags: 👻 ai highlighted - your um selected rep um repositories. So let's assume that I am the community manager that has like a project that I have already put the uh DEIMD file. So I have one that I am using for test and demos. So um you can see it here. Hold on. ([View Highlight](https://read.readwise.io/read/01kpb2vd77q6bwwqhj45nppwm4)) - Tags: 👻 ai highlighted - put it in their community um in their community directory. So let let's go back to the project that have badged with us and I'm going to show you where they place where they placed their own the bad that they receive. You can see the badge here the bronze. So you the the project manager is going to receive this in their email. So let's go to um chaos. So chaos has badged. ([View Highlight](https://read.readwise.io/read/01kpb2vd8h9nrh9cdx5b63e7vh)) - Tags: 👻 ai highlighted