I just heard about mention-bot at PyCon 2016 <https://www.youtube.com/watch?v=gRFHvavxnos>:
https://github.com/facebook/mention-bot Do you have a GitHub project that is too big for people to subscribe to all the notifications? The mention bot will automatically mention potential reviewers on pull requests. It helps getting faster turnaround on pull requests by involving the right people early on. mention-bot checks the blame history for the files modified by a PR and automatically pings the most likely candidates for review. I wonder if it would work well for us. Nick On Thu, May 19, 2016 at 11:47 AM Nicholas Chammas nicholas.cham...@gmail.com <http://mailto:nicholas.cham...@gmail.com> wrote: I’ve also heard that we should try to keep some other instructions for > contributors to find the “right” reviewers, so it would be great to see > suggestions on that. For my part, I’d personally prefer something > “automatic”, such as easily tracking who reviewed each patch and having > people look at the commit history of the module they want to work on, > instead of a list that needs to be maintained separately. > > Some code review and management tools like Phabricator have a system for > this <http://phacility.com/phabricator/herald/>, where you can configure > alerts to automatically ping certain people if a file matching some rule > (e.g. has this extension, is in this folder, etc.) is modified by a PR. > > I think short of deploying Phabricator somehow, probably the most > realistic option for us to get automatic alerts like this is to have > someone add that as a feature to the Spark PR Dashboard > <https://spark-prs.appspot.com/>. > > I created an issue for this some time ago if anyone wants to take a crack > at it: https://github.com/databricks/spark-pr-dashboard/issues/47 > > Nick > > > On Thu, May 19, 2016 at 11:42 AM Tom Graves <tgraves...@yahoo.com.invalid> > wrote: > >> +1 (binding) >> >> Tom >> >> >> On Thursday, May 19, 2016 10:35 AM, Matei Zaharia < >> matei.zaha...@gmail.com> wrote: >> >> >> Hi folks, >> >> Around 1.5 years ago, Spark added a maintainer process for reviewing API >> and architectural changes ( >> https://cwiki.apache.org/confluence/display/SPARK/Committers#Committers-ReviewProcessandMaintainers) >> to make sure these are seen by people who spent a lot of time on that >> component. At the time, the worry was that changes might go unnoticed as >> the project grows, but there were also concerns that this approach makes >> the project harder to contribute to and less welcoming. Since implementing >> the model, I think that a good number of developers concluded it doesn't >> make a huge difference, so because of these concerns, it may be useful to >> remove it. I've also heard that we should try to keep some other >> instructions for contributors to find the "right" reviewers, so it would be >> great to see suggestions on that. For my part, I'd personally prefer >> something "automatic", such as easily tracking who reviewed each patch and >> having people look at the commit history of the module they want to work >> on, instead of a list that needs to be maintained separately. >> >> Matei >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org >> For additional commands, e-mail: dev-h...@spark.apache.org >> >> >>
