<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17/06/14 23:53, Daniel Izquierdo
wrote:<br>
</div>
<blockquote cite="mid:53A0B8D6.8020807@bitergia.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 16/06/14 21:25, Ilya Shakhat
wrote:<br>
</div>
<blockquote
cite="mid:CAMzOD1KNqDcUDk=rjAB3PT_7tTL3pnxwnrDOPaj5DmwGd0QHmw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Let me explain how Stackalytics grouping works. <br>
</div>
</div>
</blockquote>
Thanks for the clarification here.<br>
<br>
Stefano, given that it's simple to group projects, a <br>
</blockquote>
<br>
Sorry about this incomplete email u_u. I was trying to wrap up ideas
but well... fat trigger finger<br>
<br>
<br>
Daniel.<br>
<br>
<br>
<blockquote cite="mid:53A0B8D6.8020807@bitergia.com" type="cite">
<blockquote
cite="mid:CAMzOD1KNqDcUDk=rjAB3PT_7tTL3pnxwnrDOPaj5DmwGd0QHmw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
Most of groups are created from the official <a
moz-do-not-send="true" href="http://programs.yaml">programs</a><a
moz-do-not-send="true">.yaml</a>. Every program turns into
item in the module list (colored in violet), for example
'Nova Compute' is a group containing 'nova',
'python-novaclient' and 'nova-specs'. Every type of repo
(integrated, incubated and others) turns into the project
type, for example 'integrated' type would contain all
modules for a chosen release.<br>
<br>
Also Stackalytics has a few custom <a
moz-do-not-send="true"
href="https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json#L7833-L7879">project
types</a>, for example 'infra' is every project under
'openstack-infra' git, or 'documentation' which is the group
'documentation' from programs.yaml. Custom <a
moz-do-not-send="true"
href="https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json#L7749-L7778">module
groups</a> are also possible, but actually used for
stackforge projects only. Currently there's no group for
python clients, but it would be very easy to add such group.<br>
<br>
</div>
Thanks,<br>
Ilya<br>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-06-16 21:57 GMT+04:00
Stefano Maffulli <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:stefano@openstack.org"
target="_blank">stefano@openstack.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="">On Fri 13 Jun 2014 10:51:24 AM PDT,
Stangel, Dan wrote:<br>
> You can also refer to the example of
Stackalytics, who have created<br>
> their own hierarchy and groupings for metrics
reporting:<br>
> <a moz-do-not-send="true"
href="https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json"
target="_blank">https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json</a><br>
<br>
</div>
It's a very neat grouping. It seems to me that the
clients are grouped<br>
with their parent git/gerrit repo (nova with
python-novaclient, under<br>
'Compute' program) and Nova is shown alone. I don't
see the python<br>
clients individual repositories or grouped: is that
correct?<br>
<br>
For the quarterly reports I will need granularity
because I believe<br>
that clients have different dynamics than their
parent project (and if<br>
that proves not to be the case, we can remove this
complexity later and<br>
merge data).<br>
<br>
can you share a concrete example of how you group
things?<br>
<div class="im"><br>
--<br>
Ask and answer questions on <a
moz-do-not-send="true"
href="https://ask.openstack.org" target="_blank">https://ask.openstack.org</a><br>
<br>
</div>
<div class="">
<div class="h5">_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Daniel Izquierdo Cortazar, PhD
Chief Data Officer
---------
"Software Analytics for your peace of mind"
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.bitergia.com">www.bitergia.com</a>
@bitergia
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Daniel Izquierdo Cortazar, PhD
Chief Data Officer
---------
"Software Analytics for your peace of mind"
<a class="moz-txt-link-abbreviated" href="http://www.bitergia.com">www.bitergia.com</a>
@bitergia
</pre>
</body>
</html>