You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Mark Orciuch <ma...@ngsltd.com> on 2003/07/22 18:38:24 UTC
[PROPOSAL] Contributed portlets page
Just wanted to make sure that everyone is OK with this initiative. I would
like to add a new page to Jetspeed documentation site containing links to
contributed portlets. There are several portlets out there, including the
recent To Do Portlet from Raffele Ragni, which could be put on that page.
If no objections, I'll put it together sometime tomorrow.
Best regards,
Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: [PROPOSAL] Contributed portlets page
Posted by Sami Leino <sa...@netorek.fi>.
> 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: sami@netorek.fi
Phone: +358 44 0140499
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: [PROPOSAL] Contributed portlets page
Posted by Tim Reilly <ti...@consultant.com>.
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.
Portlet application "war's" could be separate from the portal server
repository.
In that situation the portlet contributor could mark their portlet's as
version 2.xx compatible, etc.
For example, if 5 people wanted to contribute different versions of a
StockTicker portlet they could perhaps submit it to the "catalog" with:
Title: title
Description: description
Provider: name
Compatible: J2.xx, J2.yx
Download URL:
License:
etc...
Of course, having them in CVS would help facilitate better collaboration,
community bug tracking, fixing, and all the great advantages of
open-source`dom. So perhaps no download url, nor license, but rather a
"unsupported" branch of the CVS as mentioned.
Am I jumping too far into the future... probably.
But IMHO Mark's suggestion moves towards that path;
?
-----Original Message-----
From: Mark Orciuch [mailto:mark_orciuch@ngsltd.com]
Sent: Tuesday, July 22, 2003 2:08 PM
To: Jetspeed Developers List
Subject: RE: [PROPOSAL] Contributed portlets page
> When you say "contributed portlets", it makes me think that they are
> contributed to the Jetspeed CVS.
> Shouldn't the portlet documentation go in the Portlet Catalog?
They are "contributed" but not "committed". Another example would be
WebSurfPortlet.
>
> Or are these portlets that are not in the CVS, perhaps for licensing
> reasons...
>
Licensing may be one reason. Another would be complexity and future
maintenance issues. Not all contributors are committers and not all
committers have the time for integration. However all contributions are
valuable and we should provide a centralized place to access them. Since we
don't have a true portlet repository, I though we'd have a page pointing to
the publishers' sites.
I think that Jetspeed-2 portlet applications contributed by others could
also be placed on that page.
Best regards,
Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[VOTE] To Do List Portlet
Posted by Mark Orciuch <ma...@ngsltd.com>.
Please vote on whether to commit Raffaele Ragni's To Do List Portlet to CVS
or include a link to it in Jetspeed's documentation
(http://www.cone.it/cone/portal/media-type/html/user/anon/page/prog.psml/js_
pane/Jetspeed). Once the votes are in, I'll create an appropriate Bugzilla
enhancement task for this.
Best regards,
Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: [PROPOSAL] Contributed portlets page
Posted by Mark Orciuch <ma...@ngsltd.com>.
> When you say "contributed portlets", it makes me think that they are
> contributed to the Jetspeed CVS.
> Shouldn't the portlet documentation go in the Portlet Catalog?
They are "contributed" but not "committed". Another example would be
WebSurfPortlet.
>
> Or are these portlets that are not in the CVS, perhaps for licensing
> reasons...
>
Licensing may be one reason. Another would be complexity and future
maintenance issues. Not all contributors are committers and not all
committers have the time for integration. However all contributions are
valuable and we should provide a centralized place to access them. Since we
don't have a true portlet repository, I though we'd have a page pointing to
the publishers' sites.
I think that Jetspeed-2 portlet applications contributed by others could
also be placed on that page.
Best regards,
Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [PROPOSAL] Contributed portlets page
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Tuesday, July 22, 2003, at 09:38 AM, Mark Orciuch wrote:
> Just wanted to make sure that everyone is OK with this initiative. I
> would
> like to add a new page to Jetspeed documentation site containing links
> to
> contributed portlets. There are several portlets out there, including
> the
> recent To Do Portlet from Raffele Ragni, which could be put on that
> page.
>
> If no objections, I'll put it together sometime tomorrow.
>
When you say "contributed portlets", it makes me think that they are
contributed to the Jetspeed CVS.
Shouldn't the portlet documentation go in the Portlet Catalog?
Or are these portlets that are not in the CVS, perhaps for licensing
reasons...
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org