Sorry for stepping this late, but my laptop broke down on the last day of the ApacheCon and as I packed it into my luggage, the luggage had some extra security treatment on the flight back, so I received the laptop last night, then had to repair the hard drive and now everything seems to work again...(ok, this is totally ot, but I thought starting with a little story makes everything more interesting). Back to the topic:
> > Maybe part of the problem with this thread is that several issues > are at play here. > - a proposal for a new light-weight portal > - a proposal for a separate portals-commons > - a proposal for maybe even a "Portals Suite" whatever that might be > - Cocoon Portal not being part of Apache Portals > Yes, agreed - there are several issues here discussed at once. I'll comment on some of them :) Cocoon Portal is currently part of Cocoon (obviously :) ). Now, it really lacks of committers and visibility. Noone knows that Cocoon has a nice portal solution. Ralph and myself are nearly the only developers on the portal. Now what do you guys think of moving the Cocoon portal to the portals project to create more visibility and hopefully to make collaboration between the various portals projects more efficient? Now, although I wrote more than 90% of the Cocoon portal code (and this fact shows the community problem of the portal), I don't care what happens with it over the long term. I think, in the end we should try to have only one portal solution at Apache - being this Jetspeed 2, Cocoon or something different is imho not that important. Now, I don't know J2 that much, but from what I understand so far, it seems similar to the Cocoon solution in most areas, so I might be possible to add some things from the Cocoon portal to J2 and then ditch the Cocoon code (I guess this now scares Ralph :) ) - But I see this more as a long term goal which we can start addressing when I know more about J2 - I'm, planning to look into J2 in the next weeks and then see, if it's possible to add some ideas from Cocoon there. I'll start a thread at the J2 list by then. > Anyways, I did *not* say the solution *must* be tailored around J2. I only > asked > for looking into that as a possible solution. > Note: this specifically concerns the issue of a new light-weight portal which > I think > might less of interest to Cocoon (please correct me if I'm wrong here). Yup - I have not thought about this light-weight portal stuff yet, but currently I see no need for this for myself; but I'm open to any further discussions of course. > But, our Jetspeed components could be made (or maybe already are) reusable > for Cocoon or any > other portal like Gridsphere for instance. Yepp :) > I also have no objection to move such components to a separate (sub) project > of Portals > if they are really (going to be) reused and others will help out maintaining > them. Ok. > <SNIP/> > > That is one solution, another one could be a separate J2 build, J2-light or > whatever which is > simply a lighter packaged version of J2 with an appropriate simpler > configuration and assembly. > And yes, maybe a new project could be more appropriate in the end, but I'm > not convinced of that yet :-) > As long as the components are really separatly usable from J2, I don't care that much were they are maintained - as long as I have access to it :) And we can then later on move them to a commons project if appropriate. > Anyways, for Cocoon, I recognize that separate usage of our J2 components or > further generalized > ones in a new portals-commons project might be very useful. > > May I suggest you or Carsten create a new discussion thread here, or on the > Jetspeed dev list, in which > we discusss what J2 features could be of use to Cocoon or we can create > together for both our communities? > I honestly like to help out with that one. Great, thanks, Ate - yes, I think the best place would be the J2 list for now; I'll start a thread in the new year. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
