> I like the idea, however (or in addition) as time pasts (with Jetspeed > 2) I think the Jetspeed CVS will be able to be more portlet container > oriented and select a core set of portlets for the main distribution. I > imagine it would concentrate on the services to provide to portlets, and > the administration of portlets, layouts, users, etc.
I agree. One of the complaints I have heard about Jetspeed is the lack of useful portlets. Many potential users have thus moved towards other portal solutions offering dozens of useful built-in portlet applications, despite of the fact that the overall feature set of their chosen portal engine core is not even close to the rich feature set of Jetspeed core. If there was a separate portlet repository allowing users to easily upload/download portlets, there would be more portlets to choose from, and users would feel that their productivity increases as they do not need to develop everything themselves. Such a portlet repository would make Jetspeed even more successful project than it is today. It would also make it easier (and faster) to develop a clean portal engine, as the committers would no more need to spend their time on portlets (I guess you guys receive far too many questions that have nothing to do with the Jetspeed core). As I see it, the Jetspeed core should be kept as clean and simple as possible. From the developer's point of view, the Jetspeed 1 architecture can sometimes be a bit troublesome. When you need to change something to suit your needs, you have to find out where that functionality comes from - from Jetspeed, from Turbine or possibly from some other component. It can sometimes be a tedious task to find the correct spot, if you know what I mean (there are parts in Jetspeed 1 that contain too many layers, IMHO). Of course creating a new portlet repository (or whatever you want to call it) introduces problems. Some of the portlets would be very crappy, and some of the portlets would overlap each other. Voting functionality would be needed in order to make the good portlets rise above the not-so-good ones. Users would be provided with an option to write reviews of portlets. If I had a vote, I would give my +1 to a clean separation of Jetspeed core and portlets. Regards, Sami -- Sami Leino Software Developer, Netorek Oy, Turku, Finland Email: [EMAIL PROTECTED] Phone: +358 44 0140499 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
