search

jupyter / enhancement-proposals

Enhancement proposals for the Jupyter Ecosystem
https://jupyter.org/enhancement-proposals
BSD 3-Clause "New" or "Revised" License
116 stars 65 forks source link

proposed wording for user facing nb7 messaging #110

Closed paddymul closed 4 months ago

paddymul commented 1 year ago

I'm trying to collaborate/propose tighter messaging around NB7

paddymul commented 1 year ago

I'm making this PR to tighten up the wording of the user facing messaging about NB7.

I'm trying to consider the following user groups

  1. Active users of Jupyter. This group is much less familiar with the day to day goings on of jupyterlab development
  2. Current extension developers. They want to know what changes need to be made to their projects for compatibility.
  3. Future extension developers. They need to be able to quickly understand the Jupyter ecosystem to know which extension system it makes sense to target their extension to. They can deal with more details of the internals than active users.
JohanMabille commented 4 months ago

Hi @paddymul - @JohanMabille from the @jupyter/software-steering-council here.

We're working through old JEPs and closing proposals that are no longer active or may not be relevant anymore. Under Jupyter's new governance model, we have an active Software Steering Council who reviews JEPs weekly. We are catching up on the backlog now. Since there has been no active discussion on this JEP in awhile, I'd propose we close it here (we'll leave it open for two more weeks in case you'd like to revive the conversation). If you would like to re-open the discussion after we close it, you are welcome to do that too.