Dashboard > SportsForge > Home
Added by Ted Husted, last edited by Ted Husted on Oct 02, 2006  (view change)
Labels: 
(None)


The SportsForge application provides stories, statistics, and forums regarding youth sports teams.

The application is now implemented as a "model 1" application using JSPs and scriptlets. This project is migrating the application to Struts 2. The source code is available at Struts SourceForge. To checkout the source, use the Subversion command

svn co https://svn.sourceforge.net/svnroot/struts/SportsForge/v2 SportsForge2

Project source code and documentation is provided under the Apache License.

The project uses Struts 2, which is under development. To build the project, you must first checkout and build Struts 2.
svn co https://svn.apache.org/repos/asf/struts/struts2/trunk struts2

To build the Struts and SportsForge source, install Maven 2. Then, change to the Struts folder and run mvn install. When that process completes, change to the SportsForge folder and run mvn install again.

If you are using IDEA, you can run mvn idea:idea to generate the IDEA projects. For Eclipse, you can run mvn eclipse:eclipse.

The project shares with Apache Struts and the ASF common values regarding collaborative, community-based open source development. Volunteers are invited to subscribe to the mailing list to get started.

Documentation

Resources

Portal The project portal describes the application to both users and developers. (You are here. )
Repository The repository contains a working copy of project materials, including source code and the portal.
Issue Tracker The issue tracker monitors progress on individual tasks, including applicatlon features and fixes.
Mailing List The mailing list is the nexus of team communication. All development decisions should be made on the list, even if by summary of any meetings, chats, or telephone conferences. Ideally, all changes to the Portal, Repository, or Issue Tracker, should be logged to the list, or List Archive.

External Resources

  • SportsForge: A Working Example

Next Steps

Setup PRIM infrastructure
Define requirements and use cases.
Implement a use case as a working example and starting point.
Prioritize the use cases in terms of a series of interations in which we implement the use cases. Each iteration should produce an application that does some useful work.
Implemented each interation.

= TODO; = Pending; = DONE.

Conventions (SportsForge)
Data Model (SportsForge)
Issue Tracker (SportsForge)
Requirements (SportsForge)
Use Cases (SportsForge)

Site running on a free Atlassian Confluence Open Source Project License granted to OSS. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) - Bug/feature request - Contact Administrators