GregSutcliffe
commented
1 year ago I'm not averse to this, but I've never really seen an example of it used in a way that adds something to the meeting. Certainly in the Ansible meetings, we would chair literally everybody anyway, so what value does it add over just allowing anyone access to some/all of the commands?
Our team discussed this a while ago, and came to the conclusion that a shorter list of people who can start/stop meetings (and maybe a few other exploitable commands like meetingname) should be reserved, and the rest (like info, action, etc) should be open access to everyone, hence the way I've coded it to start with.
Obviously, if you want to code it up, go for it, but since we're building a new thing, I figured I'd ask if tradition is the only reason for this feature (and thus worth challenging) or there's something I'm missing (quite likely :P).
james02135
OG meetbot has a feature where the person that starts a meeting instantly becomes the chair of the meeting, allowing them to use the meeting commands. A chair is also allowed to add new users to the chairs list and they are allowed to do commands as well.