nextcloud / nextcloud/spreed

RFC: make participants aware of their conversation permissions

Open
#11,211 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: conversations 👥 feature: frontend 🖌️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
17h 55m
Merged PRs (30d)
350

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
It's known for moderators, but not for the participants itself, or could be found in some non-obvious places, although frontend is receiving and can use this data

Describe the solution you'd like
Conversation settings => Setup overview => List of permissions for given conversation
image

Describe alternatives you've considered
Context messages / tooltips where it's applicable

image
Example of usage (bitiwise + negation check):

videoButtonTooltip() {
	if (~this.conversation.permissions & PARTICIPANT.PERMISSIONS.PUBLISH_VIDEO) {
		return t('spreed', 'You are not allowed to enable video')
	}
},

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the frontend conversation settings and Setup overview, then trace how conversation permissions are received and currently exposed to participants. Review the proposed permissions list and the alternative context messages or tooltips, including the shown video-permission example. Done means participants can find their conversation permissions and understand applicable restrictions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.