-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CZI proposal on documentation and maintenance: steering council approval #128
Comments
+1 from me. |
👍 too, thanks for putting this out in the open! |
+1 as well... IMHO, this is super important for this transitional phase. |
Thanks all for the positive replies and support. We plan to submit the letter of intent by Friday (Apr. 15th). |
The letter of intent has been submitted - the final version can be seen in the jupyterlab/frontends-team-compass#140. |
The letter of intent has been accepted. Time to write the full application. |
We (QuantStack) are working on a CZI EOSS 5 proposal targeting the documentation and maintenance of JupyterLab v4 & Jupyter Notebook v7.
As discussed 10 days ago, the proposal is focusing on the known and unknown (will happen after the release) challenges relevant to the major technological stack shift of Jupyter Notebook v7 (the backend will be the independent jupyter server and the frontend will be built from JupyterLab plugins).
The draft letter of intent is opened at jupyterlab/frontends-team-compass#140.
This request of approval follows the process done for the CZI proposal on accessibility #100. Hence we (QuantStack) would like to request formal approval from the steering council to move forward with this work.
Don't hesitate to comment and to propose changes on the current letter of intent.
The text was updated successfully, but these errors were encountered: