search

Rembane / lemmingpants

A system to handle the speakerlist on Datateknologsektionens meetings.
Apache License 2.0
6 stars 5 forks source link

No duplicates in speakers queue #55

Closed Kirens closed 6 years ago

Kirens commented 6 years ago

A user should not be added to the queue if they are already on it already. It seems reasonable they speak both ideas at once instead. This would close #54

Rembane commented 6 years ago

This is a very reasonable request. But I wonder if there are cases where we actually need duplicates in the speaker queue. I can't think of any at the moment though.

advall commented 6 years ago

I would definitely argue that a single person should only be allowed to be listed once at any given time. With that said, I’m not considering technical practicalites such as a ”lapplös” user acting as a placeholder for multiple people.

Rembane commented 6 years ago

@advall I think it can be a good way to signal that we really need people to register themselves in the system. OTOH, people are lazy and cunning so they will solve this by borrowing their friends' numbers. This will work out. I'll implement this and let it crash. :)

advall commented 6 years ago

Letting it crash sounds good.

However, with the risk of going OT, there will never be a complete abscense of ”lapplös”. Partly because of people’s inherent lazyness, but also more legit; such as a programansvarig or an inspektor dropping by to give a message or take part in a certain debate. For those cases, it might be nice to add ”lapplös” as a special feature, where admin can add a plaintext name of a userless person in the entry field instead of a number.

Rembane commented 6 years ago

@advall That is indeed true. Though having lapplös as a special feature would make a lot of things very messy, so I instead propose that we add a user for each person that shows up to the meeting and wants to speak. If for instance an inspektor shows up, the inspektor can register themselves or the presidium can do it for them.