CHAOSS Weekly Community Call, Jan 13, 2026 ![rw-book-cover](https://img.youtube.com/vi/sCQBNacQ3eU/maxresdefault.jpg) ๐Ÿ”— **Source:** [CHAOSS Weekly Community Call, Jan 13, 2026](https://www.youtube.com/watch?v=sCQBNacQ3eU) > [!note]+ Document Notes > tags: #chaoss #open-source #community #badging #chaos-con #ospo #funding > author: CHAOSS Community > source: YouTube > reference: https://www.youtube.com/watch?v=sCQBNacQ3eU > date created: 2025-01-13 18:30 > > # ๐Ÿท๏ธ Title: CHAOSS Weekly Community Call, Jan 13, 2026 > <!-- deep-read:sections start --> ## ๐Ÿงฐ Action Inbox - [H1] Review CHAOSS Con schedule on TeamUp platform โ€” new interactive calendar format #chaos-con - [H2] Update dependency vulnerabilities in badging system โ€” ongoing security maintenance #badging - [H3] Connect with funding working group members at CHAOSS Con โ€” networking opportunity #funding ## ๐Ÿงญ 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/) - [OSPO Curious](https://ospocurious.org/) ## ๐Ÿ“ Summary - What happened: Weekly CHAOSS community call covering working group updates, badging status, and CHAOSS Con preparations - Why it matters: Shows active community coordination and evolution of open source health metrics - Key stakeholders: CHAOSS community members, OSPO professionals, academic researchers - Risks and tradeoffs: Working group consolidation may reduce specialized focus but improves efficiency - Bottom line: CHAOSS Con 2026 represents significant growth with new accessibility features and professional scheduling ## ๐Ÿ“– Main Content The CHAOSS community held its weekly call discussing organizational updates and conference planning. Key changes include merging the University Working Group into the Research and Science Working Group due to overlap, with displaced members joining OSPO Curious meetings. The badging program maintains steady but low volume with three current applications. CHAOSS Con 2026 shows significant evolution with a professional TeamUp calendar system, multiple rooms, interactive workshops, and notably includes a hearing-impaired speaker, marking new accessibility commitments. ## ๐Ÿ—’๏ธ Notes #### โฑ๏ธ [00:00](https://youtu.be/sCQBNacQ3eU?t=0) โ€” [H1] Weekly community call opening - Key idea: Regular Tuesday community gathering with appreciation for attendance - Evidence: "Really great to see everybody... you could be doing anything else and you chose to be here" #### โฑ๏ธ [02:30](https://youtu.be/sCQBNacQ3eU?t=150) โ€” [H2] Working group restructuring update - Key idea: University Working Group merged with Research and Science Working Group - Evidence: "Rolling the university working group into the research and science working group since there's a lot of overlap" #### โฑ๏ธ [03:45](https://youtu.be/sCQBNacQ3eU?t=225) โ€” [H3] OSPO Curious introduction - Key idea: Alternative community for displaced university working group members - Evidence: "OSPO meetings in curious... focused on open source program offices specifically at universities" #### โฑ๏ธ [05:20](https://youtu.be/sCQBNacQ3eU?t=320) โ€” [H2] Funding working group hiatus - Key idea: January meetings cancelled due to busy schedules, resuming February - Evidence: "January meetings have been cancelled because everybody's super busy" #### โฑ๏ธ [06:15](https://youtu.be/sCQBNacQ3eU?t=375) โ€” [H3] Badging program status check - Key idea: Current badging applications at low volume with three active requests - Evidence: "We just have three at the moment... There is no problem" #### โฑ๏ธ [08:30](https://youtu.be/sCQBNacQ3eU?t=510) โ€” [H2] Security vulnerability concerns - Key idea: Multiple dependency alerts requiring backend package updates - Evidence: "A lot of the dependabot things that are coming across with badging" #### โฑ๏ธ [09:45](https://youtu.be/sCQBNacQ3eU?t=585) โ€” [H1] CHAOSS Con schedule reveal - Key idea: New professional TeamUp calendar system showcasing conference growth - Evidence: "We switched our... schedule over to teamup... indication of how far Chaos Con has come" #### โฑ๏ธ [12:00](https://youtu.be/sCQBNacQ3eU?t=720) โ€” [H2] TeamUp calendar features demonstration - Key idea: Interactive scheduling with filtering, multiple views, and session descriptions - Evidence: "You can click on this... filter by keyword... different look" #### โฑ๏ธ [15:30](https://youtu.be/sCQBNacQ3eU?t=930) โ€” [H3] Calendar reusability for future events - Key idea: TeamUp system can support up to five calendars for future conferences - Evidence: "Definitely for future Chaos Cons or workshops or whatever else we want to use it for" #### โฑ๏ธ [16:45](https://youtu.be/sCQBNacQ3eU?t=1005) โ€” [H2] Manual customization efforts - Key idea: Time-intensive process of creating unified visual presentation - Evidence: "I did the circle too... manually do these in Canva... timeconsuming" #### โฑ๏ธ [18:20](https://youtu.be/sCQBNacQ3eU?t=1100) โ€” [H1] Accessibility milestone announcement - Key idea: First hearing-impaired speaker represents significant inclusivity advancement - Evidence: "Heart of hearing, hearing impaired deaf speaker... push us to be more inclusive and accessible" ## ๐Ÿ“š References - [CHAOSS Community Website](https://chaoss.community/) - [OSPO Curious](https://ospocurious.org/) - [TeamUp Calendar Platform](https://teamup.com/) ## ๐Ÿ—ฃ๏ธ Paraphrase - CHAOSS consolidated university-focused activities into broader research groups while redirecting academic OSPO members to specialized communities - The badging program maintains steady operations with manageable application volumes and ongoing security maintenance needs - CHAOSS Con 2026 represents organizational maturity through professional scheduling tools and commitment to accessibility inclusion ## ๐Ÿ“ฐ Newsletter The CHAOSS community continues evolving its organizational structure while preparing for an ambitious 2026 conference. This week's call highlighted the merger of university and research working groups, demonstrating how open source communities adapt their governance as they mature. Most exciting is CHAOSS Con's new accessibility commitment with their first hearing-impaired speaker, setting important precedents for inclusive conferences. The new TeamUp calendar system showcases significant conference growth with multiple tracks, interactive workshops, and professional presentation. This evolution from simple spreadsheets to sophisticated scheduling tools reflects the community's expanding impact in open source health metrics. Resources: [CHAOSS Metrics](https://chaoss.community/metrics/), [Badging Program](https://chaoss.community/diversity-and-inclusion-badging/), [OSPO Curious](https://ospocurious.org/) ## โœ… Action Items #### Community - Contributors: Implement accessibility features for hearing-impaired conference attendees - Maintainers: Address dependency vulnerabilities in badging system infrastructure - Sponsors: Support expanded conference format with multiple rooms and interactive sessions #### WordPress - Accessibility: Document inclusive conference planning practices for hearing-impaired speakers - Community: Apply CHAOSS badging program learnings to WordCamp accessibility improvements - Meta: Consider TeamUp calendar integration for WordCamp scheduling systems ## ๐Ÿงช Hypotheses - Working group consolidation reduces administrative overhead while maintaining specialized expertise through cross-community collaboration - Professional scheduling tools increase conference attendance and participant satisfaction through improved user experience - Explicit accessibility commitments create sustainable infrastructure for future inclusive events - Community-driven metric development scales more effectively than centralized approaches ### ๐Ÿ“Š Methodology - Track attendance and engagement metrics before/after working group consolidation - Survey participant experience with TeamUp calendar versus previous scheduling methods - Measure accessibility accommodation success through post-conference feedback - Compare badging application quality and processing times across calendar years ### โ“ Questions - How do community members navigate multiple overlapping working groups and external communities? - What technical accommodations ensure meaningful participation for hearing-impaired conference speakers? - Can the TeamUp calendar model scale to larger multi-track conferences with hundreds of sessions? ### ๐Ÿ”ฎ Future Research - Long-term impact of working group consolidation on specialized domain expertise - Effectiveness of cross-community member migration between CHAOSS and OSPO Curious - Accessibility accommodation models for distributed open source conferences ### ๐Ÿ’ก Implications - Practice: Community organizers need flexible governance structures that can evolve with membership needs - Policy: Accessibility commitments require proactive infrastructure planning rather than reactive accommodations - Education: Professional scheduling tools reduce barriers to conference participation through improved information architecture - Funding: Working group consolidation may reduce resource requirements while maintaining output quality ### ๐Ÿง  Learning Styles Assessment Reading level estimate: 12th Grade #### ๐Ÿ‘€ Visual learners - Present: TeamUp calendar demonstration, multiple view options, color-coded sessions - Improve: Architecture diagrams showing working group relationships, visual timeline of organizational changes #### ๐Ÿ”Š Aural learners - Present: Video call format with verbal updates and discussion - Improve: Audio-only version of key announcements, podcast-style summary #### ๐Ÿ—ฃ๏ธ Verbal learners - Present: Clear definitions of OSPO Curious, detailed explanations of calendar features - Improve: Glossary of community terminology, analogy-based explanations of governance changes #### ๐Ÿงฉ Kinesthetic learners - Present: Interactive calendar demonstration, hands-on TeamUp exploration - Improve: Step-by-step working group transition checklist, practical accessibility planning guide #### ๐Ÿง  Logical learners - Present: Clear timeline of changes, logical rationale for working group consolidation - Improve: Decision trees for working group selection, metrics tracking organizational changes #### ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Social learners - Present: Community call format encouraging participation, collaborative conference planning - Improve: Breakout discussions for working group transitions, peer mentoring for new members #### ๐Ÿง˜โ€โ™€๏ธ Solitary learners - Present: Individual calendar exploration, self-guided TeamUp features discovery - Improve: Reflection prompts on community involvement, self-assessment tools for working group fit #### ๐ŸŒฟ Naturalistic learners - Present: Organic community evolution, adaptive governance structures - Improve: Ecosystem thinking about community relationships, sustainability planning for growth ### ๐Ÿ“Š Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive link text for calendar features - Improve: Alt text for calendar screenshots, ARIA labels for interactive elements #### Keyboard navigation - Present: Standard web controls for video playback, TeamUp keyboard support - Improve: Skip navigation for calendar views, keyboard shortcuts documentation #### Contrast and readability - Present: Standard video player controls, readable calendar text - Improve: High contrast calendar theme option, larger text size settings #### Text resizing and reflow - Present: Responsive calendar layout, scalable video player - Improve: Text-only calendar view option, zoom-friendly layout testing #### Media and captions - Present: Video recording available, transcript provided - Improve: Live captions during calls, downloadable transcript formats #### Forms and interactions - Present: Clear calendar filtering options, intuitive session selection - Improve: Form validation for session preferences, accessible error messaging #### Standards reference - Calendar interface should meet WCAG 2.2 AA for interactive content and time-based media ### ๐ŸŒ DEIB Assessment #### Cultural breadth - Present: Global community participation, multiple time zone considerations - Improve: Multi-language calendar interface, international accessibility standards #### Inclusive language - Present: Person-first language for hearing-impaired speaker, welcoming tone - Improve: Consistent terminology for accessibility features, avoid medical model language #### Neurodiversity support - Present: Multiple calendar view options, structured information presentation - Improve: Sensory considerations for conference planning, cognitive load reduction #### Representation - Present: Hearing-impaired speaker inclusion, diverse working group participation - Improve: Representation across disability types, varied communication preferences #### Psychological safety - Present: Appreciative tone, acknowledgment of volunteer contributions - Improve: Clear communication about accessibility accommodations, supportive transition messaging ### โœ… Logical Validity #### Strong reasoning - Deductive strength: Working group overlap leads to consolidation efficiency - Inductive strength: Past conference growth suggests continued expansion success - Causal reasoning: Professional tools improve participant experience - Analogical strength: Other communities' accessibility commitments provide guidance #### Fallacies - Appeal to novelty: Assuming new calendar system is better without evidence - Hasty generalization: Low badging volume may not indicate overall program health #### Tone of voice - Overall tone: Enthusiastic and appreciative with authentic community leadership style ### ๐Ÿ›ก๏ธ DARVO Analysis - Deny: No concerning denial patterns observed - Attack: No attacks on community members or critics present - Reverse victim/offender: No victim/offender reversals identified - Emotional cues: Genuine enthusiasm for accessibility progress and community growth ## ๐ŸŽฏ Conclusion The CHAOSS community demonstrates mature governance evolution through working group consolidation while advancing accessibility commitments for CHAOSS Con 2026. The transition to professional scheduling tools and inclusion of hearing-impaired speakers represents significant organizational growth. Practitioners should note how successful open source communities adapt their structures organically while maintaining core values of inclusivity and collaboration. ## ๐Ÿงฑ Refactor Appendix ### ๐Ÿ“š Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Working group consolidation improves operational efficiency > [!quote] CHAOSS Weekly Community Call by CHAOSS Community via YouTube. Published 2026-01-13. Accessed 2026-01-13. > "Rolling the university working group into the research and science working group since there's a lot of overlap." Demonstrates adaptive governance in open source communities. [view highlight](https://youtu.be/sCQBNacQ3eU?t=150#H1) #xref #articleseed ID:rw_chaoss_consolidation ### [H2] Professional scheduling tools indicate community maturity > [!quote] CHAOSS Weekly Community Call > "This right here is kind of an indication of how far Chaos Con has come." Infrastructure investments reflect organizational growth and professionalization. [view highlight](https://youtu.be/sCQBNacQ3eU?t=585#H2) #xref ID:rw_chaoss_tools --- ### ๐Ÿ”– Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Accessibility commitments require proactive infrastructure planning - Applies to conference organizing and community building contexts - Reference: 18:20 hearing-impaired speaker announcement - Links: [[Community-Governance]] [[Accessibility-Planning]] #### [Z2] Cross-community collaboration reduces specialized working group overhead - Relevant for communities with overlapping domains - Reference: 02:30 working group merger discussion - Links: [[Open-Source-Governance]] [[Resource-Optimization]] --- ### โœ๏ธ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Research OSPO Curious structure โ€” compare to TODO Group approach #fleeting #inbox - [F2] Document TeamUp calendar best practices โ€” reusable for other communities #fleeting #inbox - [F3] Create accessibility accommodation checklist โ€” hearing-impaired speaker support #fleeting #inbox --- ## Full Transcript [00:01] Hello everyone. It's Tuesday again. Here<br>[00:04] you are at the Chaos weekly community<br>[00:05] call. Really great to see everybody. I<br>[00:08] know I say that every time, but I<br>[00:09] honestly do mean it. It is really great<br>[00:11] to see you all. So, I'm glad you're here<br>[00:15] because you could be doing anything else<br>[00:16] and you chose to be here. So, we<br>[00:17] appreciate you very much.<br>[00:20] Oh, I don't want to do that. That's<br>[00:22] wrong. Hold on. Don't look.<br>[00:27] All right. Hold on. What's going on?<br>[00:29] Stop share.<br>[00:30] >> Did I share everything?<br>[00:31] >> Yeah, it was everything.<br>[00:33] >> Okay. Well, don't look.<br>[00:35] Maybe I'll just cut that out of the<br>[00:36] recording. Here we go. Okay,<br>[00:39] >> there we go.<br>[00:41] >> Real fast and try to log in.<br>[00:43] >> Super secret information. Not really. I<br>[00:45] got nothing.<br>[00:46] >> My life is so boring. I wish I had super<br>[00:48] secret information that I had to blur<br>[00:51] out. Not that important. Okay. Um, is<br>[00:55] there one thing you want to accomplish<br>[00:56] today?<br>[00:58] I don't know. Maybe there's a lot of<br>[01:00] things. But if you want to tell us<br>[01:01] something you're working on today,<br>[01:02] that'd be cool.<br>[01:05] I'm working on Chaos Con stuff.<br>[01:08] There we go.<br>[01:12] Damian, this seems like<br>[01:14] a lot of work and maybe more than just<br>[01:17] today.<br>[01:18] >> Uh, no. It seems like a lot of boring<br>[01:20] work and I tried to convince some AI to<br>[01:23] do it, but it didn't. So, I will have to<br>[01:25] manually do it.<br>[01:28] H man, I hate when people just, you<br>[01:31] know, don't want to do what you want<br>[01:32] them to do. Gosh.<br>[01:35] Well, I'm sure that you will solve all<br>[01:37] the problems and make amazing progress.<br>[01:40] I have all the faith in you. I know you<br>[01:42] can do it. Um whether you want to or<br>[01:44] not, right? So, okay. Yeah. Um okay,<br>[01:49] just a quick a couple quick um working<br>[01:52] group updates, funding, and university.<br>[01:54] Uh in case you missed it last week, we<br>[01:56] did have a discussion about rolling the<br>[01:58] university working group into the<br>[02:00] research and science working group since<br>[02:01] there's a lot of overlap. And then um<br>[02:04] the folks who aren't really in that<br>[02:06] space are going to go over to the OSPO<br>[02:08] meetings in curious. So we have taken<br>[02:10] those meetings off the calendar and<br>[02:12] we've um archived the minutes or moved<br>[02:14] them to inactive. I believe that the um<br>[02:18] Slack channel is still active though. Is<br>[02:20] that right?<br>[02:21] >> That's okay. I'll post again like just<br>[02:24] remind people of this.<br>[02:26] >> Okay.<br>[02:27] >> Um just to make sure that if if they're<br>[02:30] still kind of looking. My guess is is<br>[02:32] that at this point um most everybody who<br>[02:36] attends regularly knows and it was all<br>[02:39] good.<br>[02:40] >> Yeah. I just want to make sure in case<br>[02:41] anybody missed that and we're planning<br>[02:42] to attend.<br>[02:44] Uh Damian, go ahead.<br>[02:46] >> Uh what is curios?<br>[02:49] Oh. Um, let's let's find it. It's uh<br>[02:54] Nope, here it is. Oh, I had that tab<br>[02:56] open in something else.<br>[02:57] >> Damian, it's a group that is focused on<br>[03:00] open source program offices specifically<br>[03:03] at universities.<br>[03:05] Oh,<br>[03:05] >> okay. Uh, it's separated from to-do.<br>[03:09] What's that?<br>[03:10] >> It's separated from to-do group.<br>[03:12] >> Um, yeah, it's different from the to-do<br>[03:14] group which is kind of focused more on<br>[03:16] the corporate ospo side. There are<br>[03:18] sometimes representatives in fact I<br>[03:20] think maybe David did you say you were<br>[03:24] um to-do group as well<br>[03:25] >> to do I think to-do is broader it's it<br>[03:28] started out industry but I think it's<br>[03:30] broader um curious is definitely just<br>[03:33] research or academic focused<br>[03:40] >> right<br>[03:43] >> and it's funded by the Alfred Peace<br>[03:45] Foundation so it's it's completely<br>[03:46] separate from all the Linux foundation<br>[03:47] stuff,<br>[03:54] >> but there was a lot of overlap, so it<br>[03:55] kind of didn't make sense to splinter<br>[03:57] those conversations into two places. So,<br>[04:02] all right, any other questions about<br>[04:04] that for Matt?<br>[04:08] That was a good question. Thanks,<br>[04:09] Damian.<br>[04:12] Um, and then obviously no, well, not<br>[04:14] obviously, but there is a note here. no<br>[04:16] changes to the chaos OSPO working group.<br>[04:18] So, just to clarify that that is still<br>[04:20] in place. And um just a quick update on<br>[04:23] the funding meetings. The um January<br>[04:26] meetings, the two January meetings have<br>[04:27] been cancelled because everybody's super<br>[04:28] busy. They will return again in<br>[04:30] February. So, there you go. And I think<br>[04:34] a lot of those folks will be at Chaos<br>[04:35] Con, too. So, connect up with them if<br>[04:38] you are so inclined.<br>[04:40] >> Yeah. And there's also a funding uh dev<br>[04:42] room which is what a lot of the people<br>[04:45] are busy with at FOST.<br>[04:47] >> Excellent.<br>[04:50] Okay. I see Matt is in real time adding<br>[04:53] things to the agenda.<br>[04:54] >> Yeah, that was just something I've been<br>[04:55] seeing um like in Slack, you know, how<br>[04:58] the applications still come across. How<br>[05:02] is it still like what's the volume that<br>[05:05] we're seeing on the badging stuff right<br>[05:07] now? I will defer to Eddie Inca on that.<br>[05:10] Not to put you on the spot, Eddie Inca,<br>[05:12] but<br>[05:15] >> is she here?<br>[05:17] >> Oh, yeah, she's here.<br>[05:18] >> Hi, I miss. Sorry.<br>[05:20] >> Hi.<br>[05:27] >> Sorry. Yeah, we were just asking about<br>[05:29] the volume of badging requests if that's<br>[05:31] something that um because we still see<br>[05:33] them on GitHub, but we're just curious,<br>[05:35] you know, how how that's going, how what<br>[05:37] the volume is if there's a lot of folks<br>[05:39] who are still applying.<br>[05:41] >> Oh, okay. So, um I wouldn't say we have<br>[05:46] um a lot of volume. We just have three<br>[05:48] at the moment.<br>[05:50] Uh and I think uh we are good. There is<br>[05:54] no problem.<br>[05:56] >> Okay. Do you don't we have like a big<br>[06:00] push maybe a couple times a year where<br>[06:03] there's a whole bunch of applications<br>[06:06] that come in.<br>[06:10] >> Oh, okay. Um probably um into uh the mid<br>[06:14] year, not at the beginning.<br>[06:17] >> Okay.<br>[06:18] >> Forance um in December we didn't we<br>[06:20] didn't have a lot of vacations. In fact,<br>[06:22] there was rest.<br>[06:24] >> Sure.<br>[06:24] >> Yeah. Good.<br>[06:26] >> Okay. Yeah, I was just kind of curious<br>[06:28] how things were going, but sounds like<br>[06:31] >> Okay,<br>[06:31] >> just good. Okay, thank you.<br>[06:37] >> Um, but Matt, you did mention I I think<br>[06:40] I saw an issue you created about um<br>[06:43] getting a lot of messages around um<br>[06:46] securities and vulnerabilities.<br>[06:50] >> I haven't posted anything like that<br>[06:52] recently.<br>[06:56] Okay, I think I saw that. I just wanted<br>[06:59] to say um we are working on something at<br>[07:02] the back end and so we might just have<br>[07:05] to update some some packages.<br>[07:08] >> Okay. Oh yeah, there are a lot of I do<br>[07:11] know that a lot of the dependabot things<br>[07:14] that are coming across with badging. So<br>[07:16] maybe it's some of that. Okay.<br>[07:21] >> All right.<br>[07:21] >> Oh yeah, I did post that now that I<br>[07:24] think about it.<br>[07:27] I saw you.<br>[07:29] >> I'm done for the day.<br>[07:34] >> Okay.<br>[07:40] Any other questions, conversation before<br>[07:42] we go on?<br>[07:46] I see chat here. What's the chat?<br>[07:50] Oh, just the docs. Okay. Um, yeah. Okay.<br>[07:56] The only other thing that I wanted to<br>[07:59] let everybody know specifically about<br>[08:00] Chaos Con, and we can take time at the<br>[08:02] end to do our Chaos Con committee stuff<br>[08:04] as we do, but um I just wanted to show<br>[08:07] everyone cuz I think it's awesome. I'm<br>[08:09] going to humble brag a little. I think<br>[08:12] it looks um pretty cool. So, we switched<br>[08:15] our because we have multiple rooms,<br>[08:17] multiple things, interactive workshops,<br>[08:20] talks, a whole bunch of stuff going on<br>[08:22] at Chaos Con this year. So, we decided<br>[08:25] to move the schedule over to teamup. So,<br>[08:28] it's similar to our calendar. Um, I have<br>[08:32] a few things to fill in at uh a few<br>[08:34] details still to fill in, but um this is<br>[08:37] our schedule for Chaos Con. We have a<br>[08:40] lot a lot of stuff going on. Um I'm<br>[08:44] pretty excited. Uh just in case anybody<br>[08:46] hasn't been really involved in those<br>[08:48] conversations, there are a whole lot of<br>[08:50] stuff. um lots of talks, lots of<br>[08:52] workshops, guided discussions, birds of<br>[08:54] feather things. So, it should be a very<br>[08:56] exciting time and um I think that this<br>[09:00] right here is kind of an indication of<br>[09:03] how far Chaos Con has come. So, pretty<br>[09:06] excited to to be there and to see all<br>[09:08] this unfold.<br>[09:10] Well, thanks, Cali. Thank you. I still<br>[09:13] have a few, like I said, things to<br>[09:14] finish up mostly um at the bottom here.<br>[09:17] these last evening ones. I haven't put<br>[09:19] in the descriptions yet, but what is<br>[09:21] nice about this too is you can click on<br>[09:24] here. We'll look at Dawn's. So, you can<br>[09:26] click on this. There's about Dawn and<br>[09:28] then the session description is there.<br>[09:30] So, um that's a little bit easier, I<br>[09:33] think, for people to find where they<br>[09:35] want to go. You can also filter by<br>[09:38] keyword. So, if I want to see all of<br>[09:40] Dawn's talks, I would just do that. And<br>[09:43] then it will just show me all of her<br>[09:44] stuff which is right now two things.<br>[09:48] Um you can also focus by you know<br>[09:51] keyword. If you want to just see<br>[09:52] anything that's has to do with funding<br>[09:53] for instance you can see that there's<br>[09:56] one thing. I think that might be all. Oh<br>[09:58] something at the end. Yeah.<br>[10:01] Um and then of course you can and this<br>[10:03] is I'm going to put a little thing in<br>[10:04] here because this right here is not<br>[10:06] intuitive. Um theuler is by room. The<br>[10:10] day is by time of what all is going on<br>[10:13] at the same at a at a time. Um the<br>[10:16] timeline is by room also but across and<br>[10:20] time. So it's a little bit of a<br>[10:21] different look. And then a list is just<br>[10:23] a flatout list. Here's a list of all the<br>[10:25] things. So um yeah, it's a little bit<br>[10:29] this is not intuitive at all. So we<br>[10:32] might put a little thing here just to<br>[10:33] explain that for people.<br>[10:36] So yeah, exciting stuff.<br>[10:40] I'm excited anyway. So, if you see if<br>[10:42] anybody sees anything, if you're poking<br>[10:43] around and you see something that looks<br>[10:44] weird, please let me know. We were doing<br>[10:46] some testing yesterday and it was a<br>[10:48] little weird with the time zones and how<br>[10:49] it was displaying. So, yeah, just let me<br>[10:52] know. Will this page be re reusable uh<br>[10:56] for future chaos cons? For sure. Yeah,<br>[10:58] we have um with our uh teamup account,<br>[11:02] you can create um as long as it's up to<br>[11:05] five. So, we can have up to five<br>[11:07] different things in one calendar. So, as<br>[11:09] long as you keep it under five, we're<br>[11:10] good. Um, I think actually with our paid<br>[11:13] account, we can maybe expand that. Uh,<br>[11:16] but yeah, you can create a calendar for<br>[11:17] for anything. So, yeah, definitely for<br>[11:19] future Chaos Cons<br>[11:22] or workshops or whatever else we want to<br>[11:23] use it for. So, yeah, thanks you guys.<br>[11:26] I'm excited.<br>[11:29] It's the little things, you know, that<br>[11:31] make me happy.<br>[11:31] >> Was it difficult?<br>[11:33] it not difficult uh just uh time<br>[11:38] consuming I guess it's more like because<br>[11:41] you know you have to like I would<br>[11:43] imagine yeah just<br>[11:44] >> just you know pull in things from the<br>[11:45] spreadsheets cuz they're in a couple<br>[11:47] different spreadsheets um and then I had<br>[11:49] to manually do these in Canva the circle<br>[11:51] but I like the circle images I don't<br>[11:53] know cuz when you get them they're all<br>[11:55] different sizes square rectangle<br>[11:57] whatever and so I wanted them to be<br>[11:59] unified so um I did the circle too so<br>[12:03] That was a little timeconsuming, but<br>[12:05] yeah.<br>[12:09] >> Thank you, Elizabeth. Looks really<br>[12:10] >> Oh, yeah. You're welcome. You're<br>[12:12] welcome. Um, but again, if you guys see<br>[12:15] anything, I'm also going to fix this so<br>[12:18] it matches above. Um, so it's more of<br>[12:20] just like the pictures of everybody, you<br>[12:23] know, in one thing and not and I'll just<br>[12:25] save all the the descriptions of<br>[12:28] everything and leave it in hidden up<br>[12:30] here if that's okay. So, it's just like<br>[12:32] cleaner and easier.<br>[12:36] And I can link to these. So, I can also<br>[12:39] share a link if I want to put, you know,<br>[12:42] the person in their talks or something<br>[12:44] like that. We can we can do this. Oops.<br>[12:48] I don't know what that was, but yeah,<br>[12:51] we'll look at that again as Paige. I<br>[12:54] kind of like that, too. So,<br>[12:57] there you go. Exciting things for Chaos<br>[13:00] Gone.<br>[13:04] Um, anything uh so I should say do we<br>[13:08] have anything else that's like for<br>[13:09] everybody and not specific to the Chaos<br>[13:11] Con committee.<br>[13:22] Nobody is jumping in so that's okay. Um,<br>[13:26] okay. So, do we want to just end this<br>[13:29] part of the meeting then? and move on to<br>[13:31] for those who are helping organize Chaos<br>[13:33] Con to stick around.<br>[13:35] >> I think so in this final weeks here<br>[13:39] probably.<br>[13:40] >> Yeah, we have a lot to kind of talk<br>[13:42] about. So,<br>[13:45] oh, I also do want to say one one quick<br>[13:47] other thing that's exciting about this<br>[13:48] chaos con is that we do have a heart of<br>[13:51] uh sorry, heart of hearing, hearing<br>[13:52] impaired deaf speaker this year, which<br>[13:55] is super exciting, I think, and um will<br>[13:58] really push us to be more inclusive and<br>[14:02] accessible and all of those things for<br>[14:04] the future. So, um I'm I'm quite excited<br>[14:06] about that. So, that's something new for<br>[14:08] for Chaos. So, yay.<br>[14:14] Okay, I'm going to stop sharing now. Now<br>[14:16] that I've shared my whole entire screen<br>[14:18] with everyone all over, I'm done. And I<br>[14:22] will stop recording, too. <!-- deep-read:sections end --> ๐Ÿ“„ **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, Jan 13, 2026.md|CHAOSS Weekly Community Call, Jan 13, 2026 by YouTube]] ## Highlights - >> Did I share everything? >> Yeah, it was everything. >> Okay. Well, don't look. Maybe I'll just cut that out of the recording. Here we go. Okay, >> there we go. >> Real fast and try to log in. >> Super secret information. Not really. I got nothing. >> My life is so boring. I wish I had super secret information that I had to blur out. Not that important. Okay. Um, is there one thing you want to accomplish today? I don't know. Maybe there's a lot of ([View Highlight](https://read.readwise.io/read/01kp9k9ek710x2wpm3qxxqn981)) - Tags: ๐Ÿ‘ป ai highlighted - open source program offices specifically at universities. Oh, >> okay. Uh, it's separated from to-do. What's that? >> It's separated from to-do group. >> Um, yeah, it's different from the to-do group which is kind of focused more on the corporate ospo side. There are sometimes representatives in fact I think maybe David did you say you were um to-do group as well >> to do I think to-do is broader it's it started out industry but I think it's ([View Highlight](https://read.readwise.io/read/01kp9k9ekndrrev9t2g80g3aw5)) - Tags: ๐Ÿ‘ป ai highlighted - something that um because we still see them on GitHub, but we're just curious, you know, how how that's going, how what the volume is if there's a lot of folks who are still applying. >> Oh, okay. So, um I wouldn't say we have um a lot of volume. We just have three at the moment. Uh and I think uh we are good. There is no problem. >> Okay. Do you don't we have like a big ([View Highlight](https://read.readwise.io/read/01kp9k9emeksfk5s822yan3brq)) - Tags: ๐Ÿ‘ป ai highlighted - push maybe a couple times a year where there's a whole bunch of applications that come in. >> Oh, okay. Um probably um into uh the mid year, not at the beginning. >> Okay. >> Forance um in December we didn't we didn't have a lot of vacations. In fact, there was rest. >> Sure. >> Yeah. Good. >> Okay. Yeah, I was just kind of curious how things were going, but sounds like ([View Highlight](https://read.readwise.io/read/01kp9k9enapqcahjmr4rrfkkxd)) - Tags: ๐Ÿ‘ป ai highlighted