Conversation
Updated maintainer roles and removed two maintainers. This is based on the new Staff Pass Ratio as well as qualitative impact of contributions.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thank you for your contribution! 🎉 PR Rating: ⭐ Track your contributions and see the leaderboard at: tscircuit Contribution Tracker |
rushabhcodes
added a commit
to rushabhcodes/contribution-tracker
that referenced
this pull request
Mar 19, 2026
…le config (regression from tscircuit#321)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updated maintainer roles and removed two maintainers.
This is based on the new Staff Pass Ratio as well as qualitative impact of contributions.
The expectation for maintainers is they do not need multiple reviews for every PR because of basic issues such as naming, not following convention, or not reviewing their own PR to find simple mistakes.
Moreover there are maintainers who pick on issues that have a big impact on customers and there are maintainers who are optimizing for score instead of on helping the users of the project. In fact, I've seen that contributors have picked up user issues then dropped them without communicating that they've dropped them. These contributors can be doing more harm than good.
Clear communication, clean code, and picking important work are the 3 things that make someone trustworthy to maintain!