Hi Terry,
your question is natural, and my message did not explain the motivations
behind the ObjectWeb decision.
I see three main motivations for our offer to support the Enhydra.org
infrastructure.
- The first reason is "emotional".
ObjectWeb has had a cooperation with Lutris around Enhydra (and
then LEAS) since 1999. We feel that it would be a shame to see the
Enhydra.org community be dislocated, and thus our offer to take over the
infrastructure.
- The second reason is complementarity between our two communities.
Enhydra hosts a number of projects which are very complementary
to the ObjectWeb projects. For example, the recent Enhydra projects in
the domain of embedded software are very much in one of the directions
that ObjectWeb is considering. In terms of application server, ObjectWeb
does not have the presentation layer that Enhydra 3 realizes. ObjectWeb
is a user of Zeus. It could make sense to see what DODS and the
ObjectWeb JORM project could share in terms of persistence.
These are only examples.
It thus makes sense that ObjectWeb sponsors Enhydra projects since
our two offers are complementary.
I do believe that some ObjectWeb developers will become more involved,
as developers, in Enhydra projects.
- The third reason is the disappearance of LEAS.
The recent stop of LEAS (Lutris' commercial J2EE platform) is
an opportunity to build an open source J2EE platform based on
Enhydra 3 and the JOnAS EJB server (remember that JOnAS used to be
embedded in LEAS).
This could offer previous LEAS users a valuable alternative to LEAS.
We are aware of the recent effort to move projects to
SourceForge, and are sorry that we could not react faster to prevent
this
move. Regarding the move to SourceForge, and after discussion with Paul
Morgan
and some of the project leaders, the position is that it makes sense to
move
back to Enhydra.org in order to maintain the coherence of the community
around Enhydra. Moreover, the current position of SourceForge is
somewhat
unstable.
We're hoping that projects which had already moved to SourceForge
would be ready to move back to Enhydra.org.
I hope that this message will answer your concerns.
Do not hesitate to get back to me for any question you may have.
Regards,
alex
> Terry Steichen wrote:
>
> Hi Alexandre,
>
> I have been participating in the Enhydra community for over 3 years,
so I've
> seen a lot of changes. This one puzzles me a bit. You say you are
taking
> over sponsorship of Enhydra.org, presumably with Lutris' blessing.
You
> don't want to impose anything on us - that's good. But, ahem.., I'm
not
> clear what you do want to do. What is the purpose of this transfer
and more
> pointedly, what does ObjectWeb get out of it?
>
> Do you have developers that use and understand Enhydra and related
> architectures, so they could contribute meaningfully to discussion
groups?
>
> Moreover, several long-standing members of the Enhydra community have
(I
> think) already gone to a lot of effort to get the stuff hosted on
> SourceForge (with Lutris' blessing too, I think). Does this duplicate
that
> effort or what?
>
> I'm not trying to give you a hard time, I'm just not sure what's going
on.
>
> Regards,
>
> Terry
>
> ----- Original Message -----
> From: "LEFEBVRE ALEXANDRE FTRD/DTL/GRE"
> <alexandre.lefebvre@rd.francetelecom.com>
> To: <enhydra@enhydra.org>; <enhydra-announce@enhydra.org>;
> <xmlc@enhydra.org>; <barracuda@enhydra.org>; <dods@enhydra.org>;
> <kelp@enhydra.org>; <me@enhydra.org>; <mapper@enhydra.org>;
> <zeus@enhydra.org>; <webdocwf-enhydra@lists.sourceforge.net>
> Sent: Thursday, April 25, 2002 12:21 PM
> Subject: Enhydra: ObjectWeb position about the sponsorship of
Enhydra.org
>
> > Dear Enhydra community,
> >
> > Following the ObjectWeb proposal to take over sponsorship of
> > Enhydra.org we, at ObjectWeb, would like to give you some
explanations
> > about the intentions behind our offer.
> >
> > ObjectWeb proposes to provide hosting to the Enhydra community in
> > order to allow the seamless continuation of Enhydra.org as an Open
> > Source community. We do not want to impose anything on you guys. We
> > hope that the Enhydra community will become as open as possible, and
> > we think that the fact that we are another open Open Source
community
> > provide some guarantee on that.
> >
> > ObjectWeb does not intend to take over the management of projects,
but
> > just to maintain the infrastructure. We hope that most project
leaders
> > will accept to continue their very valuable work on Enhydra.org. For
> > us, each project leader is fully responsible of his/her project
> > (project web pages, mailing lists, versioning policy, deciding who
has
> > write rights on cvs, etc.). For those projects for which there is no
> > project leader any more, we encourage volonteers to take the lead.
> >
> > We have asked Christophe Ney, one of the Enhydra architect and
> > formerly in charge of the coordination between Lutris and ObjectWeb,
> > to help us coordinating the restart of Enhydra projects.
> >
> > It may be useful to formalize somewhat the way the Enhydra community
> > operates, and to have global coordination structure, but again it is
> > up to the Enhydra community to decide.
> >
> > Please do not hesitate to contact us (mailto:contact@objectweb.org)
to
> > discuss or clarify anything.
> >
> > More information about ObjectWeb and the way it operates can be
found
> > at: http://www.objectweb.org/consortium/index.jsp
> >
> > --
> > Alexandre Lefebvre, R&D Engineer
> > France Telecom R&D - DTL/ASR
> > 28 chemin du Vieux Chene - B.P. 98
> > 38243 Meylan CEDEX - France
> > phone: +33 4 76 76 45 63 - fax: +33 4 76 76 45 57
> > email: alexandre.lefebvre@rd.francetelecom.com
> > email: alefebvr@acm.org
> > _______________________________________________
> > Enhydra mailing list
> > Enhydra@enhydra.org
> > http://www.enhydra.org/mailman/listinfo.cgi/enhydra
> >
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@enhydra.org
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
|