cvs commit: xml-site/targets news.html
cziegeler01/11/14 03:48:55 Modified:sources/website news.xml targets news.html Log: Added Cocoonrc2 to news Revision ChangesPath 1.10 +7 -0 xml-site/sources/website/news.xml Index: news.xml === RCS file: /home/cvs/xml-site/sources/website/news.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- news.xml 2001/09/18 19:45:01 1.9 +++ news.xml 2001/11/14 11:48:55 1.10 @@ -8,6 +8,13 @@ news about their projects. Be sure to see the information about updating the xml.apache.org website in the link idref=guidelinesguidelines/link. /p + s3 title='Cocoon 2.0 Release Candidate 2 is released' + p +The second release candidate of Cocoon 2 is a big step to the final +version of the complete rewrite of the XML Publishing framework. +The distribution is available from the jump href='/dist/'download pages/jump. + /p + /s3 s3 title='Xerces 2.0.0 (beta) is released' p The beta release for Xerces2 marks the first step in producing the 1.26 +7 -0 xml-site/targets/news.html Index: news.html === RCS file: /home/cvs/xml-site/targets/news.html,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- news.html 2001/11/05 02:25:26 1.25 +++ news.html 2001/11/14 11:48:55 1.26 @@ -46,6 +46,13 @@ news about their projects. Be sure to see the information about updating the xml.apache.org website in the A href=guidelines.htmlguidelines/A. /P + TABLE border=0 cellpadding=0 cellspacing=0 width=484TRTD bgcolor=99 colspan=2 width=484TABLE border=0 cellpadding=0 cellspacing=0 width=484TRTD bgcolor=#039acc height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD bgcolor=#039acc height=1 width=482IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=482/TDTD bgcolor=#0086b2 height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TD/TRTRTD bgcolor=#039acc width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD bgcolor=#0086b2 width=482FONT color=#ff face=arial,helvetica,sanserifIMG border=0 height=2 hspace=0 src=resources/void.gif vspace=0 width=2BCocoon 2.0 Release Candidate 2 is released/B/FONT/TDTD bgcolor=#017299 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TD/TRTRTD bgcolor=#0086b2 height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD bgcolor=#017299 height=1 width=482IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=482/TDTD bgcolor=#017299 height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TD/TR/TABLE/TD/TRTRTD width=10nbsp;/TDTD width=474FONT color=#00 face=arial,helvetica,sanserif size=-1 + P +The second release candidate of Cocoon 2 is a big step to the final +version of the complete rewrite of the XML Publishing framework. +The distribution is available from the A href=/dist/download pages/A. + /P + /FONT/TD/TR/TABLEBR TABLE border=0 cellpadding=0 cellspacing=0 width=484TRTD bgcolor=99 colspan=2 width=484TABLE border=0 cellpadding=0 cellspacing=0 width=484TRTD bgcolor=#039acc height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD bgcolor=#039acc height=1 width=482IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=482/TDTD bgcolor=#0086b2 height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TD/TRTRTD bgcolor=#039acc width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD bgcolor=#0086b2 width=482FONT color=#ff face=arial,helvetica,sanserifIMG border=0 height=2 hspace=0 src=resources/void.gif vspace=0 width=2BXerces 2.0.0 (beta) is released/B/FONT/TDTD bgcolor=#017299 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TD/TRTRTD bgcolor=#0086b2 height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TDTD bgcolor=#017299 height=1 width=482IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=482/TDTD bgcolor=#017299 height=1 width=1IMG border=0 height=1 hspace=0 src=resources/void.gif vspace=0 width=1/TD/TR/TABLE/TD/TRTRTD width=10nbsp;/TDTD width=474FONT color=#00 face=arial,helvetica,sanserif size=-1 P The beta release for Xerces2 marks the first step in producing the - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
cvs commit: xml-site/targets/cocoon2/userdocs/xsp/graphics index-header.jpg_label=User Documentation - XSP.jpg
cziegeler01/11/14 03:57:40
Modified:targets/cocoon2/userdocs index.html
Added: targets/cocoon2/userdocs/graphics XSP-label.jpg
XSP-label_over.jpg
targets/cocoon2/userdocs/xsp index.html
targets/cocoon2/userdocs/xsp/graphics
index-header.jpg_label=User Documentation - XSP.jpg
Log:
Added missing xsp
Revision ChangesPath
1.2 +3 -0 xml-site/targets/cocoon2/userdocs/index.html
Index: index.html
===
RCS file: /home/cvs/xml-site/targets/cocoon2/userdocs/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.html2001/11/08 08:40:01 1.1
+++ index.html2001/11/14 11:57:40 1.2
@@ -63,6 +63,9 @@
td valign=top align=lefta onMouseOver=rolloverOn('Actions')
onMouseOut=rolloverOff('Actions') href=actions/actions.htmlimg
onLoad=rolloverLoad('Actions', 'graphics/Actions-label_over.jpg',
'graphics/Actions-label.jpg'); vspace=0 hspace=0 name=Actions
width=120 height=12 border=0 src=graphics/Actions-label.jpg
alt=Actions/a/td
/tr
tr
+td valign=top align=lefta onMouseOver=rolloverOn('XSP')
onMouseOut=rolloverOff('XSP') href=xsp/index.htmlimg
onLoad=rolloverLoad('XSP', 'graphics/XSP-label_over.jpg',
'graphics/XSP-label.jpg'); vspace=0 hspace=0 name=XSP width=120
height=12 border=0 src=graphics/XSP-label.jpg alt=XSP/a/td
+/tr
+tr
td align=left valign=topimg width=120 vspace=0
src=images/close.gif hspace=0 height=14 border=0br
/td
/tr
1.1 xml-site/targets/cocoon2/userdocs/graphics/XSP-label.jpg
Binary file
1.1
xml-site/targets/cocoon2/userdocs/graphics/XSP-label_over.jpg
Binary file
1.1 xml-site/targets/cocoon2/userdocs/xsp/index.html
Index: index.html
===
html
head
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
titleUser Documentation - XSP/title
script type=text/javascript src=resources/script.js
language=JavaScript/script
/head
body bgcolor=#ff marginheight=4 marginwidth=4 leftmargin=4
topmargin=4 alink=#cc vlink=#0086b2 link=#039acc text=#00
table border=0 cellpadding=0 cellspacing=0 width=100%
tr
td align=left valign=top rowspan=3 height=60 width=135img
border=0 vspace=0 hspace=0 src=images/logo.gif height=60
width=135/tdtd background=images/line.gif colspan=2 align=left
valign=top height=5 width=100%img align=left border=0 vspace=0
hspace=0 src=images/line.gif height=5 width=1/tdtd align=left
valign=top rowspan=3 height=60 width=29img border=0 vspace=0
hspace=0 src=images/right.gif height=60 width=29/td
/tr
tr
td bgcolor=#0086b2 colspan=2 align=right valign=top height=35
width=100%img align=right alt=User Documentation - XSP border=0
vspace=0 hspace=0
src=graphics/index-header.jpg_label=User%20Documentation%20-%20XSP.jpg/td
/tr
tr
td background=images/bottom.gif bgcolor=#0086b2 align=left
valign=top height=20 width=100%img align=left border=0 vspace=0
hspace=0 src=images/bottom.gif height=20 width=3/tdtd
background=images/bottom.gif width=288 valign=top height=20
bgcolor=#0086b2 align=right
table width=288 cellspacing=0 cellpadding=0 border=0
tr
td align=left valign=top height=20 width=96a
onMouseOver=rolloverOn('xml'); onMouseOut=rolloverOff('xml'); target=new
href=http://xml.apache.org/;img onLoad=rolloverLoad('xml',
'images/button-xml-hi.gif', 'images/button-xml-lo.gif'); border=0 vspace=0
hspace=0 name=xml src=images/button-xml-lo.gif height=20 width=96
alt=http://xml.apache.org/;/a/tdtd align=left valign=top height=20
width=96a onMouseOver=rolloverOn('asf'); onMouseOut=rolloverOff('asf');
target=new href=http://www.apache.org/;img onLoad=rolloverLoad('asf',
'images/button-asf-hi.gif', 'images/button-asf-lo.gif'); border=0 vspace=0
hspace=0 name=asf src=images/button-asf-lo.gif height=20 width=96
alt=http://www.apache.org/;/a/tdtd align=left valign=top height=20
width=96a onMouseOver=rolloverOn('w3c'); onMouseOut=rolloverOff('w3c');
target=new href=http://www.w3.org/;img onLoad=rolloverLoad('w3c',
'images/button-w3c-hi.gif', 'images/button-w3c-lo.gif'); border=0 vspace=0
hspace=0 name=w3c src=images/button-w3c-lo.gif height=20 width=96
alt=http://www.w3.org/;/a/td
/tr
/table
/td
/tr
/table
table width=100% cellspacing=0 cellpadding=0 border=0
tr width=100%
td valign=top width=120
table width=120 cellspacing=0 cellpadding=0 border=0
tr
td valign=top align=leftimg width=120 vspace=0
src=images/join.gif hspace=0 height=14 border=0br
/td
/tr
tr
td valign=top align=lefta onMouseOver=rolloverOn('Main')
onMouseOut=rolloverOff('Main') href=../../index.htmlimg
onLoad=rolloverLoad('Main', 'graphics/Main-label_over.jpg',
Re: [POLL] WASP Lite on Apache?
Anne Thomas Manes wrote: Stefano, I'm pleased that you think it's a good thing. To clarify: I was commenting Sam's note on I am looking forward to increased synergy and participation. Increased synergy is what I believe it's a good thing. Whether or not making WASP Lite an apache subproject, *this* is yet to be clarified to my eyes. Just to make sure that everybody understands this distinction: synergy *automatically* generates better communities. Competing projects, normally, do not. So to be crystal clear: synergy - good thing competing subprojects - not so sure We first thought of submitting WASP Lite to Axis, but after consideration determined that this approach would be too disruptive and technically challenging. Who considered that? you or the axis community? WASP Lite is a complete code base, and it would be very difficult to attempt to merge this code base with the Axis code base. Oh, believe me, you'd be surprised on how creative people can become if they are really interested in something. Any merger attempt would significantly delay both projects. We don't want to disrupt the Axis project. We share the same concerns though. Let us understand whether or not the move you propose goes in this direction or not. At the same time we think that the open source community will definitely benefit from WASP Lite. Oh, I don't question that. If Sam says so, I trust his technical judgement. But you didn't state We think that a separate project is the better way to go. I thank you very much for your suggestion and will be taken into very high consideration, but please keep in mind that it's up to the apache communities to decide what to do with donated code. If you decide to donate it in order to communities to benefit, it should not be your concern where the code ends up living, but should be the community's itself. Over time Axis and WASP Lite are likely to share code. Perhaps the projects might eventually converge. This wouldn't be the first time we've had competing projects at Apache (Crimson/Xerces/Xerces2 comes to mind). Exactly. We got burned big time by the politics involved in this very example and we DO NOT want this to happen again since we wouldn't have the energy to do this over again. It is exactly because of this example that I'm seriously concerned about having competing subprojects. Note: we have rules that allow committers of one project to propose an internal fork of the subproject itself, then is the community to decide what to do, but this doesn't separate them. If some of your guys are already committers of Axis and you think your solution is better from a technical perspective, then why don't you propose an internal fork with a new codename and work from there? I think it just goes to show that the community is very interested in the technology. Sorry, I can't follow you. I asked explicitly for overlap analysis in order to understand why you propose a different subproject but I didn't get that answer. Now, if you care about the interest of the community is should not matter where the code ends up living or what name it will end up having. Right? If you are so concerned about the name and the location, it only goes to show me that you are more interested in its location and its visibility than to the community interests. But I sincerely hope you can prove me wrong. So, let's get to the point: I'm personally against having two competing subprojects for no technical reason, no matter what they do. Technical competition should happen inside an existing community, following the Rules for revolutionaries. So, either somebody explains those technical reasons in detail (and convices me of the value of having two competing communities), or my vote remains a +1 on the acceptance of the code donation, but as a -1 on the creation of a new subproject. DISCLAIMER: having resigned from PMC last year, this vote is not pending but just a crystal clear way of expressing my very personal opinion as part of this community. -- 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]
Re: [POLL] WASP Lite on Apache?
Anne, My viewpoint is similar to Stefano's. I like the idea of working with your team and get the code into Apache. But i am not sure if we need one more SOAP implementation. A lot of people are already confused what to use and when. This will split up effort of the developers/users and increase friction/confusion. Here's my +1 on accepting the code donation. But i want the Axis developers and people on the general list to have a say in where it is going to live. Personally, i would want the code to be merged with Axis and not start as a new sub-project. Sam, Did you have any thoughts on where the code should live and how we should go about accepting this offer? Thanks, dims --- Sam Ruby [EMAIL PROTECTED] wrote: Anne Thomas Manes wrote: WASP Lite for Java is a Web services framework developed by Systinet that supports SOAP 1.1, WSDL 1.1, and XML Schema 1999/2000/2001. Details, including binaries and documentation, can be found at http://www.systinet.com/products/wasp_lite/index.html. The product is currently distributed under a free commercial binary license. It has a large user base, many of whom have requested that we make the source available. A number of companies and individuals have expressed interest in contributing to the development of this code. The code has been developed using a modular approach, which should make it relatively easy for others to get comfortable with the code, and which should allow easy sharing of code with the SOAP and Axis projects. We would like to submit this proposal to the members of the Apache XML project for consideration of accepting this donation as a sub-project. Thank you very much for your attention to and consideration for this proposal. We look foward to your questions, comments, or concerns. +1 Two of the developers are already committers on Axis. I am looking forward to increased synergy and participation. - Sam Ruby - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = Davanum Srinivas - http://jguru.com/dims/ __ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] WASP Lite on Apache?
Anne, My viewpoint is similar to Stefano's. I like the idea of working with your team and get the code into Apache. But i am not sure if we need one more SOAP implementation. A lot of people are already confused what to use and when. This will split up effort of the developers/users and increase friction/confusion. Here's my +1 on accepting the code donation. But i want the Axis developers and people on the general list to have a say in where it is going to live. Personally, i would want the code to be merged with Axis and not start as a new sub-project. Sam, Did you have any thoughts on where the code should live and how we should go about accepting this offer? Thanks, dims --- Sam Ruby [EMAIL PROTECTED] wrote: Anne Thomas Manes wrote: WASP Lite for Java is a Web services framework developed by Systinet that supports SOAP 1.1, WSDL 1.1, and XML Schema 1999/2000/2001. Details, including binaries and documentation, can be found at http://www.systinet.com/products/wasp_lite/index.html. The product is currently distributed under a free commercial binary license. It has a large user base, many of whom have requested that we make the source available. A number of companies and individuals have expressed interest in contributing to the development of this code. The code has been developed using a modular approach, which should make it relatively easy for others to get comfortable with the code, and which should allow easy sharing of code with the SOAP and Axis projects. We would like to submit this proposal to the members of the Apache XML project for consideration of accepting this donation as a sub-project. Thank you very much for your attention to and consideration for this proposal. We look foward to your questions, comments, or concerns. +1 Two of the developers are already committers on Axis. I am looking forward to increased synergy and participation. - Sam Ruby - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = Davanum Srinivas - http://jguru.com/dims/ __ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] WASP Lite on Apache?
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... 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. 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. 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. 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 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]
website ++ - monochromatic version
At 4:30 PM +0100 11/5/01, Vincent Hardy wrote: This would make the overall design monochromatic and I think it would look great. following Vincent Hardy's comments, a monochromatic version can be found at (only index.html page): http://www.corrosive.co.uk/xml_apache_org/site-mono/ max -- -- Max Guglielmino Corrosive http://www.corrosive.co.uk - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: website ++ - monochromatic version
[EMAIL PROTECTED] wrote: At 4:30 PM +0100 11/5/01, Vincent Hardy wrote: This would make the overall design monochromatic and I think it would look great. following Vincent Hardy's comments, a monochromatic version can be found at (only index.html page): http://www.corrosive.co.uk/xml_apache_org/site-mono/ max Ooh, nice :) -- Those who would trade liberty for temporary security deserve neither - Benjamin Franklin - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] WASP Lite on Apache?
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]
RE: [POLL] WASP Lite on Apache?
Stefano, Sorry that I have't responded to the discussion -- I've been on a plane all day. Before initiating this poll, I discussed it with Sam. I first suggested submitting WASP to Axis. Sam suggested that we set it up as a separate project. But we're happy to abide by the community's decision. As Sam said, Axis supports JAX/RPC. WASP supports JAXM. WASP also supports pluggable transports, pluggable XML protocols, pluggable header processing, pluggable encoding, and pluggable serializers. I saw a recent note from James Snell saying that he was making a fairly significant architecture change to Axis to support pluggable transports. I think there will be lots of opportunity to steal/merge code across the two code bases. I just don't want there to be a huge disruption in Axis to make it happen. Regards, Anne -Original Message- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 14, 2001 4:49 AM To: [EMAIL PROTECTED] Subject: Re: [POLL] WASP Lite on Apache? Anne Thomas Manes wrote: Stefano, I'm pleased that you think it's a good thing. To clarify: I was commenting Sam's note on I am looking forward to increased synergy and participation. Increased synergy is what I believe it's a good thing. Whether or not making WASP Lite an apache subproject, *this* is yet to be clarified to my eyes. Just to make sure that everybody understands this distinction: synergy *automatically* generates better communities. Competing projects, normally, do not. So to be crystal clear: synergy - good thing competing subprojects - not so sure We first thought of submitting WASP Lite to Axis, but after consideration determined that this approach would be too disruptive and technically challenging. Who considered that? you or the axis community? WASP Lite is a complete code base, and it would be very difficult to attempt to merge this code base with the Axis code base. Oh, believe me, you'd be surprised on how creative people can become if they are really interested in something. Any merger attempt would significantly delay both projects. We don't want to disrupt the Axis project. We share the same concerns though. Let us understand whether or not the move you propose goes in this direction or not. At the same time we think that the open source community will definitely benefit from WASP Lite. Oh, I don't question that. If Sam says so, I trust his technical judgement. But you didn't state We think that a separate project is the better way to go. I thank you very much for your suggestion and will be taken into very high consideration, but please keep in mind that it's up to the apache communities to decide what to do with donated code. If you decide to donate it in order to communities to benefit, it should not be your concern where the code ends up living, but should be the community's itself. Over time Axis and WASP Lite are likely to share code. Perhaps the projects might eventually converge. This wouldn't be the first time we've had competing projects at Apache (Crimson/Xerces/Xerces2 comes to mind). Exactly. We got burned big time by the politics involved in this very example and we DO NOT want this to happen again since we wouldn't have the energy to do this over again. It is exactly because of this example that I'm seriously concerned about having competing subprojects. Note: we have rules that allow committers of one project to propose an internal fork of the subproject itself, then is the community to decide what to do, but this doesn't separate them. If some of your guys are already committers of Axis and you think your solution is better from a technical perspective, then why don't you propose an internal fork with a new codename and work from there? I think it just goes to show that the community is very interested in the technology. Sorry, I can't follow you. I asked explicitly for overlap analysis in order to understand why you propose a different subproject but I didn't get that answer. Now, if you care about the interest of the community is should not matter where the code ends up living or what name it will end up having. Right? If you are so concerned about the name and the location, it only goes to show me that you are more interested in its location and its visibility than to the community interests. But I sincerely hope you can prove me wrong. So, let's get to the point: I'm personally against having two competing subprojects for no technical reason, no matter what they do. Technical competition should happen inside an existing community, following the Rules for revolutionaries. So, either somebody explains those technical reasons in detail (and convices me of the value of having two competing communities), or my vote remains a +1 on the acceptance of the code donation, but as a -1 on the creation of a new subproject. DISCLAIMER: having
