-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Description
For each of the applications of ipfs that we've made issues for provide an outline of:
- use cases (very granular)
- groupings of use cases (coarser, clearer)
- which foundational features & functionality the use cases need or rely on (ie. libp2p, private networks, etc.) - this sources interdependence between feature sets
- related products or projects that are addressing those use cases (ie. matrix working on p2p chat)
- related organizations who either 1) have those use cases or 2) are building solutions for those use cases (ie. akasha, mediachain, openbazaar, neocities)
Guidelines:
- Emphasize specific, deliverable user experiences - not just merged, not just a demo. Actual user experiences.
- If a use case relies on an underlying library, link to the repo on github
- If a use case relies on features or functionality that haven't been implemented or released yet, make sure there is a github issue in the appropriate repo for that feature and link to that issue from the use case.
roobie, dryajov, adamlawrencium, wscherphof, camelmasa and 5 moreFingerLiu, davidvasandani and swanthropos
Metadata
Metadata
Assignees
Labels
No labels