Steven Silvester

cf https://github.com/jupyterlab/team-compass/issues/146

> Just to be clear, if the hatch solution pans out, is the plan to sunset this project and eventually archive it? Yes, that is correct

Not yet 😅. I'm tracking the migration effort in https://github.com/jupyterlab/hatch-jupyter-builder/issues/54

I like the idea of separating governance from "key contributors", as it appears from the outside that the Steering Council is providing both functions at the moment. Having a long-term...

Hi @choldgraf, thanks for the thoughtful revival. I agree with your points, and have been speaking to several people about how we can move forward with the governance restructure. I...

It might be my military bias, but I like Jupyter Captain better. ;). It might also read better on a resume. Mission Commander implies a single mission to me. Either...

cc @dsblank. We are currently using the [error](https://github.com/Calysto/metakernel/blob/3acf00a9de954ac371585ff5ec706a80d89481a9/metakernel/_metakernel.py#L393) message type for errors emitted from the `%%python` magic in metakernels.

Once https://github.com/pypa/setuptools/pull/2872 is merged and released we can extend the new build functions in the same way we currently do with the other functions in `setuptools.build_meta`.

https://github.com/pypa/setuptools/pull/2872 was closed, and https://github.com/pypa/setuptools/pull/3082 was opened in its stead, but it may be a while before support lands in `setuptools`.

cf https://github.com/jupyter/jupyter-packaging/pull/69#issue-591751095