Davanum Srinivas wrote:
Hi all,
Does anyone think that moving to a jakarta-commons/cocoon model where
there is a single ACL for all of web services will help? We can still
have separate release cycles for all projects., and each project can
have a list of active participants.
For example, i want the Axis/C++ folks (and the folks on
Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
get everyone more involved (it's not too late yet!) now, it will ease
the pains of "porting" existing code to Axis2...and so on.
Basically, we will have 1 list on CVS/SVN with all web services
committers and all of them will have rw privileges on all CVS/SVN
modules. Existing committers who want to contribute to another sister
WS project can sign up in the list of active folks for that project
and help out with that project.
Yes, we are all scared of folks changing stuff willy-nilly. But it
just implies, we need to monitor changes more closely and work a bit
more on mentoring others on our code.
What do you all think?
i think it is very good idea (especially to be able to fix bugs
introduced when common code is changed) as long as we have well
documented how to run some regression testing (like unit tests)
thanks,
alek
--
The best way to predict the future is to invent it - Alan Kay
