Fabric's Feedback
Platforms
- What is your preferred community platform? Fabric mailing list.
- Where do you do the majority of your communication for work/hobby/education? All over the map, but mostly Slack
- How many different platforms do you use to communicate with DLT communities? Slack for internal communication, mailing list for project communication, bi-weekly contributor meetings for project updates and deep dive topics, RocketChat for community support, GitHub issues for managing new work and bugs.
- List them?
Identity
- Do you need to log-in to access the community you want? (Does a LFID hinder you from using the Hyperledger chat platform?) LFID login has not been a problem
- Do you prefer to share your info (for follow-up, email support, more) or remain anonymous? Mixed bag... we've found that the maintainers that engage most will get hammered with direct chats and emails, mostly people wanting support/help for their specific use case and environment. It can be overwhelming, there is therefore a penalty and disincentive for named community engagement and most maintainers have pulled back from RocketChat as a result.
- Would another authentication format entice you over the Linux Foundation ID? LFID has not been a problem.
- What information about yourself are you comfortable sharing? What information about yourself are you NOT comfortable sharing? Email, LFID, and github ID is fine to share, but see above.
Engagement
- Why do you log on to the Hyperledger community platform? To understand what is going on with community and provide help.
- What functionality (or level of engagement) would make you log on more to the platform? The RocketChat experience itself is poor relative to Slack that we use for our day jobs, both because it requires a different client and because of the user experience itself. So I guess I'd say if it were Slack we'd use it more, but I understand this is cost prohibitive.
- Do you ever browse the chat channels other than your primary channel? If not, what is stopping you from doing so? Fabric itself has too many channels, making it difficult to browse them all, let alone others. We should probably consolidate to a smaller list, e.g. one for maintainers/contributors, and one for users. I think that would make sense for mailing list as well. A separate maintainer/contributor mailing list may drive more dialog there, as the messages wouldn't get lost within the sea of user questions. If we could establish some kind of recommended breakdown for project chat channels and mailing lists, I think that would help.
- Do you collaborate outside of Hyperledger chat platforms to accomplish your DLT or project work? We live in Slack for internal communications. If Hyperledger used Slack we would participate more in Hyperledger chats.
Geography
- Where are you located? US
- What community platforms that others may use are NOT supported in your geo or language?