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. In a chat, Niall suggested a JIRA plugin to notice active non-committers [we were marvelling at a very, very active new contributor in VFS]. That's something that this could do too I think - flagging activity of non-committers. I have a dumb script to show svn commits in individual Jakarta projects this year. I use that to see how active a project is - very dumb I know. I know that Martin uses a script that looks at mails that have happened during a time period as a measure of activity in Jakarta. I'd love to flag emails that haven't been answered on user@ lists [keep meaning to do this in Brett's mboxer lab]. It'd be good to run all this as a copy within the Incubator. ie) treat the Incubator as an umbrella rather than a single project. Maybe we would do the same for Jakarta and WS. Pondering... Brett's examples below are meta information, whereas I'm talking about instance data I think. Anyway; I'm in favour of Brett's below, but also interested in what people think about widening the scope of this to be a whole series of scripts (or whatever) to measure the noise of Apache. Hen On 5/14/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi, I'd like to request a Lab for utilities to assist ASF projects in the creation of accurate and timely board reports. Remembering 3 months of project activity can be difficult, and by the time all the standard information is gathered, there's little time left for discussing the real state of the project. This lab aims to keep track of standard reportable project information over a stated time period, such as: - committers added, departed - PMC members added, departed - releases made - upcoming releases (roadmap) - events / conferences - project level issues Scope could possibly include: - notification of reports due (Marvin) While this could also gather other tools to better understand how a community is operating, that is likely to fit better under a separate lab (such as MBoxer, Pulse) to keep this focused. Challenges: - It may become necessary to record and report on information private to the PMC / membership at the time of the report I haven't spoken to David yet, but I expect this would cross paths with both projects.apache.org and Marvin. This would also be of interest to others that are playing with tools to interact with JIRA and Confluence. Thanks, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
