Reuven, that's great. In this thread, we can continue discussing the usage of review tools, dashboards, and metrics.
On Tue, Jun 26, 2018 at 5:27 PM Reuven Lax <re...@google.com> wrote: > So I suggested a while ago that we create a code-review guidelines doc, > and in fact I was coincidentally just now drafting up a proposal doc. I'll > share my proposal doc with the dev list soon. > > On Tue, Jun 26, 2018 at 5:18 PM Huygaa Batsaikhan <bat...@google.com> > wrote: > >> Hi, I've been looking into ways to improve Beam's code review process >> based on previous discussions on dev list and summits, and I would like to >> propose improvement ideas. Please take a look at: >> https://s.apache.org/beam-code-review. >> >> Main proposals suggested in the doc are: >> >> 1. Create a code review guideline document. >> 2. Build/setup code review tools and dashboards for Beam. >> 3. Collect metrics to monitor Beam's code review health. >> >> Feel free to add comments in the doc. I am looking for all sorts of >> suggestions including existing code review guidelines, potential code >> review tools etc. >> >> Thanks so much, >> Huygaa >> >
