Swarm: add API to promote someone to an administrator

Goal

Because an administrator can leave, the swarm will have no administrator at the end. Make it possible for an administrator to promote someone else.

TODO

• Implement promotion/demotion (NOTE: no demotion if 1 admin) in the daemon
• Validate an API
• Add feature in clients
• Check demotion

changed due date to September 30, 2023

added BacklogLow swarm labels

added to epic &49 (closed)

1. Is there an option to demote someone who is an administrator?
2. If there is more than 1 administrator, can a jami user self-demote themselves as an administrator?

Thank you

1. Should be indeed, like ban/unban => promote/demote
2. In a swarm, to avoid split, critical actions are submitted as a vote, so if a user self-demote, it will be voted and if 50%+ of admins accept, the vote is accepted

2. For the self-demotion special case, please allow no self-demotion to occur without a vote if there are 2 or more administrators.
3. Will self-demotion not be allowed and a prompt show to promote someone to administrator if there is only 1 administrator?

Thank you

2. is actually similar to jami-project#1515 (moved)

One thing we might have to consider:

• If admin 1 promotes a peer to admin 2, admin 2 should NOT be able to kick admin 1 (if nobody leaves)?
• Same if admin 1 leaves and joins again ... will he be an administrator (again) and can't be kicked anyway? Or will admin 1 loose all permissions?

EDIT 2:

Since it will become possible to make calls Jami Desktop/clients <-> JamiWeb:

A Desktop user might promote a web user: What happens if just the web user exits? Jami clients are always p2p and the are no centralized servers.

A vote must get the majority to be validated (so >50% of the admins).

Jami-web doesn't change anything

I would like to add the following ideas:

• Should the promoted admin be able to promote another peer to a new admin? Maybe it's possible to disable that option?
• As mentioned (#798 (comment 40187)) the new admin shouldn't be able to kick the first admin?
• Maybe the new admin (2) shouldn't be able to quit the conference (just the first admin)?
• Maybe the new admin (2) has less permissions generally - so he can kick other peers but can't BLOCK them? (jami-project#1493 (moved))
• Maybe the first admin can choose how many permissions the new admin gets / or maybe there will be an option besides admin or regular peer? Like for example moderator?

if someone is an admin they will have the same powers as any other admins. It's a level. For point 2, as I said, >50% of admins must kick the other (so 2 admins can't keep one another, only they also kick theirself)

Would it make sense (especially since Jami does not rely on servers like for example BigBlueButton) to introduce a third role like Moderator?

https://docs.bigbluebutton.org/greenlight/gl-admin.html#user-roles

So that admins have more permisssions than moderators? And moderators for example can't end a conference or permanently block peers but can still kick members?

other roles are planned, but this issue is about administration

changed the description

changed epic to &52 (closed)

changed the description

marked this issue as related to #797

added typefeature request label

added sprintbacklog label