Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-26 Thread rich

+1 (sorry for the late reply)

Don Brown wrote:

http://wiki.apache.org/struts/WebWork2Incubator

= PROJECT PROPOSAL =

WebWork 2:  A Java web application development framework

A proposal to merge the WebWork 2 community and codebase into the 
Apache Struts project. The new codebase is slated to become Struts 
Action 2.


= RATIONALE =

The members of the Apache Struts project and the members of the 
OpenSymphony WebWork 2 project would like to work together on a 
next-generation web application framework utilizing an action/request 
architecture. WebWork was initially created by Rickard Oberg to 
improve on the ideas and functionality of the Jakarta Struts 
framework. (Now known as the Apache Struts Action framework.) Since 
then, the WebWork community has continued to extend and refine the 
framework's capabilities through a long series of releases, the latest 
of which, 2.2, brings advanced Ajax, templating, and Java 5 
capabilities to its solid WebWork 2 foundation.  While, to date, the 
WebWork and Struts Action codebases have overlapped, recent movements 
to bring consolidation to the web framework landscape have inspired 
both communities to work together. Apache Struts has recently 
reorganized our codebase into multiple subprojects, two of which, 
Shale and Action, represent two separate but equal web frameworks. 
Struts Shale serves the nascent JSF community, while Struts Action 
serves the established JSP community. The WebWork 2 code would be 
brought into the Action subproject as the 2.x branch.  The WebWork 2 
developers are excited by the prospect of joining the ASF and 
collaborating to solve our common need for a solid, action-based MVC2 
web framework. 
= CRITERIA =


== Meritocracy: ==

The WebWork 2 community is a healthy meritocracy with multiple 
developers who do not share a common employer. The creator of the 
project has already passed the torch to another generation of 
developers, who earn commit privileges through their individual 
contributions.


== Community: ==

The WebWork 2 community has a strong following with active mailing 
lists and forums.


https://webwork.dev.java.net/servlets/ProjectMailingListList

== WebWork Developers: ==

The WebWork developers includes individuals who have been with the 
project for a very long time and individuals who have only recently 
earned commit privileges. Contributions come steadily from all 
segments of the community, developer and user alike. Despite being 
used by many well-known corporations, WebWork 2 has not received any 
direct corporate contributions.


http://www.opensymphony.com/webwork/members.action

== Alignment: ==

WebWork and Struts Action are both action-oriented web frameworks, and 
the basic underlying models of the two are similar in many respects. 
Thus both projects strive to serve largely the same community of Java 
web application developers.


== License ==

WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache 
Software License 1.0.


* 2001-2006 http://www.opensymphony.com/webwork/license.action

= AVOIDING THE WARNING SIGNS =

== Orphaned products: ==

WebWork 2 will form the base of Struts Action 2.0 and is under heavy 
active development.


== Inexperience with open source: ==

The WebWork 2 project has been operating as a successful open source 
project for over four years.


== Homogenous developers: ==

The current list of committers includes developers from several 
different companies who are geographically dispersed. The developers 
are experienced with working in a distributed environment, and with 
resolving differences outside the scope of a common employer.


== Reliance on salaried developers: ==

WebWork does not rely on contributions from salaried developers, nor 
have commit privileges been extended based on an individual's employer.


== No ties to other ASF products: ==

The heritage of WebWork yields many close ties with the Apache Struts 
community. Many users have used one framework, then the other, and 
have different projects in the field that use either. The WebWork 2 
codebase also uses several Jakarta Commons libraries.


== A fascination with the ASF brand: ==

After several years of independence, the WebWork developers are ready 
to work within a larger community and expose the WebWork technology to 
a wider audience. The WebWork community is not seeking the ASF brand 
but seeks to collaborate with like minds in the Apache Struts 
projects. Both sets of developers are trying to solve the same 
problems in the same way, and we feel that we can create a stronger 
community and codebase together, than we can working independantly.


= INITIAL SOURCE =

The initial source comes from the WebWork 2 project, which uses CVS 
hosted at java.net.


* http://opensymphony.com/webwork/cvs.action

= RESOURCES TO BE CREATED =

* None. (Struts Action SVN module and build systems already exist.)

= INITIAL COMMITTERS =

