CHAOSS Weekly Community Call, Feb 24, 2026

CHAOSS Weekly Community Call, Feb 24, 2026 ![rw-book-cover](https://img.youtube.com/vi/SKVUoOpZgcQ/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, Feb 24, 2026](https://www.youtube.com/watch?v=SKVUoOpZgcQ) > [!note]+ Document Notes > tags: #chaoss #community-meetings #open-source #metrics #documentation > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=SKVUoOpZgcQ > date created: 2024-02-24 15:30 > > # 🏷️ Title: CHAOSS Weekly Community Call - February 24, 2026 >  ## 🧰 Action Inbox - [H1] Update WordPress redirect to temporary (302) instead of permanent (301) — prevent browser caching issues #documentation - [H2] Implement Slack meeting reminder bot using Google script and webhooks — improve meeting attendance #automation - [H3] Create blog post on supply chain analysis methodology using CHAOSS tools — help community with ecosystem analysis #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 Software Page](https://chaoss.community/software/) - [TeamUp Calendar Integration](https://teamup.com/) ## 📝 Summary - CHAOSS community discussed documentation improvements and meeting logistics for 2026 - Elizabeth (community manager) outlined new process for meeting minutes archive using redirects - Community identified need for better supply chain and ecosystem analysis capabilities beyond project-level metrics - Technical discussions covered Slack integration challenges and daylight saving time complications - CFP reminders shared for upcoming conferences with approaching deadlines ## 📖 Main Content The CHAOSS weekly community call focused on operational improvements and strategic discussions about expanding analytical capabilities. The community addressed practical challenges around documentation management, meeting scheduling across time zones, and tool limitations when analyzing broader open source ecosystems. Key technical discussions centered on the gap between current CHAOSS tools (Augur, GrimoireLab) that require predefined repository lists versus emerging needs for supply chain and ecosystem-wide analysis. This reflects growing requirements from regulations like CRA (Cyber Resilience Act) and organizations seeking to understand broader open source landscapes. The meeting also covered infrastructure improvements, including a new documentation redirect system and efforts to restore automated Slack meeting reminders that were broken when the community moved from Google Calendar to TeamUp. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/SKVUoOpZgcQ?t=0) — [H1] Welcome and agenda setup - Key idea: Elizabeth opens February 24th community call, sharing screen and agenda - Evidence: "Hi. You're here at the Chaos Weekly Community Call. It is February 24th. I am Elizabeth, the Chaos community manager." #### ⏱️ [03:15](https://youtu.be/SKVUoOpZgcQ?t=195) — [H2] New documentation archive process - Key idea: CHAOSS implementing single redirect URL for meeting minutes to solve version confusion - Evidence: "from now on, this is the only link anybody will ever have to remember is just working group minutes" #### ⏱️ [06:45](https://youtu.be/SKVUoOpZgcQ?t=405) — [H3] WordPress redirect configuration issue - Key idea: Adrian identifies need for temporary redirect instead of permanent to prevent browser caching - Evidence: "we want the temporary one cuz this link is going to keep changing year over year" #### ⏱️ [09:30](https://youtu.be/SKVUoOpZgcQ?t=570) — [H2] Daylight saving time complications - Key idea: Meeting times tied to different time zones create confusion during DST transitions - Evidence: "these meetings right here are going to change with daylight saving on March 8th" #### ⏱️ [15:20](https://youtu.be/SKVUoOpZgcQ?t=920) — [H2] Slack integration challenges - Key idea: Lost automated meeting reminders when switching from Google Calendar to TeamUp - Evidence: "when we had it on Google, there was a nice Slack reminder that said, 'Hey, there's a meeting happening'" #### ⏱️ [18:45](https://youtu.be/SKVUoOpZgcQ?t=1125) — [H3] Potential solution from To-Do group - Key idea: Anna from To-Do group has bot code using Slack webhook and Google script - Evidence: "she has a bot that does this. It posts in the channel when the next meeting is" #### ⏱️ [22:10](https://youtu.be/SKVUoOpZgcQ?t=1330) — [H1] Supply chain analysis limitations discussion - Key idea: Don raises issue about CHAOSS tools requiring predefined repository lists versus ecosystem analysis needs - Evidence: "historically, the way that our software has worked...you give it a list of GitHub organizations" #### ⏱️ [25:30](https://youtu.be/SKVUoOpZgcQ?t=1530) — [H2] Examples of unmet analysis needs - Key idea: Users requesting broader analysis like "all open source work happening in China" that current tools can't support - Evidence: "I want to better understand all of the open source you know work happening in China and I want to use chaos metrics" #### ⏱️ [28:15](https://youtu.be/SKVUoOpZgcQ?t=1695) — [H2] Matt's supply chain research methodology - Key idea: Research using deps.dev for technical dependencies plus Augur for social connections - Evidence: "we were using deps.dev for the technical connections between projects" #### ⏱️ [32:40](https://youtu.be/SKVUoOpZgcQ?t=1960) — [H3] Three-step analysis process - Key idea: Matt outlines technical dependencies first, social second, then CHAOSS metrics third - Evidence: "Technical first, social second and then ask like sustainability related metrics questions third" #### ⏱️ [35:50](https://youtu.be/SKVUoOpZgcQ?t=2150) — [H2] Blog post suggestion for methodology - Key idea: Don suggests documenting the supply chain analysis approach for community - Evidence: "I wonder if it might be good for you all to do a maybe a blog post about that" #### ⏱️ [39:20](https://youtu.be/SKVUoOpZgcQ?t=2360) — [H3] Augur naming confusion - Key idea: Multiple projects named "Augur" including blockchain project causing search confusion - Evidence: "there's another open source project called Augur that is something completely different" #### ⏱️ [42:15](https://youtu.be/SKVUoOpZgcQ?t=2535) — [H3] CFP reminders and closing - Key idea: Elizabeth shares conference CFP deadlines and wraps up meeting - Evidence: "Just two reminders about CFPs...both excellent conferences and yeah, you have you have a little bit of time" ## 📚 References - [CHAOSS Community](https://chaoss.community/) - [deps.dev](https://deps.dev/) - [TeamUp Calendar](https://teamup.com/) - [Augur GitHub Repository](https://github.com/chaoss/augur) ## 🗣️ Paraphrase - CHAOSS is implementing a streamlined documentation system using redirects to eliminate confusion about meeting minute locations and versions - Current CHAOSS analysis tools require predefined repository lists, limiting their use for broader ecosystem or supply chain analysis that regulations and organizations increasingly need - The community is working to restore automated meeting notifications and improve technical infrastructure while managing the complexity of global time zone coordination ## 📰 Newsletter **CHAOSS Community Tackles Growing Pains and Expands Analytical Vision** The CHAOSS community is evolving its tools and processes to meet growing demands for open source analysis. This week's community call highlighted both practical improvements and strategic challenges as the project matures. Key developments include a new documentation redirect system that simplifies meeting minute access and ongoing work to restore automated Slack meeting reminders. More significantly, the community is grappling with requests for ecosystem-level analysis that go beyond current tool capabilities. The discussion revealed an interesting gap: while CHAOSS metrics excel at project-level analysis, emerging needs around supply chain compliance and regional ecosystem mapping require different approaches. Matt shared promising research combining technical dependency mapping with social network analysis. This evolution reflects the broader maturation of open source governance and compliance requirements. As organizations face new regulations and seek deeper supply chain visibility, metrics projects like CHAOSS must balance focused excellence with expanding use cases. Resources: [CHAOSS Software](https://chaoss.community/software/), [Augur Documentation](https://oss-augur.readthedocs.io/), [GrimoireLab](https://chaoss.github.io/grimoirelab/) ## ✅ Action Items #### Community - Contributors: document supply chain analysis methodology, create redirect troubleshooting guide - Maintainers: implement Slack meeting reminder automation, update calendar integration documentation - Ecosystem: explore partnerships with dependency analysis tools, evaluate ecosystem mapping approaches #### OSPO - Policy & Governance: review meeting minute retention policies, establish documentation archival procedures - Software Inventory: assess CHAOSS integration for SBOM workflows, evaluate deps.dev reliability - Developer Support: create ecosystem analysis training materials, document tool limitations - Community Engagement: coordinate with supply chain analysis researchers, share methodology blog posts #### Open Source - Technical independence: ensure CHAOSS tools remain vendor-neutral for ecosystem analysis - Governance artifacts: document decision processes for expanding analytical scope - Sustainability: balance focused project metrics with broader ecosystem needs ## 🧪 Hypotheses - Automated meeting reminders will increase community call attendance rates - Single redirect URL will reduce confusion about meeting minute locations - Supply chain analysis methodology documentation will attract new CHAOSS users - Integration with deps.dev will enable socio-technical network analysis for compliance ### 📊 Methodology - A/B testing of meeting reminder effectiveness through Slack engagement metrics - User experience surveys comparing old vs new documentation access patterns - Case studies of supply chain analysis workflows using CHAOSS + deps.dev integration ### ❓ Questions - How can CHAOSS balance project-level focus with ecosystem analysis demands? - What partnerships would enable broader supply chain visibility without scope creep? - How should open source metrics projects handle increasing compliance requirements? ### 🔮 Future Research - Integration patterns between project metrics and dependency analysis tools - Scalability challenges in ecosystem-wide open source analysis - Community governance models for expanding analytical scope ### 💡 Implications - Practice: Organizations need multi-tool workflows for comprehensive supply chain analysis - Policy: Open source compliance requires both project-level and ecosystem-level metrics - Security: Dependency analysis becomes critical for vulnerability management - Education: Community needs training on when to use different analytical approaches ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade #### 👀 Visual learners - Present: Meeting agenda screenshots, calendar integration examples - Improve: Workflow diagrams for supply chain analysis, architecture diagrams for tool integration #### 🔊 Aural learners - Present: Community call recording with natural discussion format - Improve: Audio summaries of key decisions, narrated tool demonstrations #### 🗣️ Verbal learners - Present: Technical terminology explanations, collaborative problem-solving discussions - Improve: Glossary of CHAOSS/supply chain terms, analogies for complex concepts #### 🧩 Kinesthetic learners - Present: Step-by-step redirect implementation, hands-on tool configuration - Improve: Interactive tutorials for ecosystem analysis, sandbox environments #### 🧠 Logical learners - Present: Three-step analysis methodology, clear decision trees for tool selection - Improve: Flowcharts for when to use different approaches, metrics comparison tables #### 🧑‍🤝‍🧑 Social learners - Present: Community call format, collaborative problem-solving - Improve: Working groups for specific analysis types, peer mentoring programs #### 🧘‍♀️ Solitary learners - Present: Documentation archives, self-serve meeting recordings - Improve: Self-assessment quizzes for analysis readiness, independent learning paths #### 🌿 Naturalistic learners - Present: Ecosystem analysis metaphors, organic growth of tool requirements - Improve: Supply chain ecosystem analogies, sustainability impact examples ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in meeting notes, descriptive link text - Improve: Alt text for calendar screenshots, ARIA labels for complex workflows #### Keyboard navigation - Present: Standard web navigation patterns - Improve: Skip links for long transcripts, keyboard shortcuts for timestamp navigation #### Contrast and readability - Present: Standard text formatting meets basic contrast requirements - Improve: High contrast mode for technical diagrams, larger text options for complex content #### Media and captions - Present: Video recording available with auto-captions - Improve: Professional captions with speaker identification, downloadable transcripts #### Forms and interactions - Present: Basic meeting registration and calendar access - Improve: Accessible date pickers for calendar integration, clear error messaging ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global time zone accommodation, international community participation - Improve: Multi-language meeting summaries, regional ecosystem examples #### Inclusive language - Present: Professional tone, technical terms explained - Improve: Plain language summaries, cultural context for compliance requirements #### Neurodiversity support - Present: Structured meeting format, clear agendas - Improve: Shorter content chunks, consistent formatting patterns #### Representation - Present: Diverse community voices, collaborative decision-making - Improve: Highlight contributions from different regions, inclusive imagery #### Psychological safety - Present: Respectful technical discussions, acknowledgment of confusion - Improve: Clear escalation paths for conflicts, explicit inclusion statements ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear cause-effect relationships between DST changes and meeting confusion - Inductive strength: Evidence from user requests supporting need for ecosystem analysis - Causal reasoning: Technical limitations directly linked to unmet user needs - Analogical strength: Comparison between project-level and ecosystem analysis approaches #### Fallacies - Appeal to authority: Over-reliance on single researcher's methodology without broader validation - False dilemma: Presentation of either/or choice between current tools and complete ecosystem coverage #### Tone of voice - Overall tone: Collaborative and problem-solving oriented with technical focus and community care ### 🛡️ DARVO Analysis - Deny: No evidence of denial patterns - Attack: No attacks on community members or critics - Reverse victim/offender: No victim/offender reversal present - Emotional cues and rhetoric: Positive, solution-focused language with acknowledgment of limitations ## 🎯 Conclusion The CHAOSS community is navigating a critical growth phase where operational improvements intersect with expanding analytical demands. The implementation of streamlined documentation processes and meeting automation reflects organizational maturity, while discussions about supply chain and ecosystem analysis highlight the tension between focused excellence and broader applicability. The three-step methodology for socio-technical supply chain analysis offers a practical bridge between current CHAOSS capabilities and emerging compliance needs. This approach—technical dependencies first, social networks second, then CHAOSS metrics—provides a replicable framework for organizations facing new regulatory requirements. Moving forward, the community's success will depend on maintaining tool quality while strategically expanding analytical scope through partnerships and methodology documentation rather than feature creep. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] CHAOSS tools require predefined repository lists limiting ecosystem analysis > [!quote] [CHAOSS Weekly Community Call](https://youtu.be/SKVUoOpZgcQ) by CHAOSS Community via YouTube. Published 2024-02-24. Accessed 2024-02-24. > "historically, the way that our software has worked...you give it a list of GitHub organizations" Don identifies fundamental limitation preventing broader supply chain analysis workflows. [view highlight](https://youtu.be/SKVUoOpZgcQ?t=1330#H1) #xref #articleseed ID:rw_20240224001 ### [H2] Three-step socio-technical supply chain analysis methodology proven effective > [!quote] CHAOSS Weekly Community Call > "Technical first, social second and --- ## Full Transcript [00:02] There we go. Okay. Hi. You're here at [00:04] the Chaos Weekly Community Call. It is [00:07] February 24th. I am Elizabeth, the Chaos [00:10] community manager. I guess I could [00:12] change my name here. [00:14] There we go. I'm Elizabeth. Uh, great to [00:18] see you all here. Let's share the [00:20] screen. Let's share the minutes. Um the [00:25] sometimes my uh captioning covers [00:28] everything that I'm I need. I don't like [00:30] that. Why does it do that? I don't know. [00:36] >> There we go. Um if you would like to add [00:38] your name to the agenda and tell us your [00:40] favorite thing about March since we're [00:41] getting ready for March. I'm so over [00:44] February and winter. Um that'd be great. [00:48] So yeah. [00:52] And yes, Don, I I would like to see some [00:54] pictures if you are so inclined to take [00:57] pictures because I need that in my life. [01:00] >> I do. I'll send you some. I took some [01:01] pictures and sent them to my mom when I [01:03] was talking to her on the phone. So, [01:04] I've got some right here. [01:05] >> Yes. Excellent. Excellent. [01:08] >> Very current. [01:09] >> That is I really miss getting out with [01:11] my camera mostly. Uh it's just I'm not a [01:15] you know, some nature photographers are [01:16] like out at 5:00 a.m. in the Arctic. No, [01:19] >> I was going to say you can take pictures [01:21] of snow. [01:22] >> I did. I did. The first time it snowed. [01:24] I was like, "Oo, this is pretty." Yeah. [01:26] Let me get my camera. No, I don't know. [01:29] I don't want it now. I want the flowers [01:32] for sure. Um Oh, I've been signed out. [01:35] Hope that didn't screw up our recording. [01:37] There we go. Um anyway, let's go ahead [01:39] and start with our agenda. Um, okay. So, [01:44] this has been a conversation we've had a [01:46] few times in this meeting about these [01:49] minutes and this gigantic dock that we [01:51] have. Um, so we decided to start a new [01:53] dock every year like in March so that we [01:56] will have the first few meetings for [01:58] everybody still in the same dock. Um, [02:01] and then there was an issue of well how [02:03] are we going to get everybody to go to [02:05] the next one. So, just chatting with [02:07] Adrian this morning. He hopped on the [02:09] newcomer hangout. So, we didn't have any [02:11] newcomers, so we uh spent the time going [02:13] over that process and some other um [02:17] interesting things about the website and [02:19] our GitHub plugin and all the good [02:21] things. So, um thank you Adrian for [02:23] thinking this through with me. Um so [02:25] now, from now on, for starting next [02:27] week, from now on, this is the only link [02:29] anybody will ever have to remember is [02:31] just working group minutes. Um, and then [02:34] it it goes to an empty doc now, but it [02:37] will be the new dock um for everybody. [02:41] So, we don't have to remember where the [02:43] minutes are, what year it is, anything. [02:46] It will just it'll just magically [02:47] happen. And then we are going to keep [02:49] this also on the website and it'll be [02:51] just the index. Here's all the years [02:53] because it's all it's all there. It's in [02:55] the chaos drive in Google and linked in [02:58] um each of these tabs. It's linked here, [03:02] you know. So maybe we will just put the [03:05] link to the archive and just leave it at [03:08] that instead of every tab. I would have [03:10] to add then the year on every tab like [03:12] no that's too much too much work. So, [03:16] um, yeah. So, that's that's the new [03:17] process and I hope that makes it so much [03:20] easier for everyone. And it's on the on [03:22] the back end, it's super easy to just [03:24] change the redirect to because it can go [03:26] wherever we want and then it would just [03:28] be adding another line to this one [03:30] document here. So, I hope that makes [03:33] sense to everyone. Let me know what I'm [03:35] missing in that process. [03:38] There's glaring problems with that. So [03:41] over each year we'll just have like a [03:43] giant one giant archive dock for the [03:46] year essentially. [03:48] >> And then that top link is just like a is [03:52] that the current year? [03:53] >> It's it's yes. So yes. So this is uh [03:56] just a redirect in our WordPress [03:58] instance [03:59] >> and then we'll just change where where [04:00] it redirects to [04:02] >> and if you want to go look at some [04:03] minutes from two years ago, you click [04:05] that second link. Yep. And it'll just [04:07] like link out to the different archives. [04:09] >> Yep. It'll just be an index of all the [04:11] years. [04:12] >> Okay. [04:13] >> So, [04:15] make it super easy. And then instead of [04:17] each tab having the archived minute, you [04:20] know, having this on every tab, it'll [04:22] just be [04:23] >> that link, the archive link. [04:24] >> How old is this document? [04:27] >> Oh, uh, this that's a great question. I [04:30] want to say [04:34] 2020, [04:35] early 2024 maybe. So, maybe two years. [04:39] Okay. Okay. [04:41] >> Um, so yeah, so we've been just, you [04:43] know, cop, you know, um, moving the [04:46] stuff over to a new doc, but we've been [04:48] all the the versions are still there. [04:51] And so, you know, it's just [04:52] >> I get it. Yeah. [04:54] >> Yeah. [04:55] >> Okay. Okay. Yeah, that makes sense. [04:59] >> Well, also, um, and the new doc take out [05:01] these inactive ones, which we kind of [05:03] kept around and like [05:05] >> they can be in the archive, but they [05:06] don't need to be in the current doc, I [05:07] don't think. [05:07] >> For sure. Yep. [05:09] >> So, [05:11] okay. Any other questions, comments, [05:16] thoughts, stuff. [05:22] >> Oh, that makes sense. Until we change it [05:24] next time. [05:25] >> Yeah. So, this will happen next starting [05:27] the meetings next week. Um, and I'll [05:28] change the calendars, of course, and I [05:30] put it in the working group leader um [05:32] Slack so that those folks know as well. [05:35] But I'll just make sure everybody kind [05:36] of knows as much as we can. So, [05:43] okay. Um, the other uh thing is the [05:48] daily saving time which is happening in [05:50] two weeks. Um, and that causes chaos [05:53] with 1s, not the good kind like we are. [05:56] Um, yeah. So, it's the time when those [05:59] of you who don't know, it's the time [06:00] when the US starts daylight saving. A [06:03] lot of people don't, some people do, [06:05] some people never do. It's kind of a a [06:07] mess. Um, and we have our meetings are [06:10] tied to different time zones. So, like [06:13] these meetings right here are going to [06:15] change with daylight saving on March [06:18] 8th. All of these meetings. So, if [06:19] you're in a place that doesn't change or [06:22] hasn't changed yet, these will all be at [06:24] a different time for you. [06:26] Um, these meetings are tied to West [06:28] Africa time and do not change with DST. [06:31] So, if you are in a place that does do [06:33] DSD and has changed, these will be at a [06:37] different time zone for you or time for [06:39] you. You get where I'm going with this? [06:42] So, the reason we have all of these tied [06:44] to different times is because it makes [06:46] more sense for folks who are in that [06:48] area, right? So, like there's why would [06:51] folks in Africa have to change their [06:54] like nobody there does a DST. So, it [06:56] doesn't make any sense for us to force [06:58] them to change with the US. Um, same [07:01] thing with the Chaos Asia. It doesn't [07:03] make any sense. And then the UTC one, [07:04] they decided to do that and that's I [07:06] mean, why not? YOLO, you know, hey, what [07:09] it works for them. That that's what [07:10] would be the best for them. So, um [07:15] Oh, I need Adrienne says I need to [07:17] change the redirect on WordPress 301 [07:18] permanent to three [07:21] to temporary. [07:22] >> Probably a bit of a tech. I don't know [07:23] how much control you have on WordPress, [07:25] but there are different types of [07:26] redirects [07:27] >> and we want the temporary one cuz this [07:29] link is going to keep changing year over [07:31] year and we we want people's browsers to [07:32] keep checking the current redirect and [07:35] not just saving this redirect to the [07:37] 2026 doc forever. [07:40] Especially because the more if people [07:41] click on this before this gets changed, [07:43] their browsers are going to remember the [07:45] 2026 link [07:46] >> like mine. [07:48] probably you I think you can like clear [07:49] your there's there's ways to clear it [07:51] like your it's just a temporary storage [07:53] in your browser but it's not something [07:55] that frequently gets cleared by most [07:58] people. So [07:59] >> okay that is Adrian see this is why I [08:03] love [08:04] >> I'd sanity check that before I started [08:05] changing all the links and all the um I [08:07] mean I can still update the link I just [08:09] don't want people to click it until we [08:10] fix that. [08:11] >> Yes, I appreciate that so much. Um, I [08:15] Adrienne, what I need really is for you [08:17] to just follow me around my day and just [08:20] like point out the things that I'm [08:23] missing or like like just clean up my [08:25] mess as I go cuz you're amazing at that. [08:28] Thank you so much. I would never have [08:30] caught that ever. So, good call. [08:32] Excellent work. I really appreciate you [08:35] very much. [08:35] >> Buy the Cheetos. You should buy [08:40] >> Exactly. Just my crumbs. as I go along [08:44] cuz I make I kind of do make a mess [08:46] wherever I go. So, here we are. Um, [08:51] sorry. Um, yeah. So, anyway, daylight [08:53] saving is a mess. Um, but the good news [08:57] is the chaos calendar will be the single [08:59] source of truth because it is smart and [09:01] knows where everything [09:04] everything is. No, there is not an AI, [09:06] Elizabeth. although they probably would [09:08] do they would probably be more [09:10] productive and better at things than I [09:12] am. But you know what? It's okay. It's [09:14] all right. Uh so yeah. So anyway, if [09:17] you're subscribed to the chaos calendar, [09:19] you'll be good. Uh if you're wondering, [09:22] you can go now and see what time things [09:24] will be for you later. Uh because it's [09:26] smart that way and it already knows. [09:28] Just make sure that you're looking at it [09:30] in your time zone. So, [09:33] okay, questions about that? Any [09:35] questions? [09:39] I wish there was an easy fix for [09:41] daylight saving. I don't think there is. [09:44] >> I just was reading through some of the [09:45] daylight savings stuff and um not to [09:48] make things any more complicated than [09:49] they probably already are, but like [09:52] like the meeting like if you are in a [09:54] region that honors daylight savings, but [09:57] the meeting is pinned to UTC, your [09:59] meeting the meeting time for you is [10:01] still going to change even if the [10:02] meeting time for everyone else doesn't. [10:04] >> Correct. Maybe we need to just write a [10:06] blog post or something that's like the [10:07] comprehensive guide to understanding [10:09] when the crap you're supposed to be [10:10] meeting. [10:12] >> Well, and you know, a while ago, so we [10:14] used to have the calendars tied to to [10:16] Google and then we had all these [10:18] different meetings and people would have [10:19] to subscribe to everything or nothing. [10:21] So, it was did not give us the um [10:23] granularity that we wanted. So, we [10:25] switched to team up and there they you [10:27] know are we host on them and um it's [10:30] been great like it that you can [10:32] subscribe to just one calendar. We have [10:33] a lot of flexibility with how that's run [10:35] and it keeps track of all this stuff. [10:37] So, it's wonderful. The only um drawback [10:40] is there when we had it on Google, there [10:43] was a nice Slack reminder that said, [10:45] "Hey, there's a meeting happening. If [10:47] you want to go to it, here's the here's [10:50] the link." And then that that is broken. [10:52] And I tried this is Adrian maybe another [10:56] conversation you and I have to have [10:58] >> conveniently. So, conveniently, Sean [11:00] gave me, I guess, admin access to Slack [11:03] like yesterday because I was trying to [11:04] get I'm trying to set up a uh a Slack [11:07] bridge because we have an internal [11:08] maintainers chat for Augur on Slack and [11:10] there's also a Discord server and it's [11:12] like, hang on, half the maintainers are [11:14] over here and half of them are over [11:15] here. I just want to bridge these with a [11:17] bot so that anything that gets sent in [11:19] either place gets sent to the other [11:20] place. Um, and I've just been trying to [11:23] deal with a half unmaintained bridging [11:26] software. [11:27] So, but I could probably look at the [11:30] Slack integrations while I'm in there. [11:32] >> Yeah, I mean that would be great. I I [11:33] was resorting to this and that theft and [11:37] that worked. It worked for some meetings [11:39] and not for others. And I don't I don't [11:42] know why. And um then I got distracted [11:44] and on to other things. So, I never had [11:46] time to go back and really dig into what [11:48] I had broken. But, it did work for a [11:50] minute. I think that would be really [11:52] helpful if we could have a Slackbot that [11:54] just told people when meetings were [11:56] happening. Um, [11:57] >> I was actually, so I was talking to um [12:00] Anna from the to-do group and they have [12:03] a bot that um that does this. It posts [12:06] in the channel when the next meeting is. [12:08] It gives you like an hour notice or [12:10] something. Um, and she recently just [12:12] changed the way that she did that um to [12:14] something that might work for us. [12:16] >> Okay. [12:17] >> And she she sent me all of the code. So, [12:19] what I'm going to do is I'm going to [12:21] send that I guess maybe to you and [12:23] Adrien. [12:24] >> Okay. Yeah, that would be great. I I'll [12:26] just send you everything she sent me [12:28] >> and then if that works or [12:31] >> Yeah. [12:32] >> Yeah. [12:32] >> I'll send it to the two of you and then [12:34] we'll see what happens. [12:35] >> Yeah, that would be awesome. Um back [12:37] when So that used to be a seamless [12:39] integration between uh Google and Slack [12:41] and then Slack broke that. So To-Do [12:44] group had a workaround and I we borrowed [12:46] it from them at the time and then we [12:48] moved off of of Google so we didn't need [12:50] it. Um but I never got back around to [12:53] kind of closing that loop. So, yeah, [12:55] that would be awesome. That would be [12:56] >> Yeah, I guess it's a it's a Slack web [12:58] hook and a Google script, [12:59] >> right? Okay. Okay. And would that work [13:02] if our calendar's still on team up? [13:05] >> I have no idea. [13:06] >> Okay. [13:06] >> I'll be honest, she sent it to me [13:08] because I was like, "Oh, that sounds [13:09] really good." And then I just haven't [13:10] had time to look at it. And so, [13:12] >> so now I'm just passing the buck. You [13:14] see how that works? [13:15] >> Yeah, I love it. I I'm great at that. [13:16] That's why I'm going to pass it right on [13:18] to Adrian as soon as this call. No, I'm [13:20] just kidding. Um, there is like Slackish [13:23] integration, but it requires people to [13:25] have a team up account. Like if we if we [13:27] all were on like had something blah team [13:30] up whatever an account there then it [13:32] would be it would be seamless [13:34] integration. But it's the fact that it's [13:36] like we're not using team up for [13:38] everything for everybody. It's not like [13:40] a company that h you know what I mean [13:42] like we're not here. So yeah, the Slack [13:44] is [13:45] >> it is it is specific to Google Calendar, [13:47] but there might be [13:49] >> I don't know. There might be a way to [13:50] adapt it. So I've said what I have and [13:52] if it doesn't work, we're no further [13:54] behind than we were before. [13:55] >> Right. Right on. I love it. Do it. Yes. [13:58] Thank you very much. [14:00] >> Yeah. [14:01] Essentially, I just really don't like [14:03] technology. Technology just Yeah. makes [14:07] me [14:09] makes me want to drink wine is what it [14:11] does. But that's okay. Um, it is what it [14:13] is. If anybody else has any ideas or [14:16] experience in any of this and wants to [14:19] speak up like even after the call, [14:21] excellent. Please do. Please feel free. [14:24] No. Uh, [14:26] we're not going to be like, "No, you [14:28] cannot you cannot help us with this. [14:30] That would not that would not happen." [14:31] So, that'd be great. [14:35] Okay. Any final thoughts or anything [14:38] before we move on? [14:42] Okay. Um, Don put this on here, so I'm [14:44] going to let her take that away. [14:48] Yeah. So, this is um this is a random [14:50] thought and it's it's but it's something [14:52] I've been thinking about a lot recently. [14:54] So, historically, the way that our [14:57] software has worked. So, both Augur and [14:59] Grimmar Lab, you give it a list of [15:01] GitHub organizations or a list of [15:03] repositories that you want it to analyze [15:05] and it goes off. It collects all the [15:07] data and then you can uh visualize it [15:09] which is great when you're say a [15:13] community manager and you're focused on [15:15] a few specific repositories or [15:17] organizations or when you know which [15:20] organizations and repositories you want [15:22] to look at. So like OSO wanting to look [15:25] at all of the code that they own for [15:28] example. Um the tools are great for [15:30] that. But lately I've had a lot of [15:32] people um come to me. There was somebody [15:34] in one of the um one of the I forget it [15:38] was like a workshop I think it was one [15:39] of the one of the workshops that we had [15:40] at Chaoscon EU and he was like yeah I [15:43] want to better understand all of the [15:44] open source you know work happening in [15:46] China and I want to use chaos metrics to [15:48] do that. Um and and yeah there's metrics [15:51] that you can use but the software [15:53] doesn't really doesn't really allow for [15:55] that more more of an ecosystem analysis. [15:59] Um, and this is becoming a lot more [16:01] important as people are digging into [16:04] supply chains as a whole where you might [16:06] not know exactly which repositories in [16:09] advance you need to collect data on. Um, [16:11] and we have a package metadata working [16:13] group which I know is is kind of kind of [16:16] in this space. But I was just I was just [16:19] curious if people have if people have [16:21] thought about this because I feel like I [16:24] feel like maybe maybe the chaos project [16:27] needs to maybe we need to do more in [16:29] this area. Maybe we need to just say [16:31] that's not that's not our space. Um and [16:34] you know there are other tools that do [16:36] that like ecosystems for example. I [16:38] don't have any I don't have any [16:39] solutions. I just know that the number [16:41] of times people have come to me with [16:43] questions that were more supply chain or [16:45] ecosystem related and had to say, "Well, [16:48] yeah, but our our software really [16:49] doesn't do that." So, I'm curious what [16:52] other people think. In particular, Matt, [16:53] I know you've done some research on [16:55] supply chains. I'm curious what you [16:57] think. [16:58] >> Right. So, totally. Um, so I a couple [17:02] things that immediately come to my mind [17:05] is on the stuff that we've been doing [17:07] around supply chains and people could [17:08] tell me they don't agree with me, but I [17:10] I treat ecosystem and supply chains as [17:13] different things. And so Yep. And so I [17:16] treat ecosystems like the CNCF as an [17:20] ecosystem. Those projects may or may not [17:22] be related to one another like [17:24] technically um but they all are kind of [17:27] in that cloudnative space. Um, so that's [17:31] an ecosystem to me and then a supply [17:33] chain has kind of an inherent connection [17:36] between projects. Um, and then so I have [17:41] not been looking at the ecosystem stuff [17:44] at all. I've been looking at the supply [17:46] chain stuff and we [17:51] um have been gathering our data from two [17:54] different places. So we were using [17:57] deps.dev dev for the technical [18:00] connections between projects. So, we [18:03] were able to kind of sort out technical [18:05] dependencies at least like one one [18:08] level, you know, like not too deep [18:10] because obviously supply chains can go [18:12] on kind of forever. Um, and so there are [18:17] I'm not sure who runs deps.dev, but I [18:21] think like there are challenges in using [18:23] it. So, for example, I think they just [18:25] stopped supporting um Go as one of the [18:30] things that they take a look at from a [18:32] dependency perspective, which I think is [18:34] kind of interesting because I thought it [18:35] was a Google project, dup.dev. Anyway, [18:39] um and so we look at it at two levels. [18:42] One is just the technical dependencies [18:44] and then we've been able to use augur [18:46] data. So, we installed an augur instance [18:49] to get social connections as well. So, [18:52] we can take a look at like the people [18:54] that are present in one you know say a [18:57] focal project is what we'll call it as [19:00] well as um any of the identified [19:04] technically dependent projects one layer [19:07] upstream. So you know Don if you were [19:09] present in the focal project we can see [19:12] based on our technical construction our [19:15] dependency construction if you're [19:17] present in any of say whatever the five [19:20] projects that are upstream. So we are [19:22] able to build these sociotechnical maps [19:27] of projects [19:29] with limitations, you know, like if the [19:32] data is not available in depths.dev, [19:34] then we just run into a problem. Um, and [19:36] so it's it's working pretty well. And [19:39] then once we can build that [19:41] construction, we're able to [19:44] kind of uh look back in time, you know, [19:48] like say a six-month window or a [19:50] three-month window or whatever the [19:51] window is and see if there's any um [19:54] predictability that was evident in that [19:56] six-month window. So you know Don if you [19:59] are present in both of the downstream [20:01] and the upstream project what impact or [20:04] if there's say you know 60% of the [20:06] people are present in both projects does [20:08] that have any say effect on the [20:10] responsiveness of these projects. So we [20:13] understand that say the responsiveness [20:16] in this system is pretty solid. So yeah, [20:19] I mean we are we can answer some of [20:20] these questions or I think at least part [20:22] build the maps at least from augur data [20:25] but the dependencies the technical [20:27] dependency stuff I don't think either of [20:28] those either augur or grimmora lab [20:31] provides that. [20:34] >> Yeah and that was that was kind of some [20:37] of the stuff that I was thinking about. [20:38] So you know looking at you know for [20:40] example like a lot of companies are [20:42] looking at um you know CRA is is coming [20:46] down the the pipe for those of you know [20:48] those in Europe [20:49] >> and um and that requires kind of a [20:52] dependency level analysis that [20:56] >> um yeah and so I'm I'm not saying we [20:59] should change anything. I'm just I'm [21:00] just curious if if there's [21:03] maybe more we can do within chaos to [21:05] maybe highlight some of you know some of [21:08] maybe some of the ways that you've done [21:10] some of the analysis with with augur um [21:13] because I don't think that that's [21:15] >> it's not really like we can't it's not [21:18] native in like the visualizations in in [21:20] 8 for example [21:23] >> um so there's some some extra stuff that [21:24] has to happen and I'm kind of wondering [21:26] if that's something that [21:29] would be useful for people. I you know I [21:31] don't I don't know. But there's also [21:33] lots of other types of analysis you know [21:35] like like the you know geographical [21:38] regions or there's a lot of stuff and [21:40] people people kind of look at the chaos [21:43] I have lots of weird conversations with [21:44] people about the chaos project because [21:46] they kind of look at us for like all [21:49] metrics on on everything um related to [21:53] related to open source and and all the [21:55] data. They think we hold all of the data [21:57] about all of the open source projects [21:59] everywhere in the world. And so they're [22:01] like, "Can't you just like run a run a [22:03] thing and tell me, you know, where all [22:04] the open source projects in China are?" [22:06] Like, "No, we we don't we we just don't [22:09] have that kind of data. That's not what [22:11] we're that's not what we've been focused [22:12] on." And I'm not saying we should I'm [22:14] not saying we should have that data. I'm [22:16] just I'm just curious [22:19] Yeah. Yeah, I'm just curious if there's [22:20] anything that we can do to help point [22:22] people to maybe other things that do [22:24] that or give them [22:27] >> because there's like just the say a [22:29] sociotechnical map that you can say here [22:31] are the things that appear to be [22:33] connected [22:34] between technical dependencies and [22:36] people [22:39] like no nothing beyond that but here's a [22:41] map of the things that you might be [22:42] interested in. [22:44] >> Yeah, I think that's something that some [22:45] people would be interested in. Um, I [22:48] think in a lot of cases I think they're [22:50] not in some cases they're not really [22:53] looking at people. They just want to [22:54] know like what what projects and then I [22:56] think in other cases people really want [22:58] to know more about about the people who [22:59] are behind them. [23:01] >> Yeah. [23:02] >> I think I think it just I think it just [23:03] depends. I just you know people tend to [23:06] think we have all the all the data and [23:07] we really don't. And so I'm curious [23:08] where other people have been drawing [23:10] this line and whether there's something [23:12] we should be doing differently. [23:13] >> Okay. Um [23:16] >> does um does compass do any of this? [23:20] >> I don't think so. [23:20] >> No, Compass is built on top of Grimmar [23:22] Grimar Lab. So it has [23:23] >> Okay. So just Okay. [23:24] >> You have to you have to know which [23:26] repositories and organizations you want [23:28] to you you want data on before. [23:30] >> Okay. Okay. Because I know that they did [23:32] hold some data on some of the projects, [23:35] but Okay. [23:36] >> Yeah. And then, you know, the new SAS [23:38] instances, both the one that that Sean [23:40] runs and the one at at Red Hat, those um [23:44] are kind of, you know, kind of getting [23:46] to the point where they're helping solve [23:48] this problem, at least for certain [23:50] certain types of projects, like they [23:51] have because of Red Hat's interest in [23:53] the CNCF. I think they probably have [23:55] most or all of the CNCF projects. So, [23:58] you could probably pretty easily look at [24:00] that as an ecosystem within, you know, [24:03] at least the the Red Hat instance of [24:05] Augur. Um but but there's lots of other [24:08] other projects that they they don't [24:10] have. They don't have all the projects [24:12] uh in the world, nor should they. It [24:13] would fall apart, I think, at that [24:16] point. [24:18] >> But I'm not looking for answers. We're [24:19] not going to make a decision or anything [24:20] about this. I was just it's just [24:22] something I wanted people to think [24:23] about. [24:24] >> I mean, honestly, I think it's you could [24:25] tell people I think it's a three-step [24:27] process. So the first is to map the [24:29] technical dependencies, which can be [24:30] done from [24:31] >> dubs.dev, [24:32] >> and there are ways to to do that. The [24:35] second is is that off of that technical [24:38] map, you could map social dependencies [24:40] if that's what you care about as well. [24:42] >> And you know like the reason you might [24:44] want to care about that kind of stuff is [24:45] you want to understand your ability to [24:47] influence your ability to have affect [24:48] change like you know people matter in [24:52] that system. [24:53] >> Yep. [24:53] >> Um and so that would be the second step [24:56] if you want to do that. And then the [24:58] third would be like what are the chaos [25:00] metrics that you want to understand if [25:02] they have predictive power in that in [25:05] the system that you're taking a look at. [25:08] So the individual project level metrics [25:10] like do they change or are they affected [25:14] by these different constructions. So [25:16] that's how we've been treating it from a [25:18] research perspective. Technical first, [25:20] social second and then ask like [25:22] sustainability related metrics questions [25:25] >> third. [25:27] Yeah, that's helpful. You know, I wonder [25:29] I wonder if it might be good um for you [25:32] all to do a maybe a blog post about that [25:34] and just, you know, here's here's one [25:36] way that you can approach this this type [25:39] of analysis using some of the chaos [25:41] tools. Maybe that would maybe that would [25:43] help. [25:45] >> Yeah, I don't think the that would just [25:47] like kind of what I just said there. [25:48] like here's your [25:49] >> Yeah. super super high level like not I [25:51] know you guys are publishing papers and [25:52] so you can't go into the like the [25:54] >> Yeah. Like I can't quite share the [25:55] scripts yet probably just from a [25:58] um but they'd be sharable once the [26:01] paper's published you know. [26:04] >> Yeah. But like you said at a high level [26:06] you can these were the steps that we [26:08] took and and this is how you might be [26:11] able to do it. It would still they would [26:13] still have to do all of that but [26:15] >> Yeah. [26:16] >> Yeah. That' be interesting. [26:17] >> Okay. Yeah, [26:19] >> that's a [26:19] >> I think I think it's a great idea. First [26:21] of all, I think looking at looking [26:23] beyond the project level anymore is kind [26:26] of important and understanding [26:29] um the world where you live and the the [26:32] things that you depend on [26:34] >> is pretty critical. [26:40] >> Anyone else have have thoughts on that? [26:45] I googled augur because I don't know [26:47] what it is and it's quite confusing. I [26:50] found your GitHub repo but uh you guys [26:53] love names that are common place not uh [26:56] specific so it's it makes it difficult [26:59] to research [27:00] >> and there's another open source project [27:02] called Augur that is something [27:03] completely different. So did you find [27:05] >> Ethereum right like blockchain? [27:08] >> Yeah it's blockchain stuff. [27:09] >> Yeah. Yeah. Yeah. I thought that's why I [27:10] was like, you guys are not I'm not in [27:12] another blockchain group, am I? Um, not [27:14] that I have anything wrong with it. It's [27:16] just too many crypto bros in my life. [27:20] >> Yeah. And here's uh so the the Chaos [27:22] Software page has links to the the [27:25] sources of truth for for all of this [27:28] >> software. Okay, cool. [27:30] >> Might help. [27:31] >> Um, yeah. [27:33] >> I didn't know it existed. This is kind [27:35] of interesting. I always wondered how [27:37] you guys scraped [27:40] Yep, there's a lot of GitHub API calls. [27:43] >> Yep, I'm basically one of the more [27:46] active maintainers of Augur currently. [27:47] So, if you have questions about [27:48] anything, let me know. I know we've [27:50] already talked a lot. You still need to [27:53] add me on Signal, by the way. [27:56] >> I will. I uh joined the wrong Slack [27:58] apparently. So, now I'm in the right [27:59] Slack. So, I was looking for you in [28:01] Slack, but [28:02] >> Oh, did you join chaos.slack whatever [28:04] instead of chaos-workspace.slack [28:07] whatever? I joined the open futures [28:09] slack, not the chaos slack, [28:13] >> which is something that Emma Emma Irwin [28:15] has been building. Yes. So, it's it's [28:17] definitely in the same space. [28:20] >> So, I can I can see the confusion. [28:22] >> Yes. Very confusing. Um, but no, I'm in [28:24] the 4,000 or 3,000 person Slack now. So, [28:27] uh, yeah, I'll grab you your signal. [28:33] >> Awesome. All right. Thanks. That was an [28:34] interesting discussion. That was that [28:36] was all I had. [28:39] Thanks, Don, for bringing that up. Very [28:41] cool. [28:43] Um, looks like we don't have anything [28:45] else on the agenda. Just two reminders [28:47] about CFPs. So, if these are things you [28:50] want to submit, then here are your [28:52] deadlines and links to how to do that. [28:56] So, both excellent conferences and yeah, [29:00] you have you have a little bit of time, [29:02] not a lot, but you have a little time to [29:04] build that out. So, yeah. [29:08] Anything else? We're a little early. [29:13] Love it. [29:20] Okay. Well, I'm going to stop sharing [29:23] and I will let you all go. Um, enjoy the [29:26] rest of your day and we'll see you [29:28] around. Have a good one. [29:31] Bye everybody.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, Feb 24, 2026.md|CHAOSS Weekly Community Call, Feb 24, 2026 by YouTube]] ## Highlights - and then there was an issue of well how are we going to get everybody to go to the next one. So, just chatting with Adrian this morning. He hopped on the newcomer hangout. So, we didn't have any newcomers, so we uh spent the time going over that process and some other um interesting things about the website and our GitHub plugin and all the good things. So, um thank you Adrian for thinking this through with me. Um so now, from now on, for starting next week, from now on, this is the only link anybody will ever have to remember is ([View Highlight](https://read.readwise.io/read/01kpb4kmhbrtz36wysxyrf8n2x)) - Tags: 👻 ai highlighted - still going to change even if the meeting time for everyone else doesn't. >> Correct. Maybe we need to just write a blog post or something that's like the comprehensive guide to understanding when the crap you're supposed to be meeting. >> Well, and you know, a while ago, so we used to have the calendars tied to to Google and then we had all these different meetings and people would have to subscribe to everything or nothing. So, it was did not give us the um granularity that we wanted. So, we switched to team up and there they you know are we host on them and um it's ([View Highlight](https://read.readwise.io/read/01kpb4kmjkn2ggb94rrxz7g9ja)) - Tags: 👻 ai highlighted - if our calendar's still on team up? >> I have no idea. >> Okay. >> I'll be honest, she sent it to me because I was like, "Oh, that sounds really good." And then I just haven't had time to look at it. And so, >> so now I'm just passing the buck. You see how that works? >> Yeah, I love it. I I'm great at that. That's why I'm going to pass it right on to Adrian as soon as this call. No, I'm just kidding. Um, there is like Slackish integration, but it requires people to have a team up account. Like if we if we all were on like had something blah team ([View Highlight](https://read.readwise.io/read/01kpb4kmmea3vaw5zqtxz1bjpd)) - Tags: 👻 ai highlighted - up whatever an account there then it would be it would be seamless integration. But it's the fact that it's like we're not using team up for everything for everybody. It's not like a company that h you know what I mean like we're not here. So yeah, the Slack is >> it is it is specific to Google Calendar, but there might be >> I don't know. There might be a way to adapt it. So I've said what I have and if it doesn't work, we're no further behind than we were before. >> Right. Right on. I love it. Do it. Yes. Thank you very much. ([View Highlight](https://read.readwise.io/read/01kpb4kmnxjb0ztj121pga92z0)) - Tags: 👻 ai highlighted - that. But lately I've had a lot of people um come to me. There was somebody in one of the um one of the I forget it was like a workshop I think it was one of the one of the workshops that we had at Chaoscon EU and he was like yeah I want to better understand all of the open source you know work happening in China and I want to use chaos metrics to do that. Um and and yeah there's metrics that you can use but the software doesn't really doesn't really allow for that more more of an ecosystem analysis. Um, and this is becoming a lot more ([View Highlight](https://read.readwise.io/read/01kpb4kmt63yym627cft5qp32x)) - Tags: 👻 ai highlighted - important as people are digging into supply chains as a whole where you might not know exactly which repositories in advance you need to collect data on. Um, and we have a package metadata working group which I know is is kind of kind of in this space. But I was just I was just curious if people have if people have thought about this because I feel like I feel like maybe maybe the chaos project needs to maybe we need to do more in this area. Maybe we need to just say ([View Highlight](https://read.readwise.io/read/01kpb4kmwg2rrt15h2b3mcez90)) - Tags: 👻 ai highlighted