[general] Announcing Melody

[Stefano Mazzocchi <st...@apache.org>]

I'm proud to announce Melody, a testing dashboard for Harmony.

Melody is currently hosted in Geir's office at the currently transient URL

 http://67.86.14.213:10000/

My goal is to move part of this into the Harmony zone.

The main feature of Melody is a graphical history, which is
automatically generated every night out of fresh data.

The past has been 'reconstructed' by taking a snapshot of harmony every
week over the entire history of the project, compile it and running the
latest japitools over it.

I also run japitools without the checks for the SerialUI checks which
generate a lot of false positives for Swing stuff.

Plans for the future include:

 1) add a chart for the number of subscribers to the various lists (I
already have a script for this, but I need somebody with apmail karma to
run it on the apache machine that handles our mail)

 2) add a chart for email traffic

 3) start performing static analysis on the code using tools like
findbugs, PMD and CPD

Comments, suggestions and criticism welcome!

-- 
Stefano.

Re: [general] Announcing Melody

[Tim Ellison <t....@gmail.com>]

Salikh Zakirov wrote:
> Stefano Mazzocchi wrote:
>>  2) add a chart for email traffic
> 
> GMane has a chart for harmony traffic:
> http://dir.gmane.org/gmane.comp.java.harmony.devel

Boy, I wish my portfolio chart looked like that! :-)

Regards,
Tim

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

Re: [general] Announcing Melody

[Salikh Zakirov <Sa...@Intel.com>]

Stefano Mazzocchi wrote:
>  2) add a chart for email traffic

GMane has a chart for harmony traffic:
http://dir.gmane.org/gmane.comp.java.harmony.devel

Re: [general] Announcing Melody

[Tim Ellison <t....@gmail.com>]

Stefano Mazzocchi wrote:
> Also, I know personally two of the authors of that paper and I strongly
> respect their work and motives but I think it's much harder to collect
> data about a community because 'quantity' and 'quality' don't
> necessarily go together.

Sure, the quality is hard to pin down, but as you show it is often
useful to visualize different aspects of a communities 'data' and use
that to draw some conclusions about its effectiveness.

Regards,
Tim

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

Re: [general] Announcing Melody

[Stefano Mazzocchi <st...@apache.org>]

Tim Ellison wrote:
> Stefano Mazzocchi wrote:
>> Plans for the future include:
>>
>>  1) add a chart for the number of subscribers to the various lists (I
>> already have a script for this, but I need somebody with apmail karma to
>> run it on the apache machine that handles our mail)
>>
>>  2) add a chart for email traffic
>>
>>  3) start performing static analysis on the code using tools like
>> findbugs, PMD and CPD
>>
>> Comments, suggestions and criticism welcome!
> 
> At the risk of 'going meta', there are a number of indicators of the
> health of Harmony that would be interesting to plot.  Some relate to the
> codebase (LOC, test passes, API completeness, etc.) and some relate to
> the effectiveness of the community (mailing list activity, jira
> turn-around time, number of committers, etc.)
> 
> The following paper by Crowston et al. [1] has a list of interesting
> measures that you could gather for Harmony.
> 
> [1] http://opensource.mit.edu/papers/crowstonannabihowison.pdf

just to give you an idea of where I'm going with Melody, this is what
I've done for my day job

 http://simile.mit.edu/history/

the code is available under a BSD license at

 http://simile.mit.edu/repository/stats/

Also, I know personally two of the authors of that paper and I strongly
respect their work and motives but I think it's much harder to collect
data about a community because 'quantity' and 'quality' don't
necessarily go together.

I try to be more creative in my community analysis, for example

 http://people.apache.org/~stefano/agora/

-- 
Stefano.

Re: [general] Announcing Melody

[Tim Ellison <t....@gmail.com>]

Stefano Mazzocchi wrote:
> Plans for the future include:
> 
>  1) add a chart for the number of subscribers to the various lists (I
> already have a script for this, but I need somebody with apmail karma to
> run it on the apache machine that handles our mail)
> 
>  2) add a chart for email traffic
> 
>  3) start performing static analysis on the code using tools like
> findbugs, PMD and CPD
> 
> Comments, suggestions and criticism welcome!

At the risk of 'going meta', there are a number of indicators of the
health of Harmony that would be interesting to plot.  Some relate to the
codebase (LOC, test passes, API completeness, etc.) and some relate to
the effectiveness of the community (mailing list activity, jira
turn-around time, number of committers, etc.)

The following paper by Crowston et al. [1] has a list of interesting
measures that you could gather for Harmony.

[1] http://opensource.mit.edu/papers/crowstonannabihowison.pdf

Regards,
Tim

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

Re: [general] Announcing Melody

["Geir Magnusson Jr." <ge...@pobox.com>]

"bugs"?  We don't have "bugs".  They are "contribution opportunities"

:)

geir


Jin Mingjian wrote:
> Good! Do you plan to add some bugs-related charts?
> 

Re: [general] Announcing Melody

[Jin Mingjian <ji...@gmail.com>]

Good! Do you plan to add some bugs-related charts?