Ralph Goers wrote:
So the real question is, are we here to just implement the RI for the
spec or can we go beyond it and if so, how?
From a historical perspective, the general thought of the pmc has been
that pluto should be scoped at the portlet container level while other
portals projects should focus on the portal services. Whether or not
the container needs to only focus on the reference implementation of go
beyond is what's up for discussion.
As for my self, I believe:
1) Pluto should focus on the following 3 goals (in order and as stated
in it's mission):
- reference implementation
- easy portlet testing/development
- embeddable container for portal/webapp developers
2) Jetspeed should be the focus of enterprise portal development
3) Other subprojects of the protals community should provide additional
functionality/features.
In other words, yes, we can *and should* go beyond the specification.
That said, we need to determine the appropriate place.
The question at hand (auto-deployment in pluto) is borderline
functionality to me. It specifically hits the second goal of pluto
(easy portlet testing/development), but could also be seen as enterprise
functionality.
David
