Hi Dims, Is this basically the same question Roy asked on incubator@ - whether the WS project should become one project or split into multiple TLPs?
I'm very much in favor of keeping the WS-* projects together and to doing things to move the projects closer to each other. The question of course is how to do it. While I'm in favor of your suggestion of providing a common r/w perms mechanism, I'm not sure its enough. How about doing some active community building exercises? Let's start with a regularly scheduled IRC chat for all the WS committers. The first topic I suggest is an information exchange to let everyone know what the current cross-project dependencies are and maybe what they could be. Then we could talk about plans across projects and try to get interest from across the projects. Sanjiva. On Fri, 2005-06-03 at 16:04 -0400, 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? > > Thanks, > dims
