jashkenas / jashkenas/backbone
Community question: who is interested in reviewing my pull requests?
- Dominant language
- JavaScript
- Stars
- 28.1k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
I have taken on the burden of maintaining Backbone. I also happen to believe that ideally, each code change should be reviewed by somebody other than the author.
When somebody else submits a pull request (please do!), I can obviously review it. When I submit a pull request myself (which I expect to do a lot), it is not so obvious who might review it.
So far, I've been blindly `@mention`ing people who I thought (or hoped) might be interested in reviewing. I now feel that this pattern is not sustainable; I will miss people who are interested and annoy people who are not. Instead, I would like to actually know which people are interested in reviewing.
Of course, I'm hoping that expert contributors are interested, but non-expert reviewers are welcome, too. The more reviewers, the better.
- [ ] If you are interested in reviewing and you are already watching the repo so you will be aware of new pull requests, please leave a 👀.
- [ ] If you are interested in reviewing and you would like to be `@mention`ed to draw your attention, leave a 🚀.
- [ ] If you welcome *formal* review requests (so you see "review requested" in your GitHub notifications), leave a ❤️. If you opt-in for this, please also leave a comment to let me know what you consider an acceptable frequency and how quickly you expect to be able to respond (on average).
- [ ] If you just feel like voting, leave a 👍.
Text replies for other reasons also welcome, of course.
For the last time, a blind CC (sorry): @paulfalgout @ogonkov @GammaGames @chkpnt @jcbrand @karloscarweber @Rayraz @taburetkin @alanhamlett
Contributor guide
Research direction
This is a community coordination request and names no source files, tests, or implementation entry points. Read the issue discussion and repository contribution guidance first; the requested outcome is a set of contributors indicating how they want to review pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100