This repo serves as a touchpoint for a new repo under github.com/todogroup that consolidates information about all active TODO Group working groups. The repo itself is intended as a navigation hub: missions, meetings, and communication channels live here.
This repository does not host the deliverables themselves. It exists so that newcomers and existing community members can quickly find their way to
the right working group and the repo where the work is actually happeningn(ospology, chaoss/wg-ospo, awesome-ospo, and others).
- What is a TODO Working Group?
- Active working groups at a glance
- Working group details
- How to join a working group
- Working group lifecycle and inactivity policy
- License
Within TODO, working groups (WGs) are the spaces where the community collaboratively builds frameworks, books, guides, metrics, and tooling for open source and AI management and oprerations. Working groups are:
- Open to everyone. You don't need to be a Linux Foundation or TODO Group member to participate. Just join the channel, the call, or open a pull request.
- Community-driven. Direction is set by the participants. The Steering Committee approves the formation of new working groups and provides scaffolding to keep them sustainable, but it does not run them.
- Public. Calls follow Chatham House Rules, meeting agendas are tracked in GitHub Discussions, and deliverables are released under permissive licenses (CC-BY 4.0 for content,Apache 2.0 for code).
If you're new to the TODO Group, start with the community onboarding guide and the TODO Charter.
| Working group | Focus | Meeting cadence | Slack | Working repo |
|---|---|---|---|---|
| 📖 OSPO Book WG | A collaborative reference book for organizations building or running OSPOs. | See TODO Calendar | #project-ospobook |
ospology/ospo-book |
| 🧩 OSS in Business WG | Articulating the business value of open source for executives and decision-makers. | See TODO Calendar | #wg-oss-in-business |
ospology/whitepapers/business-value |
| 📊 CHAOSS OSPO Metrics WG | Defining metrics that demonstrate the value of open source projects and OSPO programs. Joint effort with CHAOSS. | See TODO Calendar | #wg-ospometrics-chaoss |
chaoss/wg-ospo |
| 🤖 Agentic AI to Empower OSPOs WG | Exploring how agentic AI workflows can scale OSPO operations (compliance, intake, project health, advocacy). | #wg-agentic-ai |
Mission. Maintain and expand the OSPO Book, a collaboratively authored reference for organizations developing strategies to use, contribute to, or create open source projects through Open Source Program Offices.
Status. Active development (v1.0).
Where the work happens.
- 📂 Working repo:
todogroup/ospology/ospo-book - 🌐 Published book: https://ospobook.todogroup.org/
Communication channels.
- 💬 Slack:
#project-ospobook(in the TODO Slack) - 📧 Mailing list: https://lists.todogroup.org/g/WG-ospo-book-project
- 📅 Meetings: see the TODO Group Community Calendar
How to contribute. Read the
contribution guidelines in the working repo
and open a PR or issue. New chapters are proposed via
GitHub Discussions in ospology
under the Ideas or proposal labels.
Mission. Produce the OSS in Business Guide — a vendor-neutral resource that articulates the business value of open source and helps organizations connect open source activity to strategic outcomes: innovation, risk management, cost efficiency, and long-term sustainability. The guide is aimed at decision-makers, OSPO practitioners, and stakeholders outside engineering.
Status. Draft, active development.
Where the work happens.
- 📂 Working repo:
todogroup/ospology/whitepapers/business-value
Communication channels.
- 💬 Slack:
#wg-oss-in-business - 📧 Mailing list: https://lists.todogroup.org/g/WG-oss-in-business
- 📅 Bi-weekly call — see the TODO Group Community Calendar
How to contribute. Pick up an open workstream in the working folder,
introduce yourself in #wg-oss-in-business, and join the bi-weekly
call. PRs against the whitepaper outline are welcome from anyone.
Mission. Advance how organizations understand and communicate the value of open source projects and the value of the programs and initiatives that support them. The WG defines metrics, metrics models, and best-practice guidance for OSPOs to demonstrate impact.
This is a joint working group between the CHAOSS Project and the TODO Group, with co-chairs from both communities.
Status. Active. Co-chairs: Gary White and Dawn Foster.
Where the work happens.
- 📂 Working repo:
chaoss/wg-ospo - 🌐 CHAOSS metrics catalog: https://chaoss.community/kbtopic/all-metrics/
- 🧭 CHAOSS WG overview: https://chaoss.community/kb/working-groups/
Communication channels.
- 💬 Slack:
#wg-ospometrics-chaoss(TODO Slack) and the CHAOSS Slack - 📅 Bi-weekly call, Thursdays 11:00 US Central / 18:00 CET — see the TODO Group Community Calendar and the CHAOSS calendar
How to contribute. New metrics are proposed as PRs in
chaoss/wg-ospo following the
CHAOSS metric template. Discussion items are surfaced in either the
TODO or CHAOSS Slack and reviewed on the bi-weekly call.
Mission. Explore, document, and share patterns for using agentic AI to scale OSPO operations. Likely areas of focus include: compliance and license review, internal Q&A and policy navigation, project-health monitoring, intake of inbound/outbound requests, and operational metrics.
The WG sits at the intersection of the TODO Group's 2026 strategic direction (helping OSPOs demonstrate value across AI and security) and the broader Linux Foundation Agentic AI Foundation ecosystem.
ℹ️ This WG is in formation. The sections below will be filled in as the founding charter, channels, and meeting cadence are confirmed by the Steering Committee. Pull requests welcome.
Status.
Where the work happens.
- 📂 Working repo:
- 🗨️ Origin discussions: see the touchpoint BoF outcomes on OSPO + AI.
Communication channels.
- 💬 Slack:
#wg-agentic-ai - 📧 Mailing list:
- 📅 Meetings:
Related content.
How to contribute. Until the WG is fully bootstrapped, share use
cases, prompts, and prototypes in the channels above and propose new
artifacts via ospology GitHub Discussions.
There is no formal membership for TODO working groups. To get involved:
- Join the TODO Slack and the working-group-specific channel listed above.
- Subscribe to the working group's mailing list (if one exists) on https://lists.todogroup.org.
- Add the meeting to your calendar via the TODO Group Community Calendar.
- Show up to a call or open a PR — both count as participation.
- Sign your commits with the
Developer Certificate of Origin
(
git commit -s). Required for all contributions to TODO repos.
💡 You don't need to be a TODO General Member or OSPO Associate to contribute. Working groups are open to all.
TODO has an inactivity policy for working groups, Slack channels, and mailing lists (source: governance repo):
- Phase 1 - 3 months of no activity. A working group participant, chair or steering committee liaison notifies The TODO Project Manager of this inactivity, then posts a warning to the channel and mailing list and asks for volunteers to re-engage.
- Phase 2 - no volunteers after 2 weeks. The PM archives the related materials, officially closes the WG, and notifies the Steering Committee. The closure is recorded as a GitHub Discussion for transparency. Archived materials remain available; nothing is deleted.
Documentation in this repository is licensed under the Creative Commons Attribution 4.0 International License (CC-BY-4.0).
Any code contributions are licensed under the Apache License, Version 2.0.
This follows the licensing convention used across the TODO Group GitHub organization.