> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/contributions-and-quality-assurance.md).

# Contributions & Quality Assurance

#### Contributions

It takes a lot of hard work to build an open source tech stack and contributions to OEC repositories are warmly welcomed within the Ocean Enterprise [ GitHub](https://github.com/OceanProtocolEnterprise) organization.

All Ocean Enterprise code (software) is licensed under an [GLP3.0 (GNU General Public License version 3)](https://www.gnu.org/licenses/gpl-3.0.en.html) a strong copyleft license that ensures software remains free and open source.

All contributions to the Ocean Enterprise code are also licensed under the GLP3.0 license.\
\
If you are a current member of the Ocean Enterprise Collective e.V then there is nothing extra for you to do: licensing is already handled.\
\
If you are not a current member of the Ocean Enterprise Collective e.V then you are considered to be an "external contributor".  All external contributors are welcome to open an issue in the Ocean Enterprise GitHub repositories specifying in detail the recommendation or bug they have found. Comments submitted by external contributors should clearly indicate if the comment relates to an improvement or a bug.  Please remember to be respectful in the comments, as outlined in the Contributor Code of Conduct ([LINK](https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/code-of-conduct)).

#### Automated Testing

* Comprehensive test suite running on CI
* Code coverage requirements (e.g., >80%)
* Performance regression tests
* Security scanning (dependency checks, SAST tools)

#### Manual Testing&#x20;

* Installation/upgrade procedures
* Critical user workflows
* Platform-specific testing (OS, browsers, etc.)
* Accessibility compliance
* Documentation accuracy


---

# 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://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/contributions-and-quality-assurance.md?ask=<question>&goal=<user_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.
