> For the complete documentation index, see [llms.txt](https://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://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-committees/open-source-committee-osc.md). # Open Source committee (OSC) {% hint style="info" %} View more details in the dedicated Committee space [opensourcecommittee.docs.intersectmbo.org](https://opensourcecommittee.docs.intersectmbo.org/) {% endhint %} ## What is the Open Source committee? Intersect’s Open Source Committee fosters the development and evolution of Cardano as a community-led, decentralized open-source project. Our mission is to support the growth of Cardano through community-driven decision-making. By delivering essential tools, establishing clear policies, and providing expert guidance, we ensure Cardano remains adaptive, accessible, and positioned for long-term success. ## Why is this committee important? The committee acts as a rallying point for members to get advice on building in an open-source environment. ## Which topics does this committee cover? * Manage and oversee the allocation and use of OSC Budget * Provide strategic direction and input on Intersect's open-source initiatives and policies * Review and approve the OSO Annual Roadmap * Manage and lead various working groups * Evaluate the output of working groups and the OSO * Oversee OSO Project Support Services, such as project selection and vendor review ## How to join? * The Open Source Committee is held publicly every other Thursday at 2-3pm UTC. This call is [open to everyone](https://meet.google.com/eeb-qjbx-agw). If time permits, there is an open-ended questions section at the end of each meeting. * Members can also participate in the Discord thread [#open-source-committee](https://discord.com/channels/1136727663583698984/1158760831203430470) under Intersect’s Discord page. * The OSC participates in Intersect committee elections to select the next cohort of members. Intersect always communicates details on how to apply and vote well in advance of each election. ## Extra info or links * The OSC approved governance policy can be found [here](https://intersect.gitbook.io/open-source-committee/policies/governance) * Learn more about the Paid Open Source Model [here](https://committees.docs.intersectmbo.org/intersect-open-source-committee/about/open-source-office-oso/intersecting-open-source-and-sustainability-a-paid-open-source-model-for-ecosystems) *** --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-committees/open-source-committee-osc.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 `build a script that syncs our docs to a CMS` 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.