[GitHub] [arrow] westonpace commented on issue #15232: [Documentation] Provide guidance to contributors on getting reviews

[GitBox <gi...@apache.org>]

westonpace commented on issue #15232:
URL: https://github.com/apache/arrow/issues/15232#issuecomment-1376587209

   I'm in favor of more users reading the contributing guidelines / docs (they're great).
   
   I don't know how effective assigning reviewers (or something like code owners) will be.  On the one hand, I suppose I could stop looking at all notifications which is what I do today.  On the other hand, I fear I would become blind to anything that wasn't modification of files I was assigned to (I assume we would just self-assign?)  Have other projects had success with this?
   
   Another suggestion might be to make sure PRs are assigned to at least one reviewer, ping reviewers when they do not respond in a reasonable amount of time and, if too much time passes, assign to a different reviewer or close.  Not sure if that can be automated or would require some kind of human intervention.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org