* Jason Carreira (jcarreira at apache.org)
* Don Brown (mrdon 

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Ted Husted
On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:
 http://wiki.apache.org/struts/WebWork2Incubator

+1

With some minor patches:

- The WebWork community is not seeking the ASF brand but seeks
+ The WebWork community is not seeking the ASF brand but seek

- JamesMitchell
+ James Mitchell

And, as Martin mentioned

 = INITIAL COMMITTERS =

* Jason Carreira (jcarreira at apache.org)
+  * Martin Cooper (martinc at apache.org)


-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Wendy Smoak
On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:
 http://wiki.apache.org/struts/WebWork2Incubator

 = PROJECT PROPOSAL =

 WebWork 2:  A Java web application development framework

 A proposal to merge the WebWork 2 community and codebase into the Apache
 Struts project. The new codebase is slated to become Struts Action 2.

+1

--
Wendy Smoak

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Joe Germuska

At 8:16 PM -0800 1/24/06, Don Brown wrote:

= PROJECT PROPOSAL =

WebWork 2:  A Java web application development framework

A proposal to merge the WebWork 2 community and codebase into the 
Apache Struts project. The new codebase is slated to become Struts 
Action 2.


+1
--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com


You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed.  Try something new.
-- Robert Moog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread James Mitchell

+1



--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring
678.910.8017

- Original Message - 
From: Don Brown [EMAIL PROTECTED]

Newsgroups: gmane.comp.jakarta.struts.devel
Sent: Tuesday, January 24, 2006 11:16 PM
Subject: [VOTE] Accept WebWork 2 Merger Incubator Proposal



http://wiki.apache.org/struts/WebWork2Incubator

= PROJECT PROPOSAL =

WebWork 2:  A Java web application development framework

A proposal to merge the WebWork 2 community and codebase into the Apache 
Struts project. The new codebase is slated to become Struts Action 2.


= RATIONALE =

The members of the Apache Struts project and the members of the 
OpenSymphony WebWork 2 project would like to work together on a 
next-generation web application framework utilizing an action/request 
architecture. WebWork was initially created by Rickard Oberg to improve 
on the ideas and functionality of the Jakarta Struts framework. (Now 
known as the Apache Struts Action framework.) Since then, the WebWork 
community has continued to extend and refine the framework's 
capabilities through a long series of releases, the latest of which, 
2.2, brings advanced Ajax, templating, and Java 5 capabilities to its 
solid WebWork 2 foundation.  While, to date, the WebWork and Struts 
Action codebases have overlapped, recent movements to bring 
consolidation to the web framework landscape have inspired both 
communities to work together. Apache Struts has recently reorganized our 
codebase into multiple subprojects, two of which, Shale and Action, 
represent two separate but equal web frameworks. Struts Shale serves the 
nascent JSF community, while Struts Action serves the established JSP 
community. The WebWork 2 code would be brought into the Action 
subproject as the 2.x branch.  The WebWork 2 developers are excited by 
the prospect of joining the ASF and collaborating to solve our common 
need for a solid, action-based MVC2 web framework.  


= CRITERIA =

== Meritocracy: ==

The WebWork 2 community is a healthy meritocracy with multiple 
developers who do not share a common employer. The creator of the 
project has already passed the torch to another generation of 
developers, who earn commit privileges through their individual 
contributions.


== Community: ==

The WebWork 2 community has a strong following with active mailing lists 
and forums.


https://webwork.dev.java.net/servlets/ProjectMailingListList

== WebWork Developers: ==

The WebWork developers includes individuals who have been with the 
project for a very long time and individuals who have only recently 
earned commit privileges. Contributions come steadily from all segments 
of the community, developer and user alike. Despite being used by many 
well-known corporations, WebWork 2 has not received any direct corporate 
contributions.


http://www.opensymphony.com/webwork/members.action

== Alignment: ==

WebWork and Struts Action are both action-oriented web frameworks, and 
the basic underlying models of the two are similar in many respects. 
Thus both projects strive to serve largely the same community of Java 
web application developers.


== License ==

WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache 
Software License 1.0.


* 2001-2006 http://www.opensymphony.com/webwork/license.action

= AVOIDING THE WARNING SIGNS =

== Orphaned products: ==

WebWork 2 will form the base of Struts Action 2.0 and is under heavy 
active development.


== Inexperience with open source: ==

The WebWork 2 project has been operating as a successful open source 
project for over four years.


== Homogenous developers: ==

The current list of committers includes developers from several 
different companies who are geographically dispersed. The developers are 
experienced with working in a distributed environment, and with 
resolving differences outside the scope of a common employer.


== Reliance on salaried developers: ==

WebWork does not rely on contributions from salaried developers, nor 
have commit privileges been extended based on an individual's employer.


== No ties to other ASF products: ==

The heritage of WebWork yields many close ties with the Apache Struts 
community. Many users have used one framework, then the other, and have 
different projects in the field that use either. The WebWork 2 codebase 
also uses several Jakarta Commons libraries.


== A fascination with the ASF brand: ==

After several years of independence, the WebWork developers are ready to 
work within a larger community and expose the WebWork technology to a 
wider audience. The WebWork community is not seeking the ASF brand but 
seeks to collaborate with like minds in the Apache Struts projects. Both 
sets of developers are trying to solve the same problems in the same 
way, and we feel that we can create a stronger community and codebase 
together, than we can working independantly.


= INITIAL SOURCE =

The initial source comes from the WebWork 2 project

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Gary VanMatre
+1 non-binding

-- Original message -- 
From: Don Brown [EMAIL PROTECTED] 

 http://wiki.apache.org/struts/WebWork2Incubator 
 
 = PROJECT PROPOSAL = 
 
 WebWork 2: A Java web application development framework 
 
 A proposal to merge the WebWork 2 community and codebase into the Apache 
 Struts project. The new codebase is slated to become Struts Action 2. 
 
 = RATIONALE = 
 
 The members of the Apache Struts project and the members of the 
 OpenSymphony WebWork 2 project would like to work together on a 
 next-generation web application framework utilizing an action/request 
 architecture. WebWork was initially created by Rickard Oberg to improve 
 on the ideas and functionality of the Jakarta Struts framework. (Now 
 known as the Apache Struts Action framework.) Since then, the WebWork 
 community has continued to extend and refine the framework's 
 capabilities through a long series of releases, the latest of which, 
 2.2, brings advanced Ajax, templating, and Java 5 capabilities to its 
 solid WebWork 2 foundation. While, to date, the WebWork and Struts 
 Action codebases have overlapped, recent movements to bring 
 consolidation to the web framework landscape have inspired both 
 communities to work together. Apache Struts has recently reorganized our 
 codebase into multiple subprojects, two of which, Shale and Action, 
 represent two separate but equal web frameworks. Struts Shale serves the 
 nascent JSF community, while Struts Action serves the established JSP 
 community. The WebWork 2 code would be brought into the Action 
 subproject as the 2.x branch. The WebWork 2 developers are excited by 
 the prospect of joining the ASF and collaborating to solve our common 
 need for a solid, action-based MVC2 web framework. 
 
 = CRITERIA = 
 
 == Meritocracy: == 
 
 The WebWork 2 community is a healthy meritocracy with multiple 
 developers who do not share a common employer. The creator of the 
 project has already passed the torch to another generation of 
 developers, who earn commit privileges through their individual 
 contributions. 
 
 == Community: == 
 
 The WebWork 2 community has a strong following with active mailing lists 
 and forums. 
 
 https://webwork.dev.java.net/servlets/ProjectMailingListList 
 
 == WebWork Developers: == 
 
 The WebWork developers includes individuals who have been with the 
 project for a very long time and individuals who have only recently 
 earned commit privileges. Contributions come steadily from all segments 
 of the community, developer and user alike. Despite being used by many 
 well-known corporations, WebWork 2 has not received any direct corporate 
 contributions. 
 
 http://www.opensymphony.com/webwork/members.action 
 
 == Alignment: == 
 
 WebWork and Struts Action are both action-oriented web frameworks, and 
 the basic underlying models of the two are similar in many respects. 
 Thus both projects strive to serve largely the same community of Java 
 web application developers. 
 
 == License == 
 
 WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache 
 Software License 1.0. 
 
 * 2001-2006 http://www.opensymphony.com/webwork/license.action 
 
 = AVOIDING THE WARNING SIGNS = 
 
 == Orphaned products: == 
 
 WebWork 2 will form the base of Struts Action 2.0 and is under heavy 
 active development. 
 
 == Inexperience with open source: == 
 
 The WebWork 2 project has been operating as a successful open source 
 project for over four years. 
 
 == Homogenous developers: == 
 
 The current list of committers includes developers from several 
 different companies who are geographically dispersed. The developers are 
 experienced with working in a distributed environment, and with 
 resolving differences outside the scope of a common employer. 
 
 == Reliance on salaried developers: == 
 
 WebWork does not rely on contributions from salaried developers, nor 
 have commit privileges been extended based on an individual's employer. 
 
 == No ties to other ASF products: == 
 
 The heritage of WebWork yields many close ties with the Apache Struts 
 community. Many users have used one framework, then the other, and have 
 different projects in the field that use either. The WebWork 2 codebase 
 also uses several Jakarta Commons libraries. 
 
 == A fascination with the ASF brand: == 
 
 After several years of independence, the WebWork developers are ready to 
 work within a larger community and expose the WebWork technology to a 
 wider audience. The WebWork community is not seeking the ASF brand but 
 seeks to collaborate with like minds in the Apache Struts projects. Both 
 sets of developers are trying to solve the same problems in the same 
 way, and we feel that we can create a stronger community and codebase 
 together, than we can working independantly. 
 
 = INITIAL SOURCE = 
 
 The initial source comes from the WebWork 2 project, which uses CVS 
 hosted at java.net. 
 
 * 

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Niall Pemberton
+1

Niall

On 1/25/06, Don Brown [EMAIL PROTECTED] wrote:
 http://wiki.apache.org/struts/WebWork2Incubator

 = PROJECT PROPOSAL =

 WebWork 2:  A Java web application development framework

 A proposal to merge the WebWork 2 community and codebase into the Apache
 Struts project. The new codebase is slated to become Struts Action 2.

 = RATIONALE =

 The members of the Apache Struts project and the members of the
 OpenSymphony WebWork 2 project would like to work together on a
 next-generation web application framework utilizing an action/request
 architecture. WebWork was initially created by Rickard Oberg to improve
 on the ideas and functionality of the Jakarta Struts framework. (Now
 known as the Apache Struts Action framework.) Since then, the WebWork
 community has continued to extend and refine the framework's
 capabilities through a long series of releases, the latest of which,
 2.2, brings advanced Ajax, templating, and Java 5 capabilities to its
 solid WebWork 2 foundation.  While, to date, the WebWork and Struts
 Action codebases have overlapped, recent movements to bring
 consolidation to the web framework landscape have inspired both
 communities to work together. Apache Struts has recently reorganized our
 codebase into multiple subprojects, two of which, Shale and Action,
 represent two separate but equal web frameworks. Struts Shale serves the
 nascent JSF community, while Struts Action serves the established JSP
 community. The WebWork 2 code would be brought into the Action
 subproject as the 2.x branch.  The WebWork 2 developers are excited by
 the prospect of joining the ASF and collaborating to solve our common
 need for a solid, action-based MVC2 web framework.

 = CRITERIA =

 == Meritocracy: ==

 The WebWork 2 community is a healthy meritocracy with multiple
 developers who do not share a common employer. The creator of the
 project has already passed the torch to another generation of
 developers, who earn commit privileges through their individual
 contributions.

 == Community: ==

 The WebWork 2 community has a strong following with active mailing lists
 and forums.

 https://webwork.dev.java.net/servlets/ProjectMailingListList

 == WebWork Developers: ==

 The WebWork developers includes individuals who have been with the
 project for a very long time and individuals who have only recently
 earned commit privileges. Contributions come steadily from all segments
 of the community, developer and user alike. Despite being used by many
 well-known corporations, WebWork 2 has not received any direct corporate
 contributions.

 http://www.opensymphony.com/webwork/members.action

 == Alignment: ==

 WebWork and Struts Action are both action-oriented web frameworks, and
 the basic underlying models of the two are similar in many respects.
 Thus both projects strive to serve largely the same community of Java
 web application developers.

 == License ==

 WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache
 Software License 1.0.

  * 2001-2006 http://www.opensymphony.com/webwork/license.action

 = AVOIDING THE WARNING SIGNS =

 == Orphaned products: ==

 WebWork 2 will form the base of Struts Action 2.0 and is under heavy
 active development.

 == Inexperience with open source: ==

 The WebWork 2 project has been operating as a successful open source
 project for over four years.

 == Homogenous developers: ==

 The current list of committers includes developers from several
 different companies who are geographically dispersed. The developers are
 experienced with working in a distributed environment, and with
 resolving differences outside the scope of a common employer.

 == Reliance on salaried developers: ==

 WebWork does not rely on contributions from salaried developers, nor
 have commit privileges been extended based on an individual's employer.

 == No ties to other ASF products: ==

 The heritage of WebWork yields many close ties with the Apache Struts
 community. Many users have used one framework, then the other, and have
 different projects in the field that use either. The WebWork 2 codebase
 also uses several Jakarta Commons libraries.

 == A fascination with the ASF brand: ==

 After several years of independence, the WebWork developers are ready to
 work within a larger community and expose the WebWork technology to a
 wider audience. The WebWork community is not seeking the ASF brand but
 seeks to collaborate with like minds in the Apache Struts projects. Both
 sets of developers are trying to solve the same problems in the same
 way, and we feel that we can create a stronger community and codebase
 together, than we can working independantly.

 = INITIAL SOURCE =

 The initial source comes from the WebWork 2 project, which uses CVS
 hosted at java.net.

  * http://opensymphony.com/webwork/cvs.action

 = RESOURCES TO BE CREATED =

  * None. (Struts Action SVN module and build systems already exist.)

 = INITIAL COMMITTERS =

  * Jason Carreira 

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Greg Reddin


On Jan 24, 2006, at 10:16 PM, Don Brown wrote:


http://wiki.apache.org/struts/WebWork2Incubator


+1

Greg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Martin Cooper
On 1/25/06, Ted Husted [EMAIL PROTECTED] wrote:

 On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:
  http://wiki.apache.org/struts/WebWork2Incubator

 +1

 With some minor patches:

 - The WebWork community is not seeking the ASF brand but seeks
 + The WebWork community is not seeking the ASF brand but seek


Um, no. The English is correct as is. Community is singular, not plural.

--
Martin Cooper


- JamesMitchell
 + James Mitchell

 And, as Martin mentioned

 = INITIAL COMMITTERS =

 * Jason Carreira (jcarreira at apache.org)
 +  * Martin Cooper (martinc at apache.org)


 -Ted.

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Joe Germuska

At 9:11 AM -0800 1/25/06, Martin Cooper wrote:

On 1/25/06, Ted Husted [EMAIL PROTECTED] wrote:


 On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:
  http://wiki.apache.org/struts/WebWork2Incubator

 +1

 With some minor patches:

 - The WebWork community is not seeking the ASF brand but seeks
 + The WebWork community is not seeking the ASF brand but seek


Um, no. The English is correct as is. Community is singular, not plural.


heh.  I wondered about the same thing.  I don't think there's a 
conclusive answer.  At least, a little googling seemed to turn up 
arguments for either way.


For example, when referring to a musical group whose name isn't 
plural, there are different conventions in the US and the UK.  Like 
this current headline from nme.com: Elbow join Lancastrian 
super-gig  In the States, it would probably be Elbow joins...


Joe
--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com


You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed.  Try something new.
-- Robert Moog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread James Holmes
On Jan 24, 2006, at 10:16 PM, Don Brown wrote:

 http://wiki.apache.org/struts/WebWork2Incubator

+1

James


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Laurie Harper

+1 non-binding

Don Brown wrote:

http://wiki.apache.org/struts/WebWork2Incubator

= PROJECT PROPOSAL =

WebWork 2:  A Java web application development framework

A proposal to merge the WebWork 2 community and codebase into the Apache 
Struts project. The new codebase is slated to become Struts Action 2.


= RATIONALE =

The members of the Apache Struts project and the members of the 
OpenSymphony WebWork 2 project would like to work together on a 
next-generation web application framework utilizing an action/request 
architecture. WebWork was initially created by Rickard Oberg to improve 
on the ideas and functionality of the Jakarta Struts framework. (Now 
known as the Apache Struts Action framework.) Since then, the WebWork 
community has continued to extend and refine the framework's 
capabilities through a long series of releases, the latest of which, 
2.2, brings advanced Ajax, templating, and Java 5 capabilities to its 
solid WebWork 2 foundation.  While, to date, the WebWork and Struts 
Action codebases have overlapped, recent movements to bring 
consolidation to the web framework landscape have inspired both 
communities to work together. Apache Struts has recently reorganized our 
codebase into multiple subprojects, two of which, Shale and Action, 
represent two separate but equal web frameworks. Struts Shale serves the 
nascent JSF community, while Struts Action serves the established JSP 
community. The WebWork 2 code would be brought into the Action 
subproject as the 2.x branch.  The WebWork 2 developers are excited by 
the prospect of joining the ASF and collaborating to solve our common 
need for a solid, action-based MVC2 web framework. 
= CRITERIA =


== Meritocracy: ==

The WebWork 2 community is a healthy meritocracy with multiple 
developers who do not share a common employer. The creator of the 
project has already passed the torch to another generation of 
developers, who earn commit privileges through their individual 
contributions.


== Community: ==

The WebWork 2 community has a strong following with active mailing lists 
and forums.


https://webwork.dev.java.net/servlets/ProjectMailingListList

== WebWork Developers: ==

The WebWork developers includes individuals who have been with the 
project for a very long time and individuals who have only recently 
earned commit privileges. Contributions come steadily from all segments 
of the community, developer and user alike. Despite being used by many 
well-known corporations, WebWork 2 has not received any direct corporate 
contributions.


http://www.opensymphony.com/webwork/members.action

== Alignment: ==

WebWork and Struts Action are both action-oriented web frameworks, and 
the basic underlying models of the two are similar in many respects. 
Thus both projects strive to serve largely the same community of Java 
web application developers.


== License ==

WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache 
Software License 1.0.


* 2001-2006 http://www.opensymphony.com/webwork/license.action

= AVOIDING THE WARNING SIGNS =

== Orphaned products: ==

WebWork 2 will form the base of Struts Action 2.0 and is under heavy 
active development.


== Inexperience with open source: ==

The WebWork 2 project has been operating as a successful open source 
project for over four years.


== Homogenous developers: ==

The current list of committers includes developers from several 
different companies who are geographically dispersed. The developers are 
experienced with working in a distributed environment, and with 
resolving differences outside the scope of a common employer.


== Reliance on salaried developers: ==

WebWork does not rely on contributions from salaried developers, nor 
have commit privileges been extended based on an individual's employer.


== No ties to other ASF products: ==

The heritage of WebWork yields many close ties with the Apache Struts 
community. Many users have used one framework, then the other, and have 
different projects in the field that use either. The WebWork 2 codebase 
also uses several Jakarta Commons libraries.


== A fascination with the ASF brand: ==

After several years of independence, the WebWork developers are ready to 
work within a larger community and expose the WebWork technology to a 
wider audience. The WebWork community is not seeking the ASF brand but 
seeks to collaborate with like minds in the Apache Struts projects. Both 
sets of developers are trying to solve the same problems in the same 
way, and we feel that we can create a stronger community and codebase 
together, than we can working independantly.


= INITIAL SOURCE =

The initial source comes from the WebWork 2 project, which uses CVS 
hosted at java.net.


* http://opensymphony.com/webwork/cvs.action

= RESOURCES TO BE CREATED =

* None. (Struts Action SVN module and build systems already exist.)

= INITIAL COMMITTERS =

* Jason Carreira (jcarreira at apache.org)
* Don Brown (mrdon at apache.org)
* 

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Martin Cooper
On 1/25/06, Joe Germuska [EMAIL PROTECTED] wrote:

 At 9:11 AM -0800 1/25/06, Martin Cooper wrote:
 On 1/25/06, Ted Husted [EMAIL PROTECTED] wrote:
 
   On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:
http://wiki.apache.org/struts/WebWork2Incubator
 
   +1
 
   With some minor patches:
 
   - The WebWork community is not seeking the ASF brand but seeks
   + The WebWork community is not seeking the ASF brand but seek
 
 Um, no. The English is correct as is. Community is singular, not plural.

 heh.  I wondered about the same thing.  I don't think there's a
 conclusive answer.  At least, a little googling seemed to turn up
 arguments for either way.


Depends on whether you're talking about _correct_ usage versus _common_
usage. I'm talking about the former, and there's no debate. The latter is
quite frequently out of sync with the former, especially in the US, but
increasingly so in the UK as well, unfortunately.

For example, when referring to a musical group whose name isn't
 plural, there are different conventions in the US and the UK.  Like
 this current headline from nme.com: Elbow join Lancastrian
 super-gig  In the States, it would probably be Elbow joins...


Oh my gosh - I seriously hope people aren't learning their English from NME!
;-)

