Skip to content

Commit

Permalink
This commit was generated by cvs2svn to compensate for changes in r163,
Browse files Browse the repository at this point in the history 
which included commits to RCS files with non-trunk default branches.


git-svn-id: http://mantisbt.svn.sourceforge.net/svnroot/mantisbt/trunk@164 f5dc347c-c33d-0410-90a0-b07cc1902cb9
  • Loading branch information
prescience committed Feb 8, 2001
0 parents commit 31fff94
Show file tree
Hide file tree
Showing 18 changed files with 848 additions and 0 deletions.
37 changes: 37 additions & 0 deletions cvs.php3
@@ -0,0 +1,37 @@
<html>
<head>
<style>
body { background-color:#ffffff; font-family:Verdana, Arial; font-size=10pt }
td { font-family:Verdana, Arial; font-size=10pt }
p { font-family:Verdana, Arial; font-size=10pt }
</style>
<title>Mantis</title>
</head>
<body bgcolor=#ffffff>

<p>
<div align=center>
<h2>Mantis</h2>
</div>

<p>
<div align=center>

<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
<td>
<b><font size=+1>CVS</font></b>
<p>

</td>
</tr>
</table>

<p>
<div align=right>
<A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=14963" width="88" height="31" border="0" alt="SourceForge Logo"></A>
</div>

</body>
</html>
45 changes: 45 additions & 0 deletions database.php3
@@ -0,0 +1,45 @@
<html>
<head>
<style>
body { background-color:#ffffff; font-family:Verdana, Arial; font-size=10pt }
td { font-family:Verdana, Arial; font-size=10pt }
p { font-family:Verdana, Arial; font-size=10pt }
</style>
<title>Mantis</title>
</head>
<body>

<p>
<div align=center>
<h2>Mantis</h2>
</div>

<p>
<div align=center>

<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
<td>
<p>
<b><font size=+1>Database Schema</font></b>
<p>
This is a basic view of the database schema used in Mantis. In my defense it was my first try at a decently sized project and the project has grown out of its original design. It should and will be re-normalized 'soon'. The schemas are a bit rough right now. I should add indicators for index, primary keys, 'foreign keys' (mysql doesn't support these, you have to fake them), unique fields, and relationships (1 to 1, 1 to many, etc).
<p>
<ul>
<li><a href="mantis-0.14.0.gif">version 0.14.1</a> <? echo round(filesize("mantis-0.14.0.gif") / 1024) ?>KB
<li><a href="mantis-0.13.0.gif">version 0.9.0 to 0.13.1</a> <? echo round(filesize("mantis-0.13.0.gif") / 1024) ?>KB
</ul>
<p>
Any database experts who'd like to offer their insights can email me.
</td>
</tr>
</table>

<p>
<div align=right>
<a href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=14963" width="88" height="31" border="0" alt="SourceForge Logo"></A>
</div>

</body>
</html>
53 changes: 53 additions & 0 deletions demo.php3
@@ -0,0 +1,53 @@
<html>
<head>
<style>
body { background-color:#ffffff; font-family:Verdana, Arial; font-size=10pt }
td { font-family:Verdana, Arial; font-size=10pt }
p { font-family:Verdana, Arial; font-size=10pt }
</style>
<title>Mantis</title>
</head>
<body>

<p>
<div align=center>
<h2>Mantis</h2>
</div>

<p>
<div align=center>

<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
<td>
<p>
<b><font size=+1>Demo Bugtracker</font></b>
<p>
Here you can login to report actual bugs in Mantis. You may also log feature requests as well. Finally, just use it to play around and see if it meets your needs.
<p>
Login as:
<ul>
<li>viewer / viewer - most limited access
<li>reporter / reporter - you can report bugs and add bugnotes
<li>rep / rep - same
<li>updater / updater - you can edit bugs
<li>Sign up for your own account! You will need a valid email address.
</ul>
<p>
Again, feel free to explore but please, do not mess around with any valid bug entries. I will periodically be cleaning out any test bugs.
<p>
<div align=center>
<a href="http://mantisbt.sourceforge.net/mantis/"><b>Demo Bugtracker</b></a>
</div>
</td>
</tr>
</table>

<p>
<div align=right>
<a href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=14963" width="88" height="31" border="0" alt="SourceForge Logo"></A>
</div>

</body>
</html>
46 changes: 46 additions & 0 deletions download.php3
@@ -0,0 +1,46 @@
<html>
<head>
<style>
body { background-color:#ffffff; font-family:Verdana, Arial; font-size=10pt }
td { font-family:Verdana, Arial; font-size=10pt }
p { font-family:Verdana, Arial; font-size=10pt }
</style>
<title>Mantis</title>
</head>
<body>

<p>
<div align=center>
<h2>Mantis</h2>
</div>

<p>
<div align=center>

<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
<td>
<p>
<b><font size=+1>Download</font></b>
<p>
Use the link to get to the download site for Mantis. The package is kept in .tar.gz which any reasonable (unix systems, WInzip, Stuffit) decompression program can handle.
<p>
<div align=center>
<a href="http://sourceforge.net/project/showfiles.php?group_id=14963&release_id=19129"><b>Download Mantis</b></a>
</div>

<b><font size=+1>Mirroring</font></b>
<p>
I would prefer that you sign up on the announcements <a href="mailinglists.php3">mailing list</a> if you wish to mirror the software. You should also have a link back to this page if you offer Mantis for download.
</td>
</tr>
</table>

<p>
<div align=right>
<A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=14963" width="88" height="31" border="0" alt="SourceForge Logo"></A>
</div>

</body>
</html>
94 changes: 94 additions & 0 deletions guidelines.php3
@@ -0,0 +1,94 @@
<html>
<head>
<style>
body { background-color:#ffffff; font-family:Verdana, Arial; font-size=10pt }
td { font-family:Verdana, Arial; font-size=10pt }
p { font-family:Verdana, Arial; font-size=10pt }
</style>
<title>Mantis</title>
</head>
<body bgcolor=#ffffff>

<p>
<div align=center>
<h2>Mantis</h2>
</div>

<p>
<div align=center>

<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
</td>
<td>
<h3>Mantis Coding Conventions</h3>

<p>
This is the Mantis coding conventions document. It lists all the basic conventions that I have followed in order to make the code easy to read and maintain. ANyone working on the code, adding features, or wanting to send in a patch should take a quick look through this document. Currently the code is very flat and procedure based. A future version may switch to objects at which point some of these conventions may change or be added to.

<p>

<h3>Naming</h3>
<ul>
<li>Use descriptive names (except loop variables)
<li>Use _ to separate words
<li>Always use lowercase
<li>Use .php3 or .php for all file extensions. Do not use .inc
<li>Form variables are prefixed with f_
<li>User variables are prefixed with u_
<li>Temporary variables are prefixed with t_
<li>Function parameters should be prefixed with p_
<li>Global varialbes should be prefixed with g_
<li>Use the v_ prefix for primary purpose variables in a page
<li>$query and $result should be used for SQL query text and results respectively.
<li>Included files should be suffixed by _inc.php
<li>Count variables should follow the format $<what>_count. eg $bug_count.
<li>functions that print should be prefixed with print_.
</ul>

<h3>Formatting</h3>
<ul>
<li>Use TABS with a size of 4 to make the code easily readable while not wasting too much space
<li>Follow the table formatting of existing pages
<li>Break up SQL queries to be easy to read
</ul>

<h3>Page Guidelines</h3>
<ul>
<li>The first item should be the copyright notice
<li>The next line should be a cookie check to see if the user is logged in
<li>Next should be the majority of the SQL queries for a page
<li>Next will be the various html print_ functions.
<li>The main body of the page will follow
<li>At the bottom will be the footer information and closing print_ functions.
</ul>

Above all, write code that is easy to read and maintain. Code that is not will be rewritten or deleted. Comment blocks of code and functions at all times.

<!-- ---------------------------------------------------------------------- -->
<p>
<hr size=1>
<p>

<font size=-1>
<b>ChangeLog</b>
<p>

<li>version 1.0 December 23, 2000 - Kenzaburo Ito (prescience@300baud.org)<br>
<i>Initial creation</i>

</font>
<p>
<hr size=1>
</td>
</tr>
</table>

<p>
<div align=right>
<A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=14963" width="88" height="31" border="0" alt="SourceForge Logo"></A>
</div>

</body>
</html>
Binary file added images/ss1.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/ss2.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/ss3.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/ss4.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/ss5.gif
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
97 changes: 97 additions & 0 deletions index.php3
@@ -0,0 +1,97 @@
<html>
<head>
<style>
body { background-color:#ffffff; font-family:Verdana, Arial; font-size=10pt }
td { font-family:Verdana, Arial; font-size=10pt }
p { font-family:Verdana, Arial; font-size=10pt }
</style>
<title>Mantis</title>
</head>
<body bgcolor=#ffffff>

<p>
<div align=center>
<h2>Mantis</h2>
</div>

<p>
<div align=center>

<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
<td>
<b><font size=+1>What is it?</font></b>
<p>
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.7 and higher
<li><a href="http://www.mysql.com/">MySQL database</a> (check back to see when new databases are added)
<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. It also helps a great deal to at least be able to tinker with php scripts (when there's a little bug or you want to tweak something). Of course, knowing HTML is essential to do any custom formatting. Along the lines of appearance, I have tried to use my best judgement in colors, layout, and feel. Eventually I hope to be able to customize the look and feel from a single CSS file.

<p>
<b><font size=+1>Features and Benefits</font></b>
<p>
<li>Web based and platform independent
<li>Supports PHP3 and PHP4
<li>Configuration files allow for for site-wide control
<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>ETA and projection for each bug
<li>Shows which bugs have been modified in last X hours
<li>Stored profiles
<li>Complex viewing filters
<li>Detailed summary reports

<p>
<b><font size=+1>Upcoming Features</font></b>
<p>
<li>Mailing module
<li>Multiple project support
<li>File upload module
<li>Support for PostgreSQL/Database abstraction layer
<li>Weekly progress reports
<li>Bug searching
Check the <a href="roadmap.php3">Roadmap</a> for a more detailed and up to date list of items.
<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.

<p>
<b><font size=+1>Credits</font></b>
<p>
<li><a href="mailto:prescience@300baud.org">Kenzaburo Ito</a> - programming
<li>Hai Nguyen - original implementation
</td>
</tr>
</table>

<p>
<div align=right>
<A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=14963" width="88" height="31" border="0" alt="SourceForge Logo"></A>
</div>

</body>
</html>

0 comments on commit 31fff94

Please sign in to comment.