<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>Excellent initiative!
<br>
<br>One question that came to my mind is the lower level metrics.
<br>Is there a need to see some rough metrics on the server performance level?
<br>I'm personally interested in those, but is there a wider interest?
<br>
<br>Tero
<br>
<br>P.S. I narrowed my answer to just the community list.
<br>
<br>----- Original message -----
<br>> Just in case there weren't enough projects erupting around MeeGo, here's
<br>> another.  :D
<br>>
<br>> I think most of us understand that at the root of successful projects
<br>> lies good data.  To that notion, Dawn Foster and I have started an
<br>> effort to establish metrics definitions and reporting solutions for the
<br>> MeeGo community.  As a Data Analyst I am constantly frustrated by how
<br>> frequently reporting is an afterthought and would prefer we get this
<br>> exploration started now instead of waiting for the need.
<br>>
<br>> maemo.org has a solid history of reporting as exemplified by Stephen
<br>> Gadsby's popular bug jars, but for MeeGo we are looking at taking this
<br>> to the next level.
<br>>
<br>> Dawn set up a new wiki page at <a href="http://wiki.meego.com/Metrics">http://wiki.meego.com/Metrics</a> and I have
<br>> added content which I will share here:
<br>>
<br>>
<br>>
<br>> Metrics to capture:
<br>>
<br>>
<br>>  * builds
<br>>  * performance and error metrics
<br>>  * bugzilla reports (Intel has some of this already from Moblin
<br>>  that we can re-use).
<br>>  * various open source aspects
<br>>  * membership / user accounts
<br>>  * mailing list subscriptions / participation
<br>>  * contributor activity
<br>>
<br>>
<br>> Points to consider:
<br>>
<br>>
<br>>  * Reporting solution
<br>>  * Report sharing methods
<br>>  * Public vs Private data
<br>>
<br>> I'll start things off by proposing we look into reporting solutions that
<br>> are highly flexible, scalable and support a variety of typical
<br>> report-sharing methods.  I would consider a good benchmark to
<br>> be MicroStrategy (<a href="http://microstrategy.com/">http://microstrategy.com/</a>) although it would make
<br>> sense to identify good open source alternatives.  MicroStrategy does
<br>> have a free version
<br>> (<a href="http://www.microstrategy.com/freereportingsoftware/">http://www.microstrategy.com/freereportingsoftware/</a>) that could be
<br>> utilized if we don't find that alternative.
<br>>
<br>> I have added Dawn and myself as contributors but feel free to include
<br>> yourself on the list if you would like to participate.
<br>>
<br>> Thanks all,
<br>>
<br>> Randall (Randy) Arnold
<br>> maemo.org community council
<br>> <a href="http://tabulacrypticum.wordpress.com/">http://tabulacrypticum.wordpress.com/</a>
<br>>
<br>>
<br>>
<br>> --------------------------------------------------------------
<br>> Ovi Mail: Get mail on your mobile or the web
<br>> <a href="http://mail.ovi.com">http://mail.ovi.com</a>
<br>>
<br>
<br><Attachment>  ATT00001..txt
<br><br></p>
</body>
</html>