On Monday, December 15, 2003, at 02:51 PM, Carsten Ziegeler wrote:
David Sean Taylor wrote:+1
<SNIP GREAT IDEA/>
:) Ask and you get an answer :)Regarding Cocoon's portal, I don't understand Cocoon's portal well enough to say it should or should not be a part of portals.apache.org. I have doubts that they would want to decouple from Cocoon, but you don't know until you ask.
:)
No, the cocoon portal is from the code size a big extension to cocoon. Although we haven't discussed this a lot, it seems that we agree that the long-term plan is to move the portal out of cocoon anyway, e.g. as a Cocoon sub project (this is planned after the 2.2 release of Cocoon which might happen sometime next year). So, some of us already think that decoupling is a good think for Cocoon. And I personally think that moving it to a portal project at apache is better than as a subproject in cocoon.
I guess there will be a great overlap between jetspeed-2 and the cocoon portal, so having them at the same place seems to be the best solution. This would minimize could duplication etc.
Carsten
I am very happy to hear that!
Having two portal solutions at portals.apache.org will be great for the end users.
The projects have different implementations and philosophies, and this gives users choice right here at Apache.
The projects will benefit from shared code and discussions, and being part of the same community.
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
