Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
# Ocean Bounty: Docker Setup for Ocean Protocol on Windows OS
## How can you help?
We need help with making Barge, our docker compose files, work with the various Windows OS.
[Our Docker Compose](https://github.com/oceanprotocol/barge) files for setting up the full Ocean Protocol stack is working for MacOS/Linux but not on Windows. Docker for Windows offers a different solution compared to the experience with Docker on Linux and Docker for Mac, due to the difference between Windows SO and Unix-type kernels. These differences are turning out to be problematic when trying to run a Docker project built thinking on the other platform.
P.S. - At Ocean we reference everything with Marine life references, so we call our docker system "barge" as barges carry containers on the water! ;)
## What needs to be done?
The outcome of this bounty is to deliver a Windows-compatible version of [barge](https://github.com/oceanprotocol/barge). You may face some incompatibility issues due to how the different operating systems manage the network. Additionally, the runner script (`start-ocean.sh`) may need some modification/migration to PowerShell to get it working over Windows as well as modifying some files/script to make it work on Windows.
You will also configure the local Windows system to enable the network connection between containers (https://forums.docker.com/t/bridge-with-docker-for-windows/30936/10). Document any action you may require to do in order to achieve the goal.
## We are very happy when
- README file explaining how to start setup on windows. Please refer to our barge repo and format the README.md file. All documentation related to the setup must be included in this.
- For the final submission, please create a PR to the [barge repository](https://github.com/oceanprotocol/barge)
For any other comments or questions, you can reach us on Github or, for an immediate revert, on our [Gitter channel](https://gitter.im/oceanprotocol/Lobby)
## Seen this problem before?
Any help solving this is welcome. Feel free to leave any comments and help someone else to solve it. We might airdrop tokens to someone even if not directly completing bounty.
## Questions & Reviews
Pull requests will be reviewed by one of the maintainers or long-term contributors. In case of any additional questions feel free to ask in this thread and we will do our best to add the missing info :)
## Things to know
The bounty lifecycle process including payout will be managed using [Gitcoin](https://gitcoin.co/explorer?network=mainnet&keywords=oceanprotocol&order_by=-web3_created).
We'll be responding to your questions here, but for discussion and clarification we recommend to join also our [Gitter channel](https://gitter.im/oceanprotocol/Lobby) where our tech community is accessible.
In order to see the PROCN balance in your wallet you'll need to reference the related token contract with address _0xf2aabdd898a0139195b2b5da7387d43a45ded254_. If you use a Metamask plugin you'll find the the exact steps [here](https://metamask.zendesk.com/hc/en-us/articles/360015489011-Managing-ERC20-Tokens).
Lastly, even if it is a contest bounty, we will reward all valuable contributions and efforts. We greatly appreciate the value our open source community brings to Ocean and will always award some tokens to all great contributions! :smiley:
Once the project was reviewed and merged in the master branch, you will receive the reward. PROCN is a proto-Ocean token. Bounty hunters that earn PROCN will be able to convert them 1:1 to Ocean tokens on network launch (Ocean Token will be valued at at 0.22 EUR on network launch). Network launch is expected to happen by Mar 31, 2019. Until then PROCN will be locked and non-transferrable in the ETH wallet to which it is delivered to.