Decision Document: Creating a Community Forum for IPFS and Related Projects #246
Conversation
flyingzumwalt
force-pushed
the
decision/discourse
branch
from
b56f7fb
to
bb3f862
Compare
|
|
||
| ### Scaling Factor: Proliferation of Comms Channels and Resulting Notification Overload | ||
|
|
||
| Spreading communication across many channels confuses the heck out of everyone, especially new arrivals. It also makes it very hard for core contributors to participate in open community discussions on top of the existing volume of implementation-focused discussions. |
There was a problem hiding this comment.
I feel a tool like Discourse could decrease cognitive load on core devs.
At Github, they can watch ipfs/faq or ipfs/support but this means they will receive a notification for EVERY message. If they are not interested in issue, they need to explicitly opt-out.
In Discourse there is a setting that sends notification for the first post in thread, and it is up to dev to decide if he or she wants to follow it further (opt-in):
I feel there should be a note about this in "Use Discourse for All Community Support" section
| * would require a lot more management of community discussions in order to maintain a good [SNR](https://en.wikipedia.org/wiki/Signal-to-noise_ratio). Hopefully a lot of that effort can come from community members | ||
| * would require attention to keep "community discussion" on discourse from drifting away from task-oriented, github-based discussion about implementation, maintenance and design | ||
| * would be a protocol change for core contributors | ||
| * would add to the already-crushing volume of notifications |
There was a problem hiding this comment.
Actually, it could DECREASE the number of notifications, see #246 (comment)
|
Merging this as a reference document. The actual decision will proceed on loomio at https://www.loomio.org/d/imMrpwRF. See https://github.com/ipfs/community/blob/master/decisions/community-forum-platform.md#decision |
We will finalize the decision on Friday 17 March 2017 and write the conclusion into this document.
This document gathers all of the needs, factors to consider, and relevant proposals around creating a community forum for IPFS and its related projects. It's structured to allow final discussions about this topic so that we can make a decision about how to proceed. The information in the document was sourced from all the related issues and notes from a couple public calls (see references).
If you have modifications to the proposal, modifications to the background information or if you want to block this proposal and argue for an alternative, please speak up before Friday.
References: