Ted Husted wrote:
>
> Sam Ruby wrote:
> > The more important question is whether or not there are people willing and
> > able to do the work.
>
> So, all emoticons aside, are we seriously discussing installing a copy
> of SourceForge that our Committers could use to launch and maintain
> their own subprojects? Like an incubator?
What do we get out of this? Why not use SourceForge?
Anyway - I see that sentiment appears to be bimodal:
1) I got involved here because of my interest in seeing some of the
useful bits of code present in Jakarta projects, code that generally is
supportive of the project goals but not the goal itself, be brought out
and maintained in a sharable, 'productized' manner. My canonical
example is a DBConnectionPool, currently present in Struts, Turbine and
apparently Avalon, among others. I feel this is the type of
utility/component that is valuable not only within Jakarta projects, but
for anyone building Java servlet-based software, and therefore a clearly
chartered project delivering pooling/db pooling would be in-line with
the Jakarta mission. Despite the 'alternative charter' of Avalon, the
mythical 'Jakarta-Tools' project, I don't currently see a place in
Jakarta-land where this goal is clear, public, and active. And if what
I want to do is a dumb idea, I would really like it if someone told me
so :)
2) The other mode is more oriented toward a 'library' or as I prefer,
'software depot', an open-access repository for miscellaneous bits of
code that can be shared across Jakarta projects by all Jakarta
committers. This too is tremendously valuable, although a bit of a
departure from what I percieve as the usual Jakarta project model. But I
think that's ok :) ( As an aside, Taglibs seems to be more of a hybrid,
with a clear charter that allows the open library model. )
I am willing to participate in both, but as my original goal-vision-itch
is still important to me, it might be a good idea if we decide clearly
and finally where this 'LIBRARY' project is headed. If the group decides
that it is not towards or inclusive of path #1, that is fine : I am
happy to stay, but I will also know to continue with my efforts
somewhere else towards the projectization/productization of some of the
common bits I see in Jakarta. I don't want to continue swimming
upstream.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
