From: Wei Liu <wei.liu2@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: Code Review Dashboard (nearly-complete)
Date: Thu, 14 Apr 2016 16:43:42 +0100 [thread overview]
Message-ID: <20160414154342.GC19098@citrix.com> (raw)
In-Reply-To: <9251D040-A69F-4B22-AE66-14434C8EF284@gmail.com>
On Thu, Apr 14, 2016 at 01:26:29PM +0100, Lars Kurth wrote:
> Hi folks,
>
> the code review dashboard is nearly complete. The read-only version is accessible via https://kibana.bitergia.com/xen
>
> We added plenty of documentation in the Documentation menu at the top, which explains how the panels and various use-cases work.
>
> Items still to do:
> * We have not been able to match code reviews that relate to Linux, QEMU, FreeBSD, NetBSD, etc. which are cross-posted on xen-devel@ ... These will currently show up as un-merged and skew the backlog (aka make it bigger than it is). We will look at these at some later point.
> * The data is nearly up-to-date as per 2 days ago, but we have not yet set up the cron-job to update the underlying data set
> * We have not added time filters for release cycles (Xen 4.2, Xen 4.3, ...) : I just have not had the time to map the labels to
The last point is particularly good idea.
>
> But generally it is very good and I believe it should help all members within the Xen community to track their own patches, as well as help reviewers, maintainers and committers.
>
> Feedback is welcome: I can also easily create new views and dashboards, if needed. I will give a demo at the Hackathon, for those who are interested. I believe, the dashboard will really be able to provide some useful insights, as well as help various members in the community.
>
> Please have a look!
>
The upside is that the tool looks very powerful, the downside is that it
is a bit hard to consume information and filter stuff without prior
experience. The way the documentation is arranged is not very
structural and the glossary is missing at the moment. I think that can
be improved.
Wei.
> Best Regards
> Lars
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-14 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 12:26 Code Review Dashboard (nearly-complete) Lars Kurth
2016-04-14 15:43 ` Wei Liu [this message]
2016-04-15 9:05 ` Lars Kurth
2016-04-15 16:56 ` 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=20160414154342.GC19098@citrix.com \
--to=wei.liu2@citrix.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xenproject.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).