As part of https://2022.ipfs-thing.io, we want to:

1. Drive home the message that IPFS is many implementations by multiple groups. Basically IPFS is not go-ipfs or Protocol Labs. Add IPFS Implementations page ipfs-docs#1193
2. Provide accurate information about how to engage with the community.

Historically:

1. "ipfs" has been used to denote "go-ipfs" (Kubo), which is wrong since ipfs is bigger than a particular implementation.
2. 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:

• https://github.com/ipfs/ipfs
• https://github.com/ipfs/ipfs-docs
• https://github.com/ipfs/community
• https://github.com/ipfs/team-mgmt
• https://github.com/ipfs/roadmap
• https://github.com/ipfs/notes

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.

• Add IPFS Implementations page ipfs-docs#1193
• Update chat options for 202207 ipfs-docs#1195
• Houseclean README for multiple implementations and community source of truth #486
• List other Kubo RPC API clients ipfs-docs#1194
• Add deprecation notice to README community#760
• docs(readme): add banner about inaccurate state team-mgmt#1204
• rename go-ipfs to kubo roadmap#92
• chore: houseclean README js-ipfs#4157
• chore: houseclean ipfs/README js-ipfs#4156
• chore: houseclean interface-ipfs-core/README js-ipfs#4158
• chore: update docs/core-api/README js-ipfs#4159
• chore: houseclean ipfs-core/README.md js-ipfs#4160