- Read and understand the [legal requirements when contributing code](/concepts/legal-reqs/). In particular, note that you must:
- add a copyright notice to the top of all files you modify or create (if one isn't there already).
- include a Signed-off-by line in all your Git commit messages.
- Look through the [dev-ocean repository on GitHub](https://github.com/oceanprotocol/dev-ocean). It summarizes Ocean Protocol software development practices and policies.
- Ask technical questions in the [Ocean Protocol chatroom on Gitter](https://gitter.im/oceanprotocol/Lobby).
- Find repository-specific development notes in each repository (usually in the root `README.md` file).
To report a bug that isn't a vulnerability, go to the relevant GitHub repository, click on the Issues tab, click on the New issue button, and read the instructions.
To write an issue, go to the relevant GitHub repository, click on the Issues tab, click on the New issue button, and read the instructions.
## Make a Feature Request or Proposal
To make a feature request or proposal, you can go to the [🐙 Ocean Protocol Enhancement Proposals (OEPs)](https://github.com/oceanprotocol/OEPs/) repository and write a proposal.
- [Read the announcement of the Ocean Protocol Ambassador Program](https://blog.oceanprotocol.com/envoys-of-the-new-data-economy-ocean-protocol-ambassadors-3816a0e63611)
- [Apply to become an ambassador](https://oceanprotocol.com/#ambassadors)