But this is more than a little off-topic, so I'll shut up now, even if I am
a stickler for this kind of thing.

--
Martin Cooper


Joe
 --
 Joe Germuska
 [EMAIL PROTECTED] * http://blog.germuska.com

 You really can't burn anything out by trying something new, and
 even if you can burn it out, it can be fixed.  Try something new.
 -- Robert Moog



Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-25 Thread Hubert Rabago
On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:
 http://wiki.apache.org/struts/WebWork2Incubator

 = PROJECT PROPOSAL =

 WebWork 2:  A Java web application development framework

+1

Hubert

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-24 Thread Don Brown

http://wiki.apache.org/struts/WebWork2Incubator

= PROJECT PROPOSAL =

WebWork 2:  A Java web application development framework

A proposal to merge the WebWork 2 community and codebase into the Apache 
Struts project. The new codebase is slated to become Struts Action 2.


= RATIONALE =

The members of the Apache Struts project and the members of the 
OpenSymphony WebWork 2 project would like to work together on a 
next-generation web application framework utilizing an action/request 
architecture. WebWork was initially created by Rickard Oberg to improve 
on the ideas and functionality of the Jakarta Struts framework. (Now 
known as the Apache Struts Action framework.) Since then, the WebWork 
community has continued to extend and refine the framework's 
capabilities through a long series of releases, the latest of which, 
2.2, brings advanced Ajax, templating, and Java 5 capabilities to its 
solid WebWork 2 foundation.  While, to date, the WebWork and Struts 
Action codebases have overlapped, recent movements to bring 
consolidation to the web framework landscape have inspired both 
communities to work together. Apache Struts has recently reorganized our 
codebase into multiple subprojects, two of which, Shale and Action, 
represent two separate but equal web frameworks. Struts Shale serves the 
nascent JSF community, while Struts Action serves the established JSP 
community. The WebWork 2 code would be brought into the Action 
subproject as the 2.x branch.  The WebWork 2 developers are excited by 
the prospect of joining the ASF and collaborating to solve our common 
need for a solid, action-based MVC2 web framework.  


