CHAOSS Data Science WG, April 7, 2026 - CourtneyR.dev's 2nd Brain

CHAOSS Data Science WG, April 7, 2026 ![rw-book-cover](https://img.youtube.com/vi/nDnxUnY8noM/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Data Science WG, April 7, 2026](https://www.youtube.com/watch?v=nDnxUnY8noM) > [!note]+ Document Notes > tags: #chaoss #data-science #augur #8not #ecosope #open-source #metrics #visualization > author: CHAOSS Data Science Working Group > source: YouTube > reference: https://www.youtube.com/watch?v=nDnxUnY8noM > date created: 2024-12-19 14:30 > > # 🏷️ Title: CHAOSS Data Science WG, April 7, 2026 >  ## 🧰 Action Inbox - [H1] Submit PR for Augur 8not visualization issues — sovereign tech fund application requirement #career-development - [H2] Formalize ecosope project under CHAOSS repository structure — project governance #project-management - [H3] Review maintainer agreement for ecosope and broader CHAOSS adoption — governance templates #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 Working Groups](https://chaoss.community/participate/) - [8not Repository](https://github.com/chaoss/8knot) ## 📝 Summary - **What happened**: CHAOSS Data Science Working Group monthly meeting covering 8not contributions, ecosope project formalization, and maintainer agreements - **Why it matters**: Critical governance decisions for growing CHAOSS ecosystem projects and establishing maintainer responsibilities - **Key stakeholders**: Ernest (ecosope maintainer), Adrian (covering for Cali), Nest (foundational staff contributor), Cali (project lead) - **Risks and tradeoffs**: Geographic data analysis raises legal compliance concerns for trade embargo countries; download metrics remain methodologically controversial - **Bottom line takeaway**: CHAOSS is evolving from theoretical metrics to practical software ecosystem with multiple active projects requiring formal governance ## 📖 Main Content The CHAOSS Data Science Working Group is transitioning from an informal collection of metrics discussions to a structured software development ecosystem. Three main initiatives dominated this meeting: individual contributor onboarding to 8not, the formalization of ecosope as an official CHAOSS project, and the adoption of maintainer agreements across CHAOSS repositories. The 8not project, which provides visualizations for software project health metrics, is receiving increased attention as contributors seek assignment to issues for career development purposes, particularly for grant applications like the Sovereign Tech Fund. However, the project currently relies on mock databases and requires more robust testing infrastructure. Ecosope represents a significant evolution in CHAOSS methodology - instead of analyzing individual projects, it performs cross-foundation analysis of Apache Software Foundation, Eclipse Foundation, and CNCF data to understand ecosystem-level sustainability patterns. This timing is particularly relevant given upcoming European Union regulatory changes that will impact open source stewardship. The discussion revealed important ethical and legal considerations around geographic analysis of contributor data. Organizations can face legal liability if they knowingly retain contributors from trade embargo countries (Iran, China), but are not required to actively seek this information. This creates a delicate balance for data science teams working on contributor analytics. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/nDnxUnY8noM?t=0) — [H1] Meeting introductions and agenda setting - Key idea: Adrian covering for Cali, focusing on Augur 8not questions - Evidence: "I'm here mostly just covering for Cali... hoping to help answer questions about potentially Auger 8 stuff" #### ⏱️ [02:30](https://youtu.be/nDnxUnY8noM?t=150) — [H2] Ernest's Sovereign Tech Fund application requirements - Key idea: Need CHAOSS contribution for grant application, targeting 8not visualization issues - Evidence: "I submitted application for the sovereign tech by the SDA... just to meet that requirement I happen to currently contribute to chaos and open telemetry and I just used a not as the third one" #### ⏱️ [05:45](https://youtu.be/nDnxUnY8noM?t=345) — [H3] Issue assignment process for career development - Key idea: Contributors need visible issue assignments on profiles for grant reviewers - Evidence: "just assigning me to that particular issue name so that it could show on my profile" #### ⏱️ [08:20](https://youtu.be/nDnxUnY8noM?t=500) — [H2] Mock database configuration in 8not - Key idea: Environmental variables point to Docker-based mock database for development - Evidence: "there is a environmental variable that is like a sample you know for database connection to a so I noticed that is a mock database" #### ⏱️ [12:15](https://youtu.be/nDnxUnY8noM?t=735) — [H3] Docker infrastructure for testing - Key idea: Empty but schematically correct Augur database exists in Docker container for CI testing - Evidence: "I took an augur database that's basically freshly initialized. It's empty but it's schematically correct and just shipped it in a Docker container" #### ⏱️ [16:30](https://youtu.be/nDnxUnY8noM?t=990) — [H2] Visualization workflow checklist system - Key idea: Each visualization gets standardized checklist including notebook review and data science working group approval - Evidence: "for every visualization it would have this like this check mark on the eight side of each of the steps that need to be done to get a visualization merged into eight not" #### ⏱️ [20:45](https://youtu.be/nDnxUnY8noM?t=1245) — [H1] Geographic data analysis legal concerns - Key idea: Organizations face liability if they knowingly retain contributors from embargo countries - Evidence: "if you know that somebody is in China or Iran, you are liable to remove them from the community" #### ⏱️ [25:30](https://youtu.be/nDnxUnY8noM?t=1530) — [H3] Download metrics methodology controversy - Key idea: Download data widely considered unreliable due to CI/CD overcounting and VPN distortions - Evidence: "a lot of people who've done who do analysis on open source pretty much refuse to look at any download data... because of the like because there's it's a little bit different whenever the mis... very small things can like throw things out the window" #### ⏱️ [32:10](https://youtu.be/nDnxUnY8noM?t=1930) — [H2] Tribal nation use case for consumption metrics - Key idea: Government entities need public consumption tracking for compliance and representation analysis - Evidence: "tribal nation a security council... they have federal and state guidelines... if they're doing it on behalf of a government they have to do it publicly as all governments do" #### ⏱️ [38:45](https://youtu.be/nDnxUnY8noM?t=2325) — [H1] Ecosope project formalization discussion - Key idea: Cross-foundation analysis project ready for official CHAOSS repository status - Evidence: "instead of measuring individual projects... we are now interested in how does communication metrics reported across different foundations" #### ⏱️ [42:20](https://youtu.be/nDnxUnY8noM?t=2540) — [H2] Multi-foundation data integration challenges - Key idea: Apache, Eclipse, CNCF have different stewardship models and JSON schemas requiring complex integration - Evidence: "Those structures are both very different in their stewardship of open source and very different in their JSON schematics" #### ⏱️ [45:15](https://youtu.be/nDnxUnY8noM?t=2715) — [H3] Repository structure for growing CHAOSS ecosystem - Key idea: Multiple data science projects considering donation to CHAOSS, requiring organized structure - Evidence: "there's multiple projects that are like data science focused projects that are talking about donating to Chaos" #### ⏱️ [48:30](https://youtu.be/nDnxUnY8noM?t=2910) — [H2] Maintainer agreement template development - Key idea: Formal maintainer agreements drafted and ready for implementation across CHAOSS projects - Evidence: "we've drafted a version of this... I've had a couple of just like nice comments from community members on it" ## 📚 References - [CHAOSS Metrics](https://chaoss.community/metrics/) - [8not Project Repository](https://github.com/chaoss/8knot) - [Augur Documentation](https://oss-augur.readthedocs.io/) - [Sovereign Tech Fund](https://www.sovereigntechfund.de/) ## 🗣️ Paraphrase - CHAOSS is evolving from an academic metrics discussion group into a practical software ecosystem requiring formal project governance structures and maintainer agreements - Geographic analysis of open source contributors creates legal compliance challenges due to trade embargo restrictions, requiring careful data handling protocols - The ecosope project represents a methodological advancement from single-project analysis to cross-foundation ecosystem health measurement, particularly relevant for EU regulatory compliance ## 📰 Newsletter The CHAOSS Data Science Working Group is scaling rapidly with multiple projects transitioning from research to production software. The ecosope project offers groundbreaking cross-foundation analysis across Apache, Eclipse, and CNCF ecosystems - perfect timing as European Union regulations reshape open source stewardship requirements. Key developments include formalized maintainer agreements, improved Docker infrastructure for 8not development, and careful protocols for geographic data analysis that respect trade embargo compliance. Contributors can now access standardized checklists for visualization development and clearer pathways for career development through visible project contributions. For those interested in ecosystem-level metrics and sustainable open source communities, these tools provide unprecedented insight into multi-foundation health patterns. Resources: [CHAOSS Community](https://chaoss.community/), [8not Repository](https://github.com/chaoss/8knot), [Augur Platform](https://oss-augur.readthedocs.io/) ## ✅ Action Items #### DevRel - Developer experience: Improve 8not Docker setup documentation and mock database workflows - Community management: Establish clear contributor onboarding paths for grant applications and career development #### OSPO - License Compliance: Document geographic data handling protocols for trade embargo compliance - Community Engagement: Support Sovereign Tech Fund applications through visible contribution tracking #### Community - Contributors: Implement standardized visualization checklists for 8not submissions - Maintainers: Deploy formal maintainer agreements across CHAOSS projects #### WordPress - Documentation: Apply CHAOSS visualization workflows to WordPress contributor analytics #### The WPCC - Programs: Consider CHAOSS methodology for cross-project health measurement ## 🧪 Hypotheses - Formalized maintainer agreements will increase contributor retention and project sustainability across CHAOSS ecosystem - Cross-foundation analysis through ecosope will reveal common patterns in healthy open source communities ahead of EU regulatory implementation - Standardized visualization checklists will improve quality and consistency of 8not dashboard contributions - Docker-based mock databases will reduce contributor onboarding friction for data science projects ### 📊 Methodology - Survey ecosope data across Apache Software Foundation, Eclipse Foundation, and CNCF for contributor activity patterns pre-CRA implementation - A/B test visualization submission process with and without standardized checklists - Track contributor onboarding success rates before and after improved Docker documentation ### ❓ Questions - How can CHAOSS balance geographic analytics utility with trade embargo compliance requirements? - What governance structures best support rapid scaling from research projects to production software? - Which cross-foundation metrics most accurately predict community sustainability under regulatory pressure? ### 🔮 Future Research - Development of automated compliance checking for geographic contributor data - Integration of European Union CRA requirements into open source health metrics - Expansion of ecosope methodology to additional foundation ecosystems ### 💡 Implications - Practice: Data science teams need explicit protocols for handling contributor geographic information to avoid legal liability - Policy: Open source foundations must prepare governance structures for EU regulatory compliance starting 2026 - Security: Mock database infrastructure requires security review before production deployment - Education: Contributors need clear documentation on Docker setup and testing procedures - Funding: Grant applications increasingly require visible open source contribution history ### 🧠 Learning Styles Assessment Reading level estimate: 14.2 (Graduate level) #### 👀 Visual learners - Present: 8not dashboards, ecosope cross-foundation visualizations - Improve: Docker architecture diagrams, governance workflow charts #### 🔊 Aural learners - Present: Working group meeting recordings, verbal policy discussions - Improve: Podcast format for governance decisions, narrated setup guides #### 🗣️ Verbal learners - Present: Technical definitions, compliance terminology, project analogies - Improve: Glossary of CHAOSS/governance terms, regulatory explanation guides #### 🧩 Kinesthetic learners - Present: Docker container setup, GitHub issue assignment workflows - Improve: Interactive tutorials for 8not development, hands-on compliance training #### 🧠 Logical learners - Present: Maintainer agreement templates, visualization checklists - Improve: Decision trees for geographic data handling, compliance flowcharts #### 🧑‍🤝‍🧑 Social learners - Present: Working group discussions, collaborative project development - Improve: Mentorship programs for new maintainers, peer review processes #### 🧘‍♀️ Solitary learners - Present: Individual contribution tracking, self-paced project setup - Improve: Self-assessment rubrics for maintainer readiness, solo learning paths #### 🌿 Naturalistic learners - Present: Ecosystem-level thinking, cross-foundation health patterns - Improve: Sustainability metrics, community lifecycle analogies ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Structured meeting notes, clear heading hierarchy - Improve: Alt text for 8not visualizations, ARIA labels for dashboard elements #### Keyboard navigation - Present: Standard GitHub navigation, text-based issue tracking - Improve: Keyboard shortcuts for dashboard filtering, skip links #### Contrast and readability - Present: Standard text formats in documentation - Improve: High contrast modes for data visualizations, font size options #### Text resizing and reflow - Present: Responsive documentation layouts - Improve: Scalable dashboard components, mobile-friendly visualization views #### Media and captions - Present: Meeting recordings available - Improve: Auto-generated captions, downloadable transcripts #### Forms and interactions - Present: Standard GitHub forms for issues and PRs - Improve: Error handling for Docker setup, accessible form validation #### Standards reference - Map dashboard interface to WCAG 2.2 AA guidelines for data visualization accessibility ### 🌍 DEIB Assessment #### Cultural breadth - Present: International contributor base across multiple foundations - Improve: Documentation in multiple languages, timezone-inclusive meeting scheduling #### Inclusive language - Present: Technical terminology clearly defined - Improve: Plain language summaries, avoiding geographic bias in examples #### Neurodiversity support - Present: Structured meeting agendas, clear action items - Improve: Multiple information formats, processing time considerations #### Representation - Present: Diverse foundation representation in ecosope analysis - Improve: Balanced case studies, inclusive contributor examples #### Psychological safety - Present: Respectful technical discussions - Improve: Code of conduct enforcement, newcomer support systems ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Geographic compliance requirements follow logically from trade embargo law - Inductive strength: Cross-foundation patterns suggest broader ecosystem health indicators - Causal reasoning: Formal governance structures support sustainable project growth - Analogical strength: Cybersecurity maintainer models apply well to open source governance #### Fallacies - Appeal to tradition: "Download metrics are controversial" doesn't invalidate new use cases - addressed through specific tribal nation context - False dichotomy: Presenting download metrics as entirely useful or useless - resolved through use-case specific evaluation #### Tone of voice - Overall tone: Collaborative and technically focused, with appropriate caution around compliance issues ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - Attack: No attacking behavior noted - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Professional technical discussion with appropriate concern for legal compliance ## 🎯 Conclusion CHAOSS is successfully transitioning from academic metrics research to production software ecosystem governance. The formalization of ecosope, implementation of maintainer agreements, and careful handling of geographic compliance --- ## Full Transcript [00:03] Okay, excellent. Well, we're gonna get [00:07] the data science meeting started. Um, [00:10] before we do, everyone just give some [00:13] quick introductions and what you're [00:15] hoping to cover today. And if people [00:16] continue joining in today, we'll uh stop [00:19] and see what they want to cover. [00:25] >> I can start real quick. I'm I'm Adrian. [00:27] I'm here mostly just covering for Cali. [00:30] I guess I work very closely with her. [00:31] So, I'm just kind of covering and um [00:33] hoping to help answer questions about [00:34] potentially Auger 8 stuff if if those [00:37] come up, but I don't really have any [00:38] specific agenda items really. So, [00:44] >> yeah. Um [00:46] introduction, right? So, I'm Nest. I [00:49] have been active in the working group [00:51] for a while and uh I happen to have made [00:53] a bit dinner recently and uh most of my [00:56] work has been on the foundational staff [00:58] we which we're now trying to build up to [01:01] become an important project that we call [01:03] scope. So um that's pretty much about [01:07] me. I do have a few questions about it [01:11] not so maybe because of the meeting [01:25] Sorry, I was saying I think we can [01:28] probably just dive in. I'm going to set [01:29] up a little bit around the agenda which [01:32] is magically happening. I love open [01:34] source. Um and uh yeah, I think we can [01:39] have a discussion around augur and 8not [01:41] and um yeah, I will just take excellent [01:44] notes. Um, I have a few questions [01:47] myself. I've been using Augur [01:50] particularly. [01:51] Uh, and uh, welcome in. We're just at [01:55] introductions. So, uh, say hello if you, [01:58] uh, just come in. [02:09] >> I think you wanted to, right? [02:13] >> Yeah. But it's all right if they can't [02:15] join in at this moment. Um [02:19] we can just jump in on the augur 8 not [02:22] discussion. [02:24] >> Okay. Yeah. Um so um yesterday I I think [02:29] Sally is aware that I submitted [02:31] application for the sovereign tech by [02:35] the SDA and uh you know one of the [02:38] requirements was to contribute to which [02:42] I don't think is straight but you know [02:43] just to meet that requirement I happen [02:47] to currently contribute to chaos and [02:49] open telemetry [02:52] and I just used a not as the third one [02:56] which my contribution is still at the [02:58] very early stage. I'm still yet to send [02:59] the PR but I have like two issues that I [03:02] think I could you know work on which is [03:05] um both of them were opened by Khali but [03:08] unfortunately she's not here. So I [03:10] responded I think earlier today that if [03:13] I could get assigned to the issue just [03:15] for it to be on my profile in case the [03:18] SDF reviewers are doing that before I [03:21] sign the PR. But um I think with the [03:25] current plan that I have that I made in [03:27] the early hours of today I should if [03:30] there are no setting up issues you know [03:33] for contingencies I should be sending a [03:35] view out in a few days. [03:37] So the the issues that I want to work on [03:40] is the visualization that for both [03:43] activity which Ki raised. I think I can [03:46] quickly find that [03:50] and share with you. The point is not [03:52] necessarily the EU but just assigning me [03:55] to that particular um [03:59] um issue name so that it could show on [04:01] my profile. [04:03] >> You have the links to these issues. Um [04:05] >> yeah, bring in the issue numbers and [04:10] >> um since I'm I'm very I [04:13] with some of the complications happening [04:14] in the augur community right now. If you [04:16] if you're looking specifically to be [04:17] assigned to issues that are in the chaos [04:20] or um I have the ability to do that on [04:23] basically any chaos repo. Um Augur [04:26] specifically is not currently in the [04:29] chaos or for reasons I will not get into [04:32] here. [04:34] I actually meant eight not the one on [04:37] red hearts. [04:38] >> Okay. So 8 8 not technically is not in [04:41] the chaos or yet either but um I can I [04:45] do have access to that too if you if if [04:47] that would help you. I'm not sure how [04:48] strict the application is on wanting [04:51] specifically chaos if that's what you're [04:52] applying for but I I can I can do that [04:54] if you send me the issues. [04:56] >> That's no problem. It works really well [04:58] with our plan and it's just open source [05:00] contributions. Oh [05:01] >> okay. Oh it's very broad. Okay. Perfect. [05:04] >> Yeah, this and uh the second one I will [05:09] send I will send the second one but this [05:10] is the one I'm currently focusing on but [05:13] just for reviewer sake to meet the [05:17] reviewer too. [05:19] >> Is that your username? [05:22] >> Yes. Yes. [05:26] >> Or did I send [05:39] Then um [05:42] today a follow-up question to that is [05:45] today I noticed that you know the sample [05:48] environment variable and that has like a [05:52] mock DB of A. So I was going to ask is [05:54] that sufficient for me to do whatever I [05:56] want to do. which rep that was in [06:01] >> you know the current structure on the [06:04] um it's not repo there is a [06:07] environmental variable that is like a [06:09] sample you know for database connection [06:12] to a so I noticed that is a mock [06:15] database and I wanted to confirm I think [06:17] you should be able to answer that [06:18] whether is sufficient for me to do all [06:21] my connections along the way so you know [06:25] I'm just anticipating problems Right. [06:27] >> Can you be a little more specific on [06:29] where you're see is that um in the is [06:32] that like the sample environment [06:34] variables like where where are you [06:36] seeing that in the repository? [06:38] >> Yeah, I I will send that as well. It is [06:41] on the root repo for the one I just sent [06:44] to you now. [06:45] >> I will send that as well. This is the [06:47] second issue. Oh, Khali is here. Wow. So [06:51] >> 8 right now had So [06:54] we have a I think there's a Docker image [06:57] somewhere. I need to go dig through the [06:59] CI config to to grab the exact name. But [07:02] we basically uh in order to have some [07:04] sort of vague unit tests uh just to make [07:06] sure that pull requests don't break. [07:09] Um, we do I think we have there's a [07:12] Docker image I built quite a while ago [07:14] now that basically is just uh it it's [07:19] basically I took an augur database [07:21] that's basically freshly initialized. [07:23] It's empty but it's schematically [07:25] correct and just shipped it in a Docker [07:28] container. So it's not really best [07:29] practice but at least it's enough to [07:31] have a database to connect to so that 8 [07:34] will at least start up. Um, [07:37] so that's what that probably is. Um, I [07:41] am planning to kind of extend that with [07:44] uh some more like to actually have sort [07:47] of a an image that actually has a more [07:50] current database and or actually has a [07:53] couple of small repositories in it. Um, [07:57] so I not 100% sure when I can get to [08:00] that, but that's that's one of the [08:01] things I'm trying to work on it. um work [08:06] on doing soon. Um [08:08] >> so I think if you if you wanted to try [08:10] pulling that image and and using that [08:13] locally that should work and the [08:15] credentials in that sample should be [08:18] valid for that. But that's a that's like [08:20] a basically an empty database. So the [08:23] the credentials don't get you very much. [08:27] Oh, are those credentials real or I mean [08:29] to my knowledge those were just [08:30] placeholders for people to know the [08:33] format for the credentials? [08:36] >> I think they are real. It's just for [08:38] that um I need to double check, but I I [08:42] think they there was a purpose for [08:43] having real credentials in there. [08:45] Otherwise, it would have just put your [08:46] password here. [08:48] >> Um [08:49] >> yeah, but it's also just like a Docker [08:51] image that happened at one moment in [08:53] time. [08:55] Um, [08:55] >> yeah, pretty much. I I've been trying to [08:57] kind of systematic like get that more [09:00] >> Yeah. [09:00] >> like I'd like to have um one of my one [09:02] of my goals for [09:05] um the the more the more augur side of [09:07] this is I want to we already have some [09:10] testing in place that basically will run [09:13] the Docker container for augur and and [09:15] for like three minutes or something in [09:17] CI and look for specific log lines to [09:19] make sure it started up. I'd like to [09:21] build on that and see, okay, can we can [09:23] we also run Augur on a couple of tiny [09:27] repos that only take a few minutes to [09:28] collect and then we can actually make [09:30] some assertions about, okay, this tiny [09:32] archived repo is fully collected in CI [09:36] and we can check the database to make [09:38] sure the data is as we expect. I think [09:40] that's a natural place to like okay at [09:42] the end of that build that Docker job [09:45] build an image and push it somewhere so [09:47] that somebody can just pull down an [09:48] image with like if all you need is a [09:51] good enough augur database with data to [09:53] connect something else to like that that [09:56] I think would be a good purpose of that. [09:58] >> Yes. [10:00] >> But that's more that's I haven't gotten [10:02] to that yet. [10:06] >> Sorry. Is it possible for you to point [10:08] me to that Docker email that you [10:10] mentioned earlier that you said you [10:12] >> working on finding Matt? I think. [10:16] >> Excellent. Because I think that gives us [10:17] an opportunity. We can follow up on this [10:20] like in writing and in the following [10:22] weeks. But like really getting a chance [10:25] to build hygienically from that Docker [10:27] image is a cool opportunity and we can [10:29] think about it a little bit which is [10:31] nice. Um, and then [10:37] from there [10:40] right now, Ernest, do you think you got [10:42] any questions on bringing in the [10:45] foundation stat stuff or do you want to [10:48] give it a pass through? [10:51] Sorry, I didn't get that answer. [10:54] >> So, [10:56] I'm interested in building out with the [11:01] Docker image, but I'm also curious about [11:03] like right now fundamentally for any of [11:05] your pipelines. Are you blocked? [11:08] >> Oh, I don't think we should worry about [11:10] that yet for what we currently have. [11:14] But, you know, when we want to connect [11:16] to instances, yeah, that should [11:18] definitely be the approach. [11:20] Yeah. Cool. [11:25] >> So, I'm I'm noticing I found the um [11:28] Docker link, the Docker image to that [11:31] empty database. Um and RCI is basically [11:35] just adding that as a service to the [11:37] YAML file to the Docker compose. Like I [11:39] think the service name is mock DB and [11:42] and then that's the the image. I'm [11:45] noticing that that's I don't know. I [11:49] don't think that Docker image like that [11:50] Docker image should still be around. It [11:52] looks like it's based in the Chaos or [11:55] so. So, I don't think that would be [11:56] affected by any of the the repository [11:59] things going on in Augur. Um, so that I [12:02] I would say give that a try first and [12:03] let me know, ping me on Slack if you [12:05] have issues uh pulling that or getting [12:07] that to work. Worst case, I can just run [12:09] a a local Docker local augur install on [12:13] my machine on a couple of small repos, [12:15] wait for it to get fully collected, and [12:17] then just push a push an image somewhere [12:20] um with that database if if that would [12:22] help you. Um like I can always kind of [12:24] manually redo this until I have the time [12:28] to actually go and make it an automatic [12:30] process. [12:32] >> Yeah, that makes sense. Thank you. [12:37] Yeah, I just linked in chat what we did [12:40] for the selfmerge like um visualization. [12:43] And so the idea would be that for every [12:46] visualization it would have this like [12:48] this check mark on the eight side of [12:50] each of the steps that need to be done [12:52] to get a visualization [12:55] um merged into eight not and one of [12:58] those steps is the notebook and the data [13:02] science working group. So, it's like a [13:04] subportion of the overall. And so, I was [13:06] I'm going to be creating the issues and [13:09] populating all of them with these check [13:10] with like the to-do list and opening it [13:13] on the 8 site. So, any feedback on stuff [13:15] that I should include or ways to improve [13:18] that process, let me know because this [13:20] would be a good time before I go and do [13:22] a whole bunch of them and then have to [13:23] update later. [13:27] >> Cool. I had a lot of fun building out. [13:30] I'll bring a link for this one sec. [13:35] But building out this clue line [13:37] visualization, it might not be the most [13:39] expected visualization for it, but I [13:41] went and I just like scanned Kubernetes. [13:45] Um, I'll bring up a link to it and I'll [13:48] just uh have it as a reference. But I'd [13:50] love to see more. Like what I enjoyed [13:52] about this was trying to get like a [13:54] minimal visualization of like what [13:58] countries, what jurisdictions are [14:00] consuming and producing. [14:03] Um, so I'll bring that up in uh in just [14:07] a second, but for now, [14:08] >> are you familiar with the country like [14:10] the things that you should be aware of [14:12] when it comes to looking at country data [14:14] just as a [14:17] >> Yes. Yeah. But this is just looking at [14:19] like jurisdiction. [14:21] >> Okay. Um yeah, because we pretty much [14:23] avoid any country analysis like the [14:26] plague so that we don't have to remove [14:28] contributors from specific countries. [14:30] But if you're like analyzing a community [14:31] that you're not pretty much you're as a [14:33] community, you are not responsible to [14:34] know where everybody is at. But if you [14:37] know that somebody is in China or Iran, [14:40] um you are liable to remove them from [14:43] the community. So it is something to [14:45] kind of be aware of when it comes to [14:47] doing analysis on location. [14:49] >> Yeah. Yeah. [14:52] But the visualizations are really nice. [14:54] Does it matter? So what about the [14:56] consuming? So what I'm only able to cons [14:59] look at are like consumption of [15:03] open source like I'm looking at who's [15:05] consuming it. [15:06] >> How are you what are you counting as com [15:09] of consume like a download? [15:11] >> Yeah. [15:13] controversial. [15:14] Um, oh no, I don't mean that in a I got [15:17] that I didn't mean that in a mad way. I [15:19] mean that in like a very literal um [15:21] downloads are very controversial and [15:23] like I like in the overall measurement [15:26] um community whenever it comes to [15:28] because of how much it miscounts like [15:30] that it is a very it could be a a [15:34] misleading metric. [15:36] >> Yeah. Um because it can count like I [15:38] guess but I guess you're looking at [15:39] purely from like a I just want to see if [15:41] a location is is represented rather than [15:43] the scale. Is that what you're going [15:45] for? [15:46] >> Yeah. So like in my consumer class I get [15:49] a lot of questions like okay so is the [15:51] European Union like actively [15:53] contributing to the space or not? So I [15:55] have a line that just shows across all [15:57] the EU known active like consumption and [16:01] that works really well and it's a it's a [16:04] very anonymous aggregate but it did use [16:07] this baseline to get it [16:09] >> interesting. Um, yeah, I'd be curious if [16:13] Don comes back around at certain points [16:16] or talking to Greg because I would say [16:18] um a lot of people who've done who do [16:21] analysis on open source pretty much [16:23] refuse to look at any download data [16:26] including myself um because of the like [16:29] because there's it's a little bit [16:31] different whenever the mis or not even [16:34] the miscounts but if the stuff is at [16:36] scale so it's like oh if in this way [16:37] this could underount in this way and it [16:39] could overount in another way. If [16:41] they're scale-wise similar, then you're [16:43] like kind of like, okay, that's a bit of [16:45] a wash. But the ways in which the [16:47] counting can be done of man, if somebody [16:50] just like sets up a certain way of [16:51] downloading a server in a certain way or [16:54] using a VPN, it just completely ruin [16:56] like messes with the entire like [16:59] analysis. Like very small things can [17:01] like throw things out the window. [17:05] >> Yeah. Yeah, for sure. Yeah. But I think [17:09] uh yeah, I think what I'm looking at is [17:11] like I'm I'm looking for really the [17:14] proof that some like small areas are [17:17] consuming like tribal nations or PBLO [17:19] nations or like [17:20] >> Yeah. You know, [17:21] >> if the answer is like consu consumption [17:23] as a check mark rather than a scale, [17:26] completely agree. [17:28] >> Does that does that make sense? Or [17:29] you're just like saying like this exists [17:31] here rather than like oh because if [17:33] you're trying to compare scale that can [17:35] be a problem. [17:38] No, I don't think so. Yeah, it's a it's [17:40] really not something that would go into [17:42] like a consumer report, but like a [17:44] government is going to be interested in [17:46] understanding how much from their [17:47] citizenship is publicly consuming [17:49] intentionally because it's a government [17:51] platform, right? So, [17:54] >> yeah, [17:56] but yeah, maybe a discussion that we [17:58] should probably have and loop in on. [18:01] >> Yes, I do. I this is a good I'm glad [18:05] like I think that it's good to bring in [18:07] a different perspective of this cuz I [18:08] think that the conversation has just [18:10] been stopped at no we should not do this [18:12] for a while and that might not be the [18:14] correct like I'm I would be very curious [18:17] for you to bring up like kind of like [18:18] show what you're doing analysis wise why [18:21] like you're like kind of backing behind [18:23] of like why this isn't uh like [18:26] misrepresentation of counts as like a [18:29] double negative or like showing why it [18:31] is like valid for this like thing and [18:33] having an open discussion around it [18:34] because this probably was a bit before [18:37] you were involved, but this was like [18:38] this used to be like the topic that [18:41] everyone was talking about all the time. [18:43] Counting like counting download metrics, [18:45] why we shouldn't like to the point of [18:47] like doing a joint um blog post of [18:49] saying we refuse to count as like um um [18:54] researchers in this space, please stop [18:56] asking us to count downloads. Um but I [18:59] like that you have a different idea on [19:01] it. I think it's worth discussing again [19:03] because just because we have been saying [19:05] it doesn't mean that we should. [19:07] >> Well, okay. So, I think I think it [19:09] probably came from a very different [19:10] space and energy and like very much I [19:12] come from this I like I have a [19:14] consultancy with people that never come [19:16] to this room because I'm just in it [19:17] building the things with and for them. [19:19] Right. [19:20] >> Yeah. [19:20] >> And here's what it looks like when [19:23] someone receives [19:24] the little like cog in the wheel of my [19:27] system that is augur. So we'll go [19:30] through first and it'll be like a tribal [19:32] nation a security council and we'll go [19:35] through eight metrics but we'll go [19:36] through everything from hardware to [19:37] software like what do you have [19:40] what do you know you have what do you [19:41] have attestation for like because they [19:43] have federal and state guidelines right [19:45] so we go through all the open standards [19:46] and regulation [19:49] and then if we want to see how like and [19:53] specifically like for a like tribal [19:56] nation very easy to get that if they're [19:58] doing it on behalf of a government they [20:00] have to do it publicly as all [20:01] governments do. So then we can go and [20:04] track that so that we can show what [20:06] percentage of contribution they have [20:08] which is something that they're all very [20:09] interested in. But if that I would be [20:12] interested if like from that frame and [20:14] from that understanding is that [20:15] unethical that is a question that we [20:18] should probably have on another call. [20:21] I wouldn't say the ethics is it usually [20:23] the conversation but it's more of is [20:25] this [20:27] >> do these counts actually give us [20:29] something useful [20:31] because but if you're very you know a [20:34] lot about what are the systems that are [20:36] downloading these files and is it going [20:38] to is a CI/CD system that's calling it a [20:41] bunch of different times or if you're [20:43] familiar with how this data is being [20:44] downloaded or not data but the project [20:46] is being downloaded and the things that [20:48] go into the account that is different [20:50] scope which I think is an [20:53] a better conversation of when is [20:56] download data useful if instead of where [21:00] I think a lot of places right now and [21:02] like the open source analysis space is [21:04] that download data is never useful and [21:07] that might not be the right way of [21:09] thinking about it. Um, and so that's [21:12] that's more of where I'll be really [21:14] curious to see the use ca use case and [21:16] the count and all this different stuff [21:17] because it's just a diff like it [21:19] challenges what has been assumed in this [21:22] space which makes it very interesting. [21:25] >> Yeah. Yeah. Well, what I mean it might [21:27] be an outlier case but I think this is [21:29] an interesting situation of like within [21:31] the Linux Foundation like [21:33] >> yeah that's definitely like [21:36] >> a pipeline that I've built because it's [21:37] been requested. [21:39] >> Yeah. Um, and [21:43] yeah, it wouldn't go into a Linux [21:45] Foundation report. I understand that. [21:47] But if it's an issue to do that under [21:50] this like license and work, [21:53] we should talk about that cuz I'm I'm [21:55] curious. I'm I'm super [21:56] >> there's no license issue. It's more of [21:59] just like from a method like as a like [22:01] from the perception of research like [22:03] myself as a researcher or and I'm only [22:06] speaking for Dawn and um Greg Suckliffe [22:08] because they've spoken like very [22:09] definitively and publicly about it. It's [22:11] not like an ethics thing, but a um issue [22:15] with how like the value of like if [22:18] you're comparing the idea that you're [22:20] comparing apples to oranges and saying, [22:21] "Oh, this this one project or in this [22:23] one place there's a thousand downloads [22:24] in this one one place there's 5,000 [22:26] downloads because of the different ways [22:28] that the like their like counts of [22:30] downloads can occur. that the scale can [22:33] be like that doesn't mean like that it [22:35] does not mean anything and the scope of [22:37] it because you think about like the [22:39] different ways that things can be [22:40] overcounted and underounted and the fact [22:43] that those things are not at scale to [22:45] one another. I think I think it's [22:47] probably not too big of a problem [22:49] because this sounds like this was [22:50] probably like a center of report or like [22:52] something that was going considered, you [22:55] know, like a research report or white [22:57] paper. That is a single metric out of [23:00] quite literally over 100 that I look at. [23:04] It's not something that we decisions by. [23:08] Um, yeah. So, I don't think [23:12] I think it's okay. [23:13] >> Yeah. In case you're curious, this there [23:16] is some I I don't think I don't know if [23:18] Don's put out anything, but this is a [23:20] blog post from Oh, wow. That is not link [23:24] not working anymore. Lovely. I'll try to [23:27] find that. [24:09] I think Ki is trying to find the [24:12] >> a link to it. Do we want to I mean in [24:14] the meantime, this is this is definitely [24:16] like a topic that we [24:18] can come back to, but I really think for [24:21] like my use case, it's just like it's a [24:24] use that I've had for Aubra. I've used [24:26] it for other things as well, but um I [24:28] just liked my visualization for it. [24:30] That's all. [24:32] >> Yeah, I would be curious and like I [24:33] guess where does the down are I didn't [24:36] even know that auger got download data. [24:39] >> No, so what I've been No, so what I've [24:41] been doing is I I created a system which [24:43] just says okay for what you already have [24:46] as a security posture, what do you do? [24:48] And then I compare that to what like [24:51] OpenSSF has available for example like [24:53] what are the free and open tools or the [24:55] hardware that you would want to use and [24:57] then giving them the option of like do [24:59] you want to look at the contributor for [25:01] that if you've been contributing because [25:03] these are like groups that have [25:06] identifiable [25:08] names and they're trying to find [25:09] themselves. The needle in the haystack [25:11] is them. So is that a problem? Because [25:14] that's not for a broad audience. That's [25:16] not making a big argument. [25:20] >> Yeah, I guess [25:21] >> I'm not even because if you're using [25:22] auger, I guess can you repeat the end [25:25] like where slash when are you getting [25:27] download data in this because I'm still [25:28] not I don't I think I'm that's what I'm [25:30] >> so on my side here what I what I had the [25:34] only thing that I so that was that was [25:36] the thing where we got off on to [25:37] downloads because I was I was looking at [25:39] that as well. What I have in here is [25:41] just a ring that shows like where the [25:44] like relative geography is for the [25:49] contributors to Kubernetes. [25:51] >> Oh, nice. Yeah. [25:52] >> Is that a problem? [25:54] >> Um yes. um if you're get if you're [25:56] providing that. Okay, now I get um so [25:59] the location data um if that is [26:01] something that you're providing to the [26:03] CNCF um I would recommend blacking out [26:06] any um country that has any type of [26:09] trade embargo with um the US. Um so [26:14] usually that they the two big concerns [26:16] are Iran and um China and so like if the [26:20] CNCF like Kub if Kubernetes knows that [26:24] they have contributors that are [26:26] contributing from China or Iran they are [26:29] liable to remove them but they are not [26:32] required [26:33] to know. So if you do not seek out said [26:38] information, you are not responsible. [26:40] But if you do know that, it is a legal [26:43] liability that you have to remove them [26:45] from the community. So that's everyone [26:48] has gone about doing that. So this is [26:50] like outside of download data, but from [26:52] the contributor data um of how you go [26:55] about making sure that that is not a [26:58] piece of information that the community [27:00] has provided. [27:02] >> Yeah. [27:04] Yeah. Well, I think that's fine. Yeah. [27:07] >> I'm not like bouncing it back to the [27:09] community. I do it in printed reports. [27:13] >> Yeah. Because as long as you're doing [27:14] consumer reports, then it's like Yeah. [27:16] Then you're you're fine. It's just [27:17] something that's like, oh, if you're [27:18] working with like with the Linux [27:20] Foundation, if the Linux found if you're [27:22] working with the Linux Foundation, [27:24] analyzing a Linux Foundation's projects, [27:26] and then that report has [27:28] >> Yeah. Well, it's interesting because I [27:30] thought like Kubernetes would be super [27:31] safe because I thought it would be like [27:33] they've limited their liability and [27:35] really making sure they know who's [27:36] contributing. Um, but yeah, it's it's [27:40] good to just make sure if it's going to [27:41] be in any way public, which is open [27:43] source. So, [27:44] >> yes, [27:45] >> I'm glad we had this discussion because [27:47] that's an angle I did not know. [27:52] Yes, it is a kind of a weird there's so [27:55] many weird corner cases when it comes to [27:57] like data and analysis which is the [27:59] interesting sides of it. [28:01] >> Yeah. And the antitrust but good good to [28:04] know. Um okay, [28:07] I [28:09] want us to move on. We've got about 20 [28:12] more minutes. Let's talk a little bit [28:15] about the like next steps of formalizing [28:19] our latest like project repository [28:23] okioscope. [28:24] I think I'm saying that right. Um but [28:28] Ernest you've given a description of [28:30] this before but just give another quick [28:32] pitch and then we are going to talk a [28:35] little bit about like where does it fit [28:37] inside the chaos repository and then [28:39] within that we are going to put in a [28:43] like formal maintainer agreement [28:46] and once we put that in place we should [28:48] come up with a like good way to make [28:51] sure that that is like solid and [28:53] communicated but using that as a little [28:56] bit of like marketing campaign for the [28:58] project to get more contributors as [29:00] well. Um [29:03] so yeah, I'd love thoughts on that but [29:04] Ernest take it away. Yeah. So um we got [29:09] uh the name inspiration from a and he [29:13] says that because foundational staff [29:16] project that we started working on the [29:18] unique value that is adding is that [29:21] instead of measuring individual projects [29:24] that does you know we are now interested [29:27] in how does communication metrics [29:29] reported across different foundations. [29:32] How does it help us to answer [29:33] sustainability questions on a cross [29:36] variational level? So because that's an [29:39] ecosystem level measurement. So we now [29:41] said let us measure ecosystem which is [29:44] what we now call ecosope. [29:46] Yeah, that's pretty much about the Navy [29:49] and um I think that should [29:56] >> Yeah, what makes this interesting for me [29:59] is like we've gotten multi-year data [30:01] from Apache Software Foundation, Eclipse [30:04] Foundation, CNCF, [30:06] and we're at a really interesting moment [30:09] in time with the CRA. We're looking at [30:11] some of their patterns of contributor [30:13] activity. [30:14] um that's going to change because of [30:18] strong regulation from the European [30:20] Union right now on stewards of open [30:23] source. So we're doing this like moment [30:27] like up to this moment in time analysis [30:29] and looking for the signals that showed [30:31] like really positive and robust [30:32] communities which is very cool. Those [30:35] structures are both very different in [30:38] their stewardship of open source and [30:40] very different in their JSON schematics. [30:43] So it's not the easiest but we are uh [30:48] continuing to put those together. So [30:51] with that it's an interesting like it is [30:53] a data science project and turning into [30:55] a dashboard for ongoing uh like [30:59] analytics. [31:02] Are we ready to put that at the like [31:04] project level of the chaos um repository [31:09] generally? And if so, I'm sure there's a [31:11] few lines that we'll have to go to to uh [31:14] ensure that's solid. [31:17] Any advice? [31:22] >> So, is the ask [31:25] the dashboards ready to put it into the [31:27] working group repository under its own [31:29] like top level directory? Is that kind [31:31] of [31:32] >> Yeah, because it's been sitting inside [31:34] of the like the like data repository [31:39] because it started as a data project, [31:41] but now it is a formal project like Don [31:44] is happy to have as a project and [31:45] Earnest is the maintainer. So, we've got [31:48] everything we solidly need to have it be [31:51] active at that level. [31:54] >> Yeah. um putting it in under it's kind [31:57] of similar which we're going to have to [31:58] rename but like similar to how we did [32:00] like the augur notebooks. It seems like [32:02] it would make sense to have like a top [32:04] level directory specifically for this. [32:06] >> Yes. Yeah. [32:14] >> And it has a good name and I tried to [32:16] give it a silly little logo that looks a [32:17] little bit like the chaos logo. [32:27] Yeah. So [32:30] that's the Yeah, that's the ask there. I [32:32] think probably I mean we formalized it [32:35] as an issue for now, but that was very [32:38] much just a draft of like here's the [32:39] template for it. Um [32:44] yeah. So is there anything that we I [32:47] mean I'm thinking of this at the level [32:48] of if there's any more repositories that [32:51] come up and bubble through this system. [32:53] Is there anything that we'd want to do [32:54] at this stage um before creating a like [32:57] project formally uh within chaos or [33:00] anything that we need to do cuz I think [33:01] we've gone through the steps and the [33:03] issue is public. So I think we're all [33:05] right. [33:06] >> Yeah, it makes it easier that we're just [33:08] doing it under this repository rather [33:10] than like opening a new repository for [33:12] another project. Like if the scope grew [33:14] to that size that would make sense, but [33:16] I think this is a better approach for [33:18] like something that's pretty small [33:19] scale. [33:20] >> Yeah. And the nice thing is I think with [33:22] chaos we actually are getting a bit of [33:25] an ecosystem of projects. These projects [33:28] work together. So to keep them together. [33:31] >> Yeah, definitely. And especially like [33:33] with some of the conversations that are [33:34] happening behind the scenes. I think [33:35] there's there's multiple projects that [33:37] are like data science focused projects [33:39] that are um talking about donating to [33:41] Chaos. So, it's going to become which I [33:44] also think is imp with some of the other [33:46] crazy things that are going on there. [33:49] It's not just one person who's [33:50] developing software here. Um, and chaos. [33:53] There's a lot of people at this point [33:54] that are um and so I think that it's [33:58] good that all the things that are kind [33:59] of like orbiting around chaos, the more [34:02] that they are officially under chaos, I [34:03] think um helps in a lot of way build [34:07] reputation that chaos is more than just [34:09] like uh like theoretical like metrics [34:11] community which it I think it has been [34:13] for a while and um prevents some people [34:17] from making some I don't think valid [34:20] claims about a singular person being the [34:23] only software maintainer in chaos. [34:27] >> Yeah, that's uh that's not possible [34:29] under the by lines unfortunately. [34:31] >> So, [34:33] we'll be all right. [34:38] Okay. Uh the next thing that that brings [34:41] us to is the maintainer agreement. [34:46] So, we've drafted a version of this. Uh [34:49] it's had a couple of review rounds. I've [34:51] had a couple of just like nice comments [34:53] from community members on it which I [34:54] wasn't expecting. Um, which is really [34:57] nice. Um, so I think we're ready to [34:59] publish it, make it live, but I want to [35:02] do that after the [35:05] repo is like reinitialized [35:08] at a project level and then immediately [35:11] I will bring in Earnest under that [35:16] and then we'll start searching for the [35:17] next maintainer so that we don't get [35:19] burned out. [35:21] >> Yeah. Um, yeah, I was hoping that Kaio [35:23] would be on the call because we've [35:24] talked about this a little bit and I've [35:25] talked about this with Kyle that that [35:27] would be the hope like there is our like [35:31] that Kyle would be that next maintainer [35:33] to kind of come in um and be more [35:37] involved in this like in this like he is [35:40] involved but become more of a maintainer [35:42] in this repository. [35:44] >> Yeah. [35:46] Yeah, that'd be perfect. Um, so yeah, [35:48] I'll bring I'm I can bring the [35:50] maintainer agreement back in um as soon [35:52] as we have that repo live. But is there [35:54] anything else that we need to cover on [35:56] that or we'll just uh I'll say like [35:58] bring it in on the next agenda. [36:01] >> Yeah, I think it'd be good to bring in [36:02] for the next agenda because I also think [36:04] there there might be um [36:08] are we recording right now? I don't [36:11] >> uh we are but if finish up the agenda we [36:14] can have a chat afterwards. Yeah, I was [36:16] just saying that the maintainer [36:17] agreement might um be nice to adopt in [36:22] other areas of chaos that might be um [36:25] looking for more official ways to um [36:27] solidify maintain [36:29] >> everywhere because this is how we do it [36:31] in cyber security and sometimes cyber [36:33] security is right. [36:36] >> But yeah, if we want to turn off the the [36:38] recording then I I can say more. [36:40] >> Excellent. Is there anything else that [36:42] we need to cover today on the agenda? I [36:45] think we're good to go. [36:48] I think we're set. All right, Adrian, [36:50] you have control of the recording.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Data Science WG, April 7, 2026.md|CHAOSS Data Science WG, April 7, 2026 by YouTube]] ## Highlights - some assertions about, okay, this tiny archived repo is fully collected in CI and we can check the database to make sure the data is as we expect. I think that's a natural place to like okay at the end of that build that Docker job build an image and push it somewhere so that somebody can just pull down an image with like if all you need is a good enough augur database with data to connect something else to like that that I think would be a good purpose of that. >> Yes. >> But that's more that's I haven't gotten ([View Highlight](https://read.readwise.io/read/01kpb5rx1x0m2c8a0m0wr8zy7w)) - Tags: 👻 ai highlighted - I think a lot of places right now and like the open source analysis space is that download data is never useful and that might not be the right way of thinking about it. Um, and so that's that's more of where I'll be really curious to see the use ca use case and the count and all this different stuff because it's just a diff like it challenges what has been assumed in this space which makes it very interesting. >> Yeah. Yeah. Well, what I mean it might be an outlier case but I think this is an interesting situation of like within ([View Highlight](https://read.readwise.io/read/01kpb5rx3wt5jzrpam2vwhkseh)) - Tags: 👻 ai highlighted - >> Yeah. And the antitrust but good good to know. Um okay, I want us to move on. We've got about 20 more minutes. Let's talk a little bit about the like next steps of formalizing our latest like project repository okioscope. I think I'm saying that right. Um but Ernest you've given a description of ([View Highlight](https://read.readwise.io/read/01kpb5rx6d15ew5hv692qjkbdz)) - Tags: 👻 ai highlighted - of >> Yeah, because it's been sitting inside of the like the like data repository because it started as a data project, but now it is a formal project like Don is happy to have as a project and Earnest is the maintainer. So, we've got everything we solidly need to have it be active at that level. >> Yeah. um putting it in under it's kind of similar which we're going to have to rename but like similar to how we did ([View Highlight](https://read.readwise.io/read/01kpb5rxcg1387avg0vbahk77w)) - Tags: 👻 ai highlighted - that's the Yeah, that's the ask there. I think probably I mean we formalized it as an issue for now, but that was very much just a draft of like here's the template for it. Um yeah. So is there anything that we I mean I'm thinking of this at the level of if there's any more repositories that come up and bubble through this system. Is there anything that we'd want to do at this stage um before creating a like project formally uh within chaos or ([View Highlight](https://read.readwise.io/read/01kpb5rxk2g19c9e9eb7pmhy1s)) - Tags: 👻 ai highlighted - anything that we need to do cuz I think we've gone through the steps and the issue is public. So I think we're all right. >> Yeah, it makes it easier that we're just doing it under this repository rather than like opening a new repository for another project. Like if the scope grew to that size that would make sense, but I think this is a better approach for like something that's pretty small scale. >> Yeah. And the nice thing is I think with chaos we actually are getting a bit of an ecosystem of projects. These projects work together. So to keep them together. ([View Highlight](https://read.readwise.io/read/01kpb5rxt6wh9xapt43t8jqg7c)) - Tags: 👻 ai highlighted