CHAOSS Weekly Community Call, Feb 3, 2026 - CourtneyR.dev's 2nd Brain

CHAOSS Weekly Community Call, Feb 3, 2026 ![rw-book-cover](https://img.youtube.com/vi/48fQKM6t6qI/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, Feb 3, 2026](https://www.youtube.com/watch?v=48fQKM6t6qI) > [!note]+ Document Notes > tags: #chaoss #open-source #community-management #gsoc #conferences > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=48fQKM6t6qI > date created: 2026-02-03 14:00 > > # 🏷️ Title: CHAOSS Weekly Community Call - February 3, 2026 >  ## 🧰 Action Inbox - [H1] Send post-event survey for CHAOSSCon — Elizabeth working on with Jay #chaoss - [H2] Research Google Docs performance impact of version history — Elizabeth to investigate #infrastructure - [H3] Contact Fascia team about GSOC application deadline — Elizabeth to ping Divia #gsoc ## 🧭 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 - [CHAOSSCon Live Stream Recording](URL) - [CHAOSS Slack - WG Augur & knot channel](URL) - [8knot Instance](URL) ## 📝 Summary - CHAOSSCon 2026 was highly successful with best attendance ratio ever and 17 countries represented - Elizabeth announced she will step back from full-time community management at end of March due to grant funding uncertainty - Community discussed vouching for Fascia organization for Google Summer of Code participation - Technical discussions about managing large meeting minutes document and design contribution opportunities - Strong community support and planning for transition period ## 📖 Main Content The February 3rd CHAOSS weekly call covered several major updates. CHAOSSCon 2026 was declared a major success, featuring a new venue with community feel, comprehensive programming including lightning talks, workshops, keynotes, and unconference sessions. The event achieved the best registration-to-attendance ratio in CHAOSS history with 17 countries represented. Elizabeth made a significant announcement about stepping back from full-time community management at the end of March. Her position has been funded by the Alpha Omega Foundation for nearly 6 years, and while they've been asked to submit a proposal for one more year, the funding remains uncertain. She emphasized this is stepping back, not stepping away, and will continue contributing to the open source project in some capacity. The community discussed vouching for Fascia, an organization focused on inclusivity and helping women in the Indian region, to participate in Google Summer of Code. This requires existing GSOC participants to recommend new organizations, though timing concerns arose as the application deadline was the same day. Technical discussions included managing the unwieldy shared meeting minutes document and opportunities for design contributions to projects like 8knot and Augur. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/48fQKM6t6qI?t=0) — [H1] CHAOSSCon 2026 Success Report - Key idea: Conference achieved best attendance ratio ever with comprehensive programming - Evidence: "17 countries represented" and "literally every aspect of a conference that you can have, we had" #### ⏱️ [03:45](https://youtu.be/48fQKM6t6qI?t=225) — [H2] Venue and Community Experience - Key idea: New community-run venue provided better atmosphere than hotel venues - Evidence: "very much more of that community feel" and "everyone chips in, everyone helps out" #### ⏱️ [06:30](https://youtu.be/48fQKM6t6qI?t=390) — [H3] Financial Success Despite Challenges - Key idea: Conference made modest profit despite higher venue costs and providing lunch - Evidence: "we came out like plus $600 or something like that" with €40 ticket price #### ⏱️ [09:15](https://youtu.be/48fQKM6t6qI?t=555) — [H1] Elizabeth's Transition Announcement - Key idea: Community manager stepping back due to grant funding uncertainty - Evidence: "at the end of March, I will be stepping back from full-time chaos community management" #### ⏱️ [12:00](https://youtu.be/48fQKM6t6qI?t=720) — [H2] Funding Background and Future Uncertainty - Key idea: Six-year Alpha Omega Foundation funding ending with uncertain renewal - Evidence: "they have asked us to put together a proposal for one more year of funding, but that is still up in the air" #### ⏱️ [15:30](https://youtu.be/48fQKM6t6qI?t=930) — [H3] Community Response and Transition Planning - Key idea: Community expressing gratitude and discussing workload distribution strategies - Evidence: "shadow maybe some of the kinds of work you've been doing" and "split off that would be potentially in alignment with certain majors" #### ⏱️ [18:45](https://youtu.be/48fQKM6t6qI?t=1125) — [H2] GSOC Vouching Request - Key idea: CHAOSS Asia community requesting vouching for Fascia organization - Evidence: "some folks from the Chaos Asia community approached me" for GSOC recommendation #### ⏱️ [21:00](https://youtu.be/48fQKM6t6qI?t=1260) — [H3] GSOC Timing Concerns - Key idea: Application deadline timing created urgency for vouching decision - Evidence: "application for that closes like uh probably in a few hours if not now" #### ⏱️ [24:15](https://youtu.be/48fQKM6t6qI?t=1455) — [H3] Meeting Minutes Document Management - Key idea: Large shared document becoming unwieldy with performance concerns - Evidence: "This document is huge. It's very unwieldy" with Google Docs history concerns #### ⏱️ [27:30](https://youtu.be/48fQKM6t6qI?t=1650) — [H2] Design Contribution Opportunities - Key idea: Community member asking about design contribution beyond conferences - Evidence: "other ways I can contribute to actual opensource projects besides just contributing to like conferences" #### ⏱️ [29:45](https://youtu.be/48fQKM6t6qI?t=1785) — [H3] 8knot Redesign Achievement - Key idea: Recent successful redesign based on CHAOSS Africa design team work - Evidence: "we actually ended up landing a big redesign of 8 knot based on a design that was made by the Chaos Africa design team" ## 📚 References - [CHAOSSCon Live Stream Recording](URL) - [Alpha Omega Foundation](https://alpha-omega.dev/) - [Google Summer of Code](https://summerofcode.withgoogle.com/) - [CHAOSS 8knot Project](https://github.com/8knot/8knot) ## 🗣️ Paraphrase - CHAOSSCon 2026 exceeded expectations with excellent attendance, global representation, and comprehensive programming in a community-focused venue - Elizabeth's transition from full-time community management creates uncertainty but opens opportunities for distributed community leadership - The community demonstrated strong support systems and willingness to adapt to changing circumstances while maintaining project continuity ## 📰 Newsletter **CHAOSS Community Celebrates Success While Navigating Transition** The CHAOSS community is riding high from CHAOSSCon 2026's remarkable success - achieving their best-ever attendance ratio with representatives from 17 countries. The new community-run venue fostered collaboration and featured everything from keynotes to workshops to unconference sessions. However, the community faces a significant transition as long-time community manager Elizabeth steps back from full-time duties due to grant funding uncertainty. Her six-year tenure, funded by the Alpha Omega Foundation, has been instrumental in CHAOSS's growth. The community is already rallying to distribute responsibilities and ensure continuity. For open source contributors, this highlights the importance of sustainable funding models and community resilience. Consider how your projects might weather similar transitions and what distributed leadership could look like. Resources: [CHAOSS Metrics](https://chaoss.community/), [Community Handbook](https://handbook.chaoss.community/), [CHAOSSCon](https://chaoss.community/chaosscon-2026/) ## ✅ Action Items #### DevRel - Document community management processes for knowledge transfer - Create onboarding materials for distributed community leadership roles - Establish metrics for measuring community health during transitions #### Community - Maintainers: develop succession planning templates and transition checklists - Contributors: identify skills-based volunteer opportunities matching academic research - Sponsors: explore sustainable funding models beyond single large grants #### FAIR - Technical independence: ensure project continuity despite personnel changes - Governance artifacts: document decision-making processes and role responsibilities ## 🧪 Hypotheses - Community-run venues provide better collaboration environments than commercial hotel spaces - Distributed community management can maintain project momentum with proper coordination - Academic partnerships offer sustainable alternatives to grant-dependent staffing models - Regional focus in diversity initiatives creates more effective inclusion outcomes ### 📊 Methodology - Survey attendees comparing venue experiences across multiple years - Track community health metrics during leadership transition periods - Analyze volunteer engagement patterns in skills-based matching programs ### ❓ Questions - How can open source projects build resilient leadership structures that survive funding uncertainties? - What distributed community management models work best for technical projects? - How do we maintain institutional knowledge during personnel transitions? ### 🔮 Future Research - Best practices for open source project succession planning - Sustainable funding model development for community infrastructure - Academic-industry partnership frameworks for project sustainability ### 💡 Implications - Practice: Need for documented processes and distributed expertise in community management - Funding: Importance of diversified funding sources for project sustainability - Community: Value of regional chapters and skills-based contribution matching - Governance: Critical need for succession planning in open source projects ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Meeting agenda structure, clear topic separation - Improve: Conference venue photos, organizational charts, funding timeline visuals #### 🔊 Aural learners - Present: Full video recording with natural conversation flow - Improve: Timestamped audio chapters, key decision point summaries #### 🗣️ Verbal learners - Present: Clear explanations of complex funding and governance situations - Improve: Glossary of community management terms, analogy examples #### 🧩 Kinesthetic learners - Present: Interactive discussion format, real-time decision making - Improve: Transition planning worksheets, community health assessment tools #### 🧠 Logical learners - Present: Clear cause-effect relationships between funding and staffing - Improve: Decision trees for transition planning, timeline dependencies #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion format, collaborative problem-solving - Improve: Peer mentoring programs, transition support groups #### 🧘‍♀️ Solitary learners - Present: Detailed meeting minutes for individual review - Improve: Self-assessment tools for community contribution readiness #### 🌿 Naturalistic learners - Present: Organic community evolution discussions - Improve: Ecosystem thinking about project sustainability ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive timestamps - Improve: More detailed alt text for any visual references #### Keyboard navigation - Present: Standard video controls, text-based content - Improve: Skip links for long transcript sections #### Contrast and readability - Present: Standard text formatting - Improve: Highlighted action items, better visual hierarchy #### Text resizing and reflow - Present: Responsive text format - Improve: Ensure timestamp links remain functional at high zoom #### Media and captions - Present: Full transcript available - Improve: Closed captions on video, downloadable transcript #### Forms and interactions - Present: Basic video interaction - Improve: Accessible video player controls ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global participation with 17 countries represented - Improve: Multi-timezone meeting scheduling, cultural context for governance #### Inclusive language - Present: Welcoming tone, defined community terms - Improve: Pronunciation guides for international names, translation resources #### Neurodiversity support - Present: Multiple information formats (video, transcript, notes) - Improve: Content warnings for emotional topics, structured agendas #### Representation - Present: Women and international voices in leadership discussions - Improve: Diverse examples in succession planning #### Psychological safety - Present: Supportive community response to difficult announcements - Improve: Explicit community guidelines, conflict resolution processes ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Conference success metrics logically support venue choice decisions - Inductive strength: Past funding patterns inform future sustainability planning - Causal reasoning: Clear connection between funding uncertainty and personnel decisions #### Fallacies - Appeal to emotion: Some discussions rely on community sentiment rather than objective criteria - False dilemma: Limited exploration of alternatives between full-time and stepping away entirely #### Tone of voice - Overall tone: Professional but warm, transparent about uncertainties while maintaining optimism ### 🛡️ DARVO Analysis - Deny: No significant denials noted in community discussions - Attack: No attacks on community members or external organizations - Reverse victim/offender: Not applicable to this content - Emotional cues: Appropriate emotional responses to personnel transitions, supportive community dynamics ## 🎯 Conclusion The CHAOSS community demonstrated remarkable resilience and maturity in this call, celebrating significant conference success while thoughtfully addressing major personnel transitions. Elizabeth's announcement about stepping back from full-time community management, while emotional for the community, was handled with transparency and forward-thinking planning. The community's immediate response to begin distributing responsibilities and exploring academic partnerships shows sophisticated understanding of sustainable open source project management. The successful CHAOSSCon 2026, with its community-focused venue and global participation, provides a strong foundation for navigating upcoming changes. Key takeaways include the importance of diversified funding models, documented processes for knowledge transfer, and the value of community-driven venues for fostering collaboration. The transition period ahead offers opportunities for distributed leadership models that could strengthen the project's long-term sustainability. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Conference success correlates with community-focused venues > [!quote] CHAOSS Weekly Community Call by CHAOSS Community via YouTube. Published 2026-02-03. Accessed 2026-02-03. > "very much more of that community feel...everyone chips in, everyone helps out" Community-run spaces foster collaboration better than commercial venues for technical conferences. [view highlight](https://youtu.be/48fQKM6t6qI?t=225#H1) #xref #articleseed ID:rw_chaoss_venue ### [H2] Grant dependency creates organizational vulnerability > [!quote] CHAOSS Weekly Community Call > "that funding round is now coming to an end...still up in the air" Single large grant dependencies expose open source projects to personnel discontinuity risks. [view highlight](https://youtu.be/48fQKM6t6qI?t=555#H2) #xref ID:rw_funding_risk --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Distributed community management enables project resilience - Applies when single-person dependencies create vulnerability - Referenced at transition planning discussion - Links: [[Open-Source-Sustainability]] [[Community-Leadership]] #### [Z2] Academic partnerships provide sustainable contribution models - Works for skills-based matching with research alignment - Referenced at volunteer coordination discussion - Links: [[University-Collaboration]] [[Volunteer-Management]] --- ### ✏️ Fleeting Queue - [F1] Research CHAOSSCon venue selection criteria — community vs commercial #fleeting #inbox - [F2] Document transition planning best practices — open source projects #fleeting #inbox - [F3] Explore academic research alignment — community contribution matching #fleeting #inbox --- ## Full Transcript [00:02] Okay. Hi everybody. We missed you last [00:04] week, but we're back this week. It is [00:07] Tuesday, February 3rd, 2026. Um, [00:11] tomorrow is my son's birthday. Yay. [00:12] Happy birthday, Will. Uh, [00:16] yeah. Add your name if you want. If you [00:18] had a good dad joke or pun or silly joke [00:20] you want to plop in here, that'd be [00:22] great. A little levity for today. [00:28] I'm reading. [00:32] >> That's great. [00:36] >> You did two yesterday and didn't know [00:38] it. What do you mean, Matt? [00:39] >> Yeah. One was So, have you seen the like [00:42] the guy Fiery? You know what I'm talking [00:45] about? [00:45] >> Yeah. [00:46] >> Did you see his like new look that they [00:48] posted? [00:49] >> No. [00:50] >> Okay. Well, anyway, at one point I said [00:52] it's the same guy and I didn't even [00:55] >> Oh, the same guy. [00:58] That's what I was say. [01:03] >> Oh, that's funny. It looks like Adrien [01:05] has a few. Thank you, Adrian, for [01:07] sharing these with us. Uh, okay. We have [01:11] a lot on agenda, so let's hop into it [01:14] today. Um, yeah, Chaos Conu was awesome, [01:19] awesome, awesome. for those who were [01:22] able to make it, it was great to see [01:23] you, Ilico mostly, I think, and Adrian, [01:26] of course. Uh, I think you are the only [01:28] ones here that was that were there. So, [01:31] yeah, it was great. I would be [01:32] interested to hear how you, you know, [01:34] you all felt about it. Um, I thought it [01:36] was great and it was such a different [01:38] departure from what we typically do. We [01:40] had, I think, literally every aspect of [01:43] a conference that you can have, we had. [01:46] So we had in some way lightning talks, [01:49] unconference, keynotes, regular talks, u [01:52] workshops, like we had it all. So we [01:54] even had a a meet and greet with an [01:55] author um Paloma who at lunch. We had [01:59] lunch and learn like yeah we had it all. [02:00] So very very um excited to see what kind [02:04] of feedback we get from attendees. And [02:08] >> the venue was nice. [02:10] >> It was good. Yeah, it was um there were [02:13] a lot of stairs. So, I will say that it [02:16] was not super uh in my opinion, but it's [02:20] Europe, so like a lot of buildings [02:22] aren't super, you know, accessible [02:24] accessible friendly. [02:26] >> How is it compared to the the hotel from [02:29] prior years? [02:30] >> I I liked it a lot better. It has a lot [02:33] more of a community feel. It's very much [02:35] a communityrun [02:37] um space. So, everyone chips in, [02:39] everyone helps out to clean up and put [02:42] the food out and um it's very much more [02:45] of that community feel. So, in that [02:47] regard, I really really liked it a lot [02:49] and they were absolutely wonderful. The [02:52] the uh hosts that uh were part of the [02:55] comments hub, they were absolutely [02:57] amazing. So, yeah. [03:00] >> Yeah. even just on paying and stuff like [03:02] that. They've been super easy to work [03:05] with. [03:05] >> Yeah. Yeah, they really have. You know [03:08] what? I'm going to turn my video off. I [03:10] see that I'm kind of choppy a little [03:11] bit. So, [03:12] >> not me or not. [03:13] >> No. [03:14] >> No. [03:15] >> Okay. I don't know. Maybe it's the snow. [03:19] More snow is making my internet weird. [03:23] But, um, but anyway, yeah. Um, we do [03:25] have a recording of the live stream and [03:27] Adrian and I are going to work together [03:28] to chop that up and and or tag where the [03:32] talks are, but if you want to watch the [03:34] full thing, you can do so at that link [03:36] right here. [03:38] >> Um, [03:38] >> there is also um one of the one of quick [03:40] note about the live stream. I think I [03:42] the live stream failed at towards the [03:45] start of the panel discussion after [03:47] lunch or whenever that was um cuz my [03:50] laptop decided to die right then like [03:53] not just for battery not for battery [03:55] reasons like actually die. So um I I [03:59] have an offline recording from someone's [04:01] phone that captures more of that panel [04:04] than the live stream did. There might [04:06] still be some missing but it should be a [04:08] lot less. So, I'll try and also get that [04:11] either edited together with the live [04:13] stream footage or just uploaded as its [04:15] own thing. Um, I have that on my laptop [04:17] right now. So, [04:20] >> excellent. Um, also just a huge huge [04:24] shout out to Adrian for running that all [04:27] day long. I mean, that was so much work [04:30] setting it up, testing it, preparing for [04:33] it all these months or weeks. I guess we [04:35] gave him We didn't give you much time. [04:37] Um just absolutely fantastic. Like I I [04:40] we even had like beautiful slides in [04:42] between when there was pauses. So thanks [04:44] to the design team for that. Ununice [04:46] worked on that. Um just really really [04:48] well done. I I feel like um despite the [04:50] hiccup and I'm so sorry about your [04:52] laptop. I hope it's okay now. Um but [04:55] yeah, it was really really awesome. Very [04:57] very uh job well done for all of all of [05:00] that. [05:04] We are going to be sending out a [05:06] postevent survey. Jay is working on [05:08] that. We basically took last year's [05:10] repurposed it added maybe one question I [05:12] think about the uh two questions we [05:14] added about the venue specifically and [05:16] about lunch because we did provide lunch [05:18] this time which we typically don't. So [05:20] we added those two and we'll be sending [05:21] that out um pretty soon. Very excited to [05:25] see what what the feedback is um and how [05:27] we can be better next year. [05:29] Uh we did have um a lot of folks check [05:34] in that had registered. So I think that [05:36] is the best ratio we've ever seen ever. [05:38] Hands down. Like we did [05:40] >> Yeah, we did not have [05:42] >> two, [05:43] >> right? Um, and I think that the honestly [05:46] I think the ones that didn't show had [05:49] travel issues or something else. Like I [05:51] don't think it was um like typically we [05:54] just have a lot of people that don't [05:55] come um for whatever reason they decide [05:57] to go to another event or um [05:59] >> I feel like sometimes it's a way for [06:01] people to make a small donation to [06:04] >> also valid. Yes. [06:05] >> Yeah. [06:06] >> Yeah. Um but this time it was the the [06:09] price was more for those who don't know. [06:11] We did raise the price. um we didn't [06:13] have quite the sponsorship we were [06:14] hoping for and also we were providing [06:16] lunch which was a big expense um and the [06:19] social event we had food at that as well [06:21] so um we did raise the price a little um [06:24] to €40 um but as you can see that [06:27] actually really made a huge difference [06:29] so I think we came out fine I don't [06:31] think [06:31] >> we did we we made we made a little bit [06:33] of money so our sponsorships were pretty [06:36] standard we get about same every year [06:39] >> the the venue and the food were just [06:42] more expensive. [06:43] >> Yeah. [06:44] >> This year, that's all. But then because [06:46] of the 78, I think we came out like plus [06:49] $600 or something like that. [06:51] >> Awesome. [06:52] >> Yeah. Which is good. [06:54] >> Yeah. Yeah. Uh we did have 17 countries [06:58] represented, which I think is also very [07:01] cool. Um Yeah. So, great job to [07:05] everybody. I don't think uh Gay York is [07:08] on the meeting. [07:10] >> No, [07:10] >> he's not. Okay. [07:12] >> Yeah, Gayorg and Cali did a fantastic [07:14] job also with the schedule and [07:16] coordinating all everything. And now [07:18] that we've been there, we know where the [07:19] rooms are. That was the only other thing [07:20] is the it was kind of confusing where [07:22] the rooms were cuz it's spread across [07:24] three floors. So, kind of like, oh, [07:27] where is this room? I don't know. [07:28] Where's that room? But now we know. So, [07:30] we can even make our own maps if we need [07:32] to, our own signage. But the again, the [07:34] venue is very helpful at helping people [07:36] find their way. So, hopefully everybody [07:37] was okay with that. [07:39] >> Okay. [07:44] Anybody have questions, comments? [07:47] >> Is open source summit in North America [07:51] like has that been declared? Oh [07:52] >> yeah, there's a there's a thread about [07:55] that. Yeah. In chaos con committee. [07:58] >> Okay. Yeah. Okay. Well, that I mean we [08:01] wouldn't organize for that anyway [08:03] because it's in May. [08:04] >> Too soon. Yeah. [08:06] >> Happen. [08:08] >> Yeah. For for those who don't know, um, [08:10] Open Source Summit North America is in [08:11] Minneapolis, Minnesota, which is a [08:13] little bit, um, unsettled, uh, if I can [08:16] say that right now. It's not [08:20] very I have feelings. I have feelings [08:23] about it, which I don't know if I'll [08:25] share here because it's recorded, but [08:27] um, yeah, I would be glad if we did not [08:31] subject any attendees to have to [08:34] navigate that. Yeah, that and then the [08:36] timing it like there are just so many [08:38] things that wouldn't work. [08:39] >> Yeah, it's a very quick turnaround. It's [08:40] in May and that's just like not much [08:43] time to turn around a whole event. [08:45] >> So then I'm wondering if we would do [08:46] anything in summer. [08:49] >> Yeah, in that thread that was in the [08:51] castcon committee planning somebody [08:53] mentioned I think Adrianne mentioned FSY [08:55] was in August or September in uh British [08:59] Columbia Vancouver. So [09:02] >> yeah. Yeah. [09:05] Okay. [09:06] >> Yeah. So, there's options I think for [09:07] later. Um, there was something else. [09:11] >> Aussie makes a lot of sense though. [09:13] >> Yeah. [09:16] Yeah. There was another Oh, maybe pie. [09:18] >> Also suggested potentially doing a [09:19] virtual event, but I think that's [09:21] probably not that there doesn't seem [09:22] like there was a lot of interest in [09:23] that. [09:27] >> Yeah, I guess we can talk about it. Um, [09:30] yeah. I I mean, I think we if we can, we [09:34] want to do in person, but I don't know. [09:35] I mean, maybe certainly opens it up for [09:39] participation a little bit more globally [09:41] than [09:42] >> Is FSY for sure in Canada? [09:45] >> I think so. [09:45] >> 2026 FSY is they they've they were [09:48] they've been in can they're doing [09:49] Canada. Yeah. [09:50] >> Okay. Okay. [09:53] >> Yeah, I think they're I think they're at [09:54] UBC. Um, I'm not sure what the what the [09:57] logistics behind the scenes would look [09:59] like as far as us being able to like get [10:01] the same venue on a similar day or or if [10:04] we'd have to do like [10:06] >> um go to like University of Victoria or [10:08] another university nearby or or what [10:10] collocation options are. But [10:12] >> I mean it it's that seems like if if the [10:14] goal is to colllocate with something [10:16] else [10:17] >> that's in North America and [10:20] >> like that that could be an option. We [10:22] did one chaos con once at a university [10:25] there years ago and I think Sean has a [10:29] connection. So anyway [10:30] >> Oh nice. [10:31] >> Yep. Okay. Thanks. [10:34] I'm just going to drop that note in [10:36] here. [10:54] Okay. [10:56] All right. Any other questions, [11:00] comments, anything about Chaos Cons? [11:08] Okay. Um, so the next one is me. I am [11:12] going to turn my video back on. So I [11:14] hope it's not choppy. Maybe start video. [11:19] There we go. Okay. Soh, [11:23] I'm going to try not to get emotional on [11:24] this, but um as some of you might know, [11:28] um some of you might not know, uh my [11:30] position here at Chaos is funded through [11:33] a grant from the Alpha Peace Loan [11:35] Foundation and they've funded this [11:37] position for 6 years uh almost 6 years [11:40] and um that funding round is now coming [11:43] to an end. So, um, they have asked us to [11:46] put together a proposal for one more [11:48] year of funding, but that is still up in [11:51] the air. So, we don't know what's going [11:53] to happen. Um, so I was kind of forced [11:56] to make a a difficult decision about my [11:59] future. And, um, I have decided that at [12:04] the end of March, I will be stepping [12:07] back from full-time chaos community [12:09] management. Um, I do have another [12:12] opportunity that is coming along that [12:14] has not been announced yet. So, I'm not [12:17] going to I'm not really at liberty to [12:18] say anything about that. But, um, yeah. [12:21] So, at the end of March, I will be [12:23] stepping back stepping back. Not [12:25] stepping away, just stepping back. I [12:28] will be around in some some capacity. [12:32] Um, you know, I'm not I mean, I love [12:34] chaos. I'm not going to just leave. So, [12:37] um, that is, if you're, uh, thinking [12:39] about that, I'm that's not the case. Uh, [12:42] there there is just a lot of unknowns. [12:44] So, we don't know what's going to [12:45] happen. Uh, we don't know what that [12:48] transition will look like if the funding [12:50] does come in. Um, we don't know anything [12:52] really. Um, but we have a little bit of [12:53] a buffer to figure it out. So, I just [12:56] wanted to let everybody know in the [12:58] community before um, the other thing is [13:02] announced probably in a few days, maybe [13:03] this week, I don't know. Um, but yeah, [13:06] so that's what's going on with me and [13:10] chaos. So, [13:12] >> you didn't cry. [13:13] >> I didn't. I'm very proud of myself. I [13:15] was Yeah, [13:18] >> I was getting a little choked up earlier [13:19] when I was thinking about it. I was [13:20] like, "Oh, [13:21] >> yeah." The anticipation and then the [13:23] delivery. [13:25] >> Yeah. So, [13:26] >> we can't say that we, you know, I mean, [13:28] we love you so much and thank you for [13:30] everything. So [13:32] >> yeah, it's it's um it's a big decision [13:36] obviously, but um but again, I'm really [13:38] happy that it's an open source project [13:39] and I can still contribute here and [13:42] there um as I can. So um that makes me [13:45] glad. So [13:47] >> yeah, [13:48] >> agreed. [13:49] >> I'm happy to answer questions if people [13:50] have them, if I can. I don't know if [13:52] I'll have the answer, but I can try. [13:54] >> Yeah, there's one big question that's [13:57] hanging out there, but you can't answer [13:58] it, so [13:59] >> No. [14:02] Yeah. [14:04] >> Hey, Elizabeth. [14:06] This is Adena. [14:09] I don't know how to feel about this, but [14:11] I I just want to say thank you. Thank [14:14] you for your good work. Ah, it's been [14:18] been a very good um [14:21] relationship with you. I don't even know [14:24] what's going to happen, but again, [14:26] fingers crossed, you know. [14:30] Thank you so much. Thank you. [14:31] >> Thank you for saying that. I appreciate [14:33] you. Now I'm going to cry. Thanks Eddie [14:34] and for making me cry. [14:37] Oh my goodness. So yeah, [14:41] thank you for saying that. That's very [14:43] kind of you. [14:45] >> You're going to do great. [14:47] >> Thanks, Matt. [14:48] >> And I don't I was like, you know, I I [14:50] don't know if we can really have We [14:51] could try to have a party, but it's like [14:53] going to be on Zoom. [14:55] >> Yeah. [14:55] >> We don't want to have cake and cookies [14:57] and stuff like that. [14:59] Everybody get your own and we'll all [15:00] just eat them together. How's that? [15:04] >> Really? I think we should I think we [15:07] should have a party. [15:09] >> Zoom party. [15:11] >> I mean, we at least have to do that. We [15:13] We did have a party once where we drew [15:14] donuts and put sprinkles on them. [15:16] >> Ah, I remember. It was like a Christmas [15:18] holiday thing and we had like a [15:20] whiteboard. Yeah, I remember that. That [15:22] was fun. [15:22] >> We could do another doughnut party. [15:24] >> We could I love it. I love the doughnut [15:26] party. All [15:30] right. [15:32] Anybody else have any questions? [15:39] I was kind of curious like are you um [15:41] open to the idea of like people uh if [15:44] people are interested like in your sort [15:46] of transition period to stepping back [15:48] like having some people kind of shadow [15:51] maybe some of the kinds of work you've [15:52] been doing in Chaos and see if that [15:54] helps anyone like spark anyone's [15:56] interest in [15:58] like helping kind of take over some or [16:00] like various parts of it because I know [16:01] you do like probably 15 different things [16:03] but like maybe if there's a way to kind [16:05] of have some people who've been around [16:07] in chaos for a little bit like take one [16:10] or two of those and and kind of [16:13] like help take some of that workload off [16:15] if you if you don't have the capacity to [16:17] to do all of it anymore. [16:20] >> Yeah, that's a that's a really good [16:21] idea. Um I think right now again it's [16:24] like everything's kind of just up in the [16:26] air. Um but I definitely think that [16:29] there is space for that. Yeah, for sure. [16:31] I think um we could uh talk about that, [16:35] what that would look like, how you know, [16:36] how we want to do that. Um we do have a [16:38] little bit of time um because I wanted [16:41] to kind of announce this sooner than [16:43] later also. Um uh so we do have some [16:47] time to kind of sort out what the future [16:49] can look like. Um yeah, sorry I don't [16:53] really I don't really have an answer, [16:54] but I I like that idea. Yeah. [16:58] >> Yeah. not knowing and [17:01] um it's probably a smart thing to do [17:04] what Adrian brings up like [17:06] >> edge a bit on that and think about how [17:10] some of your like maybe most critical [17:12] roles [17:14] >> you know that you would look at and be [17:15] like okay this one's got a [17:17] >> maybe you know versus others that maybe [17:20] could I don't know if they weren't [17:23] attended to for a little while might [17:25] survive a bit Yeah. Yeah. [17:28] >> Yeah. I was also thinking like too maybe [17:30] even finding figuring out if there's any [17:32] roles that maybe obviously like Matt [17:34] said, prioritize the critical things, [17:36] but also like I I know a large part of [17:38] chaos is like research and university [17:40] focus. Maybe if there's certain roles [17:42] that you can kind of split off that [17:43] would be potentially in alignment with [17:46] certain majors or certain tracks of [17:48] research that that could lead someone [17:50] who's doing research in a particular [17:52] area to maybe take that over and then [17:54] they wouldn't need necessarily any [17:55] funding because they're maybe already [17:56] funded for their research or they're in [17:59] school and and don't necessarily need [18:01] funding or things like that. So [18:04] >> a lot of flexibility. [18:07] >> Yeah, that's a really good idea. I like [18:10] that. [18:17] >> So, a few things I think Elizabeth um [18:20] like not more work on this announcement, [18:23] but like letting more than just the nine [18:27] of us in this call know [18:30] >> and then [18:30] >> Yeah, agreed. [18:31] >> Probably the board as well. Like sending [18:34] something to the board. Yeah, that's a [18:37] good idea, too. [18:38] >> Would make sense. [18:40] >> I'll do that right after this meeting. I [18:42] I was going to um post something in the [18:46] uh general channel and in the working [18:48] group channel. Um and I could just post [18:51] to the board mailing list to just let [18:52] everybody know. [18:53] >> That's what I was thinking. That's [18:56] >> okay. [18:57] Okay. [19:00] Yeah. So, y'all heard it here first. [19:09] Okay. Anything else before we kind of [19:11] move on? [19:14] >> We're all happy for you. [19:15] >> Oh, thank you. Thank you. [19:17] >> We really are. [19:18] >> Thanks, Matt. [19:20] >> Times change and, you know, paths go [19:23] where they go. [19:24] >> Yeah. Yeah. I mean, yes, they do. Um, [19:27] and again, you know, because it's an [19:29] open source project, I can contribute [19:32] whenever I want or whenever I can. So [19:34] that's great. Whereas if it was a [19:36] company, you know, you can't really go [19:38] back and still work there sometimes. So, [19:40] so I'm very very I feel very blessed [19:43] that, you know, this is a a project that [19:45] is still open and can still contribute. [19:49] >> I might even have a little more freedom [19:50] to contribute in different ways. So [19:54] there you go. Would that be weird? [19:55] >> Yeah. [19:58] Uh anyway, um yeah. So there we go. [20:05] And I'm also, you know, if anybody has [20:07] any questions or, you know, wants to ask [20:09] something privately, of course, hit me [20:11] up on Slack. I'm happy to chat with [20:14] anybody about anything as as far as I [20:16] can as far as the information that I [20:18] have. Um, yeah, [20:21] I love you all. You all know that. But I [20:23] do I love you all very much. So, thank [20:25] you for Yeah, you'll see it in my [20:27] general channel. It'll be all sappy and [20:30] stuff. So yeah, [20:33] >> lot of emojis. [20:34] >> Yes. Oh yeah, you know it. You know [20:36] there's going to be some hearts [20:37] involved. So [20:40] >> much love to you all. H Yeah. [20:45] Okay, I'm going to move on because I [20:47] will start to cry. So [20:49] >> Okay. And I have to drop off because I [20:50] have [20:51] >> And you got to drop off anyway. Yeah. [20:54] >> Okay. See you. [20:54] >> Um so vouching for I don't know how to [20:58] pronounce this. Fascia, Fageia, I don't [21:01] know how to pronounce it. Um, it is uh [21:04] so some folks from the Chaos Asia [21:07] community approached me and asked me if [21:10] um we would be okay with vouching for [21:14] this group that they're also part of. [21:16] Um, so [21:19] the rules of GSOC now say that in order [21:22] for you to join as a new org, you have [21:24] to have a recommendation from somebody [21:26] else who has participated in GOC before. [21:30] So, um, I don't think it's an issue. I [21:33] don't see where why it would be, but I [21:35] just wanted to bring it here to the [21:36] community just to like double check and [21:39] make sure that, you know, if anybody [21:41] sees something that I'm missing, like I [21:43] don't think that that would be a problem [21:45] to kind of just vouch that yes, this is [21:46] a an org that will, you know, [21:48] participate in good faith and be awesome [21:51] and all of that stuff. I mean, the whole [21:53] their whole thing is a uh is inclusivity [21:56] and, you know, helping women in the uh [22:00] Indian region. So [22:02] >> you said this came from, sorry, you said [22:04] this came from um some of our like like [22:08] people in like the Chaos Asia. [22:10] >> Uhhuh. [22:10] >> type place. Um I when I initially saw [22:13] this in the dock, I read it as as Foss [22:15] Asia, which is an or with a very similar [22:18] acronym and probably a very similar [22:19] mission just for a different community. [22:22] Um [22:23] >> I just wanted to double check that this [22:26] is the correct thing. Yeah, this yes, I [22:29] think this is the correct thing. But now [22:32] that you say that, now I'm [22:33] secondguessing myself. So I Let me make [22:37] sure. [22:38] >> That's okay. Um and so I asked just cuz [22:41] I I when I was at Fosdam this last [22:43] weekend, um I actually I walked I went [22:46] by the Fosasia booth. So they not this [22:48] or but the other one I was thinking of. [22:50] Um and they were selling these like [22:52] little LED like if you go to conferences [22:54] and you see people with little LED [22:55] badges. I think this is they're one of [22:56] the main ones that sells those. Um, and [22:59] there's a whole lot of open source [23:00] around that. Um, [23:03] so I mean that was I was going to say [23:05] that's my experience with them, but I [23:06] realize this is probably a different [23:07] organization. Um, but either way, a [23:10] general comment that would apply to [23:11] either is um I know in the at least last [23:14] year and I assume this year too, even [23:16] though we're not participating, um [23:18] there's been a large sort of influx of [23:20] AI people like people with AI applying [23:24] to Google Summer of Code and things. Um [23:27] I think that's been the one of the [23:28] primary drivers of why we've had like [23:32] we're now at 80 open poll requests on [23:34] Augur since October. largely I would [23:37] assume because of people who who saw [23:39] that we've participated in Google Summer [23:40] of Code in the past and are trying to [23:42] kind of get a leg up and and get get [23:44] some contributions in uh in the hopes of [23:47] getting accepted. Um, so I I part of me [23:51] is a little bit skeptical of of like we [23:54] want to make sure like if if we're going [23:55] to be vouching for either of these orgs [23:58] to join Google Summer of Code that that [24:00] they're maybe aware that they might get [24:02] flooded like that and that that's [24:04] something they're okay with or prepared [24:06] to handle. Um, [24:08] >> yes. Yes, that is an excellent point. [24:10] And I did talk to so Kana had reached [24:13] out to me just to kind of get a feel for [24:15] what our experience was from chaos. Um [24:18] just because they were considering it. [24:20] And so that's exactly what I told that's [24:22] exactly what I told her of like you just [24:25] have to be ready because it will bring [24:26] an influx not just this year but [24:28] probably in future years as well because [24:30] people will use that list next year to [24:33] kind of get ahead. So um they I think [24:37] they are set up for that. um they are I [24:40] don't know that they'll get the the um [24:44] uh volume that we do um just because we [24:47] are a little more global and they're [24:49] like a little more you know um focused [24:52] on the region and uh kind of their [24:54] mission. So they might not have that [24:57] problem as much as we did but um I did [25:00] Yeah. Yeah. Adrianne I did definitely [25:01] mention [25:03] the experience of Yeah. and why and why [25:06] we're not participating again this year, [25:08] you know. [25:10] >> Yeah. So, um also are they hoping to get [25:13] in Google Summer of Code this 2026 [25:16] cycle? [25:17] >> I think the application for that closes [25:18] like uh probably [25:23] in a few hours if not now. [25:25] >> What? Oh, [25:26] >> or gaps are until February 3rd, 1800 [25:29] UTC. [25:30] >> Oh my gosh. [25:31] >> Oh, well that's a great question then. I [25:33] don't know. I had assumed this year. I [25:36] did not realize that that deadline was [25:37] already here. So [25:39] >> yeah, the application period started [25:41] just before Chaos Con Fosdam and it ends [25:43] just after. So it was like [25:45] >> super inconveniently timed for for us if [25:47] we wanted to apply. But [25:48] >> yeah. Okay, that's an excellent um [25:52] question. [25:53] Um if hoping for 2026 [25:57] deadline is today, like in a few hours. [26:02] Yeah, I will ping them. I, you know, the [26:05] between the time zones though, I don't [26:07] even know if anybody's really around. [26:08] So, okay, I'll just ping Divia and let [26:11] her know um [26:14] Yeah. and ask her about about the [26:16] deadline. I don't I don't know about [26:19] that. That's a great question. That's a [26:21] great point. [26:30] I I wanted to ask if we know any of the [26:34] team members, but then I think I s um I [26:37] site Kitana. [26:39] >> Yeah. [26:41] >> Yeah. And um Divia Divia is the one who [26:43] uh pinged me also about this. So I don't [26:46] know if Divia's directly involved or [26:49] indirectly involved, but I know she's [26:50] been in the loop as well. [26:53] >> Okay. Okay. [27:00] Okay. Well, I'll find out what's [27:02] actually going on, what their intentions [27:05] are for this year. Um, maybe they [27:08] already did something. I don't know. I [27:10] don't know. Well, I'll figure it out. [27:19] Okay. Thanks everybody. I appreciate [27:22] that very much. [27:25] Um, okay. And then this was also on the [27:28] agenda. I'm not sure who put this on [27:30] there, if they're here or not. [27:35] Um, I I know this is a thing. This [27:38] document is huge. It's very unwieldy. [27:41] Um, I kind of got stuck with archiving [27:44] because someone brought up the fact that [27:47] uh Google Docs keeps a history of all of [27:50] the changes. So even if I delete [27:53] everything from you know earlier uh from [27:57] 2025 this the the Google doc could still [28:00] be big and chunky. Um so there was a [28:03] proposal to to decide I guess between do [28:06] we keep this doc just go with the big [28:09] bulky history of all time or do we start [28:12] a new doc every year which would change [28:15] the links everywhere. [28:19] How long have we been using the current [28:21] doc? [28:22] >> I uh I think just since the beginning of [28:25] 2025. [28:27] Um actually that's is that right or have [28:30] we been did we do that in 2024? [28:34] I don't know. Let me look. [28:40] It's a good question [28:44] >> because I also wonder like if we're [28:45] going to have to change the links, I [28:46] wonder if it would be helpful to like [28:49] put make some kind of like shortcut like [28:52] a page on the chaos website or like [28:54] chaos community/minut or something that [28:57] redirects to the doc. So it's like we we [29:00] use that minutes page everywhere and [29:03] then we can update it like sort of like [29:05] our own little DIY URL shortenerish [29:08] thing. Mhm. And just make [29:11] >> then if we do cycle it every year, [29:12] that's an easy easy fix in one place [29:16] once we get around to changing [29:18] everywhere we have it shared. [29:21] >> Yeah. [29:23] Um [29:25] that's a great question. I I'm not sure [29:28] when we switched over. We could go back [29:30] and look uh when we when we first [29:32] created this doc. I don't actually [29:34] remember. [29:36] I'd have to go back and look through the [29:37] minutes to find out where we talked [29:39] about it. [29:39] >> I see the last something says last [29:41] meeting of 2023 just when you were [29:42] scrolling down to the bottom. So maybe [29:44] it's [29:45] >> Yeah. [29:45] >> Mega doc since vaguely then. [29:48] >> Well, maybe we So what we did was we um [29:53] we copied all of the current ones into [29:56] that big dock. [29:59] So I am not sure. [30:00] >> Oh, okay. So it was like the community [30:02] used to be a separate dock. [30:04] >> Yes. Yes. Everybody had their own. Um, [30:07] so we decided to just bring them all [30:09] together because, uh, it was hard to [30:12] find them all separated out. So, we [30:15] brought them all together so there would [30:16] be just one link that people had to [30:18] remember to get to the the minutes. So, [30:21] um, [30:22] >> yeah, I personally like having the one [30:23] link, but like I can see how like if I [30:25] mean I've got a pretty decent computer [30:27] and a pretty solid internet connection, [30:28] so it's not usually an issue for me. [30:30] >> But I suspect if if our goal is trying [30:32] to include people in like other [30:34] countries, other time zones, other [30:36] levels of internet quality, like [30:38] >> yeah, [30:39] >> maybe even cycling it year by year or we [30:41] could do like every six months [30:44] maybe. I don't know. Um, [30:46] >> yeah. [30:48] Yeah, that's a good idea. Um, also we do [30:51] have these inactive ones in here which [30:53] we can take out. Uh, that will help a [30:55] little and just move them to a separate [30:57] doc and link at the top you know we how [31:00] we have here. So okay let me uh let me [31:04] think about it a little more and then [31:06] next week I'll come back with a plan. Um [31:10] I because I also am not sure about that [31:12] history how much like how much does that [31:16] bog down? If it's not much, u then it's [31:19] not a problem. But we haven't done I I [31:22] haven't had time to do any research on [31:23] it. So, someone just brought that up as [31:25] a as a potential kind of flag that that [31:28] might also not be helping with, you [31:30] know, with the [31:31] >> They also I potentially wonder if they [31:33] could have been talking about history in [31:35] terms of we just stack each meeting on [31:37] top of the last one, [31:39] >> but I think Google Docs also keeps a [31:40] history too. So I don't [31:42] >> Yeah, I think it was more [31:45] >> Yeah, it was more about the versions [31:47] that it keeps like all of the versions [31:49] and so [31:50] >> you can disable that. [31:51] >> Uh I don't know. Maybe [31:54] >> like it can't even load this. Yeah, [31:57] >> someone else might have had things. [32:01] >> Yeah, I will come back with this. Oh, [32:06] how do I get back? Oh, [32:10] okay. [32:12] Okay. [32:14] Yeah, we'll come back to it next week. I [32:16] I do want to do a little bit of research [32:18] on how much that matters. You know, if [32:21] it doesn't matter that much, then um [32:24] then we it might be a non- problem, but [32:26] I know we didn't really get a chance to [32:28] figure that out. So, I will do that [32:32] for next week. Um I do know what uh [32:35] Eddie Inca, I want to give her time to [32:37] talk about this because we we did not [32:38] have time last time and I should have [32:39] bumped this up a little bit. I'm so [32:40] sorry. Um, but let me turn it over to [32:42] you, Ada. Go for it. [32:45] >> I I actually sent you a message, but is [32:47] it okay to move it to next week? [32:50] Um, [32:52] >> yeah. Okay, we can certainly do that. [32:56] >> Yes, [32:58] thank you. [32:59] >> Yeah, no worries. I just want to give [33:02] you space. Oh, and I just see the ping [33:03] there on my chat. Sorry. Sorry. [33:09] Okay. Well, now we have a little bit of [33:12] extra time if we do want to move this to [33:14] next week. So, um, does anybody have [33:16] anything else to put on the agenda? [33:30] And there were crickets. I guess not. [33:35] Okay. Well, I will go ahead and stop [33:38] sharing. [33:40] Um, yeah, if we don't have anything [33:43] else, we can go ahead and close the [33:46] meeting out. Any any final thoughts? [33:56] >> Hi, I wanted to ask a question. Hi, good [33:58] evening [34:00] >> everyone. Okay, evening here Nigeria. [34:02] So, um, it's one year since I joined [34:04] Chaos. I joined chaos on 27th of January [34:06] last year. Um I've contributed to like [34:10] just the conferences but I wanted to ask [34:13] if there are other ways I can contribute [34:15] to actual opensource projects besides [34:18] just contributing to like conferences. [34:22] Yeah, that's my question as a designer. [34:24] Yeah, thank you. [34:26] >> Yeah, that's a great question. Um [34:30] yeah, that's a really good question. [34:33] I I'm trying to think if the um Adrian, [34:36] you might have an answer to this. I [34:37] don't know. Do you know if there are [34:40] issues with eight knot that could use uh [34:42] designer help? [34:44] >> Uh I think actually so we [34:48] probably a month or two ago now. I think [34:50] we we actually ended up landing a big [34:53] redesign of 8 knot [34:55] >> based on a design that was made by the [34:56] Chaos Africa design team. Um, so I think [34:59] it's already had a a large look. I think [35:04] >> I heard some mild conversation uh pre [35:07] Chaos Con about I think where Cali was [35:09] interested in potentially having some [35:12] design people look at the augur UI. Um, [35:17] I don't know how far that really got [35:20] down the planning process. [35:22] Um, but I mean if if you've got [35:25] feedback, like if if anyone wants to go [35:27] look at either of them and and like give [35:30] give feedback, like sketch some stuff up [35:33] or whatever, like I mean contributions [35:35] welcome. Um, [35:38] and I I can I can help kind of be part [35:40] of those conversations and steer things. [35:42] um if if anyone who's into design wants [35:45] to kind of chat with Cali and see what [35:47] she had in mind or just propose sort of [35:50] ad hoc changes and things like that, but [35:53] I don't think there's any current major [35:55] plans um [35:58] for on either one, but happy to chat. [36:02] >> Ununice, are you um how are you how [36:04] would you feel about working on like [36:06] some frontend stuff versus like creating [36:08] assets for things? So when you say front [36:12] front end, do I have to write code? [36:17] >> You probably don't have to. I think that [36:18] was that the largely I think I think the [36:20] designs we got for the eight knot the [36:23] big eight knot redesign like that was [36:25] just we were we were looking at a Figma [36:27] doc and we lar I think uh we had an [36:30] intern on our uh our team that largely [36:34] did like a big first pass of it I think [36:37] largely with AI and then we've we sort [36:40] of took that large PR and broke it up [36:41] into small phases and and [36:44] actually sort of reviewed it in detail [36:46] and landed it So, I think I think it's [36:49] really up to like whatever you're [36:50] comfortable with. Like if you if you'd [36:51] like to learn some basic like HTML and [36:54] CSS, like I'd be happy to help. Um, but [36:57] like you you could also like if if [36:59] there's ideas that you have and you want [37:01] to just sketch them up in in a design [37:03] tool that that works too. I think I [37:04] think the biggest thing is really just [37:06] being in contact with whichever team [37:08] maintains whichever thing that that [37:10] you're looking to help with design-wise [37:11] and just making sure that everyone's [37:14] road maps are aligned and that that like [37:17] everyone's sort of in agreement on like [37:18] which direction we want to go and and [37:21] hey yeah we'll we'll make room on the [37:23] timeline to implement it if if someone [37:25] can help design it or things like that. [37:30] >> Okay, thank you. But for this particular [37:32] one, um, should I reach out to you to [37:34] look at your current design or should I [37:37] reach out to Khali? [37:39] >> Um, [37:40] the current so eight not uh there's I [37:43] can put a link in the chat to uh the [37:45] instance [37:47] I help run. Um, [37:52] that that's the one that's I think most [37:54] up to date with the current 8 code. I [37:56] know the chaos instance is also on the [38:00] new redesign um as well. So you can you [38:04] can just explore like if you want to [38:05] just go and play with 8 knot without [38:07] having to like run it locally you can [38:09] use those um [38:12] and then yeah like if you have if you [38:14] have feedback uh the the WG augur 8 knot [38:16] channel in in chaos slack is probably a [38:18] good place to start just being like hey [38:20] like I found a found a bug or or you [38:23] could file a GitHub issue. Um, [38:28] yeah, I think those are probably good [38:29] places to get started. And then I'm sure [38:31] Callie's Callie's more attentive to the [38:33] eight knot side than than the augur [38:34] side, but u I I try and keep an eye on [38:38] everything, mostly augur, but [38:42] it'll it'll get to the right people if [38:43] you reach out. So, [38:46] >> thank you so much, Adren. [38:49] >> Yeah, no problem. [38:55] Okay. Anything else before we close the [38:57] meeting out? [39:04] All right. Well, everybody have a good [39:06] rest of your day and I will see you on [39:08] Slack and also see you here next week. [39:11] Bye, everybody. [39:14] Thank you, Elizabeth.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, Feb 3, 2026.md|CHAOSS Weekly Community Call, Feb 3, 2026 by YouTube]] ## Highlights - that. We are going to be sending out a postevent survey. Jay is working on that. We basically took last year's repurposed it added maybe one question I think about the uh two questions we added about the venue specifically and about lunch because we did provide lunch this time which we typically don't. So we added those two and we'll be sending that out um pretty soon. Very excited to see what what the feedback is um and how we can be better next year. Uh we did have um a lot of folks check ([View Highlight](https://read.readwise.io/read/01kpb3vgs30dzyy6b24h4khbh5)) - Tags: 👻 ai highlighted - we can even make our own maps if we need to, our own signage. But the again, the venue is very helpful at helping people find their way. So, hopefully everybody was okay with that. >> Okay. Anybody have questions, comments? >> Is open source summit in North America like has that been declared? Oh >> yeah, there's a there's a thread about that. Yeah. In chaos con committee. >> Okay. Yeah. Okay. Well, that I mean we ([View Highlight](https://read.readwise.io/read/01kpb3vgsvj5kqrhwt77brzmd2)) - Tags: 👻 ai highlighted - wouldn't organize for that anyway because it's in May. >> Too soon. Yeah. >> Happen. >> Yeah. For for those who don't know, um, Open Source Summit North America is in Minneapolis, Minnesota, which is a little bit, um, unsettled, uh, if I can say that right now. It's not very I have feelings. I have feelings about it, which I don't know if I'll share here because it's recorded, but um, yeah, I would be glad if we did not ([View Highlight](https://read.readwise.io/read/01kpb3vgtkvgc2xase8e3nn6w8)) - Tags: 👻 ai highlighted - Um, you know, I'm not I mean, I love chaos. I'm not going to just leave. So, um, that is, if you're, uh, thinking about that, I'm that's not the case. Uh, there there is just a lot of unknowns. So, we don't know what's going to happen. Uh, we don't know what that transition will look like if the funding does come in. Um, we don't know anything really. Um, but we have a little bit of a buffer to figure it out. So, I just wanted to let everybody know in the community before um, the other thing is ([View Highlight](https://read.readwise.io/read/01kpb3vgvm2331eetmr50p94pw)) - Tags: 👻 ai highlighted - Yeah. So, y'all heard it here first. Okay. Anything else before we kind of move on? >> We're all happy for you. >> Oh, thank you. Thank you. >> We really are. >> Thanks, Matt. >> Times change and, you know, paths go where they go. >> Yeah. Yeah. I mean, yes, they do. Um, and again, you know, because it's an open source project, I can contribute ([View Highlight](https://read.readwise.io/read/01kpb3vgx9fd897ezcc5d7kzfb)) - Tags: 👻 ai highlighted - Yeah. Yeah. Adrianne I did definitely mention the experience of Yeah. and why and why we're not participating again this year, you know. >> Yeah. So, um also are they hoping to get in Google Summer of Code this 2026 cycle? >> I think the application for that closes like uh probably in a few hours if not now. >> What? Oh, >> or gaps are until February 3rd, 1800 UTC. ([View Highlight](https://read.readwise.io/read/01kpb3vgznymb8h92dnbjvs6ex)) - Tags: 👻 ai highlighted - give feedback, like sketch some stuff up or whatever, like I mean contributions welcome. Um, and I I can I can help kind of be part of those conversations and steer things. um if if anyone who's into design wants to kind of chat with Cali and see what she had in mind or just propose sort of ad hoc changes and things like that, but I don't think there's any current major plans um for on either one, but happy to chat. ([View Highlight](https://read.readwise.io/read/01kpb3vh49djezfr4qs1c7gkvk)) - Tags: 👻 ai highlighted