Move repo into ipfs or ipfs-shipyard

[parkan]

Following up from the email thread and looping in @Stebalien. Let's move this repo into an ipfs-related org so we can get more eyes on the discussion + code.

There are two choices:

• Move into ipfs-shipyard: package this as a kind of "mobile SDK" on top of IPFS, similar to how peer-base relates to building dynamic data apps, or how ipfs-provider helps use multiple backends. Pros: loose coupling, lower integration overhead upfront. Cons: somewhat lower visibility, requires ongoing community stewardship.
• Move into ipfs core: integrate more deeply into the core modules (required to be placed in ipfs org). Pros: potentially deeper integration, lower risk of APIs going out of sync, etc. Cons: upfront evaluation and integration cost, needs core maintainer time.

My suggestion is to move into ipfs-shipyard and make public ASAP, possibly even before merging #5. We saw some amazing energy around this application area at IPFS camp, and not letting it wither is very important. Having a visible place for the discussion of IPFS-on-mobile is a big win even without shipped code. However, It might be worth completing #2, or otherwise clarifying what this module will actually do.

(N.B. most code is currently in #5, waiting on @gfanton to return from vacation)

[parkan]

@Stebalien who else should we invite to review this?

[parkan]

@Stebalien PR updated here and ready for review: #5

let's merge + move into ipfs-shipyard unless you have objections?

[aeddi]

Hello @parkan and @Stebalien,

What would you like to do about this issue?

We could move the repo under the IPFS organization directly or make it open-source as is and wait until it is a bit more polished (CI, lifecycle management, streams, etc...) before moving it.

What would you prefer?

[Stebalien]

I'm happy to move it to ipfs-shipyard immediately. However, someone else is going to have to maintain it and review patches.

[alanshaw]

Please initiate the transfer - I can accept it to ipfs-shipyard.

[aeddi]

Ok cool, I just updated the disclaimer and added a roadmap to the README.
I'll initiate the transfer 👍

[aeddi]

@alanshaw I can't transfer it directly to ipfs-shipyard because I'm not a member of the organization.
Can I transfer it to your account so you can forward it?

[alanshaw]

Sure!

[alanshaw]

Done, let me know who else to add to the team @aeddi

[aeddi]

@alanshaw Can you add @glouvigny, @moul and @gfanton please?
Thanks :)