|
From: Benjamin C. <bc...@us...> - 2001-10-03 04:04:04
|
Update of /cvsroot/phpbt/phpbt/docs/html In directory usw-pr-cvs1:/tmp/cvs-serv14353/html Modified Files: adminguide.html configuration.html devguide.html devstandards.html index.html userguide.html Log Message: Getting started on the user's guide -- can NS4 show PNG? Index: adminguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/adminguide.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- adminguide.html 2001/09/29 18:35:54 1.3 +++ adminguide.html 2001/10/03 04:03:55 1.4 @@ -99,7 +99,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN12" +NAME="AEN32" ></A ><P >One of the main design goals of phpBugTracker is to make installation and administration easy. In fact, the difficulty of installing bugzilla was a key motivator for phpBugTracker's existence.</P Index: configuration.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/configuration.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- configuration.html 2001/10/01 01:12:38 1.2 +++ configuration.html 2001/10/03 04:03:55 1.3 @@ -84,7 +84,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN64" +NAME="AEN84" ></A ><P >The options listed in this section can be configured by the <TT Index: devguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devguide.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- devguide.html 2001/10/01 01:12:38 1.4 +++ devguide.html 2001/10/03 04:03:55 1.5 @@ -113,7 +113,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN169" +NAME="AEN189" ></A ><P >Adding on to or extending phpBugTracker should be easy for those with a knowledge of PHP and SQL. New developers are always welcome to join the project at <A @@ -136,7 +136,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN174" +NAME="AEN194" ></A ><P >phpBugTracker requires one external package, PHPlib, and can optionally use JpGraph. Of course a web server and a database are also necessary.</P @@ -161,7 +161,7 @@ ><H3 CLASS="SECT3" ><A -NAME="AEN180" +NAME="AEN200" >3.1.1.1. Database Abstraction</A ></H3 ><P @@ -220,7 +220,7 @@ ><H3 CLASS="SECT3" ><A -NAME="AEN192" +NAME="AEN212" >3.1.1.2. Templates</A ></H3 ><P Index: devstandards.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/devstandards.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- devstandards.html 2001/10/02 04:06:34 1.5 +++ devstandards.html 2001/10/03 04:03:55 1.6 @@ -77,7 +77,7 @@ ><DIV CLASS="ABSTRACT" ><A -NAME="AEN198" +NAME="AEN218" ></A ><P > This section details the coding and process standards to be Index: index.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/index.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- index.html 2001/10/01 01:12:38 1.4 +++ index.html 2001/10/03 04:03:55 1.5 @@ -55,6 +55,15 @@ HREF="userguide.html" >User's Guide</A ></DT +><DD +><DL +><DT +>1.1. <A +HREF="userguide.html#PRIMER" +>Getting Started</A +></DT +></DL +></DD ><DT >2. <A HREF="adminguide.html" Index: userguide.html =================================================================== RCS file: /cvsroot/phpbt/phpbt/docs/html/userguide.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- userguide.html 2001/09/29 18:35:54 1.2 +++ userguide.html 2001/10/03 04:03:55 1.3 @@ -86,6 +86,60 @@ >Currently all interactions with phpBugTracker are done via the web interface. Users can submit bugs, communicate with developers and testers about bugs, and search through the bug database.</P ></DIV ></BLOCKQUOTE +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="PRIMER" +>1.1. Getting Started</A +></H1 +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="AEN12" +>1.1.1. Creating an account</A +></H2 +><P +>You can create a new account by following the link labeled <SPAN +CLASS="bold" +><B +CLASS="EMPHASIS" +>Open a new account</B +></SPAN +>. To create a new account you will need to enter at least a valid email address (so that your password can be mailed to you). Providing your name is optional, but if you submit it then your name will appear with bugs you submit and comments you make. If the system has been configured to use a login separate from the email address, you will also be prompted for a login. If you have chosen an email address (or login) that is already in use, you will be prompted to choose a different one. After completing this form, your password will be mailed to you. Once you have received your password you can then login with your email (or login) and password to be able to submit bugs.</P +></DIV +><DIV +CLASS="SECT2" +><H2 +CLASS="SECT2" +><A +NAME="ENTERBUG" +>1.1.2. Entering a bug</A +></H2 +><P +>Once you have logged in to the system you can follow the <SPAN +CLASS="bold" +><B +CLASS="EMPHASIS" +>Enter Bug</B +></SPAN +> link from the top navigation bar to create a new bug. If there is more than one project for which you can submit a bug, you will be prompted to choose one.</P +><DIV +CLASS="MEDIAOBJECT" +><P +><IMG +SRC="images/shots/user/enterbug-chooseproject.png" +ALT="Screen shot of selecting a project for a bug report." +></IMG +></P +></DIV +><P +>..</P +></DIV +></DIV ></DIV ><DIV CLASS="NAVFOOTER" |