I would think that each of the sub projects would have its own set of committers. I don't think I should have the rights to muck with the WSIF code just because I know what I am doing in Axis.
Given that we expect the number of projects involving web services to only increase, I think it would make much more sense that each project has its own set of committers, mailing list, CVS tree, etc, etc. I see webservice.apache.org as more of an organizational grouping than a 'we are a bunch of people all working on every one of these projects'. I freely admit that there may be Apache organizational principals that govern this that I am not aware of.... -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Sam Ruby [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 9:24 AM To: [EMAIL PROTECTED] Subject: Re: Web Services top-level project (was Re: [AXIS/WSIF] proposed new WSIF home page URL) Davanum Srinivas wrote: > +1 for creating a new project called webservices.apache.org and migrating > Apache Axis, Apache SOAP, WSIF, WSIL etc. under that as components. > That means there would be one set of committers, one PMC, one set > of rules/guidelines etc.. Let me expand upon that last statement. Jakarta is an umbrella PMC with lots of pieces. One such piece was Avalon, which itself had a lot of pieces. Both resulted in serious community and oversight issues. I can provide more detailed background if necessary, but sufficie it to say that there is a strong desire that any new PMC that is created addresses some of these issues. The first thing we need to consider is whether there are WSIF developers and Axis developers as separate concepts. Example, does a WSIF developer need to submit a patch to WSDL2Java in order to address one of "their" needs, or is WSDL2Java community property? - Sam Ruby
