You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 @mentioning 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 @mentioned 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.
I've been following this repo for many years, but my last backbone maintenance project wound down a few months ago and my in-depth familiarity with the code-base has faded over time. I enjoy thinking through conceptual decisions about features and the direction of the API though and those don't always require the deepest familiarity with the source code. Feel free to @mention me from time to time if you feel like you are short on this type of input you expect reduced familiarity with the source won't be too much of a disadvantage.
I haven't really dug into the code, but I do use the library regularly for work and would be happy to do the occasional review! Glad to see some organization going on and look forward to progress 🙂
Pretty invested in Bb and Marionette. You can put me on things to review. I'm generally available at some time during the week for reviews. But it's difficult to give exact estimates over time. My day job supports me working on the OSS we use, but it's somewhat dependent on workload.
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.
@mention
ed to draw your attention, 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
The text was updated successfully, but these errors were encountered: