>On 2/2/2001 at 8:33 AM Sam Ruby wrote:
In Jakarta, some of us have worked hard to produce something different
- a community centered around the building of related software. Perhaps
we are deluding ourselves. You tell me.
I would venture that if the goal of each Jakarta product were to be the
defacto (or actual) reference implementation for it's breed, then the
relations will follow. Besides meritocracy, another important Apache
principle is "correct first". If we pursue that, the rest will follow.
A good role for the Jakarta PMC is to stay in touch with what the
various product teams are planning, and try to suggest a link to
another product when an idea is gestating (repeat, gestating). Another
good role is to point-out to a team where there is signicant component
that could be turned into a product in its own right.
On the table now is a Jakarta connection pool product. Another
candidate might be the Jetspeed portlet.
But to be useful to the other products, these components must also be
exposed at the product level, and have their own set of committers,
release plans, and the rest of it. The Ant model is a good one: the
developers of one Jakarta product become the users of another.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
