-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Move jupyter-server-ydoc in this organization #175
Labels
enhancement
New feature or request
Comments
cc @jupyterlab/jupyterlab-council what do you think? |
I don't have very strong feelings about which org the repo is in.
…On Thu, Jan 26, 2023 at 4:48 AM Frédéric Collonval ***@***.***> wrote:
cc @jupyterlab/jupyterlab-council
<https://github.com/orgs/jupyterlab/teams/jupyterlab-council> what do you
think?
—
Reply to this email directly, view it on GitHub
<#175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAGXUE7YHRGD3VZWWADW43WUJXC3ANCNFSM6AAAAAAUHOUMDI>
.
You are receiving this because you are on a team that was mentioned.Message
ID: ***@***.***>
--
Brian E. Granger
Senior Principal Technologist, AWS AI/ML ***@***.***)
On Leave - Professor of Physics and Data Science, Cal Poly
@ellisonbg on GitHub
|
Moving the repo to the |
A consensus to move the repository in jupyterlab organization was reached during the weekly meeting. A separate discussion about that package being shipped by default with JupyterLab 4.0.0 is happening there |
The repository is now in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
A target for 4.0.0 is to extract collaboration feature of JupyterLab core (jupyterlab/jupyterlab#13726).
The rational behind it:
ContentsManager
)The remaining question is where to place the extracted code.
Proposed Solution
The logic seems to move the code in a repository within this organization as it comes from core JupyterLab and it is officially supported by the JupyterLab development team. But as it interacts directly with an existing server extension, I'ld like to propose moving the code in that server extension repository (to avoid repository explosion) and to move that repository from
jupyter-server
tojupyterlab
organization.The text was updated successfully, but these errors were encountered: