Plan for SciPy announcement

[yuvipanda]

I'm guessing @SylvainCorlay and others will announce Voila at SciPy. We should make sure the Gallery is upto the task of the folks who will be coming to check it out.

1. Make sure our instance is big enough
2. Have some monitoring & metrics in place (so we know how many people showed up)
3. Have more examples?
4. Quick design refresh
5. Make sure idle culling is in place.

Other things to do? /cc @pbugnion @jtpio

[jtpio]

Those are all good points. Also:

• HTTPS by default for voila-gallery.org
• A tutorial so people can deploy their own gallery? (including links to the existing guides in TLJH)

[martinRenou]

• Support for themes templates in the gallery (if that's not already done, or I suppose it's related to this Switch templates via query string parameters voila#201)

[jtpio]

@martinRenou both themes and templates?

[martinRenou]

Sorry, I meant templates :)

[maartenbreddels]

FYI, this is the material for the tutorial on widgets:
jupyter-widgets/tutorial#33

It will include instructions for mybinder, but we hope to do more :)

I feel torn about the templates, I think before we let people make new templates, we should have a stable template system. If we push out an early release, we might have to break it twice (once for the directory layout+nbconvert coop., once for the progressive rendering). So just be aware that this area is still moving.

[SylvainCorlay]

Thanks @yuvipanda for opening this.

FYI, @maartenbreddels and @martinRenou will be giving the talk about voila. I will finally not attend scipy (going to give another talk at CICM about voila as well). There should also be some voila chapter in the jupyter widgets tutorial.

[jtpio]

I think the current state of the gallery together with the open PRs (#48, #45 and #50) cover most of the points listed above.

The current instance is a b2-30 that comes with 30 GB RAM, 8 vCores and 200 GB SSD. That should be enough to start with.

Regarding the templates this is something that we need to handle in voila before exposing it in the gallery.

For the idle culling, there is a basic activity timeout which means that the notebook servers will be shut down if they become inactive (same values as for mybinder.org). There is no user culling yet, the temporary users are still kept in the JupyterHub database. This is something that can tackled later on.

For the monitoring and metrics, maybe @yuvipanda has something we can setup quickly? (would using the /metrics endpoint be enough?)

[jtpio]

Closing as the remaining points mentioned here now have their own issues.