Sharing of Registration Info Among Collaborators

[Shinmera]

Currently only the admin (@didierverna) can view the registrants, since that information is tied to the private stripe keys. This is a bit of a hurdle, since the local chair might need to know some of this information as well in order to do local organisation.

I'm not yet sure how this sharing could be facilitated without involving too much manual interaction, or leaking sensitive data.

[didierverna]

Viewing the registrants (in the way I suspect you mean it) is only part of the story, because when people pay via bank transfer, Stripe is not involved anyway. The simplest way to keep track of registration info more or less in real time is to change the Cc: address in the confirmation email, so that more people get it. But even then, that info is not the whole story (consider invited speakers etc.).

I actually use an Emacs Lisp script to process registration emails and maintain an org table that I will share periodically or on demand, with the current registration status.

[Shinmera]

Ah, yeah, I had forgotten about the bank transfer. Invited speakers and other core contributors aren't a problem since they're already in the edition database.

Right now I'm thinking about having the registration script append the data to a plain text sexpr file. This file could then be committed and pushed automatically from the server to a private repository somewhere.