Anna: This section sets up Community Tech-Leads. Treat it as the frame for the decisions, handoffs, and evidence that appear in the next slides.
Greg: The practical question is simple: by the end, what should a junior IT professional be able to explain, check, or document in a real workplace?
Anna: Our opener frames community tech-leads as connective tissue because they sit between governance, engineering and contributor care. Once a project grows past a couple dozen maintainers, somebody has to watch the whole ecosystem.
Greg: Right, otherwise RFCs stall, moderation escalations slip, and users lose trust. That ratio call-out—one tech-lead per 150 to 250 active contributors—gives learners a benchmark for when to lobby their foundation for funding the role.
Anna: On the responsibilities slide we emphasise facilitation as much as technical leadership. Tech-leads host backlog triage, shepherd RFCs and ensure incident responses loop back into documentation.
Greg: And they are the culture keepers. Calling out inclusive communication, mentorship pipelines and reporting to sponsors signals that this role is accountable to people, not just code.
Anna: Bridging community & engineering focuses attention on a concrete part of the work. Hosts contributor office hours across time zones and languages, Converts user research, localisation feedback and Indigenous data protocols into actionable issues, and Maintains tooling for translation, documentation builds and contributor analytics.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Converts user research, localisation feedback and Indigenous data protocols into actionable issues; Maintains tooling for translation, documentation builds and contributor analytics; Negotiates with corporate stakeholders to ensure funding aligns with community roadmap.
Anna: The bridge slide paints the tech-lead as translator—turning localisation, Indigenous data sovereignty requirements and user research into engineering tickets.
Greg: Exactly, and the workflow slide anchors that translation in a daily cadence. Learners see how office hours, merge queue triage and mentoring rosters all live on the same calendar.
Anna: For pathways we wanted to show this isn’t a mysterious promotion—you can come through long-term contribution, fellowship programs or corporate OSPO rotations.
Greg: Including iwi digital innovation hubs reinforces that Indigenous technologists belong in these roles. The 4 to 6 year experience band sets expectations for skill depth without gatekeeping specific degrees.
Anna: The skills slide leans into empathy, multilingual communication and systems thinking because tech-leads spend most of their time orchestrating people, not just writing code.
Greg: We also highlight calm incident facilitation and documentation-first habits—those are the traits that reduce burnout and make governance transparent to new contributors.
Anna: The team slide shows how tech-leads partner with community managers, legal counsel and accessibility experts. It grounds the abstract role in a concrete staffing model.
Greg: Calling out stipend advocacy and data-sharing up to boards also keeps the justice lens present—tech-leads are accountable for equitable recognition, not just sprint velocity.
Anna: For progression we mapped a lattice: maintainer to tech-lead to ecosystem leadership, with lateral moves into OSPOs, developer relations or policy work.
Greg: That helps students see longevity—this isn’t a cul-de-sac role. It can lead to foundation CTO seats or Indigenous data sovereignty leadership, which signals strategic impact.
Anna: We close by reminding learners that investing in tech-leads is about sustaining trust and resilience, not just adding another title.
Greg: Exactly—funding this role protects values, speeds reviews and keeps governance tethered to community reality. That’s the north star for Part 7.