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 is currently a proposal and is still waiting for team decision on the matter.
--
Over the past few months we've been thinking about how to improve the PR experience for both external contributors and the maintainers of the project. Over the past couple years, there has been an increase in AI generated or statically analyzable PRs. At the same time, the value of being a committer on go-ethereum is high due to potential airdrops. This creates a bad incentive where contributors want to land commits without caring about progressing the projects.
We value the external contributions, even the small stuff. It's part of what makes go-ethereum amazing. But we also have no way to combat contributors who are abusing the system and only submitting low-value pull requests that move around code.
After a lot of deliberation, I am are proposing a collaborator allow-list. It will start out with all known GitHub contributors to the go-ethereum repository. New collaborators can request being added to the list be filling out this short form. We're not looking to do KYC on contributors. We just want to create some very minimal friction to reduce the number of opportunistic and automated pull requests we encounter. Our intention is add contributions regularly and keep the bar to entry relatively low. What this system provides us is a an avenue to restrict contributors who consistently do not change their contributing behavior despite requests from the maintainers.