Morga Escribio:
> I'm just concerned that, if other subprojects (e.g.
> ServletApi, Turbine, Avalon, Tomcat, Taglibs, etc.
> etc. etc.) can vote/commit on our path, but we can't
The big misunderstanding here is that i dont want to create yet another
small set of committers with a clear and definite goal, which is ok for
other projects, what i want is precisely this to see commits from all
this subprojects in my way, but with clear and concise rules, empowering
componentization and common interfaces between competing
implementations...
I want to give the facilities to share quality code to all Jakarta
projects..
Please please put up a proposal for a rule the library that no ones can
veto a new package for the simple reason that there is one that does the
same job, :)
i want to give people a place to share their different visions of the
same thing without a project barrier to stop anybody...
> affect theirs, then ours is a ship with a dozen
There are no ours and yours in my way, is only ours as jakarta
communitty, i want to discuss the facilities needed and the first
contributions evry project already represented here can give..translate
the discussion to the respective projects ... and start to work..
> rudders and no sail. We're at the mercy of those
I dont want to drive nobody's ship at all, put only one big, sharp,
clean rudder : Interfaces & Componentization & JavaBeans & Apache
quality people ( actual committers )
> groups arguing about their competing implementations.
Well very simple to solve in my vision, put the competing
implementations near ..... and let people choose..
Saludos ,
Ignacio J. Ortega
