CHAOSS Africa Technical Writers WG, Jan 14, 2026

CHAOSS Africa Technical Writers WG, Jan 14, 2026 ![rw-book-cover](https://img.youtube.com/vi/qt3TK1clWsc/maxresdefault.jpg) 🔗 **Source:** [CHAOSS Africa Technical Writers WG, Jan 14, 2026](https://www.youtube.com/watch?v=qt3TK1clWsc) > [!note]+ Document Notes > tags: #technical-writing #chaoss #open-source #community-building #documentation #africa > author: CHAOSS Africa Technical Writers WG > source: YouTube > reference: https://www.youtube.com/watch?v=qt3TK1clWsc > date created: 2026-01-14 15:30 > > # 🏷️ Title: CHAOSS Africa Technical Writers Working Group January 2026 Meeting >  ## 🧰 Action Inbox - [H1] Create resource bank for technical writers — discussed at 15:45 #technical-writing - [H2] Plan hands-on workshop for October 2026 — proposed at 14:20 #community-building - [H3] Document 2026 goals in community channel — action at 17:30 #planning ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [CHAOSS Project](https://chaoss.community) - [Linux Foundation](https://linuxfoundation.org) ## 📝 Summary - What happened: January 2026 meeting of CHAOSS Africa Technical Writers WG with new member onboarding and 2026 planning - Why it matters: Demonstrates community growth and strategic planning for open source documentation initiatives - Key stakeholders: Technical writers, open source contributors, African tech community - Risks and tradeoffs: Need to balance ambitious goals with volunteer capacity - Bottom line: Active community planning resource development and hands-on workshops for 2026 ## 📖 Main Content The CHAOSS Africa Technical Writers Working Group held their first meeting of 2026, welcoming new member Kate Aurika and conducting strategic planning for the year. CHAOSS (Community Health Analytics for Open Source Software) operates under the Linux Foundation to create metrics and guides for evaluating community and project health in open source software. The technical writers focus group specifically works to improve documentation experiences across repositories and working groups while providing educational opportunities for members. The meeting highlighted the group's 2025 achievements, including a successful workshop with over 170 registrants from seven countries and partnerships with organizations like Wikipedia and Write the Docs. The discussion emphasized that open source contribution doesn't require coding skills, promoting documentation and other non-technical contributions. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/qt3TK1clWsc?t=0) — [H1] Meeting startup and live notifications - Key idea: Team coordinates going live and waiting for attendees - Evidence: "Please can you drop a text that we are live and ready?" #### ⏱️ [03:15](https://youtu.be/qt3TK1clWsc?t=195) — [H2] New member Kate joins the call - Key idea: Kate Aurika joins as new member, initially quiet but welcomed - Evidence: "Good morning. I've been here since I've just been keeping quiet cuz I don't know what to say" #### ⏱️ [05:30](https://youtu.be/qt3TK1clWsc?t=330) — [H1] New member introduction - Kate Aurika - Key idea: Multi-skilled professional with computer science background - Evidence: "I'm a product designer, sometimes a product manager, sometimes an HR... I do a lot of plenty things" #### ⏱️ [08:45](https://youtu.be/qt3TK1clWsc?t=525) — [H1] CHAOSS project explanation by Harmony - Key idea: CHAOSS creates metrics for evaluating open source community health - Evidence: "chaos is a project under the Linux Foundation and the focus of this project or this community is basically under community health analytics of open source software" #### ⏱️ [10:20](https://youtu.be/qt3TK1clWsc?t=620) — [H2] Technical writers focus group mission - Key idea: Group improves documentation experience and provides non-code contribution pathways - Evidence: "We try to ensure or improve on the experience of technical documentation across various repositories" #### ⏱️ [12:15](https://youtu.be/qt3TK1clWsc?t=735) — [H1] 2025 achievements recap - Key idea: Successful workshop with 170+ registrants from seven countries - Evidence: "the workshop where we had over a 170 person register for the workshop and it cut across seven countries" #### ⏱️ [13:45](https://youtu.be/qt3TK1clWsc?t=825) — [H2] Additional 2025 accomplishments - Key idea: Wikipedia collaboration and partnership with Write the Docs - Evidence: "We contributed together with Wikipedia on updating African opensource scholars... We also had event partnership with ride the docks" #### ⏱️ [14:20](https://youtu.be/qt3TK1clWsc?t=860) — [H1] 2026 planning begins - hands-on workshop proposal - Key idea: Mio proposes hands-on experience addition to workshops - Evidence: "I'm looking forward to that where we have to create like a platform where they can be able to do use their hands" #### ⏱️ [15:45](https://youtu.be/qt3TK1clWsc?t=945) — [H1] Resource bank proposal - Key idea: Harmony proposes creating technical writers resource repository - Evidence: "we should properly create a resource bank a technical writers resource bank resource bank basically" #### ⏱️ [16:30](https://youtu.be/qt3TK1clWsc?t=990) — [H2] Kate's learning goals - Key idea: Kate seeks learning opportunities in technical writing - Evidence: "I can have a place where I can be able to like learn... technical writing, I've never done that before" #### ⏱️ [17:30](https://youtu.be/qt3TK1clWsc?t=1050) — [H2] Meeting wrap-up and next steps - Key idea: Goals will be documented in community channel for broader input - Evidence: "I'm going to drop this in the channel so more people can actually add things on it" ## 📚 References - [CHAOSS Community](https://chaoss.community) - [Linux Foundation](https://linuxfoundation.org) - [Write the Docs](https://www.writethedocs.org/) - [Wikipedia](https://wikipedia.org) ## 🗣️ Paraphrase - CHAOSS Africa Technical Writers Working Group welcomed new member Kate Aurika and reviewed successful 2025 initiatives including workshops with international reach - The group plans to create educational resources and hands-on experiences for technical writers while maintaining focus on improving open source documentation - Community emphasizes volunteer-based learning environment where non-coding contributors can meaningfully participate in open source projects ## 📰 Newsletter The CHAOSS Africa Technical Writers Working Group kicked off 2026 with exciting plans for resource development and community growth! 🚀 **Key Highlights:** - Welcomed new member Kate Aurika, showcasing our inclusive onboarding process - Celebrated 2025 achievements including 170+ workshop registrants across seven African countries - Planning comprehensive resource bank for technical writing education **Practical Benefits:** This demonstrates how open source communities can create structured pathways for non-technical contributors while building sustainable documentation practices. **Get Involved:** - Join CHAOSS community meetings every other Thursday - Contribute to documentation improvements across open source projects - Access upcoming resource bank for technical writing skills Resources: [CHAOSS Community](https://chaoss.community), [Technical Writing Resources](https://learn.wordpress.org/), [Open Source Contribution Guide](https://developer.wordpress.org/) ## ✅ Action Items #### Community - **Resource Development**: Create comprehensive technical writers resource bank with learning pathways, articles, and videos - **Workshop Planning**: Design hands-on technical writing workshop for October 2026 with practical PR creation activities - **Goal Documentation**: Collect 2026 objectives from broader community through channel discussions - **Onboarding**: Develop structured introduction process for new members like Kate's experience #### Documentation - **Article Writing**: Increase article and guide production across working groups - **Documentation Review**: Establish systematic review process for repository documentation improvements - **Knowledge Base**: Build searchable resource repository for African technical writers #### Events - **CHAOSSCon 2026**: Plan technical writers track or session for annual conference - **Monthly Sessions**: Continue educational sessions that reached 2000+ participants in 2025 - **Partnership Development**: Expand collaborations with organizations like Write the Docs and Wikipedia ## 🧪 Hypotheses - Creating structured resource banks increases technical writing participation in open source projects - Hands-on workshops with practical activities improve skill retention over lecture-based formats - African-focused technical writing communities can scale internationally while maintaining local relevance - Volunteer-driven documentation initiatives can achieve professional-quality outcomes with proper coordination ### 📊 Methodology - Survey workshop participants before and after hands-on activities to measure skill acquisition - Track pull request submissions and documentation contributions from resource bank users - Monitor community growth metrics across African countries and internationally - Analyze engagement patterns in volunteer vs. paid documentation initiatives ### ❓ Questions - How can the resource bank best serve both beginners like Kate and experienced contributors? - What specific hands-on activities would provide the most valuable learning experience? - How can the group maintain momentum and volunteer engagement throughout 2026? ### 🔮 Future Research - Investigate scalability models for technical writing education in emerging tech markets - Explore integration opportunities between CHAOSS metrics and documentation quality assessment - Study effective volunteer retention strategies in open source documentation communities ### 💡 Implications - **Practice**: Demonstrates need for structured onboarding and educational pathways in open source communities - **Policy**: Shows importance of inclusive contribution models beyond coding - **Education**: Highlights demand for practical, hands-on technical writing instruction - **Community**: Illustrates successful volunteer-driven international collaboration model ### 🧠 Learning Styles Assessment Reading level estimate: Grade 8-10 #### 👀 Visual learners - **Present**: Screen sharing during meeting, written meeting minutes - **Improve**: Create visual roadmaps for 2026 goals, infographics for resource bank #### 🔊 Aural learners - **Present**: Live discussion format, recorded meeting - **Improve**: Podcast series on technical writing, audio versions of resources #### 🗣️ Verbal learners - **Present**: Clear explanations of CHAOSS mission, interactive Q&A - **Improve**: Glossary of technical terms, storytelling examples in documentation #### 🧩 Kinesthetic learners - **Present**: Planned hands-on workshops for 2026 - **Improve**: Interactive documentation exercises, live PR creation sessions #### 🧠 Logical learners - **Present**: Structured agenda, clear goal-setting process - **Improve**: Metrics dashboard for community growth, systematic resource organization #### 🧑‍🤝‍🧑 Social learners - **Present**: Community meeting format, collaborative planning - **Improve**: Peer mentoring programs, group documentation projects #### 🧘‍♀️ Solitary learners - **Present**: Self-paced resource access mentioned - **Improve**: Individual learning paths, self-assessment tools #### 🌿 Naturalistic learners - **Present**: African community focus, regional connections - **Improve**: Local ecosystem examples, cultural context in documentation ### 📊 Accessibility Assessment #### Screen reader semantics - **Present**: Clear verbal introductions, structured agenda - **Improve**: Ensure meeting minutes have proper heading structure #### Keyboard navigation - **Present**: Standard Zoom meeting controls - **Improve**: Accessible resource bank interface design #### Contrast and readability - **Present**: Clear audio quality in recording - **Improve**: High contrast documentation templates #### Text resizing and reflow - **Present**: Standard video player controls - **Improve**: Responsive design for resource bank #### Media and captions - **Present**: Audio recording available - **Improve**: Add captions to meeting recordings, provide transcripts #### Forms and interactions - **Present**: Simple meeting participation format - **Improve**: Accessible feedback forms for workshops ### 🌍 DEIB Assessment #### Cultural breadth - **Present**: African focus with seven-country representation, multiple languages implied - **Improve**: Document language preferences, include more regional examples #### Inclusive language - **Present**: Welcoming tone for new members, patient explanation of concepts - **Improve**: Create style guide for inclusive technical writing #### Neurodiversity support - **Present**: Patient onboarding approach, multiple ways to participate - **Improve**: Provide meeting agendas in advance, offer alternative participation formats #### Representation - **Present**: Female leadership (Harmony), diverse professional backgrounds - **Improve**: Highlight diverse contributor stories in resources #### Psychological safety - **Present**: Encouraging response to Kate's uncertainty, emphasis on learning - **Improve**: Formal community guidelines, clear escalation processes ### ✅ Logical Validity #### Strong reasoning - **Deductive strength**: Clear mission from CHAOSS → technical writing focus group goals - **Inductive strength**: 2025 success patterns → 2026 planning expansion - **Causal reasoning**: Resource gaps identified → resource bank solution proposed - **Analogical strength**: Previous workshop success → hands-on format adoption #### Fallacies - **Appeal to popularity**: "Over 170 registrants" used as success metric without quality assessment - **Planning fallacy**: Ambitious 2026 goals without detailed capacity planning #### Tone of voice - **Overall tone**: Welcoming, collaborative, educational with emphasis on volunteer learning and community building ### 🛡️ DARVO Analysis - **Deny**: No defensive patterns observed - **Attack**: No attacking behavior present - **Reverse victim/offender**: No victim/offender dynamics evident - **Emotional cues**: Positive, welcoming atmosphere with enthusiasm for growth and learning ## 🎯 Conclusion The CHAOSS Africa Technical Writers Working Group demonstrates a thriving volunteer community focused on documentation improvement and education in open source. Their 2026 planning session reveals strategic thinking around resource development, hands-on learning, and inclusive community building. The successful onboarding of new member Kate Aurika showcases their welcoming approach and commitment to skill development regardless of prior experience. Key next steps include creating the proposed resource bank, planning hands-on workshops, and documenting community goals for broader input. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Open source communities succeed through structured educational pathways > [!quote] CHAOSS Africa Technical Writers WG Meeting by Harmony via YouTube. Published 2026-01-14. Accessed 2026-01-14. > "We should properly create a resource bank a technical writers resource bank basically somewhere that people can actually go and get started." Demonstrates demand for systematic learning resources in volunteer technical communities. [view highlight](https://youtu.be/qt3TK1clWsc?t=945) #xref #articleseed ID:rw_chaoss_resource_bank ### [H2] Volunteer communities require inclusive onboarding for non-technical contributors > [!quote] CHAOSS Africa Technical Writers WG Meeting > "There's this stereotype that if you're going to contribute to open source you have to be extremely technical inclined which means you have to write codes." Challenges common misconceptions about open source contribution requirements. [view highlight](https://youtu.be/qt3TK1clWsc?t=620) #xref ID:rw_chaoss_inclusivity --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Documentation communities scale through hands-on learning experiences - Applies to technical writing education in open source contexts - Referenced at 14:20 in meeting discussion - Links: [[Community-Building]] [[Technical-Documentation]] #### [Z2] African tech communities demonstrate international collaboration potential - Applies to regional open source community development - Referenced throughout meeting with seven-country workshop example - Links: [[Global-Communities]] [[Open-Source-Education]] --- ### ✏️ Fleeting Queue - [F1] Research CHAOSS metrics for documentation quality assessment — meeting context #fleeting #inbox - [F2] Investigate Write the Docs partnership models — mentioned collaboration #fleeting #inbox - [F3] Document successful volunteer onboarding --- ## Full Transcript [00:00] Please can you drop a text that we are [00:03] live and ready? That's how they say live [00:07] ready. We're active. [00:12] >> I can Yeah. I think life is more is a [00:15] common word that is being used. [00:18] >> Okay. [00:19] >> That scenario. [00:21] >> Okay. I think we can use that. [00:40] So, I've dropped the comment. You guys [00:41] should drop the comment. Are you guys [00:43] already on the call? You guys are [00:44] waiting for people. So, we'll get more [00:45] people here on the call. [00:53] >> Okay, I'll do that. [01:20] Trying to bring up our [01:23] meeting it. [01:36] Let me bring about me 10 minutes. [01:40] Okay. Okay. Okay. Okay. Okay. Okay. [01:44] Okay. Okay. [01:55] Are you guys still here? [01:58] Looks like we have a new member. Kate, [02:01] >> good afternoon. Good morning. [02:04] >> Good morning. I've been here since I've [02:07] been here since I've just been keeping [02:09] quiet cuz I don't know what to say. [02:11] >> Please don't [02:12] >> Good morning. [02:14] >> Please don't be keeping quiet, please. [02:16] We need you here. [02:18] I'm here. [02:25] >> Hi Kate, welcome. [02:28] >> Hi Moto. We meet again. [02:31] >> Yeah, [02:31] >> you guys have met before [02:34] >> like where where did we meet? Oh, [02:38] >> when you again call [02:42] >> Oh, newcomer. Oh. Oh, that was [02:43] yesterday. Okay. Yeah. Yeah. Yeah. [02:45] >> Yesterday. That was [02:47] >> Oh yes, [02:50] >> because we had one yesterday too. We not [02:52] there. [02:53] >> Yeah, I couldn't join yesterday. Even [02:55] today, I think they had one today. Not [02:57] sure. [02:58] >> Yeah, yesterday newcomer. Am I supposed [03:02] to join like all of [03:03] >> No, no, no. It's not every time. It's [03:05] just maybe where you have questions and [03:08] join. [03:09] >> Or if you want to assist, there's no [03:11] harm in assisting too. Yeah, probably [03:14] you want to assist or you just want to [03:16] like engage and [03:18] >> Okay, now I know that. [03:21] >> Yeah, [03:22] >> I'm actually looking for a meeting [03:24] minutes. I know I have that document [03:26] pinned. I just cannot find it right now. [03:31] >> Okay, I'm joining this. I'm switching [03:34] this to my laptop. [03:38] >> This meeting is [03:40] okay. actually. [03:44] >> Okay, I finally found it. Yay, I found [03:46] it. [03:49] So, I'll be sharing the link. I expect [03:51] you guys to please this. What's today's [03:54] date? What's today's date? What's [03:56] today's date? What's today's date? [03:58] >> Today is 14. [04:00] >> Okay, today is 14. First things first, [04:04] happy new year. [04:07] Happy New Year to you [04:09] >> everyone. [04:12] Same to you. [04:18] Yes. [04:19] >> I wonder why Zoom is not having those [04:21] sounds. [04:22] >> They should actually. I don't know why. [04:28] >> Not like Discord where we have drones [04:29] and whatsoever. I just [04:32] >> there sounds on Discord. [04:35] >> Yeah, there are sounds on Discord. [04:39] So I've I'm sharing the link now. So our [04:42] first question is going to be what was [04:45] your favorite moment in the holidays? [04:51] What was [05:01] so let me share. [05:03] Please do well to add your name. The [05:06] all of the little things and the big [05:10] things [05:19] you know I'm finding that not [05:21] okay I've shared it. So welcome back. I [05:25] nearly said welcome back to Chaos C. [05:29] So yeah, welcome back everyone and it's [05:32] a pleasure to have you here back in the [05:34] technical writers focus group and we're [05:36] excited we have a new member in the [05:39] house. [05:40] >> Hi Kate, please do introduce yourself. [05:43] I'm just going to give you a clap. [05:45] >> No, you buy me a car. [05:48] >> We can we can actually [05:49] >> No worries. [05:50] >> But we can't do that. [05:52] >> We'll do it on GitHub. Just create an [05:54] >> Just buy me Just buy me a BMW and that [05:58] works. I'm not doing that. [06:01] >> Oh god, she wants a BMW. That's nice. [06:04] >> A BMW M5 [06:06] or an X6 series or the X series. Any of [06:09] them. Either green color. Emarrage green [06:12] or black. Any of them. [06:15] >> I'm trying to imagine your face, but [06:17] that's fine. Please [06:20] introduce yourself. We'll do as much as [06:21] we can to ensure we get you BMW. We're [06:23] not promising. [06:25] So, but then [06:27] >> but then please do do it to introduce [06:29] yourself [06:30] >> and then while you're introducing [06:32] yourself, you can take like a minute or [06:34] two to fill in the minute the meeting [06:36] minutes. Yeah. [06:39] >> Okay. Um, who am I here? That's how they [06:43] introduce themselves. This feels like a [06:45] talking stage. Jesus Christ. [06:49] >> Sorry. [06:49] >> The meeting is recorded that way though. [06:52] Yeah, please do introduce yourself. [06:56] >> So, um my name is Isakit Aurika. [07:01] >> Okay. [07:02] >> What is um [07:06] I'm a graduate of University of [07:07] Portacott. I study computer science. [07:11] I'm a product designer, [07:13] sometimes a product manager, sometimes [07:15] an HR. I don't even know what I do [07:17] sometimes. Okay. No, I'm serious now. a [07:20] virtual assistant and currently I am a [07:28] illustration designer. [07:30] Um, can you still hear me? [07:33] >> Yes, we can. Loud and clear. [07:35] >> The thing is I do a lot of plenty [07:36] things. Just plug me in. I promise you. [07:38] I just know how to navigate. Provided [07:41] you explain and you are willing to allow [07:43] me ask questions then. [07:47] >> Okay. So before I tell you where we are [07:50] here in chaos and chaos technical [07:52] writers is there anything okay I'll tell [07:54] you first and then allow you to you know [07:57] tell us what you're looking for where we [07:58] can help where we can come in stuff like [08:01] that but then my name is Harmony and I [08:04] currently need the technical writers [08:06] focus group and the lady beside you [08:10] beautiful lady is Mioayo she's one of [08:13] our focus group members and she's [08:14] extremely very much active what I do for [08:17] work is aside technical documentation [08:20] I'm also a project and product manager [08:22] and I do a couple of other stuff too [08:24] just like you and par venture not par [08:28] venture we also stay in the same city [08:30] and that's good you're welcome [08:32] >> which do you stay [08:35] >> but then [08:36] >> oh my former city [08:38] >> okay your former city yeah I guess [08:40] you're in Lagos now [08:43] >> so so like welcome welcome to chaos so [08:47] what Are we in chaos? So chaos is a [08:50] project under the Linux Foundation and [08:52] the focus of this project or this [08:54] community is basically under community [08:57] health analytics of open source software [09:01] right and then that's also the meaning [09:04] of our acronym. The core thing we do [09:06] here is create metrics and also prepare [09:09] various guides and also systems that [09:12] helps communities like chaos and also [09:15] opensource software to enable them [09:17] evaluate community health and project [09:19] health. We are open source that means [09:22] that everybody 99% of everybody you [09:26] would find in the community is here to [09:28] learn and also volunteer. We are not [09:31] paid for the work we do. And one of the [09:35] way we get fulfillment is we learn. So [09:38] you're not restricted to a certain [09:40] group, focus group, working group or [09:42] even chapter though apparently you would [09:45] be under the chaos African chapter and [09:47] they have their meetings. We do have our [09:49] meetings every other Thursday by 3 p.m. [09:53] I think 3 p.m. or 4 p.m. However, but [09:56] here in the technical writers focus [09:58] focus group what we do majorly is try to [10:01] ensure or improve on the experience of [10:03] technical documentation across various [10:06] repositories and also across various [10:09] working groups. Additionally, we help to [10:11] write articles and a couple of other [10:14] things. Now for our focus group members, [10:16] we try to see as much as possible where [10:19] we can help out on regards various forms [10:22] of education where they need like a [10:25] helping hand to either better their [10:27] career, they need somebody to be able to [10:28] put them through on certain things. We [10:31] could always reach out to somebody that [10:33] is an expert in that field to help you [10:36] out on that regard. We also try to host [10:39] spaces and also workshop where we [10:43] educate people about open source [10:44] generally and also on documentation and [10:47] also other ways that you can actually [10:49] contribute to open source that are known [10:52] code. [10:54] So there's this stereotype that if [10:56] you're going to contribute to open [10:57] source you have to be extremely [10:59] technical inclined which means you have [11:01] to write codes develop website and stuff [11:03] like that. You don't have to do them [11:06] yet. [11:07] That's the whole point. So, welcome back [11:10] again. I don't know if you have any [11:11] question. I'm open to give answers to [11:13] them. [11:17] Do you have any question? [11:18] >> No, no, I don't want. [11:20] >> Okay. So, the one thing that I would ask [11:22] after this is basically how or what is [11:26] like your objective? So, we could see [11:28] how we could come in to help you [11:30] facilitate our objective, right? [11:33] Especially now that you're here in [11:36] in our focus group meeting. [11:39] >> What if I said that your focus group [11:42] meeting I joined was because I missed my [11:44] own meeting. [11:45] >> Sorry. [11:46] >> That's good. [11:48] >> No, there's no design. I was supposed to [11:52] be in design group meeting by 11, but I [11:55] was trying to sort out NYC [11:58] and [12:00] >> Yeah. Yeah. [12:00] >> Yeah, I get it. So, but it's it's [12:03] amazing that you're here. [12:05] Right. And then you also learn about us [12:08] while you still you can still work with [12:10] the design team. We work with them a lot [12:12] of time. I think everybody works with [12:13] the designs and they have been doing a [12:14] lot of work and a lot of amazing stuff. [12:17] Kinsley is the lead literally. [12:22] >> Okay. [12:23] >> Yeah. So our our agenda let me share my [12:26] screen. [12:29] Our agenda for today is very much [12:32] simple. [12:34] So say that she ate rice and met. [12:38] So recap of 2025 and see if we can begin [12:43] planning [12:46] our goals for this year. [12:53] So recap of change, we did a lot of [12:55] amazing stuff. One of which, the most [12:58] notable one is the workshop where we had [13:01] over a 170 person register for the [13:05] workshop and it cut across seven [13:08] countries and it was a very very lively [13:13] session that we did in a day and we had [13:15] at least 50 people 40 to 50 people that [13:18] joined the session live on Zoom. So [13:22] recap of 2025 was extremely amazing. [13:25] Wow. And we also did things like we [13:28] contributed together with Wikipedia on [13:32] updating [13:34] African opensource scholars or [13:36] enthusiasts on the wiki page on [13:39] Wikipedia basically. We also had event [13:42] partnership with ride the docks. We also [13:47] we also had monthly session that ran up [13:49] to or over 2,000 people that tuned in. [13:53] So it was actually a very very pleasant [13:56] moment. We had like a lovely time in [13:59] last year 2025. So aside this lovely [14:03] time, I don't want to ask what's like a [14:06] f moment [14:08] since Kate wasn't here. [14:12] Are you with us? [14:17] >> But I didn't get the last question. You [14:19] said [14:19] >> like your favorite moment in 2025 like [14:22] things we did and things we would have [14:24] done better. [14:26] >> Yeah, I think my favorite moment was [14:28] just me staying at home eating rice. [14:32] That's all. Eating rice and meat. [14:35] >> So I meant for the focus group for you. [14:40] >> That's all like me just relaxing. [14:44] >> Yeah, I heard you. No, I mean favorite [14:47] moment in the stuff like favorite things [14:49] we did as a focus group in [14:52] the favorite moment was just the time [14:55] where we had [14:58] shop and that was around October during [15:01] the October first um [15:04] uh event. Yeah. [15:08] >> Okay. That's one and also when we had [15:11] chaos. [15:12] >> Chaos in August. [15:14] >> Yes. [15:14] >> Yeah. Those are my favorite. [15:20] >> Thank you. I think Chaoscon was actually [15:22] very much lovely because I also had met [15:25] people that I've not met before. Also [15:27] get to like share hugs also shook hands [15:30] and you know share a meal even if I was [15:34] sick. But yeah share share a meal as [15:36] well. So it was very very good. [15:38] Lovely. But now the very big question [15:40] which is not going to end in this [15:42] meeting. I also want to put it in the [15:44] channel is [15:46] I would want us to plan our 2025 [15:49] together especially the goals just like [15:51] we did last year. So we're going to also [15:53] come together to achieve them as a focus [15:56] group as well like everybody's hands [15:58] together and stuff like that. It's just [16:00] going to be very very simple. What would [16:03] you want us to do this year? Or what do [16:05] you think we would have done last year [16:06] that we can move to doing this year? [16:10] So, [16:12] and now that Kate is here, Kate has [16:14] heard everything about us. She can also [16:16] tell us what she thinks we should also [16:18] add. Probably do this here as well. So, [16:21] I'm dropping into the house. Mio, Kate, [16:25] and me, Harmony. [16:33] I think for my hand I think we just have [16:36] to have [16:40] okay for last year when we had the [16:41] workshop it was October 1st we didn't [16:44] have like hands on we didn't have [16:48] like where [16:50] um the members are going to like do [16:53] something with their own hand I'm [16:55] thinking I'm looking forward to that [16:56] where we have to create like a platform [16:59] where they can be able to do use their [17:01] hands whether to actually create like PR [17:04] concerning documents or something. So, [17:07] but I don't want it to just be like [17:08] workshop like that one. We could have [17:11] something like that workshop that's [17:14] before the October first. Then during [17:16] the October Fest, we could have like I [17:18] don't know probably a repo where they [17:21] have to where where they have to walk or [17:24] something. Yeah. Just hands-on [17:26] experience. [17:26] >> Yeah. from my end. Then I'm looking [17:29] forward to Chaos Con 2026. Obviously, [17:33] we're having one, so [17:35] I'm looking forward to that. [17:37] >> Do you think we should do something in [17:39] Chaos Con 2026? [17:42] >> Yeah, but I don't really have an idea [17:45] yet. [17:46] I don't know. [17:49] I don't really have an idea yet, but I [17:51] think we should. [17:54] >> Okay. So for me I think we should [17:55] properly create a resource bank a [17:58] technical writers resource bank [18:07] resource bank basically somewhere that [18:10] people can actually you know go and get [18:13] started with articles videos stuff like [18:16] that [18:19] then I also think Uh, [18:24] I also think that um [18:27] we should [18:29] we should write more articles and [18:32] guides. [18:49] I think we should write more articles [18:50] and guides too as well. [19:08] So I don't know any other thing. [19:15] Kate, do you have anything at heart? [19:20] >> Can you hear me? [19:22] >> Yes, I can hear you. [19:24] >> Actually, nothing much at the moment [19:26] because I don't really like know [19:29] anything like that. But [19:34] if I can have a place where I can be [19:36] able to like learn, [19:38] you get like learn what to do because [19:40] technical writing, I've never done that [19:42] before. So [19:45] place I can learn to do technical wing [19:49] that works fine. And yes, everybody have [19:52] to be patient with me cuz it's just like [19:54] telling me to learn how to drive a car [19:56] >> when I've never se never se before. [20:00] >> So that was one. Then secondly, um yeah, [20:05] I would love to volunteer for every [20:09] chaos conf conference. I want to do 500 [20:12] this year up and active or how it is to [20:15] see the English. Yes. [20:17] >> Yeah, I'm very much active. [20:19] >> So that's that's that I don't really [20:22] have [20:24] much to say at the moment. [20:27] I think when I become more acquainted to [20:30] everything, [20:31] >> yeah, I'll contribute [20:35] clearly. [20:38] >> Okay, that's good. Any [20:42] other thing from anyone? So the resource [20:45] bank that we're going to be creating [20:46] would allow people just like you and [20:48] also me that want to improve in [20:50] technical writing or learn have like a [20:53] clear pathway that would lead them, you [20:56] know, to get things done. [21:05] Okay, that's fine. [21:10] But then any other thing from anyone? I [21:12] think it's already 12:30. But do I have [21:15] any other thing? I think I'll put this [21:26] uh nothing on my hand. [21:45] Okay. In absence to anything, I'm going [21:49] to drop this in the channel so more [21:50] people can actually add things on it. [21:54] in absence to anything. I think we can [21:55] have an amazing day and then come back [21:59] every the next other Wednesday. [22:04] But then really k is like really a [22:06] pleasure for you to join us. I know you [22:08] wanted to join the design focus group [22:10] meetings but yeah it's actually very [22:12] huge pleasure for you to join us. [22:16] >> Thank you so much. [22:20] >> Thank you so much everyone having me [22:22] here. [22:23] You're welcome. [22:24] >> I think about joining technical writers, [22:27] but let me let me pray and think about [22:29] it. [22:30] >> Okay, that would be good [22:31] >> because it seems like a lot. [22:34] >> No, it's not a lot actually. But yeah, [22:37] >> people [22:39] >> No, we don't. [22:42] >> So, what do you do? [22:44] >> We write articles. We review [22:47] documentations. We help improve them. [22:50] Basically, that's what we do. [22:53] So, I don't need to do [22:55] C minus. [22:58] >> No, you're not. I think as much as [23:00] you're writing articles, you don't have [23:02] to write the technical ones. You can [23:04] decide to just write a blog post [23:07] and that's still fine. [23:10] >> Let me think if my writing skill is [23:12] still active. I used to write when I was [23:14] small. I loved writing. [23:17] I just got tired. I didn't get tired of [23:20] it though. [23:27] Okay, thank you very much everyone. [23:29] Thank you so much Kit. So we'll be [23:31] seeing you in the next other Wednesday. [23:34] Bye everyone.  📄 **Full text:** ![[Full Document Contents/Articles/CHAOSS Africa Technical Writers WG, Jan 14, 2026.md|CHAOSS Africa Technical Writers WG, Jan 14, 2026 by YouTube]] ## Highlights - >> Okay, I'm joining this. I'm switching this to my laptop. >> This meeting is okay. actually. >> Okay, I finally found it. Yay, I found it. So, I'll be sharing the link. I expect you guys to please this. What's today's date? What's today's date? What's today's date? What's today's date? >> Today is 14. ([View Highlight](https://read.readwise.io/read/01kp9kcan3zf4905pth0dd06np)) - Tags: 👻 ai highlighted - to write codes develop website and stuff like that. You don't have to do them yet. That's the whole point. So, welcome back again. I don't know if you have any question. I'm open to give answers to them. Do you have any question? >> No, no, I don't want. >> Okay. So, the one thing that I would ask after this is basically how or what is like your objective? So, we could see how we could come in to help you ([View Highlight](https://read.readwise.io/read/01kp9kcapa8zw5s4vbrs1qxt2k)) - Tags: 👻 ai highlighted - facilitate our objective, right? Especially now that you're here in in our focus group meeting. >> What if I said that your focus group meeting I joined was because I missed my own meeting. >> Sorry. >> That's good. >> No, there's no design. I was supposed to be in design group meeting by 11, but I was trying to sort out NYC and ([View Highlight](https://read.readwise.io/read/01kp9kcaq4hwebezytkjrwkfz4)) - Tags: 👻 ai highlighted - everything, >> yeah, I'll contribute clearly. >> Okay, that's good. Any other thing from anyone? So the resource bank that we're going to be creating would allow people just like you and also me that want to improve in technical writing or learn have like a clear pathway that would lead them, you know, to get things done. ([View Highlight](https://read.readwise.io/read/01kp9kcaw2h5t2d3xv9x7bmqq0)) - Tags: 👻 ai highlighted