Jeremy Tuloup

## Wednesday, November 20th | Name | Affiliation | GitHub | | -----|-------------|--------| | Nicolas Brichet | QuantStack | @brichet | | Andrii Ieroshenko | AWS | @andrii-i | |...

## Wednesday, December 4 | Name | Affiliation | GitHub | | -----|-------------|--------| | Gabriel Fouasnon | Quansight Labs | @gabalafou | | Mike Krassowski | Quansight | @krassowski |...

## Wednesday, December 11 | Name | Affiliation | GitHub | | -----|-------------|--------| |William Stein | CoCalc | @williamstein | | Mike Krassowski | Quansight | @krassowski | | Jason...

## Wednesday, December 18 | Name | Affiliation | GitHub | | -----|-------------|--------| | William Stein | CoCalc | @williamstein | | Andrii Ieroshenko | AWS | @andrii-i | |...

The next meeting scheduled for December 25 is cancelled, since many people will be off during the end of year holiday break. Closing this issue since there won't be any...

> Any clue on the check-release failure ? This seems to be failing as part of the `check-python` step, and related to https://github.com/jupyter-server/jupyter_releaser/issues/499. Which was also noticed in https://github.com/voila-dashboards/voici/pull/106. A...

It would be better to get that `check-release` check green, to give more confidence when making releases and catching potential other issues.

https://github.com/jupyter-server/jupyter_releaser/issues/499 is still opened and there is no work-in-progress to fix this on the releaser at the moment. The easiest workaround for now would likely be to skip the `check-python`...

Wondering if this could be the same issue as with Notebook 7 at the moment: 

Thanks @MUFFANUJ! Yeah that looks good, please don't hesitate to open a draft PR so we can have the preview documentation built and then it will be easier to do...