Communities (originally: org. channels)

iurimatias commented 3 years ago

Organization channels

Source: Roadmap planning work shop item 41 and Discuss

As an organization, I want to have a list of channels that I manage So that I can use status as a slack/discord replacement
As a user I want to find relevant information without having to search through content in a channel

View community profile: name, description, image (optional)
Edit community profile
Set community to private or public
Invite members to join private community, they are not listed publicly (join.status.im/c/medella
Create chats
Set permission requirements to create chats
Group chats into categories
Set up mailserver

Join a public community (Messages and chats of a community are not visible until joined by default, something like publicly broadcasting a chat should be an opt-in)
Receive invite and join private community
View list of members
- members can (future scope) have different rank (based on... activity, community token in wallet, stake in community
- different rank allows different privileges (future scope)
- list of members is visible to everyone
- members can be managed by senior staff of the community with appropriate permissions, their permissions can be changed, they can be kicked etc.
View list of chats
- Chats in a community can be made private
A community has a way of organising those chats into groups
Pin messages (optional)

A community can have different rules for members, like say owning a certain amount of token to join
- Membership can be paid only
A community can publish its own stickers
A community can publish and reward its own badges
A community requires staking a certain amount of SNT to feature it / downvote upvote on a list

Preliminary designs

hesterbruikman commented 3 years ago

Added dependency to issue in #status-react and #nim-status-client

guylouis commented 3 years ago

renamed epic in to communities to unify of how we call things