= CRITERIA =

== Meritocracy: ==

The WebWork 2 community is a healthy meritocracy with multiple 
developers who do not share a common employer. The creator of the 
project has already passed the torch to another generation of 
developers, who earn commit privileges through their individual 
contributions.


== Community: ==

The WebWork 2 community has a strong following with active mailing lists 
and forums.


https://webwork.dev.java.net/servlets/ProjectMailingListList

== WebWork Developers: ==

The WebWork developers includes individuals who have been with the 
project for a very long time and individuals who have only recently 
earned commit privileges. Contributions come steadily from all segments 
of the community, developer and user alike. Despite being used by many 
well-known corporations, WebWork 2 has not received any direct corporate 
contributions.


http://www.opensymphony.com/webwork/members.action

== Alignment: ==

WebWork and Struts Action are both action-oriented web frameworks, and 
the basic underlying models of the two are similar in many respects. 
Thus both projects strive to serve largely the same community of Java 
web application developers.


== License ==

WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache 
Software License 1.0.


* 2001-2006 http://www.opensymphony.com/webwork/license.action

= AVOIDING THE WARNING SIGNS =

== Orphaned products: ==

WebWork 2 will form the base of Struts Action 2.0 and is under heavy 
active development.


== Inexperience with open source: ==

The WebWork 2 project has been operating as a successful open source 
project for over four years.


