> For the complete documentation index, see [llms.txt](https://governance.opendataproducts.org/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://governance.opendataproducts.org/v1/readme.md). # Governance of Open Data Product Specification How Open Data Product Specification development is governed ## Why do we need governance? Adopting a governance model and drawing up a project governance document as early as possible is critical for the creation of a successful open development project. A successful open development project needs to be welcoming to those who are likely to contribute in a way that improves project sustainability while preventing those with incompatible needs from wasting their own time and that of the project team in fruitless engagements with the project. In order to be effective, a governance document needs to be concise, accessible, and easy to refer to. It should focus on the main aspects of the decision-making structure and mechanism but needs to be flexible enough to address the increasing complexity associated with the growth of its community and interaction with the external world. The above summarizes the need for this document. ## How to contribute We welcome all contributions, but you need to follow the given process and guidelines. Read more from [Contributions](/v1/contributions.md) ## Decision-making ## Consistent versioning drives adoption ## Controlled releases Our release model and related processes are described in the [Decision-making processes section](/v1/decision-making-process.md) --- # 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://governance.opendataproducts.org/v1/readme.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.