CHAOSS Weekly Community Call, April 21, 2026

CHAOSS Weekly Community Call, April 21, 2026 ![rw-book-cover](https://img.youtube.com/vi/zTi_F-CKXNk/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Weekly Community Call, April 21, 2026](https://www.youtube.com/watch?v=zTi_F-CKXNk) > [!note]+ Document Notes > tags: #chaoss #open-source #governance #community-management #repository-management #elections > author: CHAOSS > source: YouTube > reference: https://www.youtube.com/watch?v=zTi_F-CKXNk > date created: 2024-12-19 14:30 > > # 🏷️ Title: CHAOSS Weekly Community Call, April 21, 2026 >  ## 🧰 Action Inbox - [H1] Create repository proposal process through GitHub issue in community repo — data science working group needs new repo #governance - [H2] Implement GitHub teams for working group repository permissions — infrastructure committee coordination #repository-management - [H3] Create issues for Hugo website development to enable contributor onboarding — web developers needed #website ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [CHAOSS Community Repository](https://github.com/chaoss/community) - [CHAOSS Hugo Website](https://github.com/chaoss/hugo) ## 📝 Summary - CHAOSS community discussed creating formal processes for new repository requests within existing working groups - Infrastructure committee formation and GitHub permissions management were key governance topics - Community elections are imminent with candidate nomination process requiring PR endorsements - Augur project has officially separated from CHAOSS with potential fork remaining under CHAOSS - Website migration to static Hugo-based system is in progress but needs developer contributors ## 📖 Main Content The CHAOSS community is undergoing significant organizational changes, focusing on governance formalization and infrastructure management. The primary challenge involves establishing clear processes for repository creation requests from working groups, as admin access is being deliberately restricted to fewer people. The community is implementing GitHub teams for permission management and requiring DCO sign-offs as mandated by the Linux Foundation. Simultaneously, upcoming elections require candidates to submit PRs with two eligible voter endorsements, while the Augur project separation creates opportunities for community-managed forks. The website modernization effort using Hugo requires additional developer contributors to complete the migration from WordPress. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/zTi_F-CKXNk?t=0) — [H1] Repository creation process discussion - Key idea: Data science working group needs formal process for new repository under existing working group - Evidence: "What is the proper process to propose a new repository in the chaos organization that fits under an existing working group" #### ⏱️ [02:15](https://youtu.be/zTi_F-CKXNk?t=135) — [H2] Current informal approach to repository management - Key idea: CHAOSS historically has loose, informal processes for repository creation - Evidence: "I don't think there is a process. I think it's been, you know, very true to chaos form. I'm just very loose with that" #### ⏱️ [03:30](https://youtu.be/zTi_F-CKXNk?t=210) — [H1] Admin access restrictions necessitate formal processes - Key idea: Reduced admin access means repository creation needs structured approval - Evidence: "There's going to be so much less people with admin access and so the permissions are only going to be in the hands of a few now" #### ⏱️ [05:45](https://youtu.be/zTi_F-CKXNk?t=345) — [H2] GitHub issue-based approval process proposed - Key idea: Using GitHub issues in community repository for transparent repository requests - Evidence: "Create an issue where we go through everyone that was informed about it everyone that said yes in the process already tag them into it" #### ⏱️ [07:20](https://youtu.be/zTi_F-CKXNk?t=440) — [H3] GitHub teams for permission management - Key idea: GitHub teams can manage working group repository access automatically - Evidence: "You could have like a data science working group team and then that team can just own some repos" #### ⏱️ [09:10](https://youtu.be/zTi_F-CKXNk?t=550) — [H2] DCO requirement from Linux Foundation - Key idea: Developer Certificate of Origin sign-off is mandatory across CHAOSS repositories - Evidence: "That is actually an LF thing. So we don't have control over that. We have to implement that" #### ⏱️ [10:30](https://youtu.be/zTi_F-CKXNk?t=630) — [H1] CHAOSS elections imminent with PR-based nominations - Key idea: Elections starting within days requiring GitHub PR submissions for candidates - Evidence: "The chaos elections are almost here... there is a PR with all of the information and a guide for candidates" #### ⏱️ [12:00](https://youtu.be/zTi_F-CKXNk?t=720) — [H2] Two endorser requirement for election candidates - Key idea: Candidates need endorsements from two eligible voters via PR approvals - Evidence: "You need an endorsement from two eligible voters I think to to be a candidate" #### ⏱️ [14:15](https://youtu.be/zTi_F-CKXNk?t=855) — [H1] Augur project officially separated from CHAOSS - Key idea: Augur is no longer part of CHAOSS organization with potential community fork - Evidence: "Augur is officially outside of chaos. Um and there is going to be there is a proposal um for like having some type of fork" #### ⏱️ [16:45](https://youtu.be/zTi_F-CKXNk?t=1005) — [H2] Hugo website migration progress update - Key idea: Static website generation using Hugo is in development but needs contributors - Evidence: "I was able to get it on just quickly generated on GitHub pages and so people can kind of browse around" #### ⏱️ [18:30](https://youtu.be/zTi_F-CKXNk?t=1110) — [H3] Website styling and content formatting needed - Key idea: Website content migrated but requires significant styling and layout work - Evidence: "The styling still needs to be updated to like better match the current chaos website" #### ⏱️ [20:00](https://youtu.be/zTi_F-CKXNk?t=1200) — [H2] Need for contributor issues and documentation - Key idea: GitHub issues needed to enable new contributors to website development - Evidence: "It will be easier for contributors if you can have issues... So they know what to pick up" ## 📚 References - [CHAOSS Community Repository](https://github.com/chaoss/community) - [CHAOSS Hugo Website Development](https://github.com/chaoss/hugo) - [Linux Foundation DCO Requirements](https://developercertificate.org/) ## 🗣️ Paraphrase - CHAOSS is establishing formal governance processes for repository creation as they reduce the number of people with admin access, moving away from their historically informal approach - The community is preparing for elections where candidates must submit pull requests with endorsements from two eligible voters, while also managing the separation of the Augur project - Website modernization efforts using Hugo are progressing but require additional developer contributors to complete the styling and create proper onboarding documentation ## 📰 Newsletter The CHAOSS community is maturing its governance structure with new formal processes for repository management and upcoming elections. As they transition from informal to structured approaches, they're implementing GitHub teams for permission management and requiring proper endorsement processes for leadership candidates. The separation of the Augur project creates new opportunities for community-driven development, while their website modernization using Hugo shows promise but needs developer support. This evolution reflects the natural growth of open source communities as they balance accessibility with accountability. Resources: [CHAOSS Community](https://chaoss.community/), [GitHub Teams Documentation](https://docs.github.com/en/organizations/organizing-members-into-teams), [Hugo Static Site Generator](https://gohugo.io/) ## ✅ Action Items #### OSPO - Policy & Governance: Document repository creation process in community guidelines - License Compliance: Ensure DCO sign-off implementation across new repositories - Community Engagement: Support working group transition to GitHub teams model #### Community - Maintainers: Create GitHub teams for working group repository management - Contributors: Develop onboarding issues for website development contributors - Sponsors: Support infrastructure committee formation and governance documentation #### DevRel - Developer experience: Improve documentation for repository request processes - Community management: Facilitate election process and candidate support - Education: Create tutorials for GitHub teams and permission management ## 🧪 Hypotheses - Formal repository creation processes will reduce confusion and improve community transparency - GitHub teams will streamline permission management while maintaining security - Static site generation will reduce hosting costs and improve contributor experience - Structured election processes will increase candidate participation and community trust ### 📊 Methodology - Track repository request processing time before and after formal process implementation - Measure contributor onboarding success rates with GitHub teams versus individual permissions - Compare website maintenance effort between WordPress and Hugo implementations ### ❓ Questions - How will the infrastructure committee coordinate with existing working group autonomy? - What happens to existing Augur community members during the transition period? - How can the website migration maintain content contributor accessibility? ### 🔮 Future Research - Best practices for open source project governance scaling - Effectiveness of different permission management models in GitHub organizations - Impact of static site generation on community content contribution patterns ### 💡 Implications - Practice: Repository requests require more planning and community coordination - Policy: Infrastructure committee will need clear charter and decision-making authority - Security: DCO requirements strengthen code provenance and legal compliance - Education: Contributors need training on new GitHub teams and permission models ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Process flow discussion, repository organization concepts - Improve: Governance workflow diagrams, GitHub teams visualization #### 🔊 Aural learners - Present: Community call format with verbal discussion - Improve: Process explanation podcasts, recorded tutorials #### 🗣️ Verbal learners - Present: Clear definitions of governance terms, process explanations - Improve: Glossary of community roles, governance terminology guide #### 🧩 Kinesthetic learners - Present: GitHub PR process, hands-on repository management - Improve: Step-by-step repository request workflows, interactive tutorials #### 🧠 Logical learners - Present: Permission management logic, governance decision trees - Improve: Process flowcharts, decision matrices for repository approval #### 🧑‍🤝‍🧑 Social learners - Present: Community calls, collaborative decision-making - Improve: Working group coordination guides, mentorship programs #### 🧘‍♀️ Solitary learners - Present: GitHub issue templates, self-service documentation - Improve: Individual contributor guides, self-assessment checklists #### 🌿 Naturalistic learners - Present: Organic community evolution concepts - Improve: Community ecosystem metaphors, governance lifecycle thinking ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Meeting transcript with clear speaker identification - Improve: Structured headings for different agenda items #### Keyboard navigation - Present: Standard video controls and transcript access - Improve: Keyboard shortcuts for transcript navigation #### Contrast and readability - Present: Plain text transcript with good contrast - Improve: Enhanced formatting for speaker changes and emphasis #### Text resizing and reflow - Present: Responsive transcript layout - Improve: Customizable text size options #### Media and captions - Present: Full transcript available for video content - Improve: Time-stamped captions, speaker identification #### Forms and interactions - Present: Standard video player interface - Improve: Accessible transcript search functionality ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global open source community participation - Improve: Multi-timezone meeting options, asynchronous participation methods #### Inclusive language - Present: Professional, welcoming community tone - Improve: Define technical jargon, avoid exclusionary terminology #### Neurodiversity support - Present: Structured agenda, clear meeting flow - Improve: Advance agenda sharing, meeting summaries #### Representation - Present: Multiple community member voices, collaborative decision-making - Improve: Ensure diverse working group leadership representation #### Psychological safety - Present: Respectful discussion tone, open question format - Improve: Clear community guidelines, conflict resolution processes ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Infrastructure committee formation logically follows from admin access reduction - Inductive strength: GitHub teams success inferred from other organization experiences - Causal reasoning: Formal processes needed because informal approaches don't scale - Analogical strength: Fedora website model applied to CHAOSS context #### Fallacies - Appeal to tradition: "Very true to chaos form" could resist necessary change - False dilemma: Formal vs informal processes presented as binary choice #### Tone of voice - Overall tone: Collaborative and pragmatic, focused on community needs and practical solutions ### 🛡️ DARVO Analysis - Deny: No denial patterns observed in governance discussions - Attack: No attacks on community members or processes - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive, solution-focused language throughout ## 🎯 Conclusion The CHAOSS community is successfully navigating the transition from informal to formal governance structures while maintaining their collaborative culture. The key takeaway is that growing open source communities need structured processes to scale effectively, but implementation must preserve community values and accessibility. Next steps involve documenting these processes clearly and ensuring the infrastructure committee has the authority and resources needed to support community growth. This evolution represents a healthy maturation that other open source communities can learn from. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Repository governance requires formal processes at scale > [!quote] CHAOSS Weekly Community Call, April 21, 2026 by CHAOSS via YouTube. Published 2026-04-21. Accessed 2024-12-19. > "There's going to be so much less people with admin access and so the permissions are only going to be in the hands of a few now." CHAOSS community recognizing need for structured repository creation processes. [view highlight](https://youtu.be/zTi_F-CKXNk?t=210#H1) #xref #articleseed ID:rw_CHAOSS_001 ### [H2] GitHub teams enable scalable permission management > [!quote] CHAOSS Weekly Community Call, April 21, 2026 > "You could have like a data science working group team and then that team can just own some repos." Technical solution for managing working group repository access automatically. [view highlight](https://youtu.be/zTi_F-CKXNk?t=440#H2) #xref ID:rw_CHAOSS_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Open source communities need governance scaling strategies - Applies to communities transitioning from informal to formal structures - Evidence from CHAOSS repository management discussion - Links: [[Community-Governance]] [[Open-Source-Scaling]] #### [Z2] GitHub teams provide technical governance solutions - Scope: Large organizations with working group structures - Evidence from infrastructure committee recommendations - Links: [[Permission-Management]] [[GitHub-Organization-Management]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Research Fedora website content management system approach — Adrian mentioned as model #fleeting #inbox - [F2] Document DCO implementation requirements across Linux Foundation projects — compliance research needed #fleeting #inbox - [F3] Create contributor onboarding checklist for Hugo website development — immediate need identified #fleeting #inbox --- ## Full Transcript [00:00] cloud. Um, and we can get started. I put [00:03] something at the top of the agenda [00:04] because I know there is someone who's [00:06] only able to be here for a couple of [00:07] minutes because there was a good topic [00:09] that is kind of communitywide that was [00:11] brought up in the data science working [00:13] group meeting and I don't anticipate we [00:16] will have an answer to this right now [00:18] but just wanted to propose it to the [00:20] larger community is that what is the [00:22] proper process to propose a new [00:25] repository in the chaos organization [00:28] that fits under an existing working [00:30] group. So it's not we're not creating [00:33] like a new project, a new working group, [00:34] but a new repo is needed for said group. [00:38] What do you do? [00:42] >> I don't think there is a process. I [00:44] think it's been, you know, very true to [00:47] chaos for true to chaos form. I'm just [00:51] very loose with that. Um so, you know, [00:54] whatever is kind of needed for people to [00:56] do their what they want to do or what [00:58] they're trying to accomplish. I think um [01:00] that being said there like yeah there [01:03] may need to be a process. [01:06] >> Yeah, especially now there's a lot less [01:07] there's going to be so much less people [01:08] with admin access and so the per like [01:11] and purposely so there's only going to [01:13] the permissions are only going to be in [01:15] the hands of a few now. Um so this is [01:18] going to be more necessary across the [01:21] board I would assume. [01:25] Would you say this is open- source [01:28] process and organizational structure? [01:30] Because if so, that's my favorite topic. [01:32] Okay, so this is good. So I think we [01:35] have a couple of issues going on the [01:37] subject of like where and how to place [01:38] this. need to shape up the repo just a [01:40] little bit this next week and then we're [01:43] gonna I think create I well what I'm [01:46] gonna do is like throw it in at that [01:49] level with an issue where we go through [01:52] everyone that was informed about it [01:54] everyone that said yes in the process [01:56] already tag them into it make sure that [01:57] there is a full and open process um I [02:00] think uh Cali and I can probably have a [02:02] discussion if there's anything more [02:04] formal than just creating that issue and [02:06] seeing through that process how we want [02:09] to formalize it, but I think using this [02:10] as a clear test case is good. It is [02:13] interesting because this is a stage of [02:16] the project where it's going to sit [02:18] under a working group and it has the [02:20] community of the working group. If it [02:22] were to spin off into a formal project [02:26] that meets on its own hours, that's [02:28] actually a simpler process because we [02:29] already have that in place. So for this [02:31] it's a bit of a interesting use case [02:34] single issue and then if we need to [02:36] write up documentation from that or [02:37] point back to just that issue. Adrian [02:40] what do you think? [02:41] >> No I was just going to add kind of some [02:43] more to the Kelly's general general [02:44] topic about like the process. I think [02:47] yeah it sounds like I did I do know that [02:49] I've seen in the chaos charter that I [02:51] think for repositories I think like DCO [02:54] sign off is like a requirement across [02:56] chaos. Uh I don't know if that's [02:58] necessarily a requirement for creating a [02:59] repo. Um, but I also and I also know [03:01] that you can do like teams in GitHub so [03:04] that like you could have like you could [03:05] have like a data science working group [03:07] team and then that team can just own [03:09] some repos and like if you if you get [03:11] added to the team, you automatically get [03:13] access to whatever the team has access [03:15] to. So like that could be a way to like [03:17] even though all the repos are still [03:19] under like github.com/kaosreo [03:22] name like you could still kind of have [03:25] it the permissions sort of managed as a [03:28] group and I imagine that would be [03:30] something that would fall under a lot of [03:31] the like the management of that would [03:33] probably be the the new infrastructure [03:34] committee. [03:41] >> Yeah, I think that's perfect. Yeah. [03:44] Um, we may need to put that into place [03:48] now. Or [03:52] >> yeah, [03:54] >> I think for this one, let's run it [03:57] through as an issue, as a dialogue, and [04:00] make sure everyone definitely everyone, [04:02] let's on this like call that's engaged, [04:04] get you tagged into it, and make sure [04:06] that we have a clear process for that. [04:09] When you say an issue, are you saying on [04:11] the data science working group issue or [04:13] should this be something in the [04:15] community like like the chaos community [04:18] repository? [04:20] >> It should be in the community repository [04:22] most likely. [04:23] >> Okay. [04:23] >> Yeah, cool. [04:25] >> Yeah, I think as long as there's some [04:27] sort of paper trail as to how it came [04:29] about. Um I think Yeah. And um just a uh [04:33] thing about the DCO, that is actually an [04:35] LF thing. So we don't have control over [04:37] that. We have to implement that. So, I [04:40] know it's a pain, but yeah, [04:45] >> it's good cyber security. Come on, [04:47] y'all. [04:48] >> I mean, that's that's fair. [04:52] >> I'm really bad at our best. [04:56] >> I am. It's I [04:59] do. We have any Does anybody have [05:00] anything else on this specific topic [05:02] before we [05:05] move on? [05:06] >> No, I've got my note. We'll uh hand that [05:09] repo off like a PR and link it on the [05:12] community repository issues and get full [05:15] feedback. Perfect. [05:16] >> Done. Thank you all. I'm going to go [05:19] enjoy the sunshine. Very well. [05:23] >> Um uh the next thing on the agenda just [05:27] going to mention that the Slack is [05:29] continuing on and is being paid for by [05:32] the LF. So love a something working [05:37] itself out. Sounds great to me. [05:41] Um next is that the new infrastructure [05:45] committee is being worked on on the [05:47] chaos board. There was an announcement [05:50] in general if anybody would like to [05:52] refer to it um that about this. So [05:55] really excited to kind of see this like [05:57] next step maturing the chaos community [05:59] and having a little bit more structure [06:02] and so more to come about that. Also the [06:08] election the chaos elections are almost [06:10] here which is crazy. We've been talking [06:11] about this for a really long time. Um I [06:15] yeah and they should come in the next um [06:18] day or two and there is a PR with all of [06:23] the information and a guide for [06:27] candidates about the information [06:29] information about running yourself or um [06:32] nominating somebody else. [06:35] I did not put this in the minutes. I [06:36] probably should. Um, just so you all [06:38] know, there is an open office hours on [06:40] Thursday, uh, where you can come in and [06:43] ask any questions. So, it will [06:44] definitely be open by Thursday. By [06:46] Thursday, um, and then there's also a [06:49] Slack channel that's election help. So, [06:51] if you have questions, pop in there or [06:53] you can you can ask me or Emma, Irwin or [06:55] Ally. Okay. [06:59] >> Then, what was the Can you put the [07:00] channel in the working group in the [07:02] document? That'd be great. [07:04] >> Great. Um, is there any questions about [07:09] the elections? [07:15] >> Is there a particular like is I'm seeing [07:18] the the sort of part about like you need [07:20] an endorsement from two eligible voters [07:23] I think to to be a candidate. Is there a [07:26] particular like format or location that [07:29] that like should that be is that just [07:32] like how do like would I just go and [07:35] reach out to two people and then [07:38] >> yeah just point them [07:39] >> include screenshots [07:42] >> I think we're asking for approvals on [07:44] the PR on [07:46] >> oh you make a PR hand of seat okay yeah [07:50] that seems to be the simplest way to [07:52] kind of track that so [08:05] All right. If there's nothing else, I'll [08:07] go to the next one. Um, extension of [08:10] kind of the announcement that was made [08:12] at the end of last week. I was just [08:14] going to acknowledge that um, Augur is [08:16] officially outside of chaos. Um and [08:21] there is going to be there is a proposal [08:25] um for like having some type of fork or [08:29] the project under chaos and there will [08:32] be a coordinated effort to update all [08:34] the documents and mentions of oer in the [08:37] chaos documentation [08:39] and um if you want more information or [08:42] kind of seeing the day-to-day [08:44] developments around this please join the [08:46] working group software which is a [08:48] combination of all the software working [08:49] groups which has been really cool that [08:51] came out of this past this meeting last [08:53] week which was really exciting. Um and [08:57] the augur um 8 knot working group um the [09:03] that channel which will be renamed um so [09:06] there will be a lot to come on this I [09:08] think there's a lot of people who are [09:10] involved on the has been involved in the [09:12] actual project is including myself very [09:14] excited to get back to working on the [09:16] project itself um instead of all the [09:19] administrative sides around it. Um, [09:23] so yeah, that's that. Um, [09:27] I don't know if somebody wants to or [09:29] Adrian was the website you [09:32] >> Yeah, this was just something I was [09:33] working on. I've been I've been doing a [09:34] little bit of traveling this week, but I [09:36] had some time on the train just to kind [09:37] of mess around with the with some of the [09:39] new, as you people probably know from [09:41] previous meetings, I've been kind of [09:42] experimenting with kind of what was [09:45] talked about with with hey, can we move [09:47] since since we're getting most of the [09:48] content from the chaos website from [09:49] GitHub? Anyway, does it make sense to [09:52] kind of try seeing if if a more [09:54] statically generated website would be [09:57] kind of easier, like cheaper to host, [09:59] easier to just kind of edit, like fewer [10:02] layers of logging in and permissions and [10:05] things. Um, and we just kind of use a [10:07] regular kind of GitHub pull request type [10:09] workflow. Maybe it's still kind of in [10:11] progress, but um the the main update is [10:14] that uh the the site that I sort of sent [10:17] a screenshot of in the the WG website [10:19] channel, I was able to get it on just [10:22] quickly generated on GitHub pages and so [10:25] people can kind of browse around. It's [10:27] very not the styling still needs to be [10:30] updated to like better match the current [10:32] chaos website. Uh, and I think I all the [10:35] content is moved over, but it's all very [10:37] much not like laid out for like I still [10:40] need to kind of figure out the [10:41] formatting of the pages. There's a lot [10:42] of work to be done and I think there's [10:44] definitely a lot of room for if anyone's [10:47] interested in in helping contribute like [10:50] there's a lot a lot to happen. Um, so I [10:53] imagine that that'll probably just keep [10:54] keep moving along especially as people [10:56] come and help. And I imagine that will [10:57] also probably get adopted to some extent [10:59] by the infrastructure committee. [11:11] Hi Adrian. [11:13] Um, [11:15] uh, so I noticed that we this present um [11:21] website we've changed the the color the [11:24] palette and um can't see the logo. [11:28] Is that deliberate? [11:30] >> No, no, that's just this was mostly just [11:33] me kind of throwing stuff together. The [11:35] my the main thing I sort of migrated out [11:37] of WordPress was the content. Everything [11:39] else around that is still like this [11:42] isn't meant to be like [11:44] a done thing. It's just a sort of a [11:46] progress update and just saying hey like [11:49] as you can see there's a lot of things [11:50] that need work on. Um continuing to seek [11:53] contributors um yeah this is this is [11:56] very far from being final. [12:00] >> Okay. So um where where's the report? [12:04] >> Uh it is um it's on chaos. I think the [12:07] repository is just it's the you could [12:09] kind of get to the repository from the [12:10] URL, but I will put the link as well. [12:14] Um, it's basically just [12:16] github.com/taos/hugo. [12:18] I think [12:20] it's a really I just basically threw [12:22] together a a random name just for for [12:24] testing. Like we can move it around. We [12:26] can kind of do whatever with it. Um [12:32] >> Okay. Um I'll check it out. [12:35] Do we have like um issues created [12:38] already that someone can just pick up? [12:40] I'm asking because um I could then refer [12:43] um care of Africa developers to it. [12:48] >> Not not yet. [12:50] >> Oh, okay. [12:51] >> Yeah. No, there's not any issues yet [12:53] just because this is something I've been [12:55] throwing together through various with [12:56] various bits of like offline train time [13:00] like when I can't when I can't really [13:01] work on other things. Um, so I I can try [13:05] and do that. U, I think there's still, [13:07] yeah, it does still need, I think, a lot [13:08] of attention from especially kind of web [13:10] developers. Um, I think eventually I do [13:13] also want to maybe start to mimic more [13:16] of what like the Fedora website's doing [13:17] where they have a a sort of the main [13:19] website repo that's the very oriented [13:21] for web developers. And then there's a [13:23] separate sort of content repo that's [13:25] managed with a more graphical content [13:27] management system that uses sort of git [13:30] behind the scenes. [13:32] So that if people if if people want to [13:34] just go and update a blog post or add a [13:36] new blog post or do just do content only [13:39] changes though that can be done in a [13:42] much more user friendly way without [13:44] having to have people go in and be [13:46] deeply digging into the styles and the [13:48] themes and all the things that really [13:50] don't need to change from page to page. [13:52] Um so that's kind of hopefully where I [13:54] hope to go with it. But I I think I'm [13:58] very low on available time. So if [14:00] there's other developers who want to get [14:01] involved, I'm happy to kind of bring [14:03] people up to speed with this and and [14:05] maybe hand it off to someone else to to [14:07] sort of be responsible for or kind of [14:10] help lead if people are willing to lead [14:11] like and whatever works really. [14:14] >> I get that. So I'm just saying that it [14:16] will be easier for contributors if you [14:18] can have issues. Yeah. [14:20] >> So they know what to pick up to be [14:22] faster than also. [14:26] >> Yeah, I can try I can try and get some [14:27] of those up. [14:29] Welcome. [14:41] Okay. Um, I don't know. That's we've [14:44] kind of hit the end of the agenda. So, I [14:46] don't know if um anybody has any other [14:50] topics or anything else. [15:17] Well, if there is nothing else, I think [15:19] we probably can just have a short [15:22] meeting for today. Um, [15:25] don't know if there's any just trying to [15:28] Yeah, if there's anybody else who would [15:29] like to volunteer for like pretty much [15:33] doing what I'm doing right now, which is [15:34] facilitating the meeting. Um there's a [15:38] signup sheet on the working group [15:40] minutes. Um it would be great for other [15:43] people to um start. Yeah, it's not [15:47] anything crazy. You just log in and um [15:51] follow through the agenda. There's a [15:52] facilitation guide and a signup sheet. [15:55] So that is that's all I got. [16:03] Easy peasy. [16:07] Sweet. Well, it was great to see [16:09] everybody and um we'll talk soon. [16:13] >> Thanks, Cali. [16:14] >> Take care. [16:15] >> Bye, everybody. Leaving still.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Weekly Community Call, April 21, 2026.md|CHAOSS Weekly Community Call, April 21, 2026 by YouTube]] ## Highlights - anything else on this specific topic before we move on? >> No, I've got my note. We'll uh hand that repo off like a PR and link it on the community repository issues and get full feedback. Perfect. >> Done. Thank you all. I'm going to go enjoy the sunshine. Very well. >> Um uh the next thing on the agenda just going to mention that the Slack is continuing on and is being paid for by ([View Highlight](https://read.readwise.io/read/01kq2r0ndkm0fd2vgj4kh17qpz)) - Tags: 👻 ai highlighted - >> Okay. Um I'll check it out. Do we have like um issues created already that someone can just pick up? I'm asking because um I could then refer um care of Africa developers to it. >> Not not yet. >> Oh, okay. >> Yeah. No, there's not any issues yet just because this is something I've been throwing together through various with various bits of like offline train time ([View Highlight](https://read.readwise.io/read/01kq2r0nenydn0gj2e10nw6q9q)) - Tags: 👻 ai highlighted