This document covers best practices surround the naming, information fields, and roles for the chat channels. Today, we have the following type of chat channels (see channel mapping):
- Project channels (e.g., fabric-*, sawtooth-*)
- Working Group channels (e.g., architecture-wg, identity-wg)
- SIG channels (e.g., social-impact-sig, healthcare-sig)
- Community channels (e.g., community-*)
- Language-specific channels (e.g., russia, portuguese)
- Program channels (e.g., meetup, ambassador)
- Event channels (e.g., blockchain4good, hackfests)
- Devops channels (e.g., ci-pipeline, jenkins-robot)
Channel Naming
Channel Information
Roles
This section covers the best practices surrounding roles for the chat channels. Today, our chat program supports the following roles:
- Admin
- Moderator
- Owner
- User
By default, all users will have the User role. The other three roles should be granted only in these instances:
| Channel Type | Group | Role |
|---|---|---|
| Project | Maintainers | Moderator |
| Working Group | WG Chair | Moderator |
| SIG | SIG Chair | Moderator |
| Program | Responsible LF Staff | Owner |
| All | LF Staff | Admin |
| All (except non-program) | hyperledger-bot | Owner |
From the above, you will see the following:
- Some of our channel types will not have moderators. This is because there is no one person or set of people who act in this role.
- Ownership is only provided to LF Staff. Owners can perform the following tasks over and above moderators that should not be provided to the community: Archive Room, Delete Public Channels, Force Delete Message, Set Leader, Set Moderator, Set Owner, Set React when ReadOnly, Set ReadOnly.
- Non-program channels will have the owner set to a Hyperledger-owned account to allow for administrators to leave channels that they created.