Re: [DISCUSSION] Tracking & Visualizing various metrics of the Beam community

Hi, The UI looks cool and powerful. I'm not sure about using the devstats service, since it only has github statistics as I can understand. I would prefer to have single entry point for all of our dashboards: build stats, eng metrics, tests, project health metrics, etc. However, devstats uses

Re: [DISCUSSION] Tracking & Visualizing various metrics of the Beam community

Thanks Udi, I am working on spinning up a test instance. On Tue, Aug 7, 2018 at 11:31 AM Udi Meiri wrote: > These tables look very cool! > > I certainly don't object to using tools made by another organization. The > only issue might be compatibility with our process. > > From my understanding

Re: [DISCUSSION] Tracking & Visualizing various metrics of the Beam community

These tables look very cool! I certainly don't object to using tools made by another organization. The only issue might be compatibility with our process. >From my understanding of the Kubernetes review process, they use Github's tagging feature to specify PR statuses such as LGTM and approval.

Re: [DISCUSSION] Tracking & Visualizing various metrics of the Beam community

tl;dr - is there any objections to trying out DevStats tool created by CNCF? On Mon, Aug 6, 2018 at 3:43 PM Huygaa Batsaikhan wrote: > Continuing the discussion > > about

[DISCUSSION] Tracking & Visualizing various metrics of the Beam community

Continuing the discussion about improving Beam code review, I am looking into visualizing various helpful Beam community metrics such as code velocity, reviewer load, and new