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

CHAOSS Data Science WG March 24 2026 ![rw-book-cover](https://img.youtube.com/vi/yS5CB7F7p7s/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Data Science WG March 24 2026](https://www.youtube.com/watch?v=yS5CB7F7p7s) > [!note]+ Document Notes > tags: #chaoss #open-source-analytics #data-science #maintainer-transition #community-governance > author: CHAOSS Data Science Working Group > source: YouTube > reference: https://www.youtube.com/watch?v=yS5CB7F7p7s > date created: 2024-12-19 16:15 > > # 🏷️ Title: CHAOSS Data Science WG March 24 2026 >  ## 🧰 Action Inbox - [H1] Document practitioner guide review process — before Don's transition #documentation - [H2] Complete funding impact measurement guide — end of March deadline #practitioner-guides - [H3] Finalize maintainer sponsorship documentation — next week with Ernest #governance ## 🧭 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/) - [Eight Not (8knot)](https://github.com/8knot-io/variable-speed-limit) - [Augur](https://github.com/chaoss/augur) ## 📝 Summary - CHAOSS Data Science Working Group transition meeting with Don stepping down as co-chair after 3-year Sloan Foundation funding period - Multiple project updates including foundation stats rebranding to "Leoscope" and new self-merge rate visualization - Commercial open source software dataset merged with confidence scores from Serena and OSS Capital - Practitioner guide publishing process documentation and knowledge transfer discussions - Maintainer sponsorship program finalization and potential GitHub repository mirroring to Codeberg ## 📖 Main Content The meeting covered a significant transition as Don announced his departure from the co-chair role after completing a three-year Director of Data Science position funded by the Sloan Foundation. The working group discussed multiple active projects including the Foundation Stats project (being renamed to "Leoscope"), new data visualization notebooks, and practitioner guide publishing processes. Key technical updates included a demonstration of a self-merge rate analysis notebook and the integration of commercial open source company data from multiple sources. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/yS5CB7F7p7s?t=0) — [H1] Don's co-chair transition announcement - Key idea: Stepping down after 3-year Sloan Foundation funding period ends - Evidence: "The Sloan Foundation had funded this position as director of data science for three years" #### ⏱️ [03:45](https://youtu.be/yS5CB7F7p7s?t=225) — [H2] Research software impact guide published - Key idea: Completed practitioner guide with Matt German Prey and Claire Delan - Evidence: "We got the research software impact guide published" #### ⏱️ [05:20](https://youtu.be/yS5CB7F7p7s?t=320) — [H3] Practitioner guide review process documentation needed - Key idea: Need to document review criteria and publishing workflow - Evidence: "Would this guide help someone who's relatively new to this particular topic make some progress" #### ⏱️ [09:15](https://youtu.be/yS5CB7F7p7s?t=555) — [H2] Foundation stats project rebranding to Leoscope - Key idea: Project evolution requires new name reflecting ecosystem-level analytics - Evidence: "Ecosystem then scope is to measure. So I just say oscope" #### ⏱️ [12:30](https://youtu.be/yS5CB7F7p7s?t=750) — [H2] Sovereign Tech Fund application in progress - Key idea: Ernest working on STF fellowship application for maintenance funding - Evidence: "We started writing for the sovereignty tech fellowship which I think we should be able to meet those requirements" #### ⏱️ [16:45](https://youtu.be/yS5CB7F7p7s?t=1005) — [H1] Self-merge rate visualization notebook demonstration - Key idea: New template notebook analyzing PRs merged by same author who opened them - Evidence: "We're dealing with like a selfmerge rate visualization" #### ⏱️ [25:10](https://youtu.be/yS5CB7F7p7s?t=1510) — [H2] Commercial open source software dataset integration - Key idea: Merged CSV with company data from multiple sources including confidence scores - Evidence: "Basic details about commercial open source companies... from Serena and OSS Capital" #### ⏱️ [30:20](https://youtu.be/yS5CB7F7p7s?t=1820) — [H3] Dataset documentation needed - Key idea: README required to explain data sources and methodology - Evidence: "Right now the readme is the data and more details are coming soon" #### ⏱️ [33:15](https://youtu.be/yS5CB7F7p7s?t=1995) — [H2] Maintainer sponsorship program finalization - Key idea: Working with Ernest to complete sponsorship documentation - Evidence: "Hopefully by the end of the next week we're going to have that completely written out" #### ⏱️ [36:40](https://youtu.be/yS5CB7F7p7s?t=2200) — [H3] GitHub repository mirroring discussion - Key idea: Considering Codeberg mirroring for resilience after recent outages - Evidence: "Do we want to consider for chaos mirroring the chaos GitHub repository on Codeberg" #### ⏱️ [39:50](https://youtu.be/yS5CB7F7p7s?t=2390) — [H3] All Things Open CFP reminder - Key idea: Conference CFP deadline March 31st in Raleigh, North Carolina - Evidence: "All things open. The CFP is March 31st" ## 📚 References - [CHAOSS Practitioner Guides](https://chaoss.community/practitioner-guides/) - [Sovereign Tech Fund](https://www.sovereigntechfund.de/) - [All Things Open Conference](https://allthingsopen.org/) ## 🗣️ Paraphrase - Don is transitioning away from co-chair role after completing his funded position, with S and Calie continuing leadership - Multiple practitioner guides are in progress with new documentation processes being established - The Foundation Stats project is evolving into "Leoscope" focusing on ecosystem-level analytics and applying for funding - New visualization notebooks are being created as templates, starting with self-merge rate analysis ## 📰 Newsletter The CHAOSS Data Science Working Group is experiencing a leadership transition as Don steps down from his co-chair role after completing a successful three-year tenure. This creates exciting opportunities for community members to get more involved in practitioner guide development and data visualization projects. The group continues advancing open source analytics with new tools like the "Leoscope" project for ecosystem measurement and template notebooks for community contributions. These resources make it easier for newcomers to contribute meaningful analysis to the open source community. Resources: [CHAOSS Community](https://chaoss.community/), [Augur Analytics](https://github.com/chaoss/augur), [Practitioner Guides](https://chaoss.community/practitioner-guides/) ## ✅ Action Items #### DevRel - Developer education: Create template notebooks for community contributors to analyze open source metrics - Documentation: Establish clear review criteria and publishing workflow for practitioner guides - Community engagement: Support maintainer sponsorship program to increase participation #### OSPO - Strategic alignment: Align CHAOSS metrics with organizational open source health measurement needs - Community engagement: Support funding applications for ecosystem analytics projects - Developer support: Provide consultation on open source project health assessment #### Community - Maintainers: Develop sponsorship programs to support ongoing maintenance work - Contributors: Create accessible onboarding through template notebooks and clear documentation - Ecosystem: Coordinate cross-project analytics through tools like Leoscope #### WordPress - Community: Adapt CHAOSS practitioner guides for WordPress ecosystem health measurement - Documentation: Apply practitioner guide review processes to WordPress documentation projects - Meta: Consider integrating CHAOSS metrics into WordPress.org project health dashboards ## 🧪 Hypotheses - Template notebooks reduce barriers to contributing open source analytics - Ecosystem-level metrics provide better sustainability insights than individual project metrics - Maintainer sponsorship programs increase long-term project health - Repository mirroring improves community resilience during platform outages ### 📊 Methodology - Notebook template effectiveness: Track contributor onboarding success rates and time-to-first-contribution - Ecosystem metrics validation: Compare Leoscope insights against traditional project-level measurements - Sponsorship program impact: Measure maintainer retention and contribution consistency ### ❓ Questions - How can CHAOSS metrics be better integrated into daily open source project management? - What ecosystem-level indicators best predict project sustainability? - How should confidence scores in aggregated datasets be validated and communicated? ### 🔮 Future Research - Development of standardized ecosystem health measurement frameworks - Investigation of commercial open source company sustainability patterns - Analysis of self-merge rates as indicators of project maturity and governance ### 💡 Implications - Practice: Template notebooks enable broader community participation in analytics - Policy: Maintainer sponsorship models could inform foundation funding strategies - Education: Practitioner guides bridge academic metrics research with practical application - Funding: Ecosystem analytics tools like Leoscope support evidence-based funding decisions ### 🧠 Learning Styles Assessment Reading level estimate: Grade 12-14 (technical content with domain-specific vocabulary) #### 👀 Visual learners - Present: Jupyter notebook demonstrations, data visualizations, charts - Improve: Architecture diagrams showing data flow between Augur, notebooks, and 8knot #### 🔊 Aural learners - Present: Full meeting recording with clear audio - Improve: Segmented audio summaries of key decisions #### 🗣️ Verbal learners - Present: Technical terms explained in context, project naming rationale - Improve: Glossary of CHAOSS-specific terminology #### 🧩 Kinesthetic learners - Present: Step-by-step notebook walkthroughs, hands-on demonstration - Improve: Interactive tutorial for creating first visualization #### 🧠 Logical learners - Present: Clear project timelines, funding deadlines, decision frameworks - Improve: Flowcharts for practitioner guide review and publishing process #### 🧑‍🤝‍🧑 Social learners - Present: Working group collaboration, peer review processes - Improve: Structured mentorship for new contributors #### 🧘‍♀️ Solitary learners - Present: Template notebooks for independent learning - Improve: Self-assessment checklists for contribution readiness #### 🌿 Naturalistic learners - Present: Ecosystem metaphors in project naming and description - Improve: Connection between open source health and biological ecosystem concepts ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Video captions available, clear speaker identification - Improve: Structured headings in meeting notes, descriptive alt text for visualizations #### Keyboard navigation - Present: Standard video player controls - Improve: Timestamp navigation shortcuts #### Contrast and readability - Present: Clear audio quality, readable notebook displays - Improve: High contrast mode for code demonstrations #### Text resizing and reflow - Present: Responsive meeting notes format - Improve: Scalable notebook font sizes in demonstrations #### Media and captions - Present: Full video with auto-generated captions - Improve: Human-reviewed captions, downloadable transcript #### Forms and interactions - Present: Standard Zoom meeting controls - Improve: Alternative participation methods for audio/video issues ### 🌍 DEIB Assessment #### Cultural breadth - Present: International working group participation, global time zone considerations - Improve: Multi-language documentation for broader contributor base #### Inclusive language - Present: Professional, technical discussion without exclusionary terms - Improve: Plain language summaries for complex technical concepts #### Neurodiversity support - Present: Structured agenda, consistent meeting format - Improve: Written follow-up for all verbal decisions #### Representation - Present: Diverse technical perspectives and project approaches - Improve: Broader geographic representation in leadership transitions #### Psychological safety - Present: Respectful discussion of project changes and concerns - Improve: Clear escalation paths for technical disagreements ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear cause-effect relationships between funding cycles and role transitions - Inductive strength: Pattern recognition in successful practitioner guide development - Causal reasoning: Connection between documentation quality and contributor onboarding success - Analogical strength: Comparison of ecosystem analytics to biological ecosystem measurement #### Fallacies - Appeal to authority: Reliance on funder preferences without independent validation - False urgency: March deadlines creating pressure without clear justification #### Tone of voice - Overall tone: Professional, collaborative, forward-looking with appropriate acknowledgment of transitions ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - Attack: No attack behaviors identified - Reverse victim/offender: No victim/offender dynamics present - Emotional cues: Positive, supportive language around transitions and new contributors ## 🎯 Conclusion The CHAOSS Data Science Working Group demonstrated strong continuity planning during leadership transitions while advancing multiple technical initiatives. The development of template notebooks and documentation processes creates sustainable pathways for community contribution. Key next steps include completing funding applications, finalizing sponsorship programs, and establishing clear knowledge transfer documentation to ensure project momentum continues beyond individual contributor changes. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Split level: H3 ### [H1] Open source analytics requires accessible contributor onboarding > [!quote] [CHAOSS Data Science WG March 24 2026](https://youtu.be/yS5CB7F7p7s) by CHAOSS Data Science Working Group via YouTube. Published 2026-03-24. Accessed 2024-12-19. > "Template notebook being very explanatory like detailed because we're also trying to work in a more of a template notebook so that every new contributor can just see it and know the roadmap." Template notebooks reduce technical barriers for community participation in open source measurement. [view highlight](https://youtu.be/yS5CB7F7p7s?t=1005#H1) #xref #articleseed ID:rw_chaoss_templates ### [H2] Practitioner guides need consistent review frameworks > [!quote] [CHAOSS Data Science WG March 24 2026](https://youtu.be/yS5CB7F7p7s) > "The biggest thing is alignment with the audience. The practitioner guides are designed for people who are not experts in a topic." Clear review criteria ensure guides serve their intended learning objectives. [view highlight](https://youtu.be/yS5CB7F7p7s?t=320#H2) #xref ID:rw_guide_review --- ### 🔖 Atomic Split Pad (Zettel Candidates) Split level: H4 #### [Z1] Self-merge rates indicate project governance maturity - Scope: Projects with formal review processes versus informal contribution models - Pointer: 16:45 notebook demonstration - Links: [[Code-Review-Practices]] [[Project-Governance]] #### [Z2] Ecosystem-level metrics complement project-specific measurements - Scope: Multi-project sustainability assessment frameworks - Pointer: 09:15 Leoscope discussion - Links: [[Sustainability-Metrics]] [[Open-Source-Ecosystems]] --- ### ✏️ Fleeting Queue - [F1] Research confidence score validation methods — commercial OSS dataset #fleeting #inbox - [F2] Explore Codeberg mirroring automation — GitHub resilience #fleeting #inbox - [F3] Document 8knot visualization integration workflow — contributor onboarding #fleeting #inbox --- ## Full Transcript [00:00] Okay, welcome everyone to the chaos data [00:03] science working group meeting for March [00:06] 24th. Question of the day is something [00:08] you enjoy about spring. Um, yeah, I'm [00:12] also with S. It's not winter, so that's [00:14] that's better. Although to be fair, in [00:16] in the UK it's it's still rainy and [00:19] chilly in spring. Um, more daylight. [00:22] Yeah, that's great. Love that. Uh, [00:26] plants and animals. Totally. [00:30] Um, all right. So, uh, let's go ahead [00:33] and and kick off on the agenda. So, I [00:37] think most or all of you know that I'm [00:39] actually stepping down as co-chair at [00:41] the end of this month. So I am uh [00:45] basically the funding so the Sloan [00:48] Foundation had funded this position as [00:50] director of data science for three years [00:54] and so that three years is up at the end [00:56] of end of March and so I've I've decided [01:00] to step down as co-chair partly because [01:02] I feel like S and Calie um as co-chairs [01:05] and Ernest as a maintainer I feel like [01:07] y'all have got this pretty well pretty [01:09] well covered. So, I think I'm going to [01:11] focus on other things within chaos. So, [01:13] I'm not leaving chaos. I'm still on the [01:16] governing board, but I'm going to shift [01:18] my focus to continuing to co-chair the [01:21] OSPO uh working group and funding impact [01:23] uh measurement working groups, which are [01:26] other things that I've been involved in [01:27] and are more more well aligned with the [01:30] type of consulting that I plan to do [01:32] after taking April and May off. So, I'm [01:35] going to take some time off. I'm going [01:36] to relax. I'm going to chill out. my [01:38] mom's gonna come visit me here in the UK [01:40] for three weeks. So yeah, so I'm looking [01:44] forward to that. [01:46] Um but yeah, so this does mean that this [01:47] is this is probably my last uh data [01:50] science working group meeting at least [01:51] for a while. I I may opt in and out. [01:54] We'll see see what's going on. [01:57] Um [01:59] okay, a couple of practitioner guide [02:01] updates. I was able to sync up with Matt [02:04] German Prey and we got the research [02:06] software impact guide published. So that [02:08] was something that he'd been working [02:10] with Claire Delan and a few others in [02:11] the university OSPO working group. Um [02:15] and they'd been working on that for a [02:16] while. So we we took it and and got it [02:19] published. So that that felt good to get [02:21] one to get one out. Um the funding [02:23] impact measurement uh practitioner [02:25] guide, that one I do still plan to [02:27] finish that at the end of March. So I'm [02:29] going to continue to to work on that. [02:31] I've got loads of edits from people um [02:34] suggestions from people that I just need [02:35] to um figure out how to how many of [02:38] those I can incorporate and then get [02:40] that one out the door. And then the [02:43] other one that we have kind of work in [02:44] progress right now is the usage adoption [02:46] and popularity which I think no one has [02:50] really had time to work on so much. So [02:53] um so we keep tracking that one and [02:54] eventually we'll set up some time in [02:56] this meeting and and talk about it. Um, [02:59] is that something that you would still [03:00] be interested in being like with [03:02] stepping down from the chair? Are you [03:04] still like wanting to be involved in [03:07] practitioner guides or like kind of what [03:11] where do you see that going for [03:13] yourself? [03:14] >> Yeah. So, I'm I am happy to help out [03:16] with practitioner guides for sure. [03:18] >> Um, I'm also happy if people just want [03:20] to do them and I'm not involved. That's [03:23] also totally cool. like I don't I don't [03:25] feel like I don't feel like I have to be [03:26] involved in the practitioner guides, but [03:28] I am I am also happy to be involved in [03:31] them because it is something that I that [03:33] I care a lot about. And in particular, [03:35] this one usage, adoption, and popular [03:37] popularity is a topic that I I care [03:40] about quite a bit. So, I'm I'm still [03:41] happy to help with that. [03:43] >> Do you have written down anywhere like [03:45] and this probably is like more of an [03:46] unofficial thing, but like when you [03:48] review practitioner guides, what are the [03:51] things that you are looking at? um like [03:54] what are Yeah. What what is the lens [03:56] that you're reviewing from? [04:00] >> Yeah. So I would say the biggest thing [04:03] is is alignment with the audience. So [04:06] the practitioner guides are are designed [04:09] for people who are not experts in a [04:11] topic. Um even the advanced guides are [04:14] still for people who are still learning [04:16] how to do the thing. So, I would say [04:19] that's the biggest thing that I look for [04:22] is, you know, would this guide help [04:24] someone who's relatively new to this [04:26] particular topic um make some progress [04:29] on whatever whatever this topic is. So, [04:32] that's one of the biggest things that I [04:33] look for. And then I also look for [04:35] consistency with the other guides. So, [04:37] there's there's kind of a format, [04:38] there's some common elements. I try to [04:40] make sure that the guides kind of fall [04:42] into into some of the same some of the [04:45] same patterns so that they look like [04:46] more of a cohesive unit. [04:49] >> Okay. if there's like things that you [04:50] think of uh if you want to write those [04:52] down in a document for since that like [04:55] you kind of been the main person that is [04:57] reviewing the practitioner guides and I [04:59] probably will still like be like hey Don [05:01] for the first couple of like just [05:03] getting another eye on it but to be able [05:05] to I feel like transfer that reviewer [05:08] role over having some like just view [05:11] into how you've thought about the guides [05:13] and reviewing them I think would be [05:15] helpful. [05:17] >> Yeah, absolutely. And that's um so [05:20] that's also paired with I was just [05:22] working with Elizabeth and she um uh she [05:25] had started to document and then I kind [05:27] of finished it the process for [05:29] publishing a practitioner guide. [05:30] >> Yep. [05:31] >> Um because it's not it's not as easy as [05:33] just pring it into the data science [05:34] working group repository. There's a bit [05:36] that has to be done by someone with um [05:39] edit access in WordPress. So there are [05:42] some other things that that have to [05:44] happen and so we've started documenting [05:45] some of that but I hadn't really thought [05:47] about the review process. So I will I'll [05:50] work on that as well. [05:52] >> Yeah, those documents probably can live [05:53] in the in like I kind of see them under [05:56] a similar umbrella. Um so then the [05:58] things that you because there's some [06:01] stuffs that you don't know how like [06:02] you're like oh it's you think about it [06:04] as you go but anything that you can [06:05] write down means that we don't need to [06:08] ask you. [06:11] Yeah, for sure. Plus, it's just good to [06:13] have documentation on on stuff like [06:15] that. Anyways, so I will I'll think more [06:17] about that and start working on [06:18] something. [06:19] >> Yeah, I know I keep on saying this, but [06:21] I do really want to do the usage [06:23] adoption and popularity and plan on [06:26] doing it. I've just had to completely [06:28] focus on Augur for the last month. Um [06:32] so, um I'm hoping that end is very near. [06:38] >> Yeah, fair enough. We all have Yeah. [06:40] days and weeks like that for sure. [06:44] >> Oh, sorry. [06:45] >> Oh, no. Go ahead. [06:47] >> Um, just with all these related topics [06:50] made me think that I'm making a um like [06:54] notebook of how to identify contributors [06:58] for the chaos board elections. Um, [07:02] I'm probably would go under Augur [07:04] notebooks. I think that it would make [07:06] sense for to contribute that upstream. [07:08] Um, and so maybe I'll make like a [07:10] notebook for it. I don't know if like [07:11] there's just like a place that you're [07:12] kind of putting like more processy type [07:15] things because I feel like this would be [07:16] kind of somewhat under like pro how like [07:20] to do a certain process. I don't know if [07:22] it should should stay under because it's [07:23] not really analysis. It's more of like [07:26] chaos um process review like I don't [07:30] know it it kind of I don't know if it [07:31] should fall under the same branch of [07:33] like what you're talking about here of [07:34] like how do we go about doing this or if [07:36] it should go under more anal like augur [07:39] analysis. [07:41] >> Yeah, that's a good question. I was sort [07:42] of thinking about putting the [07:43] practitioner guide process into the part [07:47] of the repo that has the practitioner [07:48] guide so that everything's in [07:51] >> because I don't think we have we have [07:53] that but yeah so I think maybe doing [07:55] that in the augur notebook would be [07:56] good. It might also be good to link to [07:58] have the election um officers link it [08:02] from some of the they're working on some [08:04] frequently asked questions and things [08:05] like that. So it might be good to get it [08:07] linked from that as well. Okay, [08:11] >> cool. Um, okay. Anything else on the [08:13] practitioner guides? [08:17] Okay, project updates. Let's start with [08:19] uh Ernest and S on the foundation stats. [08:25] >> Yeah, thank you. So, for the past couple [08:28] of weeks, we've been trying to um you [08:31] know, after we figured that we could not [08:34] meet uh the requirement for the SSF U [08:38] grant. So we started writing for the [08:42] sovereignty tech fellowship [08:45] which I think um we should be able to [08:47] meet those requirements. I think I made [08:49] a couple of drafts. Sal reviewed it like [08:53] I think today and it will be nice if you [08:56] and Khalan as well have a look you know [08:59] and um because there is a requirement on [09:02] STF that says you have to be like [09:05] contribute to minimum of three three [09:06] open source projects. Currently I I [09:09] contribute to two which is chaos data [09:12] chaos working group data science working [09:15] group and open telemetry that I did my [09:17] LFX. So I'm looking at I'm currently [09:20] like I started looking at 8 knots I mean [09:23] 8 not but I think I lean towards 8 not [09:26] more because it's I think it's the [09:28] quickest way I could do something. Yeah, [09:30] even though it's been long I worked on [09:32] dash maybe four years ago just for one [09:34] project but I should be able to find my [09:36] my reading. So yeah, I'm saying that now [09:40] in case Kali has a quick um issue that [09:43] she thinks I could pass I quickly work [09:45] on. But I'm definitely exploring the [09:48] issues myself. But you know yeah that's [09:51] pretty much the general update. [09:53] >> Yeah, you should definitely talk to Kyle [09:56] actually. Um Kyle would be the best [09:58] point of contact. um he's also in this [10:00] call for um getting started with Augur. [10:03] There's also an Augur 8 knot working [10:05] group channel. Um so and we're trying to [10:08] work in 8 right now to make sure that [10:11] all of our issues are up to date. So [10:13] then somebody like you can more easily [10:15] come in and start contributing. [10:18] There's also kind of a good path of [10:21] which we'll talk about in a second of [10:22] like working on maybe like a [10:24] visualization notebook and then the next [10:26] step of that is putting is making that [10:28] visualization in 8 knot which Kyle will [10:31] be showing something like what that [10:33] looks like um a little bit later on. [10:37] >> Yeah, that's great. I'll reach out to [10:38] you maybe Slack. [10:43] >> Thank you. [10:44] >> Yeah, [10:45] >> I don't know. Okay. Yeah. Yeah. Uh, the [10:48] final note there. Um, yeah. So, we're [10:50] going to be working through this and [10:51] Ernest, we should meet like probably [10:53] Monday next week just to do a final [10:54] overview. I'm also gonna go and work on [10:58] the repo a little bit to make it look [11:00] more CNCF. [11:02] Uh, which is generally good. Um, but [11:05] yeah, I think we're at a reasonably good [11:07] spot. And I honestly think even with the [11:09] really minor deficits that we have [11:11] around like contributions and whatnot, [11:14] it is so strong and compelling for the [11:17] funding because we can essentially [11:19] provide a CRA baseline which uh I think [11:24] they're really going to like. [11:27] >> Yeah. Then um I don't know S if we [11:30] should talk about the uh name change we [11:33] are thinking or we should take that to [11:36] Slack. [11:38] >> Yeah. Um why don't you just uh announce [11:40] it here and then we can also bring it to [11:42] Slack. But I think it's a great name. [11:46] >> Yeah. So um Salah and I thought we um in [11:50] in the coming days we see foundational [11:52] start like growing to have it own name [11:56] just beyond the foundational you know [11:59] statistics that we currently call it and [12:02] the name I came up with is um hopefully [12:05] I pronounce it welloscope [12:08] I sort of you know rest on the way ago [12:10] was named to now say okay ago is [12:13] measuring um open source project while [12:16] we are doing ecosystem level kind of [12:19] analytics to to to see how communication [12:22] channels are informing um sustainability [12:25] questions and all. So is like ecosystem [12:28] then scope is to measure. So I just say [12:30] oscope you know and uh I'm going to type [12:33] that in chat in case I did not pronounce [12:35] it well you guys can correct me. [12:39] Yeah, I mean I would say that we we just [12:42] uh so I'm really bad at naming things [12:44] and I probably just threw a name [12:45] together for this and like you said it's [12:48] um it's evolved quite a bit uh since you [12:51] started. So my perspective on projects [12:54] like this is that those of you who are [12:56] working on the project can rename it to [12:58] whatever you'd like. Uh I don't have any [13:00] strong feelings. I don't know if I don't [13:02] know if Calie or anybody else has any [13:06] strong feelings. [13:09] Nope. I feel similar about naming. [13:13] >> Yep. [13:16] >> That's how Eight Not came to be. Um was [13:18] me and James just being outdoorsy people [13:21] and naming entire set of project names [13:24] after different outdoorsy titles. [13:29] Cool. [13:32] All right. Anything else on the uh [13:36] leoscope project or foundation staff [13:39] project? [13:40] >> One last note on like Tuesday of next [13:44] week. Um I'm going to send some links [13:46] out to probably Don and Cali. If you [13:48] have 10 minutes just to give our [13:52] submission a review or anyone else you [13:54] would recommend. Maybe I'll just throw [13:55] it on the main chat, but I'm looking for [13:56] just eyes on it before we do a final [13:58] submit. [14:00] What is this submission for exactly? [14:04] >> This is for the Sovereign Tech Fund uh [14:06] which is looking to provide Yeah. [14:08] maintenance funding. [14:11] >> Yes. [14:13] >> Yeah, I'm happy to take a look at it. [14:15] >> Cool. [14:19] >> Okay. Uh next project. It looks like [14:22] Cali and uh KO have some updates. [14:26] >> Yeah. Um, I think mainly it'll be we're [14:29] going to have Kyle kind of walk through [14:31] the notebook. Um, this will be kind of [14:33] the first notebook that's been made [14:34] since the migration over to the data [14:37] science working group for this type of [14:38] work of making the a visualization based [14:42] off of a chaos definition. And once that [14:45] is merged, then it moves over to the 8 [14:48] knot side and will be integrated into 8 [14:51] knot as a visualization there. Um so [14:55] still working to get all of the like [14:58] linked um issues. So then there is an [15:01] issue on 8not and an issue on in this um [15:05] repository where they link to each other [15:07] um because we do have a bit of a backlog [15:09] of them but people are open to if they [15:13] have an idea for a visualization um that [15:16] is um please go for it or anything that [15:19] is especially if something is under [15:20] already defined visualization under [15:23] chaos in the metrics models um we're [15:26] really trying to kind of pull together [15:28] all of the different work that's been [15:30] done in chaos. Um, and yeah, and so I'll [15:34] kind of pass it off to Kaio so you can [15:36] walk through the first notebook. [15:39] >> Do you want me to stop sharing so that [15:40] you can share or do you want to send me [15:42] a link? I'm good either way. [15:44] >> Uh, yeah, I'll try to share it here. [15:46] >> Perfect. [15:47] >> I I always have problems sharing from um [15:52] Zoom instead of uh Google, but let's [15:55] see. [16:15] Just a second. [17:00] Okay. So, if anyone can help just to [17:03] share [17:05] for me to share just like one window or [17:08] something, [17:10] >> you should just be able to share. [17:13] Um, so are you using the desktop or are [17:15] you do you have the the Zoom app or [17:18] Yeah, there we go. [17:18] >> Yeah, it is. There you go. [17:20] >> I think now you can see. Yeah. [17:22] >> So, uh, you can see just the [17:26] >> the Jupyter Lab is it? [17:28] >> Yes, we can see a little bit, but yeah, [17:31] we can see the whole screen for the [17:32] Jupiter lab. [17:34] >> Okay, sounds good. All right, so like [17:37] finally uh being able to introduce [17:40] myself to everyone in this working [17:41] group. So Kyle, um I'm also like working [17:45] alongside Kylie and Adrian on the data [17:47] team of Ospo and Red Hat and uh yeah, so [17:51] it's great to finally like introduce [17:53] like the first notebook uh also my first [17:57] notebook into this working data uh group [17:59] that we're going to put into 8 knot soon [18:02] as well. So I tried to have it the [18:06] notebook being very [18:08] um explanatory like detailed like [18:11] because we're also trying to work in a [18:13] more of a template notebook so that [18:15] every new contributor can just pretty [18:18] much see it and know like the road map [18:20] or the path to uh create and work into [18:24] new uh visualizations. So this one is a [18:27] very self-explanatory one as well. So [18:30] we're dealing with like a selfmerge rate [18:32] visualization. So we just wanted to [18:35] explore how many of um the PRs being [18:39] merged were actually being merged by the [18:41] same author or the same contributor that [18:44] that opened the PR. So just going [18:46] through the visualization here. Uh we [18:50] have uh the installing the dependencies [18:52] which uh we're also working into like [18:55] updating the the way that we manage the [18:58] packages or install the packages. In [19:00] this instance here I'm taking advantage [19:02] of the all the package that are already [19:05] being installed or are installed by [19:07] Anaconda. But I also put um an option to [19:11] have like a requirements text where you [19:14] could pretty much install all of the [19:16] require uh the the dependencies through [19:18] that text. Uh and I also loaded the [19:22] credentials through like a JSON which is [19:24] another option that you can you can have [19:26] as well. Uh then the connection for the [19:29] database. Uh and then for the queries [19:32] that's where we start to get like the [19:34] information that we need for the plots. [19:36] uh we first get the repo ids and the [19:39] repo names from the augur data and then [19:41] for this specifically uh visualization [19:45] we get sorry we get the contributor ID [19:49] which is the person who opened the PR [19:51] and we also we also get the merger [19:54] contributor ID which is pretty much the [19:56] person who merged the PR. So that [19:59] information will give us the base to [20:01] compare each other and see if the if it [20:05] was self merged or not. That's where we [20:07] get like our information. Uh I also [20:10] introduced another optional filter. So [20:12] let's say you want to analyze [20:16] how many uh were selfmerged but also the [20:19] PRs who had like at least uh 10 lines of [20:23] code changed or at the most 500 lines of [20:27] change co uh uh lines of code modified [20:30] or something like this. So this kinds of [20:33] like adds a bit more detail and [20:36] information into your plot as well which [20:38] I think makes the analysis a bit uh like [20:41] a bit more fine-tuned [20:44] and then uh you can see a bit of like [20:46] the representation here. So for this [20:48] example, there's no filters applied. So [20:50] there's 1,900 rows. Uh and then this is [20:54] pretty much like the data processing [20:56] here where we get to see if the author [20:59] is the same as the one that merged the [21:02] PR. [21:04] Uh [21:05] yeah. So and then we get the plot here. [21:09] So this plot here is pretty much showing [21:11] like the curve uh the blue curves just [21:14] showed the total number of PRs merged. [21:16] And then the red curve shows like the [21:18] the amount of PRs who were merged uh by [21:21] the same author who opened the PR. [21:24] And then we had another plot as well [21:26] which is pretty much the rate of the [21:29] selfmerge which is just the selfmerge uh [21:32] number over the total number of uh PRs [21:35] merged. So there you go. So that's uh [21:39] just a [21:41] rep like just the plots. Uh and then I [21:44] just wanted to show you here as well. Um [21:47] for example, like if we change here, so [21:50] we want let's say uh we want to filter [21:54] like at least 50 minimal like lines of [21:57] code change in 100. So I can just go [22:03] run again the query [22:06] and run this one. And you can see that [22:07] now with the additional filter there's [22:10] only 176. That was fine. that that was [22:13] found. [22:15] So [22:17] we can run again for the plot and you [22:19] can see that's way like a smaller [22:22] number. [22:27] And there you go. That's the second [22:29] graph with the filters applied now. [22:33] And the rate as well. [22:36] So there you go. That's the new [22:38] visualization that we're working on. Any [22:44] questions, comments? [22:48] >> No, that's great. That's really that's [22:49] really interesting. It's a it's a metric [22:52] that I've always particularly been been [22:54] interested interested in and it's uh [22:57] it's interesting to see this for um for [22:59] augur in particular. So this is this is [23:01] interesting. [23:02] >> Yeah, absolutely. [23:06] >> Yeah. And from here we'll do this will [23:08] go into 8 knot and 8 has a pretty set [23:12] visualization template as well. And so [23:14] kind of the hope is that this will be [23:16] the first one. It'll show the path. We [23:18] can get things really templated out get [23:20] the a um augur an augur instance that [23:24] people can use um that is like very bare [23:27] bones. So say that somebody wants to [23:29] make a visualization but does not have [23:31] um their own augur instance that there [23:33] will be credentials that they can [23:35] connect to that just have the very [23:37] barebone repositories in it so you have [23:40] data to be able to make the initial [23:43] visualization and to run 8 knot. Um so [23:46] yeah I'm really excited about this. Um [23:52] >> yeah I think I enjoyed watching that. So [23:55] if I get it right, I just want to [23:57] confirm I'm seeing the big um the big um [24:03] picture. I believe the big picture is to [24:06] uh put two perspective as many chaos [24:09] defined metrics into similar notebooks [24:12] like this. Is that correct? [24:14] >> Yes. Um pretty much that would be I [24:17] think that's a part like a sub portion. [24:18] So on 8 knot itself there are issues [24:21] that are opened of visualizations that [24:24] aren't under the chaos definition or a [24:27] slight iteration. Um and I would say a [24:30] lot of times from the chaos definition [24:31] there needs to be a little bit of [24:34] tinkering on the idea to work with the [24:37] data that um is available in augur. So [24:40] because a lot of times I would say the [24:42] um metrics definitions are not bounded [24:45] by any data source. It's more of like if [24:48] we had the data this is what we would [24:50] look at and sometimes you have to be [24:51] like okay now how do we look at this and [24:53] get the same um insight with what we do [24:56] have and so um some of the [24:58] visualizations are metrics models based [25:02] some of them are different ideas that [25:03] are coming from the community um I I [25:06] don't want to limit it's not just [25:07] limited to those metrics models but I do [25:09] think a lot of them do and if people [25:11] want to get started um I'm going to be [25:14] opening up a bunch of the issues for [25:15] that but it's also of if there's a [25:17] metric model that you find interesting [25:19] that is based off of um like repository [25:22] data, please open an open a notebook. Um [25:25] the good part about this is that the [25:27] person who creates the notebook, they [25:30] can do the final step of putting it into [25:33] 8, but also somebody else can take the [25:36] results of the notebook and open a PR on [25:39] 8 knot with it. And so our hope is this [25:42] that we can make it as accessible for [25:44] contributors um at any point of their [25:47] like interest skill level time to get [25:50] involved in this. [25:53] >> Yeah, thank you. I think I'm clear on [25:55] what I can do for us now. [25:58] >> Yeah, thank you. [26:01] >> All right. Uh yeah, thanks so much. This [26:04] is this is really interesting. Um a [26:06] quick update, Matt isn't here. Um but I [26:10] I met with him yesterday and we got the [26:14] initial [26:15] um commercial open source software CSV [26:18] file uh merged into the repository. So [26:22] it has um so some basic basic details [26:26] about commercial open source companies. [26:28] So these are these are companies that [26:29] are predominantly making money around [26:32] open source and there are different ways [26:34] to define it. And so we actually um [26:36] actually merged a couple of data sets to [26:38] get this, but it's got it's got the [26:40] company, the percent confidence, how [26:42] sure are they that it's an actual [26:43] commercial open source company, um a [26:45] couple of categories, the reasoning, and [26:47] the the source for the data. So, uh this [26:51] is something that I personally find find [26:54] really interesting. So, it's something [26:56] that, you know, somebody could start a [26:58] project on. We could we could do really [27:00] anything with this this data. maps [27:02] contributed it to the chaos uh project [27:05] with the idea that maybe maybe there's [27:07] something interesting that we can we can [27:08] do with this data set. So, um I know [27:11] we've got some other things on the [27:12] agenda, but uh yeah, have a think about [27:15] how how people might be interested in in [27:18] doing that. [27:21] >> I haven't looked at that PR, so I'm if [27:23] I'm tagged on it. Sorry. Um do we [27:26] >> No, I just merged it. We we were on a [27:28] call and I I just merged it. Um, is [27:30] there details of what the of where this [27:33] data comes from and like because it [27:34] sounds like there's multiple sources [27:36] being merged? Um, is there details like [27:39] because I wouldn't expect it to be in [27:41] the CSV um itself. Maybe it is. Um, but [27:45] it would be good to just know what the [27:47] like, hey, how is this gathered? If it's [27:49] a combination of the different sources, [27:51] what are those sources? Um, because [27:53] that's I think important context for [27:55] using data for analysis. [27:57] Um yeah so I would uh so there is a [28:01] source so this uh so there are companies [28:04] that gather this type of data that um [28:07] gave it to Matt for the commercial open [28:09] source software um association [28:11] initiative so um there were two sources [28:15] one was Serena and the other one was OSS [28:18] capital so that is listed here but we [28:22] don't know how they came up with with it [28:23] and we don't know what their what their [28:26] compet evidence level means. So I would [28:28] say that this is a data set that would [28:31] um before you used it for anything would [28:34] probably require a bit of additional [28:37] maybe additional cleanup or or analysis. [28:40] >> Would we be able to add I and I can open [28:42] up an issue now for this like just a [28:43] read me that has that and like just kind [28:45] of that basic information because I know [28:47] like if you scroll it's there but it [28:49] like without any context um there's no [28:52] way of really knowing that. I think it [28:54] would probably be a pretty I would only [28:56] expect it to be a couple of sentences, [28:58] but I think that's kind of helpful [28:59] context so somebody knows where to [29:00] launch from. [29:02] >> Yeah, exactly. I was I was hoping that [29:05] we would get to that and uh Matt and I [29:07] didn't. Uh he's he's really busy with [29:10] something else and then I'm getting [29:11] ready to um take some time off so I [29:14] haven't had a chance to either. But yes, [29:16] we need to because right now the readme [29:18] is um [29:21] yeah, the the data and more details are [29:23] coming soon. Uh so uh [29:24] >> is this new? Is this [29:29] >> uh Yeah. [29:30] >> Yeah, it's from this week. [29:33] >> Yeah, we just we just merged it [29:35] yesterday. [29:36] >> Should I open a issue [29:39] >> to update the readme? [29:40] >> Yeah. [29:41] >> Yes, [29:42] >> that would be great. Just so there's a [29:45] reminder. [29:46] >> Yeah. Did you have a question about it, [29:48] Karen? [29:50] >> That was Karen, right? [29:52] >> Yeah. Sorry. No, I'm just curious. I'm [29:54] I'm looking for as many lists as I can [29:57] find, but I've uh encountered a uh as I [30:02] talk about AI lots and use it, I can [30:05] also see it when I see it. And this [30:09] looks kind of AI generated. [30:12] So is that possible? [30:14] >> Uh I do not believe so. I do not believe [30:16] that this is AI generated. [30:18] >> Not with the confidence scores. [30:20] >> I don't know how they calculated the [30:21] confidence scores, but I believe that [30:23] these um [30:26] >> that's something AI does by itself a lot [30:28] and I dislike it. So I'm just curious. [30:30] That's why I saw that signature and I [30:32] was like, uh, okay. Just wanted to make [30:33] sure it wasn't AI generated. [30:35] >> I don't I don't believe so. Um you can [30:37] reach out to Matt on Slack and ask him [30:39] because he's the one that that might [30:40] know. [30:41] >> Yeah. Okay. Thank you. [30:42] >> Yeah, [30:43] >> but I mean confidence intervals are [30:45] something we've had for [30:46] >> Yeah. [30:46] >> for decades in data science. So AI does [30:50] use them, but there are loads of [30:52] different ways to collect uh confidence [30:55] levels. And Serena and OSS Capital are [30:57] both relatively reputable um [31:00] organizations that tend to have data [31:03] sets on this type of this type of thing. [31:06] >> Yeah. That's what I was about to say [31:07] that confidence scores uh like I think [31:10] they're becoming more popular because of [31:11] AI. Um but whether it is like in a [31:15] machine learning like there's just so [31:16] many ways that confidence scores have [31:18] existed in data science for 20 plus [31:21] years. So in this context it's not I [31:23] understand where where that flag is. Um [31:26] but it's not always I would say most [31:31] >> yeah it's well done and written. It's [31:33] there because it's been built in, but so [31:35] are these confidence scores. So like [31:37] nowadays I don't trust them. That's [31:39] that's like instantly I just stop [31:40] trusting anything with like confidence [31:43] score because it's just so easy to pump [31:44] out. But if I find the background I will [31:47] add this to my encyclopedia. This is [31:49] dope. [31:51] >> Awesome. Thanks. Okay, let's keep going [31:54] because we don't have much time and we [31:55] have sorry we have a couple more items [31:57] on the agenda. So [31:59] s [32:00] >> I will speak to the next two things. So [32:03] the new maintainer on boarding and the [32:05] maintainer sponsorship. I will be [32:08] working with Earnest on finalizing this [32:11] um sponsorship thing. It got a little [32:13] bit delayed because of my CubeCon. Um [32:15] but hopefully by the end of the next [32:17] week we're going to have that completely [32:19] written out, signed and added to the [32:22] repository. [32:23] I am then going to reshare it to the uh [32:28] working group to get anyone's comments [32:30] or thoughts on it. And then after that, [32:33] I'm gonna do a bit of a public campaign [32:35] around this because these are so useful [32:37] and sponsorship should exist outside of [32:39] security. Um and see if we can get some [32:42] really like interesting and positive [32:44] engagement around chaos because it so [32:45] naturally fits along with a lot of our [32:49] uh community criterion which we can [32:51] bring up in explaining it. So, there's a [32:53] nice little campaign around that which [32:55] will go very well with applying for [32:57] funding at the same time. Um, my next [33:00] note here is for CubeCon, I have been [33:04] doing what I call cuber stocking and [33:06] trying to get all of the information [33:07] that I can out of specifically the [33:09] Kubernetes repository. I used Augur for [33:12] some aspects of that and I've built out [33:14] a dashboard that provides the signals [33:17] for exactly what jurisdiction [33:20] contributors are coming from if we can [33:23] track them. Um, which is kind of [33:26] interesting. So, it was just a fun uh [33:28] sort of half-personal project, but also [33:31] comes from some ways that I use Augur uh [33:33] when engaging with like tribal [33:35] populations to communicate with them. [33:37] So, if you want to go play with that, [33:39] tell me what you think. And if there's [33:41] any aspects of that that are worth [33:42] upstreaming, [33:44] I'd be happy to, but it's uh it's [33:46] definitely a little bit off from the [33:48] typical community focus, but so much fun [33:50] to build. So uh go play with that if you [33:52] want. [33:54] >> And I think that's it for me. [33:57] >> Kelly has a question. [33:58] >> Yeah, I would be curious. It sounds like [34:00] you've gone through process of making [34:02] different dashboards using Augur data. I [34:05] would be curious to know what the gap is [34:08] of either integrating it in with 8 knot [34:10] or I don't know if this is how publicly [34:14] aware this is part of how the eight knot [34:15] is set up is for it to be incredibly [34:18] templated so that if somebody wants to [34:20] fork it to use it for a different like [34:22] kind of clear off and make it so kind of [34:24] how everything is interconnected you can [34:26] search on your repositories kind of the [34:28] general functionality is there but you [34:31] can take it and only have a certain [34:33] visualizations or do different things. [34:35] So, you're the first person I've kind of [34:37] heard in the wild to use Augur data and [34:40] making different dashboards. So, I'd be [34:42] curious to hear feedback of what that [34:44] gap would be to use um at least the [34:48] Augur or the 8 codebase as a shell for [34:52] what you're doing. [34:54] >> Yeah, I need I think it's just a next [34:56] step in my development process to be [34:58] honest. Uh right now in that development [35:00] process, I'm just having a nightmare [35:03] automatically locating sbombs as usual. [35:07] So as soon as I get through what is [35:09] everyone's nightmare in that problem in [35:11] theory, um I think in about two weeks [35:14] I'm going to like completely build this [35:15] out and then at that point I'll convert [35:18] it to like a notebook and see if there's [35:19] anything worth upstreaming because I am [35:21] having fun with it. Um but yeah [35:24] >> but yeah even if it's not something that [35:25] you see as a as a fit um the feedback of [35:28] where that gap would be of like in [35:31] saying in the next time you're using it [35:32] to create a dashboard for this purpose [35:35] our hope is that 8not would be able to [35:37] be forked and used and for in different [35:40] contexts. So that feedback would be [35:42] super helpful. [35:44] >> Sweet. Yeah. And there's a very cool [35:46] case study in starting with augur then [35:48] moving to the formalization with 8 knot. [35:50] So yeah, let's do it. [35:54] >> Cool. Thanks. Yeah, that does look [35:55] really interesting. Um, okay, we've got [35:58] about 10 more minutes. Are there any [36:00] other agenda items that we want to talk [36:02] about? Anything we want to add to the [36:05] agenda on the fly? [36:10] >> I have one thing. Um yeah, given the [36:14] recent outages, um and also the process [36:17] that I've always used in my businesses, [36:19] >> do we want to consider for chaos, um [36:23] mirroring the chaos GitHub repository on [36:26] Codeberg for greater resilience? [36:33] I've also thought about this just in [36:35] terms of like having GitHub be very slow [36:39] to respond when I'm trying to review a [36:40] PR for like the AI detection GitHub [36:43] action project. I was like, "Hey, do we [36:45] want to mirror to Codeberg?" [36:47] I feel like some of my experiences [36:48] mirroring to Codeberg, uh, I don't know. [36:50] I think I've mostly tried mirroring [36:52] codebook to GitHub, but either way, I'm [36:55] not sure if there's necessarily like [36:57] they do have a feature for that, but I [36:59] think you you might you might require [37:02] having like a GitHub like um token on [37:06] the code side so it can push and I think [37:08] those tok GitHub sort of enforces that [37:10] you set an expiry on those tokens and so [37:12] that might need to be an ongoing process [37:15] of maintaining like rotating those [37:17] tokens as they expire so that the [37:19] mirroring continues to [37:21] if if the code is sort of the primary [37:22] side of the the migration. [37:26] >> Yeah. The way that I'm getting around [37:27] that issue by being extremely lazy is [37:29] just by doing it manually. So when I do [37:32] a like big push, um I use a script [37:35] called engage which pushes out to both. [37:38] So I don't even actually mirror from [37:40] them. I just push my code local to both [37:42] separately. [37:43] >> Um [37:43] >> yeah, that's basically what I've been [37:44] doing. [37:45] >> Yeah. Um but yeah, I think it's a good [37:48] idea. Um, I think it's uh it also opens [37:51] this up to contributors who aren't [37:53] looking on GitHub if we're providing the [37:55] same information. [37:56] >> And that also means potentially um it [37:58] could be a fun test case for because I [38:00] know Augur looks at chaos repositories [38:03] by default or at least some subset of [38:04] them. So if if most of the chaos [38:06] repositories are also there, that will [38:08] probably help for [38:10] in probably six to nine months time as [38:14] I'm getting around to sort of testing [38:15] what will probably end up being 4Jo [38:17] support in Augur like being able to test [38:21] metrics on those repos would probably be [38:22] super helpful. [38:25] So what I would say is that that's not a [38:27] decision that we get to make here in the [38:28] data science working group. Um that's [38:30] something that we need to talk about in [38:32] the community meeting and in the chaos [38:35] general Slack channel. Um so decisions [38:38] like that are generally made by [38:40] community consensus. So um I think we [38:43] just need to loop the broader broader [38:44] community into this discussion and have [38:47] a discussion about the the right way um [38:50] to to do this. And I do think that Shawn [38:53] should be involved in that discussion [38:54] because he manages a lot of the the [38:56] chaos infrastructure. So, um, so yeah, [38:59] we should make sure that that that [39:01] conversation happens in the in the kind [39:04] of more public, uh, general [39:08] community. Um, and I do I do want to [39:10] make sure that Sean is involved in that [39:12] conversation. [39:15] But yeah, I think it's a really [39:16] interesting really interesting idea. [39:21] Okay. So, we have a couple of agenda [39:24] items for upcoming meetings that were [39:27] basically things that uh would be great [39:29] to talk about when we when we get some [39:32] extra time in the agenda. So, we have [39:34] less than five well about five minutes. [39:36] So, so probably not this week. Is there [39:38] anything that anyone else wants to add [39:40] to the agendas for future future [39:43] meetings? [39:50] Okay. I would say you're also welcome to [39:51] just add those anytime. So if you think [39:54] of something later, just go ahead and [39:55] add it to the most recent um notes and [39:59] and then you know we can talk about it [40:00] in the meeting. [40:02] Um I just have one reminder. All things [40:05] open. The CFP is March 31st. It's a [40:08] delightful conference in Raleigh, North [40:11] Carolina. So if you're interested in [40:13] going to that and submitting a talk, um [40:15] you have another few days. [40:21] Okay, I think we've almost reached the [40:24] end of our time. Is there anything else [40:26] anyone wants to chat about before we [40:28] wrap up the meeting? [40:31] >> I just want to say have so much fun with [40:33] taking a little bit of time and space [40:36] back and uh having some vacation time. [40:38] Good for you. [40:40] >> Yeah, thank you. So, I'm really looking [40:41] forward to it. Super excited. [40:46] All right, cool. Well, thank you so much [40:48] everybody. Um, and have a great rest of [40:52] your day. [40:54] >> Thank you everyone. Bye. [40:56] >> Yeah. Bye everyone.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Data Science WG March 24 2026.md|CHAOSS Data Science WG March 24 2026 by YouTube]] ## Highlights - I've got loads of edits from people um suggestions from people that I just need to um figure out how to how many of those I can incorporate and then get that one out the door. And then the other one that we have kind of work in progress right now is the usage adoption and popularity which I think no one has really had time to work on so much. So um so we keep tracking that one and eventually we'll set up some time in this meeting and and talk about it. Um, is that something that you would still ([View Highlight](https://read.readwise.io/read/01kpb5e7zm9dddk7zjp3srg7mx)) - Tags: 👻 ai highlighted - stuffs that you don't know how like you're like oh it's you think about it as you go but anything that you can write down means that we don't need to ask you. Yeah, for sure. Plus, it's just good to have documentation on on stuff like that. Anyways, so I will I'll think more about that and start working on something. >> Yeah, I know I keep on saying this, but I do really want to do the usage adoption and popularity and plan on doing it. I've just had to completely focus on Augur for the last month. Um ([View Highlight](https://read.readwise.io/read/01kpb5e80demgy8jpn3sgh85qf)) - Tags: 👻 ai highlighted - I'm probably would go under Augur notebooks. I think that it would make sense for to contribute that upstream. Um, and so maybe I'll make like a notebook for it. I don't know if like there's just like a place that you're kind of putting like more processy type things because I feel like this would be kind of somewhat under like pro how like to do a certain process. I don't know if it should should stay under because it's not really analysis. It's more of like chaos um process review like I don't ([View Highlight](https://read.readwise.io/read/01kpb5e80x0cbfc99k6k0cd1t6)) - Tags: 👻 ai highlighted - know it it kind of I don't know if it should fall under the same branch of like what you're talking about here of like how do we go about doing this or if it should go under more anal like augur analysis. >> Yeah, that's a good question. I was sort of thinking about putting the practitioner guide process into the part of the repo that has the practitioner guide so that everything's in >> because I don't think we have we have that but yeah so I think maybe doing that in the augur notebook would be good. It might also be good to link to have the election um officers link it ([View Highlight](https://read.readwise.io/read/01kpb5e81h59s1vsj5amtc3tzq)) - Tags: 👻 ai highlighted - from some of the they're working on some frequently asked questions and things like that. So it might be good to get it linked from that as well. Okay, >> cool. Um, okay. Anything else on the practitioner guides? Okay, project updates. Let's start with uh Ernest and S on the foundation stats. >> Yeah, thank you. So, for the past couple of weeks, we've been trying to um you ([View Highlight](https://read.readwise.io/read/01kpb5e825kpn2s4h70htm5rnj)) - Tags: 👻 ai highlighted - call for um getting started with Augur. There's also an Augur 8 knot working group channel. Um so and we're trying to work in 8 right now to make sure that all of our issues are up to date. So then somebody like you can more easily come in and start contributing. There's also kind of a good path of which we'll talk about in a second of like working on maybe like a visualization notebook and then the next step of that is putting is making that visualization in 8 knot which Kyle will ([View Highlight](https://read.readwise.io/read/01kpb5e831mpj2zjgwrjkq8nqh)) - Tags: 👻 ai highlighted - um their own augur instance that there will be credentials that they can connect to that just have the very barebone repositories in it so you have data to be able to make the initial visualization and to run 8 knot. Um so yeah I'm really excited about this. Um >> yeah I think I enjoyed watching that. So if I get it right, I just want to confirm I'm seeing the big um the big um ([View Highlight](https://read.readwise.io/read/01kpb5e85z6hhcz4ha4pd868f4)) - Tags: 👻 ai highlighted