Steven Silvester

We had discussion today about how to evolve contributed extensions, documented in #52

> maybe we could request the beta Done! ``` jupyterlab has been added to the new projects beta waitlist. Please make sure your primary email address is up to date....

I support publishing under the @jupyterlab org and considering both for being brought into this GitHub org. We may also want to consider a separate set of "known good" orgs...

I'd say it is a fairly reasonable outcome for folks to publish an example just to try out the mechanism, and the number of published examples bears that out ;).

Not right now, we'd have to add another tag or some other filter criteria. In the meantime, I'd say it is fair to at least strip out xkcd and apod...

We don't publish to conda directly. It is done via merging a pull request on the conda-forge repo.

AFAIK the only remaining issue is recovery codes: https://github.com/pypa/warehouse/issues/5800

Fair, we could keep `PYPI_TOKEN` and recommend against using it unless using a private repository. We would still want to get rid of `TWINE_USERNAME` since it should always be `__token__`,...

Yeah, that should work, without any changes to core.

Yeah, I don't see a way around that, since the assets are tied to the version bump commit.