Hi folks I could deploy it on openshift http://reviewstat-nachi.rhcloud.com/
2014-05-19 20:36 GMT-07:00 Nachi Ueno <na...@ntti3.com>: > Hi Boris > > Ya, I know this stats. > The primary usecase for this patch is helping reviewer assignment for > each patch. > > 2014-05-19 18:50 GMT-07:00 Boris Pavlovic <bo...@pavlovic.me>: >> Hi Nachi, >> >> >> Sorry for question, but did you try stackalytics? >> >> E.g. this page http://stackalytics.com/report/contribution/neutron/30 >> >> Best regards, >> Boris Pavlovic >> >> >> >> >> On Tue, May 20, 2014 at 5:20 AM, Nachi Ueno <na...@ntti3.com> wrote: >>> >>> Hi folks >>> >>> As per neutron discussion, we agreed there is really important to >>> distribute >>> core-reviewer loads. >>> so we got an idea to specify primary/secondary reviewers for each reviews. >>> >>> IMO, this is almost impossible without some helper tool. >>> >>> so, I wrote it. >>> >>> https://www.youtube.com/watch?v=ouS5h5Z-W50&feature=youtu.be >>> >>> This is a review for review stats. >>> https://review.openstack.org/#/c/94288/ >>> # Note, this code is my side work,, so hopefully we can get lower bar >>> for review :) >>> >>> sudo python setup.py develop >>> ./run_server.sh >>> open http://127.0.0.1:8080/ >>> >>> This webui identifies primary/secondary reviewers from comment. >>> so if you put the comment like this, >>> >>> primary: mestery, secondary:maru >>> >>> Kyle, and Maru will be assigned as primary/secondary reviewer. >>> This is regexp "primary:\s*(.+),\s*secondary:\s*(.+)" >>> >>> Otherwise, this webui selects primary/secondary from existing >>> core-reviewer who are reviewing the change set. >>> >>> Some my thoughts for next steps. >>> >>> (1) core-reviewer-scheduler >>> Currently, 208 patch needs core in Neutron related projects. >>> I feel manual assignment by discussion won't work in this scale... >>> >>> I think we need core-reviewer-scheduler such as nova-scheduler too. >>> # I'm not sure cores likes this idea, though >>> >>> (2) launchpad integration >>> Yep, it is great if we can also show priorities by launchpad data in here. >>> >>> (3) Hosting this code in somewhere, (hopefully, in infra) >>> (4) Performance impact for review.openstack.org >>> This code is using a heavy rest api call (get all reviews,comment, >>> reviews for all patches for a project). I hope this code won't kill >>> the review.openstack.org >>> >>> Best >>> Nachi >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev