Although they are absolutely “server” based, it remains to be seen whether the gateway projects, Kernel or Enterprise, will ever use Jupyter Server. I suppose one could argue that Kernel Gateway’s HTTP Personality has the “best shot” at becoming an ExtensionApp. (In fact, I think it would make a great POC datapoint for JS.) I could also envision there being enterprise-level extensions (most likely surrounding HA and, possibly, multi-tenancy) at some point, although I don’t think “gateway” would necessarily be appropriate.
Based on Zach and Chris’s responses, I think we’re converging on the following…
- Go ahead and create a separate Jupyter Server category.
- At some point, depending on how the existing gateway projects evolve relative to their migration to Server, create sub-categories.
@choldgraf - A good candidate sub-category for JS would be Kernel Providers. This is probably where most of EG’s functionality will move. Not sure we need to create that right away, but I think its a good example of a sub-category relative to JS.
I didn’t realize that there could be sub-categories, so I’m wondering if we could have Gateway Projects - with Kernel Gateway and Enterprise Gateway as sub-categories?