> For the complete documentation index, see [llms.txt](https://opensourcecommittee.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opensourcecommittee.docs.intersectmbo.org/about/open-source-office-oso/partnerships/todo-group.md). # TODO Group TODO: https\://todogroup.org/blog/todo-member-intersect/ We are excited to announce that Intersect's Open Source Office has joined the TODO Group, a renowned community of open source practitioners dedicated to enhancing Open Source Program Offices (OSPOs) worldwide. **How This Partnership Enhances Intersect:** * **Access to Best Practices:** By collaborating with the TODO Group, we gain insights into industry-leading strategies for managing and scaling our open source initiatives, ensuring we align with global standards. [todogroup.org](https://todogroup.org/resources/guides/how-to-create-an-open-source-program-office/?utm_source=chatgpt.com) * **Community Engagement:** This partnership enables us to connect with a vast network of OSPO professionals, fostering knowledge exchange and collaborative growth within the open source ecosystem. * **Resource Enrichment:** Membership provides us with a wealth of resources, including training modules, guides, and case studies, empowering our team to drive innovation and efficiency in our open source projects. Joining the TODO Group signifies our commitment to advancing open source excellence at Intersect, leveraging collective expertise to benefit our community and stakeholders. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://opensourcecommittee.docs.intersectmbo.org/about/open-source-office-oso/partnerships/todo-group.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.