No matter if it goes through the incubator or not, I'd like to make sure
the pluto committers have an opportunity to review the code before it's
committed. I was originally under the impression that the way this
development was going to work was that instead of a code "grant" or
dump, incremental modifications would take place in a branch - all
starting from a clean 1.1 branch.
If this is not the way it will work, we just need to iron out the
protocol - such as if the incubator is the right approach.
In terms of our contact with Torsten, I personally have had any
discussions other than trying to connect with him. I think the ideal
would be for him (and others on his team) to join the pluto-dev list and
allow us to all contribute to the discussions. . .
Just my 2 cents. . .
David
[EMAIL PROTECTED] wrote:
see below
Carsten Ziegeler <[EMAIL PROTECTED]> wrote on 08/24/2006 03:54:44 PM:
> [EMAIL PROTECTED] wrote:
> > IBM has contracted with a group at the University of Jena in
Germany to
> > help create the reference implementation of JSR-286 to be hosted at
> > Apache. David and I have been in contact with this group, which is
headed
> > by Torsten Dettborn, a member of the JSR-286 Expert Group.
Torsten's group
> > has done some work on the JSR-286 RI based on Pluto 1.1 that they
want to
> > contribute to our repository.
> >
> > Unless anyone objects, I would like to create a Pluto 2.0 branch in
SVN to
> > house the JSR-286 Reference Implementation code. The starting point
for
> > this branch will be the Pluto 1.1 code now in our SVN trunk.
> >
> > This is a great chance for the community to contribute to the
JSR-286 RI
> > and get an early look at an implementation of the developing
JSR-286 spec.
> I think every code donation must go through the incubator first, so we
> should definitly first check with them.
>
They are contributing code that builds on our current code base. I do
not see why it has to go through the incubation process. Like Tomcat,
which revs up a version for a new servlet/JSP spec, we are creating a
new version that corresponds to the new portlet spec.
/Craig
> Carsten
> --
> Carsten Ziegeler - Open Source Group, S&N AG
> http://www.s-und-n.de
> http://www.osoco.org/weblogs/rael/
