CHAOSS Weekly Community Call, Feb 10, 2026

CHAOSS Weekly Community Call, Feb 10, 2026 ![rw-book-cover](https://img.youtube.com/vi/op1xwH93KrQ/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, Feb 10, 2026](https://www.youtube.com/watch?v=op1xwH93KrQ) > [!note]+ Document Notes > tags: #chaoss #dei #project-badging #open-source #community #outreach > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=op1xwH93KrQ > date created: 2024-12-28 10:30 > > # 🏷️ Title: CHAOSS Weekly Community Call - DEI Project Badging Initiative Update >  ## 🧰 Action Inbox - [H1] Add contacts to project badging spreadsheet — community members with project connections #outreach - [H2] Create new minutes document annually — avoid version history overload #documentation - [H3] Share project badging workshop recording — DEI working group channel #education ## 🧭 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 DEI Badging](https://github.com/badging) - [Everything Open Source](https://everythingopensource.com) ## 📝 Summary - CHAOSS DEI working group launched structured outreach initiative for project badging - Goal to badge 20 open source projects by end of H1 2026 with dedicated project manager - Four new outreach ambassadors joined existing team members for community engagement - Community discussed archiving annual meeting minutes to reduce document load times - Open Source Summit North America CFP extended through end of week ## 📖 Main Content The CHAOSS DEI working group is implementing a more structured approach to project badging after limited progress over the past 6 months. The initiative centers on accountability through dedicated roles and systematic outreach to open source communities. Eddie Inca presented the working group's strategy, which includes appointing a project manager (Winnie Bri) and recruiting outreach ambassadors to engage with communities like Apache Foundation and Python Software Foundation. The team conducted a workshop during CHAOSS Con to train interested ambassadors on the project badging process. The group has established GitHub-based tracking through a dedicated repository and project board for transparency. Four new ambassadors (Thea, Richmond, Akitella, and one other) are joining existing team members to reach the 20-project goal by June 2026. Community members offered to provide contacts at target organizations, leveraging existing relationships to accelerate outreach efforts. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/op1xwH93KrQ?t=0) — [H1] Community call opening - Key idea: February 10th weekly CHAOSS community call with light agenda - Evidence: "Hey everybody, it's February 10th. You're here at the weekly community call for chaos" #### ⏱️ [03:45](https://youtu.be/op1xwH93KrQ?t=225) — [H1] DEI project badging initiative overview - Key idea: Working group pursuing two major goals including 20 project badges by H1 end - Evidence: "The DEI working group early this year we started working towards two major goals and one is to get the project budget to 20 project by the end of H1" #### ⏱️ [05:12](https://youtu.be/op1xwH93KrQ?t=312) — [H2] Accountability structure implementation - Key idea: Single point of accountability through project manager role to overcome past stagnation - Evidence: "Having a single point of accountability we are thinking that would help us to kind of move ahead" #### ⏱️ [06:30](https://youtu.be/op1xwH93KrQ?t=390) — [H1] Outreach ambassador program - Key idea: Dedicated ambassadors will engage communities about project badging benefits - Evidence: "To have outreach ambassadors that could help us with this goal of reaching out to communities" #### ⏱️ [08:15](https://youtu.be/op1xwH93KrQ?t=495) — [H2] Project manager appointment and progress - Key idea: Winnie Bri appointed as project manager with enthusiastic early work - Evidence: "Right now we have like a project manager who has started working enthusiastically and passionately shout out to you winner Bri" #### ⏱️ [09:45](https://youtu.be/op1xwH93KrQ?t=585) — [H2] GitHub-based tracking system - Key idea: Repository and project board created for transparent activity tracking - Evidence: "We created like a repository for the project badging outreach on the badging organization account and we've created like a project on the project board" #### ⏱️ [11:20](https://youtu.be/op1xwH93KrQ?t=680) — [H3] Ambassador recruitment workshop - Key idea: Workshop conducted during CHAOSS Con to train interested ambassadors - Evidence: "We then did was to organize a workshop which we recorded to explain how the project badge works for people that showed interest" #### ⏱️ [13:00](https://youtu.be/op1xwH93KrQ?t=780) — [H2] New ambassador cohort - Key idea: Four new people joined existing DEI working group members as ambassadors - Evidence: "On the call we had about four people... We have Thea, we have Richmond, we have Akitella" #### ⏱️ [16:45](https://youtu.be/op1xwH93KrQ?t=1005) — [H3] Community contact networking - Key idea: David suggests partnering with Everything Open Source for event visibility - Evidence: "I had an idea. I don't know if you guys know Abigail who has her everything opensource" #### ⏱️ [19:30](https://youtu.be/op1xwH93KrQ?t=1170) — [H3] Community members offering project contacts - Key idea: Don volunteers contacts at many target projects for outreach acceleration - Evidence: "I'm going to add some contacts in that spreadsheet. I have contacts at a lot of those projects" #### ⏱️ [21:15](https://youtu.be/op1xwH93KrQ?t=1275) — [H2] Minutes archiving discussion - Key idea: Annual document creation proposed to resolve performance issues from version history - Evidence: "Going to propose that we do in fact create a new document every year for the minutes" #### ⏱️ [24:00](https://youtu.be/op1xwH93KrQ?t=1440) — [H3] Open Source Summit CFP extension - Key idea: CFP for Minneapolis Open Source Summit extended to end of week - Evidence: "The CFP for the Open Source Summit North America, which is in Minneapolis this year, has been extended to the end of this week" ## 📚 References - [CHAOSS Project](https://chaoss.community/) - [DEI Badging Initiative](https://github.com/badging) - [Open Source Summit North America](https://events.linuxfoundation.org/open-source-summit-north-america/) - [Everything Open Source](https://everythingopensource.com) ## 🗣️ Paraphrase - The CHAOSS DEI working group is systematically approaching project badging with dedicated roles and structured outreach after recognizing the need for better accountability - Community members are leveraging existing relationships to provide direct contacts at target open source projects, significantly accelerating potential outreach success - Technical improvements to meeting documentation through annual archiving will address performance issues while maintaining accessibility for community members ## 📰 Newsletter The CHAOSS community is making significant strides in diversity, equity, and inclusion measurement with a revitalized project badging initiative. The DEI working group has appointed a dedicated project manager and recruited outreach ambassadors to systematically engage 20 open source projects by mid-2026. This structured approach addresses previous challenges through clear accountability and GitHub-based transparency. Community members are already contributing project contacts to accelerate outreach efforts, demonstrating the collaborative spirit that makes open source communities thrive. The project badging system helps organizations assess and improve their DEI practices through evidence-based evaluation. For WordPress projects considering DEI improvements, this framework offers valuable guidance and recognition opportunities. Resources: [CHAOSS Project](https://chaoss.community/), [DEI Badging](https://github.com/badging), [Community Handbook](https://handbook.chaoss.community/) ## ✅ Action Items #### Community - Maintainers: Review DEI badging criteria for project applicability assessment - Contributors: Connect target projects with CHAOSS outreach ambassadors through existing relationships - Sponsors: Evaluate DEI badging as measurable impact criterion for funding decisions - Ecosystem: Share project badging initiative across adjacent open source communities #### WordPress - Community: Assess WordPress.org projects for potential DEI badging pilot participation - Training: Incorporate DEI measurement concepts into community leadership curricula - Marketing: Highlight DEI initiatives and badging achievements in community communications - Meta: Evaluate DEI metrics integration into contributor experience measurement ## 🧪 Hypotheses - Dedicated project management role will significantly increase project badging completion rates compared to distributed responsibility model - Direct community contacts through existing relationships will achieve higher response rates than cold outreach campaigns - GitHub-based transparency will improve volunteer engagement through visible progress tracking - Annual documentation cycles will reduce technical barriers to community participation ### 📊 Methodology - Track project badging completion rates before and after project manager appointment - Compare response rates between contact-facilitated outreach versus direct cold outreach - Monitor GitHub engagement metrics on project board activity and repository contributions - Measure document load times and accessibility metrics across different archiving approaches ### ❓ Questions - How can WordPress projects adapt CHAOSS DEI badging criteria for CMS-specific community contexts? - What integration opportunities exist between CHAOSS metrics and WordPress contributor recognition systems? - How might structured DEI measurement influence open source project funding and sustainability models? ### 🔮 Future Research - Cross-platform DEI measurement standardization across major open source ecosystems - Automated DEI metric collection and badging pipeline development - Long-term impact assessment of DEI badging on community diversity outcomes ### 💡 Implications - Practice: Structured accountability models can revitalize stalled community initiatives through clear role assignment - Policy: DEI measurement frameworks may become standard requirements for organizational open source participation - Education: Community leadership training should incorporate systematic approach to volunteer coordination and transparency - Funding: DEI badging could become evaluation criterion for grant programs and corporate sponsorship decisions ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Project board screenshots mentioned, GitHub repository visualization - Improve: Process flow diagrams showing badging workflow, ambassador engagement maps #### 🔊 Aural learners - Present: Recorded workshop for ambassador training, community call audio format - Improve: Podcast-style DEI badging explainer, audio summaries of written resources #### 🗣️ Verbal learners - Present: Clear definitions of roles and processes, acronym explanations - Improve: Glossary of DEI terminology, analogies comparing badging to familiar certification processes #### 🧩 Kinesthetic learners - Present: GitHub project board interaction, hands-on workshop format - Improve: Interactive badging assessment checklist, step-by-step contribution guides #### 🧠 Logical learners - Present: Goal timelines with specific targets, systematic approach documentation - Improve: Decision tree for project eligibility, success metrics dashboard #### 🧑‍🤝‍🧑 Social learners - Present: Ambassador program with dedicated channels, community call participation - Improve: Peer mentoring program for new ambassadors, collaborative project evaluation sessions #### 🧘‍♀️ Solitary learners - Present: Self-guided project assessment criteria, individual contributor roles - Improve: Private reflection prompts for DEI assessment, independent study materials #### 🌿 Naturalistic learners - Present: Ecosystem thinking about open source community health - Improve: Community lifecycle analogies, sustainable engagement pattern examples ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Meeting transcript provides full content access - Improve: Structured headings in GitHub documentation, descriptive link text #### Keyboard navigation - Present: Standard video player controls, GitHub interface compatibility - Improve: Skip navigation for long transcripts, keyboard shortcuts documentation #### Contrast and readability - Present: Standard video platform interface meets basic contrast requirements - Improve: High contrast mode testing for project documentation #### Text resizing and reflow - Present: GitHub documentation supports browser zoom functionality - Improve: Mobile-responsive design verification for project resources #### Media and captions - Present: Full transcript available for meeting content - Improve: Automated captions for video content, downloadable transcript formats #### Forms and interactions - Present: Standard GitHub forms with built-in accessibility features - Improve: Error handling guidance for project submission forms #### Standards reference - GitHub platform generally meets WCAG 2.1 AA requirements for core functionality ### 🌍 DEIB Assessment #### Cultural breadth - Present: International community participation, multiple time zone considerations - Improve: Multi-language resource availability, global project representation examples #### Inclusive language - Present: Professional, welcoming tone throughout community interactions - Improve: Inclusive terminology guidelines, cultural context awareness training #### Neurodiversity support - Present: Multiple participation formats (audio, text, asynchronous) - Improve: Content warnings for meeting length, processing time accommodations #### Representation - Present: Diverse community leadership and active participation across identities - Improve: Balanced speaking opportunities, varied communication style accommodation #### Psychological safety - Present: Supportive community atmosphere, newcomer welcoming practices - Improve: Clear escalation procedures, community guidelines reinforcement ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear cause-effect relationship between accountability structure and project completion - Inductive strength: Pattern recognition from past outreach challenges informing new approach - Causal reasoning: Direct connection between project manager appointment and increased activity - Analogical strength: Comparison to successful ambassador programs in other open source communities #### Fallacies - Hasty generalization: Assuming 4-person workshop represents broader community interest - Appeal to novelty: Suggesting new approach is better simply because previous methods failed #### Tone of voice - Overall tone: Collaborative and optimistic with practical focus on measurable outcomes ### 🛡️ DARVO Analysis - Deny: No concerning denial patterns detected - Attack: No attacks on individuals or groups present - Reverse victim/offender: No victim/offender dynamic reversals observed - Emotional cues and rhetoric: Positive, solution-focused language throughout discussion ## 🎯 Conclusion The CHAOSS community demonstrates effective problem-solving by implementing structured accountability for their DEI project badging initiative. The combination of dedicated project management, volunteer ambassador programs, and transparent GitHub-based tracking addresses previous coordination challenges while leveraging community relationships for accelerated outreach. This systematic approach to community engagement and DEI measurement offers valuable lessons for other open source projects seeking to improve diversity outcomes through evidence-based assessment and recognition systems. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Structured accountability accelerates stalled community initiatives > [!quote] [CHAOSS Weekly Community Call](https://youtu.be/op1xwH93KrQ) by CHAOSS Community via YouTube. Published 2026-02-10. Accessed 2024-12-28. > "Having a single point of accountability we are thinking that would help us to kind of move ahead." DEI working group adopted project manager role after 6 months of limited progress on badging goals. [view highlight](https://youtu.be/op1xwH93KrQ?t=312#H1) #xref #articleseed ID:rw_chaoss_accountability ### [H2] Community relationship leveraging increases outreach effectiveness > [!quote] [CHAOSS Weekly Community Call](https://youtu.be/op1xwH93KrQ) > "I'm going to add some contacts in that spreadsheet. I have contacts at a lot of those projects." Existing community connections provide direct access to decision makers in target organizations. [view highlight](https://youtu.be/op1xwH93KrQ?t=1170 --- ## Full Transcript [00:00] loud. [00:03] Okay. Hey everybody, it's February 10th. [00:05] You're here at the weekly community call [00:07] for chaos. Great to see you all here. [00:11] I hope the weather's holding out for [00:14] everyone. It's actually sunny here today [00:17] and going to be like 58° which is I [00:21] don't know what in Celsius but way above [00:23] freezing which uh hopefully it's going [00:25] to melt some of the 6 in of snow that's [00:27] sitting outside cuz I'm so over it. I am [00:30] so over it. It has been below freezing [00:33] for I don't know maybe 3 weeks now. I [00:36] don't know. But it is a welcome change [00:39] for yours truly. [00:43] Um, if you're I think we've probably [00:44] asked this before. I feel like we have, [00:46] but we'll ask it again. Maybe people [00:48] change. I don't know. I can spell my [00:50] name. Here we go. I don't know what I [00:52] am. I don't think I think I'm a middle [00:54] of the day person, too, Dawn. I don't [00:56] like early morning. I go to bed early. [00:59] Yeah, I'm going to put that. [01:01] >> Yeah, that's what I am. I'm best in the [01:04] middle of the day. [01:05] >> Mhm. [01:07] >> I like it. [01:09] It's very um you know kind of covers all [01:13] the bases. [01:14] I like it. [01:20] Okay, let's jump into our agenda. We [01:23] have a light agendaish I guess lightish [01:26] uh just these two topics. So if you have [01:29] anything else you want to drop at the [01:30] end if there's time happy to chat about [01:32] other things. But um we have passed this [01:36] topic on twice now. So, thank you Eddie [01:38] Inca for your patience. Um, I'm gonna [01:41] just hand it over to you if that's okay. [01:43] So, you can can talk about this with [01:45] everybody. [01:47] >> Okay. Thank you very much. Hello, [01:50] Elizabeth. Hello, everyone. [01:54] Thank you. Um, can you hear me clearly [01:56] before I go on? I want to confirm. [02:01] >> Yeah. [02:02] >> Yeah. [02:04] >> All right. Thank you. Okay. So uh the [02:08] DEI working group [02:11] um early this year we [02:14] started working towards two major goals [02:17] and one is to get the project budget to [02:21] 20 project by the end of um H1 latest [02:26] that by the end of June we should have [02:28] um batched about 20 project open source [02:31] project and then second one is to [02:34] improve on the metrics we have for the [02:36] event badging based on past reviews. But [02:41] then right now I want to zero in on the [02:43] project badging. [02:45] And what we [02:48] decided to do in order to um achieve the [02:51] goal of um budgeting 20 project was to [02:55] get like a s good source of [02:57] accountability because we've been trying [02:58] to do this for the past 6 months and we [03:02] really haven't gotten a headway. So like [03:05] having a single point of accountability [03:08] we are thinking that would help us to [03:10] kind of move ahead. And so we are [03:13] thinking of having like a project [03:14] manager for this particular um goal and [03:19] then to have [03:21] um outreach ambassadors that could help [03:24] us with this um with this goal of [03:27] reaching out to communities in the open [03:30] source ecosystem and say hey this is um [03:34] project badging. This is what we do. [03:36] this is what it is about and we would [03:38] like uh you to to badge with us and then [03:42] um encourage project admins or community [03:45] managers to do that and um right now um [03:50] we we have made a call out I think we [03:52] did that in the um in 3 weeks ago and [03:56] right now we have like a project manager [03:58] who has started working enthusiastically [04:02] and passionately shout out to you winner [04:05] Bri right if you're on the call. She's [04:08] really um been on the onto the task. Um [04:13] and right now she had created um so we [04:15] created like a repository for the [04:18] project badging outreach on the badging [04:22] um um organization account and we've [04:26] created like a project on the project [04:28] board to be able to track their activity [04:31] and um winner has been uh on top of that [04:34] task. Then number two, we have um people [04:38] reach out to us to be ambassadors [04:41] already. Um so what we then did was um [04:46] two weeks ago when we had um the DEI [04:50] working group meeting that that [04:52] coincided with um the chaos con. Yeah. [04:56] But some people attended and what what [05:00] we then did was to organize a workshop [05:03] which we recorded to explain how the [05:08] project badge works for people that [05:10] showed interest in being um outreach [05:13] ambassadors. So um I'm looking forward [05:15] to get that recording from Elizabeth and [05:18] to um send it into the DEI working group [05:22] channel. Also we created like a personal [05:25] channel for for [05:29] the outreach ambassador like we did for [05:31] um DEI badgers who are focused on the [05:35] event badging so that we can um have [05:38] like a focused conversation and be able [05:40] to track activity for the outreach [05:43] ambassadors. So fingers crossed um we [05:46] have created a list up to like 20 [05:49] communities that we want to reach out [05:51] to. um winner is um still trying to put [05:55] all of that on the project board and um [05:57] people will then be assigned on GitHub. [06:00] Everything is going to be happening on [06:01] GitHub so that um for for transparency [06:04] sake and people can actually go to that [06:07] board and see the progress that we are [06:09] making. So fingers crossed on progress. [06:12] Um thank you very much. [06:19] Oh, that's so wonderful. That's really [06:22] great. Um, I had a couple questions. Is [06:25] there a way to [06:28] uh or would you be able to drop a link [06:30] to that repo here in the minutes? [06:33] >> Somebody add or somebody who else is [06:35] working on that project. That'd be [06:37] great. Just so people can see um or in [06:40] the chat, either one. [06:43] Um, and then the second qu what was the [06:47] second question? Oh, maybe you answered [06:49] this already. Um, and I missed it [06:51] because I was typing and I can't do more [06:53] than one thing at one time. Um, how many [06:55] people did you say had already expressed [06:57] interest [07:00] >> for to be outreach ambassadors, right? [07:02] >> Yeah. Yes. [07:04] >> Okay. So, on the call we had about um [07:07] four people. [07:09] >> Excellent. [07:10] >> Yes. But that will be in addition to the [07:12] members of the um DEI working group who [07:15] are already who had started working. Um [07:19] we have um the um DEI working group [07:23] members Mary Blessing [07:26] um Winnie Fred Young [07:31] um they have already started working and [07:34] then four other people are planning to [07:36] join us. We have Thea, we have Richmond, [07:39] we have Akitella and I think one other [07:42] person. So what what I've done was to um [07:45] bring everybody together [07:48] on um under the same group called [07:51] Outreach Ambassadors. So we have the [07:54] channel already. [07:58] Does that answer your question, [08:00] Elizabeth? [08:02] >> It does. And I accidentally stopped the [08:05] recording. Let me start that again. I I [08:08] can't do more than one thing at one [08:09] time. Okay. Sorry. Uh, did it stop or [08:13] did it keep going? Can anybody tell? I [08:16] can't tell. [08:19] >> I don't think it's recording. [08:22] >> I don't see the I don't see the light. [08:25] Oh, no. It is. It is recording. [08:26] >> Okay. Okay. Okay. [08:29] Sorry. I'm a professional. I swear. [08:32] Okay. Um, sorry, Eddie. That is that is [08:36] really great news. Um I can't wait to [08:38] hear more about this and the progress [08:40] that you all are making. So I hope that [08:43] you will be okay with providing [08:45] occasional updates here at the group um [08:47] just so we can all [08:48] >> this [08:49] >> Yeah, we would love that. We would love [08:50] that. [08:51] >> Um and also I'll probably ping you um [08:55] just as a DM because I want to put this [08:56] in the newsletter. So I'll just probably [08:59] get more info from you on like how [09:02] people can get involved where you know [09:04] where everything is. So, um, if that's [09:06] okay, I would love to put this in the [09:07] newsletter. [09:08] >> Yes, please. Thank you. [09:10] >> Awesome. And David has hands up. [09:14] >> Hi. Um, I like this um idea. Good job. [09:17] This is cool. Um, I had an idea. I don't [09:21] know if you guys know Abigail who has [09:24] her everything opensource. I'm going to [09:27] put it in the chat. Um, and she has like [09:30] a list of open source events that you [09:33] can just add to. Um, and I thought it [09:36] would be cool if we could maybe work [09:39] with her and just start putting our [09:40] badges like next to each of the events [09:42] that happen to have a badge. [09:45] >> Um, [09:46] >> yeah, [09:47] >> sort of like advertising. That's a [09:49] thing. [09:51] >> Okay. So, this is um what you just [09:53] suggested now is about open source [09:56] events. What we are focusing on now is [09:58] open source communities or projects like [10:02] Apache Infoundation [10:05] um the PSF [10:08] that's what the project badging is [10:10] focused on but the the other side of it [10:12] is the event badging that focuses on [10:15] what you are speaking about now [10:19] >> okay sorry um yeah [10:21] >> it's okay [10:22] >> I have I have been in conference world [10:25] so I probably just heard everything that [10:29] >> but I I would like I would like to say [10:31] here [10:32] >> okay um sorry Ruth before you go ahead [10:34] that if you know any person of contact [10:37] in any of these communities I already [10:40] pasted um the spreadsheet that we are [10:43] currently working on we we will soon [10:46] transfer it to the GitHub project but we [10:49] have the the spreadsheet already if you [10:51] happen to know any person of contact [10:53] that can help us accelerate the [10:55] conversation ation and all that. Um, [10:58] please uh don't hesitate to to talk [11:01] about it or share it with us. Thank you. [11:05] Ruth, please go ahead. [11:08] Oh, yeah. I was going to say something, [11:10] but I I realized that she doesn't have [11:12] it up yet. I know she plans to have like [11:14] projects, but I thought that was already [11:16] there, but I think that is still in like [11:22] >> Oh, for habig girl, right? [11:24] >> Yes. Yes, I know she had talked about [11:27] having a project kind of like a similar [11:29] thing where she highlights projects, but [11:32] I don't think that has been done yet. [11:34] So, I just checked just to confirm, but [11:37] it's not up there. Um, but I think [11:40] she'll be also be a good resource to ask [11:43] um because also she's like affiliated [11:46] with the PSF. [11:47] So, [11:50] >> okay. [11:53] >> Thank you, Ruth. Thank you, David. [11:58] >> Fun fact, she is the only other chaotic [12:00] that is in Cincinnati. So, big shout out [12:04] to her for being awesome and being here [12:07] in Cincinnati with me. Um, so if I need [12:09] to um reach out to her, uh I I think [12:12] she's still here. I know she was going [12:13] to school here. I don't think she's [12:15] moved on yet, but um yeah, I can even [12:17] help her sort stuff out if needed. So [12:22] cool. I didn't know she was working on [12:23] that. That's awesome. Thanks, Ruth. [12:28] Any other questions for um Edena? [12:36] And sorry, I turned my camera off. I [12:38] realize when I'm sharing my screen, it [12:40] really just drags my internet for some [12:43] reason. So, um yeah, I turned it off, [12:46] but I'm still here, I promise. [12:53] All right. Well, I guess we'll move on. [12:55] Um, thank you, Adinka. Yay. [12:58] >> Thank you. [12:58] >> Update. [13:02] >> Okay. Um, this is the archiving minutes [13:04] topic is something we've talked about [13:06] for a few times. Um, I think Don was the [13:09] one who brought up the fact that the [13:10] history, the version history can uh [13:13] maybe be bogging it down. And sure [13:16] enough, I believe that that is probably [13:18] what's happening because we've had this [13:19] document for a while. And if you think [13:22] of all of the version changes from all [13:25] of the groups on all of the page, like [13:27] keeping track of all of that is a lot. [13:29] So, um going to propose that we do in [13:33] fact create a new document every year [13:35] for the minutes. It kind of defeats our [13:39] purpose of having it all in one place. [13:41] um you know in one link to just [13:42] remember, but if we only change it once [13:44] a year, maybe it won't be so bad. Um and [13:48] also I think we if we put uh I think [13:50] Adrian had an idea of putting it um like [13:52] an index page at the top of the [13:54] document. So we can certainly do that. [13:56] That would point people in the right [13:58] direction if they still have the old one [14:01] bookmarked. So I'm going to throw that [14:03] out there. What do you all think about [14:05] that? [14:10] That sounds like a great idea. [14:20] Anybody see issues that I'm not seeing? [14:24] It will be a little bit of a pain point [14:26] to update those bookmarks for everybody. [14:29] Um, but I think it will make it easier [14:32] for everyone to load the dang document. [14:43] We could also, if we don't do, if we [14:45] don't want to do it every year, we could [14:46] do it maybe every two years or something [14:49] like that if it's if it's okay in a [14:52] year. I don't know. But for now, I think [14:55] just starting a new doc fresh is a good [14:58] way to get rid of all that [15:03] yearly works. Okay, cool. Thanks, Ruth. [15:08] Well, that was a quick discussion. That [15:10] was a quick quick topic. [15:13] Who else has uh has items? [15:22] Don't everybody speak at once. [15:25] Nobody has anything. That's okay. [15:32] All right. Well, um I don't want to just [15:35] hold us on the call for no reason. So, [15:40] >> I did add a reminder just letting people [15:42] know that the uh the CFP for the Open [15:46] Source Summit North America, which is in [15:48] Minneapolis this year, has been extended [15:50] to the end of this end of this week. [15:54] >> Um, a little extra little extra time. [15:58] >> Good to know. [16:00] >> Um, and [16:01] >> Oh, go ahead. [16:02] >> No, go ahead. I was just going to say if [16:04] people are looking for a Chaos Con NA uh [16:07] as a piggyback to this, we are not going [16:09] to do that this year. It's pretty tight [16:11] turnaround from the Chaos Con EU we just [16:13] did. Um so yeah, we're not going to [16:16] we're not going to do that this year [16:18] with OSSNA. Anyway, [16:26] >> what were you gonna say, Don? [16:27] >> Oh, I was so I was actually gonna say [16:29] something on another topic. So, um, [16:31] Edena, I'm going to I'm going to add [16:33] some contacts in that spreadsheet. I [16:35] have contacts at a lot of those [16:36] projects. Um, so I'm I'll I may forget [16:40] to continue updating the spreadsheet, [16:42] but I'm happy to chat about that at a [16:43] later point if you need some help [16:45] finding people at some of those [16:46] projects. [16:48] >> Thank you so much. I'm going to reach [16:49] out. Thank you. [16:50] >> Yeah, that'd be great. Thanks. [16:53] >> Yes. Yeah, that should go to everybody. [16:56] Anybody who has contacts. Um, [16:58] >> yeah, I think a lot of people on this [17:00] call have contacts at a lot of those [17:01] projects. So, I think if we crowdsource [17:04] this a bit with some of the people in [17:06] this community, we should be able to we [17:08] should be able to get you in touch with [17:09] most of those groups. [17:16] Awesome. Pawsome. [17:19] I want to give a quick shout out to our [17:22] secondyear CS student, Hassan. Welcome [17:26] to Chaos. glad you're here today. Uh [17:29] this is a kind of a quick meeting. [17:30] Usually it goes till uh 10 to the hour, [17:33] but um we're probably going to end a [17:36] little early today. So, welcome. Glad to [17:40] have you here. Do you know how to find [17:42] the info uh on Augur? Have you already [17:45] joined the Augur Slack channel and [17:47] everything? [18:03] if you haven't. It is just what is it? [18:08] WG augur 8 knot I think. I think that's [18:13] it. I'd have to go look. [18:18] But if you search all of our Slack for [18:21] Augur, that's the only one that should [18:22] come up, I think. [18:29] And you can also ask in the newcomer [18:31] channel where to find it if you can't [18:32] find it. Okay. [18:40] All right. Anything else before we end [18:42] our meeting? [18:53] Okay, well I will stop sharing here. [18:58] Thanks everybody. It was great to see [19:00] you all and I hope you have a good rest [19:02] of your day. Enjoy your time back. Go [19:04] take a nap or something fun. [19:06] I'll see y'all later. [19:09] >> Bye everybody.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, Feb 10, 2026.md|CHAOSS Weekly Community Call, Feb 10, 2026 by YouTube]] ## Highlights - end if there's time happy to chat about other things. But um we have passed this topic on twice now. So, thank you Eddie Inca for your patience. Um, I'm gonna just hand it over to you if that's okay. So, you can can talk about this with everybody. >> Okay. Thank you very much. Hello, Elizabeth. Hello, everyone. Thank you. Um, can you hear me clearly before I go on? I want to confirm. ([View Highlight](https://read.readwise.io/read/01kpb3yfxf75gm003dwavpj2j0)) - Tags: 👻 ai highlighted - people can get involved where you know where everything is. So, um, if that's okay, I would love to put this in the newsletter. >> Yes, please. Thank you. >> Awesome. And David has hands up. >> Hi. Um, I like this um idea. Good job. This is cool. Um, I had an idea. I don't know if you guys know Abigail who has her everything opensource. I'm going to put it in the chat. Um, and she has like ([View Highlight](https://read.readwise.io/read/01kpb3yfyck2pxq3pswgwchxqt)) - Tags: 👻 ai highlighted - >> Um, and >> Oh, go ahead. >> No, go ahead. I was just going to say if people are looking for a Chaos Con NA uh as a piggyback to this, we are not going to do that this year. It's pretty tight turnaround from the Chaos Con EU we just did. Um so yeah, we're not going to we're not going to do that this year with OSSNA. Anyway, >> what were you gonna say, Don? >> Oh, I was so I was actually gonna say something on another topic. So, um, ([View Highlight](https://read.readwise.io/read/01kpb3yfzjtzws7x3p03p6k3y7)) - Tags: 👻 ai highlighted - Edena, I'm going to I'm going to add some contacts in that spreadsheet. I have contacts at a lot of those projects. Um, so I'm I'll I may forget to continue updating the spreadsheet, but I'm happy to chat about that at a later point if you need some help finding people at some of those projects. >> Thank you so much. I'm going to reach out. Thank you. >> Yeah, that'd be great. Thanks. >> Yes. Yeah, that should go to everybody. Anybody who has contacts. Um, >> yeah, I think a lot of people on this ([View Highlight](https://read.readwise.io/read/01kpb3yg0t2hr7awxjmeye3p2s)) - Tags: 👻 ai highlighted