It's a great idea to have a single entry point for several apache portal projects.
<snip> ... > 2. To encourage developers from all Apache portal projects to work > together and share common code Pluto shares already code with Jetspeed and structuring the different portal projects under portals.apache.org would encourage more code sharing. > 3. To develop Portlet Applications and Portlet Application frameworks > at portals.apache.org and grow the portal community here. Portlet > Applications will be managed as sub-projects. > Portal Applications will enable a higher level of application > development while cleanly separating the development of portals such as > Jetspeed from applications code. > 4. To provide a community for portal-related Java and XML standards and > reference implementations under the ASF license at portals.apache.org > > Note that I have cross-posted to all three (Jetspeed, Pluto, and > WSRP4J) mailing lists. > To respond across mailing lists, respond to ALL. > Not sure if this is the best solution, since Im going to receive 3 > emails being that Im a member of all 3 lists. > But this allows for a cross-discussions between the three developer > groups on this thread. > (I will also post this same message to the 3 user lists tomorrow.) > > 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. > Of course the Cocoon community is welcome and we should discuss how > this can happen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
