On Wed, 2001-11-14 at 05:38, Sam Ruby wrote: > General thoughts: > > This is just a poll at this point. A perfectly reasonable response > might be for the PMC to request that consensus be reached first on the > Axis dev mailing list before proceeding to a vote. Three of the five > PMC members actively follow that list anyway...
+1 I am *very* against the idea of WASP as a separate project. If the Axis and Wasp communities can not agree, then I think we're done. We already have 2 SOAP implementations with 2 different API's. We don't need 3. At least X1, X2, and Crimson are JAXP interchangable. Right now, the SOAP situation is a mess. > I'm not clear on what the difference between internal fork and external > fork. Two committers (and an undisclosed at this point, but presumably > small number of other developers) decided to go their own way for a > period of time, and now want to share their results with the community. > > Status of other forks: > > Currently Xerces 1 and 2 are in separate cvs trees and have separate > entries on xml.apache.org's web site; as does Crimson. Committers to > any one code base have karma to all. The important thing here is that the plan is for Xerces 1 and Crimson to converge at Xerces2. This hasn't happened yet, but is in process. At that point I expect both Xerces1 and Crimson to go to the old project's home (wherever that is). > Xalan1 and Xalan2 were in the same cvs tree, but had separate entries on > xml.apache.org's web site for a time. Now Xalan1 is no more. > Currently Cocoon1 and 2 are in separate cvs trees (originally they were > in one), and have separate entries on xml.apache.org's web site. > Committers to the either code base have karma to both. The cocoon guys have been saying that C2 will supersede C1. > Currently Soap and Axis are in separate cvs trees and have separate > entries on xml.apache.org's web site. In creating Axis, I did take the > opportunity to cull the list of inactive committers - with the statement > that any could become active simply by a simple request. After Axis goes 1.0, my personal expectation is that SOAP is starting to go to the old projects home. > My personal priorities (in no particular order): > > Reuniting the community. > Not disrupting the progress of Axis to release while this donation is in > process. > Stealing heavily from both code bases to create the best product in the > marketplace I think that the WASP code and community can contribute in a number of areas. The way that we got into the Crimson / Xerces mess was that we said, we'll accept both projects and figure out how to merge them later. It took a long time for that to start to happen -- not that it's fully happened just yet. The way that Batik happend, as well as the way that the XSLTC -> Xalan donation happened are better models in my mind. Ted > Note: > > I had the opportunity to meet Anne Thomas Manes for the first time last > week at the O'Reilly P2P and WebServices conference, as did Dirk. We > discussed the priorities I listed above, and I recommended that this > proceed by her posting to the [EMAIL PROTECTED] mailing list to > gather input. I knew her name as she often posted to both the soap and > axis mailing lists, generally by answering people's questions about SOAP > and related technologies. > > - Sam Ruby > > > --------------------------------------------------------------------- > In case of troubles, e-mail: [EMAIL PROTECTED] > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
