12-16-2025 WG-BEAR Regular Meeting ๐Ÿ”— **Source:** [12-16-2025 WG-BEAR Regular Meeting](https://www.youtube.com/watch?v=syXavZ9buJk) > [!note]+ Document Notes > tags: [open-source, working-group, community-management, openssf, africa-sig] > author: WG-BEAR > source: YouTube > reference: https://www.youtube.com/watch?v=syXavZ9buJk > date created: 2024-12-16 15:30 > > # ๐Ÿท๏ธ Title: WG-BEAR Regular Meeting - OSS Africa SIG Approval & 2026 Planning > <!-- deep-read:sections start --> ## ๐Ÿงฐ Action Inbox - [H1] Create PR for OSS Africa SIG documentation โ€” Prince to lead with Stacey support โ€” 00:00 #sig-approval - [H2] Research visa requirements for conference speaking โ€” Prince to investigate timing and documentation needs โ€” 28:45 #travel-planning - [H3] Set up January working group landscape presentation โ€” Use OpenSSF slide template for welcome call โ€” 32:15 #office-hours ## ๐Ÿงญ Table of Contents - [๐Ÿ“ Summary](#-summary) - [๐Ÿ“– Main Content](#-main-content) - [๐Ÿ—’๏ธ Notes](#๏ธ-notes) - [๐Ÿ“š References](#-references) - [๐Ÿ—ฃ๏ธ Paraphrase](#๏ธ-paraphrase) - [๐Ÿ“ฐ Newsletter](#-newsletter) - [โœ… Action Items](#-action-items) - [๐Ÿงช Hypotheses](#-hypotheses) - [๐Ÿ“Š Methodology](#-methodology) - [โ“ Questions](#-questions) - [๐Ÿ”ฎ Future Research](#-future-research) - [๐Ÿ’ก Implications](#-implications) - [๐Ÿง  Learning Styles Assessment](#-learning-styles-assessment) - [๐Ÿ“Š Accessibility Assessment](#-accessibility-assessment) - [๐ŸŒ DEIB Assessment](#-deib-assessment) - [โœ… Logical Validity](#-logical-validity) - [๐Ÿ›ก๏ธ DARVO Analysis](#-darvo-analysis) - [๐ŸŽฏ Conclusion](#-conclusion) ### ๐Ÿ”— References - [OpenSSF Community](https://openssf.org/) - [WG-BEAR Working Group](https://github.com/ossf/wg-identifying-security-threats) ## ๐Ÿ“ Summary - The WG-BEAR working group officially approved the OSS Africa Special Interest Group (SIG) with unanimous support - Discussion focused on 2026 planning including tip-of-the-month content, community office hours, and speaking engagements - Significant challenges identified for African contributors attending conferences due to visa timing requirements - Community office hours planned to start January with working group landscape overview - Budget approval still pending for mentorship programs ## ๐Ÿ“– Main Content The WG-BEAR (Working Group - Broadly Enabling APAC Research) held their regular meeting to finalize the approval of the OSS Africa Special Interest Group and plan initiatives for 2026. The OSS Africa SIG received unanimous approval from all voting members present, marking a significant milestone for open source community expansion in Africa. Key discussion centered around practical challenges faced by African contributors in attending international conferences, particularly visa processing requirements that necessitate confirmed speaking acceptances before applications can be submitted. This creates timing conflicts with conference planning cycles. The group outlined their 2026 roadmap including monthly educational content (tip-of-the-month), community office hours mixing working group overviews with welcome sessions, and strategic conference speaking engagements. Budget approval for mentorship programs remains pending, potentially impacting spring timeline execution. ## ๐Ÿ—’๏ธ Notes #### โฑ๏ธ [00:00](https://youtu.be/syXavZ9buJk?t=0) โ€” [H1] Meeting Opening and OSS Africa Voting - Key idea: Final decision meeting for OSS Africa SIG approval - Evidence: "It looks like everybody voted in support. I don't see any thumbs down" #### โฑ๏ธ [02:15](https://youtu.be/syXavZ9buJk?t=135) โ€” [H1] OSS Africa SIG Official Approval - Key idea: Unanimous approval achieved for OSS Africa SIG establishment - Evidence: "Congratulations. Sounds like OSA South Africa is officially a stake under the bear working group" #### โฑ๏ธ [03:30](https://youtu.be/syXavZ9buJk?t=210) โ€” [H2] Documentation and Repository Setup - Key idea: Next steps involve creating official documentation in repository - Evidence: "Prince, are you comfortable doing that? and I'm happy to assist however I need to" #### โฑ๏ธ [05:45](https://youtu.be/syXavZ9buJk?t=345) โ€” [H2] Tip of the Month Planning Discussion - Key idea: Monthly educational content will be current-event focused and flexible - Evidence: "I may throw a audible I may pull a audible um and and that will be current event focused" #### โฑ๏ธ [08:20](https://youtu.be/syXavZ9buJk?t=500) โ€” [H2] VEX and CRA Integration Opportunity - Key idea: Current regulatory developments provide timely educational content - Evidence: "we're getting ready to publish a blog through OpenSSF and through Oasis um uh signaling the noise" #### โฑ๏ธ [12:10](https://youtu.be/syXavZ9buJk?t=730) โ€” [H2] 2026 Roadmap Search and Planning - Key idea: Team searching for previously created roadmap document - Evidence: "Marcel or Stacy, did we find the road map? Do we have a road map document?" #### โฑ๏ธ [15:30](https://youtu.be/syXavZ9buJk?t=930) โ€” [H2] Community Office Hours Structure - Key idea: January kickoff with working group landscape overview - Evidence: "January we kick off with a working group landscape kind of call" #### โฑ๏ธ [18:45](https://youtu.be/syXavZ9buJk?t=1125) โ€” [H3] Mentorship Program Status Update - Key idea: Budget approval pending, community interest confirmed - Evidence: "there have been a few like questions coming in about uh like when when that's going to start again" #### โฑ๏ธ [22:15](https://youtu.be/syXavZ9buJk?t=1335) โ€” [H2] Speaking Engagements Planning Request - Key idea: OSS Africa team to provide conference priority list - Evidence: "Prince, were you able to work with your your team and group to see uh speaking engagements for next year" #### โฑ๏ธ [25:30](https://youtu.be/syXavZ9buJk?t=1530) โ€” [H2] Conference CFP Status Review - Key idea: Most current CFPs closed, VulCon still accepting submissions - Evidence: "Volcon is still open. Um that one I think closes on December 22nd" #### โฑ๏ธ [28:45](https://youtu.be/syXavZ9buJk?t=1725) โ€” [H3] Visa Processing Challenges for African Contributors - Key idea: Visa applications require confirmed speaking acceptance first - Evidence: "if you want to apply for a visa like that your talk have to be accepted first" #### โฑ๏ธ [32:15](https://youtu.be/syXavZ9buJk?t=1935) โ€” [H2] Alternative Conference Participation Strategies - Key idea: Exploring booth representation and volunteering as visa alternatives - Evidence: "what if you're volunteering for the conference or you're setting up a booth" #### โฑ๏ธ [35:40](https://youtu.be/syXavZ9buJk?t=2140) โ€” [H2] January Office Hours Assignment - Key idea: Working group landscape presentation scheduled for January 22nd - Evidence: "the first one in January is on the 22nd" #### โฑ๏ธ [38:20](https://youtu.be/syXavZ9buJk?t=2300) โ€” [H2] Community Location Survey Request - Key idea: OpenSSF gathering community geographic data for event planning - Evidence: "we're trying to figure out like where our community is located so that we could um support uh efforts for travel" ## ๐Ÿ“š References - [OpenSSF Working Groups](https://github.com/ossf) - [VEX Standards Documentation](https://www.cisa.gov/vex) - [Community Survey Form](https://forms.gle/[MISSING]) ## ๐Ÿ—ฃ๏ธ Paraphrase - The WG-BEAR working group unanimously approved the establishment of OSS Africa as an official Special Interest Group, marking a significant expansion of open source community representation - Planning for 2026 focuses on educational content delivery through tip-of-the-month publications that will adapt to current events and regulatory developments in the security space - African contributors face substantial barriers to international conference participation due to visa requirements that create timing conflicts with standard CFP cycles ## ๐Ÿ“ฐ Newsletter ๐ŸŽ‰ **Big Community News!** The WG-BEAR working group has officially welcomed OSS Africa as a Special Interest Group, expanding OpenSSF's global reach and representation. This milestone reflects the growing recognition of Africa's contributions to open source security. **What's Coming in 2026:** The community is planning monthly educational content, regular office hours mixing working group overviews with newcomer welcome sessions, and strategic conference participation. However, they've identified important barriers for international contributors, particularly around visa processing timelines. **Get Involved:** The team is actively seeking mentorship program participants and conference speakers. They're also conducting a community survey to better understand geographic distribution for event planning. **Key Takeaway:** Community growth requires addressing practical barriers like visa processing while maintaining educational momentum through flexible, current-event focused content delivery. Resources: [OpenSSF Community](https://openssf.org/), [WG-BEAR Repository](https://github.com/ossf/wg-identifying-security-threats), [Community Survey](https://forms.gle/[MISSING]) ## โœ… Action Items #### Community - OSS Africa: Create official SIG documentation PR and repository presence - Mentorship: Await budget approval and begin project outreach for mentors - Office Hours: Prepare working group landscape presentation for January using OpenSSF templates - Survey: Complete community geographic distribution form for event planning #### OSPO - Policy & Governance: Document SIG approval process and requirements - Community Engagement: Research conference visa support policies and letter-writing capabilities - Strategic Alignment: Align 2026 roadmap with budget approvals and timeline constraints #### DevRel - Education: Develop current-event focused tip-of-the-month content calendar - Community management: Facilitate cross-working group office hours coordination - Developer marketing: Plan conference speaking strategy addressing geographic barriers ## ๐Ÿงช Hypotheses - Community office hours combining multiple functions will increase efficiency while maintaining engagement quality - Current-event focused educational content will have higher relevance and adoption than static materials - Geographic barriers to conference participation disproportionately impact contributors from visa-restricted regions - Early conference booth commitments could enable visa processing for African contributors ### ๐Ÿ“Š Methodology - Track office hours attendance and feedback comparing combined vs. separate session formats - Monitor engagement metrics for tip-of-the-month content aligned with current events vs. static topics - Survey conference participation rates by geographic region and visa requirements - Pilot booth-based visa support for select conferences and measure success rates ### โ“ Questions - How can OpenSSF better support international contributors facing visa processing barriers? - What alternative conference participation models could work for geographically distributed communities? - How should educational content balance evergreen value with current-event relevance? ### ๐Ÿ”ฎ Future Research - Comparative analysis of open source conference accessibility across different regions - Best practices for distributed community representation at industry events - Impact assessment of mentorship programs on project sustainability and contributor diversity ### ๐Ÿ’ก Implications - Practice: Conference planning must account for visa processing timelines when targeting international speakers - Policy: OpenSSF may need formal policies around international contributor support and travel assistance - Education: Educational content strategy should balance current events with foundational knowledge - Community: SIG establishment creates scalable model for geographic community expansion ### ๐Ÿง  Learning Styles Assessment Reading level estimate: 12th grade #### ๐Ÿ‘€ Visual learners - Present: Meeting agenda structure, clear action item identification - Improve: Process flowcharts for SIG approval, conference participation timeline visuals #### ๐Ÿ”Š Aural learners - Present: Full meeting audio recording available - Improve: Key decision summaries as audio clips #### ๐Ÿ—ฃ๏ธ Verbal learners - Present: Clear definitions of SIG, CFP, visa processes - Improve: Glossary of working group terminology and acronyms #### ๐Ÿงฉ Kinesthetic learners - Present: Action-oriented meeting with clear next steps - Improve: Checklist templates for SIG setup, conference submission workflows #### ๐Ÿง  Logical learners - Present: Clear cause-effect relationship between visa timing and conference participation - Improve: Decision trees for conference participation strategies #### ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Social learners - Present: Collaborative problem-solving around visa challenges - Improve: Peer support networks for conference submissions #### ๐Ÿง˜โ€โ™€๏ธ Solitary learners - Present: Individual action items with clear ownership - Improve: Self-assessment tools for conference readiness #### ๐ŸŒฟ Naturalistic learners - Present: Geographic considerations for community building - Improve: Regional ecosystem mapping for open source communities ### ๐Ÿ“Š Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure for different topics - Improve: More descriptive timestamps and topic headers #### Keyboard navigation - Present: Standard YouTube controls available - Improve: Chapter markers for easy navigation #### Contrast and readability - Present: Clear meeting notes structure - Improve: Higher contrast formatting for action items #### Text resizing and reflow - Present: Responsive text format - Improve: Consistent formatting across all sections #### Media and captions - Present: Full transcript available - Improve: Captions with speaker identification #### Forms and interactions - Present: Clear action assignments - Improve: Accessible survey forms mentioned in discussion ### ๐ŸŒ DEIB Assessment #### Cultural breadth - Present: Global representation with Africa, US, Europe participants - Improve: Translation support for non-English speaking contributors #### Inclusive language - Present: Professional, welcoming tone throughout - Improve: More explicit acknowledgment of systemic barriers #### Neurodiversity support - Present: Clear structure and predictable meeting format - Improve: Meeting materials provided in advance #### Representation - Present: Leadership roles distributed across geographic regions - Improve: Ensure equitable speaking time across all participants #### Psychological safety - Present: Supportive response to visa challenges, celebration of achievements - Improve: Explicit policies for inclusive participation ### โœ… Logical Validity #### Strong reasoning - Deductive strength: SIG approval process follows established criteria and voting procedures - Inductive strength: Conference participation challenges identified through lived experience - Causal reasoning: Visa timing requirements directly impact conference participation ability - Analogical strength: Other working groups provide model for successful community expansion #### Fallacies - None identified: Discussion maintains focus on practical problem-solving #### Tone of voice - Overall tone: Collaborative, supportive, action-oriented with celebration of community milestones ### ๐Ÿ›ก๏ธ DARVO Analysis - Deny: No instances of denial or minimization observed - Attack: No attacks on any individuals or groups - Reverse victim/offender: Not applicable to this community discussion - Emotional cues and rhetoric: Positive, celebratory tone around achievements with empathetic problem-solving approach ## ๐ŸŽฏ Conclusion The WG-BEAR meeting successfully established OSS Africa as an official SIG while identifying critical infrastructure challenges for global community participation. The unanimous approval demonstrates strong community support for geographic expansion, but highlighted visa processing barriers reveal systemic challenges requiring policy attention. **Next Steps:** The community should focus on creating accessible documentation, researching visa support alternatives, and launching educational content that balances current events with foundational knowledge. Success will depend on addressing practical participation barriers while maintaining educational momentum. **Broader Impact:** This approval model provides a template for other geographic expansions, while the visa discussion highlights the need for more inclusive conference participation frameworks across the open source ecosystem. ## ๐Ÿงฑ Refactor Appendix ### ๐Ÿ“š Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] OSS Africa achieves official SIG status through unanimous approval > [!quote] [12-16-2025 WG-BEAR Regular Meeting](https://www.youtube.com/watch?v=syXavZ9buJk) by [[WG-BEAR]] via [[YouTube]]. Published 2024-12-16. Accessed 2024-12-16. > "Congratulations. Sounds like OSA South Africa is officially a stake under the bear working group." Milestone achievement demonstrating community expansion and inclusive governance processes. [ --- ## Full Transcript [01:27] Hi everyone. I know Marcetta's uh<br>[01:30] running a little late. I got my dogs<br>[01:33] back here. So<br>[01:48] all good. I finally have a<br>[01:51] break in my schedule. I had a<br>[01:55] long standing internal meeting they just<br>[01:58] couldn't seem to get right. Um, every<br>[02:01] time I asked them to change the meeting,<br>[02:04] then there would be a a weird rift in<br>[02:08] the force where they change the meeting<br>[02:09] and then all of a sudden the meeting<br>[02:11] would happen and they're like, "Oh crap,<br>[02:13] I'm missing another meeting." So, but no<br>[02:16] meeting today. So, I'm here.<br>[02:20] >> Miracles of the holidays.<br>[02:22] >> Ready to uh kick off the um<br>[02:27] the tip of the month though for for for<br>[02:29] next month.<br>[02:32] >> Yeah.<br>[02:32] >> Be some good stuff coming into this<br>[02:35] year.<br>[02:39] >> Thank you for taking<br>[02:42] the lead on that.<br>[02:47] Good. Be good to get that get that kind<br>[02:49] of stuff out.<br>[02:51] Anybody else tired? I was on vacation<br>[02:53] for three weeks. I came back. I mean, I<br>[02:55] feel rested, but<br>[02:57] boy, am I still mentally worn out. I<br>[02:59] don't know what the I was just mentally<br>[03:02] worn out.<br>[03:05] >> Yeah. I'm just tired. It's just I guess<br>[03:07] the holidays kicking in. My body's just<br>[03:09] like, "We're done. We're done."<br>[03:15] No.<br>[03:20] All right. I'm trying to pull up the<br>[03:22] notes<br>[03:26] if anybody has a reading available.<br>[03:30] It's 2024.<br>[03:32] It's good to<br>[03:45] Oh, thank you, Stacey.<br>[03:48] All right,<br>[03:52] not<br>[03:55] see if I can share my screen.<br>[04:02] All<br>[04:03] right. So,<br>[04:11] share screen.<br>[04:19] Okay. So, if you haven't done already,<br>[04:22] feel free to chat. Sign yourself in.<br>[04:26] I know Jay, you're talking about tip of<br>[04:27] the month.<br>[04:29] Uh we had uh OSS Africa<br>[04:35] um<br>[04:37] final decision<br>[04:40] and 226 road maples<br>[04:45] in the road map I think<br>[04:51] put that in there.<br>[04:54] All right. Let me find<br>[05:04] and I think today<br>[05:08] we're making final decisions on<br>[05:13] OSS Africa if I'm not mistaken.<br>[05:20] >> All right.<br>[05:25] I got thumbs up from Stacy.<br>[05:29] Let's see if anybody said<br>[05:33] no.<br>[05:34] See another not a vote of support. All<br>[05:37] right, so it looks like everybody voted<br>[05:39] in support. I don't see any thumbs down.<br>[05:44] Uh Stacy or Marcela, what would be the<br>[05:48] next steps?<br>[06:01] Um<br>[06:02] I am unsure. I think I don't know if we<br>[06:06] have other sigs in this. I think the<br>[06:09] votes are there. So we can just say that<br>[06:11] it's voted in. Um unless there's any<br>[06:14] other objections on the call. Um, and<br>[06:18] then we can add uh the SIG maybe<br>[06:21] somewhere to the repo, I guess, to make<br>[06:23] it official.<br>[06:25] Does that sound good?<br>[06:27] >> Yeah, maybe we just connect the bear<br>[06:30] work to<br>[06:32] um<br>[06:34] we go to the Oh, it says Africa. Thank<br>[06:38] you.<br>[06:40] Yeah, no worries.<br>[06:42] like<br>[06:43] >> yeah, I don't know if we want um one of<br>[06:46] the SIG leads to just open the PR<br>[06:50] um combine all the combine all the um<br>[06:55] like the initial issue proposal that you<br>[06:57] wrote up Stacey and then also the extra<br>[06:59] content that shared um I think we can<br>[07:02] just put that in a PR and then<br>[07:05] um merge it into the repo.<br>[07:08] >> Okay, Prince, are you comfortable doing<br>[07:10] that? and I'm happy to assist however I<br>[07:13] need to.<br>[07:18] >> Yes.<br>[07:20] >> Fabulous.<br>[07:24] >> Hello everyone joining me. Sorry.<br>[07:29] >> Good holidays around. I think we just<br>[07:31] started kicking off. Well,<br>[07:34] congratulations.<br>[07:36] Sounds like OSA South Africa is<br>[07:38] officially a stake under the bear<br>[07:41] working group.<br>[07:45] Give yourselves a well<br>[07:48] cheerful<br>[07:52] screen share.<br>[07:54] >> I'll make a note in the issue if that's<br>[07:56] not there yet. Um to say that like on<br>[07:59] today's meeting we officially declared<br>[08:02] it.<br>[08:04] Thank you.<br>[08:08] Perfect.<br>[08:11] And then it was on me to put the road<br>[08:16] map in the repo. I honestly forgot. I<br>[08:19] thought I had another week. Um,<br>[08:22] where do we have that road map document?<br>[08:26] No worries.<br>[08:33] Oh, we had something.<br>[08:36] Is it here?<br>[08:43] Do you know where we put the remote?<br>[09:11] Did we create a romant?<br>[09:16] >> I thought there was one. I know. I found<br>[09:18] it before.<br>[09:21] >> Try to dig it up real quick. Um,<br>[09:29] you talked about it like two meetings<br>[09:31] ago or something.<br>[09:32] >> I think at our last meeting too.<br>[09:34] >> Yeah.<br>[09:38] Is it here anymore?<br>[09:41] This was the tech initiative document.<br>[09:45] Yeah. Found the bear working group<br>[09:47] document. So,<br>[09:50] or not the bear working group. What am I<br>[09:51] saying? the tip of the month document.<br>[09:55] Um,<br>[09:58] share that here.<br>[10:06] Stop sharing it to me. I did<br>[10:44] Okay, this is tip of the month.<br>[10:50] Uh, let's pass it over to Jay. Any top<br>[10:55] of mind or questions on the tip of the<br>[10:58] month?<br>[11:03] >> Uh, no. I'm sitting here reviewing uh<br>[11:08] the tips as they're as they're laid out.<br>[11:10] Um, what I what I may do is I may throw<br>[11:14] um<br>[11:16] I may throw<br>[11:19] a a audible I may pull a audible<br>[11:23] um and and that will be current event<br>[11:26] focused right so like for instance I see<br>[11:29] a couple of tips here you know I'll give<br>[11:32] an example trust but verify validated<br>[11:35] testations but let's say some at some<br>[11:37] point during that month some kind of<br>[11:40] regulation passes or some type of<br>[11:42] standard gets um or some type of spec<br>[11:46] turns into a standard and it's relevant<br>[11:50] for you know tips that that that we're<br>[11:53] looking at you know especially like I'll<br>[11:55] give you an example CRA stuff and and<br>[11:58] VEX in particular um we're getting ready<br>[12:00] to publish a blog through OpenSSF and<br>[12:03] through Oasis um uh signaling the noise<br>[12:08] uh we're a a consortium of of um<br>[12:10] industry<br>[12:12] uh leaders put together a document on<br>[12:14] VEX in the industry which will<br>[12:17] complement a lot of the CRA work that<br>[12:19] that you know that's happening uh with<br>[12:22] respect to vulnerability disclosures and<br>[12:24] all that kind of stuff. Um, you know,<br>[12:28] part of that conversation is how do<br>[12:31] open-source developers, new open source<br>[12:34] developers, uh, how do they, uh, how do<br>[12:37] they join the fund and being able to to,<br>[12:40] um, create vex statements, especially<br>[12:44] since they're creating tools that they<br>[12:46] hope get picked up by enterprises and<br>[12:49] some of their efforts, right? How do<br>[12:50] they create vex statements that an<br>[12:52] enterprise can then use to validate or<br>[12:55] or or to verify um you know the the you<br>[12:59] know vulnerabilities that may be present<br>[13:02] and and or or or how do they verify<br>[13:05] whether or not no coding and stuff like<br>[13:07] that um that might be relevant for tip<br>[13:10] of the month. I I mean I you know stuff<br>[13:12] like that. Not saying that that that<br>[13:15] we'll deviate so much but um in an<br>[13:17] effort to to maintain current along with<br>[13:20] our thoughts now as as we keep pushing<br>[13:23] them out for the remainder of the year,<br>[13:25] we may want to bring stuff up current<br>[13:27] during that month that will resonate a<br>[13:29] little bit more than stuff that we<br>[13:30] thought about maybe six months ago.<br>[13:32] Right? So um that that's pretty much it.<br>[13:35] Um but no questions. Uh just excited to<br>[13:38] get that moving because um you know we<br>[13:42] we're we're moving in different places<br>[13:44] and you know especially with this new<br>[13:46] SIG. It'd be good to get this tip of the<br>[13:48] month and then get that that that tip<br>[13:50] stretched as far and wide as it can uh<br>[13:54] globally, right? So that that's<br>[13:55] exciting. Yeah. No, no questions. Just<br>[13:58] just ready to get that moving.<br>[14:01] >> Yeah. Awesome. Yeah, that was kind of<br>[14:03] like the idea of it. It's like anything<br>[14:04] current um that might be coming up like<br>[14:07] anything the community does like the tip<br>[14:09] of the month can be I'm just going to<br>[14:11] say<br>[14:12] sign your AI models and then you know we<br>[14:16] point to the AI modeling uh like white<br>[14:19] paper kind of thing but things like that<br>[14:21] >> model transparency and all that<br>[14:24] >> as we begin to build out this whole new<br>[14:27] phenomenon about AI bombs and all that<br>[14:30] we can we we can even do some stuff<br>[14:33] around that right? I mean it's just<br>[14:35] whatever is relevant. So<br>[14:37] >> yeah.<br>[14:38] >> Listen, thank you J.<br>[14:43] >> Who who's gifty? That's<br>[14:47] >> I mean<br>[14:48] >> not to put you on the spot. Gifty<br>[14:50] >> just<br>[14:57] >> do want to welcome our our new members.<br>[14:59] I see few returning familiar faces.<br>[15:03] Um, and a few new friends. If anybody,<br>[15:08] we usually ask if anybody wants to<br>[15:09] introduce yourselves, but we just, we<br>[15:11] got holiday brain. Just jumped right on.<br>[15:15] >> I I've got a bit of an issue with my PC,<br>[15:19] my laptop. Sorry. So, um, but here I'm<br>[15:23] joining from my phone. So, okay.<br>[15:27] >> Everyone was gotten a souvenir here.<br>[15:33] Yes,<br>[15:35] I got it from visiting.<br>[15:41] >> I'm so sorry. I did not get to look at<br>[15:43] time. I was a little bit busy. Good<br>[15:46] evening for my time.<br>[15:49] >> Good evening. Yeah, for those who are<br>[15:51] joining um we officially voted in OSS<br>[15:53] Africa. So, if you want to send in your<br>[15:57] your celebratory reactions um either<br>[16:01] here in the chat or on Slack or reach<br>[16:05] out to the community members themselves.<br>[16:07] So, it's it's a great opportunity and<br>[16:09] great time right now. Um,<br>[16:12] >> yay. That's so exciting. This is S here<br>[16:15] and I'm going to be muted for most of<br>[16:16] this because I'm on a train, but I'm so<br>[16:19] excited to hear that.<br>[16:21] >> Yeah, it's so great. Today's a Today's a<br>[16:24] great day. Um,<br>[16:26] >> Marcel or Stacy, did we find the<br>[16:30] road map? Do we have a road map<br>[16:32] document?<br>[16:33] >> I could only find the one on GitHub from<br>[16:36] 2025. I could swear I I saw another one<br>[16:40] for 2026, but I cannot for the life of<br>[16:43] me find it right now.<br>[16:47] >> Yeah, I'm not using the same laptop as I<br>[16:50] was last time. So, Cash doesn't find<br>[16:52] anything.<br>[16:54] We usually post the links.<br>[17:01] If not, we just start a new one and go<br>[17:03] from there.<br>[17:05] Um, outside of the tip of the months, I<br>[17:07] guess top of mind for folks on what we<br>[17:10] want to do for next year, I know the<br>[17:12] other thing was the<br>[17:14] uh community office hours. We started<br>[17:18] pretty hashing pretty much hashing this<br>[17:20] out.<br>[17:22] So, I'll share that screen. Um,<br>[17:27] the idea was in January we kick off with<br>[17:30] a working group landscape kind of call.<br>[17:32] This is just us kind of talking through<br>[17:34] the different working groups, let people<br>[17:36] know um what we're doing and we're kind<br>[17:39] of collaborating<br>[17:41] um mixing our office hours with welcome<br>[17:44] calls just for simplicity at the moment<br>[17:47] until we can get um a leader for each of<br>[17:50] the different types of calls. Um so<br>[17:52] we'll start off with the uh working<br>[17:55] group landscape.<br>[17:57] Then in February we were thinking AI and<br>[18:01] ML working group CRA because those are<br>[18:04] two of the more um<br>[18:07] word buzz friendly at this moment. Um<br>[18:11] and then we find working groups for<br>[18:13] April. Um we can do bear in April. we<br>[18:18] can do another one um just to kind of<br>[18:21] keep things moving and here in technical<br>[18:23] initiatives I think we're also going<br>[18:26] through all the different working groups<br>[18:28] and then who<br>[18:30] would be like the point of contact<br>[18:32] person and then we can start assigning<br>[18:34] like who reaches out to start populating<br>[18:36] 2026.<br>[18:38] So that was my memory of what we kind of<br>[18:41] talked about for 2026 roadmap planning.<br>[18:45] Um there was the OSS Africa<br>[18:48] group getting um<br>[18:52] talks out there for uh that group and<br>[18:55] then I think seeing which uh conferences<br>[18:59] we want to set out next year to start<br>[19:03] targeting for confer papers.<br>[19:07] Those are I think the three top of<br>[19:08] minds.<br>[19:14] >> Yeah. So, I couldn't find a specific<br>[19:16] talk, but I did find like extensive<br>[19:19] notes um in the like meeting notes talk<br>[19:24] on November gosh, what date was that<br>[19:26] again? November 18<br>[19:29] um<br>[19:31] or you probably talked a bit quite a bit<br>[19:34] about um 2026 road map. So, yeah, as you<br>[19:37] were saying, speed engagements um also<br>[19:39] mentorships is on the list um for for<br>[19:42] that.<br>[19:44] So, I actually don't know if there's<br>[19:46] been<br>[19:47] an update on budget for<br>[19:51] that.<br>[20:00] But yeah, we should take like whatever<br>[20:01] notes we took on the 18th um so like a<br>[20:04] month ago and put that into<br>[20:07] um PR<br>[20:10] probably. Um<br>[20:12] >> here it is. Yeah. Yeah.<br>[20:17] >> All right. Um, and I'm guessing<br>[20:21] you said nothing yet on the budget. I<br>[20:25] haven't heard. Yeah, I didn't speak with<br>[20:27] Adrian. Um, I asked<br>[20:31] I think it was Kate who was going to<br>[20:33] speak with Adrian because Kate is<br>[20:34] actually our mentorship staff contact.<br>[20:39] Um,<br>[20:48] Yeah, there have been a few like<br>[20:49] questions coming in about uh like when<br>[20:54] when that's going to start again. So<br>[20:56] there's definitely interest from the<br>[20:58] community. Um and I think at the same<br>[21:01] time we need to start asking projects to<br>[21:06] um volunteer<br>[21:09] >> for the mentorship. Yeah. Yeah. Yeah.<br>[21:12] Projects to post mentees.<br>[21:17] Uh<br>[21:22] one quick note there. If there's anyone<br>[21:24] that's come into OpenSS in the last six<br>[21:27] months, like newcomer projects, it's a<br>[21:30] good opportunity to reach out to them<br>[21:33] directly<br>[21:35] and tell them this is actually a great<br>[21:37] time for them to bring on<br>[21:42] documentation.<br>[21:50] That would be great.<br>[21:59] You're breaking a cell,<br>[22:03] >> but uh love the mentorship programs get<br>[22:06] them paid. That's better.<br>[22:11] >> Yeah, you were breaking up in the middle<br>[22:13] of um the middle of your<br>[22:17] um discussion. I think yeah, the idea of<br>[22:21] the 11 pizza to have a pizza.<br>[22:22] >> Okay, can you hear me now correctly?<br>[22:24] >> Yeah, it's a bit better now.<br>[22:26] >> Oh, well uh I'll just send you this<br>[22:29] message.<br>[22:30] >> Sure, no problem. Um yeah, I I caught<br>[22:34] some of what you were saying,<br>[22:36] >> but<br>[22:36] >> I'll give up. I'm on the track,<br>[22:41] but uh<br>[22:48] >> yeah, it does sounds like the packets<br>[22:50] are moving in time.<br>[22:54] Um but I got the um reach out to new<br>[22:56] open-source projects and it might be a<br>[22:58] good opportunity to bring um<br>[23:01] contributors there.<br>[23:03] >> Yeah. Yeah. whether it's um whether it's<br>[23:06] documentation or it's it's coding um<br>[23:11] um is that maybe something you could um<br>[23:14] help us with Stacy is getting out those<br>[23:16] messages um to projects or even to<br>[23:21] working groups soliciting<br>[23:23] uh<br>[23:25] volunteers like I think we could start<br>[23:28] with some of the older projects too but<br>[23:30] >> yeah absolutely<br>[23:31] >> and like last year's thank you<br>[23:32] >> to to apply for the mentor mentorship<br>[23:34] program for next for the springtime. Is<br>[23:36] that what you're saying?<br>[23:38] >> No, I think to just get volunteer<br>[23:41] uh mentors.<br>[23:43] >> Okay.<br>[23:44] >> Yeah, because I think even if we do this<br>[23:47] summer, we want to start the process in<br>[23:49] the spring just because of how the<br>[23:50] application timelines work out.<br>[23:53] >> Um and on the LF side, they need like a<br>[23:57] month or so to get the whole dashboard<br>[24:00] thing set up. So, yeah.<br>[24:05] Like if we could target spring also that<br>[24:07] would be fine. Um I just think the<br>[24:10] timeline may be a bit tight. You would<br>[24:11] have to like be ready next month and I'm<br>[24:13] not sure we are. Um and yeah, given that<br>[24:16] we're still waiting on budget<br>[24:20] uh questions.<br>[24:22] Um<br>[24:23] yeah, we I'm not sure we can actually<br>[24:26] host anyone in the spring unfortunately.<br>[24:37] Yeah. So, I don't know what um the best<br>[24:40] approach would be, Stacey, but yeah, I<br>[24:42] he's been really good about reaching um<br>[24:45] reaching speakers for the um for the<br>[24:48] office hours. So, and I think Yeah.<br>[24:56] Awesome.<br>[25:00] Anything else on mentorships?<br>[25:07] Um, just for my own accountability, I'll<br>[25:11] probably<br>[25:12] I have like a to-do item to write a blog<br>[25:15] post about mentorship<br>[25:17] about like the lessons learned from this<br>[25:19] year.<br>[25:45] Okay, I got to call him over. I have a<br>[25:47] jumper.<br>[25:50] Um, all right. Jumping over to speaking<br>[25:53] engagements.<br>[25:55] Uh Prince, were you able to work with<br>[25:57] your your team and group to see uh<br>[26:00] speaking engagements for next year?<br>[26:02] Where you want to rank them? Where you<br>[26:04] like to go? What your priorizations?<br>[26:10] >> Yeah. Um so,<br>[26:14] um please let me get back to you on<br>[26:16] that.<br>[26:18] I think you suggested<br>[26:22] submitting a CFP<br>[26:25] for them but looking at some challenges<br>[26:29] that we anticipated to be sending to not<br>[26:33] submit but we look at others on the news<br>[26:39] I'd like to get back to you sty<br>[26:46] >> okay um let's target the first meeting<br>[26:50] of a year to just have it doesn't have<br>[26:52] to be anything perfect or well fleshed<br>[26:54] out. It's just a general idea of um<br>[27:01] uh like where you would like to speak to<br>[27:03] and even it's just a just a starting<br>[27:11] my image. Um yeah, I have a list of<br>[27:18] uh<br>[27:21] I have a list of security speaking<br>[27:24] engagements for another community. Um I<br>[27:28] think we need to do the same thing and<br>[27:30] decide which conferences we want to talk<br>[27:33] talk at um what our CFP is going to look<br>[27:37] like. Um,<br>[27:40] uh, Stacy, do we have or anyone on the<br>[27:43] call, do we have a list of dates, times,<br>[27:46] maybe locations for OpenSSF conferences<br>[27:49] next year?<br>[27:51] >> I do. Um, let me find my slide that I<br>[27:57] have internally and I can put them into<br>[28:01] uh the doc<br>[28:03] so you can see those. Give me a second.<br>[28:35] Stay safe. I don't the same.<br>[29:06] You're right. I still see uploads that<br>[29:11] I think package management form is<br>[29:14] already closed.<br>[29:17] Um<br>[29:20] I saw security con EU for March 23rd<br>[29:24] has their craft paper open.<br>[29:28] >> Uh that one I think is closed. We're<br>[29:31] working on the schedule for that right<br>[29:33] now. Um, and then the community day<br>[29:36] North America as well as open source<br>[29:39] summit North America. I think they're<br>[29:41] still building the websites on those. So<br>[29:43] those CFPs haven't been opened yet. Um,<br>[29:47] but yeah, the the open source security<br>[29:49] conu is definitely closed and because<br>[29:51] they're they're working on the agenda<br>[29:53] right now finalizing sessions.<br>[29:56] >> Go cheap. Okay.<br>[29:59] Maybe it was like that last coffee paper<br>[30:00] or something.<br>[30:02] I think um Volcon<br>[30:05] is still open. Um that one I think<br>[30:09] closes on December 22nd. I think that<br>[30:11] one's happening in Scottsdale, Arizona<br>[30:14] this year. If anyone is in the US and is<br>[30:16] traveling in the US, um but yeah, I<br>[30:20] think of the ones on this list, that's<br>[30:23] the only one that I'm super aware of<br>[30:25] being open at the moment.<br>[30:27] >> Okay. Would anybody be able to go to<br>[30:31] Voncon this year?<br>[30:36] >> Comments?<br>[30:37] >> I think I would try to apply a second<br>[30:40] time. Um, I got my my paper accepted for<br>[30:46] a talk in April, but because of the visa<br>[30:51] issues, I was unable to attend. So, I<br>[30:54] think Gracie<br>[30:58] suggested that I<br>[31:01] I reapply so that I speak this time<br>[31:03] around. So hopefully<br>[31:06] um I get to submit before the deadline<br>[31:09] and<br>[31:12] yeah,<br>[31:15] nice.<br>[31:18] Let us know how we can support and help<br>[31:21] um<br>[31:23] on that adventure. We would love to have<br>[31:25] you on this part of the world. Um but if<br>[31:29] not, we<br>[31:31] got valid passports and hopefully we'll<br>[31:33] be able to go visit you on your side of<br>[31:35] the worlds, which I think is fabulous.<br>[31:38] Um<br>[31:40] part of the uh part of the<br>[31:42] >> Go ahead.<br>[31:43] >> Please go ahead.<br>[31:46] >> All right. So um the reason why I<br>[31:49] couldn't get the visa early on was um<br>[31:53] because of the timing I got the<br>[31:57] paper accepted as a later time<br>[32:01] and so I applied same<br>[32:06] and a month to the conference date or<br>[32:10] sorry two months or so to the conference<br>[32:12] date<br>[32:14] that influenced not getting<br>[32:17] there was a long queue<br>[32:20] of folks who were had applied also. So I<br>[32:23] think that is something that um I don't<br>[32:27] know maybe it's conference organizers<br>[32:30] would have to look at<br>[32:33] it really affects um applying and<br>[32:38] getting visas from this part<br>[32:43] because if the the<br>[32:46] paper gets accepted say about a month or<br>[32:50] two months to the or three months to the<br>[32:54] conference<br>[32:56] it may be possible for folks from your<br>[32:59] end to attend but then<br>[33:03] then there's this issue when it comes to<br>[33:05] attending from Africa<br>[33:08] so<br>[33:10] that is just something I thought of<br>[33:11] adding<br>[33:14] >> would it be poss possible to apply for<br>[33:16] the visa after you submit the talk and<br>[33:18] then you know depending whether or not<br>[33:21] you get the talk<br>[33:24] you decide your travel plans.<br>[33:29] >> Um sorry I didn't get that.<br>[33:32] So, so apply for the visa as soon as you<br>[33:35] can<br>[33:37] >> like once you submit the talk and then<br>[33:41] if you're accepted then you can just<br>[33:43] like update I guess the visa process. I<br>[33:45] don't know how that works fully on uh<br>[33:47] for you. But that could be a possible<br>[33:50] avenue where you're just trying to get<br>[33:52] ahead of it. So once you are accepted<br>[33:54] cuz I'm always thinking positively<br>[33:57] um the visa is already in progress and<br>[34:00] you can just send them your acceptance.<br>[34:03] >> Okay. Can I say something?<br>[34:07] >> Thank you.<br>[34:09] >> Can you guys hear me?<br>[34:14] >> Yeah, we can hear you.<br>[34:15] >> Okay. So pertaining this visa<br>[34:18] application thing I think I don't know<br>[34:20] how it is in Ghana but in Nigeria if you<br>[34:22] want to apply for a visa like that your<br>[34:24] talk have to be accepted first then you<br>[34:27] use all the evidence put together and<br>[34:30] use it to apply for a visa for you to be<br>[34:32] able to get an approval. So that's how<br>[34:35] it works and that's like the whole<br>[34:36] limitation process. I don't know why<br>[34:39] Prince didn't mention that but that's<br>[34:41] literally how it works here. You have to<br>[34:43] need you have to have something to be<br>[34:45] able to apply for the visa. You don't<br>[34:46] just apply for the visa. That's how<br>[34:49] strict it is with us here.<br>[34:55] >> Okay. Thank you for that.<br>[34:58] >> No, that's that's actually really good<br>[35:00] to know. Um because I was thinking<br>[35:03] at least for the events that OpenSSF<br>[35:06] hosts, would it be possible to have? I<br>[35:09] mean actually before I speak I should<br>[35:11] just look um<br>[35:15] there are quite a bit of um<br>[35:21] travel.<br>[35:23] Okay.<br>[35:25] So there is already like a visa<br>[35:26] information section on open source<br>[35:28] summit North America for example. I know<br>[35:30] it's not hosted by OpenSSF, but I I<br>[35:32] imagine it's a similar a similar format<br>[35:35] on the website. Um, what I've seen in<br>[35:38] other conferences is that they actually<br>[35:39] say, you know, uh, if you plan to travel<br>[35:43] here, you should we recommend that you<br>[35:46] start applying around this time. Um, is<br>[35:49] there something and the conferences<br>[35:50] offer to write letters. So<br>[35:54] is that something that we could do for<br>[35:56] um OpenSSF hosted conferences?<br>[35:59] >> Oh, sure. That's something that could<br>[36:01] work. So if there is any proof or sign<br>[36:04] that um Open SSF could give out to<br>[36:07] persons that are going to apply for<br>[36:08] visas even before their speaking<br>[36:10] engagements are accepted, that would<br>[36:12] work. That would be very perfect.<br>[36:17] >> Okay.<br>[36:20] So, I don't know about Voncon<br>[36:24] um and who manages that, but maybe as a<br>[36:29] group we target North America.<br>[36:32] Um<br>[36:34] send get the letter because we got a<br>[36:35] little bit of time. get the letter,<br>[36:38] submit some bare working group talks,<br>[36:42] um help advertise OSS Africa group and<br>[36:46] um<br>[36:49] and then maybe have like a bear meetup<br>[36:52] or something. That's my thoughts around<br>[36:54] it. Love to hear audio.<br>[36:57] >> Um Stacy said in the comments that they<br>[37:01] we do not write this types of letters to<br>[37:04] her knowledge.<br>[37:14] >> I'm sorry in the chat.<br>[37:16] >> Yeah, we can't write anything ahead of<br>[37:19] time. Um, and that's not something that<br>[37:22] we can do from the OpenSSF perspective.<br>[37:25] Um, I know that the larger conferences<br>[37:27] like CubeCon and things like that<br>[37:30] provide letters. Um, but OpenSSF does<br>[37:33] not as far as I know. I will double<br>[37:35] check on that just to make sure that our<br>[37:36] 2026 policy isn't changing. Um, but I<br>[37:40] can follow up.<br>[37:43] Okay. So, um, please go ahead.<br>[37:47] >> No, go ahead, Prince.<br>[37:51] All right. Okay. So, um I think the<br>[37:54] Linux Foundation I I got a letter for<br>[37:57] the open source summit this past<br>[38:01] November, but there was a similar issue<br>[38:04] with the visa. So, I was unable to<br>[38:06] attend as well. So um I don't know if it<br>[38:10] is possible to get it through the Linux<br>[38:13] Foundation<br>[38:14] but that is if you um you are receiving<br>[38:18] sponsorship from um<br>[38:25] from the Linux Foundation or the Open<br>[38:27] SSF and I don't know if that qualifies<br>[38:31] here of<br>[38:33] yeah that's that's that was my<br>[38:36] experience So perhaps if um the Linux<br>[38:40] foundation or the open as a ser is a<br>[38:43] sponsor for a particular conference.<br>[38:48] Um<br>[38:51] >> so I think most<br>[38:53] >> okay sorry<br>[38:55] >> please go ahead.<br>[38:56] >> I think most of these things make sense<br>[38:59] if um maybe you apply for a talk and you<br>[39:02] are a speaker already. Most of these<br>[39:04] things make sense. So if it is possible<br>[39:06] for the applications to go out early and<br>[39:09] approval to come in earlier, I feel do<br>[39:12] this conversations would not be<br>[39:15] necessary because this later will be um<br>[39:19] right in hand for a speaker.<br>[39:25] >> What what other comes to mind to me is<br>[39:28] like what other requirements will allow<br>[39:30] for visa? like what if you're<br>[39:32] volunteering for the conference or<br>[39:35] you're setting up a booth. Um because<br>[39:38] what I'm envisioning is like having uh<br>[39:41] open SSF I'm sorry OSS Africa come in<br>[39:46] maybe with its own booth or like having<br>[39:49] its own that way maybe we can get open<br>[39:52] SSF to agree with that and then that<br>[39:56] shows that you're needed for the<br>[39:57] conference while we wait for the talks<br>[40:00] to be approved. That's just<br>[40:03] what I'm thinking of.<br>[40:09] It all has to get approved on on all<br>[40:11] parties, but um if the need is if the<br>[40:16] visa<br>[40:18] is to speak and potentially work at a<br>[40:20] conference or represent your<br>[40:22] organization<br>[40:24] um at a conference, uh that way you can<br>[40:27] start submitting it earlier<br>[40:30] um once we get the okay and approval<br>[40:32] from OpenSSF and the Linux Foundation.<br>[40:36] um<br>[40:38] because I don't see them<br>[40:40] approving ahead of time.<br>[41:00] Okay, I see a thumbs up. Um yeah, I<br>[41:02] think it's just we got to talk to Open<br>[41:04] SSF and then Um,<br>[41:08] uh, Prince, if you can understand and<br>[41:10] learn a little bit more of what's the<br>[41:11] requirement for the visa and in the<br>[41:13] conference,<br>[41:15] um, we can work with that and see how to<br>[41:19] get you some proof of evidence soon. It<br>[41:22] might mean that you have to work more at<br>[41:23] the conference, but um,<br>[41:27] it's all in the name of open open source<br>[41:29] Africa.<br>[41:38] Yes, sure. Um, I I'll<br>[41:43] work with you on that.<br>[41:52] >> Yeah. And to Marcela's comment, it it<br>[41:55] does seem like it's more of an issue of<br>[41:56] the timing, especially if you're trying<br>[41:58] to get folks from other areas around the<br>[42:02] world to join.<br>[42:18] Yeah.<br>[42:20] Yeah. I felt those travels.<br>[42:22] more expensive too.<br>[42:26] >> Yeah. Like I mean<br>[42:30] sometimes very you know just a month or<br>[42:34] slight less than a month times even the<br>[42:37] travel um that can be tricky with um<br>[42:41] uh like requesting travel funding and<br>[42:44] stuff like that.<br>[42:50] >> Okay. So I think we just have<br>[42:53] conversations and research to do for<br>[42:56] this. Um<br>[43:01] most of the group right now is in Africa<br>[43:03] and<br>[43:06] uh the US. We have a few in Europe.<br>[43:10] So<br>[43:12] uh<br>[43:15] maybe we think of what we want to talk<br>[43:18] about. Um<br>[43:21] or we can shift over to the next topic<br>[43:25] which is uh office hours.<br>[43:30] We do have like<br>[43:32] 14 months left.<br>[43:50] Anybody interested in either topics?<br>[43:53] Talking about maybe what we're we would<br>[43:55] submit talks on or seeing how we plan<br>[43:59] out and maybe getting the first um<br>[44:04] office hours kind of planned.<br>[44:13] I'm looking up to see when that first<br>[44:15] office hour is scheduled.<br>[44:22] We do have one at the end of this month<br>[44:23] that we have to get cancelled.<br>[44:27] >> Yeah.<br>[44:28] Yeah. And the next one the one the first<br>[44:31] one in January is on the 22nd.<br>[44:34] >> Okay. Oh,<br>[44:36] >> there's two there's two calls before<br>[44:39] that.<br>[44:47] >> Um, and that one was the welcome column<br>[44:51] and this was just talking about all the<br>[44:52] working groups.<br>[44:54] And this one we wanted to reuse<br>[44:58] the slide from the opens booth<br>[45:04] that we had in uh OSS North America<br>[45:08] this year<br>[45:11] unless it's been updated.<br>[45:13] >> Yeah. Uh<br>[45:17] I haven't updated this slide.<br>[45:23] Um, and yeah, who's actually going to<br>[45:28] give the working group landscape? It can<br>[45:30] be one of us for sure. Um,<br>[45:34] in like future calls, we'll have working<br>[45:36] group.<br>[45:38] Um,<br>[45:41] >> yeah, we'll have like working group uh<br>[45:43] chairs like come in and do that.<br>[45:48] >> Yeah, if anything, we could split it.<br>[45:50] One person talks hashes at the other the<br>[45:52] other half or something.<br>[45:55] Um,<br>[45:58] and I know Sally has sent me the<br>[46:01] template before. I just don't know if we<br>[46:03] already have something like this.<br>[46:07] I'll take that actually.<br>[46:13] Okay.<br>[46:19] I think Sally Cooper just um Sabi<br>[46:24] mentioned writing a blog post<br>[46:27] introducing<br>[46:31] USS Africa.<br>[46:34] So<br>[46:36] >> I love<br>[46:38] Stacey here. So she mentioned that Stacy<br>[46:43] and I work on it. I don't know if you've<br>[46:46] seen it, Stacey.<br>[46:50] So perhaps we work on that together and<br>[46:56] get it out.<br>[47:02] >> That' be awesome.<br>[47:10] Um,<br>[47:13] I know the the blog that EG wrote and S<br>[47:16] wrote,<br>[47:18] >> I think that was recently released if<br>[47:19] I'm not mistaken or still in the review.<br>[47:23] >> No, I saw it go out uh part three.<br>[47:27] >> Part three.<br>[47:28] >> Yeah, I think that went out this week.<br>[47:31] Um<br>[47:33] yeah, actually I was thinking because of<br>[47:36] the um kisser and s did did all that<br>[47:40] work. Um<br>[47:43] not to not to volunteer you without<br>[47:45] asking um but a would you be willing to<br>[47:48] um speak as part of the<br>[47:51] um working group landscape?<br>[47:54] Um<br>[47:55] >> oh sure.<br>[47:57] >> Sure, sure.<br>[47:58] >> Thank you. Yeah. And we can ask S too if<br>[48:01] if they're available or not. Um.<br>[48:07] >> All right.<br>[48:07] >> Cuz yeah, you guys are honestly the<br>[48:10] experts<br>[48:11] on the working groups.<br>[48:14] >> That's true.<br>[48:16] >> Yeah. You just take what's in the blog<br>[48:17] and put it in the presentation and<br>[48:37] All right. Um, she sent me one before,<br>[48:40] so I may have it already on Snag.<br>[48:43] Um,<br>[48:47] okay.<br>[48:51] same reason.<br>[48:53] And um<br>[48:56] for the last couple minutes,<br>[48:59] let me know any last thoughts or areas<br>[49:02] of focus.<br>[49:10] Um I would just like to say that I<br>[49:13] posted in the general channel. Um<br>[49:18] what day was that? a few days ago, I<br>[49:20] think it was December 9th, there is a a<br>[49:23] form uh asking folks if they can um fill<br>[49:28] out uh I I'll put the the form link in<br>[49:31] the chat here. Um but basically, we're<br>[49:34] trying to figure out like where our<br>[49:36] community is located so that we could um<br>[49:39] support uh efforts for travel and uh<br>[49:43] event attending and things like this. uh<br>[49:46] Devril and ambassador program uh<br>[49:48] possibilities um for particular regions<br>[49:51] all over the globe. Um so it's just so<br>[49:54] that we know kind of where our community<br>[49:55] is. Um so if you're able to give us that<br>[49:59] feedback uh that would be great. Um and<br>[50:02] yeah, we'd really appreciate it.<br>[50:13] >> Thank you. Yeah, I think I think I<br>[50:14] populated I added the um the template<br>[50:18] the Open SSS slide template to the chat<br>[50:20] and the notes.<br>[50:24] So if you want to kick that off<br>[50:27] next year doesn't have to be now<br>[50:29] holidays are coming up. Um<br>[50:34] there<br>[50:36] I think that's it that I had any<br>[50:40] other conversation talking points for<br>[50:42] the next seven minutes.<br>[50:50] I'm sorry Stacey. You mentioned<br>[50:52] something about a link you dropped in<br>[50:54] the general channel. Please can you I<br>[50:57] can't see it. I'm checking it.<br>[51:03] It's also in the chat.<br>[51:04] >> Oh, okay.<br>[51:06] >> It's the form<br>[51:08] forms.<br>[51:10] Joey, I think<br>[51:18] yeah, the forms.j is uh OpenSSF is<br>[51:21] trying to determine where everyone's<br>[51:23] located so they can do meetups. And then<br>[51:26] um the last link I sent is the template<br>[51:31] for OpenSSF slide deck<br>[51:34] that could be used for January's uh<br>[51:36] welcome call about all the other working<br>[51:38] groups.<br>[51:48] >> Oh, I'm sorry. I'm muted. Okay. All<br>[51:50] right. I I was answering you. I I forgot<br>[51:52] I was muted.<br>[51:54] >> You're good.<br>[52:02] All right, if there's no other talking<br>[52:04] points, um, big congratulations to<br>[52:07] Marcelo who's going to continue in the<br>[52:09] tech next year. Go ahead and shoot in<br>[52:12] your congratulations.<br>[52:15] >> Yes. Yeah, I saw I was like, yay.<br>[52:18] And then uh big congrats to uh OSS<br>[52:22] Africa for being official sake.<br>[52:26] So sending your reacts and yeah you're<br>[52:29] dancing. There you go.<br>[52:32] Looks like Prince and Seth are in the<br>[52:33] same spot like right next to each other.<br>[52:35] Um<br>[52:37] and with that, thank you so much for all<br>[52:40] your contributions, your helping support<br>[52:42] this year. Enjoy the holidays uh for<br>[52:46] those that celebrate<br>[52:49] and happy new year's will. We'll catch<br>[52:51] you in 2026<br>[52:54] to be here and thank you for being such<br>[52:57] a researcher.<br>[53:00] I try part of my day job.<br>[53:03] >> Thank you very much.<br>[53:06] >> Thanks everyone. Have a good one.<br>[53:08] >> Thank you everyone.<br>[53:09] >> Happy holidays.<br>[53:10] >> Happy holidays.<br>[53:11] >> Bye. Happy holidays.<br>[53:16] Bye<br>[53:19] >> bye. <!-- deep-read:sections end -->