New repository for Data Registry

[3coins]

Opening this issue to track overall interest in the Data Registry project, and see if other team members are ok with creating a new repository under jupyterlab/jupyterlab-contrib named jupyterlab-dataregistry. The long term intent is to make this feature part of the core JupterLab core packages, so keeping this in jupyterlab-data-explorer does not seem appropriate.

Current PR: jupyerlab-data-explorer:#149. This PR details all the concepts, and current work on the project. There is also a binder link which showcases some sample datasets and the "My Datasets" UI component.

[welcome[bot]]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively. You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:

[fcollonval]

I'm :+1: for creating it in jupyterlab-contrib - so that it is not official. And then propose its integration when its is polished. Similarly to the cell toolbar.

[ellisonbg]

The issue we have is that AWS has approved us to contribute to Jupyter itself so we are unable to post repos in our personal orgs or non-Jupyter governed orgs.

[fcollonval]

The issue we have is that AWS has approved us to contribute to Jupyter itself so we are unable to post repos in our personal orgs or non-Jupyter governed orgs.

I presume that it is then fine to create the repo in the jupyterlab organization - probably stating this is a technology maturation that will eventually land into core.

[ellisonbg]

We may want to discuss having a JupyterLab incubator program for repos like this. Jupyter has this at the global level, but that process is more design for entirely new efforts that are less related to existing subprojects.

On Wed, Mar 30, 2022 at 11:58 PM Frédéric Collonval < @.***> wrote:

The issue we have is that AWS has approved us to contribute to Jupyter itself so we are unable to post repos in our personal orgs or non-Jupyter governed orgs.

I presume that it is then fine to create the repo in the jupyterlab organization - probably stating this is a technology maturation that will eventually land into core.

— Reply to this email directly, view it on GitHub https://github.com/jupyterlab/team-compass/issues/141#issuecomment-1084170402, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGXUDCSLCVD4MQUWA3HCLVCVEK7ANCNFSM5RPOLZPQ . You are receiving this because you commented.Message ID: @.***>

-- Brian E. Granger

Senior Principal Technologist, AWS AI/ML @.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

[jasongrout]

Just to be clear, is the proposal to create/move the jupyterlab-dataregistry repo under either the github.com/jupyterlab or the github.com/jupyterlab-contrib org?

[jasongrout]

In the dev meeting, discussion resolved to renaming the existing repo in the github jupyterlab org to the new name to preserve issues, stars, etc.