== Homogenous developers: ==

The current list of committers includes developers from several 
different companies who are geographically dispersed. The developers are 
experienced with working in a distributed environment, and with 
resolving differences outside the scope of a common employer.


== Reliance on salaried developers: ==

WebWork does not rely on contributions from salaried developers, nor 
have commit privileges been extended based on an individual's employer.


== No ties to other ASF products: ==

The heritage of WebWork yields many close ties with the Apache Struts 
community. Many users have used one framework, then the other, and have 
different projects in the field that use either. The WebWork 2 codebase 
also uses several Jakarta Commons libraries.


== A fascination with the ASF brand: ==

After several years of independence, the WebWork developers are ready to 
work within a larger community and expose the WebWork technology to a 
wider audience. The WebWork community is not seeking the ASF brand but 
seeks to collaborate with like minds in the Apache Struts projects. Both 
sets of developers are trying to solve the same problems in the same 
way, and we feel that we can create a stronger community and codebase 
together, than we can working independantly.


= INITIAL SOURCE =

The initial source comes from the WebWork 2 project, which uses CVS 
hosted at java.net.


* http://opensymphony.com/webwork/cvs.action

= RESOURCES TO BE CREATED =

* None. (Struts Action SVN module and build systems already exist.)

= INITIAL COMMITTERS =

