Anne Thomas Manes wrote: > > One way to make things more apparent would be to pull the SOAP project under > the Axis project (or vice versa). It also might help to provide some > indication on the Web site that SOAP and Axis are in some way related to > each other. Note that on the http://xml.apache.org main page, Axis is listed > in the left column of projects, but it's not listed in the main text (which > implies that it isn't an XML sub-project?). (XML Security doesn't appear to > be a sub-project either). What this means is that unless someone knows to > look for Axis, new-comers will automatically go to the SOAP page and never > find the Axis project. There's no mention of Axis either in the SOAP project > description on the main page or on the SOAP project page. > > It would be useful to have some verbage on the project pages that ties the > SOAP and Axis project together -- perhaps a single project page that lists > the ongoing SOAP projects. This approach would also easily accommodate > another SOAP project (e.g., WASP).
Or come up with a new name for us to bring together these projects (i.e., a fresh slate). Such an umbrella under a PMC is not without precident, see Jakarta's Avalon and Turbine projects. We could also discuss factoring out portions that are potentially common to mulitple code bases (e.g., JAX RPC, Wsdl2Java, etc.). The one thing I want to insist is to have a single -dev list in order to facilitate the building of a community. Multiple -user lists can are fine. - Sam Ruby --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
