CHAOSS Weekly Community Call, April 7 2026

CHAOSS Weekly Community Call, April 7 2026 ![rw-book-cover](https://img.youtube.com/vi/tlcanvZfQ40/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, April 7 2026](https://www.youtube.com/watch?v=tlcanvZfQ40) > [!note]+ Document Notes > tags: #chaoss #open-source #governance #community #elections > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=tlcanvZfQ40 > date created: 2024-12-19 17:30 > > # 🏷️ Title: CHAOSS Weekly Community Call, April 7 2026 >  ## 🧰 Action Inbox - [H1] Coordinate board election nomination process — nominations delayed 1-2 weeks #elections - [H2] Investigate Zulip migration options and infrastructure funding — Slack costs $2,400/month #infrastructure - [H3] Review and update outdated metrics content — broken links and relevance #documentation ## 🧭 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](https://chaoss.community) - [Election Help Slack Channel](https://chaoss-workspace.slack.com) ## 📝 Summary - CHAOSS community held weekly call discussing board elections, infrastructure challenges, and metrics maintenance - Board elections delayed 1-2 weeks while officers finalize nomination guides and processes - Community exploring alternatives to expensive Slack ($2,400/month) including Zulip and infrastructure funding models - Metrics content needs review for broken links and outdated information - Key stakeholders include election officers, community members, and Linux Foundation ## 📖 Main Content The CHAOSS community is navigating several operational challenges while maintaining momentum on core initiatives. The board election process, originally scheduled to open nominations April 15th, faces a 1-2 week delay as officers develop comprehensive guides and resolve procedural details following recent organizational changes. Infrastructure costs present a significant challenge, with Slack expenses reaching $2,400 monthly and potential reduction to free tier limiting message history to 90 days. The community is exploring Zulip migration and innovative funding approaches through dedicated infrastructure funds via Open Collective. The metrics documentation requires systematic review for accuracy and relevance, with broken links and outdated content identified across the website. This maintenance work could align with broader website migration efforts away from WordPress toward static site generation. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/tlcanvZfQ40?t=0) — [H1] Opening and community guidelines - Key idea: Weekly call operates under CHAOSS code of conduct - Evidence: "interactions is under the chaos code of conduct. So be kind and respectful" #### ⏱️ [02:15](https://youtu.be/tlcanvZfQ40?t=135) — [H1] Election timeline update from officers - Key idea: Board elections delayed 1-2 weeks for proper preparation - Evidence: "original timeline was April 15th to open start opening the nominations... that's going to probably be pushed back maybe one or two weeks" #### ⏱️ [04:30](https://youtu.be/tlcanvZfQ40?t=270) — [H2] Eligibility requirements clarification - Key idea: One year of activity required for voting and candidacy - Evidence: "we pulled activity from the past year... someone has to be active in order to be eligible to run as a candidate or vote" #### ⏱️ [06:45](https://youtu.be/tlcanvZfQ40?t=405) — [H2] Non-PR contribution tracking system - Key idea: Contributors without GitHub PRs need to use special issue system - Evidence: "making sure that folks who are not contributing with PRs to add their name to the using that issue in the community repo" #### ⏱️ [08:00](https://youtu.be/tlcanvZfQ40?t=480) — [H1] WordPress migration proposal discussion - Key idea: Adrian investigating static site generator with Decap CMS - Evidence: "I'll probably see if I can just build a demo just on my like personal GitHub just to kind of see can we can we get the static site generator" #### ⏱️ [12:30](https://youtu.be/tlcanvZfQ40?t=750) — [H1] Slack infrastructure crisis revealed - Key idea: Slack costs $2,400 monthly with potential downgrade to free tier - Evidence: "dropping to the Slack free tier like message history is going to be limited to 90 days" #### ⏱️ [15:20](https://youtu.be/tlcanvZfQ40?t=920) — [H2] Zulip alternative exploration - Key idea: Open source chat platform could reduce costs while maintaining functionality - Evidence: "would the community be interested in moving to something like a Zulip or another sort of more open-source alternative" #### ⏱️ [18:45](https://youtu.be/tlcanvZfQ40?t=1125) — [H2] Infrastructure funding model proposal - Key idea: Open Collective subfund could support community infrastructure costs - Evidence: "community infrastructure fund... people who are working full-time or deriving a lot of their income from directly from their work on chaos, providing them a way to give back" #### ⏱️ [22:10](https://youtu.be/tlcanvZfQ40?t=1330) — [H3] Linux Foundation support inquiry - Key idea: Elizabeth exploring LF funding for Slack similar to Zoom arrangement - Evidence: "they take care of our Zoom account... it would be really great if we could also have them pay for our Slack" #### ⏱️ [26:30](https://youtu.be/tlcanvZfQ40?t=1590) — [H2] Migration technical feasibility - Key idea: Zulip supports Slack import with export capabilities available - Evidence: "Zulip does allow you to import from Slack... several of the people with elevated access to Slack are able to export at least public messages" #### ⏱️ [29:15](https://youtu.be/tlcanvZfQ40?t=1755) — [H3] Metrics maintenance issue identified - Key idea: CHAOSS metrics contain broken links and need content review - Evidence: "open demographic question cited in the in this particular metric... the link is broken. It throws a four for error" #### ⏱️ [32:00](https://youtu.be/tlcanvZfQ40?t=1920) — [H3] Systematic content review proposal - Key idea: Metrics require comprehensive review for relevance and accuracy - Evidence: "these metrics have been created for a while now and I wonder if we've had the time to actually go back to look into them" #### ⏱️ [35:30](https://youtu.be/tlcanvZfQ40?t=2130) — [H3] Automated link checking suggestion - Key idea: Static site generation could include automated link validation - Evidence: "plugins or GitHub actions... that can like scan your generated website for links and check to make sure they're all not for4ing" #### ⏱️ [38:20](https://youtu.be/tlcanvZfQ40?t=2300) — [H3] Meeting facilitation volunteer call - Key idea: Community needs volunteers for weekly meeting facilitation - Evidence: "calling for volunteers to help facilitate the the weekly meetings like this meetings... there's this sheet that Elizabeth put together" #### ⏱️ [40:45](https://youtu.be/tlcanvZfQ40?t=2445) — [H3] Education working group updates - Key idea: New courses available from CHAOSS education initiative - Evidence: "new courses from the chaos education working group... part two of the future of open source" ## 📚 References - [CHAOSS Community Repository](https://github.com/chaoss/community) - [Election Help Slack Channel](https://chaoss-workspace.slack.com/channels/election-help) - [Open Collective Platform](https://opencollective.com/) - [Zulip Chat Platform](https://zulip.com/) ## 🗣️ Paraphrase - CHAOSS board elections face 1-2 week delay as officers prepare comprehensive guides and resolve procedural issues following organizational changes - Community confronts $2,400 monthly Slack costs and explores Zulip migration with innovative infrastructure funding through Open Collective subfunds - Metrics documentation requires systematic review for broken links, outdated content, and overall relevance as part of broader website maintenance efforts ## 📰 Newsletter The CHAOSS community continues adapting to recent changes while maintaining forward momentum on governance and infrastructure improvements. Board elections, though delayed, demonstrate thoughtful preparation with comprehensive candidate and voter guides in development. The community's proactive approach to infrastructure sustainability through proposed Open Collective funding models offers valuable lessons for open source organizations facing similar cost pressures. The exploration of Zulip alternatives, combined with systematic metrics maintenance, shows commitment to long-term community health. Resources: [CHAOSS Community](https://chaoss.community/), [Open Source Metrics](https://github.com/chaoss/metrics), [Community Handbook](https://handbook.chaoss.community/) ## ✅ Action Items #### Community - Maintainers: finalize election timeline and nomination guides within 1-2 weeks - Contributors: submit non-PR contributions via community repository issue system - Sponsors: evaluate Open Collective infrastructure fund participation levels #### OSPO - Policy & Governance: review election procedures and community contribution tracking - Community Engagement: coordinate Linux Foundation infrastructure support discussions - Strategic Alignment: assess infrastructure costs against community sustainability metrics ## 🧪 Hypotheses - Open Collective infrastructure funding can provide sustainable community platform support - Zulip migration would maintain community engagement while reducing operational costs - Systematic metrics review will improve documentation quality and user experience - Static site generation will enable automated content validation and maintenance ### 📊 Methodology - Survey community members on infrastructure funding willingness and capacity - Compare Zulip vs Slack feature sets and migration complexity - Audit all metrics documentation for broken links and outdated content - Test static site generators with automated link checking capabilities ### ❓ Questions - How can open source communities sustainably fund infrastructure without corporate dependency? - What governance changes are needed when communities face sudden operational disruptions? - How do platform migrations affect community participation and engagement levels? ### 🔮 Future Research - Impact assessment of chat platform migrations on community health metrics - Comparative analysis of infrastructure funding models across open source organizations - Documentation maintenance automation for community-driven projects ### 💡 Implications - Practice: Infrastructure costs require proactive community funding strategies - Policy: Election procedures need resilience planning for organizational changes - Security: Community data preservation during platform migrations requires careful planning - Education: Volunteer training programs essential for distributed community management - Funding: Open Collective subfunds offer sustainable infrastructure financing models ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade #### 👀 Visual learners - Present: Meeting agenda structure, participant names in chat - Improve: Infrastructure cost breakdown charts, migration timeline diagrams #### 🔊 Aural learners - Present: Full audio recording of community discussion - Improve: Key point timestamps, meeting summary podcast #### 🗣️ Verbal learners - Present: Clear definitions of governance terms, procedural explanations - Improve: Glossary of CHAOSS-specific terminology, analogy-based explanations #### 🧩 Kinesthetic learners - Present: GitHub issue workflow for contributions, hands-on election process - Improve: Step-by-step migration guides, interactive cost calculators #### 🧠 Logical learners - Present: Timeline adjustments, cost-benefit analysis discussion - Improve: Decision trees for platform selection, budget planning worksheets #### 🧑‍🤝‍🧑 Social learners - Present: Community call format, collaborative decision-making - Improve: Working group coordination guides, peer mentorship programs #### 🧘‍♀️ Solitary learners - Present: Individual contribution tracking, self-directed volunteer signup - Improve: Personal reflection prompts on community participation #### 🌿 Naturalistic learners - Present: Open source ecosystem thinking, community sustainability focus - Improve: Infrastructure lifecycle analogies, ecosystem health metrics ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear agenda structure, participant identification - Improve: Structured transcription with speaker labels, topic headings #### Keyboard navigation - Present: Standard video player controls - Improve: Timestamped navigation, keyboard shortcuts for sections #### Contrast and readability - Present: High contrast meeting interface - Improve: Transcript formatting with adequate spacing and typography #### Text resizing and reflow - Present: Scalable video player interface - Improve: Responsive transcript layout supporting 200% zoom #### Media and captions - Present: Full transcript available for audio content - Improve: Real-time captions during live calls, downloadable transcript files #### Forms and interactions - Present: Clear volunteer signup process - Improve: Accessible form validation, error handling for contribution submissions ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community participation, timezone considerations - Improve: Multiple meeting time options, regional coordinator representation #### Inclusive language - Present: Gender-neutral pronouns, professional terminology - Improve: Plain language summaries, jargon definitions for newcomers #### Neurodiversity support - Present: Structured agenda format, predictable meeting rhythm - Improve: Pre-meeting materials, post-call summary documents #### Representation - Present: Diverse community voices in discussion - Improve: Balanced speaking time, rotating facilitation opportunities #### Psychological safety - Present: Code of conduct enforcement, respectful interaction norms - Improve: Clear escalation procedures, community guidelines reinforcement ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Cost analysis linking Slack expenses to sustainability concerns - Inductive strength: Platform migration experience informing decision-making approaches - Causal reasoning: Infrastructure funding models preventing future operational disruptions - Analogical strength: Linux Foundation support model applied to Slack arrangement #### Fallacies - Appeal to novelty: Assuming static site generation automatically improves all website issues - False dilemma: Presenting only Slack vs Zulip without exploring other alternatives #### Tone of voice - Overall tone: Collaborative and problem-solving focused with transparent communication about challenges ### 🛡️ DARVO Analysis - Deny: No evidence of denial or minimization - Attack: No evidence of attacking community members or processes - Reverse victim/offender: No evidence of role reversal tactics - Emotional cues and rhetoric: Professional, collaborative tone focused on constructive problem-solving ## 🎯 Conclusion The CHAOSS community demonstrates resilience and forward-thinking approaches to governance and infrastructure challenges. While board elections face minor delays, the emphasis on comprehensive preparation and community inclusion reflects mature organizational practices. The proactive exploration of sustainable infrastructure funding models and platform alternatives positions the community well for long-term success, offering valuable lessons for other open source organizations navigating similar operational challenges. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Open source communities require sustainable infrastructure funding models > [!quote] [CHAOSS Weekly Community Call, April 7 2026](https://www.youtube.com/watch?v=tlcanvZfQ40) by [[CHAOSS Community]] via [[YouTube]]. Published 2026-04-07. Accessed 2024-12-19. > "Community infrastructure fund... providing them a way to give back and support that infrastructure that often goes unsupported or unrecognized." Demonstrates proactive approach to infrastructure sustainability through community-driven funding rather than corporate dependency. [view highlight](https://youtu.be/tlcanvZfQ40?t=1125#H1) #xref #articleseed ID:rw_CHAOSS001 ### [H2] Platform migration costs extend beyond technical implementation > [!quote] [CHAOSS Weekly Community Call, April 7 2026](https://www.youtube.com/watch?v=tlcanvZfQ40) > "The biggest hurdle with that move is going to be more the social side of how do we get everyone to move along with us." Highlights community adoption challenges as primary barrier to infrastructure changes, not technical feasibility. [view highlight](https://youtu.be --- ## Full Transcript [00:04] Okay, great. Um, hi everyone. Um, I am [00:08] on low bandwidth today, so I wouldn't be [00:11] I'll be showing my face. Sorry about [00:13] that. But yes, u welcome to the chaos [00:17] weekly community call. Um, [00:20] if you're new here, please note that um, [00:23] interactions is under the chaos code of [00:26] conduct. So be kind and respectful when [00:28] you interact with others. Um we have a [00:31] question for today. Um put down your [00:34] name if you want and let us know how you [00:37] spend the holiday. [00:41] Yeah. Okay. So so the first thing on the [00:44] agenda, so this one is from last week. [00:46] Um I know someone had a question around [00:48] um if there is a date yet for candidates [00:51] to share their candidacies. So and [00:54] Elizabeth wanted to check in on that. Um [00:55] it is I didn't know if you got um [00:59] >> um get [01:02] >> Yeah, I can I can answer that. So um the [01:05] election officers, myself, Emma and [01:08] Ally. Okay. From uh the K Native [01:11] community, we um met on Thursday. We [01:16] were not certain if the election would [01:19] need to be temporarily put on hold just [01:23] until you know things kind of get [01:25] resolved uh with recent events. Um so I [01:28] reached out to the board and the general [01:31] sentiment was go ahead with elections as [01:34] planned. Um we are running a little bit [01:36] behind. Uh so my um we just need to [01:40] adjust the timeline. I would say the the [01:42] original timeline was April 15th to open [01:45] start opening the nominations and um [01:49] election uh uh nominations, yeah, I [01:52] guess would be a better word to say it. [01:54] Um but so that's going to probably be [01:56] pushed back maybe one or two weeks. Uh [01:59] there's a few things we need to just a [02:01] few minor details we need to um tie up [02:05] but um yeah so I would say in the next [02:07] probably one to two weeks we'll be [02:10] opening that. Um we are in the process [02:12] of working on guides that will have [02:15] screenshots and everything in there and [02:17] exactly what you need to do if you want [02:19] to be a voter and also exactly what you [02:21] need to do if you want to be a [02:23] candidate. So that's also in progress. [02:25] So we just need to finish that up. type [02:27] a few loose ends um that were hanging [02:29] out there um and then we can [02:32] successfully open the uh the candidacy. [02:36] Um [02:38] yeah, so if anybody has questions on [02:40] that um I'm happy to answer what I can. [02:42] There's also a Slack channel too where [02:44] you can answer or ask questions as well. [02:49] >> Yeah. [02:51] Um [02:53] I'm trying to see if there's if you put [02:55] that in the previous meeting not Oh [02:58] yeah. Um [02:59] >> yeah, it's that election help channel. [03:02] >> Yeah. Yeah. Okay. Election help channel. [03:04] Okay, great. So um yeah, anyone has [03:07] questions for Elizabeth. [03:17] Also, if I can just ask for your help in [03:20] spreading the word about um you know, [03:23] making sure that folks who are not not [03:26] contributing with PRs to add their name [03:30] to the using that issue in the community [03:33] repo. Um if everybody can just kind of [03:35] help us spread the word on that, that [03:36] would be great. And it will take um we [03:40] pulled act uh activity from the past [03:42] year. I think I might have misspoke last [03:44] week on that. it's the past year that [03:46] someone has to be active in order to be [03:48] eligible to run as a candidate or vote. [03:52] So, if you are one of those folks um and [03:55] you have not submitted anything in that [03:58] way in the past year, then you'll need [04:00] to do so. [04:07] >> Great. Um whoever is adding that to the [04:10] to the dock, thank you. [04:12] Um all right, good. any any questions or [04:19] okay great [04:22] um [04:27] so yeah the next is um the proposal to [04:30] move away from WordPress [04:33] um adren you brought this up the last [04:35] time I was wondering if like there is [04:37] any update or totally fine if we have to [04:39] skip it um [04:42] >> I haven't done a ton with it last since [04:45] last week. I think I lightly was [04:47] investigating um trying to just get some [04:50] demo maybe a demo going with with decap. [04:53] Um I hope I didn't accidentally spam any [04:55] of the other owners of to chaos GitHub [04:59] or anything with with [05:01] potentially scary looking like access [05:03] has been granted to things. I think I I [05:04] was trying to see if I could add [05:07] permissions in a very granular way and I [05:09] thought it would give me more options [05:11] when I click the button instead of just [05:12] doing it. So, I ended up I'm I'm just [05:14] going to build it per I'm going to see [05:16] if I get time, which is highly unlikely [05:19] soon. Um, I'll probably see if I can [05:22] just build a demo just on my like [05:23] personal GitHub just to kind of see can [05:26] we can we get the static site generator [05:28] that we were talking about kind of [05:29] working and just see if there's any way [05:31] we can get a proof of concept up just so [05:33] that people have something tangible to [05:34] look at and like hey can we play with [05:37] this and see what people think. Um, [05:40] I'm still I think the the the main point [05:42] of of bringing that up was mostly just [05:44] kind of seeking community involvement um [05:47] and seeking contributors on that because [05:50] I don't know if I have time to [05:51] single-handedly like rewrite or re [05:54] rework the chaos website. Um, but I [05:58] think the and I think there's a couple [06:00] items I added to the agenda a little bit [06:01] below for this week that that I think [06:03] tie into that now [06:05] >> in terms of just generally talking about [06:07] community infrastructure. I don't know [06:08] if that's if people have still questions [06:09] about the website or if we want to [06:11] include those as well. [06:15] >> Yeah. Like I mean you can go on and talk [06:17] about those. Um [06:20] assume you're the one that put them [06:21] here. The commit infrastructure, right? [06:23] >> Yeah. And and the Zulip thing. I I just [06:25] I noticed um I think it was Elizabeth's [06:28] announcement about on Slack the other [06:30] day as far as like hey, we're dropping [06:31] to the Slack free tier like message [06:34] history is going to be limited to 90 [06:36] days and things. Um, I was just kind of [06:38] throwing around ideas for how like could [06:40] like would the community be interested [06:42] in moving to something like a Zulip or [06:44] another sort of more open- source [06:46] alternative that maybe gives us more [06:47] options to self-host or something like [06:49] that. Um, and along along with the kind [06:52] of thoughts about self-hosting and [06:54] things, um, I I figured it might be [06:58] interesting to potentially look at like [07:00] could we create uh maybe like a [07:02] community infrastructure fund or [07:03] something some kind of like cuz I know [07:05] um there's other organizations I'm in [07:07] that that use Open Collective and [07:10] they've they've been able to do sort of [07:12] sub initiatives like in terms of like [07:14] making like a fundraising pool [07:16] essentially like hey we're holding this [07:17] this community dinner like the community [07:20] is paying for the dinner contribute [07:23] suggested amount to this like as [07:25] alongside your RSVP um kind of thing. So [07:28] I almost wonder if we could do something [07:29] similar to that in the chaos um open [07:32] collective and say hey here's an [07:33] infrastructure fund like obviously try [07:36] and pursue like using Zulip's uh [07:38] offerings that that for open source [07:40] projects that that let us use it for [07:42] free but even if we're getting the [07:44] infrastructure for free I think it would [07:46] be still helpful to kind of start [07:48] building a dedicated fund where people [07:51] who like especially me members of chaos [07:53] who are working full-time or deriving a [07:55] lot of their income from indirect [07:57] directly from their work on chaos, [07:59] providing them a way to give back and [08:01] support that infrastructure that often [08:03] goes unsupported or un unrecognized, but [08:06] it's like could be very disruptive if we [08:08] like lost our Slack history or something [08:10] like that. Um, so I just I was kind of [08:14] throwing a lot of that out there as [08:15] like, hey, maybe this could be sort of a [08:18] if if we somehow in the future [08:21] need to start paying for Zulip or paying [08:23] to renew a domain name or something. [08:25] there's there's already money there and [08:27] it doesn't become an immediate panic for [08:29] the community and we we have a like a [08:32] few months of runway to to find new [08:35] sources of of funding and things like [08:37] that. [08:38] So that that was just kind of the [08:40] general general vibe of a lot of those [08:42] suggestions kind of together because I [08:44] think um there's been a lot of thoughts [08:47] about community infrastructure lately. [08:53] >> Yeah. Um, I'll be curious to know what [08:56] what people think about what Adrian is [08:59] currently sharing. [09:09] >> Yeah, sure. [09:13] Um I so to your point about the subf [09:16] fund that is definitely something that [09:19] can be set up in open collective uh for [09:22] directed funding like that. We certainly [09:25] could do that. Um I don't and I think I [09:28] would love to see that. The only [09:30] challenge I see is that right now I [09:32] think our Slack I'm under the impression [09:34] that our Slack is about $2,400 a month [09:38] to fund, which is not a trivial amount [09:41] really. Uh so that would be my only uh [09:45] challenge is is would we get enough to [09:47] fund the Slack? Um but to your point [09:49] like if it could be used to fund other [09:51] things like our domain name or um I'm [09:54] not sure about Zulip how much that costs [09:55] or anything. Um then yeah, I mean I [09:59] think that's a great idea. [10:01] >> I think my intention more with the [10:03] infrastructure fund was less directly [10:06] trying to to fund Slack cuz that that [10:09] that is a lot more money than I thought [10:10] it would be. I think I was thinking of [10:13] it more in terms of like a complement [10:14] like like not necessarily mandatory but [10:17] like a a forwardthinking add-on to like [10:20] if we if we were to step into Zulip and [10:22] and utilize some donated infrastructure [10:24] from them in terms of like hey we're an [10:27] open source community can we utilize [10:29] their their sort of free policy for [10:32] getting a paid plan for free as as an [10:34] open source community if we step into [10:36] that like I I think just because we get [10:39] that infrastructure for free doesn't [10:41] mean we should necessarily treat it as [10:42] free. And I think if we kind of you have [10:47] bring up that fund at the same time, we [10:50] could kind of have like I know I would [10:52] probably personally be be willing to [10:54] donate a couple dozen dollars a month or [10:56] something to that. And it just use it as [10:58] kind of a way that like, okay, as long [10:59] as we're on Zulip, like the cost is [11:01] zero, but we're still building this fund [11:04] so that yeah, maybe maybe we're not able [11:05] to fund raise enough to do $2,400 a [11:09] month, but it's still maybe 20, 50, 100 [11:13] bucks a month from several people and [11:16] that can just accumulate as and we can [11:18] kind of live on Zulip as long as we can, [11:21] but then there's still there's there [11:22] then becomes a healthy like the longer [11:24] we we keep that going, the healthier [11:27] fund we have so that if we do need to [11:29] like buy infrastructure to self-host [11:31] Zulip or [11:33] increase our plan or something else, [11:36] there's enough money there that it sort [11:38] of it becomes more of a like what which [11:41] option do we want to do? Which one's [11:42] most economical rather than like crap, [11:46] how do we find this money? Um, so I was [11:49] just I was thinking out of it as more as [11:50] like a future cushion of like even if we [11:53] like let's try and step to something [11:55] that is going to be cheap a lot cheaper [11:57] for us than than $2,400 a month but also [12:01] if we get something for free let's not [12:03] treat it as free so that we can build [12:05] ourselves a cushion. [12:08] >> Yeah, if I understood correctly um the [12:13] the open funding you're proposing would [12:15] be for Zulip, right? um if we decide to [12:17] like move to Julie is is that correct? [12:21] Like just sustaining like the paid [12:24] domain that we'll be using to like host [12:26] that particular platform. [12:28] >> So the the I'm I'm calling it an [12:30] infrastructure fund because I don't [12:32] think it would be limited to Zulip. I [12:33] think there's a lot like Cali is saying [12:35] in the chat, I think there's a lot more [12:37] aspects of chaos that fall under [12:39] infrastructure that I think could also [12:41] make use of that money. I I don't want [12:43] to like h get create the cushion and [12:45] then immediately spend it all but like [12:47] having the money there so that like hey [12:50] crap this domain needs renew like our [12:52] chaos community needs renewing or that's [12:54] managed by LF but like if we have [12:57] important things we need to run like hey [12:59] maybe we want an account so we can [13:01] host several different things all in one [13:05] in one thing. um or whatever like [13:08] whatever whatever infrastructury things [13:10] come up like we can maybe vote on it as [13:12] a community or something and and have [13:15] the money there to support those kinds [13:16] of critical project sustaining things. [13:22] >> Yeah. Yeah. I mean with the recent [13:24] events um going on I I think um it would [13:29] make sense to assume that a lot of this [13:31] um this um um issues might arise in the [13:35] future. would need this fund to help [13:38] solve um solve them, right? Um so yeah, [13:43] that makes sense. But um specifically to [13:46] Julie, I I see Elizabeth mentioned that [13:50] we might be able to still keep Slack um [13:53] since like we are a part of LF the Lenox [13:57] Foundation and um [14:00] she's waiting to like hear back from um [14:04] from the Leen, right? Um Elizabeth is [14:08] >> Yeah. [14:08] >> So um [14:10] >> so we'll see what that what comes of [14:12] that. Um, I had not heard about that. [14:14] Um, so we'll see. We'll see if I get a [14:18] response um, relatively soon. Um, yeah, [14:22] that would be the best in my opinion, [14:23] that would be the best case scenario [14:25] that, you know, they just take care of [14:27] it and then we just can use it. Um, and [14:29] that's what we they do for our Zoom [14:31] account for anybody who doesn't know [14:32] like that that's paid for by the LF. So, [14:35] it would be really great if we could [14:37] also have them pay for our Slack. But um [14:40] yeah, I'll definitely let you know and [14:41] if I don't hear anything by tomorrow, [14:42] I'll ping her again. Um and then if I [14:45] still don't hear back, uh then we'll [14:47] figure out what to do, I guess. [14:49] >> But I think I think in general, I think [14:50] this is this is a weird combination of [14:52] of concerns cuz it's like I think even [14:55] if we do like I I would obviously agree [14:57] like if we can get LF to to adopt our [14:58] Slack, that would be the best outcome [15:01] because then that's sustainable into [15:03] forever. Um I I think even then though I [15:07] think it might still be worth maybe [15:08] maybe not as immediately but eventually [15:10] talking about some kind of community [15:11] like funding for for like like I said [15:13] Cali had other concern like other places [15:16] and I think building up that cushion is [15:18] just generally going to be something [15:19] that's going to help like [15:21] like especially just even evaluating the [15:23] appetite like how many people actually [15:25] do end up contributing to this before we [15:27] need it, right? like and then maybe that [15:29] helps us forecast like okay what what [15:31] can we do with this and still kind of [15:33] keep a healthy safety cushion. [15:36] >> Yeah, 100% agree. [15:45] >> Okay. Um I mean migrating to a new [15:47] platform is definitely not going to be [15:50] easy, right? Um especially with the fact [15:52] that we've we've tried this in the past [15:54] and it sort of like did not work. I I [15:56] believe was the discourse [15:58] um um some some years back. So um yeah [16:04] um [16:07] yeah discourse yeah [16:09] >> discourse I think is it's not [16:11] necessarily a chat platform I think [16:13] >> in terms of technically I think my like [16:15] Zulip does allow you to import from [16:17] Slack and I [16:19] >> I know me and several of the people with [16:21] with elevated access to Slack are able [16:24] to export at least public messages to [16:26] import. So, I think that the biggest [16:28] hurdle with that move is going to be [16:29] more the social side of how do we get [16:32] everyone to move along with us. And I [16:33] think if if we are indeed going to be [16:37] limited like if Slack if we have to drop [16:39] down to the free tier of Slack and lose [16:41] message history, that's a pretty strong [16:43] push away from Slack um for potentially [16:46] a lot of people. So, I don't I don't I [16:48] definitely think if we can avoid having [16:50] to move to Zulip or anything else, [16:52] that's ideal. But I think if if the move [16:55] is if we're kind of forced into moving [16:58] or losing message history, it it's at [17:00] least a slightly less high friction [17:02] option. [17:08] Yeah. [17:11] Okay. Does anyone have any comments on [17:14] this? Um any other thoughts? [17:19] I I don't know what what the next step [17:21] might look like. Maybe we'll wait to [17:23] hear back from the LF first. Um cuz I [17:26] think that's the the the infrastructure [17:28] bit that we probably need to to sort out [17:31] now, like right now. Then yeah, when we [17:34] get to hear from them or not hear from [17:36] them, don't probably like um cycle back [17:38] to that conversation. [17:43] Okay. [17:45] Um, [17:47] right. Since we're not having any [17:49] comments, uh, the next one here is the [17:52] chaos metrics. [17:54] Um, so this one was me. I was I don't I [17:58] can't remember why I, um, what I was [18:00] looking through, but I noticed that [18:02] there was a open demographic question [18:05] cited in the in this particular metric [18:07] and um, [18:09] um, it's the the link is broken. It [18:13] throws a four for error. Let's see. [18:16] Share my screen here. [18:19] I think it's somewhere here. All right. [18:22] Yeah, this question here. [18:25] Um, [18:27] yeah. So, I was just generally thinking, [18:30] so it just got me thinking about um a [18:32] lot of our metrics um and the content on [18:36] on the website currently. Um, and I was [18:40] wondering like if people [18:44] see or think that some of those texts [18:47] need updating [18:49] uh or need some review and um how might [18:53] we go about that? Um I know there's some [18:57] there's a conversation around that going [18:58] on in the DI working group um around [19:02] updating some of the metric specifically [19:04] to the event budget but I was wondering [19:06] if it's something we we want to look [19:08] into [19:10] um generally in the community like [19:13] pretty much maintaining I think this [19:15] these metrics have been created for a [19:17] while now and I wonder if we've had the [19:20] time to actually go back to look into [19:22] them and see if um they are all still [19:25] relevant, but also like um if the [19:30] um yeah, if if they need updating, [19:34] that makes sense. [19:37] So, this this is an open conversation um [19:40] to everyone. [19:45] >> That link works on my machine. [19:48] Those now touch. [19:56] >> Yeah. [19:58] Is this true for area? Could it be [20:00] location 10? [20:03] It might be. Um I don't know how [20:07] I' I don't remember the exact name of [20:10] the hosting provider that we are using [20:11] for WordPress. I believe that goes [20:13] through I think Shan is the primary one [20:15] with access to that. I think I've heard [20:17] and some other people have also access. [20:21] I don't know what the policies of that [20:23] provider are in terms of [20:26] >> like geo restrictions or anything. Um, [20:30] if I send a link to a different metric [20:32] in the Zoom chat, do you want to try [20:34] clicking on that to see if that also [20:36] 404s? [20:42] Okay. So that [20:46] >> yeah like oh I okay I think you [20:48] misunderstood what I said. I I meant [20:50] like the the um open demographic [20:54] question that was cited in the metric [20:56] not like not the metric um page itself. [21:01] Um [21:02] >> oh the the first link within it. [21:05] >> Yeah. [21:08] >> Oh no. Oh, I I [21:11] >> Yeah. No, I see I see the 404 now. Yeah. [21:13] Okay. I was just using the wrong link. [21:16] >> Okay. [21:18] Okay. [21:20] Yeah. Like I was just thinking generally [21:23] um [21:25] if a lot of this metrics needs like do [21:27] we need to go over them to really um [21:32] um see if they need updating, right? If [21:36] they're still relevant. [21:38] Um yeah, that's taking away sound like a [21:41] lot of work. Now [21:42] >> I think that's worth doing. I mean it [21:44] does sound like a lot of work. I think I [21:46] have seen in the sort of more static [21:48] site generation realm like I've seen [21:51] various plugins or GitHub actions and [21:53] things that can like scan your generated [21:56] website for links and check to make sure [22:00] they're all not for4ing and stuff and [22:03] like fail your build if they're four or [22:04] fours or whatever. Um, so I I [22:07] potentially see that as another [22:09] potential way that we could we could [22:10] benefit from starting to shift over to [22:13] um a more statically built website. I [22:17] don't know when or how fast that's [22:20] likely to actually happen, but I imagine [22:23] I imagine being a like doing just sort [22:25] of holistic content reviews might become [22:28] >> a natural part of of that migration. As [22:30] we kind of pull pages over one at a [22:32] time, we can just review them as they [22:34] get migrated. like, okay, this is still [22:36] accurate. [22:37] >> Yeah. [22:40] Yeah, of course. That makes sense. [22:44] Yeah, that makes sense. Like do both [22:46] work at the same time. And um yeah, [22:51] I don't know what what do other people [22:52] think. Any thoughts on this? [23:06] Okay. [23:08] Um [23:12] All right. Um if folks don't have any [23:15] thoughts or [23:17] um comments on that then um [23:24] and yeah I think that's all all on the [23:27] agenda today except anyone wants to talk [23:30] about anything else. [23:40] Okay. Um yeah, so we have a couple of [23:43] reminders. Um the [23:46] the first one is the [23:49] we we're calling for volunteers to help [23:51] facilitate the the weekly meetings like [23:55] this meetings. It happens weekly every [23:57] other Tuesday. So, um there's this this [24:00] sheet that Elizabeth put together that [24:02] you can, you know, put down your name. [24:04] Um if you're open to [24:07] to um contribute in in that regard, then [24:11] there is a guide for how to facilitate [24:14] these meetings. So, um like if you if [24:18] this is your first time doing something [24:20] similar, then yeah, we got you. Then, of [24:24] course, the chaos board election is [24:26] coming. Um as mentioned earlier, please [24:29] help like um spread the word especially [24:32] for people who are making contributions [24:35] that don't show up on GitHub like as a [24:38] PR, right? Um they should use this issue [24:43] um for nonpr contributions. Um yeah. [24:49] Um [24:52] sorry. [24:54] Okay. Then of course um new courses from [24:58] the chaos education working group [25:02] um if you like to take a look or also [25:04] contribute to the part two of the future [25:07] of open source and you can check that [25:09] out by visiting the GitHub repository [25:13] and um I'm asking the maintainer to [25:16] assign that to you. Yeah, I guess that's [25:18] how it works. [25:21] Um [25:23] yeah, so that's that's all for today's [25:26] meeting. [25:28] Was nice. [25:33] Oh, hi Joy. Um yeah, that's um [25:38] let me quickly refresh that link. Um [25:45] yeah, okay. So this is a spreadsheet [25:48] that you can add your name to [25:51] um volunteer to facilitate the next um [25:56] weekly meetings. [25:58] So yeah, you're welcome. [26:03] Okay. All right, friends. Um that's all. [26:05] I will stop recording. [26:09] >> Thanks everybody. Thanks for  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, April 7 2026.md|CHAOSS Weekly Community Call, April 7 2026 by YouTube]] ## Highlights - day as far as like hey, we're dropping to the Slack free tier like message history is going to be limited to 90 days and things. Um, I was just kind of throwing around ideas for how like could like would the community be interested in moving to something like a Zulip or another sort of more open- source alternative that maybe gives us more options to self-host or something like that. Um, and along along with the kind of thoughts about self-hosting and things, um, I I figured it might be interesting to potentially look at like ([View Highlight](https://read.readwise.io/read/01kpb5xqxeqnr27q0ej6ccp7qj)) - Tags: 👻 ai highlighted - challenge I see is that right now I think our Slack I'm under the impression that our Slack is about $2,400 a month to fund, which is not a trivial amount really. Uh so that would be my only uh challenge is is would we get enough to fund the Slack? Um but to your point like if it could be used to fund other things like our domain name or um I'm not sure about Zulip how much that costs or anything. Um then yeah, I mean I think that's a great idea. ([View Highlight](https://read.readwise.io/read/01kpb5xqy7nx3r8j5qtkt6bbs6)) - Tags: 👻 ai highlighted - they're all not for4ing and stuff and like fail your build if they're four or fours or whatever. Um, so I I potentially see that as another potential way that we could we could benefit from starting to shift over to um a more statically built website. I don't know when or how fast that's likely to actually happen, but I imagine I imagine being a like doing just sort of holistic content reviews might become >> a natural part of of that migration. As ([View Highlight](https://read.readwise.io/read/01kpb5xr263fka4af1h7n79dcr)) - Tags: 👻 ai highlighted - um if you like to take a look or also contribute to the part two of the future of open source and you can check that out by visiting the GitHub repository and um I'm asking the maintainer to assign that to you. Yeah, I guess that's how it works. Um yeah, so that's that's all for today's meeting. Was nice. ([View Highlight](https://read.readwise.io/read/01kpb5xr5a56yfsa38my1k28df)) - Tags: 👻 ai highlighted