CHAOSS Weekly Community Call, March 10, 2026

CHAOSS Weekly Community Call, March 10, 2026 ![rw-book-cover](https://img.youtube.com/vi/gv3pyDqefGE/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, March 10, 2026](https://www.youtube.com/watch?v=gv3pyDqefGE) > [!note]+ Document Notes > tags: #chaos #community #elections #opensource #governance > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=gv3pyDqefGE > date created: 2026-03-10 15:00 > > # 🏷️ Title: CHAOSS Weekly Community Call, March 10, 2026 >  ## 🧰 Action Inbox - [H1] Complete community contributions documentation for board election eligibility — before voting opens #chaos - [H2] Consider volunteering to facilitate weekly community calls — ongoing rotation #community - [H3] Submit conference proposals for Apache COC Glasgow (March 20) and All Things Open (March 31) — approaching deadlines #conferences ## 🧭 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 Board Elections Mechanics](referenced in call) - [Community Contributions Documentation](referenced in call) - [Apache Software Foundation Community Over Code Conference](referenced in call) ## 📝 Summary - What happened: CHAOSS weekly community call covering upcoming board elections, daylight savings time meeting updates, and conference opportunities - Why it matters: First-ever board elections require community understanding of voting eligibility and nomination processes - Key stakeholders: CHAOSS community members, potential board candidates, election officers - Risks and tradeoffs: GitHub account requirement may limit participation; new election process creates learning curve - Bottom line takeaway: Community members need to document contributions and prepare for inaugural board elections ## 📖 Main Content The CHAOSS community is implementing its first-ever board election process, managed by election officers Elizabeth, Emma Irwin, and an officer from the K native community. The election will use Elekto software for nomination and voting management. Key eligibility requirements include documented contributions to CHAOSS (either through GitHub PRs or community contributions documentation) and a GitHub account for voting verification. The election officers are currently testing the software and will release a timeline and multiple communications in coming weeks. The community is also rotating facilitation of weekly calls to distribute community management responsibilities, with Elizabeth facilitating next week's call. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/gv3pyDqefGE?t=0) — [H1] Call opening and facilitation volunteer request - Key idea: Sean opens call and seeks volunteer facilitator for next week - Evidence: "Can I get a volunteer to facilitate next week? kind of looking at the co and Mary blessing maybe" #### ⏱️ [02:15](https://youtu.be/gv3pyDqefGE?t=135) — [H2] Daylight savings time calendar updates - Key idea: CHAOSS calendar updated with daylight savings meeting time changes - Evidence: "The chaos calendar has been updated for meeting times and we are under daylight savings time" #### ⏱️ [03:45](https://youtu.be/gv3pyDqefGE?t=225) — [H1] CHAOSS board elections overview - Key idea: Elizabeth explains election process as election officer - Evidence: "We have a upcoming elections for board members and also the ability to nominate yourself or someone else" #### ⏱️ [05:20](https://youtu.be/gv3pyDqefGE?t=320) — [H1] Community contributions documentation requirement - Key idea: Non-PR contributions must be documented for voting eligibility - Evidence: "If you are giving chaos contributions that do not show up in PRs...you really need to fill this that issue out" #### ⏱️ [07:30](https://youtu.be/gv3pyDqefGE?t=450) — [H2] GitHub account requirement for elections - Key idea: Voting requires GitHub ID for Elekto software verification - Evidence: "You will have to have a GitHub account as well which is you know clearly a limitation" #### ⏱️ [09:15](https://youtu.be/gv3pyDqefGE?t=555) — [H2] Election software and ranking system - Key idea: Elekto software will manage nominations with candidate profiles and ranking - Evidence: "You'll be able to rank who you want...they'll have their name and a little paragraph about themselves" #### ⏱️ [11:00](https://youtu.be/gv3pyDqefGE?t=660) — [H2] Election timeline and testing phase - Key idea: Election officers testing software before opening nominations - Evidence: "We're right now in the process of just testing the software to make sure that it's working properly" #### ⏱️ [13:30](https://youtu.be/gv3pyDqefGE?t=810) — [H3] Conference submission reminders - Key idea: Two conference deadlines approaching for community presentations - Evidence: "Apache Software Foundation's community over code conference in Glasgow...deadline of March 20th" #### ⏱️ [14:45](https://youtu.be/gv3pyDqefGE?t=885) — [H3] Chaotic of the month recognition - Key idea: Andre recognized for contributions during CHAOS EU conference - Evidence: "Andre was super awesome during the Chaos EU conference" #### ⏱️ [16:20](https://youtu.be/gv3pyDqefGE?t=980) — [H2] Facilitation rotation explanation - Key idea: Community rotating meeting facilitation to distribute management work - Evidence: "We are starting to kind of rotate this job around of facilitating this meeting" #### ⏱️ [18:00](https://youtu.be/gv3pyDqefGE?t=1080) — [H2] Community management transition planning - Key idea: Planning for community management transition pending funding confirmation - Evidence: "We are thinking about kind of the transition around community management...we just don't really have any kind of confirmation from anybody yet around funding" ## 📚 References - [CHAOSS Board Election Mechanics Document](referenced) - [Community Contributions Repository](referenced) - [Apache Community Over Code Conference](referenced) - [All Things Open Conference](referenced) ## 🗣️ Paraphrase - CHAOSS is conducting its first board elections using Elekto software with nomination and ranking features - Community members need GitHub accounts and documented contributions to participate in voting - The organization is distributing community management responsibilities through rotating meeting facilitation ## 📰 Newsletter **CHAOSS Community Prepares for Inaugural Board Elections** The CHAOSS community is embarking on its first-ever board election process, marking a significant milestone in project governance. Election officers are currently testing the Elekto voting platform and preparing comprehensive guidance for community participation. **Key Actions for Community Members:** - Document your contributions if they don't appear in GitHub PRs using the community repository issue template - Ensure you have a GitHub account for voting verification - Consider nominating yourself or others for board positions The election represents CHAOSS's evolution toward more distributed governance, complementing ongoing efforts to rotate community management responsibilities. Multiple communication rounds will provide detailed guidance as the process launches. **Community Opportunities:** - Volunteer to facilitate weekly community calls - Submit conference proposals to Apache COC Glasgow (deadline March 20) or All Things Open (deadline March 31) - Participate in working group activities and documentation efforts This democratic transition strengthens CHAOSS's commitment to inclusive, community-driven development of open source health and sustainability metrics. Resources: [CHAOSS Website](https://chaoss.community/), [CHAOSS GitHub](https://github.com/chaoss/), [Community Handbook](https://handbook.chaoss.community/) ## ✅ Action Items #### OSPO - License Compliance: Review Elekto software licensing for election compliance - Community Engagement: Support transparent board election processes and documentation #### Community - Contributors: Complete community contributions documentation for election eligibility - Maintainers: Participate in governance transition planning and board candidate evaluation - Sponsors: Understand funding implications for community management transitions #### DevRel - Community management: Implement distributed facilitation rotation for sustainable operations - Education: Develop election participation guides and voting tutorials - Developer experience: Ensure GitHub integration doesn't exclude potential contributors ## 🧪 Hypotheses - Rotating meeting facilitation will increase community engagement and reduce single points of failure - GitHub account requirements may limit participation from non-technical community members - Elekto software integration will streamline the election process compared to manual management - Documentation of non-PR contributions will reveal significant hidden community work ### 📊 Methodology - Survey community members about facilitation interest and barriers to participation - Track election participation rates by contribution type and GitHub account status - Compare election software efficiency metrics with manual process estimates ### ❓ Questions - How will the community address voting exclusion for members without GitHub accounts? - What timeline and communication strategy will maximize election participation? - How might board election outcomes influence CHAOSS's technical and community priorities? ### 🔮 Future Research - Analyze effectiveness of distributed community management models in open source projects - Study impact of governance transitions on project sustainability and contributor retention - Investigate alternative voting mechanisms that reduce technical barriers ### 💡 Implications - Practice: Community members must actively document contributions beyond code for governance participation - Policy: GitHub account requirements create potential exclusion that may need alternative solutions - Education: Election process requires comprehensive guidance and multiple communication touchpoints - Funding: Community management transition depends on securing ongoing financial support ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Meeting notes document with clear structure and links - Improve: Election process flowcharts, timeline visualizations, contribution documentation examples #### 🔊 Aural learners - Present: Weekly video calls with recorded discussions - Improve: Election explainer podcast episodes, audio guides for participation #### 🗣️ Verbal learners - Present: Clear definitions of eligibility, contribution types, and process steps - Improve: FAQ documentation, glossary of election terminology #### 🧩 Kinesthetic learners - Present: Interactive contribution documentation templates, hands-on GitHub processes - Improve: Step-by-step voting simulation, practice nomination workflows #### 🧠 Logical learners - Present: Clear election timeline and sequential process description - Improve: Decision trees for eligibility, cause-effect diagrams for governance impact #### 🧑‍🤝‍🧑 Social learners - Present: Community calls for discussion and Q&A about elections - Improve: Board candidate forums, peer guidance for contribution documentation #### 🧘‍♀️ Solitary learners - Present: Self-service documentation and issue templates for contributions - Improve: Reflection prompts about governance participation, self-assessment tools #### 🌿 Naturalistic learners - Present: Community ecosystem analogies for governance structures - Improve: Organic growth metaphors for distributed leadership ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure in meeting notes - Improve: Alt text for any governance diagrams, proper ARIA labels #### Keyboard navigation - Present: Text-based meeting format navigable by keyboard - Improve: Ensure election platform keyboard accessibility #### Contrast and readability - Present: High contrast meeting notes in Google Docs - Improve: Verify election platform meets WCAG contrast requirements #### Text resizing and reflow - Present: Document format supports text scaling - Improve: Test election interface at 200% zoom #### Media and captions - Present: Video calls with potential for recording - Improve: Automated captions for recorded sessions, transcript availability #### Forms and interactions - Present: GitHub issue templates for contribution documentation - Improve: Clear error messages, accessible form validation #### Standards reference - Map election platform accessibility to WCAG 2.2 AA requirements ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community with distributed participation - Improve: Consider timezone impacts on election timeline, multiple language support #### Inclusive language - Present: Professional, respectful community communication norms - Improve: Review election terminology for inclusivity, avoid technical jargon #### Neurodiversity support - Present: Written documentation alongside verbal explanations - Improve: Multiple format options for election guidance, consistent structure #### Representation - Present: Encouraging broad community nomination participation - Improve: Actively seek diverse board candidates, address participation barriers #### Psychological safety - Present: Code of conduct framework for community interactions - Improve: Clear guidelines for respectful election discourse, conflict resolution ### ✅ Logical Validity #### Strong reasoning - Deductive strength: GitHub requirement logically follows from Elekto software verification needs - Inductive strength: Rotation of facilitation reasonably distributes community management load - Causal reasoning: Documentation requirement causally linked to election eligibility verification #### Fallacies - Appeal to novelty: "First-ever elections" framing may overemphasize newness without addressing process quality - Technical solutionism: Assuming software platform solves governance challenges without addressing social dynamics #### Tone of voice - Overall tone: Collaborative and informative with appropriate acknowledgment of process limitations and learning curve ### 🛡️ DARVO Analysis - Deny: No evidence of denial patterns - Attack: No evidence of attacks on community members - Reverse victim/offender: No evidence of victim/offender reversal - Emotional cues and rhetoric: Positive, supportive community tone throughout discussion ## 🎯 Conclusion The CHAOSS community is navigating its first board election process with careful attention to inclusion while managing technical constraints. The emphasis on documenting diverse contribution types demonstrates commitment to recognizing non-code community work, though GitHub account requirements present accessibility challenges. The parallel initiative to rotate meeting facilitation reflects broader efforts to distribute community management responsibilities and build organizational resilience. Success will depend on comprehensive communication, addressing participation barriers, and learning from this inaugural governance process to improve future elections. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] First board elections require comprehensive community preparation > [!quote] [CHAOSS Weekly Community Call, March 10, 2026](https://youtu.be/gv3pyDqefGE) by [[CHAOSS Community]] via [[YouTube]]. Published 2026-03-10. Accessed 2026-03-10. > "If you are giving chaos contributions that do not show up in PRs, you really need to fill this that issue out." Election eligibility depends on documented contributions beyond code, requiring proactive community member action to ensure voting rights. [view highlight](https://youtu.be/gv3pyDqefGE?t=320#H1) #xref #articleseed ID:rw_chaoss_election_prep ### [H2] GitHub requirements create participation barriers in community governance > [!quote] [CHAOSS Weekly Community Call, March 10, 2026](https://youtu.be/gv3pyDqefGE) > "You will have to have a GitHub account as well which is clearly a limitation." Technical voting requirements may exclude community members who contribute through non-technical means but lack GitHub accounts. [view highlight](https://youtu.be/gv3pyDqefGE?t=450#H2) #xref ID:rw_github_voting_barrier --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Distributed facilitation improves community resilience - Applies to volunteer-driven open source communities seeking sustainable operations - Pointer to 16:20 timestamp discussion of rotation rationale - Links: [[Community-Management]] [[Volunteer-Sustainability]] #### [Z2] Technical voting platforms require accessibility planning - Condition: When election software integrates with developer platforms like GitHub - Pointer to 7:30 discussion of GitHub account requirement and workarounds - Links: [[Digital-Democracy]] [[Accessibility-Barriers]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Research Elekto software accessibility features — election platform evaluation #fleeting #inbox - [F2] Document CHAOSS governance transition timeline — community management planning #fleeting #inbox - [F3] Compare open source project election models — governance research #fleeting #inbox --- ## Full Transcript [00:00] recording has started. So, um you can [00:02] leave your cameras on or off. Um we're [00:05] under the chaos code of conduct. Uh feel [00:07] free to put your name into the minutes [00:09] which are in the document that I'm [00:11] sharing right now and I've shared in [00:13] chat. If uh new people come, if somebody [00:16] could reshare that would be awesome. Um [00:19] and so let's just uh let's get going. So [00:22] the first agenda item is uh can I get a [00:25] volunteer to facilitate next week? [00:32] kind of looking at the co and Mary [00:34] blessing maybe. [00:38] >> All right. Well, um table for now. [00:40] >> I can I can do it. It's okay. [00:44] >> Are you sure? [00:45] >> Yeah. Yeah, that's fine. [00:46] >> I mean, unless Yeah, I'll do it for now [00:48] and then if we get a volunteer, [00:50] >> I won't fill it until the end because [00:52] maybe they'll be a volunteer. [00:54] >> Yeah. Um, just a final reminder that the [00:56] chaos calendar has been updated for [00:58] meeting times and we are under daylight [01:00] savings time. Elizabeth, you put out uh [01:04] communicate last was it last week or I [01:07] can't remember where I saw this, but I [01:08] saw a really good layout of which [01:10] meetings are conforming to the daylight [01:13] savings times, which meetings are [01:15] staying with UTC. Um, have you se do you [01:19] know where do you remember where that [01:20] right where I may have seen that [01:22] summary? Yeah, there's uh if you scroll [01:24] down in these minutes, it's there. It's [01:27] also in Slack in the general channel, I [01:29] think. Oh, there you go. Scroll back up [01:31] a little bit. [01:32] >> Uh [01:33] >> there it is. Like that's Yeah. [01:36] >> Okay. All right. [01:40] >> Yeah. So, if you want to copy and paste [01:41] that in there. Yeah. [01:49] I want to find a link, [01:53] but like I think there should be a link [01:56] to like um [01:58] there should be a way to like link this. [02:02] >> Oh, maybe if you add it as a header and [02:06] then you can link over in the left [02:08] column. You know what I mean? [02:12] Uh yeah. Okay. [02:14] >> So if you Yeah. If you expand that, you [02:16] could go down. [02:19] Yeah. Right down there. There you go. [02:20] And I think you can link straight to [02:22] that. [02:24] Copy link. [02:26] Yeah. [02:27] >> There we go. All right. Yeah. So I was [02:29] just thinking of ways to not repeat it. [02:45] Um, and then from last week, there was a [02:47] code forg. Uh, mentoring internship [02:50] planned for the UN SG working group. I [02:53] don't know, I don't see anyone from the [02:55] UN SG working group here today. [03:03] So, I don't have I don't know anything [03:06] about what this is, [03:08] but I'll follow the link and see. [03:14] This is what it is. [03:19] And apparently there are some [03:20] internships available if anyone is [03:22] interested in those. [03:25] Um, [03:27] all right, that's that. This might be a [03:29] very brief meeting. [03:32] Uh, and then the CAS board elections are [03:35] coming. Uh, I don't know if anyone's [03:38] here that can provide a summary of what [03:40] that means or how that's going to work. [03:42] >> Yeah, I can do that. Um, so as one of [03:44] the election officers, um, I can do [03:46] that. U, so in case you all haven't [03:49] heard, we are we have uh a upcoming [03:53] elections for board members and also the [03:56] ability to nominate yourself or someone [03:58] else um, as a board member. If you click [04:01] on that mechanics doc, Sean, that will [04:04] have all of the information. So, like [04:06] what the criteria are, how we figure it [04:09] all out. Um, yeah. So, read through that [04:13] doc. uh if you are interested in either [04:16] running or voting. Um in particular, if [04:20] you are giving chaos contributions that [04:23] do not show up in PRs, and this is [04:25] pretty important, you really need to [04:28] fill this that issue out uh for the [04:32] community contributions doc. If you go [04:34] to the community repo, there's an issue [04:36] template that Sean made. Makes it super [04:38] easy to add your name. Um, but we need [04:41] to have that in order to verify your [04:43] eligibility to vote or to run. So, if [04:46] you are one of those folks that um [04:49] contributes in other ways besides things [04:51] that show up in PRs, absolutely make [04:53] sure your um name is in that file [04:59] and your contribution as well. It also [05:01] seems to be the case that you will need [05:04] to that the is it that your group [05:07] Elizabeth the election officers that [05:09] will manage some list of GitHub ids [05:11] associated with the people. [05:13] >> Yep. [05:14] >> Yep. So you will have to have a GitHub [05:15] account as well which is you know [05:17] clearly a limitation. I believe we're [05:20] we're planning to have a form you can [05:21] fill out if you do not have a GitHub [05:23] account. Um and I believe we're able to [05:26] add you uh on the back end. I think um I [05:30] need to confirm that uh we have uh uh [05:32] folks from the K native community who [05:35] run these elections all the time. He's [05:37] one of our officers. He's kind of [05:39] helping Emma Irwin is the other officer. [05:41] He's helping Emma and myself sort [05:43] through all this um since we've never [05:44] done it before, none of us. Um and we [05:47] are using this Eleto software so that [05:50] we'll kind of manage that whole process [05:52] and it helps us um just like it gives [05:55] you all the everybody who is nominated. [05:58] you'll be able to see, you'll be able to [05:59] rank um who you want. Um and they'll [06:02] have their name and a little um [06:05] paragraph about themselves and their [06:08] contributions to Chaos. So um you'll be [06:11] able to see all of that, but the way [06:12] that it verifies your eligibility is to [06:15] um we send it a list of GitHub IDs um [06:19] and that's how it'll let you in. [06:21] Essentially, [06:25] we there is an FAQ doc that we are we've [06:28] started. Um it's not complete by any [06:30] means. Uh we're building it out kind of [06:32] as we go and as we sort through these [06:34] steps. We're right now in the process of [06:36] just testing the software to make sure [06:38] that it's working properly the way we [06:40] want it to. Um because there's a lot of [06:43] like backend stuff that talks to GitHub [06:46] directly and things. So, um, we're we're [06:48] currently testing it, but, uh, we should [06:51] be opening things up [06:54] next few weeks. I would I would think [06:58] next next month [07:00] >> somewhere I saw somewhere I saw an [07:01] election timeline. [07:02] >> Yeah, we haven't posted that yet. Um, we [07:05] sent it to the board for just kind of [07:07] their information first. Um, we meet [07:10] Emma and Ally and I meet every Thursday. [07:13] So, this Thursday we'll probably confirm [07:15] everything. Um, and um, you'll you all [07:19] will see us starting to remind everybody [07:22] over and over again like make sure [07:25] you've added your name to this doc. Make [07:27] sure you you know your PRs are in. Um, [07:31] and if you want to nominate yourself or [07:33] someone else, make sure they have you [07:34] have consent from them and here's the [07:37] process and all that stuff. So, you will [07:38] see multiple communications from our [07:40] team in the upcoming weeks [07:44] because I know this is new for [07:45] everybody. It's a big learning curve. [07:47] Um, we've not done this before. So, [07:49] yeah, it's going to take a little time [07:50] to kind of normalize it and make sure [07:52] everybody knows what the deal is. [08:01] I [08:01] >> think that's all I have. [08:03] >> All right. Um, and that is the entire of [08:08] the agenda that we have today, which is [08:11] cool. I mean, people don't mind getting [08:12] time back, I'm sure. It looks like [08:14] there's a few reminders about the Apache [08:16] Software Foundation's community over [08:18] code conference in Glasgow. Uh that has [08:21] a deadline of March 20th, which is let's [08:24] see two weeks. And Mered Blessing, I see [08:27] your hand is up. [08:31] Go for it. [08:31] >> Um yeah, thanks Sean. Um Adren is not [08:36] the call. I just wanted to give a shout [08:38] out to to him for being the chaotic of [08:40] the month. Um, Andre was super awesome [08:43] during the Chaos EU um, conference. So, [08:47] yeah, shout out to Andre [08:49] and I've posted on the general Slack in [08:51] case people want to go celebrate him [08:53] there. [08:55] All right, congratulations to our [08:58] chaotic of the month at Inca. [09:01] And then the final reminder is for all [09:03] things open uh, deadline of March 31st, [09:06] end of the month. Uh, similar time frame [09:09] in October. This one's in Raleigh, North [09:10] Carolina instead of Glasgow. So, choose [09:14] your destinations accordingly. [09:16] Um, I don't have anything else, [09:19] Elizabeth. I don't know if you do, if [09:20] there's anything else anyone else wants [09:21] to bring to the table. [09:30] All right, Elizabeth, I'm going to put [09:31] you in then as the um facilitator next [09:34] week and um hopefully we get another [09:38] volunteer after next meeting. [09:40] >> Totally fine. For those of you who did [09:42] not were not here last week, um we are [09:44] starting to kind of rotate this job [09:47] around um of facilitating this meeting [09:50] uh just to kind of help spread the the [09:53] work the work of the community manager [09:56] and and this is something that anybody [09:57] in the community can certainly do. So we [10:00] want to encourage folks to get in [10:01] engaged and um or be engaged, not get [10:04] engaged. That's weird. Um, but yeah, we [10:07] want you to, this is an opportunity for [10:09] you to contribute if it's something that [10:10] you're interested in doing. And we do [10:12] have a guide that basically tells you [10:15] exactly what to do. Um, so it's, you [10:17] know, it's pretty easy. It's really not [10:20] um it it it's not super stressful and [10:23] you're not doing it alone. Like we build [10:25] the agenda together. So um you know, [10:28] don't feel intimidated by that piece of [10:31] it if that's something that's on your [10:33] mind. So yeah, so that's why we're [10:36] looking for facilitators because we're [10:38] hoping to kind of rotate that out. [10:45] And I I meant to do this and I didn't do [10:47] it last week. I meant to post something [10:48] in general that that's what we're doing [10:50] just so folks kind of know. Um and just [10:53] so you all also do know um you know we [10:56] are thinking about kind of the [10:58] transition around community management [11:01] and what that might look like. We just [11:02] don't really have any kind of [11:03] confirmation from anybody yet around [11:07] funding or anything. So, [11:10] >> so it's just like kind of up in the air, [11:12] but we are definitely think about it. [11:13] We're planning everything. I have [11:15] everything documented. Um, yeah. So, so, [11:18] uh, it's just a matter of getting some [11:20] confirmation on some things. [11:25] >> Yeah. [11:28] >> All right, everybody. uh give you 25 [11:30] minutes of your life back and um see you [11:34] next week. [11:35] >> Excellent. Thanks, Sean. [11:36] >> Thank you everybody. Thank you [11:38] Elizabeth. Thanks for having us. Bye [11:40] everyone. See you later.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, March 10, 2026.md|CHAOSS Weekly Community Call, March 10, 2026 by YouTube]] ## Highlights - want to encourage folks to get in engaged and um or be engaged, not get engaged. That's weird. Um, but yeah, we want you to, this is an opportunity for you to contribute if it's something that you're interested in doing. And we do have a guide that basically tells you exactly what to do. Um, so it's, you know, it's pretty easy. It's really not um it it it's not super stressful and you're not doing it alone. Like we build the agenda together. So um you know, don't feel intimidated by that piece of ([View Highlight](https://read.readwise.io/read/01kpb56p31sjmdwk4xp93xzm9f)) - Tags: 👻 ai highlighted - it if that's something that's on your mind. So yeah, so that's why we're looking for facilitators because we're hoping to kind of rotate that out. And I I meant to do this and I didn't do it last week. I meant to post something in general that that's what we're doing just so folks kind of know. Um and just so you all also do know um you know we are thinking about kind of the transition around community management ([View Highlight](https://read.readwise.io/read/01kpb56p47vwqv7h455mpy10tv)) - Tags: 👻 ai highlighted