Sometimes lists are where the activity is, commits alone don't credit the
essential design and planning effort put in by users commiters and
non-commiters that shapes the product and maps its progress.
d.
This makes me think of all the projects on SourceForge that shoot up
high into the
On Mon, 13 May 2002 20:17, Danny Angus wrote:
Sometimes lists are where the activity is, commits alone don't credit the
essential design and planning effort put in by users commiters and
non-commiters that shapes the product and maps its progress.
Agreed - even worse. Sometimes after these
I don't really think project activity can be calculated from code changes alone. I
would say project activity should cover the complete process of setting up
requirements for the software, designing, implementing, testing and using it.
If Jakarta would have a structured software development
Agreed!
Danny Angus wrote:
Sometimes lists are where the activity is, commits alone don't credit the
essential design and planning effort put in by users commiters and
non-commiters that shapes the product and maps its progress.
d.
This makes me think of all the projects on SourceForge
On Mon, 13 May 2002, Peter Donald wrote:
On Mon, 13 May 2002 20:17, Danny Angus wrote:
Sometimes lists are where the activity is, commits alone don't credit the
essential design and planning effort put in by users commiters and
non-commiters that shapes the product and maps its progress.
: Project Activity
From: Peter Donald [EMAIL PROTECTED]
On Mon, 13 May 2002 20:17, Danny Angus wrote:
Sometimes lists are where the activity is, commits alone don't credit
the
essential design and planning effort put in by users commiters and
non-commiters that shapes the product and maps its
General List [EMAIL PROTECTED]
cc:
Subject:Re: Project Activity
On Mon, 13 May 2002, Peter Donald wrote:
On Mon, 13 May 2002 20:17, Danny Angus wrote:
Sometimes lists are where the activity is, commits alone don't credit
the
essential design and planning effort put
Back in mid March there was a discussion around the jakarta overview (
http://jakarta.apache.org/site/overview.html ) and what / wasn't a good
measure of project activity. My comment back then was commits on a project
are a good indicator.
So anyway, I've added this reporting into the cvs
I think this might be what you mean by file activity, but might not.
Aren't there two types of project activity. Developer activity and user
activity. Having no developer activity is not a bad sign if there is high
user activity, ie) sign of a solid/stable piece of code.
Now I don't know of any
I think that's pretty cool functionality. I don't agree with your way
of judging project activity.. Thats like trying to put a metric on how
blue the sky is today. I'm sure you could but what of the day where
your metric says its grey but I'm looking up and seeing blue (perhaps
because a grey
lines today? :D
- Leo
On Sat, 2002-05-11 at 17:07, [EMAIL PROTECTED] wrote:
Back in mid March there was a discussion around the jakarta overview (
http://jakarta.apache.org/site/overview.html ) and what / wasn't a good
measure of project activity. My comment back then was commits on a project
11 matches
Mail list logo
