On 5/14/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
On 5/15/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> So I've a larger thing bouncing around my head that I think this could
> be part of.
>
> I want to report on activity within projects. This is what the board
> really want, rather than the board report's usual bits of activity.
>
> I want it to be immediate rather than a quarterly thing.
I thought any issues that needs immediate reaction are reported
directly to [EMAIL PROTECTED] or [EMAIL PROTECTED]
Might not have been the right word.
I mean being able to go look at a public webpage, or run a command, so
I can see how things are activity-wise right now. Baking things into
quarterly chunks might be a nice way to keep the load low on this.
It'd be too much to let users run reports over all our data (show me
mail activity between Christmas 2004 and Easter 2006), but creating
quarterly data chunks based on when a project reports would be a nice
way to pre-generate the data and mean only publishing static and small
content.
Maybe use Abdera to create it in Atom format :)
Quarter:
Meta
Change in committers
Change in PMC members
Releases (Not sure I would do upcoming, too tricky unless we start
putting release dates in JIRA)
Events/Conferences - tricky to automate it seems to me.
Project level issues - the one I definitely wouldn't automate
Data
SVN activity, # of active committers, spread of commits across
active committers
Mail activity, # of unanswered user mail, # of dev threads, # of
user threads, average length(?)
JIRA/Bugzilla activity, # of unanswered new reports, # of resolved
old reports, # of resolved new reports.
Wiki, # of changes to the wiki.
Quick thought dump.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