* Jason Carreira (jcarreira at apache.org)
* Don Brown (mrdon at apache.org)
* Rene Gielen
* Rainer Hermanns
* 

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-24 Thread Don Brown

Unsurprisingly, my +1

Don

Don Brown wrote:


http://wiki.apache.org/struts/WebWork2Incubator

= PROJECT PROPOSAL =

WebWork 2:  A Java web application development framework

A proposal to merge the WebWork 2 community and codebase into the 
Apache Struts project. The new codebase is slated to become Struts 
Action 2.


= RATIONALE =

The members of the Apache Struts project and the members of the 
OpenSymphony WebWork 2 project would like to work together on a 
next-generation web application framework utilizing an action/request 
architecture. WebWork was initially created by Rickard Oberg to 
improve on the ideas and functionality of the Jakarta Struts 
framework. (Now known as the Apache Struts Action framework.) Since 
then, the WebWork community has continued to extend and refine the 
framework's capabilities through a long series of releases, the latest 
of which, 2.2, brings advanced Ajax, templating, and Java 5 
capabilities to its solid WebWork 2 foundation.  While, to date, the 
WebWork and Struts Action codebases have overlapped, recent movements 
to bring consolidation to the web framework landscape have inspired 
both communities to work together. Apache Struts has recently 
reorganized our codebase into multiple subprojects, two of which, 
Shale and Action, represent two separate but equal web frameworks. 
Struts Shale serves the nascent JSF community, while Struts Action 
serves the established JSP community. The WebWork 2 code would be 
brought into the Action subproject as the 2.x branch.  The WebWork 2 
developers are excited by the prospect of joining the ASF and 
collaborating to solve our common need for a solid, action-based MVC2 
web framework. 
= CRITERIA =


== Meritocracy: ==

The WebWork 2 community is a healthy meritocracy with multiple 
developers who do not share a common employer. The creator of the 
project has already passed the torch to another generation of 
developers, who earn commit privileges through their individual 
contributions.


== Community: ==

The WebWork 2 community has a strong following with active mailing 
lists and forums.


https://webwork.dev.java.net/servlets/ProjectMailingListList

== WebWork Developers: ==

