David Sean Taylor wrote: > > <SNIP GREAT IDEA/> +1 > 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. :) Ask and you get an answer :) 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
