Re: [Xen-devel] Developer Dashboards for Xen Project sub-projects (need input)

[Dario Faggioli <dario.faggioli@xxxxxxxxxx>]

On lun, 2013-11-25 at 09:35 -0500, Konrad Rzeszutek Wilk wrote:
> > We can do similar things for XAPI and Mirage.
> > 
> > So what I am looking for is
> > a) a discussion on the list on what might be useful, and
> > b) a number of volunteers (ideally one per project) who will work
> > with me and the vendor getting this off the ground
> 
> I like the idea of getting an idea of 'we are getting less and less
> commits in this area' as a way to figure out what needs attention
> (or perhaps no need).
> 
Agreed.

> But not every week, not every month either - quaterly is nice enough.
> Or maybe once a year (say at Xen Summit?). But that should be possible
> already right? Or is it a major pain to create those nice graphs?
> 
Yes, I also agree that we should pick-up a proper periodicity with which
we look at this, or we risk going mad! :-)

> What is the overall goal?
> 
> From my PoV my feeling is that:
>  a). I need to hire more folks
>  b). I have more things we want to do than there are
>      developers.
> 
> And I think the same is true for everybody else. But I don't know
> if this dashboard will help in this regards?
> 
Well, I think it goes way beyond that.

Lars is collecting numbers and plotting graphs similar to the ones this
thing is able to produce from some time now, and, honestly, I think they
provide really useful information. They tell much more than just 'there
is more effort needed in this area', they, if done well, provide
insights about the health of a community that, in my opinion, every Open
Source project should be considering very seriously.

As an example, have a look at his 'community roundup' from XS in
Edinburgh:
http://www.xenproject.org/component/allvideoshare/video/latest/xpds13-welcome.html

So, if this allows for getting even more info with even less (or equal)
effort, I think it's 100% worth it.

> Or is it a way to use that information to figure out overall
> trends of changes + test coverage -> good/bad patch ratio?
> 
That too, I guess. However, I think it's probably something more like
"using that information to as much as possible avoid the risk of dying",
as it happened some years ago! :-P :-P

So, as I said in the other mail, provided what would be needed is made a
bit more clear, I'm up for helping with this.

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

Attachment: signature.asc
Description: This is a digitally signed message part