cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <nicola...@apache.org>
Subject Re: [PROPOSAL] Cocoon-apps CVS module
Date Fri, 09 Aug 2002 08:40:56 GMT

Ivelin Ivanov wrote:
> Thanks for the clarification.
> 
> I like the idea of splitting applications as a parallel CVS repo for
> mutliple reasons.
> 
> However is the number of Cocoon apps really big enough to expand beyond
> scratchpad just yet?

Don't look at it from the apps perspective, but from the Cocoon core 
perspective.
It's not that apps need to get separated from the core as that the core 
needs the apps to get off.

> Wyona, CocoBlog, Portal. What else?
> 
> Slashedit is a demo, not a full blown app. Wrong?

Everything is a demo in Cocoon ;-)
It should be an app.

> I consider the Authentication, XMLForm & i18n extensions, which need to
> mature and eventually become part of 2.1 core.

These are not apps, these are components, with their demos.
They remain in the Cocoon CVS.

> Isn't it most important to stabilize the build,

Exactly. This is a step to stabilize it.
Complexity has to be reduced, and dependencies cleared.

> finish the documentation

That is going well on its own.

> effort and prepare cocoon 2.1 with forrest for prime time.

Again, it's on its own.

> If I remember correctly Stefano's release plan, he wanted 2.1 early next
> year. One year release cycle is a good rythm that we shouldn't disturb if
> possible.

This is to make it easier to manage the /beast/.

> Are we not taking on too many tasks at once, risking neither one to be done
> right and within a reasonable time frame.

FUD

> A month ago everyone was very excited about Dianna's initiative to
> coordinate the project documentation. Now, there are hardly any emails on
> the cocoon-doc list. We moved to the next exciting thing...again.

No. Wiki is the next step in documentation, and separating the Slashedit 
can make us help understand better how to make a Cocoon-based structured 
wiki for Forrest.

> Documentation is still a big problem.
> Look at the emails on the cocoon-user list. People are asking for
> documentation and examples.
> Let's finish that first and then integrate with Forrest.

They don't ask about docs on the cocoon-apps, so there is no big deal here.
I volunteered to do the move, so why is it going to slow you?

> Am I totally out of whack here ?-)

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message