xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby" <ru...@us.ibm.com>
Subject Merging soap, axis, wasp, and wsdl communities.
Date Mon, 26 Nov 2001 16:04:13 GMT
I have found the discussion on WASP to be a productive one.  Now it is time
to move from general discussion to development activities.  Here's a recap
of a few conclusions:

Goal 1: achieve a single active SOAP implementation.

   There is no plans to maintain in perpetuity a separate identity for
   multiple code bases.  From a technical perspective, what will emerge
   will be based primarily on what directions active committers choose to
   take these code bases.  Needless to say, those that participate more
   will have a correspondingly larger say.

Goal 2: grow a larger "web services" community building upon this common
code base

   Like avalon, turbine, tomcat, and ant; we can and should organize
   separate code bases which build upon this common base into

   If it is felt that the name "axis" is too prejudicial, then by all means
   lets rename the project.  But when all is said and done, the name we
   come up with should (1) be the name of the common soap code base that we
   all participate in, and (2) should be the name of the common -dev
   mailing list that defines the community.

   One thing I want to specifically call out here: just as xml.apache.org
   subprojects are not artificially limited in scope to only support Apache
   XML parsers or Apache XSLT processors, sub-sub-projects of whatever
   common name we come up with will not be limited to only supporting this
   soap stack.

Summary: what matters most is the community.  At times we will certainly
disagree over technical issues, but over time the code base with the
largest active development community will attract both the largest
mindshare and marketshare.

At this point, I'd like to suggest that discussions continue on axis-dev.
These discussions can include coming up with a new name, contributions of
fragments or complete soap implementations, and contributions of code bases
which build upon a soap stack...

- Sam Ruby

In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org

View raw message