You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Kuckartz <A....@ping.de> on 2004/05/04 12:17:38 UTC
Re: Why ${this.Project} is successful?]
Some of these points are closely related.
A "rapid release schedule" to "to keep the project bug-free" very much depends
on automatic "regression tests". Using Gump would be an important step. (See
http://gump.cocoondev.org/ and http://gump.apache.org/). But to do that a
cocoonified build-process would help - and that would perhaps also help with "up
and running in ten minutes or less".
Andreas
----- Original Message -----
From: "Andreas Hartmann" <an...@apache.org>
To: <le...@cocoon.apache.org>
Sent: Tuesday, May 04, 2004 9:48 AM
Subject: [Fwd: Why ${this.Project} is successful?]
> Here's a mail from Derek Hohls to cocoon-users:
>
> <snip>
> How are we doing in comparison to our peers - see:
> http://www.hibernate.org/38.html
>
> Think about how Cocoon is doing on these points which
> are, I think, valid for pretty much any OS project -
> but even more so as the scope gets wider, new features
> are added and the community grows in both size and
> range (from newbies to veterans, with a bias towards the
> former...)
>
> Derek
> </snip>
>
> Looking at the points on the linked page, I have to
> admit that Lenya could do better in some of them :)
>
> > rapid release schedule
>
> Massive potential for improvement.
>
> > regression tests
>
> The same. But I think this is quite difficult
> in a web-based application.
>
> > do one thing well
>
> This has been discussed quite frequently and
> there are different opinions in the community ...
>
> > avoid over-design
>
> I think we score quite high at this.
>
> > a central vision
>
> > documentation
>
> This one has strongly improved during the last
> months, thanks to all the external contributors.
>
> > avoid standardsism
>
> > up and running in ten minutes or less!
>
> This has also improved.
>
> > developer responsiveness
>
> "24 hours is a good target for the average response
> time between a bug report and the CVS fix."
>
> This sounds impracticable, doesn't it?
>
> > easily update-able wiki pages.....
>
> We have them.
>
> -- Andreas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Gump (Re: Why ${this.Project} is successful?])
Posted by Andreas Kuckartz <A....@ping.de>.
I just found this:
http://lsd.student.utwente.nl/gump/cocoon-lenya/cocoon-lenya/index.html
Andreas
----- Original Message -----
From: "Andreas Kuckartz" <A....@ping.de>
To: "Lenya Developers List" <le...@cocoon.apache.org>
Sent: Tuesday, May 04, 2004 12:17 PM
Subject: Re: Why ${this.Project} is successful?]
> Some of these points are closely related.
>
> A "rapid release schedule" to "to keep the project bug-free" very much depends
> on automatic "regression tests". Using Gump would be an important step. (See
> http://gump.cocoondev.org/ and http://gump.apache.org/). But to do that a
> cocoonified build-process would help - and that would perhaps also help with
"up
> and running in ten minutes or less".
>
> Andreas
>
> ----- Original Message -----
> From: "Andreas Hartmann" <an...@apache.org>
> To: <le...@cocoon.apache.org>
> Sent: Tuesday, May 04, 2004 9:48 AM
> Subject: [Fwd: Why ${this.Project} is successful?]
>
>
> > Here's a mail from Derek Hohls to cocoon-users:
> >
> > <snip>
> > How are we doing in comparison to our peers - see:
> > http://www.hibernate.org/38.html
> >
> > Think about how Cocoon is doing on these points which
> > are, I think, valid for pretty much any OS project -
> > but even more so as the scope gets wider, new features
> > are added and the community grows in both size and
> > range (from newbies to veterans, with a bias towards the
> > former...)
> >
> > Derek
> > </snip>
> >
> > Looking at the points on the linked page, I have to
> > admit that Lenya could do better in some of them :)
> >
> > > rapid release schedule
> >
> > Massive potential for improvement.
> >
> > > regression tests
> >
> > The same. But I think this is quite difficult
> > in a web-based application.
> >
> > > do one thing well
> >
> > This has been discussed quite frequently and
> > there are different opinions in the community ...
> >
> > > avoid over-design
> >
> > I think we score quite high at this.
> >
> > > a central vision
> >
> > > documentation
> >
> > This one has strongly improved during the last
> > months, thanks to all the external contributors.
> >
> > > avoid standardsism
> >
> > > up and running in ten minutes or less!
> >
> > This has also improved.
> >
> > > developer responsiveness
> >
> > "24 hours is a good target for the average response
> > time between a bug report and the CVS fix."
> >
> > This sounds impracticable, doesn't it?
> >
> > > easily update-able wiki pages.....
> >
> > We have them.
> >
> > -- Andreas
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org