# 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)).

#### Quality Assurance

Because open-source projects rarely live in isolation, OEC takes Quality Assurance (QA) as well security and vulnerability management very seriously. Before code is release OEC performs various automated and manual testing.

#### 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 

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