docs: Relax CC requirement for maintaining. #690
Closed
Conversation
This file contains hidden or 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
This can happpen when there is a team that maintains a repo and the team is adding a new member. That new member will not have gone through the CC process yet but will be listed as a maintainer by virtue of being on the team in the `catalog-info.yaml` file. Allow for this to be possible. In practice we won't run into a lot of issues with this as long as at least one person on the maintaining team can merge maintenance work.
kdmccormick
requested changes
Mar 10, 2025
There was a problem hiding this comment.
I was thinking something more like this: #691
If we approve and merge that ^, do you think this change ("on track to become or already be") would be necessary too?
|
Yea, I like that better, let's go with that, I don't think we need both. |
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.
This can happpen when there is a team that maintains a repo and the team
is adding a new member. That new member will not have gone through the
CC process yet but will be listed as a maintainer by virtue of being on
the team in the
catalog-info.yamlfile. Allow for this to bepossible. In practice we won't run into a lot of issues with this as
long as at least one person on the maintaining team can merge
maintenance work.