Thomas Kluyver

There is a related proposal for bi-directional support in the notebook: https://github.com/jupyter/notebook/issues/2178

+1 to using Github's standard labels for these things

Yeah, I'm not exactly sure when 'help wanted' makes sense. Maybe we should use it to mean that we don't plan to work on it ourselves, but: - It's not...

That's fine by me. So to summarise: - *help wanted* means there's something identified to do, but the core team is not about to do it. - *good first issue*...

`won't fix` is more like 'no', rather than 'ok if someone else does it'.

@damianavila I think that's deliberate-ish. As I see it, we support installing nbextensions inside an environment - so you could e.g. make a conda package of livereveal - but they...

I've wondered about this before. The language server protocol is what Microsoft designed to provide different language backends for VS Code. That seems superficially similar to our own [messaging protocol](http://jupyter-client.readthedocs.io/en/latest/messaging.html)....

I'd be wary of the 'handle anything thrown at us' model: while it makes it easier to dump a load of stuff into a file and hope it works, it...

> For example, should this invoke the build-backend in some way to retrieve the name? The relevant PEP is [621](https://www.python.org/dev/peps/pep-0621/). If backends implement this, the spec says the name field...

I'm happy enough to have the special case inside pep517, as #130 implements, if that's the easiest way to do it. I just hadn't got round to looking at it...