This is indeed a good idea that could be implemented.

Could you write in as much details as possible how this would work? For example, I think it would be nice to allow non group members to attend an event. This needs some logic to verify their email and create a limited user account.

Do you need this as well or am I overthinking it ?


(sent from mobile)
agorakit.org

Allowing non-group member to attend an event wouldn't be necessary. Our group will be a public group, open to anyone for joining.

Here the detailed description for further discussing the feature idea:

For an event there should be an optional maximum number of attendees (that is spots that are available). When all spots are taken new sign ups go onto a waiting list (so people can show that they would be interested in attending in case a spot get freed). The waiting list is ordered by the sign up date. When ever a spot gets freed the oldest entry on the waiting list moves onto the list of attendees and the person that got a spot is notified.

Here is an example flow:

1. The event "super popular event" is created with a maximum number of 3 attendees.
2. Bob, Alice and Carla sign up for it: the are all on the list of attendees but now the event is fully booked.
3. John, Paul, and Delores are also interested in the event and sign up. Because the event is already fully booked the all go onto the waiting list
4. The waiting list now looks like this:
   
   • John (signed up 2026-01-29 at 9:00 am)
   • Paul (signed up 2026-01-29 at 9:01 am)
   • Dolores (signed up 2026-01-30 at 10:00 am)
5. Now Alice cancels her sign up.
6. This moves John (as his sign up on the waiting list is the oldest) onto the list of attendees and he gets notified

I think the feature could even be implemented in two steps: first only the optional maximum number of attendees. The waiting list could be emulated by manual communication via a discussion in the group. That would not ensure that the oldest waiting list entry gets a spot but as MVP this might be good enough?

I'm also not 100% sure about the domain language (e.g. how the spots on the attendees list and waiting list should be called, just "spot"?) But I haven't look at the existing code. Maybe they become obvious when looking at the existing names.

Simpliest implementation proposal :


Add a setting to the calendar_event table to store max_attendees or something like that.

Then using the attending table, since we know the date of subscription, we can limit the query to show attending people based on max attendees, and a wait list if more than max people are attending, all ordered by date of attending (first come, first served).

If someone unattend, it shortens the list, thus adding the next in queue.

If someone unattend then attend again, he might be put on waiting list if the max attending is full.

This requires little change in the dB, some work in the controller and UI.


Would you be willing to work or help on this?


(sent from mobile)
agorakit.org

Thanks for the directions, Philippe :-).

Yes, I would like to try to implement that on my own.

Currently, I'm struggling a bit with the setup for the dev environment (maybe this is because I'm using podman with the podman-docker compatibility layer on Linux). When I'm following the instructions in https://docs.agorakit.org/localhost.html: do I still have to install a PHP interpreter on my machine or should the dev container image contain everything I need?

My first issue was that after running

./bin/dev-init.sh

there was an error:

Error: no container with name or ID "agorakit-dev" found: no such container
agorakit-pma
Error: executing /usr/bin/podman-compose -f compose.dev.yml up --build -d: exit status 125
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID "agorakit-dev" found: no such container
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID "agorakit-dev" found: no such container
Copying CA root cert to ./docker/dev/root.crt for convenience.
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID "agorakit-dev" found: no such container
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: no container with name or ID "agorakit-dev" found: no such container

running ./bin/dev-connect.sh after that also failed (but I think that is just a logical consequence of the first error) with

Error: no container with name or ID "agorakit-dev" found: no such container

The setup in PHPStorm worked after a bit of back and forth (because I didn't read the instruction carefully) but running composer failed because of "unmapped directories". I will investigate further later today or tomorrow.

I don't if you'd be willing to install docker in parallel to podman but I guess it would be the easiest way to start quickly.

None of us are docker nor podman experts : the docker stack was painful to make work, and I expect trying to fix podman support will be equally painful 🙂. I treat docker dev as a common ground, easily trash able and just a useable common ground.

You could of course setup another classic lamp stack, but then you won't have the little goodies Linc added to the docker stack like correct versions of everything.

I hope this won't block your participation. We can (and should) support podman but time is limited...

Help warmly welcome on any fronts !


(sent from mobile)
agorakit.org

Short update: I was able to get the dev setup running using Docker. Won't be able to work on the feature today. Hopefully, tomorrow I will find some time :-).

Great news. I created an issue with ideas and mentionned you here : https://github.com/agorakit/agorakit/issues/700