IPFS Q2 OKRs related to package management

Collecting all the OKRs that are closely related to package management from across the various IPFS working groups documented in https://docs.google.com/spreadsheets/d/1YSeyWqXh3ImanRrTkYQHHkCofiORn68bYqM_KTLBlsA/edit#gid=1681757723

project

[x] We have a prioritized roadmap for how IPFS will be used as a default distribution channel for 1000s of package manager users by EOY
[x] All IPFS working groups understand and actively address package manager needs, use cases, & pain points
[x] 5 package manager demos and/or deployments are proactively documented and shared with the wider community

[ ] It's possible to "rsync" to go-ipfs (initiative: Writable FUSE)
[ ] Implement provider strategy such that a user can add (and provide) npm or tr-wikipedia without turning off providing and without significantly impacting finding content (initiative: provider subsystem)
[ ] When connected to the global internet, IPNS record resolution takes less than 1s (initiative: IPNS over DNS, IPNS over pubsub, etc.)
[x] go-ipfs saturates a 100MiB link when downloading a sufficiently large dataset.
[x] go-ipfs has at most 10% overhead when downloading a large dataset (not including providing).
[ ] go-ipfs has experimental support for modification times and other metadata (initiative: UnixFSv2)

[ ] ipfs.io updated with up to 6 specific use cases and analytics flows that tell us which are popular
[ ] npm-on-ipfs desktop app

[x] Go-IPNS is performant and supports offline persistence
[ ] JS-IPNS is performant and supports offline persistence
[x] Identify opportunity for IPNS usage by package managers WG
[ ] There is a system that allows a third party to persist IPNS data in a gossip-based system
[x] IPNS has documentation explaining how it will support multiple configurations as well as guidance for users on how to select a configuration

[ ] Propose a solution to allow IPFS to mirror an rsync server or portion of a filesystem
[x] Example use cases relevant to package managers
[ ] Primer for registry maintainers that makes the case for IPFS simply & effectively
[ ] Howtos on handling massive data sets (e.g. repo types, optimisation flags, gotchas, etc)
[ ] We have a prioritised roadmap for how we will become the default distribution channel for several package manager ecosystems by EOY
[ ] Bootstrap the IPFS package manager community
[ ] There are some large usable deployments of IPFS-powered package mirrors/registries
[x] Design 2x elective sessions for IPFS Camp