You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide accurate information about how to engage with the community.
Historically:
"ipfs" has been used to denote "go-ipfs" (Kubo), which is wrong since ipfs is bigger than a particular implementation.
Community information has been spread across various GitHub repos.
We want to have canonical information about IPFS implementations and community information that other places can link to. https://docs.ipfs.io is the intended place that we should link to.
This tracks the work to cleanup old/wrong areas about our "docs". Example areas in scope:
As part of https://2022.ipfs-thing.io, we want to:
Historically:
We want to have canonical information about IPFS implementations and community information that other places can link to. https://docs.ipfs.io is the intended place that we should link to.
This tracks the work to cleanup old/wrong areas about our "docs". Example areas in scope:
There is a lot of stuff (including cruft) in these repos. To maintain focus and contain the scope, this issue is focused on the two items above.
This issue is here so can link to it in various PRs to provide context.
The text was updated successfully, but these errors were encountered: