@ipfs/package-managers talked about tracking tasks that we're working on, that are not directly/immediately relevant to package management.
For my own sake, I'll put them here before I forget.
Anyone else is welcome to do the same here if they want to.
Requested on:
https://github.com/ipfs/go-ipfs/issues/6262
general:
Aids with testing and distribution. Faster tests benefits everyone.
Distributable config files is nice for automation in general.
shoehorn:
Faster and easier init, should make spawning and testing mirrors slightly less painful
Some of the go-ipfs portions to get parity with js-ipfs
https://github.com/ipfs/js-ipfs/pull/2002
(this isn't the right repo for it but WIP is here) https://github.com/djdv/go-libp2p-routing-helpers/tree/dns
general:
We need to define things like this and maintain interop between core implementations and supporting this will help performance for various use cases, surrounding content resolution, and dynamic content publishing...
shoehorn:
...which will be more relevant to us longer term, but is relevant widely now.
@ipfs/package-managers talked about tracking tasks that we're working on, that are not directly/immediately relevant to package management.
For my own sake, I'll put them here before I forget. Anyone else is welcome to do the same here if they want to.
Requested on:
https://github.com/ipfs/go-ipfs/issues/6262 general: Aids with testing and distribution. Faster tests benefits everyone. Distributable config files is nice for automation in general. shoehorn: Faster and easier init, should make spawning and testing mirrors slightly less painful
IPFS Camp media content (recordings, etc.)