The WebWork developers includes individuals who have been with the 
project for a very long time and individuals who have only recently 
earned commit privileges. Contributions come steadily from all 
segments of the community, developer and user alike. Despite being 
used by many well-known corporations, WebWork 2 has not received any 
direct corporate contributions.


http://www.opensymphony.com/webwork/members.action

== Alignment: ==

WebWork and Struts Action are both action-oriented web frameworks, and 
the basic underlying models of the two are similar in many respects. 
Thus both projects strive to serve largely the same community of Java 
web application developers.


== License ==

WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache 
Software License 1.0.


* 2001-2006 http://www.opensymphony.com/webwork/license.action

= AVOIDING THE WARNING SIGNS =

== Orphaned products: ==

WebWork 2 will form the base of Struts Action 2.0 and is under heavy 
active development.


== Inexperience with open source: ==

The WebWork 2 project has been operating as a successful open source 
project for over four years.


== Homogenous developers: ==

The current list of committers includes developers from several 
different companies who are geographically dispersed. The developers 
are experienced with working in a distributed environment, and with 
resolving differences outside the scope of a common employer.


== Reliance on salaried developers: ==

WebWork does not rely on contributions from salaried developers, nor 
have commit privileges been extended based on an individual's employer.


== No ties to other ASF products: ==

The heritage of WebWork yields many close ties with the Apache Struts 
community. Many users have used one framework, then the other, and 
have different projects in the field that use either. The WebWork 2 
codebase also uses several Jakarta Commons libraries.


== A fascination with the ASF brand: ==

After several years of independence, the WebWork developers are ready 
to work within a larger community and expose the WebWork technology to 
a wider audience. The WebWork community is not seeking the ASF brand 
but seeks to collaborate with like minds in the Apache Struts 
projects. Both sets of developers are trying to solve the same 
problems in the same way, and we feel that we can create a stronger 
community and codebase together, than we can working independantly.


= INITIAL SOURCE =

The initial source comes from the WebWork 2 project, which uses CVS 
hosted at java.net.


* http://opensymphony.com/webwork/cvs.action

= RESOURCES TO BE CREATED =

* None. (Struts Action SVN module and build systems already exist.)

= INITIAL COMMITTERS =

