Establishing a Community Forum for IPFS and Related Projects
In order to have a thriving, healthy community for IPFS and its related projects (Multiformats, libp2p, etc.) we need to create a Community Forum and maintain it. Over many months, this topic has been intermittently discussed. The background for those discussions, including a list of the proposals that have been considered, is outlined in https://github.com/ipfs/community/blob/master/decisions/community-forum-platform.md
Even if we don't use discourse, we need to settle on a strong plan for supporting the growing global IPFS community. If the first proposal fails, this thread will stay open until someone proposes a better solution and the community votes to adopt that approach.
We are testing loomio as a way to make community decisions like this one. In the long run we will probably revert to using github or gitlab for decisions, but loomio offers a useful way to learn the mechanics of decision making -- something that has been missing from the past 18 months of discussion about community forums -- so that we can apply those mechanics in github or gitlab.
The major proposals considered were:
* Proposal: Build Our Own Decentralized Forum Software on IPFS
* Proposal: Continue to Use Github for All Community Support
* Proposal: Use a StackExchange Subdomain for Q&A
* Proposal: Use Discourse for All Community Support
Related Github Issues:
Poll Created Mon 20 Mar 2017 2:52AM
Use Discourse for All Community Support Closed Thu 23 Mar 2017 3:01AM
See Proposal: Use Discourse for All Community Support in the background document for further discussion of pros + cons of this approach.
- Name a DRI for the rollover to Discourse and for ongoing management of Discourse
- Set up discourse at discuss.ipfs.io subdomain
- Recruit a group of moderators from community and get them set up with appropriate moderator powers
- Move top FAQ items from ipfs/faq to discourse
- Move relevant topics from ipfs/community to discourse
- Update ipfs/community, ipfs/faq and ipfs/support to clearly redirect people to discuss.ipfs.io
- Update ipfs/ipfs README to list discuss.ipfs.io as the main place to seek support
- Announce our new discourse forum on IRC and on the mailing list
* https support is enabled
* anonymous posting is enabled
* people are able to interact with our discourse install as if it was an email mailing list
After a 3-month trial:
1. Decommission the google group, redirecting all mailing list users to subscribe to discourse in mailing list mode
2. Consider archiving ipfs/support, ipfs/faq and/or ipfs/community if they are no longer useful.
|Results||Option||% of points||Voters|
|Undecided||0%||14||SN H K HTW J J(|
13 of 27 people have voted (48%)
Mon 20 Mar 2017 2:55AM
The majority of the IPFS community has been underserved by our reliance on github. It's created a heavy, invisible burden on the core maintainers to personally support people who are looking for community. discourse is the best option for now
Mon 20 Mar 2017 2:23PM
Discourse is becoming de facto standard for community-driven support and discussion forum.
It is a pragmatic choice that removes a lot of barriers.
I believe this move will positively impact signal/noise ratio of Github notifications.
Mon 20 Mar 2017 4:17PM
The tests we have done so far have revealed some minor flaws with Discourse but I agree with both Matt and Marcin that currently we're lacking a good community support channel.
Mon 20 Mar 2017 9:08PM
IPFS Telescope could be an alternative to Discourse in my view. Today during the 2017-03-20 sprint I gave a presentation on IPFS Telescope along with links to explore the presentation and a rough draft mock-up. To avoid any bias vote, I abstain.
Tue 21 Mar 2017 10:11PM
Github is very formal for casual questions which makes people not want to ask/answer them. People feel that as they are not directly connected with the project they should not answer them. Community forum would solve that issue.
Wed 22 Mar 2017 12:14AM
IPFS Telescope could be an alternative to Discourse in my view. Today during the 2017-03-20 sprint I gave a presentation on IPFS Telescope along with links to explore the presentation and a rough draft mock-up. To avoid any vote bias, I abstain.
Wed 22 Mar 2017 1:29AM
Given we actually do everything outlined in the proposal, i'm :+1: to this.
Wed 22 Mar 2017 3:27PM
I'll abstain from this decision and not disagree with a vote of willingness to try it out after seeing so many new names agreeing. Will look forward to everyone using extensively :)