/
mantis.php3
107 lines (97 loc) · 5.11 KB
/
mantis.php3
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<html>
<head>
<? include( "css.php3" ) ?>
<title>Mantis</title>
</head>
<body bgcolor=#ffffff>
<p>
<div align=center>
<h2>Mantis</h2>
Last modified: <? echo date( "M d, Y - H:m", getlastmod() )?>
</div>
<p>
<div align=center>
<table width=100%>
<tr valign=top>
<? include("side_menu.php3") ?>
<td width=100%>
<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</a>.
<p>
Mantis is free to use and modify. It is free to distribute as long as you abide by the distribution terms of the <a href="http://www.gnu.org/copyleft/gpl.html">GNU GPL</a>.
<p>
I and a friend originally created a bugtracker as an internal tool for our own pet project. A check on the web in early 2000 revealed that there were no usable, free php based bug tracking packages (I may be mistaken). At least there were none that I would choose to use. Since then I've gone ahead with a total rewrite and decided to make it available to the public. I have no strong love of the GPL but I do feel that development tools should be free, thus my choice of license.
<p>
<b><font size=+1>Requirements</font></b>
<p>
<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.
<p>
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>
I highly recommend using <a href="http://www.phpwizard.net">phpMyAdmin</a> to administer your mysql database.
<p>
<b><font size=+1>Features and Benefits</font></b>
<p>
<li>Web based and platform independent
<li>Supports PHP3 and PHP4
<li>Emailing module
<li>Multiple project support
<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
<li>Shows which bugs have been modified in last X hours
<li>Stored user profiles
<li>Complex viewing filters
<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>Quick access to "What I want to do"
<li>Simple navigation
<li>Layered complexity
<li>Consistency
<li>Scale to browser window size
<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 items. 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 very large change in the core package, minor a significant amount of feature addition/modification, micro for mostly bug fixes. I will release a new version for a significant bugfix as often as daily.
<p>
Version 1.0.0 will be used when I consider Mantis to be production quality. This means it should be feature full and stable enough for full production use.
<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><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 any one thing, keeps me motivated.
<li><b>Buy me a book</b> off my <a href="http://www.amazon.com/exec/obidos/registry-edit-items-done/2FXMNHDUMQLA/107-9987144-7527713">wish list</a>! (or from another site if you won't deal with Amazon)
</td>
</tr>
</table>
</body>
</html>