Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consolidation of ocean/whale/playground/salmon into DeFiCh/jellyfish #580

Closed
fuxingloh opened this issue Aug 10, 2021 · 3 comments
Closed

Comments

@fuxingloh
Copy link
Collaborator

What would you like to be added:

Currently, we have 3 projects (ocean, whale, and playground) that are extensions of the jellyfish project. We should consolidate them into a singular code base so we don't need to manage dependencies updates across the ecosystem.

Why is this needed:

  • better synergy of DeFiChain open source development across concerns
  • single versioning
  • single source of truth
  • single documentation for the entirety via jellyfish.defichain.com
  • early regression detection

/assign @fuxingloh
/triage accepted

@fuxingloh fuxingloh added the kind/feature New feature request label Aug 10, 2021
@defichain-bot defichain-bot added triage/accepted Triage has been accepted needs/area Needs area label(s) labels Aug 10, 2021
@defichain-bot defichain-bot removed the needs/area Needs area label(s) label Aug 11, 2021
@fuxingloh fuxingloh changed the title Consolidation ocean/whale/playground into DeFiCh/jellyfish consolidation of ocean/whale/playground into DeFiCh/jellyfish Aug 11, 2021
@fuxingloh fuxingloh changed the title consolidation of ocean/whale/playground into DeFiCh/jellyfish consolidation of ocean/whale/playground/salmon into DeFiCh/jellyfish Sep 9, 2021
@defichain-bot defichain-bot added the needs/area Needs area label(s) label Dec 16, 2021
@defichain-bot defichain-bot removed the needs/area Needs area label(s) label Dec 23, 2021
@0ptim
Copy link

0ptim commented Jan 23, 2022

Does this mean that in the future, there will be one large SDK for calling RPC with a local full node as well as calling the ocean API or will these still be separate SDKs/libraries?

@fuxingloh
Copy link
Collaborator Author

Does this mean that in the future, there will be one large SDK for calling RPC with a local full node as well as calling the ocean API or will these still be separate SDKs/libraries?

Yup, one large SDK/Ecosystem that is divided into multiple smaller pieces within itself.

@fuxingloh
Copy link
Collaborator Author

It's done

#1497 is the last piece.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants