This reminds me of the issue @bistenes identified with module maintenance: “Since everyone maintains everything, no one maintains anything.” We encourage everyone in the community to help manage PRs - and then we look to the same people who always do it because they have always done it. How can we go beyond encouraging “everyone” to manage PRs and instead motivate and empower specific individuals to take ownership of PR management?
I can think of a couple of ways to do this, building on some things that are already in motion:
-
One of the advantages of @bistenes’ module maintenance system is that it would actually lead to more “responsive on PRs. No old PRs collecting dust” because the module maintainers are responsible for reviewing, responding to, and closing PRs. Some module maintainers have already been identified - and are working on identifying others.
-
@burke, haven’t we also integrated PR management into our developer stages?