Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-12 Thread Jeremy Stanley
On 2017-06-12 14:07:51 -0700 (-0700), Ken'ichi Ohmichi wrote: [...] > The difference between current stackalytics config and the above API > is stackalytics contains gerrit-id and launchpad-id on the config > but the API doesn't. I guess we can use e-mail address instead of > gerrit-id and launchpa

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-12 Thread Ken'ichi Ohmichi
2017-06-08 10:51 GMT-07:00 Jeremy Stanley : > On 2017-06-08 09:49:03 -0700 (-0700), Ken'ichi Ohmichi wrote: >> 2017-06-08 7:19 GMT-07:00 Jeremy Stanley : > [...] >> > There is a foundation member directory API now which provides >> > affiliation details and history, so if it were my project (it's >

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-11 Thread Dmitry Tantsur
On 06/11/2017 03:17 PM, Matt Riedemann wrote: On 6/8/2017 12:57 AM, Adam Harwell wrote: As a core reviewer for LBaaS I actually find Stackalytics quite helpful for giving me a quick snapshot of contributions, and it lines up almost perfectly in my experience with what I see when I'm actually re

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-11 Thread Matt Riedemann
On 6/8/2017 12:57 AM, Adam Harwell wrote: As a core reviewer for LBaaS I actually find Stackalytics quite helpful for giving me a quick snapshot of contributions, and it lines up almost perfectly in my experience with what I see when I'm actually reviewing and working with people (if you know w

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-09 Thread Mike Perez
On June 8, 2017 at 07:20:23, Jeremy Stanley (fu...@yuggoth.org) wrote: > > On 2017-06-07 16:36:45 > > -0700(http://airmail.calendar/2017-06-07%2016:36:45%20PDT) > (-0700), Ken'ichi Ohmichi wrote: > [...] > > one of config files is 30KL due to much user information and that > > makes the maintenanc

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 Thread Jeremy Stanley
On 2017-06-08 09:49:03 -0700 (-0700), Ken'ichi Ohmichi wrote: > 2017-06-08 7:19 GMT-07:00 Jeremy Stanley : [...] > > There is a foundation member directory API now which provides > > affiliation details and history, so if it were my project (it's > > not though) I'd switch to querying that and dele

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 Thread Ken'ichi Ohmichi
2017-06-08 7:19 GMT-07:00 Jeremy Stanley : > On 2017-06-07 16:36:45 -0700 (-0700), Ken'ichi Ohmichi wrote: > [...] >> one of config files is 30KL due to much user information and that >> makes the maintenance hard now. I am trying to separate user part >> from the existing file but I cannot find th

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 Thread Paul Belanger
On Thu, Jun 08, 2017 at 02:11:18PM +, Jeremy Stanley wrote: > On 2017-06-08 09:22:48 -0400 (-0400), Paul Belanger wrote: > [...] > > We also have another issue where we loose access to gerrit and our apache > > process pins CPU to 100%, these might also be low hanging friut for people > > wanti

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 Thread Jeremy Stanley
On 2017-06-07 16:36:45 -0700 (-0700), Ken'ichi Ohmichi wrote: [...] > one of config files is 30KL due to much user information and that > makes the maintenance hard now. I am trying to separate user part > from the existing file but I cannot find the way to make a > consensus for such thing. There

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 Thread Jeremy Stanley
On 2017-06-08 09:22:48 -0400 (-0400), Paul Belanger wrote: [...] > We also have another issue where we loose access to gerrit and our apache > process pins CPU to 100%, these might also be low hanging friut for people > wanting to get involved. [...] Wasn't that fixed with a new lower-bound on par

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-08 Thread Paul Belanger
On Wed, May 17, 2017 at 06:55:57PM +, Jeremy Stanley wrote: > On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote: > [...] > > we need help with completing the migration to infra. If interested > > you can reach out to fungi (Infra team PTL) nor mrmartin (who > > currently helps with the

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-07 Thread Adam Harwell
I wish I'd made it to that Forum session, but here's my two cents now: As a core reviewer for LBaaS I actually find Stackalytics quite helpful for giving me a quick snapshot of contributions, and it lines up almost perfectly in my experience with what I see when I'm actually reviewing and working

Re: [openstack-dev] [forum] Future of Stackalytics

2017-06-07 Thread Ken'ichi Ohmichi
2017-05-17 11:55 GMT-07:00 Jeremy Stanley : > On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote: > [...] >> we need help with completing the migration to infra. If interested >> you can reach out to fungi (Infra team PTL) nor mrmartin (who >> currently helps with the transition work). > [.

Re: [openstack-dev] [forum] Future of Stackalytics

2017-05-17 Thread Jeremy Stanley
On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote: [...] > we need help with completing the migration to infra. If interested > you can reach out to fungi (Infra team PTL) nor mrmartin (who > currently helps with the transition work). [...] The main blocker for us right now is addressed b

[openstack-dev] [forum] Future of Stackalytics

2017-05-17 Thread Thierry Carrez
Hi! Following the forum, the session moderators should summarize how their session went and detail next steps, to give opportunity to those who couldn't be around in person to catch up if interested. Here is my quick summary of the "Should we kill Stackalytics" session. You can find the etherpad a