From afb7d138833b7c932e24e7ed7544c4d274169752 Mon Sep 17 00:00:00 2001 From: prescience Date: Sat, 17 Mar 2001 04:45:03 +0000 Subject: [PATCH] new files git-svn-id: http://mantisbt.svn.sourceforge.net/svnroot/mantisbt/trunk@242 f5dc347c-c33d-0410-90a0-b07cc1902cb9 --- info.php3 | 84 +++++++++++++++++++++++++++++++ release.php3 | 135 ++++++++++++++++++++++++++++++++++++++++++++++++++ security.php3 | 47 ++++++++++++++++++ 3 files changed, 266 insertions(+) create mode 100644 info.php3 create mode 100644 release.php3 create mode 100644 security.php3 diff --git a/info.php3 b/info.php3 new file mode 100644 index 0000000..153db76 --- /dev/null +++ b/info.php3 @@ -0,0 +1,84 @@ + + + +Mantis + + + +

+

+

Mantis

+ Last modified: +
+ +

+

+ + + + + + +
+

+Information + +

+Example of Use +

+The following is a basic description of what I envisioned when developing the system. +

+Access level have been broken into the following: +

    +
  • viewer +
  • reporter +
  • updater +
  • developer +
  • manager +
  • administrator +
+Viewers should be considered outsiders to the system. They have no rights to change or add to any of the data. This is a useful state for anonymous or guest accounts. Project teams that wish to allow public access to a bug database but do not wish for more can use this access level. +

+Reporters are your basic users who report bugs or request features. Most of the time these will be your customers or testers. +

+Updaters are basically privileged reporters. They are allowed to update the status of a bug. This can range from confirming a bug, assigning it to the proper developer, or even resolving a bug. Examples would be experienced beta testers or trusted members of the product community (helpful power users). +

+Developers should be self-explanatory. These are the people who actually work on the project/product. +

+Managers are also Developers but also have the power to control access to projects. They are assigned ownership of a project on a per project basis. This is similar to a forum moderator. +

+Administrators are the people who have total control over the system. Yes, they can even screw up the project. In principle, these accounts shouldn't be used except for administrative functions. Theses might include creating new projects, assigning managers to projects, or making system changes. +

+The typical cycle for a bug would be as follows: +

    +
  • User downloads/buys product and starts using it. +
  • User discovers what he considers a bug. +
  • User returns to the product webpage to see if there is a fix or workaround. +
  • User sees that there is a public bugtracker and goes to see if his bug is listed there. +
  • User doesn't find it and so reports it. +
  • Updater comes by and notices a NEW bug and reads it. +
  • Updater decides that the bug is legitimate and so ASSIGNS it to a developer. +
  • Developer is notified and discovers he needs more information. +
  • Developer adds a note requesting information and sets the bug to FEEDBACK status. +
  • User recieves an email requesting more information and returns to give it. +
  • Developer and User correspond via bugnotes until the information needed is retrieved. +
  • Developer fixes bug and posts fix or workaround. +
  • Developer RESOLVES the bug. +
+

+Navigation +

+My biggest problem with every web based bugtracking package that I have come across is that the interfaces are inadequate. Most of the time I go to a bugtracker for one of two reasons: 1) I want to file a bug. 2) I want to browse recent, open bugs. All of the bugtrackers that I have seen up to this point made is difficult to do 2. Most of the time they use poor language like 'generate reports'. Almost all seem to think that the first thing you'd like to do when entering a bugtracker is to query for a bug by its ID. I find that bug IDs are the last thing I remember and I think it's an extremely poor choice to be presented to a new visitor. My interface reflects this disatisfaction. All major actions are available via the menu bar, thus navigation is simple and quick. +

+ +

+

+ SourceForge Logo +
+ + + \ No newline at end of file diff --git a/release.php3 b/release.php3 new file mode 100644 index 0000000..25ccb3c --- /dev/null +++ b/release.php3 @@ -0,0 +1,135 @@ +"; + PRINT ""; + echo $type; + PRINT ""; + PRINT ""; + echo $old; + PRINT ""; + PRINT ""; + echo $new; + PRINT ""; + PRINT ""; + echo $notes; + PRINT ""; + PRINT ""; + } + + function print_table($title,$color) { + PRINT ""; + PRINT ""; + PRINT "$title"; + PRINT ""; + PRINT ""; + PRINT ""; + PRINT "Action"; + PRINT "Old Value"; + PRINT "New Value"; + PRINT "Notes"; + PRINT ""; + } + + function print_release($version,$date,$message) { + PRINT ""; + PRINT ""; + PRINT ""; + PRINT ""; + PRINT ""; + PRINT ""; + PRINT ""; + PRINT "
"; + PRINT "$version - $date"; + PRINT "
"; + PRINT "

"; + PRINT "$message"; + PRINT "

"; + } + + function print_modified($list) { + $list_arr = explode(" ",$list); + $file_count = count( $list_arr ); + ### + PRINT "

"; + PRINT "Modified Files"; + PRINT "

    "; + for ($i=0;$i<$file_count;$i++) { + if (!empty($list_arr[$i])) { + PRINT "
  • $list_arr[$i]"; + } + } + PRINT "
"; + PRINT "
"; + } +?> + + + +Mantis + + + +

+

+

Mantis

+ Last modified: +
+ +

+

+ + + + + + +
+

+Release Notes + +

+This is a preliminary draft of the release notes. +

+ + + + + + + + + + + +
+ + +

+ + + + + + +
+

+ + + +

+ + +
+ +

+

+ SourceForge Logo +
+ + + \ No newline at end of file diff --git a/security.php3 b/security.php3 new file mode 100644 index 0000000..49c45ae --- /dev/null +++ b/security.php3 @@ -0,0 +1,47 @@ + + + +Mantis + + + +

+

+

Mantis

+ Last modified: +
+ +

+

+ + + + + + +
+

+Security + +

+Show Source - Warning +

+Letting users see the complete source can be a security hazard. This can happen if you set $g_show_source to something other than 0 or 1. Users can replace the f_url in the URL with any file available on the system. + +

+Passwords - Information +

+Currently the passwords are run through the crypt() function before being stored. crypt() is a one way function; this means that you cannot obtain the original password from the crypt()ed password. This ensures that the user passwords are not readable should the database be cracked into (Note: this doesn't mean they are uncrackable, enough time and processing power and brute force will reveal most passwords). However, your username and password are most likely being transmitted in clear text. You will have to use a ssl (https) connection to protect transmission. +

+ +

+

+ SourceForge Logo +
+ + + \ No newline at end of file