This page tracks the project status, incubator-wise. For more general project status, look on the project website.
The WebWork 2 project graduated on 2006-05
The WebWork 2 project graduated on 2006-05
The Apache Struts project and the members of the OpenSymphony WebWork 2 project are working 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 will be brought into the Action subproject as the 2.x branch.
|Website||www||http://incubator.apache.org/projects/webwork2/ Not needed, will use Struts site|
|Website||wiki||http://wiki.apache.org/struts" Using the Struts site|
This is the first phase on incubation, needed to start the project at Apache.
Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).
|2006-02-21||Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product.|
|N/A||If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names.|
|2006-02-21||If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.|
|N/A||If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.|
|2006-02-21||Identify all the Mentors for the incubation, by asking all that can be Mentors.|
|2006-02-21||Subscribe all Mentors on the pmc and general lists.|
|2006-02-22||Give all Mentors access to all incubator SVN directory. (to be done by PMC chair)|
|2006-02-22||Tell Mentors to track progress in the file 'incubator/projects/webwork2.html'|
|2006-04-28||Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.|
|2006-04-28||Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.|
|2006-04-28||Check and make sure that for all code included with the distribution that is not under the Apache license, e have the right to combine with Apache-licensed code and redistribute.|
|2006-04-28||Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.|
|2006-03-22||Check that all active committers have submitted a contributors agreement.|
|2006-03-22||Add all active committers in the STATUS file.|
|2006-03-22||Ask root for the creation of committers' accounts on people.apache.org.|
|2006-02-22||Ask infrastructure to create source repository modules and grant the committers karma.|
|N/A||Ask infrastructure to set up and archive Mailing lists.|
|2006-02-28||Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira).|
|2006-04-28||Migrate the project to our infrastructure.|
Add project specific tasks here.
These action items have to be checked for during the whole incubation process.
These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.
Things to check for before voting the project out.