* Jason Carreira (jcarreira at apache.org)
* Don Brown (mrdon 

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-24 Thread Bryan LaPlante
Hi folks,

I just joined your dev group and noticed the voting here in. I have looked
at most of the AJAX frameworks and I have to through my 2 cents in here.
Webwork is using DWR flavor of AJAX. In my experience this introduces more
config settings and new syntax requirements on the client and server side. I
have been writing AJAX applications since 2000 and the framework I came up
with is absolutely transparent. No config files, No new syntax on server or
client, full support for java.util.*. It doesn't have to get more
complicated to be a better idea. If you are curious how I have done this
bounce over to http://www.xoscript.org and read getting started (short read)
or download the video tutorial that talks you through the point and click.
Honestly When I wrote this I just wanted to write Java, JavaScript and html,
not learn yet another framework.

End of rant, Thanks for listening.

Bryan LaPlante

- Original Message -
From: Don Brown [EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org
Sent: Tuesday, January 24, 2006 11:26 PM
Subject: Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal


 Unsurprisingly, my +1

 Don

 Don Brown wrote:

  http://wiki.apache.org/struts/WebWork2Incubator
 
  = PROJECT PROPOSAL =
 
  WebWork 2:  A Java web application development framework
 
  A proposal to merge the WebWork 2 community and codebase into the
  Apache Struts project. The new codebase is slated to become Struts
  Action 2.
 
  = RATIONALE =
 
  The members of the Apache Struts project and the members of the
  OpenSymphony WebWork 2 project would like to work together on a
  next-generation web application framework utilizing an action/request
  architecture. WebWork was initially created by Rickard Oberg to
  improve on the ideas and functionality of the Jakarta Struts
  framework. (Now known as the Apache Struts Action framework.) Since
  then, the WebWork community has continued to extend and refine the
  framework's capabilities through a long series of releases, the latest
  of which, 2.2, brings advanced Ajax, templating, and Java 5
  capabilities to its solid WebWork 2 foundation.  While, to date, the
  WebWork and Struts Action codebases have overlapped, recent movements
  to bring consolidation to the web framework landscape have inspired
  both communities to work together. Apache Struts has recently
  reorganized our codebase into multiple subprojects, two of which,
  Shale and Action, represent two separate but equal web frameworks.
  Struts Shale serves the nascent JSF community, while Struts Action
  serves the established JSP community. The WebWork 2 code would be
  brought into the Action subproject as the 2.x branch.  The WebWork 2
  developers are excited by the prospect of joining the ASF and
  collaborating to solve our common need for a solid, action-based MVC2
  web framework.
  = CRITERIA =
 
  == Meritocracy: ==
 
  The WebWork 2 community is a healthy meritocracy with multiple
  developers who do not share a common employer. The creator of the
  project has already passed the torch to another generation of
  developers, who earn commit privileges through their individual
  contributions.
 
  == Community: ==
 
  The WebWork 2 community has a strong following with active mailing
  lists and forums.
 
  https://webwork.dev.java.net/servlets/ProjectMailingListList
 
  == WebWork Developers: ==
 
  The WebWork developers includes individuals who have been with the
  project for a very long time and individuals who have only recently
  earned commit privileges. Contributions come steadily from all
  segments of the community, developer and user alike. Despite being
  used by many well-known corporations, WebWork 2 has not received any
  direct corporate contributions.
 
  http://www.opensymphony.com/webwork/members.action
 
  == Alignment: ==
 
  WebWork and Struts Action are both action-oriented web frameworks, and
  the basic underlying models of the two are similar in many respects.
  Thus both projects strive to serve largely the same community of Java
  web application developers.
 
  == License ==
 
  WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache
  Software License 1.0.
 
  * 2001-2006 http://www.opensymphony.com/webwork/license.action
 
  = AVOIDING THE WARNING SIGNS =
 
  == Orphaned products: ==
 
  WebWork 2 will form the base of Struts Action 2.0 and is under heavy
  active development.
 
  == Inexperience with open source: ==
 
  The WebWork 2 project has been operating as a successful open source
  project for over four years.
 
  == Homogenous developers: ==
 
  The current list of committers includes developers from several
  different companies who are geographically dispersed. The developers
  are experienced with working in a distributed environment, and with
  resolving differences outside the scope of a common employer.
 
  == Reliance on salaried developers: ==
 
  WebWork does not rely on contributions from salaried

Re: [VOTE] Accept WebWork 2 Merger Incubator Proposal

2006-01-24 Thread Martin Cooper
On 1/24/06, Don Brown [EMAIL PROTECTED] wrote:

 http://wiki.apache.org/struts/WebWork2Incubator


+1

Being a dope, I only just noticed that, although I'm listed as a mentor, I
didn't list myself as an initial committer. I'd like to add my name before
we send this proposal to the incubator.

--
Martin Cooper


= PROJECT PROPOSAL =

 WebWork 2:  A Java web application development framework

 A proposal to merge the WebWork 2 community and codebase into the Apache
 Struts project. The new codebase is slated to become Struts Action 2.

 = RATIONALE =

 The members of the Apache Struts project and the members of the
 OpenSymphony WebWork 2 project would like to work together on a
 next-generation web application framework utilizing an action/request
 architecture. WebWork was initially created by Rickard Oberg to improve
 on the ideas and functionality of the Jakarta Struts framework. (Now
 known as the Apache Struts Action framework.) Since then, the WebWork
 community has continued to extend and refine the framework's
 capabilities through a long series of releases, the latest of which,
 2.2, brings advanced Ajax, templating, and Java 5 capabilities to its
 solid WebWork 2 foundation.  While, to date, the WebWork and Struts
 Action codebases have overlapped, recent movements to bring
 consolidation to the web framework landscape have inspired both
 communities to work together. Apache Struts has recently reorganized our
 codebase into multiple subprojects, two of which, Shale and Action,
 represent two separate but equal web frameworks. Struts Shale serves the
 nascent JSF community, while Struts Action serves the established JSP
 community. The WebWork 2 code would be brought into the Action
 subproject as the 2.x branch.  The WebWork 2 developers are excited by
 the prospect of joining the ASF and collaborating to solve our common
 need for a solid, action-based MVC2 web framework.

 = CRITERIA =

 == Meritocracy: ==

 The WebWork 2 community is a healthy meritocracy with multiple
 developers who do not share a common employer. The creator of the
 project has already passed the torch to another generation of
 developers, who earn commit privileges through their individual
 contributions.

 == Community: ==

 The WebWork 2 community has a strong following with active mailing lists
 and forums.

 https://webwork.dev.java.net/servlets/ProjectMailingListList

 == WebWork Developers: ==

 The WebWork developers includes individuals who have been with the
 project for a very long time and individuals who have only recently
 earned commit privileges. Contributions come steadily from all segments
 of the community, developer and user alike. Despite being used by many
 well-known corporations, WebWork 2 has not received any direct corporate
 contributions.

 http://www.opensymphony.com/webwork/members.action

 == Alignment: ==

 WebWork and Struts Action are both action-oriented web frameworks, and
 the basic underlying models of the two are similar in many respects.
 Thus both projects strive to serve largely the same community of Java
 web application developers.

 == License ==

 WebWork 2 is under the OpenSymphony 1.1 license, a modified Apache
 Software License 1.0.

 * 2001-2006 http://www.opensymphony.com/webwork/license.action

 = AVOIDING THE WARNING SIGNS =

 == Orphaned products: ==

 WebWork 2 will form the base of Struts Action 2.0 and is under heavy
 active development.

 == Inexperience with open source: ==

 The WebWork 2 project has been operating as a successful open source
 project for over four years.

 == Homogenous developers: ==

 The current list of committers includes developers from several
 different companies who are geographically dispersed. The developers are
 experienced with working in a distributed environment, and with
 resolving differences outside the scope of a common employer.

 == Reliance on salaried developers: ==

 WebWork does not rely on contributions from salaried developers, nor
 have commit privileges been extended based on an individual's employer.

 == No ties to other ASF products: ==

 The heritage of WebWork yields many close ties with the Apache Struts
 community. Many users have used one framework, then the other, and have
 different projects in the field that use either. The WebWork 2 codebase
 also uses several Jakarta Commons libraries.

 == A fascination with the ASF brand: ==

 After several years of independence, the WebWork developers are ready to
 work within a larger community and expose the WebWork technology to a
 wider audience. The WebWork community is not seeking the ASF brand but
 seeks to collaborate with like minds in the Apache Struts projects. Both
 sets of developers are trying to solve the same problems in the same
 way, and we feel that we can create a stronger community and codebase
 together, than we can working independantly.

 = INITIAL SOURCE =

 The initial source comes from the WebWork 2 project, which uses CVS
 hosted at java.net.