馃搮 Ideally open an issue two weeks before an event, though we will still consider requests up to 48 hours before the event 馃搮
This request is being put in less than 48 hours in advance. We fully understand this request might not be possible to fulfill and can drop Binder support for this section. We apologize for this late request.
@matthewfeickert (PyHEP 2020 workshop organizer contact) on behalf of @egede (presenter).
This is for a tutorial at the PyHEP 2020 workshop 2020-07-13 through 2020-07-17.
No, all speakers and organizers are volunteers. The workshop is free of charge and all resources will be made publicly available both on the workshop website/Indico page and on the High Energy Physics Software Foundation YouTube channel.
https://github.com/ganga-devs/ganga/
(This is a tutorial at a workshop, so I chose "workshop". I will be submitting more of these, so please let me know if I should change this.)
There are 1000 attendees registered, but we would anticipate that an upper _estimate_ would be maybe 600-700 would connect at this time.
Ganga: flexible use of of virtualisation for user based large scale computations (TUTORIAL) is occurring at 17:50 - 18:45 UTC-6 on 2020-07-13.
We will make an announcement at the start of the workshop about Binder, the service, and how the resources are being provided. If there is specific language the Binder team would like us to use we are happy to integrate this in.
@betatim Seems that the reported number of attendees for the "Pacific" timezone sessions is very much off from reality as we peaked at 100 people in the call and at most had 38 Binder sessions running all at once.

I'm sorry that we gave such a drastic over estimate on resources, but I'll go scale down the requests in all the other Issues.
I'm closing this Issue as well, now that the talk is over.
That's fine. It is better that we overestimate the resources and expect to be able to handle that than the other way around.
Thanks for the data on how many people were in the call and how many binders were running. It seems like (4/3)*pi is emerging as the natural constant to multiply the number of people in a live stream by to get number of concurrent binders. (I'm expecting a paper on the arxiv by theorists tomorrow explaining why 4/3pi is natural and not fine tuned 馃槀)
Most helpful comment
That's fine. It is better that we overestimate the resources and expect to be able to handle that than the other way around.
Thanks for the data on how many people were in the call and how many binders were running. It seems like (4/3)*pi is emerging as the natural constant to multiply the number of people in a live stream by to get number of concurrent binders. (I'm expecting a paper on the arxiv by theorists tomorrow explaining why 4/3pi is natural and not fine tuned 馃槀)