-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blog: registration: Post on registration management #734
base: main
Are you sure you want to change the base?
Conversation
- History of registration, difficulties of doing it with teams, why this appears online but not in-preson, distributed registration as a strategy. - It does *not* include our latest practices and what we raret trying to do in the future - others can fill that in. - Please add yourself to authors when you add more.
349c1c9
to
271d8bf
Compare
Thanks a lot. I will carefully read and comment since this is a problem I am thinking about a lot these days and also we discussed this earlier today in meeting. |
I will work on registration coming week and then this will nicely fit into my work. |
Co-authored-by: MatiasJJ <[email protected]>
Finally reviewing ... |
Points to possibly add/expand:
|
(2) is a good point! distributed registration makes things easier. but then multiple-registrations means there will be no-show in one or the other, making more work. |
I would like this to not get lost but also we have moved on a bit. Will it help if we meet for a 45 min call and finish this live together and get it published? |
I am sorry we never got this merged but maybe we can update it with lessons learned from March workshop and plan for the September and future workshops? |
this appears online but not in-preson, distributed registration as a
strategy.
to do in the future - others can fill that in.