Geir Magnusson Jr. wrote:
> I hate to interrupt all the good fun over standards, bike sheds, and general
> good community feelings, but I would like to solicit community opinion on
> something unrelated to DVSL or Jon Stevens (both of which I like, btw...)
You're taking away all the fun :)
>
> Recently, it was proposed that ObjectBridge be brought to Jakarta as a
> subproject.
>
> Costin suggested, and I supported, that a subproject of wider scope be
> created to allow the collection of similar technologies into one larger
> subcommunity (that isn't an exact quote, but I think he'll agree in general
> with that.)
>
> The idea would be to bring in ObjectBridge, but create a Commons-like
> environment in which other projects can be brought. Call it DB-Commons as
> a working name.
Ok.
>
> There are some good reasons, including community alignment, inter-project
> synergy (there, I used the word in an Apache-related post), and ease of
> discovery for new users and developers.
:)
>
> Off the top of my head, in Jakarta we have lots of db related tools already
> (Torque, commons-dbcp, and I am sure others...), and having a db-focused
> subproject in which they can be brought to with a lower barrier than
> 'fullsubproject' might be very benficial.
>
> We already have the successful Commons model to use as a starting point.
>
> Anyone have any comments?
>
Can we have Avalon related components in DB commons? Avalon has the
DataSourceComponent interface and associated implementations. There are
some things we have in Excalibur that we *can't* donate to Commons
because the charter does not allow it (I think its something about the
project can't rely on non-commons projects or something).
It only makes sense to have a focused commons-like area. This would
make the third one. Excalibur is (at least now) a commons-like area
focused on Avalon, Jakarta Commons is multipurposed, and this would
be fine.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
