Compare room capacity with actual list of registrants

[tidoust]

For TPAC meetings, the list of registrants (evolves over time but) is known at any given time. For example, see the list of registrants for TPAC 2024 (member-only link). That list gives the number of group participants and the group meetings that they plan to attend. It also gives the number of observers for each group meeting.

The numbers are likely inaccurate: people may go to different meetings in the end, they may register for two meetings that take place at the same time, various observers just pop up in meeting rooms, etc. Still, mapping these numbers to the capacity of selected meeting rooms and/or to the requested capacity could perhaps reveal things worth looking into prior to the meeting. Also, it shouldn't be too hard to do that mapping: the numbers can be slurped from the registration page somewhat easily, and the capacity of the rooms is already known. Initially, we probably don't need to create actual warnings in our system, this could perhaps just be a CLI that we run once in a while and that spits a short report in markdown.

[ianbjacobs]

I am wondering whether it ever makes sense to display the group's estimated capacity (e.g., 20-29) in the generated table. I say this because we don't actually generate the schedule until we have registration data, and once we have registration data, we should use that (and warn when the real number of registrants exceeds the room capacity).

[tidoust]

I am wondering whether it ever makes sense to display the group's estimated capacity (e.g., 20-29) in the generated table. I say this because we don't actually generate the schedule until we have registration data, and once we have registration data, we should use that (and warn when the real number of registrants exceeds the room capacity).

I created #157 to track that.