-
Notifications
You must be signed in to change notification settings - Fork 509
Allow to set default publishing permissions in a conversation #5708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to set default publishing permissions in a conversation #5708
Conversation
b13af27 to
efa5394
Compare
PVince81
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good so far, happy to see JS tests :-)
| public function updatePublishingPermissions(Room $room, Participant $participant, int $newState): void { | ||
| $attendee = $participant->getAttendee(); | ||
|
|
||
| if ($attendee->getActorType() === Attendee::ACTOR_GROUPS || $attendee->getActorType() === Attendee::ACTOR_CIRCLES) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if ACTOR_EMAILS will pop up here, might be safer to go with an allow list instead of deny list ?
| icon="icon-audio" | ||
| :close-after-click="true" | ||
| @click="grantPublishingPermissions"> | ||
| {{ t('spreed', 'Grant publishing permissions') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we might need to double check if "publishing permission" is something that users will easily understand.
on the technical level this term is fine though
|
what's missing ? a checkbox list would be nice, just in case someone needs to take over... |
|
The feedback from other teams and useful global stats/options we want to describe and have. |
efa5394 to
52f82fe
Compare
This is needed to add other actions in the menu that can be applied also to owners. Signed-off-by: Daniel Calviño Sánchez <[email protected]>
52f82fe to
9d99aa2
Compare
Publishing permissions can be set by moderators or owners on any participant. For now there is a coarse handling of publishing permissions, so it is only possible to grant or revoke all permissions, not each one of the individual permissions. Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Only moderators of group and public conversations can set the value. For simplicity, and to avoid chaos if everyone is allowed to publish during a call with a lot of listener-only participants, the value can be set only if there is no active call. Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
9d99aa2 to
745067d
Compare
|
I'm closing this in favor of the plan in #6190 (comment) |
Follow up to #5693
In #5693 publishing permissions can be set for each participant. However, by default all participants have publishing permissions, and they need to be explicitly revoked. This pull request introduces a setting for conversations to define whether everyone or only moderators should be able to publish by default in the conversation.
For now this just contains some commits salvaged from a previous version of #5693, but they might be useful to implement the feature.