Skip to content

Files

Latest commit

b9c0906 · Jan 9, 2025

History

History
100 lines (52 loc) · 5.75 KB

README.md

File metadata and controls

100 lines (52 loc) · 5.75 KB

👋 Open Community and Resource Hub for Open Source Managers and OSPO Practitioners

ospo-todoorg-readme-cover

License License GH Discussions Newsletter

TODO is an open community of practitioners who aim to create and share knowledge, collaborate on practices, tools, and other ways to run successful and effective Open Source Program Offices or similar Open Source initiatives. TODO Group is formed by its Community participants and General Members.

🚀 Learn from a diverse community of professionals with years of experience building OSPOs wordwide

“There is no broad template for building an open source program that applies across all industries — or even across all organizations in a single industry. That can make its creation a challenge, but you can learn lessons from other organizations (companies, academic institutions, governments, and more) and bring them together to fit your own organization’s requirements."

Founded in 2012, the TODO Group is a place to share experiences, develop best practices, and work on common tooling to improve OSPO adoption and education.

📝 Discover the TODO resources and initiatives

TODO resources are open to everyone and available at TODO Group GitHub repo under Creative Commons Attribution 4.0 International Licence (non-code contributions) or Apache License, Version 2.0 (code contirbutions). We encourage people to share their knowledge and help to grow this community by adding their contributions to the different TODO initiatives such as:

💬 Network

Connect with experienced OSPO professionals and industry supporters across sectors. Choose the best format that better fits your needs!

  • Touchpoints: monthly community meetings with featured topics and speakers, and informal discussions.
  • OSPO Discussions: general OSPO threads proposed by the community
  • Real-time Chat Conversations: real-time conversations to connect with peers in the OSPO community

✏️ Resources & Education

Resources created by experienced professionals to keep learning about OSPOs

  • Glossary -- Common terms and definitions of OSPO
  • Studies -- Maturity model, surveys, and reports to help your OSPO journey
  • MindMap -- Responsibilities, roles, behavior, and team sizes within OSPOs
  • Training Modules -- Free and open courses covering everything you need to know
  • Guides -- open source program management best practices for organizations
  • Case Studies Real case studies showcasing the impact of OSPOs on organizations worldwide
  • OSPO Policies

🔭 Adoption

Join the OSPO movement!

How many OSPOs are out there? Which are the different tools within the OSPO tool infrastructure? Which communities are OSPO supporters? Explore the OSPO Ecosystem and help us build together this Landscape to give visibility of OSPOs worldwide!

📈 Research

A list of research around open source and OSPOs, as well as relevant quotes.

⚙️ Tools

OSPO tooling started by the TODO Group community members:

  • RepoLinter: Lint open source repositories for common issues.

🧑‍🎨 Design & Brand Identity

📢 Communications & News

✍️ DCO and Sign-Off for contributions

The TODO Charter requires that contributions are accompanied by a Developer Certificate of Origin sign-off. For ensuring it, a bot checks all incoming commits.

For users of the git command line interface, a sign-off is accomplished with the -s as part of the commit command:

git commit -s -m 'This is a commit message'

For users of the GitHub interface (using the "edit" button on any file, and producing a commit from it), a sign-off is accomplished by writing

Signed-off-by: Your Name <YourName@example.org>

👋 Get in touch

Follow TODO Group LinkedIn Profile and join the Slack!