CHAOSS Data Science WG, Feb 24 2026 - CourtneyR.dev's 2nd Brain

CHAOSS Data Science WG, Feb 24 2026 ![rw-book-cover](https://img.youtube.com/vi/OdclF7fipLA/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Data Science WG, Feb 24 2026](https://www.youtube.com/watch?v=OdclF7fipLA) > [!note]+ Document Notes > tags: #chaoss #data-science #open-source #maintainership #academic-funding > author: CHAOSS Data Science Working Group > source: YouTube > reference: https://www.youtube.com/watch?v=OdclF7fipLA > date created: 2024-12-19 14:30 > > # 🏷️ Title: CHAOSS Data Science WG, Feb 24 2026 >  ## 🧰 Action Inbox - [H1] Complete funding impact measurement guide synthesis — incorporating diverse feedback #chaoss - [H2] Finalize maintainer sponsorship charter for Ernest — ensuring comprehensive handoff #maintainership - [H3] Scope archives project for new contributor David — connecting repositories to community needs #data-science ## 🧭 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 Project](https://chaoss.community) - [Foundation Stats Dataset](https://github.com/chaoss/wg-data-science) ## 📝 Summary - CHAOSS Data Science Working Group held a smaller-than-usual meeting due to concurrent conferences - Key updates on practitioner guides, foundation stats project, and new maintainer sponsorship program - Ernest is being sponsored as new maintainer through comprehensive handoff process - David from UCL joined to discuss academic funding opportunities and archives project - Working group continues developing cross-foundation sustainability research - New contributor interested in making archives more accessible to broader communities ## 📖 Main Content The CHAOSS Data Science Working Group meeting focused on ongoing projects and community development despite reduced attendance due to Linux Foundation events. The session highlighted the maturation of both technical projects and governance processes. The funding impact measurement guide has received substantial feedback requiring careful synthesis. The challenge lies in balancing input from contributors with varying familiarity with the guide's objectives and established methodology. Foundation stats project continues pursuing cross-foundation metadata normalization to enable comparative sustainability research. A UK-based academic partnership through University College London offers potential funding pathways, though current grant opportunities require demonstration of higher project maturity. The working group is pioneering a maintainer sponsorship model where experienced maintainers formally sponsor successors, taking responsibility for comprehensive skill transfer. This differs from traditional mentorship by placing accountability on the sponsor to guarantee the new maintainer's readiness. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/OdclF7fipLA?t=0) — [H1] Meeting opening and attendance - Key idea: Smaller group due to concurrent conferences creates opportunity for deeper discussion - Evidence: "It's a slightly shorter lineup than usual because of LF members and like two other co-occurring conferences" #### ⏱️ [02:30](https://youtu.be/OdclF7fipLA?t=150) — [H2] Practitioner guides progress update - Key idea: Funding impact guide awaiting feedback synthesis despite quality input - Evidence: "I've gotten a lot of really good feedback on the funding impact measurement guide, which means now that there's an awful lot of work in trying to synthesize that feedback" #### ⏱️ [05:15](https://youtu.be/OdclF7fipLA?t=315) — [H3] Foundation stats project and UK funding - Key idea: Cross-foundation sustainability research requires normalized metadata structures - Evidence: "We are trying to feel the metadata on availability or differences in how different foundations report metadata" #### ⏱️ [08:45](https://youtu.be/OdclF7fipLA?t=525) — [H2] SSI grant requirements and maturity - Key idea: Academic funding requires demonstrated end-user community value within 12 months - Evidence: "They're looking for a project that's at slightly higher maturity where we can demonstrate end user community value" #### ⏱️ [12:20](https://youtu.be/OdclF7fipLA?t=740) — [H3] UK academic funding landscape insights - Key idea: Physical presence in UK regions significantly improves funding prospects - Evidence: "If I tell them that my ability to get this to the UK means I'm going to go give a talk on the subject or workshop on the subject in London, Manchester, and Edinburgh, they're going to say yes" #### ⏱️ [18:30](https://youtu.be/OdclF7fipLA?t=1110) — [H1] Maintainer sponsorship program introduction - Key idea: Sponsorship model places responsibility on sponsor to guarantee successor readiness - Evidence: "A sponsorship is only different from a mentorship in that I am the sponsor. I am the only person that can fail" #### ⏱️ [22:10](https://youtu.be/OdclF7fipLA?t=1330) — [H2] Ernest's maintainer progression - Key idea: Contributors become maintainers when they provide more value than current maintainers - Evidence: "They came in as a contributor and then immediately provided more value than I was providing as the maintainer" #### ⏱️ [25:45](https://youtu.be/OdclF7fipLA?t=1545) — [H3] Academic handoff hygiene importance - Key idea: Academic projects lose significant value from poor transition practices - Evidence: "I wish when I was in academia that I had had the security experience of knowing how to do extremely hygienic handoff because we lose a lot in academia from not doing very good handoffs" #### ⏱️ [28:00](https://youtu.be/OdclF7fipLA?t=1680) — [H2] Conference CFP announcements - Key idea: Community engagement opportunities at ASF Community Over Code and All Things Open - Evidence: "ASF's community over code is going to be in Glasgow this year and the CFP deadline is March 20th" #### ⏱️ [30:15](https://youtu.be/OdclF7fipLA?t=1815) — [H3] Archives project background and challenges - Key idea: Project archiving study requires rethinking scope from manual assessment to new approach - Evidence: "The data that we were getting from those manual assessments wasn't particularly interesting" #### ⏱️ [35:20](https://youtu.be/OdclF7fipLA?t=2120) — [H2] New contributor perspective on accessibility - Key idea: Archives and data need better organization for maker spaces and general public access - Evidence: "I've talked to so many maker spaces that don't know any of this stuff exists. Like they don't know where to start" #### ⏱️ [38:45](https://youtu.be/OdclF7fipLA?t=2325) — [H1] Ernest maintainer recognition - Key idea: Official maintainer handoff scheduled for next meeting with full recognition - Evidence: "Ernest was doing all of the code reviews and providing all of the feedback and then pinging me and saying, 'Hey, can you merge this for me?'" ## 📚 References - [CHAOSS Data Science Working Group Repository](https://github.com/chaoss/wg-data-science) - [ASF Community Over Code Conference](https://communityovercode.org/) - [All Things Open Conference](https://allthingsopen.org/) - [SSI Fellowship Programme](https://www.software.ac.uk/programmes-and-events/fellowship-programme) ## 🗣️ Paraphrase - The working group is developing maintainer sponsorship as accountability-based succession planning where sponsors guarantee successors' readiness rather than just mentoring - Foundation stats project aims to normalize cross-foundation metadata enabling comparative sustainability research across Apache, CNCF, Eclipse and other ecosystems - Academic funding in UK increasingly values open source but requires demonstrated community impact and physical presence commitments ## 📰 Newsletter **CHAOSS Data Science Working Group Pioneers Maintainer Sponsorship Model** The CHAOSS community is developing an innovative approach to maintainer succession that goes beyond traditional mentorship. Their new sponsorship model places accountability on experienced maintainers to guarantee their successors' readiness, drawing from security industry practices. Key developments include Ernest's progression to maintainer status and ongoing work on cross-foundation sustainability research. The group also welcomes new contributors interested in making project archives more accessible to maker spaces and broader communities. **Practical Benefits:** - Structured knowledge transfer reducing project continuity risks - Clear accountability for maintainer readiness - Academic-industry partnership models for sustainable funding Resources: [CHAOSS Community](https://chaoss.community), [GitHub Repository](https://github.com/chaoss/wg-data-science), [Conference CFPs](https://communityovercode.org/) ## ✅ Action Items #### OSPO - Policy & Governance: Document maintainer sponsorship charter as template for other projects - Community Engagement: Establish academic partnership frameworks with UK institutions - Strategic Alignment: Develop metrics for measuring cross-foundation sustainability research impact #### Community - Maintainers: Implement sponsorship model across CHAOSS working groups - Contributors: Create onboarding materials connecting archives to maker space communities - Sponsors: Establish clear success criteria for maintainer handoff processes #### WordPress - Community: Adapt maintainer sponsorship models for WordPress contributor pathways - Documentation: Apply academic handoff hygiene practices to WordPress documentation projects - Meta: Explore cross-foundation metadata normalization for WordPress ecosystem analysis ## 🧪 Hypotheses - Maintainer sponsorship reduces project continuity risks compared to informal mentorship - Cross-foundation metadata normalization enables more robust sustainability predictions - Academic-industry partnerships increase open source project funding success rates - Structured handoff processes prevent knowledge loss in volunteer-driven projects ### 📊 Methodology - Compare project continuity metrics before/after sponsorship implementation - Survey maintainer confidence levels in sponsored vs. traditional transitions - Analyze funding success rates for projects with academic partnerships - Measure knowledge retention in structured vs. informal handoffs ### ❓ Questions - How can maintainer sponsorship models scale across different project sizes and complexity levels? - What specific competencies should sponsors guarantee for data science repository maintenance? - How might cross-foundation research inform individual project sustainability strategies? ### 🔮 Future Research - Longitudinal study of maintainer sponsorship outcomes across multiple projects - Comparative analysis of academic funding models for open source sustainability - Investigation of maker space integration with archived project repositories ### 💡 Implications - Practice: Maintainer succession becomes deliberate, accountable process rather than ad-hoc transition - Policy: Academic institutions may need new frameworks for evaluating open source impact and value - Education: Comprehensive handoff documentation becomes critical skill for technical project leadership - Funding: Cross-foundation research requires collaborative approaches to data sharing and methodology alignment ### 🧠 Learning Styles Assessment Reading level estimate: College level (technical project management content) #### 👀 Visual learners - Present: Organizational structure discussion, repository references - Improve: Maintainer sponsorship process diagram, foundation comparison charts #### 🔊 Aural learners - Present: Full video discussion with multiple speakers and perspectives - Improve: Audio summary highlighting key decisions and next steps #### 🗣️ Verbal learners - Present: Detailed explanations of sponsorship vs mentorship distinctions, academic funding requirements - Improve: Glossary of CHAOSS-specific terminology and processes #### 🧩 Kinesthetic learners - Present: References to code reviews, pull requests, repository exploration - Improve: Step-by-step sponsorship agreement template, hands-on archive analysis tasks #### 🧠 Logical learners - Present: Clear progression from contributor to maintainer, funding timeline requirements - Improve: Decision framework for sponsorship readiness, funding application checklists #### 🧑‍🤝‍🧑 Social learners - Present: Working group collaboration, academic partnership discussions - Improve: Structured peer feedback sessions, collaborative sponsorship evaluations #### 🧘‍♀️ Solitary learners - Present: Individual project exploration encouragement, self-directed research - Improve: Self-assessment rubrics for maintainer readiness, independent study guides #### 🌿 Naturalistic learners - Present: Organic community growth patterns, ecosystem sustainability focus - Improve: Project lifecycle analogies, sustainability framework connections ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear verbal communication throughout discussion - Improve: Written agenda and summary documents with proper heading structure #### Keyboard navigation - Present: Standard video platform controls - Improve: Timestamped navigation options, keyboard shortcuts for key topics #### Contrast and readability - Present: Video format with clear audio - Improve: High-contrast transcript formatting, readable font sizing #### Text resizing and reflow - Present: Responsive video player - Improve: Scalable transcript display, mobile-friendly documentation #### Media and captions - Present: Full transcript provided for analysis - Improve: Official captions with speaker identification, downloadable transcripts #### Forms and interactions - Present: Standard meeting participation - Improve: Accessible feedback forms, inclusive participation guidelines ### 🌍 DEIB Assessment #### Cultural breadth - Present: International perspectives (UK, academic institutions) - Improve: Broader geographic representation, multi-timezone considerations #### Inclusive language - Present: Professional, welcoming tone for new contributors - Improve: Defined technical jargon, multiple communication style accommodations #### Neurodiversity support - Present: Multiple communication channels (voice, text, async) - Improve: Written agendas provided in advance, processing time allowances #### Representation - Present: Academic and industry perspectives represented - Improve: Diverse role models in maintainer examples, varied career path showcases #### Psychological safety - Present: Supportive approach to new contributor questions and concerns - Improve: Explicit community guidelines, multiple feedback channels ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Maintainer progression logic from contributor value demonstration - Inductive strength: Academic funding patterns informing future strategy - Causal reasoning: Sponsorship accountability improving handoff outcomes - Analogical strength: Security industry practices applied to open source maintenance #### Fallacies - Appeal to authority: UK funding requirements based on limited sample size, needs broader validation - Post hoc reasoning: Assuming Ernest's value increase directly indicates maintainer readiness without considering other factors #### Tone of voice - Overall tone: Collaborative and encouraging with practical focus on community development and sustainable project management ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - Attack: No attacks on individuals or groups - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive community-building language, celebration of contributions ## 🎯 Conclusion The CHAOSS Data Science Working Group demonstrates mature community governance through innovative maintainer sponsorship models and strategic academic partnerships. Their approach to accountability-based succession planning offers valuable lessons for sustainable open source project management. The emphasis on comprehensive handoffs, cross-foundation research capabilities, and inclusive onboarding creates a framework other technical communities can adapt. The intersection of academic funding and open source sustainability represents an evolving landscape requiring continued attention and documentation. Next steps involve finalizing sponsorship documentation, expanding archive project scope, and leveraging academic partnerships for broader research impact. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Maintainer sponsorship creates accountability-based succession > [!quote] [CHAOSS Data Science WG, Feb 24 2026](https://youtu.be/OdclF7fipLA) by [[CHAOSS Data Science Working Group]] via [[YouTube]]. Published 2026-02-24. Accessed 2024-12-19. > "A sponsorship is only different from a mentorship in that I am the sponsor. I am the only person that can fail." Formal sponsorship places responsibility on experienced maintainer to guarantee successor readiness rather than providing optional guidance. [view highlight](https://youtu.be/OdclF7fipLA#H1) #xref #articleseed ID:rw_maintainer_sponsorship ### [H2] Academic funding requires demonstrated community value > [!quote] [CHAOSS Data Science WG, Feb 24 2026](https://youtu.be/OdclF7fipLA) > "They're looking for a project that's at slightly higher maturity where we can demonstrate end user community value within 12 --- ## Full Transcript [00:00] Yeah. [00:02] >> Okay. I just clicked I just clicked [00:04] record so you can kick it off while I [00:05] get my notes up. [00:07] >> Okay. All right. We are officially [00:09] recording. Welcome in everyone. It's a [00:12] slightly shorter lineup than usual [00:14] because of LF members and like two other [00:17] co-occurring conferences over this exact [00:20] time this week, which is great. Um it [00:22] gives us a chance to cover anything in [00:24] depth that we want to. Um, but uh yes, [00:28] we'll uh get that link out onto the chat [00:31] real quick. Feel free to put in your [00:33] name and something that you are looking [00:35] forward to and uh then we will just run [00:38] through this agenda. I suspect it's [00:40] going to be a lighter than 50 minutes [00:42] today. Um but if there's anything we [00:44] want to dive into, we've got time. [00:49] So on that note, I'm also going to add [00:51] myself into that uh attendees, but we [00:55] could start with uh practitioner guides. [01:00] Uh do we have any on those? Go ahead. [01:03] >> Uh yeah, I give some some quick updates. [01:05] There's not a lot. Um I've gotten a lot [01:07] of really good feedback on the funding [01:08] impact measurement guide, which means [01:10] now that there's an awful lot of work in [01:12] trying to synthesize that feedback and [01:15] figure out what goes what goes in and [01:16] what what doesn't. and I just honestly [01:18] haven't had enough time to do that yet. [01:21] So, um, so that's where that is. I've [01:23] gotten lots of good feedback. As soon as [01:24] I have time to sit down with that guide, [01:26] which will probably be maybe after my [01:29] little wave of conferences or maybe [01:31] while I'm traveling. Um, I'll get back [01:33] to that and we'll get that one finished. [01:34] But it's it's it's pretty close um in [01:38] that I've gotten lots of feedback. I [01:39] just need to just need to finalize it [01:42] because not all of the feedback is um [01:46] aligned with the direction of the guides [01:47] because I've gotten a lot of feedback [01:49] from people who aren't super familiar [01:50] with the guides. So, I just need to [01:53] >> need to figure figure that out. Um [01:57] the usage, adoption, and popularity. Uh [01:59] we haven't made any progress on that. I [02:01] think we're going to put that on an [02:02] agenda item for one of these meetings in [02:06] the in the future. Um, and then the uh [02:10] research software impact. Uh, Matt's [02:12] been super busy and so I haven't been [02:13] bugging him to ask him where that is, [02:15] but that's the one that Matt's been [02:16] driving along with some folks at Curious [02:19] uh, from a university standpoint. [02:23] So, that's what we have on the [02:26] practitioner guides. [02:29] Okay, that brings us into project [02:33] updates and foundation stats. [02:37] I will also point out that we have David [02:39] on this call. Thank you David for [02:42] joining us. So uh David works at uh [02:44] University College London. So uh we had [02:48] a Slack thread and I think maybe an [02:50] email chain or something around the [02:52] foundational stats and the the grant [02:54] that you were pursuing. So if you can [02:55] cover that in the update that would be [02:57] great. [02:58] >> Oh, I will do a quick update on that. Um [03:00] so we were looking at the I think it was [03:02] the SSI funding. [03:05] Um, but I think the real honest thing [03:10] there is they're looking for a project [03:12] that's at slightly higher maturity where [03:14] we can demonstrate [03:16] uh like end user community value which I [03:18] think we absolutely can inside of 12 [03:21] months. I don't think we were ready for [03:22] that grant this time. Um, but I am [03:26] extremely curious because 8n and augur [03:28] are going forward with at least the [03:30] first pass of that. So, I think it would [03:32] be a really really good idea for us to [03:34] uh come together and get any lessons [03:36] learned out of that submission. Um, but [03:41] I also think it might be worth having a [03:44] grant focused working group for chaos is [03:47] something that I have seen come out of [03:48] that interaction. That's a super super [03:50] high level. Um, but Ernest, do you have [03:53] anything that you want to And there's a [03:55] couple of new people on this call. So, [03:57] do you want to describe the foundation [03:58] stats just overall as a project? [04:03] >> All right. Thank you and uh good day [04:05] everyone. [04:06] Um, so foundational stats is um we are [04:10] trying to [04:12] feel the metadata um on availability or [04:15] differences in how different foundations [04:18] um report metadata. For example, Apache [04:21] presents their communication structure [04:23] quite differently from um CNCF and [04:28] Eclipse just using those three as a case [04:30] study. And we are hoping if we can [04:33] normalize the structure of this metadata [04:37] in the data sets, we would be able to [04:41] answer sustainability questions on a [04:42] cross foundational level basis because [04:45] previous research has not necessarily [04:47] been comparing what does sustainability [04:50] means across different foundations. [04:52] We've just been asking per project or [04:55] per package or per foundation as it may. [04:57] So we hope that if we could gather this [05:00] data we we will have found additional [05:02] work around I mean basic work elementary [05:05] or beginning work let me not use that [05:07] foundation because of the mix word we [05:10] have those initial results to answer [05:13] sustainability questions across [05:16] foundations I mean OSS foundations [05:19] yeah [05:24] thank you [05:27] >> thanks Thanks, Ernest. I don't know, [05:28] David, if you wanted if you had anything [05:30] to add about the like the Augur SSI [05:35] um grant. I don't know exactly what [05:36] they're what they're doing. [05:38] >> Sure. [05:40] >> S was talking, but in case you don't, [05:43] please let me go. [05:45] >> Right. So, [05:47] yeah, I just joined to see exactly what [05:49] definition STS were exactly and how this [05:52] could help. So for augur [05:57] essentially one of the thing that they [05:58] need is a a UK based um [06:04] person and well that's what we were [06:06] saying also in Slack a and because we [06:09] were playing with a back in October and [06:12] we were making a lot of uh complaints in [06:15] a good way like suggesting supporting [06:18] things like saying why this is not [06:19] working and and we have like pretty much [06:22] three people almost 100% for almost a [06:25] month. We did kind of a contribute in in [06:29] quite a bit and [06:32] and yeah we [06:35] we in in in our role in the university [06:38] because we are helping supporting a lot [06:40] of teams. Last year for the first round [06:42] we I think we were in 22 uh proposals as [06:47] our team and this year I think we are [06:50] way less that has been kind of a [06:53] countdown after probably the feedback we [06:55] got on the first round and we are now [06:58] like around eight uh counting over I [07:00] think. So yeah, the the idea for Aug uh [07:05] if I remember correctly was pretty much [07:06] on on helping uh including other forges [07:11] like or better support for other forges [07:15] be beside GitHub and some other things [07:19] but yeah as Sal was saying it's more [07:21] about the maintenance and and keeping [07:25] how that project can become more solid. [07:29] The problem is that their main one of [07:32] the main questions is UK impact and and [07:36] yeah we can promise that this is going [07:37] to have an impact but how proving that [07:40] has been quite hard at least from the [07:42] previous round where in some in some [07:46] proposals we have like a lot of papers [07:48] from UK that they are using this [07:50] software and they were like nope this is [07:52] not enough and others is like uh yes you [07:56] show a lot but it's too much and I'm [07:58] like okay it doesn't make sense. [08:00] Uh so yeah we are [08:02] we are not clear yet of uh what will [08:05] happen but this year one of the [08:06] interesting uh things that for at least [08:08] for the expression of interest is that [08:11] people are going to be reviewing so it's [08:14] going to be peer review by the people [08:15] who are taking part on it. So that will [08:18] maybe help which I think what happened [08:20] last time that the reviewers were not [08:22] too familiar with what is the call and [08:26] and how funding was working because some [08:29] some comments we receive are like oh [08:30] this is too much for um [08:34] uh overheads and like well that's the [08:36] overheads that this grant like that's [08:39] all that we can ask for. So it was kind [08:40] of a quite I don't know it was quite [08:43] separated like people reviewing the [08:45] thing was not really understanding what [08:46] they were reviewing in terms of the [08:48] conditions that those projects were. So [08:52] yeah I don't know what what other [08:54] questions do you have that I can help [08:57] answer. [08:58] >> That was extremely helpful. [09:02] >> Okay. [09:03] >> Yeah. So I'm really interested at this [09:05] intersection of funding open source and [09:08] academia together. Um when I was doing [09:11] open source and academia 15 years ago, [09:14] you just got funding for Nadamia and [09:16] happen to be doing open source. Now that [09:18] there's a true birectionality there and [09:21] I think this is a grant that represents [09:23] that shared values intersection. Um so I [09:28] am a little bit curious to see [09:31] particularly the way that this grant [09:33] possibly moves forward with like [09:35] auguring 8 knot and see the response [09:37] back. The first thing that I can think [09:39] of from what you just described is I [09:41] have found that specifically in the UK, [09:45] if I tell them that my ability to [09:50] get this to the UK [09:53] means I'm going to go give a talk on the [09:55] subject or workshop on the subject in [09:58] London, Manchester, and Edinburgh, [10:00] they're going to say yes. They're not [10:03] even looking for quantitative value past [10:05] that. They just want to see that you're [10:08] going to be physicalized in the UK. So [10:11] that might be something that we add and [10:13] see if it makes a difference in the [10:14] future because it's very easy to go give [10:17] a talk in London, Manchester, and the UK [10:22] um in 12 months time off of a grant. Um [10:25] that might be worth adding or [10:27] considering, but I'm also trying to get [10:30] my sea legs around uh academic grant [10:34] funding in the UK. [10:36] It's different than it was 10 years ago. [10:38] So, I'll take advice from anyone that's [10:40] in it at this moment. [10:45] >> But thank you for that. And if you got [10:48] the mic is back to you. [10:52] >> Yeah. No, I I [10:55] So, this grant is completely new, right? [10:57] So it was last well new last year but [10:59] that was kind of a and it's kind of [11:01] experiment that the sourceity is running [11:03] and they say they say the way they are [11:05] running the way they are doing the [11:07] review the way they are doing the things [11:09] they're quite open on those things so [11:10] that's quite good uh but I don't think [11:13] in open source in general on the rest of [11:16] the of the uh funding schemes are [11:22] much different than in the past but yeah [11:24] I mean uh there's maybe more in research [11:27] there's been more push of at least uh [11:30] the figure of research software [11:32] engineers has been more kind of a it has [11:34] to be or if it's be if it's if it's if [11:38] there's a research of engineer involved [11:40] in a project it has more chances to be [11:42] funded [11:44] uh but not as much as the open source [11:46] part of it some funding agencies uh say [11:51] that it has to be but uh then how is [11:54] enforce not that's a whole different [11:56] thing. [12:01] >> Yeah, I might use yellow. Sorry, what [12:02] was that? [12:05] >> Just connecting connecting the dots. [12:07] Adrian came a little late. I was just [12:08] catching them up. [12:09] >> All right, right. Okay, cool. [12:11] >> Oh, my chat window is empty. It's like [12:14] all blank anyway. Yeah. So So yeah, I [12:19] I don't know how much more info and I [12:21] don't know. [12:23] Yeah, like uh this particular call I [12:28] find that it's a a lot as well about [12:30] setting up governance and setting up [12:32] community. [12:33] >> Yeah. So I'm looking but well the one I [12:36] the one I was more involved last year [12:38] like writing it like I was in the [12:40] project one side project I have [12:43] uh it didn't pass the expression of [12:45] interest but it was most focus on okay [12:48] we want to improve something there's no [12:50] new features no software to in include [12:54] there but it's more about how we get [12:57] contributors to be sorry how to be get [12:59] users to become contributors how to be [13:01] contributors to be maintainers [13:03] that kind of a path and [13:07] but yeah I I didn't I didn't mine didn't [13:10] pass and from the 21 that we did I think [13:12] that uh only a couple passed to the next [13:16] phase and then they didn't got funded at [13:19] the end and one was for mach league for [13:22] example so it's it's [13:25] >> this price of all sizes and this is not [13:29] for open source only [13:31] >> yeah exactly Yeah. Yeah. [13:33] >> There's also type of compet compet [13:35] competition going on. [13:37] >> Yeah. Yeah. And I think uh when we're [13:40] looking at this because kind of I think [13:42] this is just a let's learn what we learn [13:44] and I will take any advisement as we go [13:47] and let's just soak up because it is a [13:49] different call than it was a year ago [13:51] and it could be a different call next [13:53] year. But I want to get an idea of what [13:56] it looks like and feels like to [13:58] proposition the value of open source [13:59] within academia in 2027. And I feel like [14:03] that's going to be a different call to [14:05] action than even this year. So [14:08] interesting open thing to keep in mind. [14:10] Um but thank you for candidly describing [14:15] it as exactly how I would describe it [14:16] from what I've read. [14:18] >> I think right on the right on the target [14:20] there. And well uh I'm also building an [14:25] OSPO in in UCL. Uh so uh [14:30] there is there's also the curious [14:32] network as well building like kind of a [14:34] OSO on on universities and academic [14:37] institutions. So maybe there's also more [14:39] opportunities out there that [14:42] >> Yeah. [14:43] >> Yeah. [14:44] >> from [14:45] >> Yeah. And I did half of my PhD at UCL, [14:47] but I was in the functional neuroiming [14:51] department, so you didn't see me. I was [14:53] in a basement. But it's a good [14:56] university and I'm excited there's no [14:58] there. Um, cool. I would say for now I [15:01] think that covers that topic. Um [15:04] although it's a topic we should [15:05] absolutely come back to as we get more [15:07] feedback. Um next on the agenda here [15:13] um [15:15] virtualization notebooks with augur [15:17] analysis. Cali is not here today because [15:19] they're at the uh Linux Foundation [15:22] membership meeting but that has been [15:24] coming together and it is very cool. So [15:26] come to the next session and I think [15:29] you'll be able to get more insight on [15:30] it. And then the costs, [15:34] are we covering that today? [15:36] >> Uh, no. Matt's not here. I suspect he's [15:38] also at the at the member summit. Um, [15:40] and I haven't had a I haven't seen any [15:43] pull requests from him and I haven't had [15:44] a chance to catch up with him and see if [15:45] he wants any help moving some of that [15:47] stuff over to the repo. [15:49] >> Cool. Sounds good. In that case, then it [15:52] looks like the last thing on the agenda [15:55] is from me, and I'm excited about it. So [15:58] this is about uh bringing in new [16:00] maintainers, on boarding and sponsoring [16:02] them, which is to say that I have [16:05] identified earnest on this call as being [16:07] excellent as a long-term maintainer to [16:10] the foundation project because they came [16:12] in as a contributor and then immediately [16:15] provided more value than I was providing [16:17] as the maintainer. And that's how you [16:19] know when you've got your next best [16:21] maintainer. Um, so what I'm trying to do [16:25] there is to set up a sponsorship program [16:29] for the maintainers. This might be [16:31] unique to this space. It's not unique to [16:33] me. I work in the security side of open [16:36] source. And before we're able to [16:39] maturely do a handoff with a maintainer, [16:41] we have to ensure that we have not only [16:45] taught but have demonstrated an instance [16:47] of demonstration of proof around things [16:50] like handling vulnerabilities. if [16:52] they're disclosed to you, things like [16:53] that. So, we're not doing a [16:56] securityoriented sponsorship in this [16:58] case, but I am in the process of [17:00] building a chaosoriented data [17:03] scienceoriented maintainer handoff, [17:06] which both respects the culture of the [17:08] community and also respects the [17:09] complexity of data science repositories, [17:12] which are slightly different from a [17:14] typical software repository. Um, so as [17:18] I'm building that out, I'm getting [17:20] initial feedback now, but once we make [17:22] that public as a possible sponsorship [17:25] charter, I would be open to feedback [17:29] from anyone on that subject. And I'm [17:31] also open to any ideas on the call if [17:34] you think the idea of a sponsorship is [17:36] good, bad, or if you've seen something [17:38] better. Um, but what I want to [17:40] responsibly do is hand off that [17:43] repository knowing that the next [17:46] maintainer has all of the skill sets [17:48] that I had while I was managing that. [17:51] Um, any questions or comments there? I [17:54] think that's something that I want to [17:56] dive into in depth probably in the next [17:59] call. Um, yes. And Adrien, I am going to [18:03] I can add you in on the conversation or [18:06] sort of bring you in. just have a MD [18:08] that we're building right now around the [18:10] sponsorship and I'm looking for anyone's [18:12] insights on it before we make it [18:14] official official. But as soon as we do, [18:17] Ernest and I are going to sign a [18:19] sponsorship agreement. Now, a [18:21] sponsorship is only different from a [18:22] mentorship in that I am the sponsor. I [18:25] am the only person that can fail. [18:28] So, I have to guarantee that the next [18:30] maintainer has all the skills that I say [18:32] and that I'm going to give them within a [18:33] year. And that's how we do it in [18:35] security. So, it's probably going to [18:37] work better here where we're doing it [18:39] with less stressful things to learn. [18:43] Um, so yeah, that's what's happening [18:45] there. It's still in progress. Um, but [18:48] I'm hoping we can come to the next uh [18:50] standup here and both myself and Ernest [18:53] can talk about the experience of sort of [18:55] deliberating that and what it currently [18:57] looks like and uh look for any [19:00] additional feedback. That's a document [19:02] that can and should evolve and it should [19:04] be probably bespoke to every repository [19:07] depending on the requirements of the [19:09] repository. So that's where that's [19:12] standing. That's a lot of words where in [19:14] the future in about 2 weeks I'll just [19:16] show you the document and we can walk [19:18] through it and understand it. Um, I also [19:21] think that I wish when I was in academia [19:23] that I had had the security experience [19:25] of knowing how to do extremely hygienic [19:28] handoff because we lose a lot in [19:30] academia from not doing very good [19:32] handoffs and this is a way to fix that [19:34] problem. [19:36] So, I think it's really good for chaos. [19:38] Um, and that's it. That's the note on uh [19:40] that update. [19:42] >> Yeah, that's great. I'm I'm so glad that [19:45] uh you and Ernest have been have been [19:46] working on this. I think it's something [19:47] that we can we can definitely use, like [19:50] you said, in other places within within [19:51] Chaos. I think it's something that's [19:53] it's really valuable and we probably [19:54] haven't done enough of before. So, I [19:57] think that's I think that's good. And I [19:58] just put it um you probably saw this [20:01] under the agenda for upcoming meetings [20:03] for the next meeting. We'll put it on [20:04] the agenda again. [20:06] >> Cool. Yeah, we'll be ready in two weeks. [20:10] >> Awesome. [20:11] >> Cool. Okay. Uh, and I think that puts us [20:16] uh right now at any opens for the next [20:20] meeting. Anything we want to cover. [20:33] >> The silence is not deafening. It's a [20:35] very nice break from what usually [20:37] happens at the end of this call, which [20:39] is like everyone's throwing down a lot [20:41] of things they want to cover. That's [20:43] really nice. Um, that means very likely [20:45] in two weeks you're going to come here [20:46] and you're going to see people have [20:47] updated this. Um, but if we've got a [20:50] nice loose schedule for next week, I [20:52] would like to create more space within [20:55] these calls, 10 minutes or so for new [20:58] entries to the community because we're [21:00] often getting those and it's a really [21:01] nice to just make sure we have that time [21:04] laid out to say, "Hi, hello, and are you [21:07] on the right Slack? [21:12] I don't feel so alone with over 3,000 [21:15] members now. [21:16] >> Yeah. [21:20] >> Excellent. [21:21] >> Awesome. [21:23] >> Okay. Anything else that we are looking [21:26] to cover? So, there's the upcoming [21:27] meetings and reminders. Do you want to [21:30] cover that? [21:31] >> Yeah. I just added a couple of [21:33] conferences that have open CFPs. So, um, [21:37] the ASF's community over code is going [21:39] to be in Glasgow this year and the CFP [21:42] deadline is March 20th. All things open, [21:44] uh, they have a slightly new format, so [21:46] it's a slightly shorter event. Um, and [21:48] their CFP deadline is March 31st. So, [21:51] those are both, uh, I've heard great [21:54] things about Community Over Code. I've [21:55] never been to it. I've been to all [21:56] things open a couple of times, and it's [21:57] a it's a lovely conference. So, I would [21:59] encourage people to submit talks if it's [22:02] something that you're interested in [22:04] attending. [22:05] I can't believe All Things Open CFP is [22:08] already open, [22:10] but I'll submit. I'm ready. [22:12] >> Yep. [22:14] >> Okay. Excellent. Um, anything else from [22:18] anyone on the group? Particularly if [22:20] you're new, this is a very good time to [22:22] soak up any wisdom from the call. Any [22:24] questions, comments, or concerns? [22:29] >> What is the archive project? I asked [22:32] that. [22:34] Yeah. So, so we uh we had this idea that [22:39] um [22:41] so so in particular so you get a lot of [22:45] projects that are archived for various [22:46] reasons, right? So you get projects that [22:48] are archived because there's no [22:50] activity. Um and and that is that's one [22:54] case that's probably I would say I guess [22:56] maybe the least interesting case. But [22:58] you also have a lot of projects that get [23:00] um archived even when there is activity. [23:02] So you've seen this with some Google [23:04] projects where they've archived the open [23:06] source project and pulled the [23:07] development internal and so you get you [23:09] also see popular projects that have been [23:11] archived um for for various reasons that [23:16] um you know and it depends. Sometimes [23:18] it's a popular project and you've got a [23:20] maintainer who's just tired of working [23:21] on it or they've you know they've had a [23:24] baby or they got a new job or whatever. [23:28] There are lots of reasons for people to [23:29] stop working on projects. And so we [23:31] started this project [23:34] um with the idea that we would look at [23:35] maybe I forget the top x number of [23:38] projects on GitHub and manually look at [23:41] them and try to decide why they were [23:43] archived. [23:44] Um and we [23:48] so and we we found that that that just [23:50] wasn't getting much traction. We the [23:53] data that we were getting um from those [23:55] manual assessments wasn't particularly [23:58] interesting. Um, so I stopped working on [24:02] it and but Calie, who's one of the other [24:05] co-chairs of this group, was like, "No, [24:06] I think there's I think there's still [24:07] something there. I think we need to just [24:09] rethink rethink it entirely. Just [24:12] basically start over and maybe do [24:13] something else, but something around [24:16] projects being being archived. So So [24:19] that's where it is right now. It is it [24:21] it was an idea. That idea didn't work. [24:23] So we put it on the shelf. Um, but we [24:25] think there's still something there and [24:28] we just need to figure out what that is. [24:29] So, that's one of the things we're going [24:30] to put on the agenda when we don't have [24:32] anything else on the agenda and we're [24:33] just going to spend some time talking [24:34] about what that project should be. [24:36] >> Cool. That's awesome. That's I'm really [24:39] down with archives. So, [24:41] >> awesome. [24:42] >> Yeah. Yeah, that's a cool project. [24:45] There's so much information that I want [24:47] to get out of that, but it just is going [24:49] to require a single person to think [24:51] about it. And I'm not saying this is a [24:53] full-time. and saying for 3 to four [24:55] hours a week, I need someone to think [24:56] about that for about three or four [24:58] months [25:00] and we will have that done. Um, and it [25:02] will be a massive contribution. Um, the [25:05] signals that you can pull from that if [25:07] you could ever get to anything [25:08] predictive and even if you can get to [25:10] something descriptive, [25:11] that's a massively valuable piece [25:15] learning. Can I ask how you're [25:17] separating all the people leaving GitHub [25:20] and tracking that? [25:24] >> Yeah. So, this is specifically for [25:26] stewarded projects that were going [25:28] through an incubation process. So, [25:30] that's not whether or not they left [25:32] GitHub, it's whether or not they were no [25:34] longer in a stewarded ecosystem. So, [25:37] they were literally dropped from the [25:39] ecosystem. That's [25:40] >> not individual open projects like [25:42] projects that you guys have worked on [25:44] then. [25:45] >> Yeah. Uh yeah, so this is for projects [25:48] that are within the Linux Foundation [25:51] broadly. So it can be any sub [25:53] foundation, the Eclipse Foundation, the [25:54] Apache software foundation [25:57] >> and other sources. So we're also working [25:58] with Fedora as well, but I don't think [26:01] we're pulling from these stats for that. [26:03] Um but the archiving is particular to [26:08] does it reach a maturity within a [26:11] stewarded graduation process or does it [26:14] get removed? If you're interested in the [26:16] statistics around does it just move to [26:19] code or elsewhere. So am I and I'm still [26:22] working on figuring that out. Um, and [26:25] uh, if I get the answer, I'll tell you, [26:29] but that is not gerine to uh, whether or [26:31] not it uh, gets archived. [26:36] >> Yeah, because I was kind of trying to [26:37] look at all like big projects on GitHub [26:39] and looking at archive. And so this is [26:41] one of the ways that we thought about [26:42] narrowing it was looking at it in the [26:44] context of the foundation stats project [26:46] and looking at at those projects being [26:49] being archived. So that's that's a a [26:51] piece of it. But we could we could we [26:54] could here. Okay. So here's the thing. [26:56] This is the data science working group [26:57] and we can uh we can study these in [27:00] whatever way we want and build whatever [27:01] data sets we decide are interesting. So [27:04] if there's something that anyone wants [27:06] to wants to look at, we can certainly we [27:09] can certainly start just doing that. We [27:11] don't you know we we have some ideas of [27:13] of what we are thinking but it doesn't [27:16] have to be it doesn't have to be that. [27:17] anybody can work on really really [27:19] anything that they find interesting and [27:21] we'll see we'll see what we can do with [27:22] it. [27:23] >> Yeah. But you sound competent and you [27:27] sound like if you were to have a scope [27:30] co-developed, you might be able to get [27:31] it done. So what I would really [27:33] recommend is look over some of the [27:35] documentation that we have available. [27:37] Send me or nest questions around [27:39] anything that we have this week because [27:41] everyone else is at a conference. But if [27:44] the archives project or that space is [27:46] really interesting to you, I think 30 [27:48] minutes with myself and Calie and Ernest [27:52] all sitting down and talking, Don can be [27:54] there because Don is the central wisdom. [27:57] But in terms of getting you scoped in to [27:59] like understanding where we could move [28:01] on this and where you could have a [28:02] specific impact, those are the three [28:04] people I'd want to come together to [28:05] advise you on point you where. um and [28:08] then see what gains your interest and [28:10] then all of us are there to support your [28:12] code. [28:15] >> Awesome. [28:15] >> And I just I just threw a link in there [28:17] um to the the data set section of the [28:21] repository. So that has details about [28:23] the foundation stats projects that has [28:26] what we did on the archive project um [28:28] and then stopped doing. So you can you [28:30] can kind of poke through poke through [28:32] some of those and see see if there's [28:33] anything anything interesting. Um, yeah. [28:37] But yeah, also I do recommend kind of [28:39] starting with with uh Sal and Ernest and [28:41] and Cali because I so I've been doing [28:44] the the work I've been co-chairing the [28:46] data science working group uh for almost [28:50] three years and my plan is to step back [28:52] at the end of March. So um so I'll I'll [28:55] continue to participate but I'm going to [28:57] step down as co-chair at the end of [28:58] March. So that's that's part of why [29:00] working with I think Sal and Cali is [29:02] probably a better better step. [29:05] >> Yeah. But it's a really good support [29:07] system because on my side I'm s I'm very [29:10] much the open source volunteer that's [29:12] here because I want to know the answers [29:13] and Cali is Red Hat. So they've got Red [29:16] Hat behind them. So if we actually get [29:18] something that's interesting or you need [29:20] extra developer hours that's actually [29:22] there in this circumstance. So uh yeah, [29:24] you're not unsupported. You could [29:26] actually have a good degree of corporate [29:29] FTE hours on this if we scope it [29:32] correctly. So worth diving into seeing [29:35] if it's curious to you. And it's more [29:38] valuable to me to know what questions [29:39] you have after looking at these repos [29:42] than anything else. So send them to me. [29:44] >> Yeah, I'm taking a look right now. It's [29:47] >> I love [29:48] >> I'm a game developer by trade, artist by [29:51] trade, but then I've put on a million [29:53] hats. And I find that we've really as [29:57] humanity, we've screwed up uh a lot on [30:00] making things fun. And uh one of them is [30:03] archiving. Like there's a huge amount of [30:05] data out there that there's so many [30:08] people that want access to it. And [30:10] there's a lot of people like kids even [30:13] that want to mess with things to learn [30:16] but they just don't know how and it's [30:18] really complicated and as an artist most [30:21] programmers have no idea how to organize [30:23] things for the general public. [30:25] >> So like that's the biggest step like the [30:27] biggest crossover for me um is making [30:30] sure if there's stuff that needs to get [30:32] worked on there are people out there [30:33] wanting to work on it. Yeah, [30:36] >> I've talked to so many maker spaces that [30:38] don't know any of this stuff exists. [30:40] Like they don't know where to start. Um, [30:42] and it's kind of funny. So, this is [30:44] where I'm starting to be the I guess [30:46] I've been a tech artist a lot of times [30:48] in projects. And that's where I think [30:50] that the world needs a a little bit of a [30:52] in between person to go in between uh [30:54] tech and art and art is more general [30:57] populace. [30:59] >> That's where I want to step in. [31:02] >> Well, good. I'm glad you're here. I get [31:05] all of my dopamine from my GitHub PRs, [31:08] both accepting and providing. Um, [31:11] there's a lot of gamification in this [31:13] process. [31:14] >> Um, but yeah, I think for today, [31:18] honestly, just go give it a look. All of [31:20] your curio curiosity is valid and [31:22] useful. You can throw an issue, a [31:24] comment, a question, a Slack message. We [31:26] will respond. Let's see over the next [31:29] two weeks if you're just playing with [31:30] the content, getting some questions [31:32] answered, and then let's scope it in and [31:34] we'll have a call with you because that [31:35] would be interesting. Um, I do want to [31:39] ask, is there anything else that anyone [31:41] wants to either cover today or make sure [31:43] that we write down on this agenda [31:45] tentatively so we don't forget? [31:51] Uh, profound silence. I love that. [31:53] That's my favorite. Um, the last thing [31:56] that I will say is we're not quite to [31:59] the process of congratulating a new [32:02] maintainer in open source, but we're [32:03] very, very close. So, we're going to do [32:05] just a very quick we're almost to having [32:07] a new open source maintainer in this [32:09] group, which is Earnest. So, we're going [32:11] to give a small clap this week because [32:13] in two weeks we're going to do the [32:15] official handoff and they will be an [32:16] official maintainer and then we have to [32:18] give our official claps. Um, and I'm [32:21] super excited about that. So, uh, all [32:23] cheers to Ernest, who's been invaluable, [32:26] and I'm so excited to have them here. [32:30] >> Yeah, this is this is welld deserved [32:31] because what was happening was Ernest [32:33] was doing all of the the code reviews [32:34] and providing all of the feedback and [32:36] then pinging me and saying, "Hey, can [32:38] you merge this for me?" Um, which just [32:40] seemed silly to have me in the loop at [32:42] all. And so, Sal and I talked about it [32:44] and yeah, I think it's great. [32:47] >> Yeah, [32:47] >> congrats. [32:49] >> Thank you so much, everyone. Thank you, [32:51] Don. Thank you, sir. I'm happy to [32:54] continue contributing. [32:56] >> Yeah. Yeah. No, it's been amazing. I've [32:59] never I literally in my entire career [33:01] have never had to just stop and be like, [33:04] "No, no, no. This is not a contributor. [33:06] This is a maintainer." So, good. I'm [33:09] glad. We'll get you trained in. Um, [33:12] excellent. Well, it could be a slightly [33:14] shorter meeting uh today if we've got [33:16] the agenda all settled. Thank you all [33:18] for coming, those that come often and [33:20] those that are new. Um, excellent [33:22] session and when you come back next time [33:25] there will be a lot more faces on this [33:27] call. It was really nice to have a [33:29] smaller group here today. Um, so thank [33:32] you for that and we'll see you I think [33:34] next time. [33:36] >> Thanks everybody. [33:38] >> Have a good one. Bye everyone. Bye.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Data Science WG, Feb 24 2026.md|CHAOSS Data Science WG, Feb 24 2026 by YouTube]] ## Highlights - Uh do we have any on those? Go ahead. >> Uh yeah, I give some some quick updates. There's not a lot. Um I've gotten a lot of really good feedback on the funding impact measurement guide, which means now that there's an awful lot of work in trying to synthesize that feedback and figure out what goes what goes in and what what doesn't. and I just honestly haven't had enough time to do that yet. So, um, so that's where that is. I've gotten lots of good feedback. As soon as I have time to sit down with that guide, which will probably be maybe after my little wave of conferences or maybe ([View Highlight](https://read.readwise.io/read/01kpb4h7td3yfae800rtczyqss)) - Tags: 👻 ai highlighted - think we're going to put that on an agenda item for one of these meetings in the in the future. Um, and then the uh research software impact. Uh, Matt's been super busy and so I haven't been bugging him to ask him where that is, but that's the one that Matt's been driving along with some folks at Curious uh, from a university standpoint. So, that's what we have on the practitioner guides. Okay, that brings us into project ([View Highlight](https://read.readwise.io/read/01kpb4h7tnxkbyxwpfgx2d40p8)) - Tags: 👻 ai highlighted - first pass of that. So, I think it would be a really really good idea for us to uh come together and get any lessons learned out of that submission. Um, but I also think it might be worth having a grant focused working group for chaos is something that I have seen come out of that interaction. That's a super super high level. Um, but Ernest, do you have anything that you want to And there's a couple of new people on this call. So, do you want to describe the foundation stats just overall as a project? ([View Highlight](https://read.readwise.io/read/01kpb4h7tz7y0eb6snetv01tz9)) - Tags: 👻 ai highlighted - something that you're interested in attending. I can't believe All Things Open CFP is already open, but I'll submit. I'm ready. >> Yep. >> Okay. Excellent. Um, anything else from anyone on the group? Particularly if you're new, this is a very good time to soak up any wisdom from the call. Any questions, comments, or concerns? >> What is the archive project? I asked ([View Highlight](https://read.readwise.io/read/01kpb4h7yhr3my9k5myssew3c6)) - Tags: 👻 ai highlighted - it and but Calie, who's one of the other co-chairs of this group, was like, "No, I think there's I think there's still something there. I think we need to just rethink rethink it entirely. Just basically start over and maybe do something else, but something around projects being being archived. So So that's where it is right now. It is it it was an idea. That idea didn't work. So we put it on the shelf. Um, but we think there's still something there and we just need to figure out what that is. So, that's one of the things we're going ([View Highlight](https://read.readwise.io/read/01kpb4h83s6qfzt1h9e81493x4)) - Tags: 👻 ai highlighted - maintainer in open source, but we're very, very close. So, we're going to do just a very quick we're almost to having a new open source maintainer in this group, which is Earnest. So, we're going to give a small clap this week because in two weeks we're going to do the official handoff and they will be an official maintainer and then we have to give our official claps. Um, and I'm super excited about that. So, uh, all cheers to Ernest, who's been invaluable, and I'm so excited to have them here. ([View Highlight](https://read.readwise.io/read/01kpb4h87yczx4jwdn91xtaz8q)) - Tags: 👻 ai highlighted