svn commit: r25 - trunk/www
gregboone at osgeo.org
gregboone at osgeo.org
Wed May 17 16:49:48 EDT 2006
Author: gregboone
Date: 2006-05-17 20:49:48+0000
New Revision: 25
Added:
trunk/www/about.html (contents, props changed)
trunk/www/artifactlifecycle.html (contents, props changed)
trunk/www/artifactlifecycle.png (contents, props changed)
trunk/www/developer.html (contents, props changed)
trunk/www/faq.html (contents, props changed)
trunk/www/projectartifacts.html (contents, props changed)
trunk/www/subversionconfig.html (contents, props changed)
trunk/www/user.html (contents, props changed)
Modified:
trunk/www/index.html
Log:
FDO2
Added: trunk/www/about.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/about.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/about.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,87 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - About</title>
+</head>
+<body>
+<h1>FDO Open Source - About</h1>
+<a href="#project">Project</a>
+<ul type="square">
+ <li><a href="#mission">Mission and Goals</a></li>
+ <li><a href="#history">Historical Background</a></li>
+ <li><a href="#license">License</a></li>
+ <li><a href="#governance">Governance</a></li>
+ <li><a href="#orgroles">Organization and Roles</a></li>
+</ul>
+<a href="#product">Product</a>
+<ul type="square">
+ <li><a href="#description">Description</a></li>
+ <li><a href="#features">Features</a></li>
+ <li><a href="#links">Useful Links</a></li>
+</ul>
+<div class="h2">
+<h2><a name="project" id="project">Project</a></h2>
+<h3><a name="mission" id="mission">Mission and Goals</a></h3>
+<!--
+<p>To create, as a community, the leading international web-based platform for developing and deploying web mapping applications and geospatial web services. The goals for the platform are as follows:</p>
+<ul type="square">
+ <li>use the service-oriented architecture pattern</li>
+ <li>fast, scalable, and cross platform</li>
+ <li>make use of open source components</li>
+ <li>support rich access to spatial data both vector and raster </li>
+ <li>provide a full suite of spatial analysis</li>
+ <li>produce visually stunning cartographic maps</li>
+ <li>include viewers that work within any browser on any platform</li>
+ <li>provide the highest degree of map interactivity possible </li>
+ <li>offer a single API that works with both vector and raster based client-side viewers </li>
+ <li>conform with open standards </li>
+</ul>
+-->
+<h3><a name="history" id="history">Historical Background</a></h3>
+<!--
+<p>FDO was first introduced as Argus FDO in 1995 by Argus Technologies in Calgary, Alberta. Autodesk acquired Argus Technologies in the fall of 1996 and within a few months the first release under the Autodesk brand was introduced, Autodesk FDO 2.0. The software progressed through a number of releases leading up to the current Autodesk FDO 6.5. To this day FDO 6.5 and previous releases are known for ease of deployment, rapid application development, data connectivity, scalability, and overall performance.</p>
+<p>Despite its success the FDO 6.5 architecture has some inherent limitations. To this day most FDO applications rely upon a client Plug-in, ActiveX Control, or Java Applet with much of the application logic written in JavaScript using the APIs offered by the client-side plug-in. All spatial analysis is performed client-side on rendered graphics rather than on the underlying spatial data. And finally the server platform is very Windows centric. </p>
+<p>In the spring of 2004 a dedicated team of developers began work on what is now FDO Open Source. Our goals were simple, retain all of the best aspects of FDO 6.5 while also meeting the goals set out above. The result is FDO Open Source. Autodesk released FDO Open Source under the LGPL in November 2005, and contributed the code to the Open Source Geospatial Foundation in March 2006.</p>
+-->
+<h3><a name="license" id="license">License</a></h3>
+<p>FDO Open Source is licensed under the <a href="lgpl.html">LGPL</a> (GNU Lesser General Public License). Our <a href="licensing_faq.html">License FAQ</a> provides more information on our license and on our policies regarding the application of the license.</p>
+<h3><a name="governance" id="governance">Governance</a></h3>
+<p>FDO Open Source is part of the Open Source Geospatial Foundation and as such follows the governance structure of the foundation.</p>
+<h3><a name="orgroles" id="orgroles">Organization and Roles</a></h3>
+<ul type="square">
+<li>Project Steering Committee - The Project Steering Committee (PSC) is responsible for the overall management of the FDO Open Source project. The PSC determines when releases will be made available, what enhancements and defects will go into a particular release, and who the Project Developers are. The PSC is also responsible for providing the Open Source Geospatial Foundation board with regular status reports. </li>
+<li>Project Developers - A Project Developer has full commit access to the trunk of the source tree. Project Developers can directly make changes to the source base of the development branch, from which the nightly builds are made. Project Developers review and accept code submitted by Project Contributors. </li>
+<li>Project Contributors - A Project Contributor is a developer who contributes patches, code, and/or documentation through the Project Tracker tool. Project Contributors do not have Subversion check-in access. Integration of a developers' contributions is at the discretion of the Project Owner and individuals in the Project Developer role. This is typically an iterative, communicative process. </li>
+<li>Users - Users are the project’s reason for being. They are the individuals that use and develop applications on the FDO Open Source API. </li>
+</ul>
+</div>
+<div class="h2">
+<h2><a name="product" id="product">Product</a></h2>
+<h3><a name="description" id="description">Product Description</a></h3>
+<!--
+<p>FDO
+ Open Source is a web-based platform that enables users to quickly develop
+ and deploy web mapping applications and geospatial web services.</p>
+<p>FDO features an interactive viewer that includes
+ support for feature selection, property inspection, map tips, and operations
+ such as buffer, select within, and measure. FDO includes an XML database for storing and managing content, and supports most popular geospatial file
+ formats, databases, and standards. The FDO platform can be deployed on Linux
+ or Microsoft Windows, supports Apache and IIS web servers, and offers extensive PHP, .NET, Java, and JavaScript APIs for application development.</p>
+-->
+<h3><a name="features" id="features">Features</a></h3>
+<!--
+<p>The <a href="features.html">Features</a> page lists the features of the FDO Open Source product. It is periodically updated, as new features are added.</p>
+-->
+<h3><a name="links" id="links">Useful Links</a></h3>
+<!--
+<p>Here are some links for information on commercial applications and tools designed to work with FDO Open Source. </p>
+<ul type="square">
+ <li><a href="http://www.autodesk.com/mapguidestudio" target="_blank">Autodesk FDO Studio</a> – free preview available</li>
+ <li><a href="http://www.autodesk.com/dwfviewer">Autodesk DWF Viewer</a> – free download</li>
+</ul>
+-->
+</div>
+<br />
+</body>
+</html>
Added: trunk/www/artifactlifecycle.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/artifactlifecycle.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/artifactlifecycle.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,571 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - Artifact Lifecycle</title>
+</head>
+<body>
+<h1>FDO Open Source - Artifact Lifecycle</h1>
+
+<div class="h2">
+<h2>Overview</h2>
+All artifacts in the FDO Open Source project follow a rigid lifecycle and all project development occurs within that lifecycle. This lifecycle is managed and tracked through the <a href="projectartifacts.html#common">Status Attribute Group</a> that all artifact types share. In particular the value of the <a href="#artifactStatus">Status</a> attribute indicates where in its lifecycle the artifact is. At any point which status transistions are allowed depend upon three things, the current status, the allowed transistions from that status, and the user's role. The following diagram shows the possible status transistions of an artifact.
+<div align="center"><br /><img src="artifactlifecycle.png" alt="Artifact Life Cycle" /></div>
+<p>When an artifacts status moves to Assigned, Resolution Proposed, or Resolved a user must be specified in the "Assigned To" attribute. Likewise when an artifact moves into the Resolved status a Resolution must be set. The following tables show the meanining of each Status value, the Resolution values, and the status transistions allowed for each user role.</p>
+</div>
+
+<div class="h2">
+<a name="artifactStatus" id="artifactStatus"><h2>Artifact Status</h2></a>
+<p>The "Status" attribute of an artifact indicates where in its lifecycle the artifact is. All artifacts start in either the Unconfirmed or New state depending on the role of the person entering the artifact.</p>
+<table width="100%">
+ <tr>
+ <th scope="col">Status Value</th>
+ <th scope="col">Description</th>
+ </tr>
+ <tr class="a">
+ <td>Unconfirmed</td>
+ <td>Initial state of an artifact that has been entered by a User. A Project Contributor, Developer, or Owner is responsible for validating the artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>New</td>
+ <td>Initial state of an issue that has been entered by a Project Contributor, Developer, or Owner.</td>
+ </tr>
+ <tr class="a">
+ <td>Assigned</td>
+ <td>The issue has been accepted and assigned to an individual.</td>
+ </tr>
+ <tr class="b">
+ <td>Resolution Proposed</td>
+ <td>A resolution has been proposed by a Project Contributor. A Project Developer or Owner is responsible for reviewing the proposed resolution and either accepting it or sending it back for additional work. </td>
+ </tr>
+ <tr class="a">
+ <td>Resolved</td>
+ <td>A resolution to the issue has been reached and is awaiting verification from quality assurance.</td>
+ </tr>
+ <tr class="b">
+ <td>Verified</td>
+ <td>Quality assurance has looked at the issue and the resolution and agrees that an adequate resolution has been reached. Issues remain in this state until a version of the project with the resolution is released.</td>
+ </tr>
+ <tr class="a">
+ <td>Closed</td>
+ <td>The issue is considered resolved and a version of the project has been released.</td>
+ </tr>
+ <tr class="b">
+ <td>Reopened</td>
+ <td>The issue was once resolved, but the resolution was deemed incorrect.</td>
+ </tr>
+</table>
+</div>
+
+<div class="h2">
+<a name="artifactResolution" id="artifactResolution"><h2>Artifact Resolutions</h2></a>
+<p>Artifacts in the Resolved state must have one of the following resolution values.</p>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
+ <tr>
+ <th scope="col">Resolution Value</th>
+ <th scope="col">Description</th>
+ </tr>
+ <tr class="a">
+ <td>Submitted</td>
+ <td>A resolution to this issue has been submitted. If the artifact involves the development or modification of code a "Reviewer" should be assigned and that individual should set the Submission Reviewed attribute to Yes once it has been reviewed.</td>
+ </tr>
+ <tr class="b">
+ <td>Invalid</td>
+ <td>The problem described is not an issue or no longer relevant.</td>
+ </tr>
+ <tr class="a">
+ <td>Will Not Address</td>
+ <td>The problem described is an issue which will never be addressed.</td>
+ </tr>
+ <tr class="b">
+ <td>Defer</td>
+ <td>The problem described is an issue which will not be fixed in this release cycle.</td>
+ </tr>
+ <tr class="a">
+ <td>External</td>
+ <td>The problem described cannot be addressed due to problems or limitations in third party components for which we have no control.</td>
+ </tr>
+ <tr class="b">
+ <td>Duplicate</td>
+ <td>The problem described is a duplicate of another issue.</td>
+ </tr>
+ <tr class="a">
+ <td>Not Reproducible</td>
+ <td>The problem as described cannot be reproduced using the information given. This resolution is available only in Defect artifacts.</td>
+ </tr>
+</table>
+</div>
+
+<div class="h2">
+<a name="statusTransitions" id="statusTransitions"><h2>Artifact Status Transitions</h2></a>
+<h3>Allowed Project Owner Transitions</h3>
+<table width="100%">
+ <tr>
+ <th width="20%"> </th>
+ <th colspan="8">TO Status</th>
+ </tr>
+ <tr>
+ <th>FROM Status</th>
+ <th width="10%">Unconfirmed</th>
+ <th width="10%">New</th>
+ <th width="10%">Assigned</th>
+ <th width="10%">ResolutionProposed</th>
+ <th width="10%">Resolved</th>
+ <th width="10%">Verified</th>
+ <th width="10%">Closed</th>
+ <th width="10%">Reopened</th>
+ </tr>
+ <tr class="a">
+ <th>Initial Creation</th>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Unconfirmed</th>
+ <td> </td>
+ <td>X</td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>New</th>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Assigned</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>ResolutionProposed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="b">
+ <th>Resolved</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="a">
+ <th>Verified</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td>X</td>
+ </tr>
+ <tr class="b">
+ <th>Closed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="a">
+ <th>Reopened</th>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+</table>
+<h3>Allowed Project Developer Transitions</h3>
+<table width="100%">
+ <tr>
+ <th width="20%"> </th>
+ <th colspan="8">TO Status</th>
+ </tr>
+ <tr>
+ <th>FROM Status</th>
+ <th width="10%">Unconfirmed</th>
+ <th width="10%">New</th>
+ <th width="10%">Assigned</th>
+ <th width="10%">ResolutionProposed</th>
+ <th width="10%">Resolved</th>
+ <th width="10%">Verified</th>
+ <th width="10%">Closed</th>
+ <th width="10%">Reopened</th>
+ </tr>
+ <tr class="a">
+ <th>Initial Creation</th>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Unconfirmed</th>
+ <td> </td>
+ <td>X</td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>New</th>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Assigned</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>ResolutionProposed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="b">
+ <th>Resolved</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="a">
+ <th>Verified</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="b">
+ <th>Closed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="a">
+ <th>Reopened</th>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+</table>
+<h3>Allowed Project Contributor Transitions</h3>
+<table width="100%">
+ <tr>
+ <th width="20%"> </th>
+ <th colspan="8">TO Status</th>
+ </tr>
+ <tr>
+ <th>FROM Status</th>
+ <th width="10%">Unconfirmed</th>
+ <th width="10%">New</th>
+ <th width="10%">Assigned</th>
+ <th width="10%">ResolutionProposed</th>
+ <th width="10%">Resolved</th>
+ <th width="10%">Verified</th>
+ <th width="10%">Closed</th>
+ <th width="10%">Reopened</th>
+ </tr>
+ <tr class="a">
+ <th>Initial Creation</th>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Unconfirmed</th>
+ <td> </td>
+ <td>X</td>
+ <td>X</td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>New</th>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Assigned</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>ResolutionProposed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="b">
+ <th>Resolved</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="a">
+ <th>Verified</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="b">
+ <th>Closed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ </tr>
+ <tr class="a">
+ <th>Reopened</th>
+ <td> </td>
+ <td> </td>
+ <td>X</td>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+</table>
+<h3>Allowed User/Non Contributor Transitions</h3>
+<table width="100%">
+ <tr>
+ <th width="20%"> </th>
+ <th colspan="8">TO Status</th>
+ </tr>
+ <tr>
+ <th>FROM Status</th>
+ <th width="10%">Unconfirmed</th>
+ <th width="10%">New</th>
+ <th width="10%">Assigned</th>
+ <th width="10%">ResolutionProposed</th>
+ <th width="10%">Resolved</th>
+ <th width="10%">Verified</th>
+ <th width="10%">Closed</th>
+ <th width="10%">Reopened</th>
+ </tr>
+ <tr class="a">
+ <th>Initial Creation</th>
+ <td>X</td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Unconfirmed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>New</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Assigned</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>ResolutionProposed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Resolved</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>Verified</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="b">
+ <th>Closed</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+ <tr class="a">
+ <th>Reopened</th>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+</table>
+</div>
+</body>
+</html>
Added: trunk/www/artifactlifecycle.png
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/artifactlifecycle.png?view=auto&rev=25
==============================================================================
Binary file. No diff available.
Added: trunk/www/developer.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/developer.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/developer.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - Getting Involved as a Contributor</title>
+</head>
+
+<body>
+<h1>FDO Open Source - Getting Involved as a Contributor</h1>
+<p><strong>NOTE: All of the information on this page is subject to change as the Open Source Geospatial Foundation makes decisions regarding its governance.</strong></p>
+
+<p>There are three different levels of involvement for developers interested in contributing to FDO Open Source. These levels of involvement are as follows:</p>
+<ul type="square">
+ <li><strong>Project Contributor</strong> - A Project Contributor is a developer who contributes patches, code, and/or documentation through the Project Tracker tool. Project Contributors do not have Subversion check-in access. Integration of a developer's contributions is at the discretion of the FDO Open Source Project Steering Comittee (PSC) and individuals in the Project Developer role. This is typically an iterative, communicative process.</li>
+ <li><strong>Project Developer</strong> - A Project Developer has full commit access to the trunk of the source tree and has a signed Contributor License Agreement on file with OSGeo. Project Developers can directly make changes to the source base of the development branch, from which the nightly builds are made. Project Developers review and accept code submitted by Project Contributors. Project Developers are elected by the PSC.</li>
+ <li><strong>Project Steering Committee (PSC) Member </strong>– The FDO Open Source PSC is the entity that manages the project. A PSC Member is a Project Developer that was elected to the FDO Open Source PSC due to the developer’s merit and active participation in the project. PSC Members have full commit access to the code repository, the right to vote for project-related decisions, and the right to propose individuals for Project Developer status.</li>
+</ul>
+<p>All developers on the project start out as Project Contributors. A developer who has sent in solid, useful patches can be elevated to the Project Developer role by the Project Steering Committee (PSC). To become a Project Contributor use the <a href="https://fdo.osgeo.org/servlets/ProjectMembershipRequest">Request project membership/role</a> link at the top of the FDO Open Source project home page and request the Project Contributor role. </p>
+<p>Please note that the Open Source Geospatial Foundation is currently defining its governance model and intellectual property policies, including the policy under which the OSGeo accepts code contributions from developers. Until these policies are fully defined, we cannot grant Project Developer status to any individual. It is expected that developers will be asked to sign a Contributor License Agreement similar to what Apache Software Foundation requires before becoming a Project Developer or PSC Member.<br />
+</p>
+
+<div class="h2">
+<h2>Join the Mailing Lists</h2>
+<p>Join the mailing lists to participate in development activities. The dev at fdo.osgeo.org is the primary channel of communication for developers working on the project. You can also sign up for the issues at fdo.osgeo.org or commits at fdo.osgeo.org mailing lists to watch development activity. If you are a registered user, <a href="https://fdo.osgeo.org/servlets/ProjectMailingListList">click here to sign up</a> to sign up for one or more of these lists. </p>
+To browse archives of any of the mailing lists, select the <a href="https://fdo.osgeo.org/servlets/ProjectMailingListList">Mailing lists</a> link under Project tools.</div>
+
+<div class="h2">
+<h2>Developer Resources</h2>
+<p>The following resources are available to help developers get started working on FDO Open Source:</p>
+<ul type="square">
+ <li>Development Process [Coming Soon]</li>
+ <li><a href="projectartifacts.html">Project Artifacts</a></li>
+ <li><a href="artifactlifecycle.html">Artifact Lifecycle</a></li>
+ <li>Contributing Patches [Coming Soon]</li>
+ <li>Coding Guidelines [Coming Soon]</li>
+ <li><a href="subversionconfig.html">Subversion Client Configuration</a></li>
+</ul>
+</div>
+
+<div class="h2">
+<h2>Areas of Need</h2>
+<p>If you are looking to get involved the following aspects of FDO Open Source could use your help:</p>
+<ul type="square">
+ <li>Bug Fixes - FDO Open Source is a 1.0.0 release and as such, probably contains a bug or two that needs to be fixed.</li>
+ <li>Platform Expansion - FDO Open Source is currently only being built and tested on Red Hat Enterprise 3 and Fedora Core 4. Updates to the code and make files to support as many Linux distributions as possible is greatly encouraged.</li>
+ <li>Localization into new Languages - FDO Open Source is globalized and has been localized in English. Support for additional locales is very desirable. </li>
+</ul>
+</div>
+
+</body>
+</html>
Added: trunk/www/faq.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/faq.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/faq.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,25 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - FAQ</title>
+</head>
+<body>
+<h1>FDO Open Source - FAQ</h1>
+These FAQ's are updated regularly as questions arise, so check back if you don't
+see what you are looking for.
+<div class="h2">
+<h2>Topics</h2>
+<!--
+<p><a href="faq_general.html">General</a></p>
+<p><a href="faq_installandconfigure.html">Install and Configure</a></p>
+<p><a href="faq_dataloadandconnect.html">Data Load and Connect</a></p>
+<p><a href="faq_layerandmapdefinition.html">Layer and Map Definition</a></p>
+<p><a href="faq_applicationdevelopment.html">Application Development</a></p>
+<p><a href="faq_ogcserices.html">Open Geospatial Services</a></p>
+<p><a href="faq_license.html">License</a></p>
+<p><a href="faq_mapguidemigration.html">FDO 6.x Migration</a></p>
+-->
+</div>
+</body>
+</html>
Modified: trunk/www/index.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/index.html?view=diff&rev=25&p1=trunk/www/index.html&p2=trunk/www/index.html&r1=24&r2=25
==============================================================================
--- trunk/www/index.html (original)
+++ trunk/www/index.html 2006-05-17 20:49:48+0000
@@ -31,6 +31,7 @@
<h1>Feature Data Objects - Project Home</h1>
Welcome to the home of Feature Data Objects.
+ <p>FDO Open Source is a new Data Objects API that was originally developed by Autodesk and contributed to the Open Source Geospatial Foundation. Learn more, get involved or download the software today. There are several ways to participate either as a <a href="user.html">user</a> or <a href="developer.html">contributor</a>. Your participation is welcome!</p>
<div class="h2"><h2>Description</h2>
<p>Feature Data Objects (FDO) is an API for manipulating, defining, and analyzing geospatial information regardless of where it is stored. FDO uses a provider-based model for supporting a variety of geospatial data sources, where each provider typically supports a particular data format or data store.</p>
<p>At this point Feature Data Objects is being offered as a preview for use with MapGuide Open Source. The links below allow you to download a full copy of the source code with FDO providers for ESRI SHP and a new format created for MapGuide called the Spatial Database Format (SDF). FDO will become a full open-source project in the coming months, so stay tuned to this page for more information, additional providers, and the launch of FDO as an active open source project. </p>
@@ -45,8 +46,19 @@
<div class="h2">
<h2>Releases</h2>
<p><a href="downloads.html">Downloads</a></p>
- <p><a href="documentation.html">Documentation</a></p><br>
+ <p><a href="documentation.html">Documentation</a></p>
+ </div>
+ <div class="h2"><h2>Essentials</h2>
+ <p><a href="about.html">About</a></p>
+<!--
+ <p><a href="features.html">Features</a></p>
+ <p><a href="system_requirements.html">Requirements</a></p>
+ <p><a href="gettingstarted.html">Getting Started</a></p>
+-->
+ <p><a href="faq.html">FAQ</a></p>
+ <div class="h2"><h2>Get Involved</h2>
+ <p><a href="user.html">As a User</a></p>
+ <p><a href="developer.html">As a Contributor</a></p>
</div>
-
</body>
</html>
Added: trunk/www/projectartifacts.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/projectartifacts.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/projectartifacts.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,295 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - Project Artifacts</title>
+</head>
+<body>
+<h1>FDO Open Source - Project Artifacts</h1>
+<div class="h2">
+<h2>Overview</h2>
+The FDO Open Source development process uses "Artifacts" to track and manage defects, enhancements, and tasks. All changes to FDO source code must be tied to an artifact. The Project Tracker application provides a database for storing artifacts along with a web based interface for entering, modifying, and querying artifacts. Each artifact type has a unique collection of "Attributes" (or fields) much like the attributes in a database table. Attributes are presented in "Attribute Groups" that gather related attributes into logical groupings. Users are associated with artifacts via special "User Attributes". All users associated with an artifact are notified any time the artifact changes.
+<h3>FDO Open Source Artifact Types</h3>
+FDO Open Source supports the following three artifact types:
+<ul type="square">
+ <li><a href="#defect">Defect</a> - Used to record and track bugs in an existing component or feature.</li>
+ <li><a href="#enhancement">Enhancement</a> - Used to record and track the development of product enhancements.</li>
+ <li><a href="#task">Task</a> - Used to record and track work that needs to be done and work in progress.</li>
+</ul>
+All of these artifact types have a common collection of Attribute Groups (<a href="#common">found here</a>) that are used for tracking the status or lifecycle of artifacts, providing information about code submissions, and for associating users with artifacts.<br />
+<br />
+To understand how artifacts progress through their lifecycle go <a href="artifactlifecycle.html">here</a>.
+</div>
+<div class="h2">
+<h2><a name="defect" id="defect">Defect Artifact Type</a></h2>
+Defect artifacts are used to record and track bugs in an existing component or feature.
+<table width="100%">
+ <tr>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Synopsis Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Summary</td>
+ <td>Brief one line description of the artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Defect Severity</td>
+ <td><p>Severity of the defect with respect to the usability of the product, one of:<br />
+ Critical – defect that results in program crash, data corruption, or data loss.<br />
+ High – frequently encountered defect without a known work-around.<br />
+ Medium – defect that has a workaround.<br />
+ Low – low impact defect. </p>
+ </td>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Details Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Description</td>
+ <td>Detailed description of the artifact. Attach any supporting materials, documents, screenshots, etc. to the artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Steps to Reproduce</td>
+ <td>Step by step instructions describing how to repoduce the defect.</td>
+ </tr>
+ <tr class="b">
+ <td>Version</td>
+ <td>Version of the product this artifact was logged against.</td>
+ </tr>
+ <tr class="b">
+ <td>Component</td>
+ <td>The component this artifact affects. See <a href="#components">Components and Subcomponents</a> for a list of the possible values. </td>
+ </tr>
+ <tr class="b">
+ <td>Subcomponent</td>
+ <td>The subcomponent this artifact affects. See <a href="#components">Components and Subcomponents</a> for a list of the possible values.</td>
+ </tr>
+ <tr class="b">
+ <td>Platform</td>
+ <td>Platform associated with this artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Operating System</td>
+ <td>Operating System associated with this artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>OS Distribution and Version</td>
+ <td>Particular distribution and version of the operating system associated with this artifact.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2"><a href="#common">Attribute Groups Common to all Artifact Types</a></td>
+ </tr>
+</table>
+<h3><a name="components" id="components">Components and Subcomponents</a></h3>
+<table width="100%">
+ <tr>
+ <th scope="col">Component</th>
+ <th scope="col">Possible Values for Subcomponent</th>
+ </tr>
+</table>
+
+</div>
+
+<div class="h2">
+<h2><a name="enhancement" id="enhancement">Enhancement Artifact Type</a></h2>
+Enhancement artifacts are used to record and track the development of product enhancements.
+<table width="100%">
+ <tr>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Synopsis Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Summary</td>
+ <td>Brief one line description of the artifact.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Details Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Description</td>
+ <td>Detailed description of the artifact. Attach any supporting materials, documents, screenshots, etc. to the artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Justification</td>
+ <td>Description of why this enhancement is a good idea.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2"><a href="#common">Attribute Groups Common to all Artifact Types</a></td>
+ </tr>
+</table>
+</div>
+
+<div class="h2">
+<h2><a name="task" id="task">Task Artifact Type</a></h2>
+Task artifacts are used to record and track work that needs to be done and work in progress. Note that tasks need not be related to product development activities. Some examples of non development related tasks might be: document a process, write a document on security, define or modify governance rules, things related to conference preparation, etc.
+<table width="100%">
+ <tr>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Synopsis Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Summary</td>
+ <td>Brief one line description of the artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Task Priority</td>
+ <td>Priority of this task, High, Medium, or Low.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Details Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Description</td>
+ <td>Detailed description of the artifact. Attach any supporting materials, documents, screenshots, etc. to the artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Need By Date</td>
+ <td>Date by which this task needs to be completed. (optional)</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Task Progress Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Planned Start Date</td>
+ <td>Date this task is planned to start.</td>
+ </tr>
+ <tr class="b">
+ <td>Planned Completion Date</td>
+ <td>Date this task is planned to be completed.</td>
+ </tr>
+ <tr class="b">
+ <td>Actual Start Date</td>
+ <td>Actual date this task was started.</td>
+ </tr>
+ <tr class="b">
+ <td>Actual Completion Date</td>
+ <td>Actual date this task was completed.</td>
+ </tr>
+ <tr class="b">
+ <td>Percent Complete</td>
+ <td>Percentage of the work on this task that is currently complete.</td>
+ </tr>
+ <tr class="b">
+ <td>Progress Notes</td>
+ <td>Notes describing the progress made to date on this task.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2"><a href="#common">Attribute Groups Common to all Artifact Types</a></td>
+ </tr>
+</table>
+</div>
+
+<div class="h2">
+<h2><a name="common" id="common">Attribute Groups Common to All Artifacts</a></h2>
+These attribute groups are common to all artifact types. These groups are related to tracking status and resolution, documenting relevant information about project submissions, and the artifact user associations.
+<table width="100%">
+ <tr>
+ <th scope="col">Attribute</th>
+ <th scope="col">Description</th>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Status Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Priority</td>
+ <td>Development priority of this artifact P1 - P5, where P1 is the highest priority.</td>
+ </tr>
+ <tr class="b">
+ <td>Artifact Status</td>
+ <td>Current status of this artifact. See <a href="artifactlifecycle.html">Artifact Lifecycle</a>.</td>
+ </tr>
+ <tr class="b">
+ <td>Status Explanation</td>
+ <td>Explanation of the current artifact status.</td>
+ </tr>
+ <tr class="b">
+ <td>Target Milestone</td>
+ <td>Planned milestone by which this artifact should be resolved.</td>
+ </tr>
+ <tr class="b">
+ <td>Artifact Resolution</td>
+ <td>How this artifact was resolved. See <a href="artifactlifecycle.html">Artifact Lifecycle</a></td>
+ </tr>
+ <tr class="b">
+ <td>Resolution Description</td>
+ <td>Description of the resolution to this artifact.</td>
+ </tr>
+ <tr class="b">
+ <td>Build</td>
+ <td>Build number that includes a resolution for this artifact if applicable.</td>
+ </tr>
+ <tr class="b">
+ <td>Submission Reviewed</td>
+ <td>Indication of whether the submitted resolution has been reviewed, Yes or No.</td>
+ </tr>
+ <tr class="b">
+ <td>Review Comments</td>
+ <td>Comments from the Reviewer regarding the submitted resolution.</td>
+ </tr>
+ <tr class="b">
+ <td>Duplicate Artifacts</td>
+ <td>List of artifacts that are duplicates of this one. Required if the resolution is "Duplicate".</td>
+ </tr>
+ <tr class="b">
+ <td>Related Artifacts</td>
+ <td>List of artifacts that may be related to this one.</td>
+ </tr>
+ <tr class="b">
+ <td>External ID</td>
+ <td>External ID that can be used to reference an item in another system that corresponds to this artifact.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2">Submission Notes Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Developer Notes</td>
+ <td>Notes about this code submission to developers regarding unit test results, work yet to be done, and/or changes that may affect other developers.</td>
+ </tr>
+ <tr class="b">
+ <td>Testing Notes</td>
+ <td>Notes about this code submission regarding how to test the code and/or regressions that should be run.</td>
+ </tr>
+ <tr class="b">
+ <td>Documentation Notes</td>
+ <td>Notes about this code submission regarding changes that may affect documentation.</td>
+ </tr>
+ <tr class="b">
+ <td>Localization Notes</td>
+ <td>Notes about this code submission regarding changes that may affect localization.</td>
+ </tr>
+ <tr class="b">
+ <td>Integration and Build Notes</td>
+ <td>Notes about this code submission that may affect integration or builds.</td>
+ </tr>
+ <tr class="a">
+ <td colspan="2">User Association Attribute Group</td>
+ </tr>
+ <tr class="b">
+ <td>Assigned To</td>
+ <td>The person this artifact is assigned to.</td>
+ </tr>
+ <tr class="b">
+ <td>Reviewer</td>
+ <td>The person responsible for reviewing this artifact's resolution.</td>
+ </tr>
+ <tr class="b">
+ <td>Verifier</td>
+ <td>The person responsible for verifying this artifact has been resolved.</td>
+ </tr>
+ <tr class="b">
+ <td>Interested Parties</td>
+ <td>Anyone interested in monitoring the progress of this artifact.</td>
+ </tr>
+</table>
+</div>
+</body>
+</html>
Added: trunk/www/subversionconfig.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/subversionconfig.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/subversionconfig.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,52 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - Subversion Configuration</title>
+</head>
+
+<body>
+<h1>FDO Open Source - Subversion Client Configuration</h1>
+<p>There are a couple of client-side configuration settings that need to be set to ensure things work smoothly when commiting changes in Subversion. These are especially important to ensure smooth nightly builds on Linux.<br />
+<br />
+All client settings are specified in a configuration file which you'll want to open for editing:</p>
+<ul>
+ <li>under Windows: open the file "C:\Documents and Settings\‹username›\Application Data\Subversion\config" (if you use TortoiseSVN then you can also open this file via the TortoiseSVN UI)</li>
+ <li>under Linux: open the file "~/.subversion/config"</li>
+</ul>
+
+<dl>
+ <dt>1. Enable use of commit times</dt>
+ <dd>Locate the "use-commit-times" setting in the configuration file, and make sure it is enabled:<br />
+ <br />
+ use-commit-times = yes<br />
+ <br />
+ If you don't enable this then there's a good chance you'll have build errors under Linux. File time-stamps need to be set correctly under Linux to ensure 'make' works properly.
+ </dd>
+
+ <dt>2. Enable the use of auto props</dt>
+ <dd>Locate the "enable-auto-props" setting in the configuration file, and make sure it is enabled:<br />
+ <br />
+ enable-auto-props = yes<br />
+ <br />
+ By enabling this you ensure that metadata gets automatically added for any new files you add to Subversion. An example is the eol-style property.
+ </dd>
+
+ <dt>3. Configure automatic properties</dt>
+ <dd>Subversion contains a number of properties (metadata) you can set per file. At the end of your config file is the [auto-props] section where you can specify which properties get automatically set when you add a file. At a minimum you must set the svn:eol-style property:<br />
+ <br />
+ * = svn:eol-style=native<br />
+ <br />
+ By default the config file has examples to specify different values for this property for different file types. Just set it to native for all file types as above and be done with it.<br />
+ <br />
+ If you frequently edit Linux shell scripts then you might want to also configure the executable property:<br />
+ <br />
+ *.sh = svn:executable=yes<br />
+ <br />
+ This makes all shell scripts executable, by default.
+ </dd>
+
+</dl>
+</body>
+
+</html>
Added: trunk/www/user.html
Url: https://fdo.osgeo.org/source/browse/fdo/trunk/www/user.html?view=auto&rev=25
==============================================================================
--- (empty file)
+++ trunk/www/user.html 2006-05-17 20:49:48+0000
@@ -0,0 +1,31 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<title>FDO Open Source - Getting Involved as a User</title>
+</head>
+<body>
+<h1>FDO Open Source - Getting Involved as a User</h1>
+<p>There are two different levels of involvement for users and application developers depending on whether you are a registered user or not. Unregistered users can download and install the software, join and participate in the mailing lists (using the links below), browse the mailing list archives, browse the source code in Subversion, and access all of the documentation and information on this site.</p>
+<p>If you register as a user of the <a href="http://www.osgeo.org">osgeo.org</a> website and become a member of the FDO Open Source project, you can directly manage your mailing list subscriptions using the tools on this site and use the Project Tracker tool to browse and enter defects and enhancement requests. You can register as user on the <a href="http://www.osgeo.org">osgeo.org</a> site by selecting the <a href="https://www.osgeo.org/servlets/Join">Register</a> link at the top right corner of the Open Source Geospatial Foundation banner. Once you are a registered user, you can request to become a project member with a user role using the <a href="https://fdo.osgeo.org/servlets/ProjectMembershipRequest">Request project membership/role</a> link at the top of the FDO Open Source project home page. </p>
+<div class="h2">
+<h2>Join the Mailing Lists</h2>
+<p>Join the mailing lists to learn what other users are doing with FDO Open Source, ask questions, get answers, and when you get comfortable jump in and answer questions. The users at fdo.osgeo.org mailing list provides a wealth of information for all FDO Open Source users from novices to experts. Find out about new releases and events related to FDO Open Source on the announce at fdo.osgeo.org mailing list. If you are a registered user <a href="/servlets/ProjectMailingListList">click here to sign up</a>. If you are not a registered user, use one of these links:</p>
+<ul type="square">
+ <li>Subscribe to the users list: <a href="mailto:users-subscribe at fdo.osgeo.org">users-subscribe at fdo.osgeo.org</a><br />or the users digest: <a href="mailto:users-digest-subscribe at fdo.osgeo.org">users-digest-subscribe at fdo.osgeo.org</a></li>
+ <li>Subscribe to the announce list: <a href="mailto:announce-subscribe at fdo.osgeo.org">announce-subscribe at fdo.osgeo.org</a><br />or the announce digest: <a href="mailto:announce-digest-digest-subscribe at fdo.osgeo.org">announce-digest-subscribe at fdo.osgeo.org</a></li>
+</ul>
+To browse archives of any of the mailing lists, select the <a href="https://fdo.osgeo.org/servlets/ProjectMailingListList">Mailing lists</a> link under Project tools.
+</div>
+<div class="h2">
+<h2>Entering Defects and Enhancements</h2>
+<p>As a registered user and member of the FDO Open Source project, you can use the Project Tracker tool to browse and enter defects and enhancement requests. You can access the <a href="https://fdo.osgeo.org/servlets/Scarab">Project Tracker</a> tool from anywhere on the site using the link under Project tools. The following links will provide some guidence for using Project Tracker and entering artifacts (Defects or Enhancements).</p>
+<ul type="square">
+ <li><a href="https://fdo.osgeo.org/nonav/servlets/Scarab/template/help,Introduction.vm">Introduction to Project Tracker</a></li>
+ <li><a href="https://fdo.osgeo.org/nonav/servlets/TrackerHelp/template/help,UserIssueEntry.vm#entering">Entering Artifacts</a></li>
+ <li><a href="projectartifacts.html">FDO Project Artifact Definitions</a></li>
+</ul>
+</div>
+<br />
+</body>
+</html>
More information about the Fdo-commits
mailing list