15:02:06 <ilyashakhat> #startmeeting Stackalytics
15:02:07 <openstack> Meeting started Mon Nov 18 15:02:06 2013 UTC and is due to finish in 60 minutes.  The chair is ilyashakhat. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:11 <openstack> The meeting name has been set to 'stackalytics'
15:02:36 <ilyashakhat> Hi everyone, it's time for our bi-weekly meeting on Stackalytics project
15:03:15 <ilyashakhat> #topic project news
15:04:45 <ilyashakhat> https://blueprints.launchpad.net/stackalytics/+spec/review-punchcard
15:04:52 <ilyashakhat> is available in beta
15:05:52 <ilyashakhat> the link to report is added to contribution summary section
15:06:14 <ilyashakhat> and it shows the activity log for engineer as well as the usual working hours
15:06:18 <ilyashakhat> like that: http://stackalytics.com/report/users/slukjanov
15:07:27 <ilyashakhat> Another blueprint in beta is https://blueprints.launchpad.net/stackalytics/+spec/module-review-backlog-stats
15:08:16 <ilyashakhat> it is also a report, available for modules
15:08:31 <ilyashakhat> it shows list of open reviews, like that: http://stackalytics.com/report/reviews/neutron
15:12:30 <ilyashakhat> #topic New blueprints
15:12:50 <ilyashakhat> We have one new blueprint https://blueprints.launchpad.net/stackalytics/+spec/openstack-status
15:13:46 <ilyashakhat> the author asks some features available in github, like used languages, download stats, etc.
15:15:44 <ilyashakhat> language stats we can calculate from git repo, but OpenStack is mostly python, so there shouldn't be any surprises :)
15:17:34 <ilyashakhat> downloads, git clone stats is not available and a bit useless since code may be checkout by devstack or set from packages
15:18:30 <ilyashakhat> so these features don't seem to be very useful, keep it untouched
15:19:27 <ilyashakhat> One more blueprint that hangs for a couple of months is https://blueprints.launchpad.net/stackalytics/+spec/review-disagreements
15:20:13 <ilyashakhat> it's not hard from math perspective, but requires a way to get list of core engs
15:21:20 <ilyashakhat> basically to get a list of cores for particular project the one should do the following:
15:21:45 <ilyashakhat> get name of gerrit core group
15:22:38 <ilyashakhat> that is easy by running ls-groups command
15:22:52 <ilyashakhat> ex. ssh -p 29418 review.openstack.org gerrit ls-groups --project openstack/python-glanceclient
15:23:17 <ilyashakhat> the core group is the one with -core suffix
15:23:50 <ilyashakhat> then goes tricky/impossible part - to get list of members for that group
15:24:26 <ilyashakhat> authorized user can get it via gerrit ui, but it doesn't accept group name, only id
15:25:48 <ilyashakhat> as an option we can track core members separately
15:31:51 <ilyashakhat> that's all with news from Stackalytics
15:32:09 <ilyashakhat> #topic Open discussion
15:36:35 <ilyashakhat> #endmeeting