CHAOSS Africa Technical Writers, March 5, 2026

๐ **Source:** [CHAOSS Africa Technical Writers, March 5, 2026](https://www.youtube.com/watch?v=uI8JNZunL1g)
> [!note]+ Document Notes
> tags: #chaos #africa #technical-writing #open-source #website #community
> author: CHAOSS Africa Technical Writers
> source: YouTube
> reference: https://www.youtube.com/watch?v=uI8JNZunL1g
> date created: 2026-03-05 00:00
>
> # ๐ท๏ธ Title: CHAOSS Africa Technical Writers Focus Group Meeting - March 5, 2026
>
<!-- deep-read:sections start -->
## ๐งฐ Action Inbox
- [H1] Complete CHAOSS Africa website copy by Wednesday next week โ website development dependency #website
- [H2] Create resource bank for technical writers in GitHub repo โ focus group deliverable #technical-writing
- [H3] Develop social media content strategy for Instagram and TikTok โ community growth initiative #community
## ๐งญ 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](https://chaoss.community)
- [CHAOSS Africa GitHub](https://github.com/chaoss/chaoss-africa)
## ๐ Summary
- CHAOSS Africa Technical Writers focus group meeting covering website development, working group updates, and community initiatives
- Critical blocker: Website copy needed for new CHAOSS Africa website development
- Multiple working groups reporting progress on education, design, and accessibility projects
- New initiative proposed for social media expansion to Instagram and TikTok
- Focus on improving community onboarding and conference outreach effectiveness
## ๐ Main Content
The meeting focused on coordinating technical writing efforts across CHAOSS Africa's various working groups. The primary discussion centered around the new CHAOSS Africa website project, which aims to move away from being hidden within the global CHAOSS website structure. The software development working group is leading the technical implementation, while the technical writers focus group will provide copywriting support.
A significant challenge emerged from conference outreach efforts in Namibia, where community members struggled to find comprehensive information about different working groups and how to contribute. This highlighted the urgent need for a well-structured website with clear pathways for new contributors.
The education working group is completing existing courses while planning AI integration for future phases. The design working group updated milestone timelines and stands ready to support website development. Accessibility and social media initiatives are also gaining momentum with proposals for expanded content creation.
## ๐๏ธ Notes
#### โฑ๏ธ [00:00](https://youtu.be/uI8JNZunL1g?t=0) โ [H1] Meeting opening and agenda review
- Key idea: Weekly check-in on CHAOSS Africa working group progress
- Evidence: "Welcome back. I'm pretty sure that we all had like an amazing week so far"
#### โฑ๏ธ [01:30](https://youtu.be/uI8JNZunL1g?t=90) โ [H1] CHAOSS Africa website development status
- Key idea: Website project stalled waiting for copywriting content
- Evidence: "Yeah, it has not started because we've not gotten copy yet"
#### โฑ๏ธ [03:45](https://youtu.be/uI8JNZunL1g?t=225) โ [H2] Copy delivery commitment and channel access
- Key idea: Technical writers committing to deliver website copy by Wednesday
- Evidence: "Monday we would be able to get a copy, right? Monday or Wednesday at most next week"
#### โฑ๏ธ [05:20](https://youtu.be/uI8JNZunL1g?t=320) โ [H1] Namibia conference feedback and website needs
- Key idea: Conference attendees need better onboarding resources beyond Slack/GitHub
- Evidence: "most of the folks were like where do I go like if I want to learn something"
#### โฑ๏ธ [08:15](https://youtu.be/uI8JNZunL1g?t=495) โ [H2] Website as wiki for working group information
- Key idea: New website should serve as comprehensive guide for contributor onboarding
- Evidence: "just a place where like it could be like just a wiki where someone can get for example if someone is interested in the data science working group"
#### โฑ๏ธ [09:30](https://youtu.be/uI8JNZunL1g?t=570) โ [H3] Multi-agent systems workshop topic
- Key idea: Brian's conference presentation covered building multi-agent systems with Python
- Evidence: "the topic was just building multi-agent systems with Python"
#### โฑ๏ธ [11:00](https://youtu.be/uI8JNZunL1g?t=660) โ [H3] Quarterly meetup planning initiative
- Key idea: Community planning local meetups per quarter across different regions
- Evidence: "having small meet up across different areas but this would be done like per quarter"
#### โฑ๏ธ [12:45](https://youtu.be/uI8JNZunL1g?t=765) โ [H2] Education working group AI integration plans
- Key idea: Education project expanding beyond current courses to include AI content
- Evidence: "we are trying to um go into a second phase for education working group which might we be involving or us bringing in uh some stuff about AI"
#### โฑ๏ธ [15:20](https://youtu.be/uI8JNZunL1g?t=920) โ [H3] Design working group milestone updates
- Key idea: Design team updated achievement timelines for CHAOSS milestones
- Evidence: "a milestone stating the time that chaos achieved different milestones like maybe a new working group was created"
#### โฑ๏ธ [17:10](https://youtu.be/uI8JNZunL1g?t=1030) โ [H2] Social media expansion proposal
- Key idea: Proposal to create Instagram and TikTok presence with quarterly content creation
- Evidence: "it would be nice for us to have Instagram and Tik Tok pages and we sort of maybe create content around open source"
#### โฑ๏ธ [19:30](https://youtu.be/uI8JNZunL1g?t=1170) โ [H3] Cross-group content collaboration suggestion
- Key idea: Working groups can create promotional videos for their specific projects
- Evidence: "focus groups and working group can actually take advantage of this as well you don't have to do too much a 30 seconds or 1 minute video"
#### โฑ๏ธ [21:45](https://youtu.be/uI8JNZunL1g?t=1305) โ [H3] Technical writers resource bank project
- Key idea: Creating markdown resource repository for technical writing guidance
- Evidence: "we have actually started working on a resource bank for technical writers where we would just drop links"
## ๐ References
- [CHAOSS Community Website](https://chaoss.community)
- [CHAOSS Africa GitHub Repository](https://github.com/chaoss/chaoss-africa)
- [CHAOSS Metrics and Models](https://chaoss.community/metrics/)
## ๐ฃ๏ธ Paraphrase
- The CHAOSS Africa website development is blocked because the technical writers haven't delivered the required copywriting content yet, but they've committed to providing it by Wednesday
- Conference outreach revealed that potential contributors struggle to find information about different working groups and contribution opportunities, highlighting the need for better onboarding resources
- Multiple working groups are making steady progress, with education expanding into AI content, design updating milestone documentation, and new social media initiatives being proposed for community growth
## ๐ฐ Newsletter
The CHAOSS Africa community is making significant progress on improving contributor onboarding and community engagement. A new dedicated website is in development to replace the current nested structure within the global CHAOSS site, with technical writers delivering copy content this week to unblock design and development work.
Recent conference outreach in Namibia highlighted the need for better contributor pathways, as interested community members couldn't easily find information about specific working groups and contribution opportunities. The new website will address this with a wiki-style structure showcasing each working group's current projects and onboarding processes.
The education working group is expanding beyond current course offerings to include AI-focused content, while design teams are updating community milestone documentation. A new social media initiative proposes quarterly content creation sessions to boost Instagram and TikTok presence.
Resources: [CHAOSS Community](https://chaoss.community), [CHAOSS Metrics](https://chaoss.community/metrics/), [GitHub Repository](https://github.com/chaoss/chaoss-africa)
## โ
Action Items
#### Community
- Contributors: Create wiki-style working group information pages for new contributor onboarding
- Maintainers: Establish quarterly local meetup coordination across regions
- Sponsors: Support social media content creation initiatives for Instagram and TikTok
#### Documentation
- HelpHub gaps: Develop comprehensive working group contribution guides
- Style guides: Create PRD template for website copywriting with character limits
- Knowledge base: Build technical writers resource bank in GitHub markdown format
#### WordPress
- Community: Implement meetup kits for quarterly regional gatherings
- Documentation: Apply lessons learned to WordPress contributor onboarding experiences
- Marketing: Consider cross-community social media content strategies
#### The WPCC
- Programs: Explore technical writing fellowship opportunities
- Projects: Support documentation sprints for open source communities
## ๐งช Hypotheses
- Better structured contributor onboarding documentation increases community participation rates
- Regional quarterly meetups strengthen local open source communities more than virtual-only engagement
- Social media presence on Instagram and TikTok attracts younger contributors to open source projects
- Wiki-style project information reduces barriers to entry for new contributors
### ๐ Methodology
- Track website analytics and contributor onboarding completion rates after new site launch
- Survey conference attendees before and after implementing improved onboarding resources
- Measure social media engagement and conversion rates from content to community participation
### โ Questions
- How can open source communities balance comprehensive documentation with approachable entry points?
- What metrics best indicate successful contributor onboarding in distributed communities?
- How do regional cultural differences affect community engagement strategies?
### ๐ฎ Future Research
- Comparative analysis of contributor onboarding effectiveness across different open source communities
- Impact study of social media content on open source project adoption
- Regional community engagement patterns in African tech communities
### ๐ก Implications
- Practice: Technical writers should create PRDs with specific character limits for web content
- Policy: Communities need clear contributor pathway documentation for sustainable growth
- Education: AI integration in educational content requires careful planning and community input
- Funding: Social media initiatives may require dedicated content creation resources
### ๐ง Learning Styles Assessment
Reading level estimate: 8th-9th grade
#### ๐ Visual learners
- Present: Meeting transcript format, clear section headers
- Improve: Add workflow diagrams for website development process, contributor journey maps
#### ๐ Aural learners
- Present: Video meeting format available
- Improve: Create audio summary of key decisions and action items
#### ๐ฃ๏ธ Verbal learners
- Present: Clear definitions of working groups, explained acronyms
- Improve: Add glossary of CHAOSS terminology, working group role descriptions
#### ๐งฉ Kinesthetic learners
- Present: Action items with specific deliverables and timelines
- Improve: Create checklists for website copy creation, contributor onboarding steps
#### ๐ง Logical learners
- Present: Clear timeline dependencies, cause-and-effect relationships
- Improve: Add project timelines, resource allocation charts
#### ๐งโ๐คโ๐ง Social learners
- Present: Community meeting format, collaborative decision-making
- Improve: Add discussion prompts for working group coordination
#### ๐งโโ๏ธ Solitary learners
- Present: Individual action items, personal responsibility assignments
- Improve: Create self-assessment rubrics for contribution readiness
#### ๐ฟ Naturalistic learners
- Present: Organic community growth discussion, ecosystem thinking
- Improve: Connect open source communities to broader technology ecosystem impacts
### ๐ Accessibility Assessment
#### Screen reader semantics
- Present: Clear heading structure, meeting participant identification
- Improve: Add speaker labels consistently, provide meeting agenda structure
#### Keyboard navigation
- Present: Standard video player controls
- Improve: Ensure transcript navigation with keyboard shortcuts
#### Contrast and readability
- Present: Text-based transcript format
- Improve: Verify timestamp links have sufficient contrast ratios
#### Text resizing and reflow
- Present: Responsive text format
- Improve: Test transcript readability at 200% zoom levels
#### Media and captions
- Present: Full transcript available
- Improve: Add speaker identification for audio clarity, consider audio descriptions
#### Forms and interactions
- Present: Basic timestamp linking functionality
- Improve: Ensure all interactive elements have accessible labels
### ๐ DEIB Assessment
#### Cultural breadth
- Present: African regional focus, multiple country representation (Namibia mentioned)
- Improve: Include more diverse geographical examples, acknowledge digital divide impacts
#### Inclusive language
- Present: Respectful participant interactions, welcoming tone
- Improve: Define technical terminology, avoid assumptions about tool familiarity
#### Neurodiversity support
- Present: Structured meeting format, clear action items
- Improve: Provide meeting agendas in advance, use consistent formatting
#### Representation
- Present: Multiple voices, collaborative decision-making
- Improve: Ensure balanced speaking time, diverse role representation
#### Psychological safety
- Present: Supportive tone when discussing challenges
- Improve: Explicitly acknowledge different comfort levels with tools like Slack/GitHub
### โ
Logical Validity
#### Strong reasoning
- Deductive strength: Conference feedback logically leads to website improvement needs
- Inductive strength: Past website navigation difficulties predict future contributor barriers
- Causal reasoning: Clear connection between copy delivery and website development timeline
- Analogical strength: Comparing wiki structure to successful documentation patterns
#### Fallacies
- Planning fallacy: Optimistic timeline for copy delivery without accounting for review cycles
- Availability heuristic: Overweighting recent Namibia conference feedback vs. broader data
#### Tone of voice
- Overall tone: Collaborative and constructive with practical problem-solving focus
### ๐ก๏ธ DARVO Analysis
- Deny: No evidence of denial patterns
- Attack: No attacks on community members or processes
- Reverse victim/offender: No victim/offender reversals observed
- Emotional cues and rhetoric: Positive, solution-oriented discussion throughout
## ๐ฏ Conclusion
The CHAOSS Africa Technical Writers focus group is actively addressing critical community infrastructure needs through website development and improved contributor onboarding. The immediate priority is delivering website copy content to unblock development work, while longer-term initiatives focus on expanding community reach through social media and regional meetups. The conference feedback from Namibia provides valuable insights for creating more accessible entry points for new contributors to the open source community.
## ๐งฑ Refactor Appendix
### ๐ Literature Split Pad
Purpose: Stage CEE units that become Literature notes.
Split level: H3
### [H1] Website copy delivery blocks development progress
> [!quote] CHAOSS Africa Technical Writers Meeting by CHAOSS Africa Technical Writers via YouTube. Published 2026-03-05. Accessed 2026-03-05.
> "Yeah, it has not started because we've not gotten copy yet."
Critical dependency relationship between content and development work.
[view highlight](https://youtu.be/uI8JNZunL1g?t=90#H1) #xref #articleseed ID:rw_chaoss_copy_blocker
### [H2] Conference outreach reveals onboarding gaps
> [!quote] CHAOSS Africa Technical Writers Meeting
> "most of the folks were like where do I go like if I want to learn something"
Direct feedback highlighting contributor pathway documentation needs.
[view highlight](https://youtu.be/uI8JNZunL1g?t=320#H2) #xref ID:rw_chaoss_onboarding_gaps
---
### ๐ Atomic Split Pad (Zettel Candidates)
Purpose: Promote reusable claims into Atomic notes.
Split level: H4
#### [Z1] Copy delivery creates development dependencies
- Applies to content-driven development projects
- Evidence at 01:30 timestamp
- Links: [[Content-Strategy]] [[Project-Dependencies]]
#### [Z2] Conference feedback drives community infrastructure needs
- Scope: Real-world community interaction insights
- Evidence at 05:20 timestamp
- Links: [[Community-Building]] [[Contributor-Onboarding]]
---
###
---
## Full Transcript
[00:00] Okay, the meeting is recording now. So,<br>[00:02] welcome back. I'm pretty sure that we<br>[00:05] all had like an amazing week so far and<br>[00:07] I hope we have like a very good weekend.<br>[00:11] How's it How's it going?<br>[00:14] How's it going for everyone<br>[00:16] so far? It's the week hectic.<br>[00:23] >> Really hectic and stressful for me.<br>[00:27] Okay,<br>[00:29] sorry about that. Anyone wants to take a<br>[00:31] bite before I go ahead.<br>[00:47] Okay. Yeah, let's go. So before we get<br>[00:50] started to know what what we have done<br>[00:53] like so far, I'll just give you guys a<br>[00:55] rundown of what was discussed last week.<br>[00:57] The call agenda for last week was the<br>[00:59] chaos African website. One of the issues<br>[01:02] that we had was the website is usually<br>[01:04] hidden right in the chaos.com<br>[01:07] community/lochapter<br>[01:09] section of the global website and we I<br>[01:13] think the agreement was for the software<br>[01:16] development working group or focus group<br>[01:19] to take up that tax and then bring it<br>[01:21] forward. Technical writer would um<br>[01:23] technical writers focus group would<br>[01:25] would help or aid in copyrightiting and<br>[01:27] all of those things which is very good.<br>[01:29] Right. So the very big question I'm<br>[01:32] going to ask is has this actually<br>[01:35] started which is one of the thing we<br>[01:37] should know like is there a meeting that<br>[01:39] has been held planned so far<br>[01:42] anybody from the working group<br>[01:47] I think uh<br>[01:52] I think are you with us or sitting<br>[01:58] >> hello sorry you were calling hear me?<br>[02:01] >> Yes. I was asking if if like<br>[02:06] >> I can hear you. Can you hear me?<br>[02:10] >> The new the new website or the moving of<br>[02:12] the website for the chaos Africa<br>[02:15] website. Have any conversation been had<br>[02:18] so far?<br>[02:22] >> Um the setup is going on.<br>[02:25] Um but I don't have um information so<br>[02:29] much information about it but I know<br>[02:32] that setup is going on.<br>[02:39] >> Yeah, I can hear you. So who's chairing<br>[02:41] it? Who's leading it<br>[02:43] >> for now? It's Ruth.<br>[02:50] >> Okay.<br>[02:52] >> Are they required designs? Are we<br>[02:54] working with WordPress or we are you<br>[02:57] know building from scratch?<br>[02:59] >> Okay, sorry. We are building from<br>[03:01] scratch but um I told Ruth that we<br>[03:04] needed copy so the copy would guide how<br>[03:07] the design would go and she mentioned in<br>[03:10] the last meeting that she would actually<br>[03:11] reach out to you to work on the copy but<br>[03:13] I don't know if she did that and she<br>[03:15] also created like a slack channel or<br>[03:19] would I say group for everybody that<br>[03:21] indicated interest on working on the<br>[03:23] website so I think every other<br>[03:26] information you get it from root<br>[03:29] Okay.<br>[03:30] Which means that the website design has<br>[03:32] not even started, I guess.<br>[03:34] >> Yeah, it has not started because we've<br>[03:36] not gotten copy yet.<br>[03:39] >> Okay, perfect. So, hasn't reached out to<br>[03:41] me and I'm just hearing this from the<br>[03:44] meeting. I did not read the meeting<br>[03:45] minutes. I just can't and I'm seeing my<br>[03:47] name there. So,<br>[03:50] Monday we would be able to get a copy,<br>[03:53] right? Monday or Wednesday at most next<br>[03:56] week. I'll add it in the meeting notes.<br>[03:58] we're able to get a copy that would<br>[04:00] direct us across but and I think I'm not<br>[04:03] also in the channel so if you can<br>[04:05] mention my name in the channel so that<br>[04:07] I'll be added or so that I will be<br>[04:09] prompted to get added so I would send<br>[04:12] the document there and everybody gets to<br>[04:15] like make a comment and review it.<br>[04:18] How about that? Yes.<br>[04:22] >> Sorry I didn't I didn't get what you<br>[04:23] just said. Sorry.<br>[04:26] So I said,<br>[04:28] >> can you can you say it again, please?<br>[04:30] >> The copy<br>[04:35] >> on Wednesday next week.<br>[04:38] >> Okay, that's fine.<br>[04:40] >> Yeah, but I'm not in the channel. Like I<br>[04:42] said, I'm just hearing it for the first<br>[04:43] time.<br>[04:43] >> Yeah. So you can just tell root to add<br>[04:44] it to the channel.<br>[04:46] >> Okay, I guess the channel is private.<br>[04:52] Okay, I'll do that.<br>[04:57] I guess we have headway for that. While<br>[05:00] we're on it, right? No, I said we are<br>[05:03] going to<br>[05:05] Okay. While we're on it, I would want to<br>[05:07] ask if uh Adena, how is it going with<br>[05:11] the DI budgeting working group?<br>[05:21] >> Um sorry, I won't be able to give up<br>[05:23] this now. Please, I am actually in<br>[05:25] transit so I'm not coordinated. Let me<br>[05:27] just listen in for today. Thank you.<br>[05:32] >> Okay. Okay. Thank you. Okay. While Okay.<br>[05:37] Uh Brian, Brian, please can you give<br>[05:40] feedback on your trip to Namibia, your<br>[05:42] talk? How was it?<br>[05:45] Yeah. The conference in Bon Namibia.<br>[05:52] >> Okay. Hi everyone. I hope you can hear<br>[05:54] me.<br>[05:54] >> Yes, thank you.<br>[05:56] >> No. Okay. Okay. Um the conference was<br>[05:59] nice. Um I mean it's always been nice<br>[06:01] from from the feedback, but it was<br>[06:03] particularly nice. Um my workshop went<br>[06:05] really well. Um all of the attendees<br>[06:07] were able to follow along and we had um<br>[06:11] a couple of folks going all through the<br>[06:13] end and also a couple of folks coming in<br>[06:14] for questions even after the talk. Um I<br>[06:18] also did um um a talk about what we do<br>[06:20] at Kos Africa and also a couple of a<br>[06:23] couple of folks were interested. Um I<br>[06:26] did share I did share the the link and<br>[06:28] the QR code to to join um to join the<br>[06:32] Slack channel. So definitely probably<br>[06:34] we're going to to see like a couple of<br>[06:36] folks a couple of folks coming through.<br>[06:39] But I think what hit me during during<br>[06:41] that is most of the folks were like<br>[06:43] where do I go like if I want to learn<br>[06:45] something because maybe most of them<br>[06:47] were not able to catch to catch the the<br>[06:49] the link or the QR code but I think<br>[06:51] maybe what is kindly been working on<br>[06:53] this is the chaos Africa website that<br>[06:55] would also be a good place where when<br>[06:57] you're at conferences or something it<br>[06:59] would be nice to direct people there so<br>[07:00] that they aware because some of them<br>[07:01] were like okay I'm interested in this<br>[07:03] working group I want to join this<br>[07:05] working group where can I get more<br>[07:06] details about them and sadly where I<br>[07:09] could just take them was either Slack or<br>[07:11] GitHub which might be so uh scary for<br>[07:14] someone who just wants to start and<br>[07:15] they're like okay they have not used<br>[07:17] Slack maybe they have not used GitHub<br>[07:18] before but I think now that we're<br>[07:20] setting up the the chaos Africa website<br>[07:22] probably in that landing page it could<br>[07:24] be nice now to also take conference<br>[07:26] attendees there so yeah um that's pretty<br>[07:30] much it was a lovely trip um NAB is<br>[07:32] always like the community is always nice<br>[07:35] it's very receptive and most of them<br>[07:38] were interested in in Chaos Africa<br>[07:40] though. Yep.<br>[07:46] >> So just to get you clearly so I know<br>[07:48] what I'm putting down on the notes. Uh I<br>[07:51] didn't get the topic that you spoke on.<br>[07:52] I would love you to like drop it at like<br>[07:54] the comments or in message up on Zumia<br>[07:58] so that I don't make mistake again. Then<br>[08:00] secondly the feedback when you share<br>[08:02] about chaos Africa people have not been<br>[08:04] able to like go around especially on the<br>[08:06] website to get details of various<br>[08:08] working groups what they're doing. So<br>[08:10] you also recommending that the new<br>[08:11] website should be able to capture that<br>[08:15] right?<br>[08:20] >> Yes. Yes. just a place where like it<br>[08:22] could be like just a wiki where someone<br>[08:24] can get for example if someone is<br>[08:27] interested in the data science working<br>[08:28] group they can just go there and learn<br>[08:30] about what we do what are the current<br>[08:31] projects you the data science working<br>[08:33] group is working on or maybe the other<br>[08:35] different working groups um inside chaos<br>[08:38] Africa maybe and also just around chaos<br>[08:40] Africa because most of them were like<br>[08:42] okay I want to join the community and<br>[08:44] maybe I'm a technical writer or I'm a<br>[08:46] product manager or I'm a product<br>[08:48] designer and all that where exactly can<br>[08:50] I contribute how can I contribute? It<br>[08:52] was hard for me to um off the bat in my<br>[08:54] mind have what each working group is<br>[08:57] doing cuz the attendees were very<br>[08:59] diverse. So if you have somewhere like<br>[09:01] that on the website, I'll be like, "Oh,<br>[09:02] just scan this Q code." You'd go to our<br>[09:04] website and you can definitely see what<br>[09:06] the the working these working groups are<br>[09:08] currently building or working on.<br>[09:12] >> Okay. Thank you very much.<br>[09:17] >> Thank you very much.<br>[09:18] >> Okay. Please just send me the topic you<br>[09:20] spoke on<br>[09:23] message. Yeah, that would be great.<br>[09:27] >> Just uh the topic was just building um<br>[09:29] multi- aent systems with Python. So<br>[09:32] yeah.<br>[09:33] >> Okay. Okay. Building multi- aent systems<br>[09:36] with Python. Sorry, I'm taking notes.<br>[09:39] >> No worries, it's fine.<br>[10:02] Thank you.<br>[10:04] Uh the next feedback I would want to get<br>[10:06] is<br>[10:09] we spoke about um okay just for<br>[10:13] announcement sake uh we last week they<br>[10:16] also spoke about having small meet up<br>[10:18] across different areas but this would be<br>[10:21] done like per quarter right I don't have<br>[10:24] a lot of context on that because I<br>[10:26] wasn't in the meeting but I think it's<br>[10:27] something that we could start discussing<br>[10:29] in our various working groups or focus<br>[10:31] groups to see how we could partake<br>[10:33] on these things as a community, right?<br>[10:37] It's going to be good to start getting<br>[10:39] data on your working group so that we<br>[10:41] know who is at this location or who is<br>[10:44] at that location so that we will be able<br>[10:46] to maximize meeting ourselves together<br>[10:49] which would allow us to more.<br>[10:53] Yeah. Thank you. And before I move<br>[10:57] forward is there has there been any<br>[10:58] development in your various working<br>[11:00] groups or the projects that you are<br>[11:02] leading particular anything exciting for<br>[11:04] us to know and the in the education<br>[11:06] project what's coming what's already<br>[11:09] working all of that any feedback<br>[11:16] are you with us<br>[11:19] >> education working group<br>[11:22] >> sorry what we're doing is like<br>[11:25] completing<br>[11:27] some already going courses and recording<br>[11:30] them and uh we we are trying to<br>[11:37] um go into a second phase for education<br>[11:39] working group<br>[11:41] um which might we be involving or us<br>[11:46] bringing in uh some stuff about AI and<br>[11:49] the rest of them but that is just uh<br>[11:53] still in the planning phase. is when<br>[11:56] um I just spoke with<br>[12:00] had a chat with on that with Matt about<br>[12:03] it. So when um all the plan is in place<br>[12:08] we bring it we can be able to give more<br>[12:13] uh information about that and how that<br>[12:15] would go with education uh project. So<br>[12:19] but at the moment we are just like<br>[12:22] completing those courses. We started<br>[12:26] um also advocating for new one case you<br>[12:29] have a course you feel like we can add<br>[12:31] up<br>[12:33] and education project or you have some<br>[12:37] things you might want us to feature some<br>[12:39] courses you've worked on or recorded or<br>[12:44] uh you might want us to feature in<br>[12:46] education project. So<br>[12:49] you can chat us uh discuss with us on it<br>[12:53] and then we can see how we can bring it<br>[12:56] up. Also the what is going on at the<br>[12:58] moment is um we're writing a second blog<br>[13:01] about u<br>[13:04] education project and we're calling all<br>[13:06] those that have contributed in one way<br>[13:08] or the other our review in one or the<br>[13:11] other to<br>[13:13] be part of it and also record themselves<br>[13:16] at the author of that blog. So if you're<br>[13:18] interested you are feel free to join us<br>[13:21] in education group or I've already<br>[13:23] shared the the link just feel free to<br>[13:26] contribute to it and that's all we are<br>[13:30] doing at the moment. Thank you.<br>[13:34] >> Okay thank you very much.<br>[13:37] Can you hear me? Yeah thank you very<br>[13:38] much. Especially the blog that's working<br>[13:40] and I like the fact that you guys are<br>[13:42] also trying to embed the AI. I don't<br>[13:45] know if you people would also the team<br>[13:47] would also consider Ospose. I don't know<br>[13:49] if there's anything about Ospose yet,<br>[13:51] but I think it's a good one to also look<br>[13:53] at. So, a good topic to also look at.<br>[13:57] >> Um, let me know how you're thinking<br>[13:59] about that then see how we can bring<br>[14:02] that up.<br>[14:04] >> Okay. Thank you. I'll do that.<br>[14:10] Any other person?<br>[14:17] any other working group. Uh the design<br>[14:19] team is there anything design working<br>[14:22] group unice? Um, currently nothing yet,<br>[14:26] but I guess when we start working on the<br>[14:28] website, we'll have something.<br>[14:33] I mean, aside the fact that um, we<br>[14:36] worked on something for Elizabeth last<br>[14:38] week that we're supposed to work on<br>[14:41] last year, but she actually provided<br>[14:45] information last week. I'll be this week<br>[14:48] and we worked on it. Yeah. Aside that we<br>[14:52] do not have<br>[14:53] >> sorry<br>[14:54] >> would you be able to tell me what you<br>[14:56] guys did for Elizabeth?<br>[14:57] >> Um I think it was something about<br>[14:59] timeline or achieve I think something<br>[15:01] related to like the achievement<br>[15:03] or timeline. I don't know exactly what<br>[15:05] that thing is called but it's<br>[15:09] >> if you're in the chaos like Africa<br>[15:11] designers group you'll see it or channel<br>[15:13] rather you'll see it. I think it was<br>[15:15] like a milestone stating the time that<br>[15:19] chaos achieved different milestones like<br>[15:21] maybe a new working group was created or<br>[15:23] something was done. So she just wanted<br>[15:26] us to update the design with the current<br>[15:28] things that have happened up from<br>[15:30] um I think 1023 to like last year. So we<br>[15:34] worked on that and that's all we've been<br>[15:37] able to do for now. But when we start<br>[15:38] working on the website we'll have like<br>[15:40] updates for you guys. Thank you.<br>[15:43] Sure.<br>[15:56] website project coming up.<br>[16:02] Uh any other person?<br>[16:05] >> Sorry, I have a question. Right. Um, so<br>[16:08] I'm I'm talking about this with already<br>[16:11] because she's the one handling the<br>[16:13] social media although I spoke about it<br>[16:16] in the last meeting that it would be<br>[16:18] nice for us to have Instagram and Tik<br>[16:19] Tok pages and we sort of maybe create<br>[16:21] content around open source and when we<br>[16:24] have like our hangouts we can also<br>[16:25] create content from that. I wanted to<br>[16:28] ask if anybody here is open to maybe<br>[16:32] being part of it. So if it works, we're<br>[16:35] thinking of doing something maybe once<br>[16:38] in a quarter or once every month. We<br>[16:41] meet somewhere and but create all the<br>[16:43] content that we may post for that month,<br>[16:47] right? Me, I'm open to doing cuz I'm a<br>[16:49] content creator and I enjoy like making<br>[16:50] videos. Yeah. Um would have to come<br>[16:54] obviously because she's the one in<br>[16:55] charge of social media, but I wanted to<br>[16:57] ask if any other person is open to the<br>[17:00] idea and would want to be a part of it.<br>[17:02] So if you're open to that, please let me<br>[17:04] know or you can let all you know. Thank<br>[17:07] you.<br>[17:09] >> My question is going to be uh would<br>[17:11] would everyone need to meet in person?<br>[17:14] How about people that in different<br>[17:15] cities as well?<br>[17:17] >> Well, that's something you can consider<br>[17:18] too. So if they're open to it, they can<br>[17:20] also maybe record their video. I'm sure<br>[17:24] maybe there's something you want people<br>[17:25] to know about open source. It doesn't<br>[17:26] even have to be serious. You can just<br>[17:28] apply storytelling. So if they are not<br>[17:30] open to meeting us when we want to do<br>[17:34] it, you can make your video and send it<br>[17:37] to us cuz I I just feel like um if we<br>[17:40] have more social media presence, we will<br>[17:42] do more, right? because a lot of people<br>[17:45] do not know about open source and how<br>[17:48] they can contribute and people consume<br>[17:50] more videos than they will read blogs or<br>[17:54] articles or stuff like<br>[17:57] >> just to also suggest I think I've<br>[17:58] mentioned it before just to also s<br>[18:01] suggest right I also think that focus<br>[18:03] groups and working group can actually<br>[18:05] take advantage of this as well you don't<br>[18:08] have to do too much a 30 seconds or 1<br>[18:10] minute video explaining what the focus<br>[18:12] group is and what they are doing is also<br>[18:15] a good way to tell people to like join<br>[18:17] chaos and like get started. So I'm<br>[18:20] saying this because I think uh pea can<br>[18:22] embed it right in the education project<br>[18:25] as well. Maybe a new course is out. Just<br>[18:27] one template that we could use stating<br>[18:30] that a new course is out and what they<br>[18:32] need to know about the course, a link<br>[18:34] where they can actually go and you know<br>[18:36] listen or view the course thereabouts.<br>[18:40] And I also think if we are given the<br>[18:42] opportunity of we can make it Instagram<br>[18:44] and Tik Tok friendly, it's also a thing<br>[18:46] that the podcast can actually take<br>[18:48] advantage of as well. basically using it<br>[18:50] as like a marketing and<br>[18:53] a yeah a marketing tool for the project<br>[18:58] marketing or publication too for like<br>[18:59] chaos entirely.<br>[19:02] I don't know just putting it out there.<br>[19:05] So<br>[19:07] I hope that helps. I hope this good.<br>[19:12] Okay. Thank you very much. Unice. Uh<br>[19:15] Brian, is there anything interesting<br>[19:17] from the<br>[19:22] Is there anything interesting with<br>[19:24] people with disability?<br>[19:27] Don't know if it's still there.<br>[19:29] >> Um not really. I know we've been picking<br>[19:31] up slowly. Uh but hopefully um the<br>[19:34] coming few um Okay. Hope hope you can<br>[19:36] hear me. It's giving me an<br>[19:43] Yeah, can you hear me?<br>[19:46] >> Yeah. So, nothing nothing much really.<br>[19:49] Not that I'm aware of. Uh, but I know<br>[19:51] we've been picking up slowly, but<br>[19:52] probably as we pick up through this<br>[19:54] month, we probably have some activities<br>[19:56] coming along. So, hopefully by the next<br>[19:58] meeting, we'll have some updates to<br>[19:59] share.<br>[20:07] For us in the technical writers focus<br>[20:10] group, we have not really been doing so<br>[20:13] much. We've just been there. However, in<br>[20:17] our agenda, we had like two things<br>[20:19] mapped out. We wanted to help review the<br>[20:22] or but I think a lot of work is going on<br>[20:25] in the working group like for us like<br>[20:28] step to look at the document. So would<br>[20:30] allow that work go ahead and consume. So<br>[20:33] far we are intending or we have actually<br>[20:36] started working on a resource bank for<br>[20:40] technical writers where we would just<br>[20:41] drop links and we could use that as a<br>[20:44] markdown file on that technical class<br>[20:46] focus group file in chaos Africa repo.<br>[20:51] However, we just that in the Google docs<br>[20:54] and we hope we would keep progressing on<br>[20:56] it. Then also what got to our table now<br>[21:00] is like the copyrightiting for the<br>[21:02] websites. We probably structure it like<br>[21:05] a POD divide it into different pages and<br>[21:08] what we intend to see there and then<br>[21:10] allow the designers to like play around<br>[21:13] their creativity. We see how we could<br>[21:15] also you know put text there as well in<br>[21:18] terms of number of characters as<br>[21:19] expected. So I don't know units<br>[21:22] should we work on like something like a<br>[21:24] P and allow you to like decide that I<br>[21:27] know that the max we can do is like 50<br>[21:30] to 100 characters in certain areas when<br>[21:32] we're trying to highlight key things and<br>[21:34] then when people click on it then a page<br>[21:36] would pop up to give a full story or<br>[21:40] full things behind that particular thing<br>[21:42] like a project right<br>[21:48] I don't know if that would work Unless<br>[21:53] >> I didn't even know you referring to me.<br>[21:55] So, I know you said something about Pi,<br>[21:58] but is it like a what kind of product is<br>[22:01] it? Is it maybe a website, web app,<br>[22:04] mobile app or what?<br>[22:05] >> It's for the website basically. We're<br>[22:07] just going to break it down into pages<br>[22:09] and the sections that are going to be in<br>[22:10] each of those.<br>[22:11] >> Yeah. Yeah. Yeah. So, please the So, are<br>[22:13] you asking if maybe the copy for the<br>[22:15] website should be more like a P? Is that<br>[22:17] what you're asking?<br>[22:18] >> Yes. Yeah, I mean if you can come up<br>[22:20] with that that would be better.<br>[22:22] >> Yeah. So that because I know that uh I<br>[22:24] don't know how the design would look<br>[22:27] right but I know that the PD can serve<br>[22:29] as a guideline then you would now use uh<br>[22:33] placeholders in certain areas so that we<br>[22:36] will now use those length of copies like<br>[22:40] length of characters to create the<br>[22:41] actual copy that would be there based<br>[22:43] off the design.<br>[22:48] Yeah, I do.<br>[22:50] >> Okay. So, I'll add that. I would get<br>[22:53] that across to you like I said Wednesday<br>[22:54] and we're going to start moving forward<br>[22:56] from there.<br>[23:01] >> Okay. Thank you. Any other thing I've<br>[23:04] missed out or anything exciting in your<br>[23:06] focus group working group that you would<br>[23:08] want to share with us?<br>[23:22] Okay,<br>[23:24] in the absence of none,<br>[23:28] right, I think we can call it a day.<br>[23:30] Thank you everyone for joining today's<br>[23:32] session. Please do well to have like a<br>[23:35] lovely week.<br>[23:37] Thank you everyone.<br>[23:40] >> Bye guys.<br>[23:42] >> Bye everyone.
<!-- deep-read:sections end -->
๐ **Full text:** ![[Full Document Contents/Articles/CHAOSS Africa Technical Writers, March 5, 2026.md|CHAOSS Africa Technical Writers, March 5, 2026 by YouTube]]
## Highlights
- up and education project or you have some things you might want us to feature some courses you've worked on or recorded or uh you might want us to feature in education project. So you can chat us uh discuss with us on it and then we can see how we can bring it up. Also the what is going on at the moment is um we're writing a second blog ([View Highlight](https://read.readwise.io/read/01kpb4yrg11gcrjze7gsb4bczf))
- Tags: ๐ป ai highlighted
- that up. >> Okay. Thank you. I'll do that. Any other person? any other working group. Uh the design team is there anything design working group unice? Um, currently nothing yet, but I guess when we start working on the website, we'll have something. ([View Highlight](https://read.readwise.io/read/01kpb4yrhmbh51mzs4g8fga0b2))
- Tags: ๐ป ai highlighted
- um I think 1023 to like last year. So we worked on that and that's all we've been able to do for now. But when we start working on the website we'll have like updates for you guys. Thank you. Sure. website project coming up. ([View Highlight](https://read.readwise.io/read/01kpb4yrjx15ag309y5g161rkq))
- Tags: ๐ป ai highlighted
- up slowly. Uh but hopefully um the coming few um Okay. Hope hope you can hear me. It's giving me an Yeah, can you hear me? >> Yeah. So, nothing nothing much really. Not that I'm aware of. Uh, but I know we've been picking up slowly, but probably as we pick up through this month, we probably have some activities coming along. So, hopefully by the next meeting, we'll have some updates to share. ([View Highlight](https://read.readwise.io/read/01kpb4yrmsnef0ftm6j3eae1ga))
- Tags: ๐ป ai highlighted