To report a bug that isn’t a vulnerability, go to the relevant GitHub repository, click on the Issues tab and select Bug report.
Before reporting a bug, search existing open and closed issues and PRs to see if something has already been reported. If not, then go ahead and create a new bug report, following the structure suggested in the issue template.
To report a vulnerability, you may do so in a less public manner.
Use the Issues section of each repository and select Feature request to suggest and discuss any features you would like to see added.
As with bug reports, search existing open and closed issues and PRs to see if something has already been reported.
We’d love to have you contribute to any repository within the
oceanprotocol GitHub organization!
Before you start coding right away, please follow those basic guidelines:
- If no issue for your case is present, open one first before starting to work on something, so it can be discussed.
- Make yourself familiar with eventual repository-specific contribution requirements and code style requirements.
- Because of the weird world of intellectual property, we need you to follow the legal requirements for contributing code.
- Be excellent to each other, as outlined in our Contributor Code of Conduct.
A typical code contribution in any Ocean Protocol repository would go as follows:
- As an external developer, fork the respective repo and push to your own fork. Ocean core developers push directly on the repo under
- You should create a new branch for your changes. The naming convention for branches is:
issue-001-short-feature-description. The issue number
issue-001needs to reference the GitHub issue that you are trying to fix. The short feature description helps to quickly distinguish your branch among the other branches in play.
- To get visibility and Continuous Integration feedback as early as possible, open your Pull Request as a
- Give it a meaningful title, and at least link to the respective issue in the Pull Request description, like
Fixes #23. Describe your changes, mention things for reviewers to look out for, and for UI changes screenshots and videos are helpful.
- Once your Pull Request is ready, mark it as
Ready for Review, in most repositories code owners are automatically notified and asked for review.
- Get all CI checks green and address eventual change requests.
- If your PR stays open for longer and merge conflicts are detected, merge or rebase your branch against the current
- Once a Pull Request is approved, you can merge it.
Depending on the release management of each repository, your contribution will be either included in a next release, or is put live automatically.
Except for GitHub, you can find most Ocean Protocol core developers in Discord if you have further development questions.
Create an app with one of Ocean Protocol’s interface points:
🎣 React hooks & components on top of ocean.js
🦑 Ocean Protocol's Python library to privately & securely publish, exchange, and consume data.
🐙 Smart contracts for Ocean Protocol v3
Ocean documentation will help. And… you’re here:)
These docs can always be improved. Every content page has an edit link at its end linking you to the content source on GitHub for simple copy editing.
If you found a technical bug or have an improvement suggestion, head over to the repo’s Issues section:
🐬 Ocean Protocol documentation
🐬 Ocean Protocol documentation
Really love building on Ocean and want to dive deeper? Consider joining us full time. Our openings are listed at https://github.com/oceanprotocol/devjobs.
Please go to the Ocean Community Page for more ideas on how to get involved.