> 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/contributions.md).

# Contributions

To ensure consistency and transparency in ODPS development we have defined a process to follow in order to contribute. 

We have different processes for breaking and non-breaking changes simply because we need to assure backwards compatability in versions. Read more about versioning from separate page under Specification: [Versioning practices](/v1/specification/versioning-practices.md) 

If you don't know is the change breaking change or nor, don't worry. Follow the standard process and maintainers will make the jugdment and act accordingly. But of course optimal solution is known or suspected breaking change cases is to use given process. That speeds up the processing and possible merge. 

### Contributions require lightweight Contributor Agreement

But don't worry. This process could be hard and heavy. In some cases, it has to be hard and heavy. We are still a bit relaxed with this requirement. If you raise and issue or make a feature request, or propose improvement in Github (the only way to contribute in the ODPS), you are notified that by using the issue reporting you to accept the [Contributor Agreement](/v1/contributions/contributor-agreement.md). Link to Contributor Agreement is presented in issue templates along with notice text of approval. 

We also utilize Github built-in "contributors to sign off on web-based commits" function. 

An example of the above is the template (below) in Github we use for improvement ideas. The same model is used in bug reports

<figure><img src="/files/m404XSngoCnY5WeoRkZ6" alt=""><figcaption></figcaption></figure>

Later on, we might need to go to a heavier and more formal process of requiring signed CAs but for now, we proceed with this lightweight model.&#x20;


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://governance.opendataproducts.org/v1/contributions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.