Menu
▾
▴
csms-cvs — Notification of CVS commits
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(157) |
Nov
(121) |
Dec
(19) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(34) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <rga...@us...> - 2003-01-09 12:07:35
|
Update of /cvsroot/csms/csms-core
In directory sc8-pr-cvs1:/tmp/cvs-serv5822
Modified Files:
centibuild.xml
Log Message:
Grouping cents
Index: centibuild.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/centibuild.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** centibuild.xml 8 Dec 2002 00:14:26 -0000 1.13
--- centibuild.xml 9 Jan 2003 12:07:32 -0000 1.14
***************
*** 22,32 ****
<taskdef file="${ant.home}/src/core/tasks.properties" />
<importcent name="antidote" />
<importcent name="java"/>
<importcent name="checkstyle" />
-
<importcent name="jdepend" />
!
<!-- FIXME: This cent should be uploaded to a Krysalis repositroy, until then
it will break builds, please comment this line out if you do not have the cent
--- 22,35 ----
<taskdef file="${ant.home}/src/core/tasks.properties" />
+ <!-- Building -->
<importcent name="antidote" />
<importcent name="java"/>
+ <importcent name="scripts" />
+ <!-- Quality Control -->
<importcent name="checkstyle" />
<importcent name="jdepend" />
! <importcent name="junit" />
!
<!-- FIXME: This cent should be uploaded to a Krysalis repositroy, until then
it will break builds, please comment this line out if you do not have the cent
***************
*** 34,47 ****
<importcent name="javaNCSS" dest="file://ext/openSource/krysalis-gpl-cents/cents"/> -->
<importcent name="forrest" />
-
- <importcent name="gump" />
-
<importcent name="javasrc" />
! <importcent name="junit" />
!
! <importcent name="scripts" />
!
<!-- =================================================================== -->
<!-- Basic build targets for the project -->
--- 37,45 ----
<importcent name="javaNCSS" dest="file://ext/openSource/krysalis-gpl-cents/cents"/> -->
+ <!-- Documentation -->
<importcent name="forrest" />
<importcent name="javasrc" />
!
<!-- =================================================================== -->
<!-- Basic build targets for the project -->
|
|
From: <rga...@us...> - 2003-01-02 00:58:54
|
Update of /cvsroot/csms/csms-core/src/documentation/override/checkstyle/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv11045
Modified Files:
book.xml
Log Message:
Workaround a bug in Forrest cent that was corrupting the index page
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/override/checkstyle/xdocs/book.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** book.xml 22 Oct 2002 09:24:04 -0000 1.1
--- book.xml 2 Jan 2003 00:58:51 -0000 1.2
***************
*** 8,12 ****
<menu label="">
! <menu-item label="Project Home" href="../"/>
</menu>
--- 8,12 ----
<menu label="">
! <menu-item label="Project Home" href="../index.html"/>
</menu>
***************
*** 17,24 ****
<menu label="Code">
! <menu-item label="Javadocs+UML" href="../javadocs"/>
! <menu-item label="Java Source Xref" href="../javasrc"/>
<menu-item label="Dependencies" href="../jdepend/index.html"/>
! <menu-item label="Unit tests" href="../junit"/>
</menu>
--- 17,24 ----
<menu label="Code">
! <menu-item label="Javadocs+UML" href="../javadocs/index.html"/>
! <menu-item label="Java Source Xref" href="../javasrc/index.html"/>
<menu-item label="Dependencies" href="../jdepend/index.html"/>
! <menu-item label="Unit tests" href="../junit/index.html"/>
</menu>
|
|
From: <rga...@us...> - 2003-01-02 00:58:43
|
Update of /cvsroot/csms/csms-core/src/documentation/override/jdepend/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv10979
Modified Files:
book.xml
Log Message:
Workaround a bug in Forrest cent that was corrupting the index page
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/override/jdepend/xdocs/book.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** book.xml 22 Oct 2002 12:23:43 -0000 1.1
--- book.xml 2 Jan 2003 00:58:40 -0000 1.2
***************
*** 8,19 ****
<menu label="">
! <menu-item label="Project Home" href="../"/>
</menu>
<menu label="Code">
! <menu-item label="Javadocs+UML" href="../javadocs"/>
! <menu-item label="Java Source Xref" href="../javasrc"/>
<menu-item label="Code Style Checks" href="../checkstyle/index.html"/>
! <menu-item label="Unit tests" href="../junit"/>
</menu>
--- 8,19 ----
<menu label="">
! <menu-item label="Project Home" href="../index.html"/>
</menu>
<menu label="Code">
! <menu-item label="Javadocs+UML" href="../javadocs/index.html"/>
! <menu-item label="Java Source Xref" href="../javasrc/index.html"/>
<menu-item label="Code Style Checks" href="../checkstyle/index.html"/>
! <menu-item label="Unit tests" href="../junit/index.html"/>
</menu>
|
|
From: <rga...@us...> - 2003-01-01 23:51:52
|
Update of /cvsroot/csms/csms-core/src/documentation/content
In directory sc8-pr-cvs1:/tmp/cvs-serv27470
Added Files:
book.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: book.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "dtd/book-cocoon-v10.dtd">
<book software="Community Sports Management System"
title="CSMS Community Home"
copyright="@year@ WkWyW.net"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Community">
<menu-item label="Project Home" href="http://sourceforge.net/projects/csms"/>
<menu-item label="License" href="license.html"/>
<menu-item label="Constitution" href="constitution.html"/>
<menu-item label="Short Term Plans" href="shortTermPlans.html"/>
<menu-item label="Long Term Plans" href="longTermPlans.html"/>
</menu>
<menu label="Docs">
<menu-item label="Introduction" href="index.html"/>
<menu-item label="Download/Install" href="downloadAndInstall/index.html"/>
<menu-item label="Manual" href="manual/index.html"/>
</menu>
<menu label="Code">
<menu-item label="Javadocs" href="javadocs/index.html"/>
<menu-item label="Java Source Ref" href="javasrc/index.html"/>
<menu-item label="Code Style Checks" href="checkstyle/index.html"/>
<menu-item label="Dependencies" href="jdepend/index.html"/>
<menu-item label="Unit tests" href="junit/index.html"/>
</menu>
</book>
|
|
From: <rga...@us...> - 2003-01-01 23:51:38
|
Update of /cvsroot/csms/csms-core/src/documentation/content/downloadAndInstall
In directory sc8-pr-cvs1:/tmp/cvs-serv27398
Added Files:
book.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: book.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "dtd/book-cocoon-v10.dtd">
<book software="Community Sports Management System"
title="CSMS Community Home"
copyright="@year@ WkWyW.net"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Community">
<menu-item label="Project Home" href="http://sourceforge.net/projects/csms"/>
<menu-item label="License" href="../license.html"/>
<menu-item label="Constitution" href="../constitution.html"/>
</menu>
<menu label="Docs">
<menu-item label="Introduction" href="../index.html"/>
<menu-item label="Download/Install" href="index.html"/>
<menu-item label="Manual" href="../manual/index.html"/>
</menu>
<menu label="Code">
<menu-item label="Javadocs" href="../javadocs/index.html"/>
<menu-item label="Java Source Ref" href="../javasrc/index.html"/>
<menu-item label="Code Style Checks" href="../checkstyle/index.html"/>
<menu-item label="Dependencies" href="../jdepend/index.html"/>
<menu-item label="Unit tests" href="../junit/index.html"/>
</menu>
</book>
|
|
From: <rga...@us...> - 2003-01-01 23:51:21
|
Update of /cvsroot/csms/csms-core/src/documentation/content/manual
In directory sc8-pr-cvs1:/tmp/cvs-serv27321
Added Files:
book.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: book.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "book-cocoon-v10.dtd">
<book software="Community Sports Management System"
title="CSMS Community Home"
copyright="@year@ WkWyW.net"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="Community">
<menu-item label="Project Home" href="http://sourceforge.net/projects/csms"/>
<menu-item label="License" href="../license.html"/>
<menu-item label="Constitution" href="../constitution.html"/>
</menu>
<menu label="Docs">
<menu-item label="Introduction" href="../index.html"/>
<menu-item label="Download/Install" href="../downloadAndInstall/index.html"/>
<menu-item label="Manual Home" href="index.html"/>
<menu-item label="Configuration" href="configuration.html"/>
</menu>
<menu label="Code">
<menu-item label="Javadocs" href="/javadocs/index.html"/>
<menu-item label="Java Source Ref" href="/javasrc/index.html"/>
<menu-item label="Code Style Checks" href="/checkstyle/index.html"/>
<menu-item label="Dependencies" href="/jdepend/index.html"/>
<menu-item label="Unit tests" href="/junit/index.html"/>
</menu>
</book>
|
|
From: <rga...@us...> - 2003-01-01 23:51:05
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs In directory sc8-pr-cvs1:/tmp/cvs-serv27265 Removed Files: book.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- book.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:50:53
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/manual In directory sc8-pr-cvs1:/tmp/cvs-serv27238 Removed Files: book.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- book.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:50:40
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall In directory sc8-pr-cvs1:/tmp/cvs-serv27198 Removed Files: book.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- book.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:50:28
|
Update of /cvsroot/csms/csms-core/src/documentation/content/downloadAndInstall
In directory sc8-pr-cvs1:/tmp/cvs-serv27106
Added Files:
configuration.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: configuration.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"./dtd/document-v11.dtd">
<document>
<header>
<title>CSMS - Configuration</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
</authors>
</header>
<body>
<section>
<title>Introduction</title>
<p>Currently the Community Sports Management System consists of the very
beginnings of one of the sports modules. This module provides facilites
to manage a fantasy Football (that's Soccer to our American friends),
However, this module can easily be adapted to provide other Fantasy
Sports games by providing additional configuration files that define the
rules for the game.</p>
<p>These configuration files are, in the default installation, loaded
from the internet, however, you can configure the locations they are
loaded from in the configuraiton dialog of the GUI interface as
described below. Example configuration files (the same ones available on
the Internet are avilable in the
<code>src/resources/conf</code>
directory of the source distributions. If you wish to fix any bugs found
in the online config files, please configure your application to use
these local files, edit them and supply patches to us via the
<link
href="http://sourceforge.net/tracker/?atid=509510&group_id=65029&func=browse">
patch tracking system</link>
. In fact, changing the settings to the local versions of the files will
make the system run faster since it will not have to download the files
from the Internet, however, you will not automatically benifit from
fixes in the files.</p>
<fixme author="rdg">Move all docs about the config files to here from
the wiki site. In the meantime, visitors can view the docs on
<link href="http://www.fanfoot.com/wiki/Wiki.jsp?page=AutomatedScoring">
our Wkii</link>
</fixme>
</section>
<section>
<title>Configuring The Fantasy Sports Module</title>
<p>The following preferneces will define where the configuration files
will be loaded from. You can change the default settings by selecting
the
<code>Preferences</code>
option in the
<code>Configuration</code>
menu.</p>
<table>
<caption>Auto Scorer Preferences</caption>
<tr>
<th>Preference Name</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<th colspan="3">Configuration Files</th>
</tr>
<tr>
<td>EventConfigurationFile</td>
<td>The URL from which the Event configuration file should be
loaded. This file defines a set of regular expression patterns that
are used to extract events from an information source concerning a
real sports game. This file is used to generate Events.xml a file
that describes all the events in a real game that may result in a
scoring opportunity in the fantasy game.</td>
<td>http://www.fanfoot.com/test/footballEvents.xml</td>
</tr>
<tr>
<td>ScoringConfigurationFile</td>
<td>The URL from which to load the Scoring Configuration file will
be loaded. This file defines how events in real games are converted
nto scores in the fantasy game. It is an XSL file that processes the
Events.xml file. When Events.xml is processed with this stylesheet
it should produce Scores.xml, a file representing all the scoring
events in a game.</td>
<td>http://www.fanfoot.com/test/ScoringConfig.xsl</td>
</tr>
<tr>
<td>Scores2HTMLStylsheet</td>
<td>The URL from which to download an XSL file used to convert the
Scores.xml file to an HTML file for display in the application.</td>
<td>http://www.fanfoot.com/test/Scores2HTML.xsl</td>
</tr>
</table>
<table>
<caption>Control Centre Preferences</caption>
<tr>
<th>Preference Name</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<th colspan="3">Miscellaneous</th>
</tr>
<tr>
<td>debug</td>
<td>Defines whether the appliation runs in debug mode or not.</td>
<td>true</td>
</tr>
</table>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:50:15
|
Update of /cvsroot/csms/csms-core/src/documentation/content/manual
In directory sc8-pr-cvs1:/tmp/cvs-serv27015
Added Files:
configuration.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: configuration.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"./dtd/document-v11.dtd">
<document>
<header>
<title>CSMS - Configuration</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
</authors>
</header>
<body>
<section>
<title>Introduction</title>
<p>Currently the Community Sports Management System consists of the very
beginnings of one of the sports modules. This module provides facilites
to manage a fantasy Football (that's Soccer to our American friends),
However, this module can easily be adapted to provide other Fantasy
Sports games by providing additional configuration files that define the
rules for the game.</p>
<p>These configuration files are, in the default installation, loaded
from the internet, however, you can configure the locations they are
loaded from in the configuraiton dialog of the GUI interface as
described below. Example configuration files (the same ones available on
the Internet are avilable in the
<code>src/resources/conf</code>
directory of the source distributions. If you wish to fix any bugs found
in the online config files, please configure your application to use
these local files, edit them and supply patches to us via the
<link
href="http://sourceforge.net/tracker/?atid=509510&group_id=65029&func=browse">
patch tracking system</link>
. In fact, changing the settings to the local versions of the files will
make the system run faster since it will not have to download the files
from the Internet, however, you will not automatically benifit from
fixes in the files.</p>
<fixme author="rdg">Move all docs about the config files to here from
the wiki site. In the meantime, visitors can view the docs on
<link href="http://www.fanfoot.com/wiki/Wiki.jsp?page=AutomatedScoring">
our Wkii</link>
</fixme>
</section>
<section>
<title>Configuring The Fantasy Sports Module</title>
<p>The following preferences will define where the configuration files
will be loaded from. You can change the default settings by selecting
the relevant option in the
<code>Configuration</code>
menu.</p>
<note>If you are using the CVS version of the application the defaults are not those
listed here, but are the relevant files in CVS.</note>
<table>
<caption>Auto Scorer Preferences</caption>
<tr>
<th>Preference Name</th>
<th>Description</th>
<th>Default <link href="#defaultsNote">*</link></th>
</tr>
<tr>
<th colspan="3">Configuration Files</th>
</tr>
<tr>
<td>EventConfigurationFile</td>
<td>The URL from which the Event configuration file should be
loaded. This file defines a set of regular expression patterns that
are used to extract events from an information source concerning a
real sports game. This file is used to generate Events.xml a file
that describes all the events in a real game that may result in a
scoring opportunity in the fantasy game.</td>
<td>http://www.fanfoot.com/test/footballEvents.xml</td>
</tr>
<tr>
<td>ScoringConfigurationFile</td>
<td>The URL from which to load the Scoring Configuration file will
be loaded. This file defines how events in real games are converted
nto scores in the fantasy game. It is an XSL file that processes the
Events.xml file. When Events.xml is processed with this stylesheet
it should produce Scores.xml, a file representing all the scoring
events in a game.</td>
<td>http://www.fanfoot.com/test/ScoringConfig.xsl</td>
</tr>
<tr>
<td>Scores2HTMLStylsheet</td>
<td>The URL from which to download an XSL file used to convert the
Scores.xml file to an HTML file for display in the application.</td>
<td>http://www.fanfoot.com/test/Scores2HTML.xsl</td>
</tr>
</table>
<anchor id="defaultsNote"/>
<p>In the CVS version of the application these defaults for the configuration files are differnet from
those indicated here. Generally, they point at the CVS HEAD version of the config files.</p>
<table>
<caption>Control Centre Preferences</caption>
<tr>
<th>Preference Name</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<th colspan="3">Miscellaneous</th>
</tr>
<tr>
<td>debug</td>
<td>Defines whether the appliation runs in debug mode or not.</td>
<td>true</td>
</tr>
</table>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:49:59
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/manual In directory sc8-pr-cvs1:/tmp/cvs-serv26939 Removed Files: configuration.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- configuration.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:49:47
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall In directory sc8-pr-cvs1:/tmp/cvs-serv26876 Removed Files: configuration.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- configuration.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:49:32
|
Update of /cvsroot/csms/csms-core/src/documentation/content
In directory sc8-pr-cvs1:/tmp/cvs-serv26805
Added Files:
constitution.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: constitution.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"./dtd/document-v11.dtd">
<document>
<header>
<title>Community Sports Management System Project Constitution</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
</authors>
</header>
<body>
<section>
<title>Project Constitution</title>
<note>Inspired by the Krysalis Community constitution, which in turn is
inspired by the xml.apache.org constitution. (Apache Software Foundation
- all rights reserved)</note>
<p>This document defines the guidelines of the Community Sports
Management Systems project (CSMS). It includes definitions of the
various categories of membership, who is able to vote, how conflicts are
resolved by voting, and the procedures to follow for proposing and
making changes to the codebase of the Project.</p>
<p>This is a living document. Changes can be made by the Project
Management Committee and must be approved by 2/3 of all Developers.</p>
<p>This document consists of the following sections:</p>
<ul>
<li>Our Mission</li>
<li>Roles and Responsibilities: defines the recognized roles in the
project</li>
<li>Decision Making: defines how action items are proposed and voted
on</li>
<li>Communication: defines how users and developers communicate</li>
<li>Source Repositories: define how the Project's source code is
organized and developed</li>
<li>Project Management: defines the roles and responsibilities of the
Project Management Committee (PMC)</li>
<li>Project Management Committee (PMC) Bylaws</li>
</ul>
</section>
<section>
<title>Our Mission</title>
<p>Our mission is to build a community and software system to support
the growth and development of sports clubs of all types. We aim to bring
these valuable real world communities together in the virtual world of
the Internet. The objective is to encourage more participation in sports
clubs of all types by all people whether they be players, organisers or
supporters.</p>
</section>
<section>
<title>Roles and Responsibilities</title>
<p>The roles and responsibilities that people can assume in the project
are based on merit. Everybody can help no matter what their role. Those
who have been long term or valuable contributors to the project obtain
the right to vote and commit directly to the document and source code
repository.</p>
<p>There are five roles within the community, each role brings with it a
set of responsabilities. These roles are not mutually exclusive. The
roles are:</p>
<ol>
<li>Members</li>
<li>Content Managers</li>
<li>Developers</li>
<li>Committers</li>
<li>Project Managmement Committee members</li>
</ol>
<section>
<title>Members</title>
<p>Anyone can be a member.</p>
<p>Members are the people who participate in the community. They use
the products of the Project. People in this role aren't contributing
code or documents to the repository, however,they are contributing to
the community by providing valuable feedback and requests for
enhancements, as well as making the community stronger through their
support.</p>
<p>This is by far the most important category of people as, without
members, there is no reason for the project or for the community.</p>
</section>
<section>
<title>Content Managers</title>
<p>Content Managers also have the responsabilities of Members.</p>
<p>Members who contribute to the data, information and news available
to the community on a frequent basis can be proposed as a Content
Manager, or they may request Content Manager status. Any member can
propose any other member as a Content Manager. Once proposed a vote of
the existing Content Managers is carried out (see below for voting
procedures). A result of at least three positive votes and no negative
votes will result in the creation of a new Content Manager.</p>
<p>Content Managers are able to edit materials posted by other members
(normally only the poster can edit their own materials). They also
have the ability to create new sections within the community to
support new sports, teams and interests. As such, the Content Managers
are answerable to the Members and must endeavour to ensure the
community facilities available are what the members require,</p>
<p>At times, Content Managers may go inactive for a variety of
reasons. A Content Manager that has been inactive for 4 months or more
may lose his or her status as a Content Manager. However, they will
always be contacted via their last known email address before Content
Manager status is removed.</p>
</section>
<section>
<title>Developers</title>
<p>Anyone can be a developer.</p>
<p>Developers are the people contribute to the project by writing code
and documentation patches or contribute positively to the project
products in other ways such as through open discussion on our
developer lists. A developer's contribution is always recognized. In
source code, all developers who contribute to a source file may add
their name to the list of authors for that file. In documentation,
they may similarly add their name to the authors list for any document
they contribute to.</p>
<p>These credits will be reproduced in all source code distributions
of the software and in all documentation.</p>
</section>
<section>
<title>Committers</title>
<p>Developers who give frequent and valuable contributions to a
subproject of the CSMS project can have their status promoted to that
of a "Committer" for that subproject.</p>
<p>A Committer has write access to the source code repository and
gains voting rights allowing them to affect the future of the
subproject. In order for a Developer to become a Committer, another
Committer can nominate that Developer or the Developer can ask for it.
Once a Developer is nominated, all of the Committers for a subproject
will vote. If there are at least 3 positive votes and no negative
votes, the Developer is converted into a Committer and given write
access to the source code repository for that subproject.</p>
<p>At times, Committers may go inactive for a variety of reasons. A
Committer that has been inactive for 6 months or more may lose his or
her status as a Committer. However, they will always be contacted via
their last known email address before commiter status is removed.</p>
<p>Committers have the right to add their details to the license under
which all proucts of the project are released.</p>
</section>
<section>
<title>Project Management Committee (PMC) Member</title>
<p>Committers who frequently participate with valuable contributions
may have their status promoted to that of a "Project Management
Committee Member".</p>
<p>This committee is the official managing body of the CSMS Project
and is responsible for setting overall project direction. On
Sourceforge (sourceforge.net) they are called admins. In order to
become a Member of the PMC, someone on the PMC must nominate the
Committer. The individual may then be approved with a 3/4 majority of
the PMC.</p>
<p>The PMC has the right to secure the health of the community, and
has the power to exclude any developer, content manager or member from
the community as an extreme measure if he/she endangers the mission of
the Project. All exclusions must be passed with a 3/4 majority vote.
No vetoes are permmmitted on such votes.</p>
</section>
</section>
<section>
<title>Decision Making</title>
<p>All Members, Developers and Content Managers are encouraged to
participate in decisions, but the decision itself is made by those that
have Committer status in the Project. In other words, the Project is a
"Minimum Threshold Meritocracy".</p>
<p>Any person, whether a member or not, may vote on any issue or action
item. However, the only binding votes are those cast by a Committer. If
the vote is about a change to the source code or documentation and the
primary author is a Developer and not a Commiter, the primary author of
what is being changed may also cast a binding vote on that issue.</p>
<p>The act of voting carries certain obligations. Voting members are not
only stating their opinion, they are also agreeing to help do the
work.</p>
<p>Each vote can be made in one of three flavors:</p>
<dl>
<dt>+1</dt>
<dd>"Yes," "Agree," or "the action should be performed." On some
issues this is only binding if the voter has tested the action on
their own system(s).</dd>
<dt>+/-0</dt>
<dd>"Abstain," "no opinion". If, as a commiter, you are unable to
commit to helping bring the results of the vote to fruition you should
abstain rather than cast a +1. The use of +0 can indicate your
preference in the event of a tied vote. In this instance a +0 vote is
taken as meaning "+1 but I can't help". A 0 or -0 vote is treated as
"no opinion".</dd>
<dt>-1</dt>
<dd>"No." On issues where consensus is required, this vote counts as a
veto. All vetos must contain an explanation of why the veto is
appropriate. Vetos with no explanation are void. No veto can be
overruled. If you disagree with the veto, you should lobby the person
who cast the veto. Voters intending to veto an action item should make
their opinions known to the group immediately so that the problem can
be remedied as early as possible.</dd>
</dl>
<p>An action requiring consensus approval must receive at least 3
binding +1 votes and no binding vetos.</p>
<p>An action requiring majority approval must receive at least 3 binding
+1 votes and more +1 votes than -1 votes.</p>
<p>All other action items are considered to have lazy approval until
somebody votes -1, after which point they are decided by either
consensus or majority vote, depending on the type of action item.</p>
</section>
<section>
<title>Action Items</title>
<p>All decisions revolve around "Action Items." Action Items consist of
the following:</p>
<ul>
<li>Long Term Plans</li>
<li>Short Term Plans</li>
<li>Release Plan</li>
<li>Release Testing</li>
<li>Showstoppers</li>
<li>Product Changes</li>
<li>Appointement of a new Content Manager</li>
<li>Appointment of a new Committer</li>
<li>Appointment of a new PMC member</li>
<li>Removal of Cotent Manager Status</li>
<li>Removal of Committer Status</li>
<li>Removal of PMC Membership</li>
<li>Exclusion of a member</li>
</ul>
<section>
<title>Long Term Plans</title>
<p>Long term plans are simply announcements that group members are
working on particular issues related to the Project. These are not
voted on, but Developers who do not agree with a particular plan, or
think that an alternative plan would be better, are obligated to
inform the group of their feelings by applying (and explaining) a
veto.</p>
</section>
<section>
<title>Short Term Plans</title>
<p>Short term plans are announcements that a developer is working on a
particular set of documentation or code files with the implication
that other developers should avoid them or try to coordinate their
changes. These are not voted on, but Developers who do not agree with
a particular plan, or think that an alternative plan would be better,
are obligated to inform the group of their feelings by applying (and
explaining) a veto.</p>
</section>
<section>
<title>Release Plan</title>
<p>A release plan is used to keep all Developers aware of when a
release is desired, who will be the release manager, when the
repository will be frozen to create a release, and other assorted
information to keep Developers from tripping over each other. Lazy
majority decides each issue in a release plan.</p>
</section>
<section>
<title>Release Testing</title>
<p>After a new release is built, it must be tested before being
released to the public. Majority approval is required before the
release can be made.</p>
</section>
<section>
<title>Showstoppers</title>
<p>Showstoppers are issues that require a fix be in place before the
next public release. They are listed in the status file in order to
focus special attention on these problems. An issue becomes a
showstopper when it is listed as such in the status file and remains
so by lazy consensus.</p>
</section>
<section>
<title>Product Changes</title>
<p>Changes to the products of the Project, including code and
documentation, will appear as action items in the status file. All
product changes to the currently active repository are subject to lazy
consensus.</p>
</section>
<section>
<title>Appointement of a new Content Manager</title>
<p>Members who contribute to the data, information and news available
to the community on a frequent basis can be proposed as a Content
Manager, or they may request Content Manager status. Any member can
propose any other member as a Content Manager. Once proposed a vote of
the existing Content Managers is carried out (see below for voting
procedures). A result of at least three positive votes and no negative
votes will result in the creation of a new Content Manager.</p>
</section>
<section>
<title>Appointment of a new Committer</title>
<p>A Committer can nominate any Developer as a new Committer or a
Developer may ask for a vote on their acceptance as a Committer. Once
a Developer is nominated, all of the Committers for a subproject will
vote. If there are at least 3 positive votes and no negative votes,
the Developer is converted into a Committer and given write access to
the source code repository for that subproject.</p>
</section>
<section>
<title>Removal of Content Manager Status</title>
<p>If a Content Manager has been inactive for 4 months or more any
other Content Manager can request the removal of Content Manager
status from that person. No vote is taken until an attempt to contact
the Content Manager at their last known email address and a further 4
weeks have past. If the Content Manager respondes, agreeing that they
are no longer active then no vote is required. However, if no response
is recieved, or if a request is to retain their status a vote is
taken. A result of 3 or more positive votes and no negative votes will
result in the removal of Content Manager status.</p>
</section>
<section>
<title>Removal of Commiter Status</title>
<p>If a Committer has been inactive for 6 months or more any other
Committer can request the removal of Committer status from that
person. No vote is taken until an attempt to contact the Committer at
their last known email address and a further 4 weeks have past. If the
Committer respondes, agreeing that they are no longer active then no
vote is required. However, if no response is recieved, or if a request
is to retain their status a vote is taken. A result of 3 or more
positive votes and no negative votes will result in the removal of
Committer status.</p>
<p>Removal of Commiter status does not mean that credits in source
code and license files is removed. These credits cannot be removed
under any circumstances.</p>
</section>
<section>
<title>Appointment of a new PMC member</title>
<p>The existing PMC can nominate any Committer as a new PMC Member.
New members are accepted on a 3/4 majority. There are no veto cotes in
this cote.</p>
</section>
<section>
<title>Removal of PMC Membership</title>
<p>Any member of the community has the right to request a member of
the PMC be removed. Such a vote will go to all members and no veto is
allowed. A majority of 3/4 is required to remove a PMC member.</p>
</section>
<section>
<title>Exclusion of a Member</title>
<p>The PMC has the right to secure the health of the community, and
has the power to exclude any developer, content manager or member from
the community as an extreme measure if he/she endangers the mission of
the Project. All exclusions must be passed with a 3/4 majority vote.
No vetoes are permmmitted on such votes.</p>
</section>
</section>
<section>
<title>Communication</title>
<p>The project obtains its strength from the communication of its
members. In order for members to easily communicate with each other, the
project has a variety of mailing lists. These lists, with the exception
of the announcement lists, are not moderated and anybody is more than
welcome to join them. However, you must be subscribed to post to a
list.</p>
<p>To reduce the bandwidth demands on everyone, mail should not contain
attachments and be in plain text. It is recommended that you place
interesting material either within the body of the message or provide a
URL for retrieval. If you do not have public space available for sharing
of large data files please post a request for assistance on the relavent
mailing list. Someone in the community will assist.</p>
<p>The Project's lists fall into the following categories:</p>
<section>
<title>Announcement Lists</title>
<p>Announcement lists are very low traffic designed to communicate
important information, such as final releases of a subproject's code,
to a wide audience.</p>
</section>
<section>
<title>User Lists</title>
<p>User lists are for users of a product to converse about such things
as configuration and operating of the products of the project.</p>
</section>
<section>
<title>Developer Lists</title>
<p>Developer lists are for the developers of the project. On these
lists suggestions and comments for code changes are discussed and
action items are raised and voted on. For the developer community,
these lists are the very center of the project where all the "action"
is.</p>
</section>
<section>
<title>Commit Lists</title>
<p>The commit lists are where all cvs code commit messages are sent.
All committers are required to subscribe to this list so that they can
stay aware of changes to the repository.</p>
</section>
</section>
<section>
<title>Source Repositories</title>
<p>The project's codebase is maintained in shared information
repositories using CVS on sourceforge.net. Only Committers have write
access to these repositories. Everyone has read access via anonymous
CVS.</p>
<section>
<title>Coding Conventions</title>
<p>Java Language source code in the repository is recommended to be
written in conformance to the Code Conventions for the Java
Programming Language as published by Sun
(http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html).</p>
</section>
<section>
<title>License</title>
<p>All source code committed to the Project's repositories must be
covered by the most recent version of The Mozilla Public License at
the time of the contribution. Binary files can, as an alternative,
contain a copyright and license that allows redistribution under the
same conditions as the Mozilla Public License.</p>
</section>
<section>
<title>Status Files</title>
<p>Each of the project's active source code repositories contain a
file named status.xml which is used to keep track of the agenda and
plans for work within that repository. The status file includes
information about release plans, a summary of code changes committed
since the last release,</p>
</section>
<section>
<title>Branches</title>
<p>Groups are allowed to create a branch for release cycles, etc. They
are expected to merge completely back with the main branch as soon as
their release cycle is complete.</p>
</section>
<section>
<title>Changes</title>
<p>Simple patches to fix bugs can be committed then reviewed. With a
commit-then-review process, the Committer is trusted to have a high
degree of confidence in the change.</p>
<p>Doubtful changes, new features, and large scale overhauls need to
be discussed before committing them into the repository. Any change
that affects the semantics of an existing API function, the size of
the program, configuration data formats, or other major areas must
receive consensus approval before being committed.</p>
<p>Related changes should be committed as a group, or very closely
together. Half complete projects should never be committed to the main
branch of a development repository. All code changes must be
successfully compiled on the developer's platform before being
committed.</p>
<p>The current source code tree for a subproject should be capable of
complete compilation at all times. However, it is sometimes impossible
for a developer on one platform to avoid breaking some other platform
when a change is committed. If it is anticipated that a given change
will break the build on some other platform, the committer must
indicate that in the commit message.</p>
<p>A committed change must be reversed if it is vetoed by one of the
voting members and the veto conditions cannot be immediately satisfied
by the equivalent of a "bug fix" commit. The veto must be rescinded
before the change can be included in any public release.</p>
</section>
<section>
<title>Patches</title>
<p>When a specific change to a product is proposed for discussion or
voting on the appropriate development mailing list, it should be
presented in the form of input to the patch command. The patch must be
inserted in the patch tracking system for consideration by the
committers.</p>
<p>The patch should be created by using the diff -u command from the
original software file(s) to the modified software file(s). For
example:</p>
<p>
<code>diff -u Main.java.orig Main.java >> patchfile.txt</code>
</p>
<p>or</p>
<p>
<code>cvs diff -u Main.java >> patchfile.txt</code>
</p>
<p>All patches necessary to address an action item should be
concatencated within a single patch message. If later modification to
the patch proves necessary, the entire new patch should be posted and
not just the difference between the two patches.</p>
</section>
</section>
<section>
<title>Project Management Committee (PMC) Bylaws</title>
<p>The Project Management Committee (PMC) was formed by the CSMS
founders in October 2002. This Committee consists of 3 founding members,
one of whom is the founding Chairman.</p>
<p>The term of the Chairman is one year. There is no term limit for
members.</p>
<section>
<title>Roles</title>
<p>The PMC is responsible for the strategic direction and success of
the CSMS project. This governing body is expected to ensure the
project's welfare and guide its overall direction. The PMC may not
necessarily participate in the day-to-day coding but is involved in
the overall development plans, the alleviation of any bottlenecks, the
resolution of conflicts, and the overall technical success of the
project.</p>
</section>
<section>
<title>Meetings</title>
<p>The PMC do not meet regularly. However, they are expected to be in
close communitation on a regular basis.</p>
<p>Formal meetings may be called by any PMC member and all members are
expected to make all reasonable efforts to attend. These formal
meetings are to discuss issues, determine strategic direction, and
forward progress. These meetings may take place online, via
teleconference, or via other means deemed effective by the PMC.</p>
<p>The PMC has an annual meeting at which time a new Chairman is
elected. The old Chairman maintains membership status with no extra
privileges.</p>
</section>
<section>
<title>Membership</title>
<p>PMC members may resign at any time. The Chairman may resign as
Chairman at any time without resigning membership to the PMC.</p>
</section>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:49:08
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs In directory sc8-pr-cvs1:/tmp/cvs-serv26757 Removed Files: constitution.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- constitution.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:48:55
|
Update of /cvsroot/csms/csms-core
In directory sc8-pr-cvs1:/tmp/cvs-serv26704
Added Files:
forrest.properties
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: forrest.properties ---
##############
# Properties used by forrest.build.xml for building the website
##############
# Prints out a summary of Forrest settings for this project
#forrest.echo=true
# Project name (used to name .war file)
#project.name=my-project
# Specifies name of Forrest skin to use
#forrest.cent.project.skin=krysalis-site
#project.skin=krysalis-site
#project.skin=avalon-tigris
##############
# layout properties
# Properties that must be set to override the default locations
#project.status=status.xml
forrest.cent.project.content-dir=src/documentation
project.content-dir=src/documentation
#project.conf-dir=${project.content-dir}/conf
#project.sitemap=${project.content-dir}/sitemap.xmap
forrest.cent.project.xdocs-dir=${forrest.cent.project.content-dir}/content
project.xdocs-dir=${forrest.cent.project.content-dir}/content
#project.stylesheets-dir=${project.content-dir}/resources/stylesheets
#project.images-dir=${project.content-dir}/resources/images
#project.schema-dir=${project.content-dir}/resources/schema
#project.skins-dir=${project.content-dir}/skins
#project.skinconf=${project.content-dir}/skinconf.xml
#project.lib-dir=${project.content-dir}/lib
#project.classes-dir=${project.content-dir}/classes
##############
# validation properties
# These props determine if validation is performed at all
# Values are inherited unless overridden.
# Eg, if forrest.validate=false, then all others are false unless set to true.
#forrest.validate=false
#forrest.validate.xdocs=${forrest.validate}
#forrest.validate.skinconf=${forrest.validate}
forrest.validate.sitemap=false
#forrest.validate.stylesheets=${forrest.validate}
#forrest.validate.skins=${forrest.validate}
#forrest.validate.skins.stylesheets=${forrest.validate.skins}
# Key:
# *.failonerror=(true|false) stop when an XML file is invalid
# *.includes=(pattern) Comma-separated list of path patterns to validate
# *.excludes=(pattern) Comma-separated list of path patterns to not validate
#forrest.validate.failonerror=true
#forrest.validate.includes=**/*
#forrest.validate.excludes=
#
#forrest.validate.xdocs.failonerror=${forrest.validate.failonerror}
#
#forrest.validate.xdocs.includes=*.x*
#forrest.validate.xdocs.excludes=
#
#forrest.validate.skinconf.includes=${skinconf-file}
#forrest.validate.skinconf.excludes=
#forrest.validate.skinconf.failonerror=${forrest.validate.failonerror}
#
#forrest.validate.sitemap.includes=${sitemap-file}
#forrest.validate.sitemap.excludes=
#forrest.validate.sitemap.failonerror=${forrest.validate.failonerror}
#
#forrest.validate.stylesheets.includes=**/*.xsl
#forrest.validate.stylesheets.excludes=
#forrest.validate.stylesheets.failonerror=${forrest.validate.failonerror}
#
#forrest.validate.skins.includes=**/*
#forrest.validate.skins.excludes=**/*.xsl
#forrest.validate.skins.failonerror=${forrest.validate.failonerror}
#
#forrest.validate.skins.stylesheets.includes=**/*.xsl
#forrest.validate.skins.stylesheets.excludes=
#forrest.validate.skins.stylesheets.failonerror=${forrest.validate.skins.failonerror}
|
|
From: <rga...@us...> - 2003-01-01 23:48:41
|
Update of /cvsroot/csms/csms-core/src/documentation/content
In directory sc8-pr-cvs1:/tmp/cvs-serv26665
Added Files:
index.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: index.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "./dtd/document-v11.dtd">
<document>
<header>
<title>Community Sports Management System</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..."/>
</authors>
</header>
<body>
<section>
<title>Introduction</title>
<p>The <strong>Community Sports Management System</strong>
sports league management system allowing the creation of leagues and
the management of teams and players within those leagues together with
all the stats generated in games. The core system is sport agnostic
and is extended to support individual sports with the add on of sport
modules. We aim to support as many sports as possible, both real and
fantasy. The software also provides mechanisms for supporting online
communities based around each sport, league and team.</p>
<section>
<title>Our Mission</title>
<p>The Community Sports Management System project aims to facilitate the
online management of sporting seasons, bringing together its
participants and encouraging collaboration between like-minded groups.<br/>
In doing this we aim to promote the growth and development of sports
clubs of all types and encourage the participation of all people whether
they be players, organisers or supporters.</p>
</section>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:48:27
|
Update of /cvsroot/csms/csms-core/src/documentation/content/downloadAndInstall
In directory sc8-pr-cvs1:/tmp/cvs-serv26622
Added Files:
index.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: index.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"./dtd/document-v11.dtd">
<document>
<header>
<title>CSMS - Download and Install</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
</authors>
</header>
<body>
<section>
<title>Downloading Released Versions</title>
<p>To run the CSMS software you need to have installed and correctly
configured the following software:</p>
<ul>
<li>
<link href="http://www.javasfot.com/download">Java 2 Standard
Edition</link>
version 1.4 or higher</li>
</ul>
<p>You can download the latest CSMS released files from
<link
href="http://sourceforge.net/project/showfiles.php?group_id=65029">
Sourceforge</link>
.</p>
<section>
<title>Installing the latest release</title>
<p>To install the application simply unpack the archive to your chosen
directory.</p>
</section>
<section>
<title>Running the latest release</title>
<p>To run the application cd into the bin directory which is located
inside the directory you unzipped the archive to and run the command:
<br />
<code>csms</code>
.</p>
</section>
</section>
<section>
<title>Downloading Source Code Versions</title>
<p>To build and run the CSMS software from source code you need to have
installed and correctly configured the following software:</p>
<ul>
<li>
<link href="http://www.javasoft.com/download">Java 2 Standard
Edition</link>
version 1.4 or higher</li>
<li>A build tool. Here you have two options:</li>
<ul>
<li><link href="http://www.krysalis.org/centipede">Centipede</link> gives access
to all build tools including javadocs, cross-referenced java source code, unit
testing, code style checks, metrics reporting and much more. This is the one you
want if you intend to work on the source code. ( you need version 1.0beta3 or greater - note that at the time of writing 1.0beta3 has not yet been released, this means you need CVS head of Centipede)</li>
<li><link href="http://jakarta.apache.org">ANT</link> build tool will provide minimal
build facilities, just enough to get you going. We suport ANT because many prospective developers
alerady have it installed and so our support of it makes it easy for you to experiment. However, for
full development work we recomend you move to Centipede (which is built ontop of ANT
and so you will bring all your existing knowledge with you).</li>
</ul>
</ul>
<p>You can get the latest cutting edge version from
<link href="http://sourceforge.net/cvs/?group_id=65029">CVS</link>
. If you are going to work with this version we strongly advise that you
join the
<link href="https://sourceforge.net/mail/?group_id=65029">developers
mailing list</link>
to keep abreast of work on the codebase.</p>
<p>You can also download archives of the source code for each release from
<link
href="http://sourceforge.net/project/showfiles.php?group_id=65029">
Sourceforge</link></p>
<section>
<title>Building from Source</title>
<p>We support two build systems, <link href="http://jakarta.apache.org/ant">ANT</link> and
<link href="http://www.krysalis.org/centipede">Centipede</link>. Ant is well known
and used by the majority of java projects (and many others). Centipede builds on top of
Ant. The build facilities in our Ant build file are minimal, but they provide quick
and easy access to the major requriements of compiling and running the application. For
more build targets (including metrics, site generation, documentation, unit tests and
much more you need to use Centipede).</p>
<section>
<title>Centipede</title>
<p>There is an interactive build system within CSMS so to get started
simply run the command
<br />
<code>cent</code><br/> from within the projects root directory
</p>
<p>For full details of the facilities available in Centipede please consult the
<link href="http://www.krysalis.org/centipede">Centipede</link> documentation.</p>
</section>
<section>
<title>Ant</title>
<p>A simple compile target has been provider for the convenience of ANT users.
Simply type the command <code>ant</code><br/> from within the projects root directory</p>
</section>
</section>
<section>
<title>Running a built system</title>
<p>There are many ways of running the application once built from CVS,
however, the easiest is to simply run the command
<br />
<code>ant run</code><br/>
We use Ant here, as it is much faster than Centipede for such a simple task, however, you can
also use the command <code>cent run</code> is you so desire.
</p>
</section>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:48:13
|
Update of /cvsroot/csms/csms-core/src/documentation/content/manual
In directory sc8-pr-cvs1:/tmp/cvs-serv26556
Added Files:
index.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: index.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>CSMS - Manual</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
</authors>
</header>
<body>
<section>
<title>Community Sports Management System - Manual Contents</title>
<note>Documentation has not yet been moved over from our Wiki site, you can
view what there is
<link href="http://www.fanfoot.com/wiki/Wiki.jsp?page=AutomatedScoring">
over there</link>.</note>
<ol>
<li><link href="configuration.html">Configuration</link> - How to configure the application</li>
</ol>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:48:01
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs In directory sc8-pr-cvs1:/tmp/cvs-serv26501 Removed Files: index.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- index.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:47:48
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/manual In directory sc8-pr-cvs1:/tmp/cvs-serv26461 Removed Files: index.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- index.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:47:35
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall In directory sc8-pr-cvs1:/tmp/cvs-serv26407 Removed Files: index.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- index.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:47:23
|
Update of /cvsroot/csms/csms-core/src/documentation/content
In directory sc8-pr-cvs1:/tmp/cvs-serv26312
Added Files:
license.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: license.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"./dtd/document-v11.dtd">
<document>
<header>
<title>Mozilla Public License version 1.1</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
</authors>
</header>
<body>
<section>
<title>1. Definitions.</title>
<dl>
<dt>1.0.1. "Commercial Use"</dt>
<dd>>means distribution or otherwise making the Covered Code
available to a third party.</dd>
<dt>1.1. "Contributor"</dt>
<dd>means each entity that creates or contributes to the creation of
Modifications.</dd>
<dt>1.2. "Contributor Version"</dt>
<dd>means the combination of the Original Code, prior Modifications used
by a Contributor, and the Modifications made by that particular
Contributor.</dd>
<dt>1.3. "Covered Code"</dt>
<dd>means the Original Code or Modifications or the combination of the
Original Code and Modifications, in each case including portions
thereof.</dd>
<dt>1.4. "Electronic Distribution Mechanism"</dt>
<dd>means a mechanism generally accepted in the software development
community for the electronic transfer of data.</dd>
<dt>1.5. "Executable"</dt>
<dd>means Covered Code in any form other than Source Code.</dd>
<dt>1.6. "Initial Developer"</dt>
<dd>means the individual or entity identified as the Initial Developer
in the Source Code notice required by
<em>Exhibit A</em>
.</dd>
<dt>1.7. "Larger Work"</dt>
<dd>means a work which combines Covered Code or portions thereof with
code not governed by the terms of this License.</dd>
<dt>1.8. "License"</dt>
<dd>means this document.</dd>
<dt>1.8.1. "Licensable"</dt>
<dd>means having the right to grant, to the maximum extent possible,
whether at the time of the initial grant or subsequently acquired, any
and all of the rights conveyed herein.</dd>
<dt>1.9. "Modifications"</dt>
<dd>means any addition to or deletion from the substance or structure of
either the Original Code or any previous Modifications. When Covered
Code is released as a series of files, a Modification is:
<br />
<em>A.</em>
<br />
Any addition to or deletion from the contents of a file containing
Original Code or previous Modifications.
<br />
<em>B.</em>
<br />
Any new file that contains any part of the Original Code or previous
Modifications.
<br />
</dd>
<dt>1.10. "Original Code"</dt>
<dd>means Source Code of computer software code which is described in
the Source Code notice required by
<em>Exhibit A</em>
as Original Code, and which, at the time of its release under this
License is not already Covered Code governed by this License.</dd>
<dt>1.10.1. "Patent Claims"</dt>
<dd>means any patent claim(s), now owned or hereafter acquired,
including without limitation, method, process, and apparatus claims, in
any patent Licensable by grantor.</dd>
<dt>1.11. "Source Code"</dt>
<dd>means the preferred form of the Covered Code for making
modifications to it, including all modules it contains, plus any
associated interface definition files, scripts used to control
compilation and installation of an Executable, or source code
differential comparisons against either the Original Code or another
well known, available Covered Code of the Contributor's choice. The
Source Code can be in a compressed or archival form, provided the
appropriate decompression or de-archiving software is widely available
for no charge.</dd>
<dt>1.12. "You" (or "Your")</dt>
<dd>means an individual or a legal entity exercising rights under, and
complying with all of the terms of, this License or a future version of
this License issued under Section 6.1. For legal entities, "You"
includes any entity which controls, is controlled by, or is under common
control with You. For purposes of this definition, "control" means (a)
the power, direct or indirect, to cause the direction or management of
such entity, whether by contract or otherwise, or (b) ownership of more
than fifty percent (50%) of the outstanding shares or beneficial
ownership of such entity.</dd>
</dl>
</section>
<section>
<title>2. Source Code License.</title>
<section>
<title>2.1. The Initial Developer Grant.</title>
<p>The Initial Developer hereby grants You a world-wide, royalty-free,
non-exclusive license, subject to third party intellectual property
claims:</p>
<ul>
<li>(a) under intellectual property rights (other than patent or
trademark) Licensable by Initial Developer to use, reproduce,
modify, display, perform, sublicense and distribute the Original
Code (or portions thereof) with or without Modifications, and/or as
part of a Larger Work;</li>
<li>(b) under Patents Claims infringed by the making, using or
selling of Original Code, to make, have made, use, practice, sell,
and offer for sale, and/or otherwise dispose of the Original Code
(or portions thereof).</li>
<li>(c) the licenses granted in this Section 2.1(a) and (b) are
effective on the date Initial Developer first distributes Original
Code under the terms of this License.</li>
<li>(d) Notwithstanding Section 2.1(b) above, no patent license is
granted: 1) for code that You delete from the Original Code; 2)
separate from the Original Code; or 3) for infringements caused by:
i) the modification of the Original Code or ii) the combination of
the Original Code with other software or devices.</li>
</ul>
</section>
<section>
<title>2.2. Contributor Grant.</title>
<p>Subject to third party intellectual property claims, each
Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license</p>
<ul>
<li>(a) under intellectual property rights (other than patent or
trademark) Licensable by Contributor, to use, reproduce, modify,
display, perform, sublicense and distribute the Modifications
created by such Contributor (or portions thereof) either on an
unmodified basis, with other Modifications, as Covered Code and/or
as part of a Larger Work;</li>
<li>(b) under Patent Claims infringed by the making, using, or
selling of Modifications made by that Contributor either alone
and/or in combination with its Contributor Version (or portions of
such combination), to make, use, sell, offer for sale, have made,
and/or otherwise dispose of: 1) Modifications made by that
Contributor (or portions thereof); and 2) the combination of
Modifications made by that Contributor with its Contributor Version
(or portions of such combination).</li>
<li>(c) the licenses granted in Sections 2.2(a) and 2.2(b) are
effective on the date Contributor first makes Commercial Use of the
Covered Code.</li>
<li>(d) Notwithstanding Section 2.2(b) above, no patent license is
granted: 1) for any code that Contributor has deleted from the
Contributor Version; 2) separate from the Contributor Version; 3)
for infringements caused by: i) third party modifications of
Contributor Version or ii) the combination of Modifications made by
that Contributor with other software (except as part of the
Contributor Version) or other devices; or 4) under Patent Claims
infringed by Covered Code in the absence of Modifications made by
that Contributor.</li>
</ul>
</section>
</section>
<section>
<title>3. Distribution Obligations.</title>
<section>
<title>3.1. Application of License.</title>
<p>The Modifications which You create or to which You contribute are
governed by the terms of this License, including without limitation
Section
<em>2.2</em>
. The Source Code version of Covered Code may be distributed only
under the terms of this License or a future version of this License
released under Section
<em>6.1</em>
, and You must include a copy of this License with every copy of the
Source Code You distribute. You may not offer or impose any terms on
any Source Code version that alters or restricts the applicable
version of this License or the recipients' rights hereunder. However,
You may include an additional document offering the additional rights
described in Section
<em>3.5</em>
.</p>
</section>
<section>
<title>3.2. Availability of Source Code.</title>
<p>Any Modification which You create or to which You contribute must
be made available in Source Code form under the terms of this License
either on the same media as an Executable version or via an accepted
Electronic Distribution Mechanism to anyone to whom you made an
Executable version available; and if made available via Electronic
Distribution Mechanism, must remain available for at least twelve (12)
months after the date it initially became available, or at least six
(6) months after a subsequent version of that particular Modification
has been made available to such recipients. You are responsible for
ensuring that the Source Code version remains available even if the
Electronic Distribution Mechanism is maintained by a third party.</p>
</section>
<section>
<title>3.3. Description of Modifications.</title>
<p>You must cause all Covered Code to which You contribute to contain
a file documenting the changes You made to create that Covered Code
and the date of any change. You must include a prominent statement
that the Modification is derived, directly or indirectly, from
Original Code provided by the Initial Developer and including the name
of the Initial Developer in (a) the Source Code, and (b) in any notice
in an Executable version or related documentation in which You
describe the origin or ownership of the Covered Code.</p>
</section>
<section>
<title>3.4. Intellectual Property Matters</title>
<dl>
<dt>(a) Third Party Claims</dt>
<dd>If Contributor has knowledge that a license under a third
party's intellectual property rights is required to exercise the
rights granted by such Contributor under Sections 2.1 or 2.2,
Contributor must include a text file with the Source Code
distribution titled "LEGAL" which describes the claim and the party
making the claim in sufficient detail that a recipient will know
whom to contact. If Contributor obtains such knowledge after the
Modification is made available as described in Section 3.2,
Contributor shall promptly modify the LEGAL file in all copies
Contributor makes available thereafter and shall take other steps
(such as notifying appropriate mailing lists or newsgroups)
reasonably calculated to inform those who received the Covered Code
that new knowledge has been obtained.</dd>
<dt>(b) Contributor APIs</dt>
<dd>If Contributor's Modifications include an application
programming interface and Contributor has knowledge of patent
licenses which are reasonably necessary to implement that API,
Contributor must also include this information in the LEGAL
file.</dd>
<dt>(c) Representations.</dt>
<dd>Contributor represents that, except as disclosed pursuant to
Section 3.4(a) above, Contributor believes that Contributor's
Modifications are Contributor's original creation(s) and/or
Contributor has sufficient rights to grant the rights conveyed by
this License.</dd>
</dl>
</section>
<section>
<title>3.5. Required Notices.</title>
<p>You must duplicate the notice in
<em>Exhibit A</em>
in each file of the Source Code. If it is not possible to put such
notice in a particular Source Code file due to its structure, then You
must include such notice in a location (such as a relevant directory)
where a user would be likely to look for such a notice. If You created
one or more Modification(s) You may add your name as a Contributor to
the notice described in
<em>Exhibit A</em>
. You must also duplicate this License in any documentation for the
Source Code where You describe recipients' rights or ownership rights
relating to Covered Code. You may choose to offer, and to charge a fee
for, warranty, support, indemnity or liability obligations to one or
more recipients of Covered Code. However, You may do so only on Your
own behalf, and not on behalf of the Initial Developer or any
Contributor. You must make it absolutely clear than any such warranty,
support, indemnity or liability obligation is offered by You alone,
and You hereby agree to indemnify the Initial Developer and every
Contributor for any liability incurred by the Initial Developer or
such Contributor as a result of warranty, support, indemnity or
liability terms You offer.</p>
</section>
<section>
<title>3.6. Distribution of Executable Versions.</title>
<p>You may distribute Covered Code in Executable form only if the
requirements of Section
<em>3.1-3.5</em>
have been met for that Covered Code, and if You include a notice
stating that the Source Code version of the Covered Code is available
under the terms of this License, including a description of how and
where You have fulfilled the obligations of Section
<em>3.2</em>
. The notice must be conspicuously included in any notice in an
Executable version, related documentation or collateral in which You
describe recipients' rights relating to the Covered Code. You may
distribute the Executable version of Covered Code or ownership rights
under a license of Your choice, which may contain terms different from
this License, provided that You are in compliance with the terms of
this License and that the license for the Executable version does not
attempt to limit or alter the recipient's rights in the Source Code
version from the rights set forth in this License. If You distribute
the Executable version under a different license You must make it
absolutely clear that any terms which differ from this License are
offered by You alone, not by the Initial Developer or any Contributor.
You hereby agree to indemnify the Initial Developer and every
Contributor for any liability incurred by the Initial Developer or
such Contributor as a result of any such terms You offer.</p>
</section>
<section>
<title>3.7. Larger Works.</title>
<p>You may create a Larger Work by combining Covered Code with other
code not governed by the terms of this License and distribute the
Larger Work as a single product. In such a case, You must make sure
the requirements of this License are fulfilled for the Covered
Code.</p>
</section>
</section>
<section>
<title>4. Inability to Comply Due to Statute or Regulation.</title>
<p>If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Code due to statute,
judicial order, or regulation then You must: (a) comply with the terms
of this License to the maximum extent possible; and (b) describe the
limitations and the code they affect. Such description must be included
in the LEGAL file described in Section
<em>3.4</em>
and must be included with all distributions of the Source Code. Except
to the extent prohibited by statute or regulation, such description must
be sufficiently detailed for a recipient of ordinary skill to be able to
understand it.</p>
</section>
<section>
<title>5. Application of this License.</title>
<p>This License applies to code to which the Initial Developer has
attached the notice in
<em>Exhibit A</em>
and to related Covered Code.</p>
</section>
<section>
<title>6. Versions of the License.</title>
<section>
<title>6.1. New Versions</title>
<p>Netscape Communications Corporation ("Netscape") may publish
revised and/or new versions of the License from time to time. Each
version will be given a distinguishing version number.</p>
</section>
<section>
<title>6.2. Effect of New Versions</title>
<p>Once Covered Code has been published under a particular version of
the License, You may always continue to use it under the terms of that
version. You may also choose to use such Covered Code under the terms
of any subsequent version of the License published by Netscape. No one
other than Netscape has the right to modify the terms applicable to
Covered Code created under this License.</p>
</section>
<section>
<title>6.3. Derivative Works</title>
<p>If You create or use a modified version of this License (which you
may only do in order to apply it to code which is not already Covered
Code governed by this License), You must (a) rename Your license so
that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL",
"NPL" or any confusingly similar phrase do not appear in your license
(except to note that your license differs from this License) and (b)
otherwise make it clear that Your version of the license contains
terms which differ from the Mozilla Public License and Netscape Public
License. (Filling in the name of the Initial Developer, Original Code
or Contributor in the notice described in
<em>Exhibit A</em>
shall not of themselves be deemed to be modifications of this
License.)</p>
</section>
</section>
<section>
<title>7. DISCLAIMER OF WARRANTY.</title>
<p>COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS,
MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU.
SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY
NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY
CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED
CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.</p>
</section>
<section>
<title>8. TERMINATION.</title>
<section>
<title>8.1.</title>
<p>This License and the rights granted hereunder will terminate
automatically if You fail to comply with terms herein and fail to cure
such breach within 30 days of becoming aware of the breach. All
sublicenses to the Covered Code which are properly granted shall
survive any termination of this License. Provisions which, by their
nature, must remain in effect beyond the termination of this License
shall survive.</p>
</section>
<section>
<title>8.2.</title>
<p>If You initiate litigation by asserting a patent infringement claim
(excluding declatory judgment actions) against Initial Developer or a
Contributor (the Initial Developer or Contributor against whom You
file such action is referred to as "Participant") alleging that:</p>
<dl>
<dt>(a)</dt>
<dd>such Participant's Contributor Version directly or indirectly
infringes any patent, then any and all rights granted by such
Participant to You under Sections 2.1 and/or 2.2 of this License
shall, upon 60 days notice from Participant terminate prospectively,
unless if within 60 days after receipt of notice You either: (i)
agree in writing to pay Participant a mutually agreeable reasonable
royalty for Your past and future use of Modifications made by such
Participant, or (ii) withdraw Your litigation claim with respect to
the Contributor Version against such Participant. If within 60 days
of notice, a reasonable royalty and payment arrangement are not
mutually agreed upon in writing by the parties or the litigation
claim is not withdrawn, the rights granted by Participant to You
under Sections 2.1 and/or 2.2 automatically terminate at the
expiration of the 60 day notice period specified above.</dd>
<dt>(b)</dt>
<dd>any software, hardware, or device, other than such Participant's
Contributor Version, directly or indirectly infringes any patent,
then any rights granted to You by such Participant under Sections
2.1(b) and 2.2(b) are revoked effective as of the date You first
made, used, sold, distributed, or had made, Modifications made by
that Participant.</dd>
</dl>
</section>
<section>
<title>8.3.</title>
<p>If You assert a patent infringement claim against Participant
alleging that such Participant's Contributor Version directly or
indirectly infringes any patent where such claim is resolved (such as
by license or settlement) prior to the initiation of patent
infringement litigation, then the reasonable value of the licenses
granted by such Participant under Sections 2.1 or 2.2 shall be taken
into account in determining the amount or value of any payment or
license.</p>
</section>
<section>
<title>8.4.</title>
<p>In the event of termination under Sections 8.1 or 8.2 above, all
end user license agreements (excluding distributors and resellers)
which have been validly granted by You or any distributor hereunder
prior to termination shall survive termination.</p>
</section>
</section>
<section>
<title>9. LIMITATION OF LIABILITY.</title>
<p>UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR
ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY
INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER
INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION
AND LIMITATION MAY NOT APPLY TO YOU.</p>
</section>
<section>
<title>10. U.S. GOVERNMENT END USERS.</title>
<p>The Covered Code is a "commercial item," as that term is defined in
48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
software" and "commercial computer software documentation," as such
terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
all U.S. Government End Users acquire Covered Code with only those
rights set forth herein.</p>
</section>
<section>
<title>11. MISCELLANEOUS.</title>
<p>This License represents the complete agreement concerning subject
matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent
necessary to make it enforceable. This License shall be governed by
California law provisions (except to the extent applicable law, if any,
provides otherwise), excluding its conflict-of-law provisions. With
respect to disputes in which at least one party is a citizen of, or an
entity chartered or registered to do business in the United States of
America, any litigation relating to this License shall be subject to the
jurisdiction of the Federal Courts of the Northern District of
California, with venue lying in Santa Clara County, California, with the
losing party responsible for costs, including without limitation, court
costs and reasonable attorneys' fees and expenses. The application of
the United Nations Convention on Contracts for the International Sale of
Goods is expressly excluded. Any law or regulation which provides that
the language of a contract shall be construed against the drafter shall
not apply to this License.</p>
</section>
<section>
<title>12. RESPONSIBILITY FOR CLAIMS.</title>
<p>As between Initial Developer and the Contributors, each party is
responsible for claims and damages arising, directly or indirectly, out
of its utilization of rights under this License and You agree to work
with Initial Developer and Contributors to distribute such
responsibility on an equitable basis. Nothing herein is intended or
shall be deemed to constitute any admission of liability.</p>
</section>
<section>
<title>13. MULTIPLE-LICENSED CODE.</title>
<p>Initial Developer may designate portions of the Covered Code as
âMultiple-Licensedâ. âMultiple-Licensedâ means that the Initial
Developer permits you to utilize portions of the Covered Code under Your
choice of the MPL or the alternative licenses, if any, specified by the
Initial Developer in the file described in Exhibit A.</p>
</section>
<section>
<title>EXHIBIT A -Mozilla Public License.</title>
<p>``The contents of this file are subject to the Mozilla Public License
Version 1.1 (the "License"); you may not use this file except in
compliance with the License. You may obtain a copy of the License at
http://www.mozilla.org/MPL/</p>
<p>Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific language governing rights and limitations under
the License.</p>
<p>The Original Code is Community Sports Management System.</p>
<p>The Initial Developer of the Original Code is We know What you
Want.net Portions created by The Initial Developer are Copyright (C)
2002 All Rights Reserved.</p>
<p>Contributor(s):</p>
<ul>
<li>Ross Gardler - ross [at] saafe.org</li>
<li>Mike Lever - mikel [at] fanfoot.com</li>
<li>Stuart Gardler - stuart [at] wkwyw.net</li>
</ul>
<p>[NOTE: The text of this Exhibit A may differ slightly from the text
of the notices in the Source Code files of the Original Code. You should
use the text of this Exhbit A rather than the text found in the Original
Code Source Code for Your Modifications.]</p>
</section>
</body>
</document>
|
|
From: <rga...@us...> - 2003-01-01 23:47:02
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs In directory sc8-pr-cvs1:/tmp/cvs-serv26247 Removed Files: license.xml Log Message: Moving documentation and adding support for Forrest 0.2 --- license.xml DELETED --- |
|
From: <rga...@us...> - 2003-01-01 23:46:50
|
Update of /cvsroot/csms/csms-core/src/documentation/content
In directory sc8-pr-cvs1:/tmp/cvs-serv26166
Added Files:
longTermPlans.xml
Log Message:
Moving documentation and adding support for Forrest 0.2
--- NEW FILE: longTermPlans.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "./dtd/document-v11.dtd">
<document>
<header>
<title>Community Sports Management System - Long Term Objectives</title>
<authors>
<person id="rdg" name="Ross D. Gardler" email="ro...@sa..."/>
</authors>
</header>
<body>
<section>
<title>CSCM Long Term Objectives</title>
<note>This document is intended to give an indication of where we intend to go with
the CSMS project and its deliverables. The document is in a constant state of change and
we welcome comments or feature requests via either our <link href="http://lists.sourceforge.net/lists/listinfo/csms-developer">developers mailing list</link> or our
<link href="https://sourceforge.net/tracker/?atid=509511&group_id=65029&func=browse">
feature request tracker</link>.</note>
<p>The Community Sports Management System project aims to facilitate the
online management of sporting seasons, bringing together its
participants and encouraging collaboration between like-minded groups.<br/>
In doing this we aim to promote the growth and development of sports
clubs of all types and encourage the participation of all people whether
they be players, organisers or supporters.</p>
<p>In order to do this we will provide a software system for the management
of sports leagues, teams, players and supporters. Furthermore, we will
provide a method for connecting these groups together. Our focus is not
a particular sport, geographical area or type of participant, it is with
the commonalities between these groups.</p>
<p>It is expected that the needs of specific groups, such as football
leagues, hockey tournaments, baseball fans or FooBar Town Peewee Team,
will be addressed by specific extension modules. The core system within
the CSMS project will provide the framework on which these more specific
systems will will be built. The framework will also provide the means
for sharing data and communicating between these specific groups.</p>
<p>In addition to the core systems the CSMS project will house a number of
sport specific modules. In order to use the Sports Management facilities
of CSMS it will be necessary to install at least one of these sports
modules.</p>
<p>The core systems provided within the CSMS project will consist of the
following facilities:</p>
<ul>
<li>Competition management</li>
<li>Team Management</li>
<li>Player Management</li>
<li>Supporter Management</li>
<li>Community Management</li>
</ul>
<section>
<title>Competition Management</title>
<p>Sport is all about competition. This section aims to assist in the management and coordination
of teams that compete against one another. It includes:</p>
<ul>
<li>Teams in competition</li>
<li>Fixtures</li>
<li>Game results</li>
<li>Competition standings</li>
<li>Competition statistics</li>
<li>Fees management</li>
<li>Competition news</li>
</ul>
<p>Of course there are many different types of competition, here are some of the ones we have thought
about supporting. If there are others you would like to see then
<link href="https://sourceforge.net/tracker/?atid=509511&group_id=65029&func=browse">tell us</link>.</p>
<ul>
<li>League Management</li>
<li>Knockout Competition Management</li>
</ul>
</section>
<section>
<title>Team Management</title>
<p>Teams need to be managed, here are some of the features we intend to include (eventually)</p>
<ul>
<li>Players in team</li>
<li>Team profile/history</li>
<li>Non playing staff</li>
<li>Financial Management</li>
<li>Team statistics</li>
<li>Team news</li>
</ul>
</section>
<section>
<title>Player Management</title>
<ul>
<li>Player profile/history</li>
<li>Statistics</li>
<li>News</li>
</ul>
</section>
<section>
<title>Supporter Management</title>
<p>Even the pub darts team has it's supporters, those people who are interested in
results but don;t play in the games. We mustn't forget them, so we aim to include the
following facilities.</p>
<ul>
<li>Supporter profile</li>
<li>Contact preferences</li>
<li>News management</li>
<li>Mailing lists</li>
</ul>
</section>
</section>
</body>
</document>
|
