Sam Ruby wrote:
>
> I have found the discussion on WASP to be a productive one.
Me too.
> Now it is time
> to move from general discussion to development activities.
Agreed.
> 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.
Absolutely.
I like the concepts Sam outlines:
1.a) SOAP is a protocol and we don't need many implementations of it
1.b) the community will decide how existing codebases should converge
toward goal 1.a)
1.c) the more you partecipate in the community, the more you'll have to
influence these decisions
> 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
> "sub-sub-projects".
yes, it seems like there would be not enough diversity to bootstrap a
new PMC and too many things to fit into a single codebase.
This said, it must be well understood that while functional overlap can
exist between sub-projects, it cannot be tollerated between
sub-sub-projects, unless one is the internal fork for of the other.
> If it is felt that the name "axis" is too prejudicial, then by all means
> lets rename the project.
Ok, but consider that this is not something that can be done everytime
something new gets merged into the sub-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.
Agreed.
> 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.
Absolutely. It should aim to create software infrastructures for web
services, also possibly cooperate with other xml-enabling frameworks
such as Cocoon.
> 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.
Agreed.
> 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...
+1
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
