You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Glenn R. Golden" <gg...@umich.edu> on 2003/10/16 14:29:50 UTC
How are Pluto decisions to be made?
A recent patch posted to the developers list raises a question for me.
I don't mean to actually comment on the merits of this particular
patch. That's because I'm not sure I have all the data or understand
Pluto well enough at this point to do so.
The question is first, who are the committers of Pluto? These are the
people who need to make sure that Pluto stays on a development path
that leads it to be the reference implementation of portlet that can be
used by many different portal engines. I think that the initial
committers are the Jetspeed committers, with some additions. I'm not
sure of the exact list.
I think that something of this nature, changing the wrapping from many
to one servlet, should be something that is carefully considered by all
the folks who know how it will impact Pluto. In fact, it seems like
this should be something put to vote by the committers.
Further, since Pluto is rather young, and our experience with it is
rather young, I highly value the guidance of the IBM folks who wrote it
and who continue to be active in it's life. I'm glad to see that
Stefan has already made comment on this.
Again, I don't know if this is a good idea or not, and don't mean to
vote against it in any way, nor am I discouraging ideas and
contributions from anyone! I just want to make sure that we tread
carefully here in the early stages of Pluto's life and make sure we
produce something that will be as "reference" and well used as Tomcat
is for Servlets.
Thanks,
- Glenn
Glenn R. Golden CHEF Architect
Jetspeed and (I think) Pluto Committer
Sr. System Research Programmer
School of Information + Media Union @ University of Michigan
ggolden@umich.edu
On Wednesday, October 15, 2003, at 08:21 PM, Andy Pruitt wrote:
> This patch routes portlet requests through one servlet per portlet app,
> instead of producing wrapped servlets for each portlet. This is done
> to
> minimize the modifications that must be done to a web.xml prior to
> deployment.
Re: How are Pluto decisions to be made?
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Thursday, October 16, 2003, at 05:29 AM, Glenn R. Golden wrote:
> A recent patch posted to the developers list raises a question for me.
> I don't mean to actually comment on the merits of this particular
> patch. That's because I'm not sure I have all the data or understand
> Pluto well enough at this point to do so.
>
> The question is first, who are the committers of Pluto?
You are for one :-)
All Jetspeed committers are Pluto committers.
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646
+01 707 529 9194