CHAOSS Weekly Community Call, March 24 2026

CHAOSS Weekly Community Call, March 24 2026 ![rw-book-cover](https://img.youtube.com/vi/ufaG0u8uVzo/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, March 24 2026](https://www.youtube.com/watch?v=ufaG0u8uVzo) > [!note]+ Document Notes > tags: #chaoss #open-source #community-management #elections #ai-alignment #github-alternatives > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=ufaG0u8uVzo > date created: 2024-03-24 15:00 > > # 🏷️ Title: CHAOSS Weekly Community Call - March 24, 2026 >  ## 🧰 Action Inbox - [H1] Create spreadsheet for meeting facilitator signups — improve volunteer coordination 24:00 #community-management - [H2] Post Codeberg mirroring discussion in general Slack channel — get community feedback 15:45 #infrastructure - [H3] Test YouTube live streaming for automated video uploads — reduce manual workload 35:20 #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 AI Alignment Survey](https://www.survey-link.com) - [CHAOSS Board Elections FAQ](https://github.com/chaoss/community) - [All Things Open CFP](https://allthingsopen.org) ## 📝 Summary - **What happened**: Weekly CHAOSS community call covering facilitator rotation, infrastructure discussions, board elections, and workflow improvements - **Why it matters**: Community governance and operational efficiency are critical for sustainable open source project management - **Key stakeholders**: CHAOSS community members, working group leaders, board election candidates - **Risks and tradeoffs**: Balancing automation with quality control, managing volunteer burnout, maintaining GitHub dependency - **Bottom line**: Community is actively working on sustainability through distributed leadership and improved processes ## 📖 Main Content The CHAOSS community is implementing several operational improvements while navigating ongoing organizational changes. The call addressed rotating facilitator responsibilities to prevent burnout, explored infrastructure alternatives like Codeberg mirroring to reduce GitHub dependency, and provided updates on upcoming board elections using ranked choice voting through the Electto platform. The community is also testing automation solutions for video uploads to YouTube while maintaining quality control through private streaming and manual review processes. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/ufaG0u8uVzo?t=0) — [H3] Meeting setup and technical issues - Key idea: Internet connectivity affecting video quality during community call - Evidence: "My internet has been so weird lately. I don't understand. Something's going on." #### ⏱️ [02:15](https://youtu.be/ufaG0u8uVzo?t=135) — [H2] Facilitator rotation discussion - Key idea: Community struggling to find volunteer facilitators for weekly calls - Evidence: "We have been rotating facilitators because nobody wants to facilitate, which is also totally fine." #### ⏱️ [03:45](https://youtu.be/ufaG0u8uVzo?t=225) — [H1] Spreadsheet solution for facilitation signup - Key idea: Structured signup process would improve volunteer coordination - Evidence: "It might be easier for people to see dates and fill in their availability... that's just not really how my brain works." #### ⏱️ [05:30](https://youtu.be/ufaG0u8uVzo?t=330) — [H3] UN SDG working group agenda item - Key idea: Recurring agenda item with no representatives present to discuss - Evidence: "This has been on the agenda for I think four weeks now... we haven't had anybody yet that has been able to make it." #### ⏱️ [06:20](https://youtu.be/ufaG0u8uVzo?t=380) — [H2] AI bot infiltration problem - Key idea: Persistent issue with meeting bots despite admin controls - Evidence: "We have selected every box everywhere throughout the entire Zoom admin and nothing works. These bots just keep coming in." #### ⏱️ [08:45](https://youtu.be/ufaG0u8uVzo?t=525) — [H3] Data privacy concerns with AI bots - Key idea: Community prioritizes data control over convenience - Evidence: "We don't have control over where that data goes if it's getting slurped up by an AI bot." #### ⏱️ [12:30](https://youtu.be/ufaG0u8uVzo?t=750) — [H2] Codeberg mirroring proposal - Key idea: GitHub reliability issues driving interest in alternative forges - Evidence: "GitHub's website's been not the most reliable over the last month or so." #### ⏱️ [15:45](https://youtu.be/ufaG0u8uVzo?t=945) — [H1] Infrastructure migration concerns - Key idea: Resource constraints limit ability to fully migrate from GitHub - Evidence: "We talked a long time ago about moving to GitLab and there were very good reasons that we did not do that mostly because of automation." #### ⏱️ [19:20](https://youtu.be/ufaG0u8uVzo?t=1160) — [H2] AI alignment survey reminder - Key idea: Community gathering data on individual AI perspectives - Evidence: "They're just curious to know how we as a community individually are thinking about things in AI." #### ⏱️ [21:15](https://youtu.be/ufaG0u8uVzo?t=1275) — [H1] Board elections progress update - Key idea: First-time election process using ranked choice voting - Evidence: "It's kind of the first time for all of us. So, it's a learning opportunity and a learning experience for everybody." #### ⏱️ [25:40](https://youtu.be/ufaG0u8uVzo?t=1540) — [H3] Election platform details - Key idea: Electto platform requires GitHub accounts for voting eligibility - Evidence: "You will need a GitHub account though to vote and to mark yourself eligible for candidacy." #### ⏱️ [30:10](https://youtu.be/ufaG0u8uVzo?t=1810) — [H2] Candidate information process - Key idea: Campaigning limited to standardized contribution documentation - Evidence: "You will fill out a form that tells all of your contributions to the project and of course your name." #### ⏱️ [35:20](https://youtu.be/ufaG0u8uVzo?t=2120) — [H1] YouTube automation proposal - Key idea: Live streaming to private YouTube could reduce manual upload workload - Evidence: "It is very time consuming and there are a lot of meetings now. So it can pile up pretty quickly." #### ⏱️ [38:45](https://youtu.be/ufaG0u8uVzo?t=2325) — [H3] Content moderation considerations - Key idea: Manual review step rarely needed but provides safety net - Evidence: "That has happened maybe twice, maybe three times in my entire like six years of being here." #### ⏱️ [42:10](https://youtu.be/ufaG0u8uVzo?t=2530) — [H2] All Things Open CFP deadline - Key idea: Conference submission deadline approaching March 31st - Evidence: "CFP deadline is March 31st. That's coming up very soon." ## 📚 References - [Electto Open Source Election Platform](https://electto.io) - [CHAOSS Community GitHub](https://github.com/chaoss/community) - [Codeberg Open Source Forge](https://codeberg.org) - [KNative Elections Example](https://github.com/knative/community/elections) ## 🗣️ Paraphrase - CHAOSS is implementing a rotating facilitator system to prevent volunteer burnout while creating better signup processes through spreadsheets - The community is exploring Codeberg mirroring as a backup to GitHub due to reliability issues, though full migration isn't feasible due to resource constraints - Board elections are progressing with ranked choice voting through Electto, requiring GitHub accounts for participation and standardized candidate documentation ## 📰 Newsletter The CHAOSS community is taking proactive steps to improve sustainability and resilience! They're implementing rotating meeting facilitators to prevent burnout, exploring infrastructure alternatives like Codeberg mirroring for better reliability, and preparing for their first board elections using modern ranked choice voting. The community is also streamlining operations by testing automated YouTube uploads while maintaining quality controls. These initiatives demonstrate how mature open source communities can evolve their governance and operations to stay healthy and inclusive. Key updates: Board elections coming soon with candidate submissions, AI alignment survey still accepting responses, and All Things Open CFP deadline March 31st. Resources: [CHAOSS GitHub](https://github.com/chaoss), [Board Elections Info](https://github.com/chaoss/community), [Working Groups](https://chaoss.community/participate/) ## ✅ Action Items #### Community - Create facilitator signup spreadsheet with date availability slots - Post Codeberg mirroring discussion in general Slack channel for broader input - Test YouTube live streaming with private settings for automated uploads - Finalize board election timeline and announce to community - Follow up with UN SDG working group for agenda item clarification #### OSPO - Evaluate forge alternatives for organizational resilience planning - Document infrastructure dependencies and migration constraints - Assess data governance implications of AI bot infiltration #### DevRel - Promote All Things Open CFP deadline in community channels - Share AI alignment survey results when available - Document election process learnings for future governance improvements ## 🧪 Hypotheses - Spreadsheet-based signup will increase volunteer facilitator participation compared to verbal requests during meetings - Private YouTube live streaming will reduce video upload workload by 70% while maintaining content quality - Codeberg mirroring will provide adequate backup infrastructure without requiring full GitHub migration - Ranked choice voting will produce more representative board election results than simple plurality voting ### 📊 Methodology - A/B test facilitator signup: spreadsheet vs. meeting requests over 8-week period - Time tracking study: manual upload vs. automated streaming workflow comparison - Infrastructure uptime monitoring: GitHub vs. Codeberg availability metrics - Election participation analysis: voter turnout and candidate diversity measurement ### ❓ Questions - How can open source communities balance automation efficiency with human oversight for quality control? - What infrastructure redundancy strategies work best for communities with limited technical resources? - How do election mechanics affect participation rates and representation in open source governance? ### 🔮 Future Research - Cross-community comparison of facilitator rotation strategies and burnout prevention - Forge ecosystem analysis for organizational resilience planning - Open source election platform evaluation for community governance ### 💡 Implications - **Practice**: Communities need systematic approaches to volunteer management and infrastructure resilience - **Policy**: Election processes must balance accessibility with security and verification requirements - **Security**: AI bot infiltration represents ongoing challenge requiring vendor-level solutions - **Education**: Governance transitions require documentation and knowledge transfer planning - **Funding**: Infrastructure alternatives may require evaluation of cost-benefit tradeoffs ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Meeting agenda structure, election timeline documentation - Improve: Infrastructure architecture diagrams, workflow visualizations #### 🔊 Aural learners - Present: Weekly video calls with recorded discussions - Improve: Audio-only versions for accessibility #### 🗣️ Verbal learners - Present: Clear explanations of technical concepts like Forgejo and Codeberg - Improve: Glossary of community-specific terminology #### 🧩 Kinesthetic learners - Present: Hands-on election process, GitHub contribution tracking - Improve: Interactive tutorials for new community members #### 🧠 Logical learners - Present: Structured decision-making process for infrastructure choices - Improve: Decision matrices for evaluating alternatives #### 🧑‍🤝‍🧑 Social learners - Present: Weekly community calls, working group collaboration - Improve: Peer mentoring programs for new contributors #### 🧘‍♀️ Solitary learners - Present: Individual contribution tracking, self-nomination process - Improve: Self-assessment tools for community involvement #### 🌿 Naturalistic learners - Present: Organic community growth patterns - Improve: Ecosystem thinking about community sustainability ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Meeting notes with clear headings and structure - Improve: Standardized heading hierarchy across all documentation #### Keyboard navigation - Present: Text-based discussion and documentation - Improve: Ensure all web interfaces support keyboard-only navigation #### Contrast and readability - Present: Plain text meeting transcripts - Improve: High contrast themes for documentation sites #### Text resizing and reflow - Present: Responsive documentation format - Improve: Test zoom capabilities across community platforms #### Media and captions - Present: Video recordings of all meetings - Improve: Automated captions and transcript publication #### Forms and interactions - Present: GitHub-based contribution tracking - Improve: Alternative forms for non-GitHub users ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community participation across time zones - Improve: Rotating meeting times for geographic inclusivity #### Inclusive language - Present: Professional, welcoming tone in community discussions - Improve: Community language guidelines and moderation #### Neurodiversity support - Present: Multiple participation formats (video, text, async) - Improve: Structured agendas and predictable meeting formats #### Representation - Present: Diverse voices in working groups and leadership - Improve: Demographic tracking for representation analysis #### Psychological safety - Present: Respectful discussion culture, clear moderation - Improve: Anonymous feedback mechanisms ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Infrastructure redundancy reduces single points of failure (premise: GitHub outages affect productivity) - Inductive strength: Past volunteer patterns predict future participation challenges - Causal reasoning: Automation reduces manual workload and enables faster content publication - Analogical strength: KNative election model provides template for CHAOSS governance #### Fallacies - Appeal to tradition: "We've always used GitHub" - addressed through evidence-based evaluation - False dilemma: Not fully exploring middle-ground solutions between manual and fully automated processes #### Tone of voice - Overall tone: Collaborative and problem-solving focused with acknowledgment of resource constraints and learning opportunities ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - community openly acknowledging challenges - Attack: No attacking behavior - constructive criticism of platforms not people - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive, solution-oriented language emphasizing collective learning ## 🎯 Conclusion The CHAOSS community demonstrates mature open source governance by proactively addressing sustainability challenges through distributed leadership, infrastructure resilience planning, and democratic decision-making processes. Their approach of testing incremental improvements while maintaining quality standards provides a model for other communities navigating similar operational challenges. The focus on volunteer well-being and inclusive participation shows how technical communities can prioritize human factors alongside technical efficiency. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Communities need systematic volunteer management approaches > [!quote] CHAOSS Weekly Community Call by CHAOSS Community via YouTube. Published 2026-03-24. Accessed 2024-03-24. > "It might be easier for people to see dates and fill in their availability rather than volunteering during meetings." Demonstrates structured signup processes improve volunteer coordination over ad-hoc requests. [view highlight](https://youtu.be/ufaG0u8uVzo?t=225#H1) #xref #articleseed ID:rw_chaoss_001 ### [H2] Infrastructure resilience requires backup strategies > [!quote] CHAOSS Weekly Community Call > "GitHub's website's been not the most reliable over the last month or so." Shows how platform dependencies create vulnerability requiring mitigation planning. [view highlight](https://youtu.be/ufaG0u8uVzo?t=750#H2) #xref ID:rw_chaoss_002 ### [H3] Automation --- ## Full Transcript [00:02] Okay. Hi everybody. It is Tuesday, March [00:05] 24th. You're here at the weekly [00:08] community call for chaos. So good to see [00:10] everyone. [00:12] Really glad you're here. [00:15] Let me share [00:18] my screen. There we go. [00:21] Nope. [00:24] Yep. [00:27] There we go. [00:30] Okay. Hopefully it doesn't get too [00:33] choppy. If it does, I'm going to turn my [00:35] camera off because my internet has been [00:37] so weird lately. I don't understand. [00:40] Something's going on. Actually, I am [00:42] going to turn my camera off [00:44] cuz [00:47] stop video. There we go. Maybe that will [00:50] be helpful. Okay. [00:52] Um, yeah. if you have not added your [00:56] name here and told us what your favorite [01:00] subject was in school. [01:04] Um, yeah, I'm just curious. I think mine [01:07] was English. [01:10] I did well in math, but I don't really [01:12] like math, honestly. [01:16] It's hard. [01:17] So is English, to be fair, but [01:21] I did I did like that. Um, okay. If you [01:24] haven't been here in a couple of weeks, [01:25] we um have been rotating facilitators [01:29] is we've been rotating, I should say, [01:31] because nobody wants to facilitate, [01:34] which is also totally fine. Um, so if [01:37] there is someone that wants to [01:39] facilitate next week, we do have a guide [01:41] for you. It is easier than it seems like [01:43] it would be. Um, so no need to be [01:45] intimidated, but um, yeah, if anyone [01:49] wants to do that, raise your hand. [01:57] Have we made a spreadsheet yet? [02:01] >> Uh, no, we haven't made a spreadsheet [02:03] yet. We are haven't even gotten people [02:06] to [02:08] >> to volunteer during the meeting. So, um, [02:11] I think [02:12] >> yeah, [02:13] >> I think that it might be easier for [02:15] people to see dates and fill in their [02:17] availab like fill like I know that's how [02:19] I would like sign up. I'm sure I'm happy [02:22] to facilitate some meetings, but like on [02:24] a in a spot in a call, I'm not going to [02:26] I won't be the one to be like, "Oh, [02:28] yeah, I'll do this." Cuz I'm that's just [02:29] not really how my brain works. Um, and [02:32] so it might be easier to allow people to [02:36] fill in and we can then distribute it on [02:38] general and people can fill in based off [02:40] of their like availability a little bit [02:43] farther out. Um, and I also might [02:48] promote doing that. Um there's a [02:50] discussion of doing this as well for the [02:52] data science working group and so I [02:54] might just ask if we can if people for [02:57] their respective working groups want to [02:59] make a tab um similar to how we have for [03:02] the general meetings um if that's how [03:04] people want to facilitate um I know [03:07] that's what we're looking at doing for [03:08] the data science working group so it [03:10] might make sense for those to all live [03:11] in the same place [03:15] >> and while we want to figure that out I [03:17] am happy to facilitate the call for to [03:19] make [03:22] except I need to change this. I will let [03:24] I let though but yeah I can. [03:29] >> Excellent. Thank you. Merry blessing and [03:31] Cali that is a great point. Um which [03:35] makes total sense to me. So I will do [03:39] that. Um [03:45] I love that idea. There we go. [03:48] because yeah, I do think there's [03:49] probably more people who would be [03:51] willing um just in a in a little bit of [03:54] a different format. [03:57] >> Perfect. Okay. [03:59] Well, thank you, Merry Blessing. And you [04:02] are all set for next week. I will [04:04] probably still be here uh just to, you [04:06] know, be here, but um so if you if you [04:09] do something comes up or whatever, I'm [04:10] happy to be a backup. No, no worries at [04:12] all. [04:16] Um okay. Any other questions, comments, [04:19] anything on that? [04:24] All right. Uh, this was from this has [04:27] been this has been on the agenda for I [04:30] think four weeks now, maybe three. Um, [04:33] because it's here and I'm holding it for [04:36] I'm holding space for it in case someone [04:38] from the UN SCG working group wants to [04:40] talk about it, but we haven't had [04:42] anybody yet that has been able to make [04:44] it to this meeting to talk about it. So, [04:48] I don't actually know more than what is [04:51] here. [04:55] So, maybe what I'll do is ask the UN SDG [05:01] working group to write out a little [05:04] thing or something, point us to [05:07] something so we have a little more [05:08] information about it. um [05:14] because that looks interesting and I [05:16] would like to hear more [05:20] unless anybody on this call knows [05:21] anything about it. [05:23] No, I don't think they do. Okay. [05:26] So, we'll just leave it at that. Um [05:30] Okay. Have we figured out who Henry is [05:34] and why the read.ai meeting notes keep [05:37] showing up? Um yeah, that is a that's a [05:41] big no on both of those things. Um the [05:45] so there in Zoom there is supposedly a [05:48] way to block various domains, [05:51] subdomains, whatever from coming into [05:54] the meeting. We have we have selected [05:57] every box everywhere in throughout the [06:00] entire Zoom admin and nothing works. [06:04] These bots just keep coming in. [06:06] fireflies, like whatever it is, otter, [06:09] even otter, you know, we were just [06:10] trying to block them all and they just [06:12] keep coming in. So, I kind of gave up [06:16] quite frankly. Um, I think maybe three [06:18] or four people have looked into this. [06:19] Nobody can figure it out. So, we just [06:21] keep kicking them out every meeting. [06:23] There we go. That's our solution. [06:25] >> Is it just the community call or is it [06:27] every call? [06:28] >> I think it's every call, right? Am I [06:31] right? Other other groups have those [06:32] bots in there too, right? [06:36] because I think I think the Augur 8 not [06:38] group uses a different link just so that [06:40] because I think there's like a time [06:41] conflict or something and I don't think [06:43] I've seen it in there but I don't know [06:45] maybe they're attaching to like the [06:47] chaos link and they just detect every [06:49] new meeting or something. I don't know. [06:50] >> I was just curious cuz I I I sent I told [06:53] one to opt out um in the chat before [06:56] this meeting and just curious. [06:58] >> Oh, is that you? Yeah, that that was I I [07:01] think that's a good idea. We can [07:02] certainly try that as well. Um I don't [07:05] know that they'll not come back, but [07:08] >> yeah, I think it just means it'll not be [07:10] there for this meeting. [07:12] >> Yeah. Yeah. [07:14] So yeah, [07:16] in answer to your question, no, they're [07:19] just going to keep coming in droves. I I [07:21] report them every time as spam every [07:24] time I fill those out. So, you know, my [07:27] hope is that eventually Zoom will get [07:28] tired of people doing that and give us [07:31] better tools to to control those. Um, [07:34] but yeah, our policy here at Chaos is to [07:36] not have those bots in the meetings [07:39] because we already are taking notes. We [07:41] publish these minutes. We publish the [07:44] videos and um we don't have control over [07:47] where that data goes if it's getting [07:50] slurped up by an AI bot. So, um, it's [07:53] just concerning and we would rather just [07:55] not have them here. So, that's why in [07:58] case anybody wonders. [08:05] Okay. Any other questions, comments, [08:08] notes, anything on that? [08:13] We'll just keep fighting big AI, I [08:16] guess. I don't know. I'm just old and [08:18] cranky, I think, at this point when it [08:20] comes to AI. Uh yeah. Anyway, uh okay, [08:25] >> we all [08:26] >> right. [08:27] >> I'm [08:28] there's still a two in my in front of my [08:31] my age and I feel old and cranky about [08:33] AI. [08:36] >> Well, good. That makes me feel young [08:38] then. Thanks, Callie. [08:40] >> Don't you worry. We're all We're all [08:44] together. [08:45] >> I love it. [08:46] >> Cranky about AI. [08:48] >> I love it. [08:50] people hating AI more than ICE. I mean, [08:53] that's fair. I hate both. Sorry, I [08:55] shouldn't be political on here, but I [08:57] Yeah, I do hate both of them. Oh, yeah. [09:02] Anyho, [09:03] um, okay, who put this on here? Data [09:05] Science Working Group. I'm guessing Don [09:07] or Cali. [09:07] >> That was me. [09:08] >> It was Adrian. [09:10] >> I I sort of I think that was kind of I I [09:12] forget exactly what the origin of that [09:13] conversation was, but it did come up in [09:15] the data science working group meeting [09:16] that just happened. And I think it kind [09:18] of the feedback was This is more of a [09:20] community level conversation. Okay. [09:23] >> I think the the idea was just like I [09:25] think GitHub's website's been [09:27] >> not the most reliable in over the last [09:30] month or so. Um [09:32] >> I I keep thinking it's because they keep [09:33] getting hit by AI bots or whatever. But [09:35] whatever it is, it's like sometimes I've [09:37] just had struggles like even just [09:38] loading the like a diff to to review a [09:41] PR or something. And so I think there [09:43] was a suggestion to like either mirror [09:46] the data science working group repo or [09:48] other repos over to codeberg. And I [09:51] think there seemed like there were a [09:52] fair number of potentially good reasons [09:54] to to also good reasons to do that. um [09:57] including um one of my goals for this [09:59] year with Augur is adding support for [10:03] additional forges like 4GO which is what [10:06] Codeberg is based on and having having [10:09] sort of a set of chaos repos which is [10:11] usually the default that Augur looks at [10:13] over there might might sort of help just [10:16] once I get to the stage of wanting to [10:17] test how well Augur collects on that [10:20] repo and then we can sort of directly [10:22] compare the the support for 4Jo versus [10:26] GitHub. [10:28] Um I think there was some others that I [10:30] forget to but I was just curious what [10:32] people think cur curious to bring this [10:34] to the community and see. [10:37] Yeah and as I mentioned in the data [10:39] science working group I think that um we [10:41] should also have this discussion with [10:43] Sean because he's he's not here and he [10:45] does manage a lot of the chaos [10:46] infrastructure. So I think this would be [10:48] good to have have a conversation with [10:50] him which Adrienne I know you talk to [10:52] him all the time anyways. [11:00] It would also be good to post this in [11:02] the general channel for discussion since [11:05] a lot of people aren't in this meeting. [11:16] I do not even know what codeberg is. [11:20] Can you somebody give me a 30 seconds [11:23] >> essentially? Um, so Forgio is an [11:26] open-source like basically [11:28] implementation of kind of a git forge. [11:30] Um, and then for uh codeberg is kind of [11:33] a like a sort of community instance of [11:37] that that I think is sort of the one of [11:39] the more common like open- source GitHub [11:42] alternatives. [11:56] How do you spell that? for forgio [12:01] 4jio [12:02] like that [12:07] or you can do oh forge.io. Okay, that [12:10] makes sense. But it's pronounced 4jio. [12:12] That's good to know. I never know how to [12:14] pronounce things cuz you know you just [12:16] see it written and you never get to [12:18] hear. So that is good to know. [12:23] Do you uh Adrian, do you want or [12:25] somebody from the data science working [12:27] group want to want to post that in [12:29] general? I think that would be good [12:34] just so you you can explain kind of why [12:37] and what and someone's in the meeting [12:40] link. You mean this you [12:44] here we go. [12:48] Hey Adrian, I'll kind of leave that to [12:50] you to facilitate. It's like to leave [12:52] that conversation. [13:01] Oh, I was muted. I can Yeah, I can post [13:02] that in general. Um, is that is that [13:05] more of just like a like, hey, we're [13:07] thinking about this. Come share feedback [13:09] kind of thing. [13:11] >> Yeah, I think so. [13:17] Yeah, my only concern would be like how [13:19] does it work like cross like I wouldn't [13:22] want I wouldn't want to want to like [13:25] leave GitHub as the place that like if [13:28] it's like something that you can do in [13:29] addition and there is like good bridging [13:32] between the two. Um, but a complete I [13:36] don't think I would be pro a complete [13:38] move over to codeberg and [13:42] no we talked a long time ago about [13:45] moving to GitLab and there were very [13:47] good reasons that we did not do that [13:50] mostly because of we have GitHub [13:52] automation and it would we just don't [13:53] have the people and resources to do a [13:55] migration. Um, but I think, you know, [13:58] the reason we would have this discussion [13:59] in general is to get people's feedback [14:01] and to make sure that, you know, if we [14:03] did something like this, if we did [14:05] mirror it to um to Codeberg, doing it in [14:09] a way that it's going to actually stay [14:11] up to date and that we're not going to [14:13] have [14:14] um, you know, issues with with the the [14:17] Codeberg instance being out of date and [14:19] people getting confused about where [14:20] things are. [14:22] >> Yeah. Or having only one of them. If [14:24] it's not, I wouldn't expect [14:25] compatibility, but kind of like blocking [14:28] issues and pull requests being open on [14:30] Cobberg unless there is like a a bridge [14:33] functionality, which sounds a little bit [14:35] would be a little bit complicated, but [14:37] as like just a pure mirror like and if [14:40] it kept up to date automatically. Yeah. [14:59] Just a side note, Codeberg comes in [15:02] mainly from the decentralized side of [15:05] things. So trying to get away from the [15:07] corporate Microsoft using their AI to [15:10] use eat all your code, but it doesn't [15:13] really work because like you're saying, [15:15] it just creates more of a splinter web. [15:17] So, [15:19] don't worry too much about it. [15:31] Unless you're willing to host your own. [15:33] In that case, then it's amazing. But if [15:36] you're not willing to go through the [15:37] effort like uh if you're not on Masttoon [15:39] or the Fedverse, then you probably don't [15:42] know about Codeberg. [16:02] Are you on mute, Elizabeth? [16:07] Yeah, I was. Um, yeah, I think that's a [16:10] really good point. That's a How does [16:12] Zoom work? I don't know. Yeah, I can't [16:15] keep up. Um, I think that's a good [16:17] point, but also, yeah, the resources [16:19] that it takes to to run that. Uh, I [16:23] don't know that we have those around us. [16:26] >> No, we do not have those for sure, [16:32] >> but [16:32] >> I think we should move on because [16:34] somehow this one got added above some of [16:35] the other agenda items that are also I [16:37] think pretty important for us to cover [16:39] today. [16:39] >> Okay. [16:39] >> Oh, it looked like they they just were [16:41] copied from last week. So, I I didn't [16:43] know if that was intentional or not. So, [16:45] sorry for [16:46] >> Oh, no, you're good. No, it's fine. It's [16:48] fine. [16:49] Um, just a reminder about the uh survey [16:54] that the AI alignment working group has [16:56] put out. I don't know what the date is [16:58] that they're ending that. So, go uh fill [17:03] that out sooner than later. Um, they're [17:06] just curious to know kind of how we as a [17:08] community individually are thinking [17:10] about things in in AI. It's um hosted by [17:13] University of Missouri, so it's already [17:15] gone through those those checks and [17:17] balances about any personal data, which [17:20] I don't even think they're collecting [17:21] any honestly. Um but it is you should [17:24] know that it does have a pretty strict u [17:27] process by which um you know data is [17:30] collected and stored. So you should uh [17:33] feel safe in filling that out. [17:38] And also Adrienne's looking for uh still [17:41] looking for contributors I assume. [17:43] Adrienne, you're still looking for [17:44] contributors, right? [17:45] >> I think so. Yeah, I think there's a [17:47] someone there's been at least one person [17:48] show up um since last week. So that [17:50] that's been helpful. But yeah, more if [17:52] people are interested in kind of helping [17:54] work on a project to detect like just [17:57] basic disclosure of like, oh, someone [17:59] had a commit that was [18:01] >> like co-authored by or authored by like [18:04] a known AI tool. like being able to flag [18:07] that and and help [18:09] metrics tools like Augur kind of see [18:11] that [18:11] >> sport. Yeah. [18:12] >> Things like that might be helpful. [18:15] >> Yeah. So I think actually a lot of [18:18] people would find that helpful. Not just [18:20] the chaos, but a lot of people because [18:23] that seems like a very good tool to [18:24] have. [18:27] So if you want to uh help out, that's [18:29] where you can go to do it into this [18:32] slack channel right here. [18:36] Um, moving on, we uh here is a reminder. [18:40] Uh, chaos board elections are coming. [18:43] Um, there is a doc that has the [18:45] information and we have an FAQ. Uh, we [18:48] do have an issue with the um the the [18:52] action, the template action to add PR, [18:56] your PR to this community contribution [18:58] stock. Just so you know, you can still [19:01] fill out the PR. There's no problem [19:03] there. Um the issue template was mainly [19:05] just to streamline that process and make [19:07] it a little easier for folks who are not [19:09] as familiar with the PR uh workflow. Um [19:12] that is not so that that is not working [19:14] right now. Um we are troubleshooting it. [19:17] Sean knows about it. He's the one who [19:18] wrote the thing. So he knows about it. [19:21] He's looking at it. Um we'll get it [19:23] fixed as soon as we can. But yeah, in [19:24] the meantime, you can still submit a PR [19:27] to the community contributions file just [19:30] straight straight through that. Um, we [19:33] did set up a Slack channel to answer any [19:35] questions. It is just election-help. [19:40] Um, and the reason I'm in there is [19:42] because I'm one of the officers. Emma [19:44] Irwin is one of the officers and Ally [19:46] from Red Hat, the uh, Kative community [19:49] is also one of the election officers. [19:51] So, feel free to pop in there and ask [19:53] any questions and we will answer them to [19:55] the best of our ability. Um, we are [19:57] making progress and we should be [19:59] announcing the actual timeline of when [20:02] things are opening pretty soon. Um, I [20:05] don't know that off the top of my head. [20:06] Um, but I think we're getting closer to [20:09] that point. So, yeah. So, keep an eye [20:12] out for that. Um, make sure you're if [20:15] you do want to vote or if you do want to [20:16] run for the board, um, just make sure [20:18] that your name it shows up in GitHub [20:21] some somewhere in chaos. uh or the [20:24] badging organization as well is included [20:26] in that. So [20:29] happy to answer any questions um if [20:32] anybody has any right now. I'm super [20:34] happy to [20:44] Okay, it doesn't sound like we have any, [20:46] but if you do, just pop into that Slack [20:48] channel and ask and we'll be happy to [20:50] help. It's kind of the first it's the [20:53] first time for all of us. So, it's a [20:55] learning opportunity and a learning [20:56] experience for everybody. Um, but yeah, [20:58] we appreciate your patience as we kind [21:00] of sort it out. It will be managed by a [21:03] platform called Electto, which other [21:05] open source projects use for things like [21:07] this. Um, I'm not sure if it's open [21:09] source itself, but it um it's a great uh [21:12] it's a great platform. You will need a [21:15] GitHub account though to vote um and to [21:19] I believe and to mark yourself eligible [21:21] for candidacy. [21:23] Um but yeah, I know that's a limiting [21:26] factor for some, but that's the way it [21:28] controls um who is allowed to vote and [21:31] who isn't and uh just keeps track of all [21:33] that using your GitHub ID. And so, um, [21:37] yeah, if you don't have a GitHub account [21:40] and you need help with that, you can [21:41] also ask in the election help channel, [21:44] um, I believe we will have a way for you [21:46] to, uh, a form you can fill out, uh, to [21:49] request to be added to the voting uh, [21:52] the voting list, but um, yeah, we don't [21:55] have that available just yet, but yeah. [21:57] Oh, yeah, Don put in a link to the to [21:59] the um the platform if you want. [22:02] >> And it is indeed open source. [22:04] >> Oh, good. There we go. [22:07] Awesomeness all around. [22:10] And we will also, it is going to be a [22:11] ranked voting so you can, you know, rank [22:14] people one, two, three. Uh, and we will [22:17] also post, if we haven't done that in [22:19] the FAQ yet, um, we'll post the [22:22] algorithm that it uses to determine the [22:24] winners and such. Um, I'm not sure if we [22:27] added that in yet. [22:31] Uh [22:31] >> I think it's mentioned in the election [22:33] mechanics. [22:34] >> This right here. Yeah, this [22:37] >> condorset method. [22:40] Um so if you're curious about how that [22:43] works, you can read all about it. Some [22:45] light reading for you to to do. Uh yeah. [22:53] Any other questions? Other questions? [22:55] Any questions at all about anything [22:58] anybody has? [23:00] I have one though. [23:04] >> So, are candidates going to be [23:06] campaigning? [23:08] >> Oh, um I I don't know. That's a good [23:12] question. I [23:13] >> What was the question? I didn't I didn't [23:15] hear. [23:15] >> Are are candidates going to be [23:17] campaigning? [23:19] >> Uh we haven't really talked about that. [23:22] >> I think No, I think that's in the [23:24] election mechanics [23:26] >> in this mechanics doc. Okay. I think [23:39] >> yeah, maybe not. [23:40] >> So, I think the way that you will quote [23:42] unquote campaign is you you're going to [23:45] if you want to be um a candidate, you [23:48] will fill out a a form that tells all of [23:51] your contributions to the project and of [23:53] course your name. so that that way [23:54] people can see kind of what you're about [23:57] and and who you are if they don't know [23:58] you. So, I think that's probably the [24:00] limit of the campaigning is just to have [24:02] all your stuff in your in your dock. [24:09] Um, if anyone is curious, so as we're [24:11] building these out, you can go to K [24:13] Native and see basically what ours is [24:16] going to look like. I think it's all [24:18] open. Maybe [24:21] we'll see. [24:25] This is kind of what we're modeling ours [24:27] after. So, yeah. And this is all open. [24:29] So, you can just kind of see um you know [24:33] what our docs will potentially look [24:35] like. [24:35] >> Actually, not not the EU doc. That's a [24:37] different thing. [24:38] >> Look at the Sorry. Go back. Go back one [24:40] and go to the [24:41] >> Oh, the regular this one. [24:43] >> The steering committee. [24:44] >> Yeah. [24:44] >> Gotcha. Okay. Thank you, Don. [24:46] >> Yeah. [24:48] >> So, um the candidates are going to be [24:51] like this. So, you'll have this is what [24:54] your file is going to look like. It will [24:55] be um and we're going to have docs that [24:58] explain all this, don't worry. But your [24:59] raw um markdown file will look like this [25:05] as a candidate. [25:08] But yeah, poke around on this um if you [25:11] want to see. And so this is also why it [25:14] works so well with um Alcto and why why [25:17] it can just pull all this from GitHub [25:19] and put it nicely into a nice platform [25:21] that is a little easier to to navigate [25:25] for folks. But but yeah, [25:33] any other questions? That was a great [25:35] question, Eda. [25:39] >> Thank you. [25:41] Yeah, you're welcome. [25:47] Okay, well, let's move on. Um, as we [25:49] mentioned, we're been talking about for [25:51] the last few weeks, we've been talking [25:52] about kind of cycling out some of the [25:55] tasks of the community manager while we [25:57] are still in limbo. That is that is [26:00] true. We're still in limbo. We still [26:01] don't know. Uh hopefully soon. We just [26:04] keep saying that, I know, but it would [26:05] be great if we actually could get some [26:08] information about it. But in the [26:09] meantime, uh this was something that [26:11] came up last time was about the [26:13] uploading of videos to YouTube because [26:17] it is very time consuming and there are [26:20] a lot of meetings now. So it it can get [26:22] it can pile up pretty quickly. So we [26:25] were talking about automatically posting [26:27] something to YouTube. We mentioned the [26:29] fact that we did have a manual kind of [26:32] interjection there. Um, just in case [26:34] someone said something confidential [26:36] about their company or something that [26:38] they just were like, "Oh, I shouldn't [26:39] have said that." If we're recording and [26:41] now it's posted, can we take that out? [26:43] So, we kind of left that manual step in [26:45] there as a as a check. Uh, I think that [26:48] has happened maybe twice, maybe three [26:50] times um in the my entire like six years [26:55] of being here. So it does not happen [26:57] often and it really does make it a lot [27:01] more time consuming. So uh that being [27:04] said there is an option to live stream [27:06] these to YouTube as we're you know as [27:10] we're going through these meetings and [27:11] we can set that listing to private so [27:13] people can't just watch it on YouTube [27:16] which I think is okay because I would [27:19] rather uh people come here than just [27:22] watch it from YouTube. And maybe that's [27:24] a controversial opinion, but I would [27:26] rather them come here and engage instead [27:28] of just watching and then maybe [27:29] commenting on YouTube or something where [27:31] we're not going to really see it. It's [27:32] going to be one more place we have to [27:34] check for comments and things. So, um, [27:36] we can set it to private. Uh, then we [27:38] can just go back. It's already there. We [27:40] can add the the little image that the [27:42] thumbnail at the beginning, give it all [27:44] the add it to the right playlist, give [27:46] it the metadata, whatever else is there. [27:48] Um, and then then it's but the files [27:51] themselves are already there which is [27:52] really the the the most time consuming [27:56] part of the process. [27:59] >> I think it should also be possible to [28:01] set the turn the comments off if we [28:02] would like to do that too. [28:04] >> We could. Yeah, we could. [28:12] Um, yeah, we also talked about building [28:14] a bot to kind of handle those reminders. [28:18] um which we still could look at doing [28:20] for sure. Um and facilitating that time [28:22] delay. I I have I read on Zoom there is [28:26] a 30 second time delay of going from [28:30] Zoom to YouTube. So I guess that does [28:32] give you a chance to you know cut out [28:35] any inappropriate language or whatever [28:37] else. It's only 30 seconds. [28:40] >> I think that's more when it's live. like [28:42] the live on YouTube will probably [28:44] delayed because YouTube's probably got [28:46] to process it three different ways and [28:48] whatever due to automatic captions and [28:49] all that [28:50] >> copyright stuff and all that. Yeah. [28:52] >> So, um so that is but you know since [28:56] it's set to private if we do if we do [28:58] decide to leave it at private then the [29:00] only people who would have seen that [29:01] were the people in the meeting and they [29:04] would already have seen that. So so [29:06] nobody will have seen it yet. Um, [29:09] I don't know, whatever we think. And we [29:11] do still need to kind of go back in and, [29:13] um, you know, assign it to a playlist, [29:16] put that image in and put the [29:18] description and all that stuff. Um, I [29:20] don't think there is an automated way to [29:22] do all of that. I think I think you have [29:24] to do that manually through YouTube. [29:26] >> I know having run the live stream for [29:28] Chaos Con, like you can set a lot of [29:31] that up in advance. like you could have [29:32] a pres. I don't know how Zoom would work [29:35] with it if it's like a pres-scheduled [29:37] stream. Um [29:40] maybe there's a way for to maybe Zoom [29:42] will just populate it with the meeting [29:44] name and description by default. I'd [29:46] have to look into how that specific [29:48] works, but anyway. Yeah, I think you [29:50] have to have it scheduled and um so [29:53] right now they all show up as just uh [29:55] chaos communities personal meeting or [29:58] whatever it is because we just use the [29:59] link, you know, we don't have these [30:01] meetings actually scheduled through Zoom [30:03] there except for the the offset ones. So [30:06] if there's a conflict then those those [30:08] conflicting meetings do get scheduled [30:10] inside of Zoom so we can give them [30:11] another link but everybody else just has [30:14] the regular link and so they're not [30:16] scheduled. Um, but you know, to your [30:19] point, if we did that, they would at [30:21] least have the the name in there, which [30:23] would be helpful for sure. [30:28] So, just something to think about. I [30:30] just kind of wanted to see like what do [30:31] we think about this? Do do we is are [30:34] there any issues with doing this? Does [30:36] anybody see any any problems [30:39] with that [30:42] that I'm not seeing? [30:50] It does sound like it would be easier [30:51] and I'm all for making it easier so that [30:53] we can get the recordings up earlier. [30:56] >> Yeah. [31:01] >> All right. Well, uh let's I will I will [31:04] post this to the working group leader [31:06] channel just to get their feedback as [31:08] well. Uh, and if um I don't know if we [31:11] want to make this a a communitywide [31:14] thing. I think that would be great if we [31:15] did, but I will also bring this up with [31:17] the working group leaders and just to [31:19] get their their feeling [31:22] about it if they like if you know if [31:24] somebody has strong feelings against it, [31:25] that's totally fine. We can sort that [31:27] out. But let me just drop that in here. [31:43] Okay. [31:47] Do you all think this is something we [31:48] should post in general, too, or do you [31:50] think it's just not that deep? [32:00] Okay, I guess it's not that deep. So, so [32:02] I'm not going to do that. [32:05] Cool. Okay. [32:07] I'm good at not doing things. This is [32:09] That's perfect for me. That's great. [32:12] All right. Um Okay. Uh anything else [32:16] that we skipped? We didn't talk about. [32:28] All right. Your last reminder is all [32:32] things open which is a great conference. [32:34] CFP deadline is March 31st. That's [32:36] coming up very soon. So if you do want [32:38] to submit something, you should do that [32:40] sooner than later. Um it is really great [32:42] conference. I love that conference a [32:43] lot. [32:52] All right. Unless anybody has anything [32:54] else, then I think we're good to go. [33:01] Okay, I see you later everybody. [33:05] Bye.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, March 24 2026.md|CHAOSS Weekly Community Call, March 24 2026 by YouTube]] ## Highlights - working group to write out a little thing or something, point us to something so we have a little more information about it. um because that looks interesting and I would like to hear more unless anybody on this call knows anything about it. No, I don't think they do. Okay. So, we'll just leave it at that. Um ([View Highlight](https://read.readwise.io/read/01kpb5gtgx0dm3qxw7asab94r9)) - Tags: 👻 ai highlighted - think that's a good idea. We can certainly try that as well. Um I don't know that they'll not come back, but >> yeah, I think it just means it'll not be there for this meeting. >> Yeah. Yeah. So yeah, in answer to your question, no, they're just going to keep coming in droves. I I report them every time as spam every time I fill those out. So, you know, my hope is that eventually Zoom will get tired of people doing that and give us ([View Highlight](https://read.readwise.io/read/01kpb5gtj46xm0e4dmpnbdj28w)) - Tags: 👻 ai highlighted - Anyho, um, okay, who put this on here? Data Science Working Group. I'm guessing Don or Cali. >> That was me. >> It was Adrian. >> I I sort of I think that was kind of I I forget exactly what the origin of that conversation was, but it did come up in the data science working group meeting that just happened. And I think it kind of the feedback was This is more of a community level conversation. Okay. >> I think the the idea was just like I think GitHub's website's been >> not the most reliable in over the last month or so. Um ([View Highlight](https://read.readwise.io/read/01kpb5gtjsvbmnrjhp6hdt3bd9)) - Tags: 👻 ai highlighted - just so you you can explain kind of why and what and someone's in the meeting link. You mean this you here we go. Hey Adrian, I'll kind of leave that to you to facilitate. It's like to leave that conversation. ([View Highlight](https://read.readwise.io/read/01kpb5gtkga8qj85873tfsfkvt)) - Tags: 👻 ai highlighted - >> but >> I think we should move on because somehow this one got added above some of the other agenda items that are also I think pretty important for us to cover today. >> Okay. >> Oh, it looked like they they just were copied from last week. So, I I didn't know if that was intentional or not. So, sorry for >> Oh, no, you're good. No, it's fine. It's fine. Um, just a reminder about the uh survey that the AI alignment working group has put out. I don't know what the date is that they're ending that. So, go uh fill ([View Highlight](https://read.readwise.io/read/01kpb5gtmkcs2fwq01yh5sa4w1)) - Tags: 👻 ai highlighted - things are opening pretty soon. Um, I don't know that off the top of my head. Um, but I think we're getting closer to that point. So, yeah. So, keep an eye out for that. Um, make sure you're if you do want to vote or if you do want to run for the board, um, just make sure that your name it shows up in GitHub some somewhere in chaos. uh or the badging organization as well is included in that. So happy to answer any questions um if ([View Highlight](https://read.readwise.io/read/01kpb5gtqrtzkfrncm6xfcwvzk)) - Tags: 👻 ai highlighted