Skip to content
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

Proposal to add SSC representatives as "owners" on the PyPI Jupyter Organization. #79

Open
Zsailer opened this issue Dec 4, 2024 · 2 comments
Assignees
Labels
community Jupyter community related issues`

Comments

@Zsailer
Copy link
Contributor

Zsailer commented Dec 4, 2024

Following up on this comment:

Also, I think we should open up the "owner" role on the PyPI org to folks on the SSC.

Right now, it's only EC folks. I don't think that's enough hands to help manage this stuff 😅.

Originally posted by @Zsailer in #70 (comment)

I'd like to propose that we considering adding SSC representatives as owners on the Jupyter PyPI organization. Since the SSC members are the arbiters of various technical aspects of the project, I think makes sense to delegate the PyPI ownership to these folks. For example, PyPI owners can add collaborators/teams to PyPI repos; it makes sense for SSC reps to manage this.

cc @Carreau

@Zsailer Zsailer self-assigned this Dec 4, 2024
@Zsailer Zsailer added the community Jupyter community related issues` label Dec 4, 2024
@Zsailer Zsailer moved this to Backlog in EC Priorities and Tasks Dec 4, 2024
@Carreau
Copy link

Carreau commented Dec 5, 2024

+1

@jasongrout
Copy link
Contributor

+1 to having some SSC members have owner role. I don't think we need to have every SSC member (or every EC member) have owner role, but perhaps we ask for some volunteers from SSC, just like we did when figuring out who has admin access to the jupyter enterprise org?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Jupyter community related issues`
Projects
Status: Backlog
Development

No branches or pull requests

3 participants