0.14.7 updates

git-svn-id: http://mantisbt.svn.sourceforge.net/svnroot/mantisbt/trunk@239 f5dc347c-c33d-0410-90a0-b07cc1902cb9

mantis.php3

@@ -27,19 +27,12 @@ p {  font-family:Verdana, Arial; font-size=10pt }
 Mantis is a php/MySQL/web based bugtracking system.  The software resides on a webserver while any web browser should be able to function as a client.  It is released under the terms of the <a href="http://www.gnu.org/copyleft/gpl.html">GNU GPL license</a>.
 <p>
 I and a friend originally created a bugtracker as an internal tool for our own pet project.  Since then I've gone ahead with a total rewrite and decided to make it available to the public.  A check on the web in early 2000 revealed that there were no free php based bug tracking packages that were usable (I may be mistaken).  Hopefully, this package helps fill that niche.  I have no strong love of the GPL but I do feel that development tools should be free for developers, thus my choice of license.
-<p>
-The release numbering convention I'm using is major.minor.micro.  Major indicates a large change in the core package, minor a significant amount of feature addition/modification, micro for mostly bug fixes.  I am leaning towards releasing a new version for a significant bugfix as often as daily.
-
-<p>
-<b><font size=+1>Goals</font></b>
-<p>
-The stated goals for this project are to produce and maintain a lightweight, simple bugtracking system.  Additions of complexity/features should be modular so that users can be shielded from unwanted complexity.  Thus, much of the package allows for a simple version of a feature along with a more fully developed but complex version.  In the 'core' package the goal is to have the most important, most used, most time saving portions of a bugtracking system.  Hopefully this gives you 90% of the functionality that you need. The product is designed, to the best of the developer's abilities, to be easily modifiable and customizable and upgradeable.
 
 <p>
 <b><font size=+1>Requirements</font></b>
 <p>
-<li><a href="http://www.php.net/">php</a> 3.0.13 and higher
-<li><a href="http://www.mysql.com/">MySQL database</a> (check back to see when new databases are added)
+<li><a href="http://www.php.net/">php</a> 3.0.13 and higher (this might drop back down to 3.0.7)
+<li><a href="http://www.mysql.com/">MySQL database</a> (more support is planned)
 <li>Web server (<a href="http://www.apache.org/">apache</a>, IIS, etc.)
 <p>
 Additionally you will need to know basic administration of MySQL (login, create new database, run a SQL query).  The webserver needs to be configured to handle php files at a minimum.
@@ -53,32 +46,59 @@ I highly recommend using <a href="http://www.phpwizard.net">phpMyAdmin</a> to ad
 <p>
 <li>Web based and platform independent
 <li>Supports PHP3 and PHP4
-<li>Mailing module
+<li>Emailing module
 <li>Multiple project support
-<li>Configuration files allow for site-wide control
+<li>Multiple language support
 <li>Integrated user and site management
 <li>Integrated news management
 <li>Color coding according to bug status
-<li>Note addition capability for each bug
+<li>Note addition capability
 <li>Shows which bugs have been modified in last X hours
 <li>Stored user profiles
 <li>Complex viewing filters
-<li>Detailed summary reports
-<li>ETA and projection for each bug
+<li>Configuration files allow for site-wide control
 
 <p>
 <b><font size=+1>Upcoming Features</font></b>
 <p>
 Check the <a href="roadmap.php3">Roadmap</a> for a more detailed and up to date list of items.
+
+<p>
+<b><font size=+1>Goals</font></b>
+<p>
+The stated goals for this project are to produce and maintain a lightweight, simple bugtracking system.  Additions of complexity/features should be modular so that users can be shielded from unwanted complexity.  Thus, much of the package allows for a simple version of a feature along with a more fully developed but complex version.  In the 'core' package the goal is to have the most important, most used, most time saving portions of a bugtracking system.  Hopefully this gives you 90% of the functionality that you need. The product is designed, to the best of the developer's abilities, to be easily modifiable and customizable and upgradeable.
+
+<p>
+<b><font size=+1>Guidelines</font></b>
+<p>
+Here are some of the guidelines that I have decided upon:
+<ul>
+<li>Simple navigation
+<li>Layered complexity
+<li>Quick access to "What I want to do"
+<li>Consistency
+<li>Minimal clutter
+<li>Minimal graphics
+<li>No frames
+<li>No animations
+<li>No Javascript
+</ul>
+<p>
+I realize I have some problems with some of the above points.  I'll be addressing them as they come to my notice or cross my annoyance threshold.
+
+<p>
+<b><font size=+1>Versioning</font></b>
+<p>
+The release numbering convention I'm using is major.minor.micro.  Major indicates a large change in the core package, minor a significant amount of feature addition/modification, micro for mostly bug fixes.  I am leaning towards releasing a new version for a significant bugfix as often as daily.
+
 <p>
 <b><font size=+1>How to Help</font></b>
 <p>
 <li>Report any bugs at the <a href="demo.php3">Demo Bugtracker</a>
 <li>Suggest (reasonable) features
 <li>Contribute code or tell me where to look
-<li>Join the development team!  Send me an email detailing what you would like to help out on.
-<li>Let me know if you use it and find it useful.
-I won't publish the information without permission, but I would appreciate the feedback.  It keeps me motivated.
+<li><b>Let me know if you use it and find it useful</b>.
+I won't publish the information without permission, but I would appreciate the feedback.  This, more than anything, keeps me motivated.
 </td>
 </tr>
 </table>

roadmap.php3

@@ -28,14 +28,11 @@ This is the Mantis feature roadmap.  It lists most fo the currently planned feat
 <ul>
 <li>Email notification perferences per user
 <li>Optional HTML escpaing
-<li>Project title in page title
 <li>Icon module
 <li>Change date_created/added to a varchar(14)
 <li>After reporting bug, allow choice of navigation
-<li>Check for already logged in status on login page
 <li>List modified files for each release
 <li>Split core_API into file modules
-<li>Add email string localizations
 <li>Eliminate strtotime()
 <li>Switch from enums to indexes
 <li>Switch from char(3) to indexes