From: Daniel Izquierdo <dizquierdo@bitergia.com>
To: xen-devel@lists.xen.org
Subject: Re: Prototype Code Review Dashboards (input required)
Date: Wed, 9 Mar 2016 18:06:20 +0100 [thread overview]
Message-ID: <56E0580C.6010801@bitergia.com> (raw)
In-Reply-To: <56D76D17.3030209@bitergia.com>
On 02/03/16 23:45, Daniel Izquierdo wrote:
[...]
>> Given, that the Xen-A1.A2.A3 dash board is quite busy, we should keep
>> that separate.
>>
>>
>>
>
> I still have to upload this, sorry for the delay!
>
>
> This is a summary of the actions unless extra comments are provided:
>
> * Balance should be calculated as reviews - patches
> * Cleaning actions in the dataset when finding multiple email addresses
> * Bugs with the post-ack comments
> * Add the extra panel defined as use case A.0
>
> Some extra feedback or discussion:
>
> * Reduce the flags to be used. We're currently using all of the flags
> available and sub-setting the reviewed-by and acked-by
> * I'm not sure if we need extra discussion related to the merge:1 filter
> * Check how reviews and patches are counted. Any new version of a
> patch is counted as a new patch. Any new reviewed-by flag in a reply
> to a patch is counted as a review.
From those actions, this is the current status:
* Balance should be calculated as reviews - patches (DONE)
* Cleaning actions in the dataset when finding multiple email addresses
(still in progress and I should add your comments in a previous email)
* Bugs with the post-ack comments (DONE)
* Add the extra panel defined as use case A.0 (DONE)
* Tables at the bottom of the panels contains proper information and not
all of the fields (DONE)
* Do not count comments to your own patches (to be done)
Regarding to the extra feedback:
* Reduce the flags to be used. We're currently using all of the flags
available and sub-setting the reviewed-by and acked-by.
** This opened a new discussion about the CC mailing lists and the
creation of some buckets of info.
* I'm not sure if we need extra discussion related to the merge:1 filter
** No advances
* Check how reviews and patches are counted. Any new version of a patch
is counted as a new patch. Any new reviewed-by flag in a reply to a
patch is counted as a review.
** No advances
Regards,
Daniel.
--
Daniel Izquierdo Cortazar, PhD
Chief Data Officer
---------
"Software Analytics for your peace of mind"
www.bitergia.com
@bitergia
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-09 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 13:53 Prototype Code Review Dashboards (input required) Lars Kurth
2016-03-01 17:04 ` Lars Kurth
2016-03-02 22:45 ` Daniel Izquierdo
2016-03-03 18:55 ` Lars Kurth
2016-03-04 8:42 ` Jan Beulich
2016-03-04 9:05 ` Lars Kurth
2016-03-04 9:21 ` Jan Beulich
2016-03-07 17:24 ` Lars Kurth
2016-03-09 16:58 ` Daniel Izquierdo
2016-03-09 17:06 ` Daniel Izquierdo [this message]
2016-03-09 20:03 ` Lars Kurth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E0580C.6010801@bitergia.com \
--to=dizquierdo@bitergia.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).