Re: [Xen-devel] Code Review Dashboard (nearly-complete)

[Lars Kurth <lars.kurth.xen@xxxxxxxxx>]

> On 14 Apr 2016, at 16:43, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
> 
> 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.

Good. Will let you know when it is there.


>> 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.

Agreed. There is a lot of stuff, and it will take a while to get used to some 
of it.

> The way the documentation is arranged is not very
> structural and the glossary is missing at the moment. I think that can
> be improved.

I think I will move the docs to the wiki and then just have a single document 
widget that links to it. The markdown and layout of the docs is just not really 
suitable to use the built-in documentation. Also there is no TOC, etc.

But before I do this, I will give a couple of demos at the Hackathon and see 
which areas of the UI and tool need more descriptions than others.

Regards
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel