Remove subpackage maintainer concept #2185
Merged
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.
Description
The repo maintainers have discussed and we feel that the subpackage maintainer concept has grown stale. Originally we wanted to split subpackages amongst ourselves where small groups of maintainers would serve as the failsafe for given subpackages. In practice this meant every subpackage would have had a very limited amount of people who were ultimately responsible. This created unnecessary stress on maintainers to feel like they were required to keep working on the project in order for the subpackage to remain viable.
Ultimately all write access maintainers can help across the repo and have been doing so for an extended period of time. However, there is an added need for reliable submodule owners which is what we've discovered over the past few months. We'll be working on improving that system through #2024
Type of change
Checklist: