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-22 18:08:43
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv23463
Modified Files:
centibuild.xml
Log Message:
Added run target to enable the system to be run from Centipede
Index: centibuild.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/centibuild.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** centibuild.xml 22 Oct 2002 17:40:27 -0000 1.6
--- centibuild.xml 22 Oct 2002 18:08:40 -0000 1.7
***************
*** 96,99 ****
--- 96,102 ----
<target name="metrics" depends="checkstyle, report, jdepend-xdoc"/>
<target name="docs" depends="test, metrics, javasrc, javadocs, forrest.docs"/>
+ <target name="run" depends="distclean, dist-bin">
+ <exec executable="${basedir}/dist/bin/bin/csms" dir="${basedir}/dist/bin/bin"/>
+ </target>
<!-- ================================== -->
|
|
From: <rga...@us...> - 2002-10-22 17:41:07
|
Update of /cvsroot/csms/csms-core/src/documentation
In directory usw-pr-cvs1:/tmp/cvs-serv27634
Modified Files:
Release-Checklist.txt
Log Message:
Added more steps to the release process
Index: Release-Checklist.txt
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/Release-Checklist.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** Release-Checklist.txt 18 Oct 2002 21:09:15 -0000 1.3
--- Release-Checklist.txt 22 Oct 2002 17:41:04 -0000 1.4
***************
*** 1,8 ****
! - update docbook stylesheets (see bug 155 for process)
! - cent clean all
- Check for any errors in the unit test reports
! - correct any failures and start again from build clean
- update ./src/status.xml
--- 1,31 ----
! - Ensure local copy is in Synch with CVS
! - cvs update
! - place feature freeze on CVS
! - Check for any errors in the unit test reports
! - cent clean test
! - correct any failures and start release process again
!
! - update ./legal
! - ensure licenses for all libs are included
!
! - update the README.txt file
!
! - Ensure local copy is in synch with CVS
! - cvs update
!
! - place code freeze on CVS
- Check for any errors in the unit test reports
! - cent clean test
! - 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 ./src/status.xml
***************
*** 13,26 ****
- update ./module.xml
- set version tag to beta, rc1, rc2 etc.
! - check dependiencies list is complete
!
! - update ./legal
! - ensure licenses for all libs are included
!
- update the web site docs
!
! - cent deploysite
!
! - ensure CVS is up to date
- tag CVS (release_X_Y_Z, where X, Y and Z are version numbers)
--- 36,44 ----
- 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)
***************
*** 28,41 ****
- publish web site
- update ./module.xml
- increment version number and set tag to alpha
! - Generate announcements and HEADER.html
!
! - upload distributions to correct dir
- send announcements to ...
! ...
- post stories on
*) Sourceforge
--- 46,60 ----
- 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
*) Sourceforge
|
|
From: <rga...@us...> - 2002-10-22 17:40:31
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv26987
Modified Files:
centibuild.xml
Log Message:
Create separate startup scripts for CSMS and FSM (fantsy sports module) releases. Note that at the moment they are both the same thing, but eventually the CSMS will be the league management stuff and FSM will be the fantasy sports stuff).
Index: centibuild.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/centibuild.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** centibuild.xml 22 Oct 2002 12:17:18 -0000 1.5
--- centibuild.xml 22 Oct 2002 17:40:27 -0000 1.6
***************
*** 107,112 ****
<target name="scripts">
<antcall target="make-main-scripts">
! <param name="scripts.cent.script.name" value="fanfoot"/>
<param name="scripts.cent.class" value="org.fanfoot.gui.ControlCentre"/>
</antcall>
--- 107,118 ----
<target name="scripts">
+ <!-- Make scripts for Fantasy Sports Module -->
<antcall target="make-main-scripts">
! <param name="scripts.cent.script.name" value="fsm"/>
! <param name="scripts.cent.class" value="org.fanfoot.gui.ControlCentre"/>
! </antcall>
! <!-- Make scripts for CSMS core application -->
! <antcall target="make-main-scripts">
! <param name="scripts.cent.script.name" value="csms"/>
<param name="scripts.cent.class" value="org.fanfoot.gui.ControlCentre"/>
</antcall>
|
|
From: <rga...@us...> - 2002-10-22 17:24:47
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv11983
Modified Files:
index.xml
Log Message:
Added mision to home page
Index: index.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** index.xml 22 Oct 2002 14:44:24 -0000 1.4
--- index.xml 22 Oct 2002 17:24:45 -0000 1.5
***************
*** 21,25 ****
fantasy. The software also provides mechanisms for supporting online
communities based around each sport, league and team.</p>
!
</section>
--- 21,32 ----
fantasy. The software also provides mechanisms for supporting online
communities based around each sport, league and team.</p>
! <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>
|
|
From: <rga...@us...> - 2002-10-22 17:22:19
|
Update of /cvsroot/csms/csms-core In directory usw-pr-cvs1:/tmp/cvs-serv9664 Added Files: README.txt Log Message: Added a readme to help get users started. --- NEW FILE: README.txt --- Community Sports Management SYstem ================================== 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. About This Release ================== 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 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. ===================== Fantasy Sports Module ===================== The fantasy sports module scrapes online sources of information (such as game commentaries) and generates a database of possible scoring events from those sources. Thse events are then processed to generate actual scores for the players according to a scoring configuration file. Installing the application ========================== This application requires a version of Java of at least version 1.4 (available from www.javasoft.com) A zip file of the control centre is available. Unzip the application in a location of your choice. Public CVS access is available, please see http://csms.sourceforge.net/downloadAndInstall for details. Running the Application ======================= To run the application cd to the bin directory inside the install directory. and run the startup script with the command fsm. The User Interface ================== Once running the you should select file|Parse URL (or file|Parse File if you have commentaries saved on your local disk) and wait for about a minute or so. At this stage processing is quite slow as all configuration files are downloaded over the internet and no caching is currently in place. Furthermore, visual feedback is limited to minimal messages in the shell where you executed the fanfoot script. Performance will be improved at a later date, as will the visual feedback. The application currently presents a graphical interface to the system. There are three menus: File - used to point to a local file or an URL of a file to be processed, currently the system only works with BBC commentaries on Barclaycard Premiership Games. However, the system is highly configurable through XML and XSL files and it is easy to enable other sources of information 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 when testing changes to configuration files. Interpreting the results ======================== Once the parsing process is complete a number of tabs will appear in the GUI. These will show the events detected in the process, the XML file representing those events, the XML file representing the scores and an HTML representatio of those scores. The most useful tab is by far the HTML summary one. This presents a summary of individual players scores. A list of errors (should any have occurred) and a breakdown of how players scores are calculated. This HTML page is created by passing the scores XML document through an XSL file. Currently this file is fixed as the one located at http://www.fanfoot.com/test/Score2HTML.xsl, in a later release this will become configurable. For now, you can only change this file if you have write access to that file. Support ======= Support is available via our online support request system at https://sourceforge.net/tracker/?atid=509509&group_id=65029&func=browse. Please search this system for an answer to your problem before posting a question. Players Database ================ We have tried to detect all errors in the calculation of points (although we are bound to miss some). These errors are listed in the errors section of the scores XML and HTML documents. They usually relate to being unable to find either a players team or full name in the players database. The database is currently a single XML file located at http://www.fanfoot.com/players.xml. If you have write access to this file, feel free to correct any errors in the database, if you do not have write access to this file please notify us of the bug through the bug reporting system at http://sourceforge.net/tracker/?group_id=65029&atid=509508 and we will address it as soon as we can. In a future release these configuration files will be local to your application and thus you will be able to edit them and provide us with patches. Errors in score Calculations ============================ If a score is calculated incorrectly there are two possible causes of this. The first (and most likely) is that the patterns matching the event description in the commentary is incomplete or incorrect. The other type of problem is in the translation of the events into points. If you come across any of these errors please report the bug on our bug tracking system at http://sourceforge.net/tracker/?group_id=65029&atid=509508. Bug Reporting ============= If you spot any problems at all please report them on our bug tracking system at http://sourceforge.net/tracker/?group_id=65029&atid=509508. Feature Requests ================ We welcome feature requrest from potential users, please post all requests on or Feature Request tracking system at https://sourceforge.net/tracker/?atid=509511&group_id=65029&func=browse Contributing ============ This is an Open Source development effort and as such we encourage your participation. Unfortunately with this release this participation is limited to testing since it is not possible to configure the application to use different configuration files than those on the fanfoot server. This will be resolved very soon. In the meantime you are welcome to join our developer mailing list at http://sourceforge.net/mail/?group_id=65029. If you do wish to contribute please take a look at our project constitution which describes ways that you can contribute positively. ALternatively simply join our mailing list (http://sourceforge.net/mail/?group_id=65029) and ask how you can help, or take a look at the outstanding tasks on our task management system (http://sourceforge.net/pm/?group_id=65029) |
|
From: <rga...@us...> - 2002-10-22 14:49:09
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall
In directory usw-pr-cvs1:/tmp/cvs-serv5858
Modified Files:
index.xml
Log Message:
Minor changes in generated page layout
Index: index.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** index.xml 22 Oct 2002 14:45:28 -0000 1.1
--- index.xml 22 Oct 2002 14:49:05 -0000 1.2
***************
*** 1,67 ****
<?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 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>
<ul>
! <li><link href="http://www.javasoft.com/download">Java 2 Standard Edition</link>
version 1.4 or higher</li>
! <li><link href="http://www.krysalis.org/centipede">Centipede</link> build tool</li>
</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>
! </section>
! <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>
! <section>
! <title>Running a CVS build</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>cent run</code></p>
</section>
</body>
</document>
--- 1,120 ----
<?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 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>
!
<ul>
! <li>
! <link href="http://www.javasoft.com/download">Java 2 Standard
! Edition</link>
!
version 1.4 or higher</li>
!
! <li>
! <link href="http://www.krysalis.org/centipede">Centipede</link>
!
! build tool</li>
</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>
!
! <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>
!
! <section>
! <title>Running a CVS build</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>cent run</code>
! </p>
! </section>
</section>
</body>
</document>
+
+
|
|
From: <rga...@us...> - 2002-10-22 14:45:32
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall
In directory usw-pr-cvs1:/tmp/cvs-serv2859
Added Files:
index.xml book.xml
Log Message:
Basic download and install instructions
--- 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 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>
<ul>
<li><link href="http://www.javasoft.com/download">Java 2 Standard Edition</link>
version 1.4 or higher</li>
<li><link href="http://www.krysalis.org/centipede">Centipede</link> build tool</li>
</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>
</section>
<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>
<section>
<title>Running a CVS build</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>cent run</code></p>
</section>
</body>
</document>
--- 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>
<menu label="Code">
<menu-item label="Javadocs" href="../javadocs/"/>
<menu-item label="Java Source Ref" href="../javasrc/"/>
<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/"/>
</menu>
</book>
|
|
From: <rga...@us...> - 2002-10-22 14:44:28
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv1869
Modified Files:
index.xml book.xml
Log Message:
Basic download and install instructions
Index: index.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** index.xml 22 Oct 2002 12:20:17 -0000 1.3
--- index.xml 22 Oct 2002 14:44:24 -0000 1.4
***************
*** 12,16 ****
<body>
<section>
! <title>Introduction"</title>
<p>The <strong>Community Sports Management System</strong>
sports league management system allowing the creation of leagues and
--- 12,16 ----
<body>
<section>
! <title>Introduction</title>
<p>The <strong>Community Sports Management System</strong>
sports league management system allowing the creation of leagues and
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/book.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** book.xml 22 Oct 2002 12:22:03 -0000 1.4
--- book.xml 22 Oct 2002 14:44:24 -0000 1.5
***************
*** 2,8 ****
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "dtd/book-cocoon-v10.dtd">
! <book software="Krysalis Centipede"
! title="Krysalis Centipede Smoke Test"
! copyright="@year@ Krysalis Project"
xmlns:xlink="http://www.w3.org/1999/xlink">
--- 2,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">
***************
*** 12,19 ****
<menu-item label="Constitution" href="constitution.html"/>
</menu>
!
<menu label="Docs">
<menu-item label="Introduction" href="index.html"/>
</menu>
<menu label="Code">
<menu-item label="Javadocs" href="javadocs/"/>
--- 12,21 ----
<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>
+
<menu label="Code">
<menu-item label="Javadocs" href="javadocs/"/>
***************
*** 22,26 ****
<menu-item label="Dependencies" href="jdepend/index.html"/>
<menu-item label="Unit tests" href="junit/"/>
! </menu>>
</book>
--- 24,28 ----
<menu-item label="Dependencies" href="jdepend/index.html"/>
<menu-item label="Unit tests" href="junit/"/>
! </menu>
</book>
|
|
From: <rga...@us...> - 2002-10-22 14:08:38
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall In directory usw-pr-cvs1:/tmp/cvs-serv31568/downloadAndInstall Log Message: Directory /cvsroot/csms/csms-core/src/documentation/xdocs/downloadAndInstall added to the repository |
|
From: <rga...@us...> - 2002-10-22 12:23:46
|
Update of /cvsroot/csms/csms-core/src/documentation/override/jdepend/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv1235
Added Files:
book.xml
Log Message:
Added book.xml override for JDepend
--- 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="Krysalis-Project"
title="Krysalis Project Template"
copyright="@year@ Krysalis"
xmlns:xlink="http://www.w3.org/1999/xlink">
<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>
</book>
|
|
From: <rga...@us...> - 2002-10-22 12:22:43
|
Update of /cvsroot/csms/csms-core/src/documentation/override/jdepend/xdocs In directory usw-pr-cvs1:/tmp/cvs-serv32745/xdocs Log Message: Directory /cvsroot/csms/csms-core/src/documentation/override/jdepend/xdocs added to the repository |
|
From: <rga...@us...> - 2002-10-22 12:22:28
|
Update of /cvsroot/csms/csms-core/src/documentation/override/jdepend In directory usw-pr-cvs1:/tmp/cvs-serv32553/jdepend Log Message: Directory /cvsroot/csms/csms-core/src/documentation/override/jdepend added to the repository |
|
From: <rga...@us...> - 2002-10-22 12:22:06
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv32051
Modified Files:
book.xml
Added Files:
constitution.xml
Log Message:
Added constitution to the web site
--- 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 Conststitution</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. 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>
Index: book.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/book.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** book.xml 21 Oct 2002 19:57:07 -0000 1.3
--- book.xml 22 Oct 2002 12:22:03 -0000 1.4
***************
*** 8,12 ****
<menu label="Community">
! <menu-item label="Project Management" href="http://sourceforge.net/projects/csms"/>
</menu>
--- 8,14 ----
<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-22 12:21:48
|
Update of /cvsroot/csms/csms-core/src/documentation In directory usw-pr-cvs1:/tmp/cvs-serv31908 Removed Files: constitution.txt Log Message: Added constitution to the web site --- constitution.txt DELETED --- |
|
From: <rga...@us...> - 2002-10-22 12:20:20
|
Update of /cvsroot/csms/csms-core/src/documentation/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv30760
Modified Files:
index.xml
Log Message:
Changed to new title element (rather than old attribute)
Index: index.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** index.xml 18 Oct 2002 14:57:28 -0000 1.2
--- index.xml 22 Oct 2002 12:20:17 -0000 1.3
***************
*** 11,15 ****
<body>
! <section title="Introduction">
<p>The <strong>Community Sports Management System</strong>
sports league management system allowing the creation of leagues and
--- 11,16 ----
<body>
! <section>
! <title>Introduction"</title>
<p>The <strong>Community Sports Management System</strong>
sports league management system allowing the creation of leagues and
|
|
From: <rga...@us...> - 2002-10-22 12:18:47
|
Update of /cvsroot/csms/csms-core/src/documentation/override/forrest/skins/csms-site/xslt/html
In directory usw-pr-cvs1:/tmp/cvs-serv29573
Modified Files:
document2html.xsl
Log Message:
Handle the new <title> element (was an attribute)
Index: document2html.xsl
===================================================================
RCS file: /cvsroot/csms/csms-core/src/documentation/override/forrest/skins/csms-site/xslt/html/document2html.xsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** document2html.xsl 21 Oct 2002 20:53:06 -0000 1.1
--- document2html.xsl 22 Oct 2002 12:18:44 -0000 1.2
***************
*** 63,76 ****
<xsl:choose>
<xsl:when test="$level=1">
! <h2><xsl:value-of select="@title"/></h2>
</xsl:when>
<xsl:when test="$level=2">
! <h3><xsl:value-of select="@title"/></h3>
</xsl:when>
<xsl:when test="$level=3">
! <h4><xsl:value-of select="@title"/></h4>
</xsl:when>
<xsl:otherwise>
! <h5><xsl:value-of select="@title"/></h5>
</xsl:otherwise>
</xsl:choose>
--- 63,76 ----
<xsl:choose>
<xsl:when test="$level=1">
! <h2><xsl:value-of select="./title"/></h2>
</xsl:when>
<xsl:when test="$level=2">
! <h3><xsl:value-of select="./title"/></h3>
</xsl:when>
<xsl:when test="$level=3">
! <h4><xsl:value-of select="./title"/></h4>
</xsl:when>
<xsl:otherwise>
! <h5><xsl:value-of select="./title"/></h5>
</xsl:otherwise>
</xsl:choose>
***************
*** 79,82 ****
--- 79,86 ----
</xsl:template>
+
+ <xsl:template match="title">
+ <!-- Do nothing - handled in the section template -->
+ </xsl:template>
<!-- ====================================================================== -->
|
|
From: <rga...@us...> - 2002-10-22 12:17:21
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv28377
Modified Files:
centibuild.xml
Log Message:
Added test and checkstyle to the docs target
Index: centibuild.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/centibuild.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** centibuild.xml 21 Oct 2002 19:57:37 -0000 1.4
--- centibuild.xml 22 Oct 2002 12:17:18 -0000 1.5
***************
*** 93,99 ****
<target name="all" depends="clean, code, metrics, docs, dist"/>
! <target name="code" depends="compile,test,package"/>
<target name="metrics" depends="checkstyle, report, jdepend-xdoc"/>
! <target name="docs" depends="javasrc, javadocs, forrest.docs"/>
<!-- ================================== -->
--- 93,99 ----
<target name="all" depends="clean, code, metrics, docs, dist"/>
! <target name="code" depends="compile, test, package"/>
<target name="metrics" depends="checkstyle, report, jdepend-xdoc"/>
! <target name="docs" depends="test, metrics, javasrc, javadocs, forrest.docs"/>
<!-- ================================== -->
|
|
From: <rga...@us...> - 2002-10-22 09:46:46
|
Update of /cvsroot/csms/csms-core/src/documentation/override/checkstyle In directory usw-pr-cvs1:/tmp/cvs-serv25847 Removed Files: book.xml Log Message: Moved checkstyle book.xml to the right place --- book.xml DELETED --- |
|
From: <rga...@us...> - 2002-10-22 09:24:07
|
Update of /cvsroot/csms/csms-core/src/documentation/override/checkstyle/xdocs
In directory usw-pr-cvs1:/tmp/cvs-serv6219
Added Files:
book.xml
Log Message:
Moved checkstyle book.xml to the right place
--- 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="Krysalis-Project"
title="Krysalis Project Template"
copyright="@year@ Krysalis"
xmlns:xlink="http://www.w3.org/1999/xlink">
<menu label="">
<menu-item label="Project Home" href="../"/>
</menu>
<menu label="Style Report">
<menu-item label="Summary" href="./index.html"/>
<menu-item label="Details" href="./details.html"/>
</menu>
<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>
</book>
|
|
From: <rga...@us...> - 2002-10-22 09:22:54
|
Update of /cvsroot/csms/csms-core/src/documentation/override/checkstyle/xdocs In directory usw-pr-cvs1:/tmp/cvs-serv4479/xdocs Log Message: Directory /cvsroot/csms/csms-core/src/documentation/override/checkstyle/xdocs added to the repository |
|
From: <rga...@us...> - 2002-10-21 22:25:30
|
Update of /cvsroot/csms/csms-core
In directory usw-pr-cvs1:/tmp/cvs-serv18309
Modified Files:
status.xml
Log Message:
Added recent actions
Index: status.xml
===================================================================
RCS file: /cvsroot/csms/csms-core/status.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** status.xml 17 Oct 2002 16:53:47 -0000 1.1.1.1
--- status.xml 21 Oct 2002 22:25:27 -0000 1.2
***************
*** 16,19 ****
--- 16,62 ----
</todo>
+ <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.
+ </action>
+ <action dev="rdg" type="add">
+ Addition of JDepend metrics report to the community site.
+ </action>
+ <action dev="rdg" type="update">
+ Various refactorings and code style checks in response to checkstyle reports.
+ </action>
+ <action dev="rdg" type="update">
+ Local browser now displays commentary before any other files are loaded, this improves performance
+ because the browser will download the file in parallel to the configuration files.
+ </action>
+ <action dev="rdg" type="update">
+ Local browser now displays contents of local file as well as remote urls when parsing.
+ </action>
+ <action dev="rdg" type="update">
+ Now able tp check for duplicate events in the event parser using the <duplicateDetection>
+ element of the the event definition in the parser config file.
+ </action>
+ <action dev="rdg" type="update">
+ Removed permanent tab panes for Events XML, Scores XML and Scores HTML.
+ These are now created as they are needed.
+ </action>
+ <action dev="rdg" type="update">
+ Added list BBC commentary URLs to the getURL dialog used to enter
+ the URL of a page to parse. You can now either type an URL or select one
+ in the combo box.
+ </action>
+ <action dev="rdg" type="add">
+ Added Event notification to EventParser and EventParserListener to allow feedback to the
+ application.
+ </action>
+ <action dev="rdg" type="add">
+ ControlCentre now controls the native broswer to display the commentary page.
+ This should assist in verifying calculated scores.
+ </action>
+ </release>
</status>
|
|
From: <rga...@us...> - 2002-10-21 22:19:35
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring
In directory usw-pr-cvs1:/tmp/cvs-serv12846
Modified Files:
EventParser.java EventPattern.java
Log Message:
Bug fixes for errors introduced during refactoring:
Repeat after me:
"I will run all tests and check all build tasks using 'cent clean all' before committing changes"
Index: EventParser.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring/EventParser.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** EventParser.java 21 Oct 2002 22:12:01 -0000 1.3
--- EventParser.java 21 Oct 2002 22:19:31 -0000 1.4
***************
*** 155,158 ****
--- 155,159 ----
StringBuffer sbData = new StringBuffer();
XMLUtils.appendAllText(docCommentary.getDocumentElement(), sbData);
+ String strData = sbData.toString();
ArrayList patterns = conf.getPatternsForType(strType);
***************
*** 160,166 ****
String strEventsUID = parseEventsUID(strData, strType);
evtsResult.setUID(strEventsUID);
-
- logger.info("Start processing " + patterns.size()
- + " event patterns.");
Events evtsCurrent;
--- 161,164 ----
Index: EventPattern.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring/EventPattern.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** EventPattern.java 21 Oct 2002 22:07:31 -0000 1.4
--- EventPattern.java 21 Oct 2002 22:19:31 -0000 1.5
***************
*** 118,122 ****
sb.append(strRE);
sb.append(')');
! addCapturingGroup();
idxGroup = idxGroup + 1;
} else if(curNode.getNodeName().equals("unwantedPart")) {
--- 118,122 ----
sb.append(strRE);
sb.append(')');
! addCapturingGroup(idxGroup, curNode);
idxGroup = idxGroup + 1;
} else if(curNode.getNodeName().equals("unwantedPart")) {
|
|
From: <rga...@us...> - 2002-10-21 22:12:06
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring
In directory usw-pr-cvs1:/tmp/cvs-serv6266
Modified Files:
EventParser.java
Log Message:
Refactoring
Index: EventParser.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring/EventParser.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** EventParser.java 21 Oct 2002 12:01:14 -0000 1.2
--- EventParser.java 21 Oct 2002 22:12:01 -0000 1.3
***************
*** 156,175 ****
XMLUtils.appendAllText(docCommentary.getDocumentElement(), sbData);
- String strData = sbData.toString();
- logger.finest("Live Data: " + strData);
-
ArrayList patterns = conf.getPatternsForType(strType);
-
Events evtsResult = new Events();
String strEventsUID = parseEventsUID(strData, strType);
evtsResult.setUID(strEventsUID);
- logger.info("UID for these events is: " + strEventsUID);
-
- Events evtsCurrent;
- EventPattern p;
logger.info("Start processing " + patterns.size()
+ " event patterns.");
for(int i = 0; i < patterns.size(); i++) {
p = (EventPattern) patterns.get(i);
--- 156,169 ----
XMLUtils.appendAllText(docCommentary.getDocumentElement(), sbData);
ArrayList patterns = conf.getPatternsForType(strType);
Events evtsResult = new Events();
String strEventsUID = parseEventsUID(strData, strType);
evtsResult.setUID(strEventsUID);
logger.info("Start processing " + patterns.size()
+ " event patterns.");
+ Events evtsCurrent;
+ EventPattern p;
for(int i = 0; i < patterns.size(); i++) {
p = (EventPattern) patterns.get(i);
***************
*** 194,200 ****
*/
private Events processEvents(EventPattern p, String strData) {
- logger.entering("org.fanfoot.scoring.EventParser",
- "processEvents(eventPattern, strData)");
-
Events evts = new Events();
Matcher m = p.getRegexPattern().matcher(strData);
--- 188,191 ----
***************
*** 225,231 ****
evts.add(evt);
}
-
- logger.exiting("org.fanfoot.scoring.EventParser",
- "processEvents(eventPattern, strData)");
return evts;
--- 216,219 ----
|
|
From: <rga...@us...> - 2002-10-21 22:07:35
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring
In directory usw-pr-cvs1:/tmp/cvs-serv1399
Modified Files:
EventPattern.java
Log Message:
Refactoring
Index: EventPattern.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring/EventPattern.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** EventPattern.java 21 Oct 2002 21:42:19 -0000 1.3
--- EventPattern.java 21 Oct 2002 22:07:31 -0000 1.4
***************
*** 79,87 ****
public EventPattern(Node node) {
super();
StringBuffer sb = new StringBuffer();
- String strGroupName;
String strRE;
- NamedNodeMap atts;
int idxGroup = 1;
Node curNode = node.getFirstChild();
--- 79,105 ----
public EventPattern(Node node) {
super();
+ NamedNodeMap atts;
+
+ regexPattern = Pattern.compile(createREPattern(node));
+ Node eventNode = node.getParentNode();
+ atts = eventNode.getAttributes();
+ String strType = atts.getNamedItem("type").getFirstChild().getNodeValue();
+ this.setType(strType);
+ }
+
+
+ /**
+ * Create a Regular Expression pattern from the supplied node.
+ * Returns the RE as a string and records the captuing groups and
+ * part names by calling setCapturingGroup for each one.
+ *
+ *@param node the node containing the XML representation of the
+ * pattern
+ *@return the string representation of the pattern
+ */
+ private String createREPattern(Node node) {
StringBuffer sb = new StringBuffer();
String strRE;
int idxGroup = 1;
Node curNode = node.getFirstChild();
***************
*** 89,93 ****
while(curNode != null) {
-
if(curNode.getNodeName().equals("part")) {
childNode = curNode.getFirstChild();
--- 107,110 ----
***************
*** 101,112 ****
sb.append(strRE);
sb.append(')');
! atts = curNode.getAttributes();
! strGroupName = atts.getNamedItem("name").getNodeValue();
! this.setCapturingGroup(idxGroup, strGroupName);
idxGroup = idxGroup + 1;
} else if(curNode.getNodeName().equals("unwantedPart")) {
strRE = curNode.getFirstChild().getNodeValue();
sb.append(strRE);
- logger.fine("Added non-capturing group with RE " + strRE);
}
--- 118,126 ----
sb.append(strRE);
sb.append(')');
! addCapturingGroup();
idxGroup = idxGroup + 1;
} else if(curNode.getNodeName().equals("unwantedPart")) {
strRE = curNode.getFirstChild().getNodeValue();
sb.append(strRE);
}
***************
*** 114,124 ****
}
! regexPattern = Pattern.compile(sb.toString());
- Node eventNode = node.getParentNode();
- atts = eventNode.getAttributes();
! String strType = atts.getNamedItem("type").getFirstChild().getNodeValue();
! this.setType(strType);
}
--- 128,149 ----
}
! return sb.toString();
! }
! /**
! * Add a capturing group at the given index, represented by the
! * given node.
! *
! *@param idx the index number for this group
! *@param node the node representing this group
! */
! private void addCapturingGroup(int idx, Node node) {
! NamedNodeMap atts;
! String strGroupName;
!
! atts = node.getAttributes();
! strGroupName = atts.getNamedItem("name").getNodeValue();
! this.setCapturingGroup(idx, strGroupName);
}
|
|
From: <rga...@us...> - 2002-10-21 21:42:22
|
Update of /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring
In directory usw-pr-cvs1:/tmp/cvs-serv8464
Modified Files:
EventPattern.java
Log Message:
Refactoring
Index: EventPattern.java
===================================================================
RCS file: /cvsroot/csms/csms-core/src/java/org/fanfoot/scoring/EventPattern.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** EventPattern.java 21 Oct 2002 12:01:14 -0000 1.2
--- EventPattern.java 21 Oct 2002 21:42:19 -0000 1.3
***************
*** 47,52 ****
* scores in a textual commentary or set of statistics.
*
! *@author rgardler
! *@created 21 October 2002
*/
public class EventPattern {
--- 47,52 ----
* scores in a textual commentary or set of statistics.
*
! *@author rgardler
! *@created 21 October 2002
*/
public class EventPattern {
***************
*** 74,79 ****
* Creates a new instance of Pattern
*
! *@param node a DOM node taken from a configuration file
! * describing an event pattern
*/
public EventPattern(Node node) {
--- 74,79 ----
* Creates a new instance of Pattern
*
! *@param node a DOM node taken from a configuration file describing
! * an event pattern
*/
public EventPattern(Node node) {
***************
*** 95,121 ****
if(childNode.getNodeType() == node.TEXT_NODE) {
strRE = childNode.getNodeValue();
- sb.append('(');
- sb.append(strRE);
- sb.append(')');
- atts = curNode.getAttributes();
- strGroupName = atts.getNamedItem("name").getNodeValue();
- this.setCapturingGroup(idxGroup, strGroupName);
- idxGroup = idxGroup + 1;
- logger.fine(
- "Added capturing group " + strGroupName
- + " with RE " + strRE);
} else {
strRE = childNode.getFirstChild().getNodeValue();
- sb.append('(');
- sb.append(strRE);
- sb.append(')');
- atts = curNode.getAttributes();
- strGroupName = atts.getNamedItem("name").getNodeValue();
- this.setCapturingGroup(idxGroup, strGroupName);
- idxGroup = idxGroup + 1;
- logger.fine(
- "Added capturing group " + strGroupName
- + " with RE " + strRE);
}
} else if(curNode.getNodeName().equals("unwantedPart")) {
strRE = curNode.getFirstChild().getNodeValue();
--- 95,108 ----
if(childNode.getNodeType() == node.TEXT_NODE) {
strRE = childNode.getNodeValue();
} else {
strRE = childNode.getFirstChild().getNodeValue();
}
+ sb.append('(');
+ sb.append(strRE);
+ sb.append(')');
+ atts = curNode.getAttributes();
+ strGroupName = atts.getNamedItem("name").getNodeValue();
+ this.setCapturingGroup(idxGroup, strGroupName);
+ idxGroup = idxGroup + 1;
} else if(curNode.getNodeName().equals("unwantedPart")) {
strRE = curNode.getFirstChild().getNodeValue();
***************
*** 138,144 ****
/**
* Getter for property regexPattern.
*
! *@return Value of property regexPattern.
*/
public Pattern getRegexPattern() {
--- 125,144 ----
/**
+ * Private add the supplied Regular Expression as a capturing group
+ * with the index number indicated
+ *
+ *@param strRE the Regular Expression for the group
+ *@param idxGroup The feature to be added to the CapturingGroup
+ * attribute
+ *@parm idxGroup the index number of the group
+ */
+ private void addCapturingGroup(String strRE, int idxGroup) {
+ }
+
+
+ /**
* Getter for property regexPattern.
*
! *@return Value of property regexPattern.
*/
public Pattern getRegexPattern() {
***************
*** 151,155 ****
* Setter for property regexPattern.
*
! *@param regexPattern New value of property regexPattern.
*/
public void setRegexPattern(Pattern regexPattern) {
--- 151,155 ----
* Setter for property regexPattern.
*
! *@param regexPattern New value of property regexPattern.
*/
public void setRegexPattern(Pattern regexPattern) {
***************
*** 161,166 ****
* Indexed getter for property capturingGroup.
*
! *@param index Index of the property.
! *@return Value of the property at <CODE>index</CODE>.
*/
public String getCapturingGroup(int index) {
--- 161,166 ----
* Indexed getter for property capturingGroup.
*
! *@param index Index of the property.
! *@return Value of the property at <CODE>index</CODE>.
*/
public String getCapturingGroup(int index) {
***************
*** 173,178 ****
* Get the part name for the indicate capturing group
*
! *@param index Index of the property.
! *@return Value of the property at <CODE>index</CODE>.
*/
public String getPartName(int index) {
--- 173,178 ----
* Get the part name for the indicate capturing group
*
! *@param index Index of the property.
! *@return Value of the property at <CODE>index</CODE>.
*/
public String getPartName(int index) {
***************
*** 185,190 ****
* Indexed setter for property capturingGroup.
*
! *@param index Index of the property.
! *@param capturingGroupName New value of the property at <CODE>index</CODE>
* .
*/
--- 185,190 ----
* Indexed setter for property capturingGroup.
*
! *@param index Index of the property.
! *@param capturingGroupName New value of the property at <CODE>index</CODE>
* .
*/
***************
*** 199,203 ****
* Getter for property type.
*
! *@return Value of property type.
*/
public String getType() {
--- 199,203 ----
* Getter for property type.
*
! *@return Value of property type.
*/
public String getType() {
***************
*** 210,214 ****
* Setter for property type.
*
! *@param type New value of property type.
*/
public void setType(String type) {
--- 210,214 ----
* Setter for property type.
*
! *@param type New value of property type.
*/
public void setType(String type) {
|
