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...> - 2002-10-31 21:11:33
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/gui
In directory usw-pr-cvs1:/tmp/cvs-serv12454
Modified Files:
ControlCentre.java
Log Message:
Fixed bug preventing local files being loaded into the browser on windows (bug #630866)
Index: ControlCentre.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/gui/ControlCentre.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** ControlCentre.java 29 Oct 2002 14:54:21 -0000 1.6
--- ControlCentre.java 31 Oct 2002 21:11:25 -0000 1.7
***************
*** 291,295 ****
*/
private void mnuitemParseURLActionPerformed(java.awt.event.ActionEvent evt) {
- //GEN-FIRST:event_mnuitemParseURLActionPerformed
getURL dialog = new getURL(this, true, strDefaultURLs);
URL url = dialog.getURL();
--- 291,294 ----
***************
*** 298,303 ****
- //GEN-LAST:event_mnuitemParseURLActionPerformed
-
/**
* Set Prefs configuration item is selected
--- 297,300 ----
***************
*** 306,310 ****
*/
private void setPrefsActionPerformed(java.awt.event.ActionEvent evt) {
- //GEN-FIRST:event_setPrefsActionPerformed
try {
PreferencesEditor dlgPrefsEditor = new PreferencesEditor(this,
--- 303,306 ----
***************
*** 318,322 ****
- //GEN-LAST:event_setPrefsActionPerformed
/**
--- 314,317 ----
***************
*** 326,330 ****
*/
private void parseBBCTExt1ActionPerformed(java.awt.event.ActionEvent evt) {
- //GEN-FIRST:event_parseBBCTExt1ActionPerformed
URL url = null;
try {
--- 321,324 ----
***************
*** 340,344 ****
- //GEN-LAST:event_parseBBCTExt1ActionPerformed
/**
--- 334,337 ----
***************
*** 369,375 ****
try {
! generateScores(file.toURL());
} catch(java.net.MalformedURLException mue) {
! logger.warning("File path does not translate to a valid URL");
// FIXME: Warn the user of this error
}
--- 362,368 ----
try {
! generateScores(new URL("file://" + file.toString()));
} catch(java.net.MalformedURLException mue) {
! logger.warning("File path does not translate to a valid URL: " + file.toString());
// FIXME: Warn the user of this error
}
|
|
From: <rga...@us...> - 2002-10-31 21:11:17
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv12304
Modified Files:
status.xml
Log Message:
Fixed bug preventing local files being loaded into the browser on windows (bug #630866)
Index: status.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/status.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** status.xml 31 Oct 2002 18:41:58 -0000 1.6
--- status.xml 31 Oct 2002 21:11:04 -0000 1.7
***************
*** 27,30 ****
--- 27,33 ----
the creation of a web based interface to the system. The first part of which
is the Auot Scoring facilites found inthe previous release.</description>
+ <action dev="rdg" type="bugfix" id="630866">
+ Fixed bug preventing local files being loaded into the browser on Windows.
+ </action>
<action dev="rdg" type="add">
Added basic ANT support. For compile and run targets Ant is much faster because
|
|
From: <rga...@us...> - 2002-10-31 19:36:07
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv8513
Modified Files:
book.xml
Added Files:
longTermPlans.xml
Log Message:
Adding long term plans document
--- 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>
<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>
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/book.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** book.xml 28 Oct 2002 18:11:25 -0000 1.7
--- book.xml 31 Oct 2002 19:36:04 -0000 1.8
***************
*** 11,14 ****
--- 11,15 ----
<menu-item label="License" href="license.html"/>
<menu-item label="Constitution" href="constitution.html"/>
+ <menu-item label="Long Term Plans" href="longTermPlans.html"/>
</menu>
|
|
From: <rga...@us...> - 2002-10-31 19:03:29
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv25745
Modified Files:
index.xml
Log Message:
Updated the mission statement to that proposed by leverm
Index: index.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/index.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** index.xml 22 Oct 2002 17:24:45 -0000 1.5
--- index.xml 31 Oct 2002 19:03:25 -0000 1.6
***************
*** 23,31 ****
<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>
--- 23,33 ----
<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>
|
|
From: <rga...@us...> - 2002-10-31 18:43:00
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv14281
Modified Files:
build.xml
Log Message:
Added a big comment telling people not to add funtionality to this script, but to put it in centibuild.xml
Index: build.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/build.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** build.xml 31 Oct 2002 18:30:23 -0000 1.1
--- build.xml 31 Oct 2002 18:42:55 -0000 1.2
***************
*** 1,8 ****
<?xml version="1.0"?>
<project default="compile" basedir="." name="project build file">
<description>* ===================================== * | CSMS
Build System | * ===================================== * The basic
build targets for those without centipede, for a more complete build
! system please use the command 'cent' to run the Centipede build system</description>
--- 1,24 ----
<?xml version="1.0"?>
<project default="compile" basedir="." name="project build file">
+
+ <!--
+ ========================================================================
+ IMPORTANT
+ ========================================================================
+
+ This is *not* the main build file. We use Centipede as the main build system.
+ This minimal Ant script is provided in order to have faster build and run targets.
+ Additions to the main build system should be made in centibuild.xml not here.
+
+
+ ========================================================================
+ IMPORTANT
+ ========================================================================
+ -->
+
<description>* ===================================== * | CSMS
Build System | * ===================================== * The basic
build targets for those without centipede, for a more complete build
! system please use the command 'cent' to run the Centipede build system.</description>
|
|
From: <rga...@us...> - 2002-10-31 18:42:02
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv13547
Modified Files:
status.xml
Log Message:
Added a couple of todos and actions
Index: status.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/status.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** status.xml 29 Oct 2002 18:44:29 -0000 1.5
--- status.xml 31 Oct 2002 18:41:58 -0000 1.6
***************
*** 12,17 ****
<todo>
<actions priority="high">
! <action context="docs" assigned-to="all">
! Test, test, test :-)
</action>
</actions>
--- 12,20 ----
<todo>
<actions priority="high">
! <action context="design" assigned-to="all">
! Design the data structures for team management in the core system.
! </action>
! <action context="code" assigned-to="all">
! Make the 0.1.1alpha release accessible as a Cocoon web app.
</action>
</actions>
***************
*** 20,24 ****
<changes>
<release version="" date="">
! <description></description>
</release>
<release version="0.1.1alpha1" date="29 October 2002">
--- 23,35 ----
<changes>
<release version="" date="">
! <description>This is release moves the prior 0.1.1alpha release to
! a Cocoon application rather than a standalone application. This enable
! the creation of a web based interface to the system. The first part of which
! is the Auot Scoring facilites found inthe previous release.</description>
! <action dev="rdg" type="add">
! Added basic ANT support. For compile and run targets Ant is much faster because
! it does not have the overhead that comes with starting Centipede. However, Centipede
! remains as the main build tool.
! </action>
</release>
<release version="0.1.1alpha1" date="29 October 2002">
|
|
From: <rga...@us...> - 2002-10-31 18:30:38
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv6296
Added Files:
build.xml
Log Message:
Added basic ANT support
--- NEW FILE: build.xml ---
<?xml version="1.0"?>
<project default="compile" basedir="." name="project build file">
<description>* ===================================== * | CSMS
Build System | * ===================================== * The basic
build targets for those without centipede, for a more complete build
system please use the command 'cent' to run the Centipede build system</description>
<!--
Give user a chance to override without editing this file
(and without typing -D each time he compiles it)
-->
<property file=".ant.properties"/>
<property file="${user.home}/.ant.properties"/>
<!-- fixed project dirs -->
<property name="build.dir" value="./build"/>
<property name="work.dir" value="${build.dir}/work"/>
<property name="temp.dir" value="${work.dir}/temp"/>
<property name="src.dir" value="./src"/>
<property name="lib.dir" value="./lib"/>
<target name="compile" description="Compile all files">
<mkdir dir="${build.dir}"/>
<mkdir dir="${work.dir}"/>
<mkdir dir="${temp.dir}"/>
<property name="project.name" value="csms-core"/>
<property name="project.build.dir" value="${build.dir}/${project.name}" />
<property name="project.work.dir" value="${build.dir}/${project.name}/work" />
<property name="project.src.dir" value="${src.dir}/java" />
<echo>
--------------------------------------------------------------
Using ${ant.version}
Build file ${ant.file}
Project Name ${ant.project.name}
--------------------------------------------------------------
</echo>
<mkdir dir="${project.build.dir}/classes"/>
<javac srcdir= "${project.src.dir}"
destdir= "${project.build.dir}/classes">
<classpath>
<fileset dir="${lib.dir}">
<include name="**/*.jar"/>
</fileset>
</classpath>
</javac>
<!-- copy all the things that are not classes to the classes dir -->
<copy todir="${project.build.dir}/classes" filtering="off">
<fileset dir="${project.src.dir}">
<patternset>
<exclude name="**/*.java"/>
</patternset>
</fileset>
</copy>
</target>
<target name="run" description="Run the CSMS core system" depends="compile">
<java classname="org.fanfoot.gui.ControlCentre" fork="yes">
<classpath>
<pathelement path="${project.build.dir}/classes"/>
<fileset dir="${lib.dir}">
<include name="**/*.jar"/>
</fileset>
</classpath>
</java>
</target>
</project>
|
|
From: <rga...@us...> - 2002-10-31 18:30:09
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall
In directory usw-pr-cvs1:/tmp/cvs-serv6011
Modified Files:
index.xml
Log Message:
Added basic ANT support
Index: index.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** index.xml 27 Oct 2002 21:22:30 -0000 1.3
--- index.xml 31 Oct 2002 18:29:58 -0000 1.4
***************
*** 54,60 ****
<section>
! <title>Downloading CVS Versions</title>
! <p>To build and run the CSMS software from CVS you need to have
installed and correctly configured the following software:</p>
--- 54,60 ----
<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>
***************
*** 65,73 ****
version 1.4 or higher</li>
!
! <li>
! <link href="http://www.krysalis.org/centipede">Centipede</link>
!
! build tool (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>
</ul>
--- 65,81 ----
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>
***************
*** 82,105 ****
to keep abreast of work on the codebase.</p>
<section>
! <title>Building from CVS</title>
!
! <p>There is an interactive build system within CSMS so to get started
! simply run the command
! <br />
!
! <code>cent</code>
! </p>
!
! <p>The CSMS project uses the
! <link href="http://www.krysalis.org/centipede">Centipede</link>
! build system. This is a system built on top of
! <link href="http://jakarta.apache.org/ant">ANT.</link>
! For full details of the facilities available please consult the
! <link href="http://www.krysalis.org/centipede">Centipede</link>
! documentation.</p>
</section>
--- 90,128 ----
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>
***************
*** 111,115 ****
<br />
! <code>cent run</code>
</p>
</section>
--- 134,140 ----
<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>
|
|
From: <rga...@us...> - 2002-10-31 18:00:15
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv22725
Modified Files:
module.xml
Log Message:
Updating version number
Index: module.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/module.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** module.xml 29 Oct 2002 18:44:29 -0000 1.6
--- module.xml 31 Oct 2002 18:00:05 -0000 1.7
***************
*** 21,25 ****
<detailed>
! A sports league management systema llowing 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
--- 21,25 ----
<detailed>
! A 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
***************
*** 62,67 ****
<version major="0"
minor="0"
! fix ="1"
! tag="alpha2-dev"/>
<package>org.fanfoot</package>
--- 62,67 ----
<version major="0"
minor="0"
! fix ="2"
! tag="alpha-dev"/>
<package>org.fanfoot</package>
|
|
From: <rga...@us...> - 2002-10-29 22:08:27
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/prefs In directory usw-pr-cvs1:/tmp/cvs-serv8405/prefs Log Message: Directory /cvsroot/csms/csms-core/src/java/org/fanfoot/prefs added to the repository |
|
From: <rga...@us...> - 2002-10-29 18:45:00
|
Update of /cvsroot/csms/csms-core In directory usw-pr-cvs1:/tmp/cvs-serv14418 Modified Files: README.txt Log Message: Minor corrections Index: README.txt =================================================================== RCS file: /cvsroot/csms/csms-core/README.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** README.txt 29 Oct 2002 15:26:18 -0000 1.2 --- README.txt 29 Oct 2002 18:44:58 -0000 1.3 *************** *** 14,21 **** System for fantasy sports games. This software *is not* ready for use in the live calculations as yet since it is in alpha form, that is it is undergoing ! rigourous testing at. When we get to the point that there are no (unreported) automated errors then ! we will adopt the software as the primary score generator in ou ronline fanatasy football game (see http://www.fanfoot.com). At this point we will begin building the league management software. --- 14,23 ---- System for fantasy sports games. This software *is not* ready for use in the live calculations as yet since it is in alpha form, that is it is undergoing ! rigourous testing. It is expected that all errors in this release will be in ! the configuration files rather than in the program code (now there's a bold ! claim!) When we get to the point that there are no (unreported) automated errors then ! we will adopt the software as the primary score generator in our online fanatasy football game (see http://www.fanfoot.com). At this point we will begin building the league management software. |
|
From: <rga...@us...> - 2002-10-29 18:44:32
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv14272
Modified Files:
module.xml status.xml
Log Message:
Moving to the next development version
Index: module.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/module.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** module.xml 29 Oct 2002 15:22:05 -0000 1.5
--- module.xml 29 Oct 2002 18:44:29 -0000 1.6
***************
*** 63,67 ****
minor="0"
fix ="1"
! tag="alpha1"/>
<package>org.fanfoot</package>
--- 63,67 ----
minor="0"
fix ="1"
! tag="alpha2-dev"/>
<package>org.fanfoot</package>
Index: status.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/status.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** status.xml 29 Oct 2002 15:20:41 -0000 1.4
--- status.xml 29 Oct 2002 18:44:29 -0000 1.5
***************
*** 19,23 ****
<changes>
! <release version="0.1alpha1" date="29 October 2002">
<description>Scrapes BBC textual commentaries of Barclaycard Premiership games and
generates scores accordingly. How the events are scraped and how the scores are
--- 19,26 ----
<changes>
! <release version="" date="">
! <description></description>
! </release>
! <release version="0.1.1alpha1" date="29 October 2002">
<description>Scrapes BBC textual commentaries of Barclaycard Premiership games and
generates scores accordingly. How the events are scraped and how the scores are
|
|
From: <rga...@us...> - 2002-10-29 18:43:48
|
Update of /cvsroot/csms/csms-core/src/documentation
In directory usw-pr-cvs1:/tmp/cvs-serv13985
Modified Files:
Release-Checklist.txt
Log Message:
Added a little SF specific info
Index: Release-Checklist.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/Release-Checklist.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** Release-Checklist.txt 29 Oct 2002 15:31:34 -0000 1.7
--- Release-Checklist.txt 29 Oct 2002 18:43:45 -0000 1.8
***************
*** 21,32 ****
- correct any failures and start release process again
- - build the distribution
- - cent clean all
-
- - test the distribution
- - Have as many developers as possible test the distribution and vote on the release
- - If there are any negative votes on the release address the issues and start this
- process again from the begining.
-
- update status.xml
- add date to release element
--- 21,24 ----
***************
*** 43,57 ****
- are the download an install instructions up to date
! - tag CVS
! - release_X_Y_Z_fix, where X, Y and Z are version numbers and fix is the fix label
! - create a branch for this release?
- publish web site
- using the command cent deploysite
- update module.xml
- increment version number and set tag to *-dev to indicate this is a development release
! - upload distributions to sourceforge and make releases
- send announcements to ...
--- 35,67 ----
- are the download an install instructions up to date
! - build the distribution
! - cent clean all
!
! - test the distribution
! - Have as many developers as possible test the distribution and vote on the release
! - If there are any negative votes on the release address the issues and start this
! process again from the begining.
- publish web site
- using the command cent deploysite
+
+ - tag CVS
+ - release_X_Y_Z_fix, where X, Y and Z are version numbers and fix is the fix label
+ - create a branch for this release?
- update module.xml
- increment version number and set tag to *-dev to indicate this is a development release
! - upload distributions to sourceforge
! - *.bin.tar.gz
! - *.bin.zip
! - *.src.tar.gz
! - *.src.zip
!
! - Make releases on sourceforge
! - Release description from module.xml is the notes on SF
! - Actions in module.xml are the changes on SF (can be copied with XML tags, as browser will strip them
!
! - Download and verify all distributions
- send announcements to ...
|
|
From: <rga...@us...> - 2002-10-29 15:31:37
|
Update of /cvsroot/csms/csms-core/src/documentation
In directory usw-pr-cvs1:/tmp/cvs-serv15174
Modified Files:
Release-Checklist.txt
Log Message:
Updated ready for the iminent release
Index: Release-Checklist.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/Release-Checklist.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** Release-Checklist.txt 29 Oct 2002 15:29:19 -0000 1.6
--- Release-Checklist.txt 29 Oct 2002 15:31:34 -0000 1.7
***************
*** 43,47 ****
- are the download an install instructions up to date
! - tag CVS (release_X_Y_Z, where X, Y and Z are version numbers)
- create a branch for this release?
--- 43,48 ----
- are the download an install instructions up to date
! - tag CVS
! - release_X_Y_Z_fix, where X, Y and Z are version numbers and fix is the fix label
- create a branch for this release?
|
|
From: <rga...@us...> - 2002-10-29 15:29:22
|
Update of /cvsroot/csms/csms-core/src/documentation
In directory usw-pr-cvs1:/tmp/cvs-serv13916
Modified Files:
Release-Checklist.txt
Log Message:
Updated ready for the iminent release
Index: Release-Checklist.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/Release-Checklist.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** Release-Checklist.txt 29 Oct 2002 15:22:17 -0000 1.5
--- Release-Checklist.txt 29 Oct 2002 15:29:19 -0000 1.6
***************
*** 33,58 ****
- create a new release element
! - update ./module.xml
- set version tag to beta, rc1, rc2 etc.
- check dependencies list is complete
- update the web site docs
! - are the download an install instructions up to date (cross check with README.TXT)
! - cent deploysite
- tag CVS (release_X_Y_Z, where X, Y and Z are version numbers)
- create a branch for this release?
- publish web site
! -cent deploysite
! - update ./module.xml
! - increment version number and set tag to alpha
! - upload distributions to sourceforge
- send announcements to ...
*) csm...@li...
*) ffl mailing lists
- post stories on
--- 33,61 ----
- create a new release element
! - update module.xml
- set version tag to beta, rc1, rc2 etc.
- check dependencies list is complete
- update the web site docs
! - are the download an install instructions up to date
+ - update the README.txt file
+ - are the download an install instructions up to date
+
- tag CVS (release_X_Y_Z, where X, Y and Z are version numbers)
- create a branch for this release?
- publish web site
! - using the command cent deploysite
! - update module.xml
! - increment version number and set tag to *-dev to indicate this is a development release
! - upload distributions to sourceforge and make releases
- send announcements to ...
*) csm...@li...
*) ffl mailing lists
+ *) orf mailing lists
- post stories on
|
|
From: <rga...@us...> - 2002-10-29 15:29:11
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv13800
Modified Files:
properties.xml
Log Message:
Updated ready for the iminent release
Index: properties.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/properties.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** properties.xml 18 Oct 2002 14:52:30 -0000 1.2
--- properties.xml 29 Oct 2002 15:29:08 -0000 1.3
***************
*** 12,44 ****
</checkstyle>
<javasrc version="dev"/>
- <!-- not currently used but working
- <xmldoclet version="latest"/>
- <maven version="latest"/>
- <centipede version="dev">
- example:
- <javadocs group="POIFS org.apache.poi.poifs*,HSSF org.apache.poi.hssf*,HPSF org.apache.poi.hpsf*,">
- <javadocs group="">
- <altenative views="uml">
- <uml prefix="uml-" suffix="" extension="html"/>
- </altenative>
- </javadocs>
- </centipede>
- <automagic version="dev"/>
- <jdepend version="dev"/>
- <umldoclet version="dev"/> -->
<forrest version="dev">
<loglevel>WARN</loglevel>
- builtin available skins:
-
- basic
- jakarta-site
- avalon-site
- scarab-site
- xml-apache-site
- forrest-site (Work In Progress)
-
- You can also use your own skin by putting it in src/documentation/override/skins.
- It will be see by Forrest as any other skin.
-
<skin
name="csms-site">
--- 12,17 ----
|
|
From: <rga...@us...> - 2002-10-29 15:26:21
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv12367
Modified Files:
README.txt
Log Message:
Updated ready for the iminent release
Index: README.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/README.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** README.txt 22 Oct 2002 17:22:15 -0000 1.1
--- README.txt 29 Oct 2002 15:26:18 -0000 1.2
***************
*** 11,15 ****
==================
! This release is our first public release and emobodies an Automated Scoring
System for fantasy sports games. This software *is not* ready for use in the
live calculations as yet since it is in alpha form, that is it is undergoing
--- 11,15 ----
==================
! This release is our first public release and embodies an Automated Scoring
System for fantasy sports games. This software *is not* ready for use in the
live calculations as yet since it is in alpha form, that is it is undergoing
***************
*** 69,74 ****
to be scraped for scoring events. See below for more details.
! Configure - Not currently working (will be used to set paths to configuration
! files)
Debug - runs the system against a standard test file with a single clik, useful
--- 69,74 ----
to be scraped for scoring events. See below for more details.
! Configure - Enables the preferences to be set for the application.
! See http://csms.sourceforge.net/downloadAndInstall/configuration.html for details.
Debug - runs the system against a standard test file with a single clik, useful
|
|
From: <rga...@us...> - 2002-10-29 15:22:20
|
Update of /cvsroot/csms/csms-core/src/documentation
In directory usw-pr-cvs1:/tmp/cvs-serv10128
Modified Files:
Release-Checklist.txt
Log Message:
Updated ready for the iminent release
Index: Release-Checklist.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/Release-Checklist.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** Release-Checklist.txt 22 Oct 2002 17:41:04 -0000 1.4
--- Release-Checklist.txt 29 Oct 2002 15:22:17 -0000 1.5
***************
*** 29,36 ****
process again from the begining.
! - update ./src/status.xml
- add date to release element
! - move tasks to the necessary release element
! - create a new release element (with a due date)
- update ./module.xml
--- 29,35 ----
process again from the begining.
! - update status.xml
- add date to release element
! - create a new release element
- update ./module.xml
|
|
From: <rga...@us...> - 2002-10-29 15:22:09
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv10028
Modified Files:
module.xml
Log Message:
Updated ready for the iminent release
Index: module.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/module.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** module.xml 27 Oct 2002 21:20:09 -0000 1.4
--- module.xml 29 Oct 2002 15:22:05 -0000 1.5
***************
*** 63,67 ****
minor="0"
fix ="1"
! tag="alpha1-dev"/>
<package>org.fanfoot</package>
--- 63,67 ----
minor="0"
fix ="1"
! tag="alpha1"/>
<package>org.fanfoot</package>
|
|
From: <rga...@us...> - 2002-10-29 15:20:43
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv9380
Modified Files:
status.xml
Log Message:
Updated ready for the iminent release
Index: status.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/status.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** status.xml 27 Oct 2002 21:20:59 -0000 1.3
--- status.xml 29 Oct 2002 15:20:41 -0000 1.4
***************
*** 5,9 ****
<developers>
<!-- in strict id alphabetical order -->
! <person name="Ross D. Gardler" id="rgardler" email="ro...@sa..."/>
</developers>
--- 5,11 ----
<developers>
<!-- in strict id alphabetical order -->
! <person name="Ross D. Gardler" id="rdg" email="ro...@sa..."/>
! <person name="Stuart Gardler" id="smgardler" email="st...@wk..."/>
! <person name="Michael Lever" id="leverm" email="mi...@fa..."/>
</developers>
***************
*** 17,24 ****
<changes>
! <release version="0..1alpha1" date="">
<description>Scrapes BBC textual commentaries of Barclaycard Premiership games and
generates scores accordingly. How the events are scraped and how the scores are
calculated is defined in configuration files.</description>
<action dev="rdg" type="add">
Addition of CSMS skin for the community web site.
--- 19,30 ----
<changes>
! <release version="0.1alpha1" date="29 October 2002">
<description>Scrapes BBC textual commentaries of Barclaycard Premiership games and
generates scores accordingly. How the events are scraped and how the scores are
calculated is defined in configuration files.</description>
+ <action dev="rdg" type="add">
+ Added ability to override preferences so that config files are stored
+ locally rather than remotely.
+ </action>
<action dev="rdg" type="add">
Addition of CSMS skin for the community web site.
|
|
From: <rga...@us...> - 2002-10-29 15:05:26
|
Update of /cvsroot/csms/csms-core/src/documentation/override/skins/csms-site/images In directory usw-pr-cvs1:/tmp/cvs-serv1715 Removed Files: add.jpg chapter.gif chapter_open.gif current.gif favicon.ico krysalis-logo-small.gif note.gif page.gif printer.gif remove.jpg singlepage.gif update.jpg void.gif Log Message: Removing unused graphics files --- add.jpg DELETED --- --- chapter.gif DELETED --- --- chapter_open.gif DELETED --- --- current.gif DELETED --- --- favicon.ico DELETED --- --- krysalis-logo-small.gif DELETED --- --- note.gif DELETED --- --- page.gif DELETED --- --- printer.gif DELETED --- --- remove.jpg DELETED --- --- singlepage.gif DELETED --- --- update.jpg DELETED --- --- void.gif DELETED --- |
|
From: <rga...@us...> - 2002-10-29 14:54:24
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/gui
In directory usw-pr-cvs1:/tmp/cvs-serv28525
Modified Files:
ControlCentre.java
Log Message:
Changed name of paths menu option to preferences
Index: ControlCentre.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/gui/ControlCentre.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** ControlCentre.java 27 Oct 2002 22:43:51 -0000 1.5
--- ControlCentre.java 29 Oct 2002 14:54:21 -0000 1.6
***************
*** 188,192 ****
mnuitemParseURL = new javax.swing.JMenuItem();
mnuConfig = new javax.swing.JMenu();
! setPaths = new javax.swing.JMenuItem();
mnuDebug = new javax.swing.JMenu();
parseBBCTExt1 = new javax.swing.JMenuItem();
--- 188,192 ----
mnuitemParseURL = new javax.swing.JMenuItem();
mnuConfig = new javax.swing.JMenu();
! setPrefs = new javax.swing.JMenuItem();
mnuDebug = new javax.swing.JMenu();
parseBBCTExt1 = new javax.swing.JMenuItem();
***************
*** 243,257 ****
mnuConfig.setText("Configuration");
mnuConfig.setToolTipText("Configure the score calculator");
! setPaths.setMnemonic('P');
! setPaths.setText("Paths");
! setPaths.setToolTipText("Set the paths to configuration files");
! setPaths.addActionListener(
new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
! setPathsActionPerformed(evt);
}
});
! mnuConfig.add(setPaths);
}
--- 243,257 ----
mnuConfig.setText("Configuration");
mnuConfig.setToolTipText("Configure the score calculator");
! setPrefs.setMnemonic('P');
! setPrefs.setText("Preferences");
! setPrefs.setToolTipText("Set the application preferences");
! setPrefs.addActionListener(
new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
! setPrefsActionPerformed(evt);
}
});
! mnuConfig.add(setPrefs);
}
***************
*** 301,310 ****
/**
! * Set Paths configuration item is selected
*
*@param evt that caused this action to be performed
*/
! private void setPathsActionPerformed(java.awt.event.ActionEvent evt) {
! //GEN-FIRST:event_setPathsActionPerformed
try {
PreferencesEditor dlgPrefsEditor = new PreferencesEditor(this,
--- 301,310 ----
/**
! * Set Prefs configuration item is selected
*
*@param evt that caused this action to be performed
*/
! private void setPrefsActionPerformed(java.awt.event.ActionEvent evt) {
! //GEN-FIRST:event_setPrefsActionPerformed
try {
PreferencesEditor dlgPrefsEditor = new PreferencesEditor(this,
***************
*** 318,322 ****
! //GEN-LAST:event_setPathsActionPerformed
/**
--- 318,322 ----
! //GEN-LAST:event_setPrefsActionPerformed
/**
***************
*** 635,642 ****
private javax.swing.JMenuItem parseBBCTExt1;
/**
! * the set paths configuration menu item, used to set paths to the
! * configuration files
*/
! private javax.swing.JMenuItem setPaths;
/**
* The tabbed pane for displaying the events once extracted from a
--- 635,641 ----
private javax.swing.JMenuItem parseBBCTExt1;
/**
! * the set prefs configuration menu item, used to set app prefs
*/
! private javax.swing.JMenuItem setPrefs;
/**
* The tabbed pane for displaying the events once extracted from a
|
|
From: <rga...@us...> - 2002-10-28 18:11:33
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv10525
Modified Files:
book.xml
Added Files:
license.xml
Log Message:
Added license file to the xdocs
--- 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>
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/book.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** book.xml 28 Oct 2002 17:16:48 -0000 1.6
--- book.xml 28 Oct 2002 18:11:25 -0000 1.7
***************
*** 9,13 ****
<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>
--- 9,13 ----
<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>
|
|
From: <rga...@us...> - 2002-10-28 18:11:04
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall
In directory usw-pr-cvs1:/tmp/cvs-serv10353
Modified Files:
book.xml
Log Message:
Added license file to the xdocs
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall/book.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** book.xml 28 Oct 2002 17:16:29 -0000 1.3
--- book.xml 28 Oct 2002 18:11:01 -0000 1.4
***************
*** 9,13 ****
<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>
--- 9,13 ----
<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>
|
|
From: <rga...@us...> - 2002-10-28 18:10:48
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/manual
In directory usw-pr-cvs1:/tmp/cvs-serv10175
Modified Files:
book.xml
Log Message:
Added license file to the xdocs
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/manual/book.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** book.xml 28 Oct 2002 17:16:17 -0000 1.1
--- book.xml 28 Oct 2002 18:10:43 -0000 1.2
***************
*** 9,13 ****
<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>
--- 9,13 ----
<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>
|
