+1
Thanks,
Gianny
On 07/12/2007, at 1:43 AM, Rick McGuire wrote:
The discussion thread has been out there long enough for comment,
and those who have responded appear positive about the prospect. I
think it's time to put this to a vote. The full proposal from Matt
Hogstrom is attached at the end, but the basic proposal we're
voting on implementing in Geronimo is:
1) Accept the Yoko core modules (corba spec, corba core
implemenation, rmi spec and rmi implementation) as a subproject of
Geronimo.
2) The Yoko subproject will be maintained as a stand-alone
component so it can be used by Harmony as well as Geronimo.
3) Lars Kuhn, Alexey Petrenko, and Darren Middleman be invited to
join the Geronimo project as commiters so that they may continue
contributing to the Yoko ORB.
This is a single vote on the entire proposal (accepting the code
and inviting the commiters).
[ ] +1 Implement the Yoko ORB subproject in Geronimo as proposed
above.
[ ] 0 No opinion
[ ] -1 Do not implement the Yoko subproject as proposed.
Only PMC member's votes are binding, but we invite anybody in the
community to speak up and vote on this.
Since the vote runs over the weekend, I'll conclude it at 10::00
Eastern time on Monday.
Rick
Matt's full proposal presented to the Yoko project:
The members of project yoko have been considering the future of
Yoko as a project. There have been several milestones delivered
and the project is used by other ASF projects. The project is not
as active as other ASF projects and it makes sense to move the code
from Yoko to other projects. The Yoko team has the following
proposal for your consideration.
Proposed Code Donation from Project Yoko to Apache CXF and Apache
Geronimo
The Yoko community has been successful in delivering several
milestones of the ORB implementation while in the Apache
Incubator. These milestones are used by other Apache projects
(namely Geronimo and Harmony) to support their releases. The
WebServices bindings are dependent on CXF. The Yoko community has
decided that the Yoko project does not have quite the momentum to
carry itself as an independent project but has sufficient value for
other projects for them to consider receiving the code and
committers for that code-base as sub-projects. Since the code
under consideration is used by Apache Geronimo, Apache CXF and
Apache Harmony the movement of the code should continue to allow
for independent releases so the code can be easily shared with
other dependent projects.
The proposed division is:
yoko-spec-corba - this is the org.omg interface classes.
rmi-spec - this is the javax.rmi spec implementation
core - This is the actual ORB implementation.
rmi-impl - This is the implementation of the RMIIIOP support.
These modules are also used by Harmony.
In addition to the code we propose that the following committers in
Apache Yoko be accepted as committers in Apache Geronimo given
their demonstration of delivering code, creating releases and
functioning as a community. Those noted with asterisks are already
Geronimo committers.
Continued involvement with the core:
Rick McGuire *
David Jencks *
Alan Cabrera *
Lars Kuhne
Alexey Petrenko
Darren Middleman
The remainder of the modules in Yoko are part of the webservices
support and are independent of the underlying ORB implementation.
api -- interface classes used for the web services support.
bindings -- code to implement the CORBA-Web services bindings.
tools -- tools for generation WSDL and IDL for the bindings
maven-plugin -- some maven plugins that can use the tools for
generating binding-related build artifacts. None of the maven-
plugin code is used by the ORB.
There is also a distribution directory with some sample
applications. One set of samples demonstrates using the core ORB,
the other set is for WebServices. We recommend that the
distribution directory should move to Apache CXF as the webservices
examples use the orb samples to bind them as web services. Since
Apache Geronimo's only use of CORBA is for exporting EJBs, these
samples are not particularly valuable for Geronimo.
The Yoko community did not have any committers that expressed an
interest in continuing work on these bindings. As such, only the
code would be moving to apache CXF.