Plugin and extension system working group

[afshin]

Please comment here if you want to work on designing and building an extension system that addresses some of the current system's shortcomings:

• Lack of schematized everything (settings are schematized, extension definitions require adhering to a specific interface, but it's still pretty under-specified
• Extension authors are inconvenienced by every single major version bump and this is a problem other applications have solved, we can too

There are other goals, too, but these are big ones to try to resolve.

@fcollonval, @blink1073, and I are interested in working on this, but we can't do it alone and would appreciate insight from others. Please indicate if you are interested and let's figure out how and when to work on it.

cc: @bollwyvl

[krassowski]

I would be interested in joining this effort!

[jasongrout]

Please add me to the list

[ericsnekbytes]

Can we add to the list: Make learning and using the extension ecosystem easier for a broader range of people, including those new to the Jupyter stack?

I'm interested in joining this effort.

[bollwyvl]

y'all know i'm down, and have bad ideas for days. avoiding pre-venting here...

...but...

...perhaps we could start a bounded number of discussions, loosely inspired by the Heilmeir Catechism:

• Who is A Stakeholder of the Jupyter client extension ecosystem?
• What is A Problem we have with the Jupyter client extension ecosystem?
• How might we improve the Jupyter client extension ecosystem?
• How might we measure whether the Jupyter client extension ecosystem is improving?

Treating individual suggestions as async, threaded comments (instead of laundry lists here) could allow setting the stage for an eventual kick-off without this linear issue becoming the working group.

[jtpio]

Thanks @afshin for opening this issue 👍

I'm also interested in joining this effort.

[afshin]

(cc: @jupyterlab/jupyterlab-council)

[ivanov]

What are the intended mechanics of a working group?

Treating individual suggestions as async, threaded comments (instead of laundry lists here) could allow setting the stage for an eventual kick-off without this linear issue becoming the working group.

I support this kind of approach, though would caution against a synchronous kick-off, or synchronous meetings in general.

[chbrandt]

I'm interested in joining too