Dave Johnson wrote:
On 8/16/06, Elias Torres <[EMAIL PROTECTED]> wrote:
I think we have heard enough opinions from many in the community. Should
we try to vote on the issue and decide? The options are many all
hovering on things from the set keeping hibernate, staying at apache,
Sun leaving roller, IBM leaving roller, making it pluggable, replace the
ORM, rewrite it in Ruby, Lisp, ML and any combination of any of these.
Personally, I don't see a crisis or a need for a vote.
Craig would like to develop an alternative backend for Roller. I don't
think we need to vote to permit him to do that in the sandbox or in a
separate banch.
Those that wish to help Craig suceed should help him by reviewing his
design, suggesting improvements and assisting with implementation.
When/if Craig and friends come up with an implementation or two we can
evaluate it and then decide what to do -- with a vote if necessary.
That sounds good to me, but I don't think that means we should stop
discussing the issue. We still need to figure out our general approach
to this problem as a community.
The first thing I would like to know is what the final apache stance is
on our use of Hibernate. Maybe it's just me, but it hasn't been totally
clear on what exactly our options are. I know that apache doesn't like
LGPL libraries, but I thought at some point there was some discussion
that we may be able to keep Hibernate in some situations. i.e. if we
were using hibernate through an open api like JPA or if there was some
form of alternative also available. In any case, I would like to get a
firm statement from apache about our options before I make any decisions
about what to do. can someone provide an official stance from apache?
-- Allen
- Dave
