-
Notifications
You must be signed in to change notification settings - Fork 480
Implementations section upgrade: explain usage #1673
Copy link
Copy link
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif/hardHaving worked on the specific codebase is importantHaving worked on the specific codebase is importanteffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekkind/suggestionSomething that you'd like to see in the docs. This can be written content, web design, or imagery.Something that you'd like to see in the docs. This can be written content, web design, or imagery.status/in-progressIn progressIn progress
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif/hardHaving worked on the specific codebase is importantHaving worked on the specific codebase is importanteffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekkind/suggestionSomething that you'd like to see in the docs. This can be written content, web design, or imagery.Something that you'd like to see in the docs. This can be written content, web design, or imagery.status/in-progressIn progressIn progress
Problem
https://docs.ipfs.tech/concepts/ipfs-implementations/ more or less catalogs the various IPFS implementations out there. However, this page (and the docs in general) don't provide information on:
Suggestion
Create an "Implementations" subsection (a few pages at most, including https://docs.ipfs.tech/concepts/ipfs-implementations/ ) that provides overview on the gaps listed above