You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
+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?
Following up on this 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
The text was updated successfully, but these errors were encountered: