- IPFS documentation: We have a dedicated docs site that's the best first place to look.
- Technical support: For specific questions, including technical support, please use the official IPFS discussion forums.
- General questions and discussions: Use the official IPFS discussion forums or chat on Matrix.
- IPFS-related community announcements: If you'd like to announce something to the IPFS community at large, use the official IPFS discussion forums; we monitor the forums for things to include in the weekly IPFS newsletter! You can also inform people via Matrix and the other venues listed below.
- Bugs and feature proposals: IPFS-codebase-related bugs and feature proposals can be reported directly in their repositories (most are in the IPFS and IPFS Shipyard GitHub orgs), for example Kubo or js-ipfs. If you're not sure where the best place to report a bug or request a feature is, ask in the forums and someone will point you in the right direction.
- Support for libp2p: Questions specific to libp2p should use the libp2p forums for faster results.
- Reporting security issues: To report security issues, please email firstname.lastname@example.org.
- Reporting abuse: To report abuse, please email email@example.com.
- Something else not listed here? Ask in the official IPFS discussion forums.
IPFS discussion forums
We aim to direct the majority of discussions and support questions toward the official IPFS discussion forums. IPFS developers keep an eye on posts in the forums and are happy to jump in to help. This makes it easier to search and learn from previous discussions, and it helps us keep code repositories focused — thereby increasing the ratio of actionable, clearly defined, and scoped issues that anyone can contribute to.
We keep all our codebases and supporting/additional repositories in GitHub. For this, we maintain several GitHub organizations:
- IPFS contains the core codebases and related libraries. We aim to keep this organization tidy, with all projects in it being actively maintained by the IPFS core teams.
- IPFS Shipyard contains many side projects, tooling, and endeavors that are not part of the core codebase and therefore may have different levels of maturity and activity. We encourage the community to step up and drive Shipyard projects forward!
- IPFS Archive contains archived repositories that are obsolete and no longer under active development (usually because they have been replaced by something else).
We aim to keep the issue trackers in most repositories for specific, scoped discussions and implementation approaches. Reducing the noise in the repositories via high-quality, on-point issues helps our teams perform more efficiently and serve the developer community faster.
Matrix and Discord
Our official chat rooms in Matrix and Discord are bridged, so you can join whichever you prefer. They can be used to ask questions and discuss with the community — however, while IPFS core developers are usually in these rooms, it can be hard to keep up with the running conversation and questions can be missed or disappear due to a lack of indexing. Therefore, we prefer the forums for support questions, though you can still try the chats!
Core IPFS developers do not monitor the following venues, but many of our community members do and are happy to help and discuss: