Require subprojects to lists its members on their team compass. #195
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We require subprojects to have a team compass, but have discovered recently that some subprojects don't list their Council members in a public place. We (the EC) propose amending the requirement to include listing Council members in the team compass.
Zsailer
approved these changes
Dec 5, 2023
vidartf
reviewed
Dec 6, 2023
| @@ -12,7 +12,7 @@ Unless the Software Steering Council (SSC) or the Executive Council (EC) says ot | |||
| - Follow the licensing guidelines and practices of the project ([use of the BSD license and copyright header](https://github.com/jupyter/jupyter/blob/master/LICENSE)). | |||
| - Follow Jupyter’s trademark, branding, and intellectual property guidelines. | |||
| - Conduct its activities in a manner that is open, transparent, and inclusive. This includes coordinating with the Software Steering Council and the Executive Council on mechanisms for information flow and updates to the broader community (details of this, project-wide, will be developed as our new governance model is adopted and implemented). | |||
| - Maintain a publicly visible Team Compass (see e.g. [JupyterHub](https://github.com/jupyterhub/team-compass) or [JupyterLab](https://github.com/jupyterlab/team-compass) for illustration of their structure and content). | |||
| - Maintain a publicly visible Team Compass with a list of the Council members (see e.g. [JupyterHub](https://github.com/jupyterhub/team-compass) or [JupyterLab](https://github.com/jupyterlab/team-compass) for illustration of their structure and content). | |||
There was a problem hiding this comment.
As an aside: What should smaller repos/groups defined below do here? I.e. the ones where "The SSC itself will be the formal Subproject Council". They often do not have a separate org, so therefore cannot have a separate team compass repo.
There was a problem hiding this comment.
@vidartf We have multiple team-compass repos in the jupyter or galready, so we can make another one here, or in whichever org you think it would best fit.
ivanov
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We require subprojects to have a team compass, but have discovered recently that some subprojects don't list their Council members in a public place. We (the EC) propose amending the requirement to include listing Council members in the team compass.