Augur8-Knot WG Meeting, April 14 2026 - CourtneyR.dev's 2nd Brain

Augur/8-Knot WG Meeting, April 14 2026 ![rw-book-cover](https://img.youtube.com/vi/uavmYhfTQkQ/maxresdefault.jpg) 🔗 **Source:** [Augur/8-Knot WG Meeting, April 14 2026](https://www.youtube.com/watch?v=uavmYhfTQkQ) > [!note]+ Document Notes > tags: #open-source #data-analytics #community #software-development #database-optimization > author: CHAOS Project > source: YouTube > reference: https://www.youtube.com/watch?v=uavmYhfTQkQ > date created: 2024-12-19 14:30 > > # 🏷️ Title: Augur/8-Knot WG Meeting, April 14 2026 >  ## 🧰 Action Inbox - [H1] Complete materialized views migration to new database structure — performance optimization #database-optimization - [H2] Implement shareable URLs feature for 8-Knot visualizations — user experience improvement #feature-development - [H3] Create public Docker image with barebones database for contributor onboarding — community growth #developer-experience ## 🧭 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 - [CHAOS Board Blog Post](URL) - [Data Science Working Group Notes](URL) ## 📝 Summary - The CHAOS Project's Augur/8-Knot Working Group discussed database optimization, feature development, and community management during ongoing organizational changes - Key technical updates include completed materialized views (12-hour processing time) and upcoming shareable URLs feature - The group is navigating community drama while planning positive announcements for multiple projects transitioning to CHAOS - Focus on creating contributor-friendly onboarding with Docker images and improved issue management - Performance improvements and caching solutions are priority items for removing technical debt ## 📖 Main Content This working group meeting covered both technical progress and community strategy during a period of organizational transition. The team reported completion of materialized views processing, which took approximately 12 hours, providing a baseline for future optimization. The 8-Knot project is prioritizing issue cleanup, new contributor onboarding, and feature development including shareable URLs and improved visualizations. The discussion addressed community management challenges, with emphasis on rebuilding trust through transparent, opt-in communication strategies. The group is preparing for multiple project announcements while being respectful of data access concerns and community dynamics. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/uavmYhfTQkQ?t=0) — [H1] Materialized Views Completion Status - Key idea: Database optimization completed overnight with 12-hour processing time - Evidence: "CPU usage is idle. So, it's it's been done for a while... It looked like it finished around 2 or 3 in the morning today" #### ⏱️ [02:30](https://youtu.be/uavmYhfTQkQ?t=150) — [H2] Meeting Recording and Attendance Setup - Key idea: Standard meeting procedures with recording notifications and collaborative notes - Evidence: "I pinned the link to the notes if people want to add themselves as attendees" #### ⏱️ [04:15](https://youtu.be/uavmYhfTQkQ?t=255) — [H1] Community Drama and Trust Rebuilding - Key idea: Addressing negative attention while promoting positive work through respectful communication - Evidence: "there's been a lot of drama around this group and an actor to bring a lot of negative energy" #### ⏱️ [06:45](https://youtu.be/uavmYhfTQkQ?t=405) — [H2] CHAOS Foundation Benefits - Key idea: Vendor-neutral space enables collaborative development across organizations - Evidence: "it's part of the Linux Foundation, right? Like it's that vendor neutral sort of space" #### ⏱️ [08:00](https://youtu.be/uavmYhfTQkQ?t=480) — [H3] Behind-the-Scenes Community Solutions - Key idea: Working on inclusive contribution pathways for community members - Evidence: "I'm working behind the scenes on trying to find a solution that works for everyone" #### ⏱️ [09:30](https://youtu.be/uavmYhfTQkQ?t=570) — [H1] 8-Knot Issue Cleanup Initiative - Key idea: Comprehensive issue review and good first issues creation for new contributors - Evidence: "putting a lot of effort this sprint into going through like focusing a lot in the issues that we had since like from a long time" #### ⏱️ [11:00](https://youtu.be/uavmYhfTQkQ?t=660) — [H2] Search Bar and Visualization Upgrades - Key idea: UI/UX improvements and new visualization features in development - Evidence: "the search bar will be finally upgraded in terms of like the design and like the the UIUX" #### ⏱️ [12:15](https://youtu.be/uavmYhfTQkQ?t=735) — [H1] Data Science Working Group Integration - Key idea: Complete pipeline for building new visualizations through notebook development - Evidence: "the entire pipeline is a strong word for building new visualizations in 8 is there" #### ⏱️ [14:30](https://youtu.be/uavmYhfTQkQ?t=870) — [H2] Docker Image for Contributor Onboarding - Key idea: Barebones database access for developers without full infrastructure setup - Evidence: "create a Docker image that basically just ships a completely empty augur database" #### ⏱️ [16:45](https://youtu.be/uavmYhfTQkQ?t=1005) — [H2] Shareable URLs Feature Development - Key idea: URL-based sharing of specific graphs and visualizations - Evidence: "have the kind of like the ID on the URL so that you can copy that URL and send to someone" #### ⏱️ [18:00](https://youtu.be/uavmYhfTQkQ?t=1080) — [H3] Caching and Performance Optimization - Key idea: Addressing technical debt through cache improvements and latency reduction - Evidence: "we had that cache in there because like the augur database and the 8 knot were were hosted in like very even different data centers" #### ⏱️ [20:30](https://youtu.be/uavmYhfTQkQ?t=1230) — [H3] Future Feature Discussion - Key idea: Planning community-driven feature development based on user needs - Evidence: "what functionality does 8 not have right now or types of visualizations that 8 doesn't have right now that users contributors want" ## 📚 References - [CHAOS Board Blog Post](URL) - [Data Science Working Group Meeting Notes](URL) - [Docker Image Repository](URL) ## 🗣️ Paraphrase - The team completed a major database optimization that took 12 hours, establishing a performance baseline for future improvements - Community management focuses on rebuilding trust through transparent, opt-in communication while navigating organizational drama - Technical development prioritizes contributor onboarding tools, feature development like shareable URLs, and performance optimization through caching improvements ## 📰 Newsletter The CHAOS Project's Augur/8-Knot Working Group is making significant progress on both technical and community fronts. With major database optimizations complete and new contributor tools in development, the project is positioned for growth within the vendor-neutral Linux Foundation ecosystem. Key highlights include the completion of materialized views processing, development of shareable URL features, and creation of Docker images for easy contributor onboarding. The team is actively addressing community concerns while preparing for positive project announcements. Resources: [CHAOS Project](https://chaoss.community/), [8-Knot Analytics](URL), [Contributor Guide](URL) ## ✅ Action Items #### Community - Maintainers: Complete issue cleanup and create good first issues for 8-Knot project - Contributors: Develop Docker onboarding tools and notebook-based visualization pipeline - Sponsors: Navigate organizational transitions while maintaining transparent communication - Ecosystem: Coordinate multiple project announcements under CHAOS umbrella #### OSPO - Community Engagement: Address drama through respectful, opt-in communication strategies - Developer Support: Provide barebones database access and contribution pathways - Strategic Alignment: Align multiple projects transitioning to CHAOS foundation ## 🧪 Hypotheses - Simplified onboarding through Docker images will increase new contributor participation - Shareable URLs will improve user engagement and collaboration on 8-Knot visualizations - Caching optimization will significantly improve application performance and user experience - Community-driven feature development will better align with actual user needs ### 📊 Methodology - Track contributor onboarding metrics before and after Docker image deployment - Monitor user engagement patterns with shareable URL feature implementation - Measure application performance improvements through caching optimization - Survey community for feature priorities and implementation feedback ### ❓ Questions - How can the project balance transparency with community members' data privacy concerns? - What specific caching architecture changes will provide the most performance improvement? - How should the project prioritize feature development versus technical debt reduction? ### 🔮 Future Research - Evaluate effectiveness of vendor-neutral foundations for multi-organization collaboration - Study optimal community management strategies during organizational transitions - Investigate performance optimization patterns for data analytics platforms ### 💡 Implications - Practice: Improved developer onboarding and user experience through technical improvements - Policy: Vendor-neutral governance provides stability during organizational changes - Security: Need for careful data access management during community transitions - Education: Docker-based onboarding reduces technical barriers for new contributors - Funding: Linux Foundation umbrella provides sustainable funding model for open source analytics tools ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Meeting structure and agenda organization - Improve: Architecture diagrams for database optimization and caching solutions #### 🔊 Aural learners - Present: Full video recording of working group discussion - Improve: Podcast-style summaries of technical decisions #### 🗣️ Verbal learners - Present: Clear definitions of technical terms and project relationships - Improve: Analogies for database optimization and community management concepts #### 🧩 Kinesthetic learners - Present: Docker images and hands-on development tools - Improve: Step-by-step onboarding guides and interactive tutorials #### 🧠 Logical learners - Present: Clear timelines and performance metrics - Improve: Decision trees for feature prioritization and technical architecture #### 🧑‍🤝‍🧑 Social learners - Present: Collaborative working group format and community discussion - Improve: Structured peer review processes for contributions #### 🧘‍♀️ Solitary learners - Present: Individual contribution pathways and self-paced onboarding - Improve: Self-assessment tools for technical skill development #### 🌿 Naturalistic learners - Present: Ecosystem thinking about project relationships - Improve: Sustainability considerations for long-term project health ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear meeting structure with verbal announcements - Improve: Detailed alt text for any visual materials shared #### Keyboard navigation - Present: Video controls accessible via keyboard - Improve: Ensure all shared tools support keyboard navigation #### Contrast and readability - Present: Clear audio quality for hearing accessibility - Improve: High-contrast visual materials when shared #### Text resizing and reflow - Present: Video format allows for subtitle sizing - Improve: Responsive design for any linked documentation #### Media and captions - Present: Full video recording available - Improve: Professional captions and downloadable transcripts #### Forms and interactions - Present: Accessible meeting participation - Improve: Multiple ways to contribute to discussions ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global open source community participation - Improve: Multi-timezone meeting options and asynchronous participation #### Inclusive language - Present: Professional, respectful communication throughout - Improve: Glossary of technical terms for newcomers #### Neurodiversity support - Present: Structured agenda and clear topic transitions - Improve: Visual agendas and predictable meeting formats #### Representation - Present: Multiple voices and perspectives in technical decisions - Improve: Actively recruit diverse contributors and maintainers #### Psychological safety - Present: Respectful handling of community drama and conflicts - Improve: Clear community guidelines and escalation procedures ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Technical debt must be addressed for performance (materialized views completion) - Inductive strength: Docker images reduce barriers based on past onboarding challenges - Causal reasoning: Vendor-neutral foundation enables multi-org collaboration - Analogical strength: CHAOS success model applies to other open source analytics tools #### Fallacies - Appeal to authority: Linux Foundation credibility assumed without specific evidence - False dichotomy: Community drama vs. positive work presented as either/or choice #### Tone of voice - Overall tone: Professional, collaborative, and solution-focused with acknowledgment of challenges ### 🛡️ DARVO Analysis - Deny: No evidence of denial patterns in community management discussion - Attack: No attacks on community members or critics observed - Reverse victim/offender: No victim/offender reversals present - Emotional cues and rhetoric: Balanced, professional tone focused on constructive solutions ## 🎯 Conclusion The CHAOS Project's Augur/8-Knot Working Group demonstrates effective technical and community management during organizational transition. Key achievements include database optimization completion and feature development planning, while community challenges are addressed through transparent, respectful communication strategies. The focus on contributor onboarding and performance improvements positions the project for sustainable growth within the Linux Foundation ecosystem. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Materialized views optimization provides performance baselines > [!quote] [Augur/8-Knot WG Meeting](https://www.youtube.com/watch?v=uavmYhfTQkQ) by CHAOS Project via YouTube. Published 2026-04-14. Accessed 2024-12-19. > "It looked like it finished around 2 or 3 in the morning today... 12 hours. That's a good marker to know." Database optimization completion establishes performance expectations for future improvements. [view highlight](https://youtu.be/uavmYhfTQkQ?t=0#H1) #xref #articleseed ID:rw_materialize_baseline ### [H2] Vendor-neutral foundations enable multi-organization collaboration > [!quote] [Augur/8-Knot WG Meeting](https://www.youtube.com/watch?v=uavmYhfTQkQ) > "it's part of the Linux Foundation, right? Like it's that vendor neutral sort of space where multiple orgs and multiple people can come together" CHAOS Project benefits from neutral governance structure during organizational transitions. [view highlight](https://youtu.be/uavmYhfTQkQ?t=405#H2) #xref ID:rw_vendor_neutral --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Docker images reduce contributor onboarding friction - Applies to open source projects requiring complex infrastructure setup - Referenced at 14:30 discussion of barebones database access - Links: [[Developer-Experience]] [[Contributor-Onboarding]] #### [Z2] Community drama requires transparent communication strategies - Relevant during organizational transitions and leadership changes - Referenced at 4:15 discussion of rebuilding trust - Links: [[Community-Management]] [[Crisis-Communication]] --- ### ✏️ Fleeting Queue - [F1] Investigate caching architecture improvements for 8-Knot — performance optimization #fleeting #inbox - [F2] Research shareable URL implementation patterns — feature development #fleeting #inbox - [F3] Document issue cleanup methodology for other projects — knowledge sharing #fleeting #inbox --- ## Full Transcript [05:03] Hello. [05:21] Did the materialized views finish last [05:23] night? [05:30] Can you hear me? [05:33] I can't hear you. [05:39] >> Would help if it had my correct [05:41] microphone? [05:41] >> Does it work now? [05:42] >> Yeah. So, um, did the materialized use [05:45] finish up last night? [05:46] >> I was saying I haven't checked, but I'll [05:47] I'll do that right now. Yeah. Let me [05:50] see. I I didn't see what [06:04] R8 not. [06:10] >> What about our eight not? [06:12] >> The the CPU usage is idle. So, it's it [06:16] it's been done for a while. Let's see. [06:18] Okay, let me start to read. [06:20] >> It looked like it finished around 2 or 3 [06:22] in the morning today. [06:23] >> Okay, so 12 hours. That's a good marker [06:26] to know. I think that it'll go down [06:29] pretty significantly [06:32] um this next go around. So I'll I'll [06:34] make the use the new materialized views [06:36] today. Um [06:38] >> the new ones haven't been generated yet. [06:39] Yes. And so I was saying that now that [06:41] that's [06:43] >> um I'm just gonna wait because I'm doing [06:45] some I'm going to do my um board [06:48] eligibility [06:50] um analysis first. [06:54] >> Sweet. [06:56] >> Hi Ruth. The recording is already on [06:59] just as an FYI. [07:02] >> Yeah, I think Zoom warns people as soon [07:04] as they join if like there's already. [07:06] Yeah, I think we set it that way [07:08] actually like we because then sometimes [07:10] we would forget to like actually [07:13] >> I I manually started the recording. Uh [07:15] but I I got here like five minutes [07:16] earlier. [07:18] >> Okay. [07:18] >> Yeah, it wasn't it wasn't automatic. Um [07:20] I can I can maybe look into that setting [07:21] if if that was intended to be automatic. [07:24] >> But yeah, there's also the uh I pinned [07:26] the link to the notes if people want to [07:27] add themselves as attendees. I think [07:29] we're probably [07:31] >> I would think we're we're there's [07:32] probably gonna be more people who are [07:33] interested in coming. So, we'll maybe [07:35] give it a few minutes, maybe give it [07:37] till Friday after. [07:38] >> I can see it both directions of people [07:40] more interested in coming. [07:42] >> Um, [07:45] and um, yeah, uh, I could see people [07:49] either being more interested or not [07:51] wanting to come anywhere near this right [07:52] now with a 10fold pil. And I can [07:55] understand both perspectives. [08:15] Okay, we can see pretty quick if the [08:18] materialized views regenerated [08:20] correctly. [08:24] Hello. [08:26] >> Hello. [08:28] >> How's it going? [08:29] >> Uh, good. Had to connect through uh my [08:32] phone. I don't know why it's not going [08:34] through my computer. So, [08:36] >> yeah, no worries. I can see what the I [08:40] was just saying that I could see it [08:41] either being a more people come to this [08:45] or I could see it being a no one wants [08:48] to come to this this week type of [08:50] situation. So, we'll just see. Um if [08:54] not, we can kind of do our our general [08:56] updates and end it early. Um cuz I'm [08:59] sure um there's more exciting [09:02] announcements coming up in this group. I [09:04] that's that is the one thing that um [09:07] especially if this is going to be the [09:08] crowd I think that is good to talk about [09:10] is um and I'm personally okay with [09:14] talking about this with recruiting is [09:15] that there's been a lot of drama around [09:17] this group and an actor to bring a lot [09:21] of negative energy towards this and [09:22] negative attention. And there's a lot of [09:25] really great work going on. And when we [09:28] come to announce like multiple projects [09:30] that fall under this, I want to think [09:33] about how we can public we can bring it [09:36] the positive attention to that work um [09:39] while also being incredibly respectful [09:42] to people's data access um and like kind [09:46] of the options that we have and routes [09:48] of like of publicizing whether it be um [09:52] like an augur fork or eight not moving [09:55] over to chaos or another project that's [09:57] talking about coming over to chaos. Um [10:00] or a um like when we're trying to let [10:03] people know that that exists, how should [10:05] we go about doing that? And maybe trying [10:08] to crowdsource more like, hey, please [10:11] post this on your like LinkedIn social [10:13] stuff like that. Um making it a very [10:15] community optin [10:17] um information situation because I think [10:19] that helps rebuild trust. [10:22] Yeah, I think that's one of the powerful [10:23] powerful things about chaos is like it's [10:25] it's I mean it's part of the Linux [10:26] Foundation, right? Like it's that vendor [10:28] neutral sort of space where multiple [10:30] orgs and multiple people can come [10:32] together and work on the same shared [10:34] thing. Uh so yeah, definitely definitely [10:37] excited for kind of the future of what [10:40] ends up kind of coming next. Um if [10:42] anyone hasn't I I think everyone in this [10:44] room has already seen but there there [10:46] was a chaos board blog post update. I [10:48] put the link to that in the meeting [10:49] notes in case anyone wants sort of the [10:51] latest of that. Um just updates from [10:54] from the board on that. Um but yeah, I [10:56] think otherwise we can kind of just talk [10:58] about kind of what what we're doing more [10:59] concretely with with uh this working [11:02] group and [11:04] things. I didn't have any specific [11:06] updates on like the augur auger code [11:08] just yet. I'm I'm working behind the [11:10] scenes on trying to find a solution that [11:12] works uh for for everyone in terms of [11:15] making sure that people have some way [11:16] they they feel like they can contribute [11:19] um and and feel like they're welcome to [11:21] the community. Um so I'm I'm kind of [11:23] working a little bit behind the scenes [11:24] on that, but I'll I'll put out whatever [11:27] whatever messages are appropriate when [11:28] when that's ready to be announced. Um so [11:32] just know that that's that's being [11:34] worked on behind the scenes. Um I think [11:36] the main the bulk of the updates I think [11:38] are largely going to be on eight knot. [11:39] Um so like Kaio did you did you want to [11:42] do any kind of eight not updates? [11:47] >> Yeah so in terms of like 8 knot updates [11:50] uh we are like putting a lot of effort [11:53] this sprint into going through like [11:56] focusing a lot in the issues that we had [11:59] since like from a long time so a few [12:02] years back. uh and we want to clean it [12:05] up everything have like all the [12:07] information as possible and uh all the [12:10] issues as they are still relevant. Uh [12:12] and then by with this effort we want to [12:15] create a lot of good first issues as [12:18] well for new contributors like to to [12:20] contribute more to 8 knot and [12:22] everything. So by the end of this sprint [12:25] uh I'd say like the the plan is to have [12:28] have gone all like through all of these [12:30] issues and uh make sure that like 8 knot [12:33] is in a good uh stand in terms of like [12:36] this uh and uh new features as well like [12:40] as we go through this sprints hopefully [12:43] we will have like a new features like [12:45] the the search bar will be finally um [12:49] upgraded in uh in terms of like the [12:51] design and like the the the UIUX like [12:55] we've been working on for like the [12:57] previous sprint and uh new [12:59] visualizations are also being worked on. [13:02] So uh soon soon to be released I'd say [13:05] in the next sprint. So that's that's [13:07] kind of like the the updates on the 8 [13:09] knot side. [13:13] Yeah, I I'll add on to that that um the [13:16] visualization issues for the data [13:19] science working group now kind of the [13:20] entire pipeline is a strong word for um [13:24] building new visualizations in 8 is [13:27] there of um we have the visualization [13:30] concept the overall issues in 8 um the [13:33] first step of that is building a um [13:35] notebook in the data science working [13:37] group and so there's link cod issues and [13:40] tells you exactly what is each step you [13:43] need to do to do a definition of done. [13:45] And the hope is that in the near future [13:48] there will be a um like a database that [13:52] we connect to there like a with a data [13:54] collection tool. I'm going to start [13:55] saying instead of augur we're going to [13:57] be I'll be calling a data collection [13:58] tool for the time being um until a um [14:02] fork project name comes out. Um but [14:04] we'll have a public access accessible um [14:09] whether that be in a docker image or [14:10] what exactly that format is we don't [14:12] know but um how where people can connect [14:17] to a barebones um data collection [14:20] database and can start to develop on a [14:23] visualization in a notebook and work on [14:25] data analysis or working directly on 8 [14:28] knot. Um, this has been something we've [14:30] been building to for a while and I'm [14:31] very excited to um hopefully get some [14:34] new contributors in here. [14:37] >> Yeah. And that um that sort of barebones [14:39] database I think that was something that [14:41] got brought up at last week's uh data [14:43] science working group meeting. Um, I [14:45] know I'm I I that's kind of one of the [14:47] things I have been trying to work on for [14:49] the last little bit, but um I've been a [14:51] little bit distracted, but I do I did a [14:54] while ago create a Docker image that [14:56] basically just ships a completely empty [14:58] augur database that it's like [14:59] structurally correct and it'll let 8 not [15:01] run, but it's just got no data in it. [15:04] So, I believe that is I put the link to [15:07] that like the where you can docker pull [15:09] that from. Um [15:12] I think that's in the the data science [15:14] working group notes from last week. Um [15:17] that I think if people are looking to [15:19] get started like just sort of running 8 [15:21] knot locally I think that's maybe a good [15:23] option if you don't want to run your own [15:25] like augur instance. Um but I there'll [15:29] definitely be some improvements coming [15:30] to that uh hopefully soon. Uh just to [15:33] kind of provide people with more more [15:35] easy options for how how do you get some [15:38] of this data and start start making [15:40] notebooks start help contributing to 8 [15:42] knot start kind of being able to build [15:44] stuff without having to do too much [15:46] infrastructure and stuff on your own [15:48] machine. [15:54] Yeah, I think that's that's all there [15:56] was. That all that is there in the in [15:59] the document so far as far as explicit [16:01] agenda items. Does anyone have [16:04] any like things to add or questions or [16:07] anything? [16:08] Um, this is going to be kind of out of I [16:11] guess like left field, but I do think [16:12] it's worth like discussing whether it's [16:14] now or later of like what we see as um [16:18] like what what is the next like feature [16:20] or enhancement that we want to focus on [16:22] for 8 knot? Um those are like kind of [16:25] discussion like what is like the thing [16:27] that maybe the community values the most [16:29] of like what are some like what [16:31] functionality does 8 not have right now [16:33] or types of visualizations that 8 [16:36] doesn't have right now that u users [16:38] contributors want to have and want to [16:41] work on. Um that's something that has [16:45] been top of mind for me. [16:51] Yeah, one of the things that I was uh [16:52] also hoping to have it like a quick uh [16:56] implementation of this for this print as [16:58] well uh is something that we discussed [17:00] before even like me, Adrian and Josh, [17:03] which is like sharable URLs. So like if [17:06] Yeah. If someone is looking into like a [17:09] specific graph, then have the kind of [17:11] like the ID on the URL so that you can [17:14] copy that URL and send to someone, then [17:17] you're going like that person opening [17:19] that link will go straight into that [17:21] stuff there. Uh so that's one thing that [17:24] I I think would be a great feature and a [17:27] quick solution to be added into eight [17:29] node as well for now. [17:31] >> Yeah, that's it's great. I'll be c [17:33] really curious to see um see that [17:36] because that's I do think we're kind of [17:37] getting like a lot of the stuff with [17:39] eight knot um I think that we're getting [17:42] to the edge of like kind of fixing a lot [17:44] of stuff. Um I do I know that what [17:46] exactly the um solution is from like a [17:50] caching standpoint cuz that's something [17:51] that's kind of come up is that right now [17:52] you have to manually reset the cache and [17:55] what is the like proper solution like to [18:00] not needing to reset the cache I would [18:02] say is kind of the last um historical [18:05] like tuck debt type or like kind of like [18:07] improvements of the current structure [18:09] and I think that we haven't talked about [18:12] feature like really talked about new [18:14] functionality in a in a really long [18:16] time. So, I like hearing about that, [18:18] Kaio, and just wanted to bring it up so [18:20] then people can start thinking about [18:22] that and we can start having more open [18:23] discussions about where we want this [18:26] project to go. [18:28] Yeah, I definitely think like the [18:29] performance and the caching side um like [18:32] that's [18:33] that going to help us eliminate a lot of [18:35] just kind of like I think I think we had [18:37] that cache in there because like the [18:40] augur database and the 8 knot were were [18:42] hosted in like very even different data [18:44] centers or different regions of of the [18:47] US. And so there was a lot of latency [18:49] between if 8n had to go all the way to [18:51] augur to get data and it would it was [18:53] better to have its own little cache [18:55] closer to 8. And so I think since the [18:59] infrastructurees kind of moved and [19:00] changed since then, maybe maybe that's [19:02] worth looking at like can we eliminate [19:03] some of those layers? Can we make some [19:05] of our materialized views more just more [19:09] efficient like those kinds of things so [19:12] that so that then we can just kind of [19:13] work towards being that like like Kyle [19:15] said people being able to share a URL [19:16] with someone and then it just loads [19:18] really quickly and and just like is nice [19:21] to work with and sort of just works as [19:23] much as we can get it to work. [19:31] Yeah. Does anyone else have ideas for [19:33] for things they want to see in 8 or kind [19:36] of visualizations or statistics they [19:39] want to see for analyzing repositories, [20:00] right? Well, it sounds like if If no [20:02] one's got things to add, um I think we [20:04] could probably go ahead and wrap early. [20:06] This is I think this is a good good kind [20:08] of chance to kind of talk about 8 and I [20:12] think I think definitely bringing the [20:13] eight not updates into these meetings is [20:14] is definitely like a nice a nice kind of [20:17] way to help bring more contributors to [20:18] that and and improve keep those keep at [20:21] least that side of the the house moving [20:23] forward. Um so yeah, thank you guys for [20:26] coming. Um notes as always are in the in [20:28] the chat. Um, and I'll I'll try and see [20:31] I'll try and work with uh Elizabeth or [20:33] whoever uh to kind of start getting [20:35] these recordings actually posted uh [20:37] posted to YouTube so other people can [20:38] see them and and [20:41] yeah. Yeah. See you guys. [20:44] >> All right. Great. Thank you so much. See [20:45] you everyone later. All right. See you. [20:46] Bye.  📄 **Full text:** ![[Full Document Contents/Articles/Augur8-Knot WG Meeting, April 14 2026.md|Augur/8-Knot WG Meeting, April 14 2026 by YouTube]] ## Highlights - orgs and multiple people can come together and work on the same shared thing. Uh so yeah, definitely definitely excited for kind of the future of what ends up kind of coming next. Um if anyone hasn't I I think everyone in this room has already seen but there there was a chaos board blog post update. I put the link to that in the meeting notes in case anyone wants sort of the latest of that. Um just updates from from the board on that. Um but yeah, I think otherwise we can kind of just talk about kind of what what we're doing more concretely with with uh this working ([View Highlight](https://read.readwise.io/read/01kpb60ctm5n2rnae4k55hrc3h)) - Tags: 👻 ai highlighted - orgs and multiple people can come together and work on the same shared thing. Uh so yeah, definitely definitely excited for kind of the future of what ends up kind of coming next. Um if anyone hasn't I I think everyone in this room has already seen but there there was a chaos board blog post update. I put the link to that in the meeting notes in case anyone wants sort of the latest of that. Um just updates from from the board on that. Um but yeah, I think otherwise we can kind of just talk about kind of what what we're doing more concretely with with uh this working ([View Highlight](https://read.readwise.io/read/01kpb616g0fhbnyqawpk4ty9tp)) - Tags: 👻 ai highlighted - just know that that's that's being worked on behind the scenes. Um I think the main the bulk of the updates I think are largely going to be on eight knot. Um so like Kaio did you did you want to do any kind of eight not updates? >> Yeah so in terms of like 8 knot updates uh we are like putting a lot of effort this sprint into going through like focusing a lot in the issues that we had since like from a long time so a few ([View Highlight](https://read.readwise.io/read/01kpb60cv37myrqsyr0rc18zhf)) - Tags: 👻 ai highlighted - just know that that's that's being worked on behind the scenes. Um I think the main the bulk of the updates I think are largely going to be on eight knot. Um so like Kaio did you did you want to do any kind of eight not updates? >> Yeah so in terms of like 8 knot updates uh we are like putting a lot of effort this sprint into going through like focusing a lot in the issues that we had since like from a long time so a few ([View Highlight](https://read.readwise.io/read/01kpb616gh13kpp8djazh9hynk)) - Tags: 👻 ai highlighted - >> Yeah, that's it's great. I'll be c really curious to see um see that because that's I do think we're kind of getting like a lot of the stuff with eight knot um I think that we're getting to the edge of like kind of fixing a lot of stuff. Um I do I know that what exactly the um solution is from like a caching standpoint cuz that's something that's kind of come up is that right now you have to manually reset the cache and what is the like proper solution like to ([View Highlight](https://read.readwise.io/read/01kpb60cw1gjy9w2sfv63nx6bh)) - Tags: 👻 ai highlighted - >> Yeah, that's it's great. I'll be c really curious to see um see that because that's I do think we're kind of getting like a lot of the stuff with eight knot um I think that we're getting to the edge of like kind of fixing a lot of stuff. Um I do I know that what exactly the um solution is from like a caching standpoint cuz that's something that's kind of come up is that right now you have to manually reset the cache and what is the like proper solution like to ([View Highlight](https://read.readwise.io/read/01kpb616hevbf27k0mz012cs0y)) - Tags: 👻 ai highlighted