1
0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-06-29 00:58:02 +02:00

+ "Develop a Service Integration Driver or Plugin"

This commit is contained in:
Troy McConaghy 2019-03-22 11:16:09 +01:00
parent 82cc7407e0
commit 0d6dc2aae8

View File

@ -17,19 +17,13 @@ Code development follows the [Ocean Engineering Principles](/concepts/principles
See the page about [reporting vulnerabilities](/concepts/vulnerabilities/).
## Report a Bug
## Report a Bug or Make a Feature Request
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 report a bug that isn't a vulnerability, or to make a feature request, go to the relevant GitHub repository, click on the Issues tab, click on the New issue button, and read the instructions.
## Write an Issue
## Suggest a Change to the Protocol Itself
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.
<repo name="OEPs"></repo>
To suggest a change to the Ocean Protocol itself (which is actually a set of protocols), go to the [Ocean Protocol Enhancement Proposals (OEPs)](https://github.com/oceanprotocol/OEPs/) repository and write a proposal, either as an issue or as a pull request.
## Write!
@ -54,3 +48,10 @@ See the page about [bounties](/concepts/bounties/).
- [Read the announcement of the Ocean Protocol Ambassador Program](https://blog.oceanprotocol.com/envoys-of-the-new-data-economy-ocean-protocol-ambassadors-3816a0e63611)
- [Read about some ambassadors](https://blog.oceanprotocol.com/an-ambassadors-tale-531401d4452f)
- [Apply to become an ambassador](https://oceanprotocol.com/#ambassadors)
## Develop a Service Integration Driver or Plugin
- Aquarius currently supports storing metadata in MongoDB, Elasticsearch or BigchainDB. Each option is supported by its own "OceanDB driver." You could write a new OceanDB driver to support another database. See [the existing OceanDB repositories for examples](https://github.com/oceanprotocol?utf8=%E2%9C%93&q=oceandb&type=&language=).
- Brizo currently supports storing data sets in Azure Storage, Amazon S3 or on-premise. Each option is supported by its own "Osmosis driver." You could write a new Osmosis driver to support another storage provider. See [the existing Osmosis repositories for examples](https://github.com/oceanprotocol?utf8=%E2%9C%93&q=osmosis&type=&language=).
- [OEP-11 lists the supported encryption and decryption options](https://github.com/oceanprotocol/OEPs/tree/master/11#encryption-and-decryption) (for encrypting URLs before putting them in the metadata, not data sets themselves). You could add support for another option.
- Other kinds of services could also be integrated. If you need help or advice, then email <a href="mailto:info@oceanprotocol.com">info@oceanprotocol.com</a>.