Open Carreau opened 2 months ago
cc @jupyter/software-steering-council for awareness
SSC should have met yesterday and on sept 23rd, is there any update @jupyter/software-steering-council ?
@Carreau Notes from previous call:
Current incubator process documented here: https://docs.jupyter.org/en/latest/projects/incubator.html
Next steps:
- Update documentation on how to bring new projects to Jupyter depending on the project (rules of thumb)
- New subproject (e.g. Jupyter-Book)
- New repository in existing subproject
- Potentially: mention contrib / Third-party repositories? Should they be "officially acknowledged" by Jupyter without being part of Jupyter.
- Update governance repository to remove links to attic and incubator - and add link to the documentation mentioned in the previous bullet point.
- Archive jupyter-incubator repository.
- Move spark magic to Jupyter or IPython.
- Move other repositories under Jupyter under the archived state.
tl;dr: In addition to the steps you outlined, we should make sure the docs on jupyter.org are updated from mentioning incubator to mentioning current ways to on-board new projects/repos. The governance text also needs updating as it currently explicitly mentions incubation multiple places, some places with references to the current process:
PS: I don't think a larger vote is need, as I think the SSC will still own the "incubation process", it is just that some tweaks to the governance text would be needed to make it clearer that the SSC is deemed in charge of how incubation is done, but without an explicit link to the incubator org.
Thanks.
This mirrors https://github.com/jupyter-governance/ec-team-compass/issues/51,
There are 4 repos in juyter incubator:
Then archive the org and kick everybody out.
This is in order to start reducing the number of orgs, as managing many orgs is a hassle for many reasons: managing security reports, managing teams, GitHub sponsors, blocking users org wide ... etc.