CHAOSS Weekly Community Call, March 17 2026

CHAOSS Weekly Community Call, March 17 2026 ![rw-book-cover](https://img.youtube.com/vi/ywXQxV8gmaQ/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, March 17 2026](https://www.youtube.com/watch?v=ywXQxV8gmaQ) > [!note]+ Document Notes > tags: #open-source #ai-governance #elections #community-management > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=ywXQxV8gmaQ > date created: 2026-03-17 14:00 > > # 🏷️ Title: CHAOSS Weekly Community Call, March 17 2026 >  ## 🧰 Action Inbox - [H1] Fix community contributions issue template automation — GitHub integration broken #community-management - [H2] Upload backlog of meeting recordings to YouTube — Elizabeth behind on uploads #video-management - [H3] Investigate Zoom to YouTube live streaming integration — automate recording process #automation ## 🧭 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 Community GitHub](https://github.com/chaoss/community) - [Board Election Mechanics](https://github.com/chaoss/governance/elections) - [AI Detection GitHub Action](https://github.com/chaoss/ai-detection) ## 📝 Summary - The CHAOSS community discussed upcoming board elections, AI detection tools, and community management funding challenges - Board elections will feature 6 seats with ranked voting through Electa system - AI detection GitHub action seeks contributors to identify AI-generated code contributions - Community management position funding from Sloan Foundation uncertain, awaiting decision - Technical discussions around automating meeting recording uploads to YouTube ## 📖 Main Content The CHAOSS (Community Health Analytics for Open Source Software) project held its weekly community call on St. Patrick's Day 2026. The meeting covered several key governance and technical initiatives affecting the open source metrics community. The most significant discussion centered on upcoming board elections, the first in CHAOSS history. Six board seats will be available through a ranked voting system managed by Electa. Community members must add their contributions to the community repository to become eligible voters and candidates. Uncertainty surrounds the community management position, as the Sloan Foundation's 9-year funding commitment is ending. While there are promising signs for continued funding, no confirmation has been received. Elizabeth has documented all community management processes to ensure continuity regardless of the funding outcome. Technical initiatives include an AI detection GitHub action seeking contributors to identify AI-generated code contributions across repositories. The project aims to score and categorize AI usage disclosure patterns to provide better metrics for open source communities. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/ywXQxV8gmaQ?t=0) — [H1] Meeting opening and four-leaf clover discussion - Key idea: Elizabeth opens meeting on St. Patrick's Day, discusses pattern recognition in finding four-leaf clovers - Evidence: "I find them all the time and I thought it was some kind of special superpower until it's more of like me being on the spectrum and it's like the pattern recognition that makes me see them" #### ⏱️ [02:30](https://youtu.be/ywXQxV8gmaQ?t=150) — [H2] Rotating meeting facilitators - Key idea: Community moving toward rotating facilitation of weekly calls - Evidence: "We are starting to kind of rotate the facilitators for this meeting if possible" #### ⏱️ [03:15](https://youtu.be/ywXQxV8gmaQ?t=195) — [H3] Code for GovTech UN working group collaboration - Key idea: CHAOSS working with UN SG working group through Code for GovTech - Evidence: "We are working with code for govtech with the UN SG working group" #### ⏱️ [04:00](https://youtu.be/ywXQxV8gmaQ?t=240) — [H1] AI alignment working group survey - Key idea: University of Missouri AI alignment group seeking community input on AI and open source - Evidence: "They have a survey out that they would really love our community to take about AI and how it pertains to their work in opensource" #### ⏱️ [06:45](https://youtu.be/ywXQxV8gmaQ?t=405) — [H2] AI detection GitHub action project - Key idea: Adrian and Andrew developing GitHub action to detect and score AI-generated code contributions - Evidence: "We're looking at sort of explicit forms of people like disclosing they're using AI whether that's like a commit author that is like a known like oh it was committed by claude" #### ⏱️ [12:30](https://youtu.be/ywXQxV8gmaQ?t=750) — [H1] Board elections announcement - Key idea: First CHAOSS board elections coming with ranked voting system - Evidence: "The chaos board elections are coming... this is the first time for us" #### ⏱️ [15:00](https://youtu.be/ywXQxV8gmaQ?t=900) — [H2] Community contributions eligibility process - Key idea: Contributors must add themselves to community file for election eligibility - Evidence: "You can do a new issue and do a chaos contribution. You fill this out and it will add your name to that list" #### ⏱️ [18:45](https://youtu.be/ywXQxV8gmaQ?t=1125) — [H3] Six board seats with ranked voting - Key idea: Six board positions available using ranked choice voting through Electa - Evidence: "I think there are six if I recall from our discussions I think there will be six seats that are open" #### ⏱️ [20:30](https://youtu.be/ywXQxV8gmaQ?t=1230) — [H1] Community management funding uncertainty - Key idea: Sloan Foundation funding for community management position ending, awaiting renewal decision - Evidence: "The Sloan Foundation has been funding this project for 9 years... the funding ended. We are really trying to get at least one more year" #### ⏱️ [24:15](https://youtu.be/ywXQxV8gmaQ?t=1455) — [H2] Documentation and contingency planning - Key idea: All community management processes documented for continuity - Evidence: "Everything I do has been completely documented and how to do everything that I do has all been written down" #### ⏱️ [26:00](https://youtu.be/ywXQxV8gmaQ?t=1560) — [H3] YouTube upload backlog problem - Key idea: Elizabeth behind on uploading meeting recordings to YouTube - Evidence: "I am so far behind on that. I will commit to getting caught up this week" #### ⏱️ [30:45](https://youtu.be/ywXQxV8gmaQ?t=1845) — [H2] Automation discussion for recording uploads - Key idea: Community discussing automated solutions for YouTube uploads - Evidence: "Maybe it is time to automate... we wanted to leave space for a manual layer of checking in case there are like something inappropriate happens" #### ⏱️ [38:20](https://youtu.be/ywXQxV8gmaQ?t=2300) — [H3] FOSDEM speaker self-clipping system - Key idea: Adrian describes FOSDEM's system allowing speakers to clip their own talk timestamps - Evidence: "You as the speaker get sent a link where you can like scrub through and pick like when does your talk start and end" #### ⏱️ [42:10](https://youtu.be/ywXQxV8gmaQ?t=2530) — [H3] Platform alternatives discussion - Key idea: Brief discussion of Discord as alternative to Zoom for better automation - Evidence: "Discord's just it the reason it gets poo pooed is because China owns it... Discord covers all those bases" ## 📚 References - [CHAOSS Board Election FAQ](https://github.com/chaoss/governance/elections) - [University of Missouri AI Survey](https://survey.missouri.edu/ai-opensource) - [AI Detection GitHub Action](https://github.com/chaoss/ai-detection) - [CHAOSS Community Repository](https://github.com/chaoss/community) ## 🗣️ Paraphrase - CHAOSS is conducting its first board elections with six seats available through ranked choice voting - An AI detection tool is being developed to identify and score AI-generated code contributions in open source projects - The community management position's future depends on uncertain funding renewal from the Sloan Foundation after 9 years of support ## 📰 Newsletter The CHAOSS project reaches a governance milestone with its first-ever board elections! Six seats are available through ranked choice voting via the Electa system. Community members can participate by adding their contributions to the community repository. Meanwhile, innovation continues with an AI detection GitHub action seeking contributors. This Go-based tool will help identify and score AI-generated code contributions across repositories, providing valuable metrics for open source communities. The project faces funding uncertainty as the Sloan Foundation's 9-year commitment ends, but comprehensive documentation ensures continuity regardless of outcome. Resources: [CHAOSS GitHub](https://github.com/chaoss), [Election Info](https://github.com/chaoss/governance), [Community Repo](https://github.com/chaoss/community) ## ✅ Action Items #### Community - Contributors: Add contributions to community repository for election eligibility - Maintainers: Fix automated issue template for contribution tracking - Sponsors: Await Sloan Foundation funding decision for community management #### OSPO - Software Inventory: Evaluate AI detection GitHub action for contribution scoring - Community Engagement: Participate in University of Missouri AI alignment survey - Strategic Alignment: Document governance processes for board election implementation #### WordPress - Community: Consider ranked choice voting systems for WordPress governance decisions - Meta: Explore automated video processing solutions for WordCamp recordings - Documentation: Apply CHAOSS documentation practices to WordPress community management ## 🧪 Hypotheses - Ranked choice voting will increase candidate diversity and community engagement in CHAOSS board elections - AI detection tools will become essential for measuring code authenticity in open source projects - Automated recording processing can maintain quality control while reducing manual workload - Pattern recognition skills correlate with ability to identify systematic issues in open source communities ### 📊 Methodology - Survey design: University of Missouri IRB-approved survey on AI usage in open source development - Election system: Electa platform with ranked choice voting algorithms for six board seats - AI detection: Go-based GitHub action scanning commit metadata and author disclosure patterns ### ❓ Questions - How will ranked choice voting affect representation compared to traditional voting methods? - What percentage of AI-generated code contributions are properly disclosed in open source projects? - Can automated systems effectively balance transparency with privacy protection needs? ### 🔮 Future Research - Comparative analysis of governance systems across open source foundations - Longitudinal study of AI disclosure patterns in major open source repositories - Community management sustainability models beyond traditional foundation funding ### 💡 Implications - Practice: First board elections establish precedent for CHAOSS governance evolution - Policy: AI detection tools may influence disclosure requirements for automated contributions - Security: Automated recording systems require balance between transparency and content moderation - Funding: Foundation funding models need diversification for long-term sustainability ### 🧠 Learning Styles Assessment Reading level estimate: Flesch-Kincaid Grade Level 12 #### 👀 Visual learners - Present: Screen sharing during meeting, GitHub repository examples - Improve: Election process flowcharts, AI detection scoring visualizations #### 🔊 Aural learners - Present: Live discussion format, verbal explanations of technical concepts - Improve: Dedicated audio summaries of key decisions and action items #### 🗣️ Verbal learners - Present: Clear definitions of governance terms, analogies for technical processes - Improve: Glossary of CHAOSS-specific terminology, comparison tables #### 🧩 Kinesthetic learners - Present: GitHub issue creation process, hands-on contribution tracking - Improve: Interactive election simulation, AI detection tool sandbox #### 🧠 Logical learners - Present: Systematic approach to election mechanics, documented processes - Improve: Decision trees for governance scenarios, metrics dashboards #### 🧑‍🤝‍🧑 Social learners - Present: Community call format, collaborative problem-solving discussions - Improve: Working group coordination guides, mentorship programs #### 🧘‍♀️ Solitary learners - Present: Documentation for self-guided contribution process - Improve: Self-assessment tools for governance participation readiness #### 🌿 Naturalistic learners - Present: Pattern recognition discussion (four-leaf clovers analogy) - Improve: Ecosystem thinking about open source community sustainability ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in documentation, descriptive link text - Improve: ARIA labels for complex governance workflows, alt text for diagrams #### Keyboard navigation - Present: GitHub interface supports keyboard navigation - Improve: Ensure election platform meets keyboard accessibility standards #### Contrast and readability - Present: Standard GitHub contrast meets WCAG guidelines - Improve: Verify election platform contrast ratios, test with high contrast modes #### Text resizing and reflow - Present: GitHub responsive design supports text scaling - Improve: Test election interface at 200% zoom, ensure form usability #### Media and captions - Present: Meeting recordings available for review - Improve: Auto-generated captions for meeting uploads, transcript availability #### Forms and interactions - Present: Clear form labels in contribution tracking - Improve: Error validation for election registration, accessible date pickers ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global open source community participation, international time zones considered - Improve: Multi-language election materials, regional governance examples #### Inclusive language - Present: Professional technical terminology, defined acronyms - Improve: Plain language summaries, avoid developer-specific jargon #### Neurodiversity support - Present: Structured meeting format, documented processes - Improve: Consistent agenda templates, clear transition signals #### Representation - Present: Diverse technical backgrounds in AI detection discussion - Improve: Highlight varied contribution types beyond code, inclusive candidate profiles #### Psychological safety - Present: Respectful discussion tone, acknowledgment of mistakes - Improve: Explicit community guidelines, confidential feedback channels ### ✅ Logical Validity #### Strong reasoning - Deductive strength: If contributors must be in community file for eligibility, then contribution tracking ensures legitimate voting - Inductive strength: Past pattern of respectful community behavior suggests automated recording is low-risk - Causal reasoning: Sloan Foundation funding end directly causes uncertainty about community management continuity - Analogical strength: FOSDEM speaker self-clipping system provides model for automated recording workflows #### Fallacies - Appeal to tradition: "This is how we've always done manual review" - location: recording discussion, fix: evaluate current needs vs historical practices - False dilemma: Manual vs fully automated recording - location: automation discussion, fix: consider hybrid approaches with delayed automation #### Tone of voice - Overall tone: Collaborative and problem-solving oriented, with acknowledgment of challenges and uncertainty ### 🛡️ DARVO Analysis - Deny: No instances of denial or minimization of problems - Attack: No attacks on community members or critics - Reverse victim/offender: No victim/offender reversal present - Emotional cues and rhetoric: Supportive and constructive throughout, with genuine concern for community needs ## 🎯 Conclusion The CHAOSS community demonstrates mature governance practices as it navigates significant transitions including first board elections, funding uncertainty, and technical innovation. The ranked choice voting system represents thoughtful democratic evolution, while AI detection tools address emerging needs in open source measurement. Key next steps include resolving community management funding, fixing technical issues with contribution tracking, and implementing automated solutions for routine tasks like recording uploads. The community's collaborative approach to problem-solving and commitment to documentation ensures resilience during leadership transitions. This call exemplifies effective open source governance through transparent decision-making, inclusive participation, and practical solutions to operational challenges. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] First board elections establish governance precedent > [!quote] [CHAOSS Weekly Call](https://youtu.be/ywXQxV8gmaQ) by [[CHAOSS Community]] via [[YouTube]]. Published 2026 --- ## Full Transcript [00:02] Okay. Hello everybody. It is uh Tuesday, [00:06] March 17th, St. Patrick's Day. I am [00:08] wearing green, my green shirt. [00:11] >> Woohoo. [00:12] >> I did uh have a green So here in Ohio, [00:16] they do a thing where they turn all the [00:18] beer green. I'm sure they do it in other [00:20] places, too. But I did have a green beer [00:22] over the weekend, so that was very [00:23] exciting. Yes, it tastes just like [00:27] regular beer, but it is a weird thing. [00:29] It's a weird thing to drink a very green [00:32] drink. I don't know. Um, let me share my [00:37] screen [00:39] here. [00:43] Here we go. Um, if you have ever found a [00:46] fourleaf clover, [00:49] tell us. [00:51] I um find them all the time and I [00:57] thought it was some kind of special, you [00:59] know, superpower [01:01] until [01:03] until uh it's more of like me being on [01:07] the spectrum and it's like the pattern [01:09] recognition that makes me see them. So [01:12] yeah, maybe that is a superpower. I [01:14] don't know. But yeah, I do find them all [01:16] the time. It's kind of weird. [01:21] I used to pick them when I was a kid. I [01:23] would pick them and put them in a book, [01:24] you know, and flatten them, keep them, [01:26] but now I just take a picture of them [01:27] because I want to leave them for [01:28] somebody else to find. So, yes. [01:32] Um, so if you've not been here for a [01:36] while, I think everybody has been, but [01:38] uh, everybody that's here now, I mean, [01:40] um, we are starting to kind of rotate [01:42] the facilitators for this meeting, um, [01:44] if if possible. So, um, if there is [01:47] somebody on the call that wants to [01:48] facilitate next week, that would be [01:51] awesome. And if not, I'm happy to do it. [01:53] But just kind of want to give other [01:55] folks the opportunity to do it. So, if [01:57] anybody wants to speak now, [02:07] don't everybody jump at the chance to do [02:10] it at once. Okay. I I can I'll put my [02:13] name down and then if somebody changes [02:15] their mind [02:17] uh totally fine. Just let me know. I'm [02:20] happy to do it. I don't mind at all. [02:25] Okay. This is from last week, actually [02:27] from two weeks ago. We didn't have [02:29] anybody here last week that could speak [02:30] to this. Um, and I'm not sure who ended [02:33] up putting it on the agenda a few weeks [02:35] ago, but um, I guess we are working with [02:39] code for govtech with the UN SG working [02:42] group. So um, if anybody has more [02:45] information than that to share, that [02:48] would be great. If not, that's okay. [02:56] Okay. All right. Cool. We'll go on then. [03:01] Uh this is a message from the AI [03:03] alignment working group. They have um [03:06] have a survey out that they would really [03:08] love our community to take about AR AI [03:13] and how it is um how it pertains to [03:16] their work in opensource. So you can get [03:19] to the survey here. um they would really [03:22] appreciate your input on this and it is [03:25] um [03:27] because it's the University of Missouri [03:29] so you know your I don't think there's [03:31] any information that they take like your [03:34] name or anything like that no personal [03:35] information but if I haven't taken the [03:37] the survey yet if there is anything in [03:39] there um it it will be protected um by [03:44] the University of Missouri so [03:48] there is a very strict for those who [03:50] don't know any kind of survey that goes [03:51] university there's a very strict uh [03:54] process for um collecting data on PE if [03:57] people are involved if human beings are [03:59] involved there's a very strict process [04:01] you have to be um you have to go through [04:03] a um qualification you have to have a be [04:06] certified to run one of those surveys um [04:09] and also it's like a very strict process [04:11] about how the data is stored how it's [04:14] collected all of those things so um you [04:17] can trust that your your information [04:18] will be safe. [04:23] Um, Adrian is adding uh he's looking for [04:26] contributors to an AI detection GitHub [04:29] action. Adrian, do you want to talk more [04:31] about that? Yeah. So, this is basically [04:34] a project that um I think it's Andrew [04:38] from I think Andrew from the um package [04:41] metadata working group and I I think we [04:43] both were kind of interested in the [04:45] similar idea um as far as having a [04:48] GitHub action that can take [04:50] basically it can like look for I think [04:53] for the first plan the first sort of [04:55] initial versions we're looking at sort [04:57] of explicit forms of people like [05:00] disclosing they're using AI whether [05:01] that's like a commit author that is like [05:04] a known like oh it was committed by [05:06] claude code or they put like a like a [05:09] co-authored by like Gemini or something [05:12] like taking all those various different [05:14] forms of how you can disclose AI and [05:18] making that finding some way to kind of [05:22] score them relative to like how like [05:24] maybe categorize it and make that [05:27] available to in sort of a more unified [05:30] form for tools like Aug. blogger or [05:32] ecosystems or any other sort of metrics [05:34] tools to kind of look and you and ingest [05:37] into their metric measurements so that [05:39] people can kind of see a better picture [05:41] of sort of metrics in their community [05:44] around like how many of how many of the [05:46] PRs that we're getting include AI or to [05:49] what extent or whatever. Um, so it's [05:52] sort of just like an exploratory project [05:54] to try and build a little tool like a a [05:58] code base that can sort of collect this [06:00] information and also like a get various [06:03] wrappers around it for like GitHub [06:04] actions, GitLab actions, things like [06:07] that. Um, it's very sort of work in [06:10] progress. I think there's sort of a [06:11] minimum viable version in the codebase [06:14] right now, but I think both Andrew and I [06:16] our primary focus is elsewhere. So [06:19] having like if if people are interested [06:20] in helping with this um there's a [06:23] there's a Slack channel. Um I think we [06:25] sort of mildly informally have meetings. [06:29] Um I I've sort of just said like hey [06:30] let's meet every two weeks after the the [06:32] Augur 8 not meeting if there's enough [06:35] stuff to talk about. Uh I think we've [06:37] had like one meeting so far a few weeks [06:39] ago. But it it would be nice to kind of [06:41] see this [06:43] take off more and and do more like make [06:46] progress and and sort of potentially [06:48] even be a space for other other similar [06:50] projects to kind of unify and under kind [06:52] of a Linux Foundation chaos umbrella to [06:55] kind of help detect a lot of this [06:56] because I know this is like very popular [06:58] like this kind of thing is I think going [07:00] to be pretty popular now with with AI [07:02] contributing all over GitHub [07:06] >> and um it looks like it's in Go. So [07:09] folks would need to know how to write [07:11] Go. Is that correct? [07:13] >> Yeah, I think for the most part, yeah, [07:15] that's that's right. Um there's probably [07:18] some amount of even just like reaching [07:21] out to other other pro like helping kind [07:23] of build build the co build kind of get [07:26] people in the Slack like other community [07:28] building type things. But yeah, I think [07:30] the main the main development is [07:32] probably going to be like looking at the [07:35] code or finding even I mean I guess [07:37] there's also some like thinking about [07:38] like how do we finding new ways to to [07:41] measure like to to detect AI and like [07:46] how do we score it? How do we rank it? [07:47] Like I think there's some thinking [07:48] around it, but yeah, the bulk of it is [07:49] going to be go. [07:59] >> You could always just say most of those [08:00] things have open issues as well as far [08:02] as like, okay, how do we do a scoring [08:03] system? How do we present this data? How [08:05] do we whatever. So I think even just [08:07] saying like [08:08] >> having feedback on the open issues is [08:10] probably a good good summary for that, [08:13] too. [08:13] >> Yeah. Okay. Excellent. [08:20] Great. [08:23] Thanks, Adrian. [08:25] Anybody have questions for him on this? [08:45] There we go. Oh, there's the Slack [08:46] channel. Thank you. That was going to be [08:48] my next uh thing to go find what that [08:50] is, but you already know. So, there it [08:52] is. [08:56] Excellent. Okay. [09:00] Um the next item, if there's is there [09:02] anybody else who had any questions or [09:04] anything before I move on? [09:12] Okay. [09:13] Um, next on our list is just a reminder [09:15] that the chaos board elections are [09:17] coming. If you want uh more information, [09:20] I know Emma and Emma Irwin, myself, and [09:23] then someone from the um K Native [09:26] community who works for Red Hat is also [09:28] helping us um since they have run these [09:30] elections in their community before. [09:32] He's kind of walking us through this [09:33] process because this is the first time [09:34] for us. Um, so we are building out this [09:37] FAQ, but this mechanics doc also has a [09:40] lot of information in it about how, who, [09:44] when. Um, it's not open yet, but it is [09:47] coming. So, we just wanted to keep [09:48] giving people the heads up that this is [09:50] coming. Um, what you can do in the [09:52] meantime is make sure that you have [09:54] added your contributions to this file by [09:56] opening that issue uh in the community [09:59] repo. [10:01] This is the file right here. Um, if you [10:04] go to issues, you can uh do a new issue [10:09] and do a chaos contribution. You fill [10:12] this out and it will add your name to [10:14] that list and then you will have um you [10:18] will have the ability to then vote on uh [10:20] in the election and also be a candidate [10:23] if you like. [10:25] So, just want to make sure people are [10:27] doing that because that's new for us and [10:30] yeah, we don't want to we don't want to [10:31] leave anybody out. So, um, the the way [10:34] the system works is it will take your [10:35] GitHub ID and put it into the system. [10:38] So, it will verify that and when you log [10:40] in to the Electto system, that's how [10:42] you'll do it. So, if you don't have a [10:44] GitHub ID, you'll need to get one. And [10:47] if that's a barrier for you, we will [10:50] also have an exceptions form you can [10:52] fill out, um, which is also fine. Um, [10:56] but, uh, it it would be quicker, easier [10:59] if you're able to get that GitHub ID. [11:01] So, um, if that's a thing you can do, [11:03] great. If not, totally fine. We will [11:05] have a form for you to fill out. [11:10] >> How many does it does it take a while [11:12] before the name reflects? Cuz um while [11:16] um Adrian was speaking, I I did fill out [11:19] the issue, but [11:22] the contribution does not yet reflect on [11:24] the community contributions file. [11:28] >> Yeah, I will have to u merge that in. Um [11:32] >> um so right. [11:34] >> Um [11:35] >> oh I think I might have gone to close [11:37] the issue cuz I didn't see it and I was [11:39] like oh maybe it doesn't work yet. [11:41] >> Yeah. No no no that's been going on. And [11:43] actually I think you're probably fine [11:45] because I think your name already exists [11:47] in that doc. Um [11:50] >> Oh yeah. [11:51] >> Yeah. Once you're in there you're good. [11:54] Um it it does we do ask for um [11:58] eligibility. So, in the past year, you [12:00] would have had to have been active. Um, [12:02] so we will look at that. But also, um, [12:05] you're in here. I I'm fairly certain [12:08] you're in here from recently. So, yeah, [12:10] you're in here. You're good. You're [12:11] good. [12:14] But if you want to fill that in um issue [12:16] out, feel free to do that. [12:21] >> Yeah. [12:23] At least I don't think it does it [12:25] automat. I think I do have to still do a [12:29] a a pull request. [12:32] Merge [12:33] >> merge. [12:34] >> Yeah, let me just try. [12:35] >> I'll just I'll just reopen the issue [12:38] then. Um we maybe we get a time. [12:43] >> Let's just go through it once and see [12:45] what happens. [12:51] >> Okay. area project community management [12:55] today is 22627. [13:01] Uh this was community management [13:06] create. Let's see what happens. [13:12] Yeah. [13:23] Let me see if this [13:27] went to [13:35] Okay. Uh, let me just check with [13:40] Sean on that because I thought it was [13:43] supposed to [13:46] do that automatically, at least create [13:48] the pull request. [13:52] I think I you wanted to add something to [13:54] that. [13:56] >> Yeah, I see. [13:59] Uh [14:00] yeah. H Okay, let me just do an action [14:04] item here cuz something got broken. It [14:08] was working and now it seems like it's [14:09] not. Um which is weird. [14:14] >> Thank you. [14:16] You can still you can still do it [14:18] manually if you like. Um you can still [14:21] >> Yeah. [14:22] >> Um [14:22] >> Anita, you have your hand up. I see. [14:27] >> Um yes. Um this is actually another [14:31] question I want to ask. But I was [14:33] wondering is it an issue that we create [14:36] here or just go straight to the pull [14:38] request? Create a pull request straight [14:41] instead of issue. [14:42] >> You Yes, you can totally just do a pull [14:44] request. Um Sean made this issue um [14:48] template process to make it easier for [14:51] folks who weren't sure how to PR. Um but [14:54] yeah, you can absolutely just do a PR. [14:57] >> Oh, okay. [14:57] >> Straight onto that doc. [14:59] >> In fact, that's I think how we started [15:01] it. Um and then it was like kind of a [15:03] barrier for some folks. So Sean made [15:05] that issue. But yeah, you can absolutely [15:06] do that. [15:09] >> Yeah, we're going to fix this because I [15:11] it's going to be a lot more easier for [15:13] for people. Mhm. Yeah. [15:20] Okay. So, the question I have, [15:26] can I go ahead? [15:28] >> Yeah. Yeah, feel free. [15:29] >> Okay. Thank you. The question I have is [15:32] that um so if you make enough code [15:34] contributions, do you still need to open [15:38] a PR here? [15:40] >> No. [15:42] >> No. Um, it will be it'll be captured in [15:44] those other places. [15:48] >> Okay. [15:49] >> So, it's all good. Yeah. Yeah. That doc [15:52] is mostly for like Yeah. community [15:54] stuff, something that doesn't show up in [15:56] a PR. [15:58] >> Yeah. That that [16:02] >> sounds good. [16:06] >> Yeah. I'm not sure what's going on with [16:08] that. So, [16:10] but we will figure that out. [16:16] Anybody have any other questions about [16:18] that? [16:26] Okay. [16:29] Okay. [16:31] Um we are um going to be setting up also [16:34] a separate Slack channel um for [16:38] questions specific for the elections. So [16:40] you can pop in there and ask whatever [16:42] you need. Um you can also ask them just [16:45] in general uh general channel as well if [16:47] you want but um we will have a dedicated [16:50] Slack channel for any questions. [16:57] Okay. And then the Oh, go ahead. Did I [16:59] somebody else [17:01] >> can I ask um how many seats are open? Is [17:03] it is it public yet? [17:06] >> I think there are six if I recall from [17:09] our discussions I think there will be [17:11] six seats that are open. [17:14] >> Okay. Okay. [17:18] And the um I can also share that the [17:20] voting process will be ranked voting and [17:23] we will be linking if we haven't done it [17:25] already we'll be linking to like the the [17:27] math and the algorithm that the system [17:30] uses to determine who the winners are. [17:33] Um but when you vote you'll see um the [17:35] list of names and then you can rank like [17:38] oh I want this person and then next I [17:41] want this person and then next I want [17:42] that person. So um so it's not just like [17:45] yes or no. you can kind of rank who you [17:48] think would be the best candidates. [17:51] >> I think that's interesting. Looking [17:54] forward to to the election process. [17:56] >> Yeah. Yeah. It will be coming very soon. [17:59] Um in the next few weeks we will be [18:02] giving more information for sure. [18:05] >> Okay. So how is the community management [18:08] coming [18:10] uh for chaos? Now [18:12] >> it's a great question. Um, so I got a [18:15] message from Sean yesterday. So for [18:18] those who don't know, um, the the [18:21] funding for the community management [18:22] position ends, um, this time of year. So [18:27] um, they've the Sloan Foundation has [18:30] been funding this project for 9 years, [18:32] which is really something like that just [18:34] doesn't happen too often um to have [18:37] three round because they come in [18:39] three-year chunks. So, um, they've been, [18:42] uh, specifically funding this position [18:44] for 6 years. Um, and so, um, the funding [18:49] ended. Uh, we are really trying to get [18:53] at least one more year of something, [18:56] some support, some financial support for [18:58] that function. Um, Sean has been working [19:01] on that in particular. So, um, I did get [19:04] a message that they still have not [19:07] confirmed with him yet. [19:10] But the uh it's it's looking promising. [19:13] They we just don't have that [19:14] confirmation yet from them. So it's it's [19:17] been a little bit in limbo quite [19:18] frankly. Um I wish I had more [19:20] information to share, but I I don't. Um [19:23] and I don't think Sean does either. [19:25] We're just kind of waiting on them to to [19:27] let us know what what they decide. Um, I [19:30] can tell you that everything I do has [19:33] been completely documented and how to do [19:36] everything that I do has all been [19:38] written down. So, whatever that looks [19:41] like, if it's going to be if it's going [19:43] to be funded, great. Then, you know, [19:46] maybe we'll have to figure out the [19:48] strategic plan for the future. Um, if it [19:51] if it isn't, then we'll also have to [19:53] figure out a strategic plan for the [19:55] future. Um there are some things this [19:57] facil facilitating this meeting for [19:59] instance that any anybody in the [20:01] community can do. Um there are certain [20:03] things that um like a trusted leader in [20:07] the community can do. Um like a working [20:09] group leader or something like that. Um [20:11] and then there are things that only an [20:14] official kind of chaos representative or [20:16] board member could do. things like [20:18] writing the visa letters for folks like [20:20] somebody who can officially represent [20:22] the project will have to do that piece. [20:25] So, um it's all ready to go as soon as [20:29] we get that confirmation from from them. [20:33] So, I know that's not a great answer, [20:35] but yeah. Yeah. [20:40] Okay. I'm looking [20:41] >> Yeah, I'm looking at these questions. [20:43] Oh, yeah. You're welcome. You're [20:44] welcome. Community open collective [20:45] account for crowdfunding. I mean, that's [20:48] that's a a possibility. Um, taking over [20:51] uploading meetings, recording to [20:52] YouTube. That is my that is on me. I'm [20:54] so so so so sorry you all. Oh my gosh, [20:57] that is on me. Um, I'm so far behind on [21:00] that. I will I will commit to getting [21:03] caught up this week. I will commit to [21:05] that. Um, I am just so sorry for that [21:09] that I am so far behind on on uploading [21:11] those meetings. I know it's been um I [21:14] know that's a problem and it's [21:15] completely on me, 100% on me. Um yeah, [21:20] so here's the thing about automating it [21:22] and we have looked at this in the past. [21:24] Um because in theory you could, right? [21:27] Like it's we could either record [21:28] straight to YouTube, just live stream it [21:30] and record it straight to YouTube or we [21:32] could share the links straight to Zoom. [21:35] Those are also options that we have [21:37] thought about. The reason that we don't [21:39] have it automated now and this could [21:42] change like if if somebody else you know [21:43] I mean this was from before so it [21:45] doesn't mean it has to be like this [21:47] forever. The reason that we decided not [21:49] to make that automated process is that [21:51] we wanted to leave space for [21:54] um a a manual [21:57] layer of checking in case there are like [22:02] something inappropriate happens in a [22:04] meeting. there's somebody says something [22:06] like maybe about their company that [22:07] they're like, "Oh, I shouldn't have said [22:09] that. Can we take that out before we [22:11] post it to the world?" You know, things [22:13] like that. Like we that was a a mindful [22:15] choice that we made back years ago just [22:18] to kind of have that layer of like human [22:21] intervention just just in case. Um but [22:25] that being said, you know, um maybe it [22:27] is time to automate. I mean, that's [22:28] definitely a question worth worth [22:31] having. the warnings are already there [22:33] before you enter the meeting. Yeah. I [22:35] mean, yes. Um but you know, [22:40] um we've had things happen that we were [22:44] like, "Oh, we should probably take that [22:45] out." Um oh, I wish I could I wish I [22:48] could tell you, but I feel like that [22:50] would be rude if I did tell you all, but [22:52] maybe I'll tell you all as soon as we [22:54] stop this recording because it was [22:55] actually pretty funny. Um but also kind [22:58] of embarrassing. So, yeah. Anyway, there [23:00] we go. Sorry, sorry that is not a not a [23:04] good answer for that. But um FOSTM has a [23:08] cool system for allowing speakers to [23:09] clip their own timestamps. [23:12] And what do you mean by that, Adrian? [23:14] Tell me more. [23:16] >> So like with Fosdom, like it's a [23:18] recorded like the like all the rooms and [23:20] tracks are recorded, but it's just live [23:22] streamed. And I think like within a day [23:24] or two of your talk ending, you I guess [23:27] you as the speaker get sent a link where [23:30] you can like scrub through and pick like [23:32] when does your talk start and end like [23:34] if you just in case you accidentally [23:36] started a minute late or a minute early [23:37] from the actual scheduled time. you can [23:40] kind of define where because it's like [23:42] the same process that you would have [23:43] that we would like I've had to do it for [23:45] for flock and we might want to do it for [23:48] chaos con where like you take the live [23:50] stream and you clip out the bits that [23:51] are the individual talks and upload them [23:53] individually. Um they just have a system [23:56] that lets the speaker like each [23:57] individual speaker do their own thing. [23:59] So it sort of crowdsources [24:01] that and so the the quicker the speakers [24:03] are at doing that that the e the more [24:05] faster the there's like a link available [24:08] on this talk page that people can just [24:10] go and rewatch the recording of the [24:12] talk. I don't know if we can replicate [24:14] that system, but I think maybe that idea [24:17] of h of spreading it around to the [24:19] different [24:21] like committee uh to the different uh [24:23] working group heads of like okay [24:25] whoever's sort of the leader of the [24:27] augur working group is the one that [24:30] >> would do that [24:30] >> presumably is in all the meeting is in [24:32] the meetings and should be able to tell [24:34] >> right [24:34] >> by just having been there okay this is [24:36] this was fine to go up like I don't [24:38] think anything sensitive was discussed [24:40] >> right well and to be fair if If we so if [24:44] you tell people, hey, we're live [24:46] streaming this, I feel like they're a [24:49] little more careful about what they say, [24:52] then it's kind of like a self-fulfilling [24:55] thing. Like we've kind of made it clear [24:57] that if if you do say something, it's [25:00] totally fine. We can take it out. But [25:02] also that means that people ha know that [25:05] you know and so that that that like kind [25:07] of um uh what do you call it you know [25:10] that that kind of mindset is there so [25:13] we've kind of done it ourselves um but [25:15] if we did say for instance we're going [25:17] to start live streaming these to YouTube [25:19] and that it's just there when we're done [25:21] um then you know that's that's maybe a [25:24] new expectation that we have for the [25:25] community and to be clear this has to to [25:28] Idico's point who who says if this [25:31] doesn't happen often. YouTube also lets [25:32] you cut pieces out of already uploaded [25:34] videos, so things will be out there for [25:36] for a time, but could be taken out if [25:38] someone asks. And and to to that point, [25:41] I think this has maybe maybe happened [25:44] three times. Like it it just doesn't [25:46] happen. you know, our community is very [25:48] well behaved and and you know, folks who [25:51] are working for companies that um are, [25:54] you know, a little uh a little more [25:56] strict on things um that they share, uh [26:00] those folks are already kind of aware of [26:03] that and so they're very aware of what [26:05] they're saying in a public setting and [26:07] something that's going to be recorded. [26:09] So, yes. I mean, maybe maybe we do just [26:13] start live streaming things [26:15] and and leaving it on YouTube. I don't [26:18] know. How does that work with Zoom, [26:20] though? [26:22] Does anybody know? Has anybody done [26:23] that? [26:29] >> I'm sure it's probably possible, but I [26:31] haven't got specific knowledge of [26:34] >> a feature like that existing. I know I [26:35] feel like I remember Jity lets you like [26:38] live stream to YouTube. I think that's [26:39] what the Fedora design team used to do [26:41] or does do, [26:43] >> but [26:44] >> you can [26:44] >> imagine switching entire platforms is [26:46] not in the cards. [26:48] >> Just use OBS. [26:50] >> It's it's that's what you'll do and then [26:52] stream it to any platform. [26:55] >> Yeah. [26:55] >> But then that requires someone in the [26:57] meeting to be streaming and then that's [26:59] that's sort of independent from Zoom's [27:01] recording. And so you might not you [27:02] might be streaming but you might not be [27:04] recording it in Zoom and then you might [27:06] not get the disclosure that it's being [27:07] recorded. [27:09] >> So that might be a bit tricky I think. [27:12] But [27:12] >> Oh yes. Okay. [27:14] >> That is that is kind of an option I have [27:15] used as like a nuclear option in the [27:17] past though for like [27:18] >> recording meetings like oh Zoom is [27:20] breaking like everyone's like we're [27:22] going to record this and no one [27:23] everyone's like it's broken. I'm just [27:24] like I'm gonna fire up OBS and just [27:26] >> do a quick and dirty recording. [27:28] >> Yeah. Yeah. [27:31] Okay. Well, how about if if um if I take [27:34] a look Oh, I just Sorry, whatever I'm [27:38] doing that to. I'm so sorry. I'm trying [27:40] to try not to get in your way. Okay. [27:41] Wait, let me just put it out here. Uh [27:44] okay, I'm going to move you down. There [27:46] we go. Okay. Um, I'll just look and see [27:49] if there is like a Zoom um, [27:53] a Zoom plus YouTube like integration [27:59] for live streaming [28:02] or like what is even out there? [28:06] Cuz I mean, yeah, now that now that [28:07] we're chatting about it, it does kind of [28:09] seem like a a little, you know, a little [28:14] bit of overkill. Like I don't know that [28:16] we need to be that um [28:19] to be that careful anymore. Like yeah, [28:23] >> even if there's like a way I wonder if [28:25] it would be helpful like if we can find [28:26] maybe like a Slack integration for Zoom [28:29] where like I don't know how we can [28:32] necessarily associate a Zoom meeting [28:33] with the Slack with a Slack channel, but [28:35] like have it so that like once the [28:38] recording for this meeting is available, [28:41] it would ping for example a general [28:42] channel for this meeting or like the [28:45] augur channel for an augur meeting and [28:47] be like, "Hey, the recording is [28:48] available." And that would kind of be a [28:50] signal for whoever to to click the link [28:52] and maybe upload to YouTube or I don't [28:54] know if there's a way we could even [28:56] automate it beyond that. But [28:58] >> I mean that's a good that's a good [29:00] question is can we because the the [29:04] recordings are all there. They're all [29:05] there in our Zoom account. Um they're [29:08] all listed as like Chaos Community's [29:10] personal meeting right now. And so [29:12] that's another thing that takes time [29:14] because I have to click on the recording [29:16] figure out which one it was. Um, and [29:19] then I like manually upload it to [29:22] YouTube with the little uh icon, you [29:25] know, the little thing, add all the [29:27] metadata to YouTube. Um, [29:31] in the meantime, I wonder if we could [29:34] like just internally share the Zoom link [29:36] cuz we don't get rid of those. They [29:38] stick around. Um, at least they have [29:41] been. I guess maybe we couldn't do that [29:43] indefinitely, but um we could share that [29:46] immediately [29:48] in the Slack channel for those folks who [29:50] are just, you know, in that small [29:52] community and then then share it broadly [29:55] with on YouTube like at cuz I would do [29:58] it every Friday is what would happen and [30:00] then I just haven't been because I've [30:01] been super busy. Um, but you know, that [30:04] way at least the folks who are who are [30:06] mostly, you know, interested in watching [30:08] that video would get it earlier and then [30:10] the rest of folks could get it a few [30:12] days later. [30:14] >> Actually, that's an interesting idea of [30:15] like doing it on Friday because I wonder [30:16] if that could solve the like need to [30:19] make emergency edits problem where it's [30:20] like as soon as it's available, it [30:22] slacks it to whatever group. That's [30:24] probably going to be the hard part. [30:25] >> Yeah. But then maybe there's like a time [30:27] delay of like okay 5 days later if they [30:30] if the process wasn't cancelled by [30:32] someone with the authority to do that [30:35] >> it's going to automatically upload to [30:36] YouTube. So like there's a buffer so [30:38] that if someone like watches the [30:39] recording and it's like um this [30:40] shouldn't be in here like the process [30:43] can be stopped but it's the default [30:46] setting is just automatic so that it's [30:48] not someone like your responsibility to [30:50] go in every Friday and do it and then [30:52] it's like you get busy and you forget [30:54] and it's all the human [30:56] things that cause that to fall like that [30:59] process to sort of be fragile. [31:01] >> Yeah. Yeah, that makes sense. Um [31:06] Yeah, that's a good that's a really good [31:07] idea. [31:09] Um [31:11] because we do have, you know, like in [31:13] the YouTube it's um you know, for the [31:16] descriptions they're pretty much the [31:17] same. They used to not be the same. Um [31:20] okay, bye. Merry blessings. See you. Um, [31:23] but now I kind of just say, "Hey, you [31:27] can find the minutes to this meeting [31:28] with this link." [31:30] >> Full stop. Like that's all I put in the [31:31] description. So, um, yeah, I used to [31:35] when we had like three meetings a week, [31:37] I was able to, you know, expand a little [31:39] bit on the on the, uh, video, but, now [31:42] that we have like 12 to 15 a week, it's [31:44] a lot more. So, it's like a lot a lot [31:47] less time spent uh crafting a beautiful [31:50] description of these videos. Uh but I I [31:54] like that idea of like automating it but [31:57] also allowing for that human [31:58] intervention if needed if needed which [32:01] is rare frankly. So [32:07] yeah, honestly like that is one of the [32:09] most I think the reason that I am so far [32:12] behind is it's one of the most [32:14] timeconsuming things I do but like the [32:16] least impactful really. Um I know people [32:20] are waiting for those videos but like [32:21] the there are other things that kind of [32:23] take priority over that. So that always [32:25] gets pushed kind of towards the bottom. [32:26] So um sadly you know but now it's kind [32:30] of a it's a thing. It's a it's a big [32:32] thing. So yeah, that's on me for sure. [32:35] Yeah, I'm not immediately able to find [32:38] like offtheshelf existing things that [32:40] can do this, but [32:42] >> um I imagine it probably wouldn't be too [32:45] crazy for this is me signing myself up [32:48] for more things, but too crazy for [32:50] someone with my level of software [32:52] development experience to just vibe code [32:55] and review code review some little like [32:58] scheduled task that just goes and like [33:01] checks the meetings. I think I was also [33:03] looking into um [33:04] >> whether there's like a Slack bot that [33:06] can because I know I know like I think [33:08] experimented before with with just [33:09] meeting reminders [33:10] >> and like since we don't use Google [33:12] calendar or Microsoft calendar like [33:14] there's not really a clear offtheshelf [33:17] like I I would have thought that there [33:18] would be a [33:19] >> like [33:20] >> ICS like it can just take any any [33:23] calendar format and just [33:25] >> process it but I guess not. So maybe [33:27] maybe maybe we could work it into that [33:29] of like you get the like a just have our [33:31] own custom bot or something that just [33:32] does meeting reminders and then like [33:34] >> detects when the like hey we know there [33:36] was a meeting that just happened. Here's [33:38] the Zoom like maybe we can somehow [33:40] associate it with the Zoom link [33:42] >> in our like a custom system [33:44] >> and then like it so then it would it [33:46] would have access to our Zoom our Slack [33:48] and our YouTube but then it could kind [33:50] of manage that. [33:52] >> Yeah. And I believe that all of those [33:55] things are um using the same email [33:58] address which is the chaos Gmail. So [34:01] that might actually work cuz that's [34:04] another problem that we had with the [34:06] calendar integration um with the teamup [34:09] in particular. Although that's it's all [34:11] under the chaos Gmail, it's uh it's it's [34:14] like its own system. So, it will only um [34:18] like that's the email we use to [34:20] administer the platform, but it will [34:23] only integrate things that are on the [34:25] chaos Gmail calendar. So, it was not [34:30] >> Yeah, it doesn't work the way we would [34:32] want it to work. We'll just say that. [34:34] We'll just say that the the out of the [34:35] box um [34:36] >> are you from team up? Yeah. [34:42] I think I think the idea of switching [34:44] away from Zoom is maybe a like I think [34:47] if we had if we if there was a solution [34:49] that required switching to Zoom I think [34:51] that would be a lot harder to adopt in [34:53] one shot. Like I think [34:55] >> if we had like [34:58] >> I mean Discord's probably arguably a [34:59] little bit more proprietary and [35:02] >> no it does everything you were saying [35:03] with a bot. You can do it perfectly and [35:05] it's exactly what you're talking about. [35:07] It's and the calendar integration. It's [35:09] way better with calendar integration. [35:11] And for video calls, it's a way smoother [35:14] service than Zoom or Google Meet. Um, [35:17] >> but I know they do recording though and [35:19] I think they weird age verification. [35:21] >> They do recording and streaming and [35:23] everything. I guess I'm in Canada so we [35:24] don't have to worry as much about the [35:26] age verification stuff. [35:28] >> Yeah, that's interesting though. [35:31] >> Uh, Discord's just it the reason it gets [35:33] poo pooed is because China owns it, [35:34] right? like you're sending your data to [35:37] another. [35:38] >> Yeah. Like CH 10-centent owns Epic Games [35:41] like they own most of the companies. So [35:43] like uh you you that's that's the only [35:47] diff difficulty. But this is this isn't [35:49] self you guys use Slack anyway. So [35:51] you're already giving everything to [35:52] Salesforce like so security doesn't seem [35:56] to be a big concern. So Discord covers [35:58] all those bases. I don't know why more [36:00] people don't use it, but I think it's [36:01] because it's a gamer platform, but [36:05] >> I mean it seems also like a lot of it [36:07] too is more of just like this is what [36:09] the community is already established on. [36:11] And I think there's I think that there's [36:12] going to be when we switching anything [36:14] there's going to be a drop off rate of [36:16] some percentage of people that just [36:18] don't like either weren't aren't really [36:20] active in the Slack or don't feel like [36:23] using Discord or whatever. And so I [36:24] think any major migration we make like [36:26] that is going to inevitably lose some [36:28] fraction of the community and how big [36:30] that fraction is sort of depend. [36:33] >> Think of it like that. We live in the [36:34] splinter web. You have to think that you [36:36] have to cover multiple communities. You [36:38] just have to cover all three. I I run [36:40] the maker space locally and we're a [36:42] 13,000 person town [36:44] >> and I can't get everyone into Discord. I [36:46] can't get everyone on Signal. I can't [36:48] get everyone into a Telegram group. I [36:49] can't get everyone. So, I have three [36:51] platforms I have to use and even then [36:54] Facebook's how I end up having to [36:55] contact most people. Um, which is sad, [36:58] but it it's the state of what we live [37:01] in. Um, but for what you're talking [37:04] about, the recordings and stuff, you can [37:07] also just stream this to Discord as [37:09] well. So, like that's where one of those [37:12] things like OBS or having someone manage [37:14] the video, uh, people can attend the [37:16] same meeting from Discord as they can [37:17] from Zoom. So, one of the things one of [37:20] the things I've been experimenting with [37:21] a little bit sort of just because I know [37:23] with with some of the augur maintenance [37:24] stuff, we do have a Discord server that [37:26] sort of came out of some of the research [37:28] origins of Augur at the University of [37:30] Missouri. And so, there's a maintainers [37:32] chat on there and then there's a a [37:34] private Slack channel for maintainers [37:35] and like they were both kind of [37:36] separate, but I I've I got a a bot set [37:39] up recently called Matterbridge that [37:41] would bridge the two. I've used it [37:42] before in other communities to do [37:43] something similar to kind of what you're [37:45] saying with juggling different [37:46] communities and groups. Um, I'm part of [37:50] me is now curious like could we use that [37:52] and maybe have a discord server where we [37:55] run that bot that you were saying and [37:57] then have just a onetoone channel like [37:59] the general like all the channels that [38:01] are in chaos slack are bridged to [38:03] discord so that the bot can kind of run [38:05] and like anything the bot shares get [38:07] sort of bridged back to slack but it's [38:09] kind of it's sort of a hacky solution [38:11] but it kind of could work if we want to [38:14] just use the off-the-shelf bot. [38:15] >> It's definitely hacky but it grows the [38:17] audience. Um, but it's just irrelevant. [38:19] I It covers a lot of the bases. So, but [38:22] it is so hard to push people to a new [38:23] platform and I don't I don't want to [38:25] push that topic. [38:30] >> Yeah, we should definitely chat more [38:31] though like if you're interested in in [38:33] like it sounds like you use a lot of the [38:35] platforms that I think Matab bridge [38:37] might support. So, I don't know if [38:38] running [38:39] >> I'm on every single platform. Yeah, I I [38:41] I for my last job, I had to set up a [38:44] streaming service so it streamed to [38:46] every single platform because that's [38:47] what they wanted, even though they [38:48] didn't know why they wanted it. And I [38:50] did it and it was quite amusing to see [38:52] uh my computer almost melt by streaming [38:55] to like 32 platforms at once um through [38:59] uh Streamlabs OBS. Um it was cool to to [39:03] be able to realize you can you can put [39:06] yourself on everything really fast. Uh [39:10] It's kind of cool. But yeah, the it's [39:13] kind of different than this. [39:22] >> Looks like we are almost out of time. [39:24] Um, great conversation. Thank you all [39:26] for helping me kind of think about this [39:28] and and bringing these ideas up. I love [39:30] it. I love these ideas. Um we can [39:33] certainly talk about it more like we [39:35] would not decide anything anything right [39:38] away for sure but um yeah these are [39:40] great ideas. I will look into the zoom [39:43] um I'm also going to double check on [39:45] that the issue uh adding to the [39:47] contributors um doc make sure that that [39:51] process is working before we open the [39:53] elections. [39:54] Um, any other questions we have before [39:58] we kind of shut down here? We do have a [40:00] couple of reminders about CFPS. If you [40:02] haven't [40:04] haven't submitted and you would like to, [40:06] that's how you can do that and when you [40:08] should do that and they're both good [40:11] good conferences there. [40:14] >> Just don't beat yourself up for not [40:15] uploading because the whole point of [40:17] these things is to come to them, right? [40:19] So, [40:19] >> hey, there you go. [40:20] >> Yeah. Yeah. That's That's never beat [40:23] yourself up for something that you [40:24] haven't done yet. [40:26] >> That's That's right. It was completely [40:28] on purpose. Um the idea was to motivate [40:30] people to come in person. Yes, that's [40:33] 100%. [40:37] >> The world's stressful and we're still [40:39] just cave people. So, [40:40] >> yeah, we're just doing the best we can. [40:45] >> Yeah, Elizabeth, you've been doing [40:47] great. Actually, keeping it. [40:50] >> Thank you. Thank you. Thank you. [40:55] All right. Well, I'm going to go ahead [40:56] and stop sharing. Um, thanks everybody [40:59] for showing up. Appreciate your input [41:01] and your voices today. Um, give you some [41:03] great ideas. So, thank you for bringing [41:05] them. And we will see you here next time [41:07] next week. Same place, same time. See [41:10] y'all later. Have a good one. [41:12] >> See you. Thank you. [41:12] >> Bye everybody.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, March 17 2026.md|CHAOSS Weekly Community Call, March 17 2026 by YouTube]] ## Highlights - information and also like a get various wrappers around it for like GitHub actions, GitLab actions, things like that. Um, it's very sort of work in progress. I think there's sort of a minimum viable version in the codebase right now, but I think both Andrew and I our primary focus is elsewhere. So having like if if people are interested in helping with this um there's a there's a Slack channel. Um I think we sort of mildly informally have meetings. Um I I've sort of just said like hey ([View Highlight](https://read.readwise.io/read/01kpb592y3kf4p0rhdy7wdzejv)) - Tags: 👻 ai highlighted - let's meet every two weeks after the the Augur 8 not meeting if there's enough stuff to talk about. Uh I think we've had like one meeting so far a few weeks ago. But it it would be nice to kind of see this take off more and and do more like make progress and and sort of potentially even be a space for other other similar projects to kind of unify and under kind of a Linux Foundation chaos umbrella to kind of help detect a lot of this because I know this is like very popular like this kind of thing is I think going ([View Highlight](https://read.readwise.io/read/01kpb592yjbnrfajfeyz7qsdjx)) - Tags: 👻 ai highlighted - that. I will I will commit to getting caught up this week. I will commit to that. Um, I am just so sorry for that that I am so far behind on on uploading those meetings. I know it's been um I know that's a problem and it's completely on me, 100% on me. Um yeah, so here's the thing about automating it and we have looked at this in the past. Um because in theory you could, right? Like it's we could either record straight to YouTube, just live stream it ([View Highlight](https://read.readwise.io/read/01kpb5931y6x7sytcvn5ar1btm)) - Tags: 👻 ai highlighted - and record it straight to YouTube or we could share the links straight to Zoom. Those are also options that we have thought about. The reason that we don't have it automated now and this could change like if if somebody else you know I mean this was from before so it doesn't mean it has to be like this forever. The reason that we decided not to make that automated process is that we wanted to leave space for um a a manual layer of checking in case there are like ([View Highlight](https://read.readwise.io/read/01kpb5934wvjzf8x0cm0mm44zw)) - Tags: 👻 ai highlighted - or like what is even out there? Cuz I mean, yeah, now that now that we're chatting about it, it does kind of seem like a a little, you know, a little bit of overkill. Like I don't know that we need to be that um to be that careful anymore. Like yeah, >> even if there's like a way I wonder if it would be helpful like if we can find maybe like a Slack integration for Zoom where like I don't know how we can ([View Highlight](https://read.readwise.io/read/01kpb593a3nx3fjht5d8nwcwp6)) - Tags: 👻 ai highlighted - necessarily associate a Zoom meeting with the Slack with a Slack channel, but like have it so that like once the recording for this meeting is available, it would ping for example a general channel for this meeting or like the augur channel for an augur meeting and be like, "Hey, the recording is available." And that would kind of be a signal for whoever to to click the link and maybe upload to YouTube or I don't know if there's a way we could even automate it beyond that. But >> I mean that's a good that's a good ([View Highlight](https://read.readwise.io/read/01kpb593eym9zfba3jmh5fa2mg)) - Tags: 👻 ai highlighted - in the meantime, I wonder if we could like just internally share the Zoom link cuz we don't get rid of those. They stick around. Um, at least they have been. I guess maybe we couldn't do that indefinitely, but um we could share that immediately in the Slack channel for those folks who are just, you know, in that small community and then then share it broadly with on YouTube like at cuz I would do it every Friday is what would happen and then I just haven't been because I've ([View Highlight](https://read.readwise.io/read/01kpb593m4hr9sjzkqy7t5y37c)) - Tags: 👻 ai highlighted