Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-24 18:55:30 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Latest version of compiled docs (picking up recent SGML changes).

Browse Source
This commit is contained in:
jake%acutex.net 2002-01-18 23:27:01 +00:00
parent e91f00e308
commit fbe037bf39
70 changed files with 8661 additions and 5243 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5520
webtools/bugzilla/docs/html/Bugzilla-Guide.html
View File

File diff suppressed because it is too large Load Diff

6
webtools/bugzilla/docs/html/about.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Purpose and Scope of this Guide"
HREF="aboutthisguide.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="aboutthisguide.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="ABOUT"
NAME="about"
>Chapter 1. About This Guide</A
></H1
><DIV

20
webtools/bugzilla/docs/html/aboutthisguide.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Copyright Information"
HREF="copyright.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,28 +66,28 @@ HREF="copyright.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="ABOUTTHISGUIDE"
NAME="aboutthisguide"
>1.1. Purpose and Scope of this Guide</A
></H1
><P
> This document was started on September 17, 2000 by Matthew P.
>&#13; This document was started on September 17, 2000 by Matthew P.
Barnson after a great deal of procrastination updating the
Bugzilla FAQ, which I left untouched for nearly half a year.
After numerous complete rewrites and reformatting, it is the
document you see today.
</P
><P
> Bugzilla is simply the best piece of bug-tracking software the
>&#13; Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration,
maintenance, and use of the Bugzilla bug-tracking system.
</P
><P
> This release of the Bugzilla Guide is the
>&#13; This release of the Bugzilla Guide is the
<EM
>2.14</EM
> release. It is so named that it
@ -108,7 +108,7 @@ NAME="ABOUTTHISGUIDE"
developers, and those who enjoy a lot of pain.
</P
><P
> Newer revisions of the Bugzilla Guide follow the numbering
>&#13; Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<A
HREF="http://www.mozilla.org/projects/bugzilla"
@ -123,13 +123,13 @@ TARGET="_top"
Got it? Good.
</P
><P
> I wrote this in response to the enormous demand for decent
>&#13; I wrote this in response to the enormous demand for decent
Bugzilla documentation. I have incorporated instructions from
the Bugzilla README, Frequently Asked Questions, Database Schema
Document, and various mailing lists to create it. Chances are,
there are glaring errors in this documentation; please contact
<TT
CLASS="EMAIL"
CLASS="email"
>&#60;<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A

34
webtools/bugzilla/docs/html/administration.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="postinstall-check.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="ADMINISTRATION"
NAME="administration"
>Chapter 4. Administering Bugzilla</A
></H1
><DIV
@ -90,34 +90,34 @@ HREF="useradmin.html"
><DL
><DT
>4.2.1. <A
HREF="useradmin.html#DEFAULTUSER"
HREF="useradmin.html#defaultuser"
>Creating the Default User</A
></DT
><DT
>4.2.2. <A
HREF="useradmin.html#MANAGEUSERS"
HREF="useradmin.html#manageusers"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>4.2.2.1. <A
HREF="useradmin.html#LOGIN"
HREF="useradmin.html#login"
>Logging In</A
></DT
><DT
>4.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
HREF="useradmin.html#createnewusers"
>Creating new users</A
></DT
><DT
>4.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
HREF="useradmin.html#disableusers"
>Disabling Users</A
></DT
><DT
>4.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
HREF="useradmin.html#modifyusers"
>Modifying Users</A
></DT
></DL
@ -134,32 +134,32 @@ HREF="programadmin.html"
><DL
><DT
>4.3.1. <A
HREF="programadmin.html#PRODUCTS"
HREF="programadmin.html#products"
>Products</A
></DT
><DT
>4.3.2. <A
HREF="programadmin.html#COMPONENTS"
HREF="programadmin.html#components"
>Components</A
></DT
><DT
>4.3.3. <A
HREF="programadmin.html#VERSIONS"
HREF="programadmin.html#versions"
>Versions</A
></DT
><DT
>4.3.4. <A
HREF="programadmin.html#MILESTONES"
HREF="programadmin.html#milestones"
>Milestones</A
></DT
><DT
>4.3.5. <A
HREF="programadmin.html#VOTING"
HREF="programadmin.html#voting"
>Voting</A
></DT
><DT
>4.3.6. <A
HREF="programadmin.html#GROUPS"
HREF="programadmin.html#groups"
>Groups and Group Security</A
></DT
></DL
@ -173,11 +173,11 @@ HREF="security.html"
></DIV
><FONT
COLOR="RED"
> Or, I just got this cool thing installed. Now what the heck do I
>&#13; Or, I just got this cool thing installed. Now what the heck do I
do with it?
</FONT
><P
> So you followed <SPAN
>&#13; So you followed <SPAN
CLASS="QUOTE"
>"<A
HREF="installation.html"

8
webtools/bugzilla/docs/html/bonsai.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="CVS"
HREF="cvs.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="cvs.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="BONSAI"
NAME="bonsai"
>5.1. Bonsai</A
></H1
><P

10
webtools/bugzilla/docs/html/bsdinstall.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Installation General Notes"
HREF="geninstall.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,15 +66,15 @@ HREF="geninstall.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="BSDINSTALL"
NAME="bsdinstall"
>3.4. BSD Installation Notes</A
></H1
><P
> For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
>&#13; For instructions on how to set up Bugzilla on FreeBSD, NetBSD, OpenBSD, BSDi, etc. please
consult <A
HREF="osx.html"
>Section 3.3</A

194
webtools/bugzilla/docs/html/bzhacking.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,26 +66,26 @@ HREF="gfdl.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="BZHACKING"
NAME="bzhacking"
>D.5. Hacking Bugzilla</A
></H1
><P
> The following is a guide for reviewers when checking code into Bugzilla's
>&#13; The following is a guide for reviewers when checking code into Bugzilla's
CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla,
you should follow the rules and style conventions below. Any code that
does not adhere to these basic rules will not be added to Bugzilla's
codebase.
</P
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="AEN2495"
NAME="AEN2504"
>D.5.1. Things that have caused problems and should be avoided</A
></H2
><P
@ -94,25 +94,25 @@ NAME="AEN2495"
TYPE="1"
><LI
><P
> Usage of variables in Regular Expressions
>&#13; Usage of variables in Regular Expressions
</P
><P
> It is very important that you don't use a variable in a regular
>&#13; It is very important that you don't use a variable in a regular
expression unless that variable is supposed to contain an expression.
This especially applies when using grep. You should use:
</P
><P
> <TABLE
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>grep ($_ eq $value, @array);
CLASS="programlisting"
>&#13;grep ($_ eq $value, @array);
</PRE
></FONT
></TD
@ -121,20 +121,20 @@ CLASS="PROGRAMLISTING"
>
</P
><P
> -- NOT THIS --
>&#13; -- NOT THIS --
</P
><P
> <TABLE
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>grep (/$value/, @array);
CLASS="programlisting"
>&#13;grep (/$value/, @array);
</PRE
></FONT
></TD
@ -143,12 +143,12 @@ CLASS="PROGRAMLISTING"
>
</P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -163,9 +163,9 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> If you need to use a non-expression variable inside of an expression, be
>&#13; If you need to use a non-expression variable inside of an expression, be
sure to quote it properly (using <TT
CLASS="FUNCTION"
CLASS="function"
>\Q..\E</TT
>).
</P
@ -177,68 +177,70 @@ CLASS="FUNCTION"
></OL
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="AEN2509"
NAME="AEN2518"
>D.5.2. Coding Style for Bugzilla</A
></H2
><P
> While it's true that not all of the code currently in Bugzilla adheres to
>&#13; While it's true that not all of the code currently in Bugzilla adheres to
this (or any) styleguide, it is something that is being worked toward. Therefore,
we ask that all new code (submitted patches and new files) follow this guide
as closely as possible (if you're only changing 1 or 2 lines, you don't have
to reformat the entire file :).
</P
><P
> The Bugzilla development team has decided to adopt the perl style guide as
>&#13; The Bugzilla development team has decided to adopt the perl style guide as
published by Larry Wall. This giude can be found in <SPAN
CLASS="QUOTE"
>"Programming
Perl"</SPAN
> (the camel book) or by typing <B
CLASS="COMMAND"
CLASS="command"
>man perlstyle</B
> at
your favorite shell prompt.
</P
><P
> What appears below if a brief summary, please refer to the perl style
guide if you don't see your question covered here.
>&#13; What appears below if a brief summary, please refer to the perl style
guide if you don't see your question covered here. It is much better to submit
a patch which fails these criteria than no patch at all, but please try to meet
these minimum standards when submitting code to Bugzilla.
</P
><P
></P
><UL
><LI
><P
> Whitespace
>&#13; Whitespace
</P
><P
> Bugzilla's prefered indentation is 4 spaces (no tabs, please).
>&#13; Bugzilla's prefered indentation is 4 spaces (no tabs, please).
</P
></LI
><LI
><P
> Curly braces.
>&#13; Curly braces.
</P
><P
> The opening brace of a block should be on the same line as the statement
>&#13; The opening brace of a block should be on the same line as the statement
that is causing the block and the closing brace should be at the same
indentation level as that statement, for example:
</P
><P
> <TABLE
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>if ($var) {
CLASS="programlisting"
>&#13;if ($var) {
print "The variable is true";
}
else {
@ -252,20 +254,20 @@ else {
>
</P
><P
> -- NOT THIS --
>&#13; -- NOT THIS --
</P
><P
> <TABLE
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>if ($var)
CLASS="programlisting"
>&#13;if ($var)
{
print "The variable is true";
}
@ -283,16 +285,27 @@ else
></LI
><LI
><P
> File Names
>&#13; Cookies
</P
><P
>&#13; Bugzilla uses cookies to ease the user experience, but no new patches
should <EM
>require</EM
> user-side cookies.
</P
></LI
><LI
><P
>&#13; File Names
</P
><P
> File names for bugzilla code and support documention should be legal across
>&#13; File names for bugzilla code and support documention should be legal across
multiple platforms. <TT
CLASS="COMPUTEROUTPUT"
CLASS="computeroutput"
>\ / : * ? " &#60; &#62;</TT
>
and <TT
CLASS="COMPUTEROUTPUT"
CLASS="computeroutput"
>|</TT
> are all illegal characters for filenames
on various platforms. Also, file names should not have spaces in them as they
@ -301,50 +314,111 @@ CLASS="COMPUTEROUTPUT"
></LI
><LI
><P
> Variable Names
>&#13; Javascript dependencies
</P
><P
>&#13; While Bugzilla uses Javascript to make the user experience easier, no patch
to Bugzilla should <EM
>require</EM
> Javascript.
</P
></LI
><LI
><P
>&#13; Patch Format
</P
><P
>&#13; All patches submitted for inclusion into Bugzilla should be in the form of a
<SPAN
CLASS="QUOTE"
>"unified diff"</SPAN
>. This comes from using <SPAN
CLASS="QUOTE"
>"diff -u"</SPAN
>
instead of simply <SPAN
CLASS="QUOTE"
>"diff"</SPAN
> when creating your patch. This will
result in quicker acceptance of the patch.
</P
></LI
><LI
><P
>&#13; Schema Changes
</P
><P
>&#13; If you make schema changes, you should modify <TT
CLASS="filename"
>sanitycheck.cgi</TT
>
to support the new schema. All referential columns should be checked.
</P
></LI
><LI
><P
>&#13; Taint Mode
</P
><P
>&#13; All new cgis must run in Taint mode (Perl taint and DBI taint), and existing cgi's
which run in taint mode must not have taint mode turned off.
</P
></LI
><LI
><P
>&#13; Templatization
</P
><P
>&#13; Patches to Bugzilla need to support templates so they do not force user interface choices
on Bugzilla administrators.
</P
></LI
><LI
><P
>&#13; Variable Names
</P
><P
> If a variable is scoped globally (<TT
CLASS="COMPUTEROUTPUT"
>&#13; If a variable is scoped globally (<TT
CLASS="computeroutput"
>$::variable</TT
>)
its name should be descriptive of what it contains. Local variables can be named
a bit looser, provided the context makes their content obvious. For example,
<TT
CLASS="COMPUTEROUTPUT"
CLASS="computeroutput"
>$ret</TT
> could be used as a staging variable for a
routine's return value as the line <TT
CLASS="COMPUTEROUTPUT"
CLASS="computeroutput"
>return $ret;</TT
>
will make it blatantly obvious what the variable holds and most likely be shown
on the same screen as <TT
CLASS="COMPUTEROUTPUT"
CLASS="computeroutput"
>my $ret = "";</TT
>.
</P
></LI
><LI
><P
> Cross Database Compatability
>&#13; Cross Database Compatability
</P
><P
> Bugzilla was originally written to work with MySQL and therefore took advantage
>&#13; Bugzilla was originally written to work with MySQL and therefore took advantage
of some of its features that aren't contained in other RDBMS software. These
should be avoided in all new code. Examples of these features are enums and
<TT
CLASS="FUNCTION"
CLASS="function"
>encrypt()</TT
>.
</P
></LI
><LI
><P
> Cross Platform Compatability
>&#13; Cross Platform Compatability
</P
><P
> While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
>&#13; While Bugzilla was written to be used on Unix based systems (and Unix/Linux is
still the only officially supported platform) there are many who desire/need to
run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive
not to make the lives of these people any more complicated and avoid doing things

64
webtools/bugzilla/docs/html/cmdline.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="The Quicksearch Utility"
HREF="quicksearch.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,26 +66,26 @@ HREF="quicksearch.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="CMDLINE"
NAME="cmdline"
>D.3. Command-line Bugzilla Queries</A
></H1
><P
> Users can query Bugzilla from the command line using this suite
>&#13; Users can query Bugzilla from the command line using this suite
of utilities.
</P
><P
> The query.conf file contains the mapping from options to field
>&#13; The query.conf file contains the mapping from options to field
names and comparison types. Quoted option names are "grepped"
for, so it should be easy to edit this file. Comments (#) have
no effect; you must make sure these lines do not contain any
quoted "option"
</P
><P
> buglist is a shell script which submits a Bugzilla query and
>&#13; buglist is a shell script which submits a Bugzilla query and
writes the resulting HTML page to stdout. It supports both
short options, (such as "-Afoo" or "-Rbar") and long options
(such as "--assignedto=foo" or "--reporter=bar"). If the first
@ -93,53 +93,53 @@ NAME="CMDLINE"
prefixed with "--default=".
</P
><P
> The columlist is taken from the COLUMNLIST environment variable.
>&#13; The columlist is taken from the COLUMNLIST environment variable.
This is equivalent to the "Change Columns" option when you list
bugs in buglist.cgi. If you have already used Bugzilla, use
<B
CLASS="COMMAND"
CLASS="command"
>grep COLUMLIST ~/.netscape/cookies</B
> to see
your current COLUMNLIST setting.
</P
><P
> bugs is a simple shell script which calls buglist and extracts
>&#13; bugs is a simple shell script which calls buglist and extracts
the bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug
list into a working link if any bugs are found. Counting bugs is
easy. Pipe the results through <B
CLASS="COMMAND"
CLASS="command"
>sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</B
>
</P
><P
> Akkana says she has good results piping buglist output through
>&#13; Akkana says she has good results piping buglist output through
<B
CLASS="COMMAND"
CLASS="command"
>w3m -T text/html -dump</B
>
</P
><DIV
CLASS="PROCEDURE"
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
> Download three files:
>&#13; Download three files:
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash$</TT
> <B
CLASS="COMMAND"
CLASS="command"
>wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
@ -149,13 +149,13 @@ CLASS="COMMAND"
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash$</TT
> <B
CLASS="COMMAND"
CLASS="command"
>wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
@ -165,13 +165,13 @@ CLASS="COMMAND"
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash#</TT
> <B
CLASS="COMMAND"
CLASS="command"
>wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
@ -183,15 +183,15 @@ CLASS="COMMAND"
></LI
><LI
><P
> Make your utilities executable:
>&#13; Make your utilities executable:
<TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash$</TT
>
<B
CLASS="COMMAND"
CLASS="command"
>chmod u+x buglist bugs</B
>
</TT

12
webtools/bugzilla/docs/html/contributors.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Feedback"
HREF="feedback.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,19 +66,19 @@ HREF="feedback.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="CONTRIBUTORS"
NAME="contributors"
>1.6. Contributors</A
></H1
><P
> Thanks go to these people for significant contributions to this
>&#13; Thanks go to these people for significant contributions to this
documentation (in no particular order):
</P
><P
> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
>&#13; Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
Teitelbaum, Jacob Steenhagen, Joe Robins
</P
></DIV

110
webtools/bugzilla/docs/html/conventions.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Using Bugzilla"
HREF="using.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,18 +66,18 @@ HREF="using.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="CONVENTIONS"
NAME="conventions"
>1.9. Document Conventions</A
></H1
><P
> This document uses the following conventions
>&#13; This document uses the following conventions
</P
><DIV
CLASS="INFORMALTABLE"
CLASS="informaltable"
><A
NAME="AEN129"
></A
@ -90,11 +90,11 @@ CLASS="CALSTABLE"
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Descriptions</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Appearance</TH
></TR
></THEAD
@ -102,17 +102,17 @@ VALIGN="TOP"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Warnings</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><DIV
CLASS="CAUTION"
CLASS="caution"
><P
></P
><TABLE
CLASS="CAUTION"
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
@ -138,17 +138,17 @@ VALIGN="TOP"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Hint</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
@ -174,17 +174,17 @@ VALIGN="TOP"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Notes</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -210,17 +210,17 @@ VALIGN="TOP"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Information requiring special attention</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
@ -246,115 +246,115 @@ VALIGN="TOP"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>File Names</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><TT
CLASS="FILENAME"
CLASS="filename"
>file.extension</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Directory Names</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><TT
CLASS="FILENAME"
CLASS="filename"
>directory</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Commands to be typed</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><B
CLASS="COMMAND"
CLASS="command"
>command</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Applications Names</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><SPAN
CLASS="APPLICATION"
CLASS="application"
>application</SPAN
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><I
CLASS="FOREIGNPHRASE"
CLASS="foreignphrase"
>Prompt</I
> of users command under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>bash$</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><I
CLASS="FOREIGNPHRASE"
CLASS="foreignphrase"
>Prompt</I
> of root users command under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>bash#</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><I
CLASS="FOREIGNPHRASE"
CLASS="foreignphrase"
>Prompt</I
> of user command under tcsh shell</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>tcsh$</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Environment Variables</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><TT
CLASS="ENVAR"
CLASS="envar"
>VARIABLE</TT
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Emphasized word</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><EM
>word</EM
></TD
@ -362,11 +362,11 @@ VALIGN="TOP"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
>Code Example</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
VALIGN="MIDDLE"
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
@ -376,12 +376,12 @@ WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
CLASS="programlisting"
><TT
CLASS="SGMLTAG"
CLASS="sgmltag"
>&#60;para&#62;</TT
>Beginning and end of paragraph<TT
CLASS="SGMLTAG"
CLASS="sgmltag"
>&#60;/para&#62;</TT
></PRE
></FONT

14
webtools/bugzilla/docs/html/copyright.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Disclaimer"
HREF="disclaimer.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="disclaimer.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="COPYRIGHT"
NAME="copyright"
>1.2. Copyright Information</A
></H1
><A
@ -91,7 +91,7 @@ VALIGN="TOP"
WIDTH="80%"
VALIGN="TOP"
><P
> Permission is granted to copy, distribute and/or modify this
>&#13; Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
@ -111,7 +111,7 @@ COLSPAN="2"
ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="ATTRIBUTION"
CLASS="attribution"
>Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
></TD
><TD
@ -120,7 +120,7 @@ WIDTH="10%"
></TR
></TABLE
><P
> If you have any questions regarding this document, its
>&#13; If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form,
please contact Matthew P. Barnson.
</P

20
webtools/bugzilla/docs/html/credits.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Contributors"
HREF="contributors.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,21 +66,21 @@ HREF="contributors.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="CREDITS"
NAME="credits"
>1.5. Credits</A
></H1
><P
> The people listed below have made enormous contributions to the
>&#13; The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</P
><P
> <A
>&#13; <A
HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
@ -89,7 +89,7 @@ TARGET="_top"
README upon which the UNIX installation documentation is largely based.
</P
><P
> <A
>&#13; <A
HREF="mailto://tara@tequilarista.org"
TARGET="_top"
>Tara
@ -98,7 +98,7 @@ TARGET="_top"
strong after Terry left Mozilla.org
</P
><P
> <A
>&#13; <A
HREF="mailto://dkl@redhat.com"
TARGET="_top"
>Dave Lawrence</A
@ -108,7 +108,7 @@ TARGET="_top"
Hat Bugzilla" appendix
</P
><P
> <A
>&#13; <A
HREF="mailto://endico@mozilla.org"
TARGET="_top"
>Dawn Endico</A
@ -117,7 +117,7 @@ TARGET="_top"
questions and arguments on irc.mozilla.org in #mozwebtools
</P
><P
> Last but not least, all the members of the <A
>&#13; Last but not least, all the members of the <A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
TARGET="_top"
> netscape.public.mozilla.webtools</A

14
webtools/bugzilla/docs/html/cvs.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Perforce SCM"
HREF="scm.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="scm.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="CVS"
NAME="cvs"
>5.2. CVS</A
></H1
><P
@ -80,7 +80,7 @@ NAME="CVS"
certain that Bugzilla is not tied into one particular software
management package.</P
><P
> Follow the instructions in the FAQ for enabling Bugzilla e-mail
>&#13; Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <SPAN
CLASS="QUOTE"
@ -92,13 +92,13 @@ CLASS="QUOTE"
state.
</P
><P
> There is also a project, based upon somewhat dated Bugzilla
>&#13; There is also a project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to
email. Check it out at:
<A
HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
TARGET="_top"
> http://homepages.kcbbs.gen.nz/~tonyg/</A
>&#13; http://homepages.kcbbs.gen.nz/~tonyg/</A
>, under the
<SPAN
CLASS="QUOTE"

12
webtools/bugzilla/docs/html/database.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD
><BODY
CLASS="APPENDIX"
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="dbschema.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
CLASS="appendix"
><H1
><A
NAME="DATABASE"
NAME="database"
>Appendix C. The Bugzilla Database</A
></H1
><DIV
@ -94,11 +94,11 @@ HREF="granttables.html"
></DL
></DIV
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -114,7 +114,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?
>&#13; This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?
</P
></TD
></TR

75
webtools/bugzilla/docs/html/dbdoc.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,15 +66,15 @@ HREF="granttables.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="DBDOC"
NAME="dbdoc"
>C.2. MySQL Bugzilla Database Introduction</A
></H1
><P
> This information comes straight from my life. I was forced to learn how
>&#13; This information comes straight from my life. I was forced to learn how
Bugzilla organizes database because of nitpicky requests from users for tiny
changes in wording, rather than having people re-educate themselves or
figure out how to work our procedures around the tool. It sucks, but it can
@ -82,7 +82,7 @@ NAME="DBDOC"
comes.
</P
><P
> So, here you are with your brand-new installation of Bugzilla. You've got
>&#13; So, here you are with your brand-new installation of Bugzilla. You've got
MySQL set up, Apache working right, Perl DBI and DBD talking to the database
flawlessly. Maybe you've even entered a few test bugs to make sure email's
working; people seem to be notified of new bugs and changes, and you can
@ -92,12 +92,12 @@ NAME="DBDOC"
testers.
</P
><P
> What's the next thing you do? Outline a training strategy for your
>&#13; What's the next thing you do? Outline a training strategy for your
development team, of course, and bring them up to speed on the new tool you've
labored over for hours.
</P
><P
> Your first training session starts off very well! You have a captive
>&#13; Your first training session starts off very well! You have a captive
audience which seems enraptured by the efficiency embodied in this thing called
"Bugzilla". You are caught up describing the nifty features, how people can
save favorite queries in the database, set them up as headers and footers on
@ -106,12 +106,12 @@ NAME="DBDOC"
and rescue Jane from the clutches of Certain Death!
</P
><P
> But Certain Death speaks up -- a tiny voice, from the dark corners of the
>&#13; But Certain Death speaks up -- a tiny voice, from the dark corners of the
conference room. "I have a concern," the voice hisses from the darkness,
"about the use of the word 'verified'.
</P
><P
> The room, previously filled with happy chatter, lapses into reverential
>&#13; The room, previously filled with happy chatter, lapses into reverential
silence as Certain Death (better known as the Vice President of Software
Engineering) continues. "You see, for two years we've used the word 'verified'
to indicate that a developer or quality assurance engineer has confirmed that,
@ -120,7 +120,7 @@ NAME="DBDOC"
'approved' as soon as possible. To avoid confusion, of course."
</P
><P
> Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I
>&#13; Oh no! Terror strikes your heart, as you find yourself mumbling "yes, yes, I
don't think that would be a problem," You review the changes with Certain
Death, and continue to jabber on, "no, it's not too big a change. I mean, we
have the source code, right? You know, 'Use the Source, Luke' and all that...
@ -128,20 +128,20 @@ NAME="DBDOC"
burbling, and boiling on a hot Jamaican sand dune...
</P
><P
> Thus begins your adventure into the heart of Bugzilla. You've been forced
>&#13; Thus begins your adventure into the heart of Bugzilla. You've been forced
to learn about non-portable enum() fields, varchar columns, and tinyint
definitions. The Adventure Awaits You!
</P
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="AEN2331"
NAME="AEN2340"
>C.2.1. Bugzilla Database Basics</A
></H2
><P
> If you were like me, at this point you're totally clueless
>&#13; If you were like me, at this point you're totally clueless
about the internals of MySQL, and if it weren't for this
executive order from the Vice President you couldn't care less
about the difference between a <SPAN
@ -165,24 +165,24 @@ TARGET="_top"
TYPE="1"
><LI
><P
> To connect to your database:
>&#13; To connect to your database:
</P
><P
> <TT
CLASS="PROMPT"
>&#13; <TT
CLASS="prompt"
>bash#</TT
><B
CLASS="COMMAND"
CLASS="command"
>mysql</B
><TT
CLASS="PARAMETER"
CLASS="parameter"
><I
>-u root</I
></TT
>
</P
><P
> If this works without asking you for a password,
>&#13; If this works without asking you for a password,
<EM
>shame on you</EM
>! You should have
@ -200,7 +200,7 @@ CLASS="PARAMETER"
this:</P
><P
><TT
CLASS="PROMPT"
CLASS="prompt"
>mysql&#62;</TT
></P
><P
@ -209,25 +209,25 @@ CLASS="QUOTE"
>"bugs"</SPAN
> is the name
you chose in the<TT
CLASS="FILENAME"
CLASS="filename"
>localconfig</TT
> file
for your Bugzilla database, type:</P
><P
><TT
CLASS="PROMPT"
CLASS="prompt"
>mysql</TT
><B
CLASS="COMMAND"
CLASS="command"
>use bugs;</B
></P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -256,11 +256,11 @@ CLASS="QUOTE"
>
</P
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="AEN2360"
NAME="AEN2369"
>C.2.1.1. Bugzilla Database Tables</A
></H3
><P
@ -269,10 +269,10 @@ NAME="AEN2360"
command:</P
><P
><TT
CLASS="PROMPT"
CLASS="prompt"
>mysql&#62;</TT
><B
CLASS="COMMAND"
CLASS="command"
>show tables from bugs;</B
></P
><P
@ -295,8 +295,8 @@ WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>+-------------------+
CLASS="programlisting"
>&#13;+-------------------+
| Tables in bugs |
+-------------------+
| attachments |
@ -329,8 +329,9 @@ CLASS="PROGRAMLISTING"
></TABLE
></P
><P
CLASS="LITERALLAYOUT"
CLASS="literallayout"
><br>
<br>
&nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br>
descriptive&nbsp;names&nbsp;that&nbsp;make&nbsp;it&nbsp;fairly&nbsp;trivial&nbsp;to&nbsp;figure&nbsp;out&nbsp;their&nbsp;jobs.<br>
<br>

14
webtools/bugzilla/docs/html/dbschema.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,23 +66,23 @@ HREF="dbdoc.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="DBSCHEMA"
NAME="dbschema"
>C.1. Database Schema Chart</A
></H1
><P
> <DIV
CLASS="MEDIAOBJECT"
>&#13; <DIV
CLASS="mediaobject"
><P
><IMG
SRC="../images/dbschema.jpg"
ALT="Database Relationships"
></IMG
><DIV
CLASS="CAPTION"
CLASS="caption"
><P
>Bugzilla database relationships chart</P
></DIV

18
webtools/bugzilla/docs/html/disclaimer.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="New Versions"
HREF="newversions.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,15 +66,15 @@ HREF="newversions.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="DISCLAIMER"
NAME="disclaimer"
>1.3. Disclaimer</A
></H1
><P
> No liability for the contents of this document can be accepted.
>&#13; No liability for the contents of this document can be accepted.
Use the concepts, examples, and other content at your own risk.
As this is a new edition of this document, there may be errors
and inaccuracies that may damage your system. Use of this
@ -84,13 +84,13 @@ NAME="DISCLAIMER"
war. Proceed with caution.
</P
><P
> All copyrights are held by their respective owners, unless
>&#13; All copyrights are held by their respective owners, unless
specifically noted otherwise. Use of a term in this document
should not be regarded as affecting the validity of any
trademark or service mark.
</P
><P
> Naming of particular products or brands should not be seen as
>&#13; Naming of particular products or brands should not be seen as
endorsements, with the exception of the term "GNU/Linux". I
wholeheartedly endorse the use of GNU/Linux in every situation
where it is appropriate. It is an extremely versatile, stable,
@ -98,13 +98,13 @@ NAME="DISCLAIMER"
environment for Bugzilla.
</P
><P
> You are strongly recommended to make a backup of your system
>&#13; You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
Heaven knows it's saved my bacon time after time; if you
implement any suggestion in this Guide, implement this one!
</P
><P
> Although the Bugzilla development team has taken great care to
>&#13; Although the Bugzilla development team has taken great care to
ensure that all easily-exploitable bugs or options are
documented or fixed in the code, security holes surely exist.
Great care should be taken both in the installation and usage of

58
webtools/bugzilla/docs/html/downloadlinks.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="The Bugzilla Database"
HREF="database.html"></HEAD
><BODY
CLASS="APPENDIX"
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,18 +63,18 @@ HREF="database.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
CLASS="appendix"
><H1
><A
NAME="DOWNLOADLINKS"
NAME="downloadlinks"
>Appendix B. Software Download Links</A
></H1
><P
> All of these sites are current as of April, 2001. Hopefully
>&#13; All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</P
><P
> Apache Web Server: <A
>&#13; Apache Web Server: <A
HREF="http://www.apache.org/"
TARGET="_top"
>http://www.apache.org</A
@ -82,71 +82,71 @@ TARGET="_top"
Optional web server for Bugzilla, but recommended because of broad user base and support.
</P
><P
> Bugzilla: <A
>&#13; Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A
>&#13; http://www.mozilla.org/projects/bugzilla/</A
>
</P
><P
> MySQL: <A
>&#13; MySQL: <A
HREF="http://www.mysql.com/"
TARGET="_top"
>http://www.mysql.com/</A
>
</P
><P
> Perl: <A
>&#13; Perl: <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org/</A
>
</P
><P
> CPAN: <A
>&#13; CPAN: <A
HREF="http://www.cpan.org/"
TARGET="_top"
>http://www.cpan.org/</A
>
</P
><P
> DBI Perl module:
>&#13; DBI Perl module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/"
HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</A
>&#13; http://www.cpan.org/modules/by-module/DBI/</A
>
</P
><P
> Data::Dumper module:
>&#13; Data::Dumper module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/"
HREF="http://www.cpan.org/modules/by-module/Data/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</A
>&#13; http://www.cpan.org/modules/by-module/Data/</A
>
</P
><P
> MySQL related Perl modules:
>&#13; MySQL related Perl modules:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/"
HREF="http://www.cpan.org/modules/by-module/Mysql/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</A
>&#13; http://www.cpan.org/modules/by-module/Mysql/</A
>
</P
><P
> TimeDate Perl module collection:
>&#13; TimeDate Perl module collection:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/"
HREF="http://www.cpan.org/modules/by-module/Date/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</A
>&#13; http://www.cpan.org/modules/by-module/Date/</A
>
</P
><P
> GD Perl module:
>&#13; GD Perl module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/"
HREF="http://www.cpan.org/modules/by-module/GD/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</A
>&#13; http://www.cpan.org/modules/by-module/GD/</A
>
Alternately, you should be able to find the latest version of
GD at <A
@ -156,15 +156,15 @@ TARGET="_top"
>
</P
><P
> Chart::Base module:
>&#13; Chart::Base module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/"
HREF="http://www.cpan.org/modules/by-module/Chart/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</A
>&#13; http://www.cpan.org/modules/by-module/Chart/</A
>
</P
><P
> LinuxDoc Software:
>&#13; LinuxDoc Software:
<A
HREF="http://www.linuxdoc.org/"
TARGET="_top"

38
webtools/bugzilla/docs/html/errata.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Step-by-step Install"
HREF="stepbystep.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="stepbystep.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="ERRATA"
NAME="errata"
>3.1. ERRATA</A
></H1
><P
@ -85,29 +85,29 @@ BORDER="0"
><TBODY
><TR
><TD
> If you are installing Bugzilla on S.u.S.e. Linux, or some
>&#13; If you are installing Bugzilla on S.u.S.e. Linux, or some
other distributions with <SPAN
CLASS="QUOTE"
>"paranoid"</SPAN
> security
options, it is possible that the checksetup.pl script may fail
with the error: <SPAN
CLASS="ERRORNAME"
CLASS="errorname"
>cannot chdir(/var/spool/mqueue):
Permission denied</SPAN
> This is because your
<TT
CLASS="FILENAME"
CLASS="filename"
>/var/spool/mqueue</TT
> directory has a mode of
<SPAN
CLASS="QUOTE"
>"drwx------"</SPAN
>. Type <B
CLASS="COMMAND"
CLASS="command"
>chmod 755
<TT
CLASS="FILENAME"
CLASS="filename"
>/var/spool/mqueue</TT
></B
> as root to
@ -116,7 +116,7 @@ CLASS="FILENAME"
></TR
><TR
><TD
> Bugzilla may be installed on Macintosh OS X (10), which is a
>&#13; Bugzilla may be installed on Macintosh OS X (10), which is a
unix-based (BSD) operating system. Everything required for
Bugzilla on OS X will install cleanly, but the optional GD
perl module which is used for bug charting requires some
@ -126,9 +126,9 @@ CLASS="FILENAME"
></TR
><TR
><TD
> Release Notes for Bugzilla 2.14 are available at
>&#13; Release Notes for Bugzilla 2.14 are available at
<TT
CLASS="FILENAME"
CLASS="filename"
>docs/rel_notes.txt</TT
> in your Bugzilla
source distribution.
@ -136,7 +136,7 @@ CLASS="FILENAME"
></TR
><TR
><TD
> The preferred documentation for Bugzilla is available in
>&#13; The preferred documentation for Bugzilla is available in
docs/, with a variety of document types available. Please
refer to these documents when installing, configuring, and
maintaining your Bugzilla installation.
@ -147,11 +147,11 @@ CLASS="FILENAME"
><P
></P
><DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
@ -167,7 +167,7 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Bugzilla is not a package where you can just plop it in a directory,
>&#13; Bugzilla is not a package where you can just plop it in a directory,
twiddle a few things, and you're off. Installing Bugzilla assumes you
know your variant of UNIX or Microsoft Windows well, are familiar with the
command line, and are comfortable compiling and installing a plethora
@ -181,11 +181,11 @@ VALIGN="TOP"
></TABLE
></DIV
><DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
@ -201,7 +201,7 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Bugzilla has not undergone a complete security review. Security holes
>&#13; Bugzilla has not undergone a complete security review. Security holes
may exist in the code. Great care should be taken both in the installation
and usage of this software. Carefully consider the implications of
installing other network services with Bugzilla.

1652
webtools/bugzilla/docs/html/faq.html
View File

File diff suppressed because it is too large Load Diff

14
webtools/bugzilla/docs/html/feedback.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Translations"
HREF="translations.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,26 +66,26 @@ HREF="translations.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="FEEDBACK"
NAME="feedback"
>1.7. Feedback</A
></H1
><P
> I welcome feedback on this document. Without your submissions
>&#13; I welcome feedback on this document. Without your submissions
and input, this Guide cannot continue to exist. Please mail
additions, comments, criticisms, etc. to
<TT
CLASS="EMAIL"
CLASS="email"
>&#60;<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
>&#62;</TT
>. Please send flames to
<TT
CLASS="EMAIL"
CLASS="email"
>&#60;<A
HREF="mailto:devnull@localhost"
>devnull@localhost</A

19
webtools/bugzilla/docs/html/future.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,29 +63,29 @@ HREF="variants.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="FUTURE"
NAME="future"
>Chapter 6. The Future of Bugzilla</A
></H1
><TABLE
BORDER="0"
BGCOLOR="#6495ED"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SYNOPSIS"
CLASS="synopsis"
>Bugzilla's Future. Much of this is the present, now.</PRE
></FONT
></TD
></TR
></TABLE
><P
> Bugzilla's future is a constantly-changing thing, as various developers
>&#13; Bugzilla's future is a constantly-changing thing, as various developers
<SPAN
CLASS="QUOTE"
>"scratch an itch"</SPAN
@ -95,9 +95,10 @@ CLASS="QUOTE"
not quite as readable as the rest of the Guide.
</P
><P
> <P
CLASS="LITERALLAYOUT"
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Bugzilla&nbsp;Blue&nbsp;Sky<br>
>&#13; <P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Bugzilla&nbsp;Blue&nbsp;Sky<br>
<br>
Customisability<br>
<br>

165
webtools/bugzilla/docs/html/geninstall.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Win32 Installation Notes"
HREF="win32.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,28 +66,28 @@ HREF="win32.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="GENINSTALL"
NAME="geninstall"
>3.5. Installation General Notes</A
></H1
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="AEN941"
>3.5.1. Modifying Your Running System</A
></H2
><P
> Bugzilla optimizes database lookups by storing all relatively static
>&#13; Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
under your installation directory.
</P
><P
> If you make a change to the structural data in your database
>&#13; If you make a change to the structural data in your database
(the versions table for example), or to the
<SPAN
CLASS="QUOTE"
@ -101,66 +101,66 @@ CLASS="QUOTE"
changes won't show up.
</P
><P
> That file gets automatically regenerated whenever it's more than an
>&#13; That file gets automatically regenerated whenever it's more than an
hour old, so Bugzilla will eventually notice your changes by itself, but
generally you want it to notice right away, so that you can test things.
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="AEN948"
>3.5.2. Upgrading From Previous Versions</A
></H2
><P
> The developers of Bugzilla are constantly adding new tables, columns and
>&#13; The developers of Bugzilla are constantly adding new tables, columns and
fields. You'll get SQL errors if you just update the code. The strategy
to update is to simply always run the checksetup.pl script whenever
you upgrade your installation of Bugzilla. If you want to see what has
changed, you can read the comments in that file, starting from the end.
</P
><P
> If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
>&#13; If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
the latest version, please consult the file, "UPGRADING-pre-2.8" in the
Bugzilla root directory after untarring the archive.
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="HTACCESS"
NAME="htaccess"
>3.5.3. <TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
> files and security</A
></H2
><P
> To enhance the security of your Bugzilla installation,
>&#13; To enhance the security of your Bugzilla installation,
Bugzilla will generate
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
><TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
></I
> files
which the Apache webserver can use to restrict access to
the bugzilla data files. The checksetup script will
generate the <TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
> files.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -176,19 +176,19 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> If you are using an alternate provider of
>&#13; If you are using an alternate provider of
<SPAN
CLASS="PRODUCTNAME"
CLASS="productname"
>webdot</SPAN
> services for graphing
(as described when viewing
<TT
CLASS="FILENAME"
CLASS="filename"
>editparams.cgi</TT
> in your web
browser), you will need to change the ip address in
<TT
CLASS="FILENAME"
CLASS="filename"
>data/webdot/.htaccess</TT
> to the ip
address of the webdot server that you are using.
@ -201,22 +201,81 @@ CLASS="FILENAME"
</P
><P
> If you are using Internet Information Server or other web
>&#13; The default .htaccess file may not provide adequate access
restrictions, depending on your web server configuration.
Be sure to check the &#60;Directory&#62; entries for your
Bugzilla directory so that the <TT
CLASS="filename"
>.htaccess</TT
>
file is allowed to override web server defaults. For instance,
let's assume your installation of Bugzilla is installed to
<TT
CLASS="filename"
>/usr/local/bugzilla</TT
>. You should have
this &#60;Directory&#62; entry in your <TT
CLASS="filename"
>httpd.conf</TT
>
file:
</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
&#60;Directory /usr/local/bugzilla/&#62;
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
&#60;/Directory&#62;
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13; The important part above is <SPAN
CLASS="QUOTE"
>"AllowOverride All"</SPAN
>.
Without that, the <TT
CLASS="filename"
>.htaccess</TT
> file created by
<TT
CLASS="filename"
>checksetup.pl</TT
> will not have sufficient
permissions to protect your Bugzilla installation.
</P
><P
>&#13; If you are using Internet Information Server or other web
server which does not observe <TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
>
conventions, you can disable their creation by editing
<TT
CLASS="FILENAME"
CLASS="filename"
>localconfig</TT
> and setting the
<TT
CLASS="VARNAME"
CLASS="varname"
>$create_htaccess</TT
> variable to
<TT
CLASS="PARAMETER"
CLASS="parameter"
><I
>0</I
></TT
@ -224,23 +283,23 @@ CLASS="PARAMETER"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="MOD_THROTTLE"
NAME="mod-throttle"
>3.5.4. <TT
CLASS="FILENAME"
CLASS="filename"
>mod_throttle</TT
> and Security</A
></H2
><P
> It is possible for a user, by mistake or on purpose, to access
>&#13; It is possible for a user, by mistake or on purpose, to access
the database many times in a row which can result in very slow
access speeds for other users. If your Bugzilla installation
is experiencing this problem , you may install the Apache
module <TT
CLASS="FILENAME"
CLASS="filename"
>mod_throttle</TT
> which can limit
connections by ip-address. You may download this module at
@ -251,7 +310,7 @@ TARGET="_top"
>. Follow the instructions to install into your Apache install. <EM
>This module only functions with the Apache web server!</EM
>. You may use the <B
CLASS="COMMAND"
CLASS="command"
>ThrottleClientIP</B
> command provided by this module to accomplish this goal. See the <A
HREF="http://www.snert.com/Software/Throttle/"
@ -260,11 +319,11 @@ TARGET="_top"
> for more information. </P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="CONTENT_TYPE"
NAME="content-type"
>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></H2
><P
@ -286,8 +345,8 @@ WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
CLASS="programlisting"
>&#13;bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' &#62;$i.tmp; \
mv $i.tmp $i; done
</PRE
@ -297,7 +356,7 @@ CLASS="PROGRAMLISTING"
></TABLE
></P
><P
> All this one-liner command does is search for all instances of
>&#13; All this one-liner command does is search for all instances of
<SPAN
CLASS="QUOTE"
>"Content-type: text/html"</SPAN
@ -319,20 +378,20 @@ CLASS="QUOTE"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="UNIXHISTORY"
NAME="unixhistory"
>3.5.6. UNIX Installation Instructions History</A
></H2
><P
> This document was originally adapted from the Bonsai
>&#13; This document was originally adapted from the Bonsai
installation instructions by Terry Weissman
&#60;terry@mozilla.org&#62;.
</P
><P
> The February 25, 1999 re-write of this page was done by Ry4an
>&#13; The February 25, 1999 re-write of this page was done by Ry4an
Brase &#60;ry4an@ry4an.org&#62;, with some edits by Terry
Weissman, Bryce Nesbitt, Martin Pool, &#38; Dan Mosedale (But
don't send bug reports to them; report them using bugzilla, at <A
@ -342,19 +401,19 @@ TARGET="_top"
> ).
</P
><P
> This document was heavily modified again Wednesday, March 07
>&#13; This document was heavily modified again Wednesday, March 07
2001 to reflect changes for Bugzilla 2.12 release by Matthew
P. Barnson. The securing MySQL section should be changed to
become standard procedure for Bugzilla installations.
</P
><P
> Finally, the README in its entirety was marked up in SGML and
>&#13; Finally, the README in its entirety was marked up in SGML and
included into the Guide on April 24, 2001 by Matt Barnson.
Since that time, it's undergone extensive modification as
Bugzilla grew.
</P
><P
> Comments from people using this Guide for the first time are
>&#13; Comments from people using this Guide for the first time are
particularly welcome.
</P
></DIV

159
webtools/bugzilla/docs/html/gfdl-0.html Normal file
View File

@ -0,0 +1,159 @@
<HTML
><HEAD
><TITLE
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="NEXT"
TITLE="APPLICABILITY AND DEFINITIONS"
HREF="gfdl-1.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-1.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-0"
>0. PREAMBLE</A
></H1
><P
>The purpose of this License is to make a manual, textbook,
or other written document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or
noncommercially. Secondarily, this License preserves for the
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by
others.</P
><P
>This License is a kind of "copyleft", which means that
derivative works of the document must themselves be free in the
same sense. It complements the GNU General Public License, which
is a copyleft license designed for free software.</P
><P
>We have designed this License in order to use it for manuals
for free software, because free software needs free documentation:
a free program should come with manuals providing the same
freedoms that the software does. But this License is not limited
to software manuals; it can be used for any textual work,
regardless of subject matter or whether it is published as a
printed book. We recommend this License principally for works
whose purpose is instruction or reference.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-1.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>GNU Free Documentation License</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>APPLICABILITY AND DEFINITIONS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

200
webtools/bugzilla/docs/html/gfdl-1.html Normal file
View File

@ -0,0 +1,200 @@
<HTML
><HEAD
><TITLE
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="PREAMBLE"
HREF="gfdl-0.html"><LINK
REL="NEXT"
TITLE="VERBATIM COPYING"
HREF="gfdl-2.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-0.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-2.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-1"
>1. APPLICABILITY AND DEFINITIONS</A
></H1
><P
>This License applies to any manual or other work that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. The "Document",
below, refers to any such manual or work. Any member of the
public is a licensee, and is addressed as "you".</P
><P
>A "Modified Version" of the Document means any work
containing the Document or a portion of it, either copied
verbatim, or with modifications and/or translated into another
language.</P
><P
>A "Secondary Section" is a named appendix or a front-matter
section of the Document that deals exclusively with the
relationship of the publishers or authors of the Document to the
Document's overall subject (or to related matters) and contains
nothing that could fall directly within that overall subject.
(For example, if the Document is in part a textbook of
mathematics, a Secondary Section may not explain any mathematics.)
The relationship could be a matter of historical connection with
the subject or with related matters, or of legal, commercial,
philosophical, ethical or political position regarding
them.</P
><P
>The "Invariant Sections" are certain Secondary Sections
whose titles are designated, as being those of Invariant Sections,
in the notice that says that the Document is released under this
License.</P
><P
>The "Cover Texts" are certain short passages of text that
are listed, as Front-Cover Texts or Back-Cover Texts, in the
notice that says that the Document is released under this
License.</P
><P
>A "Transparent" copy of the Document means a
machine-readable copy, represented in a format whose specification
is available to the general public, whose contents can be viewed
and edited directly and straightforwardly with generic text
editors or (for images composed of pixels) generic paint programs
or (for drawings) some widely available drawing editor, and that
is suitable for input to text formatters or for automatic
translation to a variety of formats suitable for input to text
formatters. A copy made in an otherwise Transparent file format
whose markup has been designed to thwart or discourage subsequent
modification by readers is not Transparent. A copy that is not
"Transparent" is called "Opaque".</P
><P
>Examples of suitable formats for Transparent copies include
plain ASCII without markup, Texinfo input format, LaTeX input
format, SGML or XML using a publicly available DTD, and
standard-conforming simple HTML designed for human modification.
Opaque formats include PostScript, PDF, proprietary formats that
can be read and edited only by proprietary word processors, SGML
or XML for which the DTD and/or processing tools are not generally
available, and the machine-generated HTML produced by some word
processors for output purposes only.</P
><P
>The "Title Page" means, for a printed book, the title page
itself, plus such following pages as are needed to hold, legibly,
the material this License requires to appear in the title page.
For works in formats which do not have any title page as such,
"Title Page" means the text near the most prominent appearance of
the work's title, preceding the beginning of the body of the
text.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-0.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-2.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>PREAMBLE</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>VERBATIM COPYING</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

156
webtools/bugzilla/docs/html/gfdl-10.html Normal file
View File

@ -0,0 +1,156 @@
<HTML
><HEAD
><TITLE
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="TERMINATION"
HREF="gfdl-9.html"><LINK
REL="NEXT"
TITLE="How to use this License for your documents"
HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-9.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-howto.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-10"
>10. FUTURE REVISIONS OF THIS LICENSE</A
></H1
><P
>The Free Software Foundation may publish new, revised
versions of the GNU Free Documentation License from time to time.
Such new versions will be similar in spirit to the present
version, but may differ in detail to address new problems or
concerns. See <A
HREF="http://www.gnu.org/copyleft/"
TARGET="_top"
>http://www.gnu.org/copyleft/</A
>.</P
><P
>Each version of the License is given a distinguishing
version number. If the Document specifies that a particular
numbered version of this License "or any later version" applies to
it, you have the option of following the terms and conditions
either of that specified version or of any later version that has
been published (not as a draft) by the Free Software Foundation.
If the Document does not specify a version number of this License,
you may choose any version ever published (not as a draft) by the
Free Software Foundation.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-9.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-howto.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>TERMINATION</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>How to use this License for your documents</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

150
webtools/bugzilla/docs/html/gfdl-2.html Normal file
View File

@ -0,0 +1,150 @@
<HTML
><HEAD
><TITLE
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="APPLICABILITY AND DEFINITIONS"
HREF="gfdl-1.html"><LINK
REL="NEXT"
TITLE="COPYING IN QUANTITY"
HREF="gfdl-3.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-1.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-3.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-2"
>2. VERBATIM COPYING</A
></H1
><P
>You may copy and distribute the Document in any medium,
either commercially or noncommercially, provided that this
License, the copyright notices, and the license notice saying this
License applies to the Document are reproduced in all copies, and
that you add no other conditions whatsoever to those of this
License. You may not use technical measures to obstruct or
control the reading or further copying of the copies you make or
distribute. However, you may accept compensation in exchange for
copies. If you distribute a large enough number of copies you
must also follow the conditions in section 3.</P
><P
>You may also lend copies, under the same conditions stated
above, and you may publicly display copies.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-1.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-3.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>APPLICABILITY AND DEFINITIONS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COPYING IN QUANTITY</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

174
webtools/bugzilla/docs/html/gfdl-3.html Normal file
View File

@ -0,0 +1,174 @@
<HTML
><HEAD
><TITLE
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="VERBATIM COPYING"
HREF="gfdl-2.html"><LINK
REL="NEXT"
TITLE="MODIFICATIONS"
HREF="gfdl-4.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-2.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-4.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-3"
>3. COPYING IN QUANTITY</A
></H1
><P
>If you publish printed copies of the Document numbering more
than 100, and the Document's license notice requires Cover Texts,
you must enclose the copies in covers that carry, clearly and
legibly, all these Cover Texts: Front-Cover Texts on the front
cover, and Back-Cover Texts on the back cover. Both covers must
also clearly and legibly identify you as the publisher of these
copies. The front cover must present the full title with all
words of the title equally prominent and visible. You may add
other material on the covers in addition. Copying with changes
limited to the covers, as long as they preserve the title of the
Document and satisfy these conditions, can be treated as verbatim
copying in other respects.</P
><P
>If the required texts for either cover are too voluminous to
fit legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto
adjacent pages.</P
><P
>If you publish or distribute Opaque copies of the Document
numbering more than 100, you must either include a
machine-readable Transparent copy along with each Opaque copy, or
state in or with each Opaque copy a publicly-accessible
computer-network location containing a complete Transparent copy
of the Document, free of added material, which the general
network-using public has access to download anonymously at no
charge using public-standard network protocols. If you use the
latter option, you must take reasonably prudent steps, when you
begin distribution of Opaque copies in quantity, to ensure that
this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you
distribute an Opaque copy (directly or through your agents or
retailers) of that edition to the public.</P
><P
>It is requested, but not required, that you contact the
authors of the Document well before redistributing any large
number of copies, to give them a chance to provide you with an
updated version of the Document.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-2.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-4.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>VERBATIM COPYING</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>MODIFICATIONS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

280
webtools/bugzilla/docs/html/gfdl-4.html Normal file
View File

@ -0,0 +1,280 @@
<HTML
><HEAD
><TITLE
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="COPYING IN QUANTITY"
HREF="gfdl-3.html"><LINK
REL="NEXT"
TITLE="COMBINING DOCUMENTS"
HREF="gfdl-5.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-3.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-5.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-4"
>4. MODIFICATIONS</A
></H1
><P
>You may copy and distribute a Modified Version of the
Document under the conditions of sections 2 and 3 above, provided
that you release the Modified Version under precisely this
License, with the Modified Version filling the role of the
Document, thus licensing distribution and modification of the
Modified Version to whoever possesses a copy of it. In addition,
you must do these things in the Modified Version:</P
><P
></P
><OL
TYPE="A"
><LI
><P
>Use in the Title Page
(and on the covers, if any) a title distinct from that of the
Document, and from those of previous versions (which should, if
there were any, be listed in the History section of the
Document). You may use the same title as a previous version if
the original publisher of that version gives permission.</P
></LI
><LI
><P
>List on the Title Page,
as authors, one or more persons or entities responsible for
authorship of the modifications in the Modified Version,
together with at least five of the principal authors of the
Document (all of its principal authors, if it has less than
five).</P
></LI
><LI
><P
>State on the Title page
the name of the publisher of the Modified Version, as the
publisher.</P
></LI
><LI
><P
>Preserve all the
copyright notices of the Document.</P
></LI
><LI
><P
>Add an appropriate
copyright notice for your modifications adjacent to the other
copyright notices.</P
></LI
><LI
><P
>Include, immediately
after the copyright notices, a license notice giving the public
permission to use the Modified Version under the terms of this
License, in the form shown in the Addendum below.</P
></LI
><LI
><P
>Preserve in that license
notice the full lists of Invariant Sections and required Cover
Texts given in the Document's license notice.</P
></LI
><LI
><P
>Include an unaltered
copy of this License.</P
></LI
><LI
><P
>Preserve the section
entitled "History", and its title, and add to it an item stating
at least the title, year, new authors, and publisher of the
Modified Version as given on the Title Page. If there is no
section entitled "History" in the Document, create one stating
the title, year, authors, and publisher of the Document as given
on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.</P
></LI
><LI
><P
>Preserve the network
location, if any, given in the Document for public access to a
Transparent copy of the Document, and likewise the network
locations given in the Document for previous versions it was
based on. These may be placed in the "History" section. You
may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.</P
></LI
><LI
><P
>In any section entitled
"Acknowledgements" or "Dedications", preserve the section's
title, and preserve in the section all the substance and tone of
each of the contributor acknowledgements and/or dedications
given therein.</P
></LI
><LI
><P
>Preserve all the
Invariant Sections of the Document, unaltered in their text and
in their titles. Section numbers or the equivalent are not
considered part of the section titles.</P
></LI
><LI
><P
>Delete any section
entitled "Endorsements". Such a section may not be included in
the Modified Version.</P
></LI
><LI
><P
>Do not retitle any
existing section as "Endorsements" or to conflict in title with
any Invariant Section.</P
></LI
></OL
><P
>If the Modified Version includes new front-matter sections
or appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option
designate some or all of these sections as invariant. To do this,
add their titles to the list of Invariant Sections in the Modified
Version's license notice. These titles must be distinct from any
other section titles.</P
><P
>You may add a section entitled "Endorsements", provided it
contains nothing but endorsements of your Modified Version by
various parties--for example, statements of peer review or that
the text has been approved by an organization as the authoritative
definition of a standard.</P
><P
>You may add a passage of up to five words as a Front-Cover
Text, and a passage of up to 25 words as a Back-Cover Text, to the
end of the list of Cover Texts in the Modified Version. Only one
passage of Front-Cover Text and one of Back-Cover Text may be
added by (or through arrangements made by) any one entity. If the
Document already includes a cover text for the same cover,
previously added by you or by arrangement made by the same entity
you are acting on behalf of, you may not add another; but you may
replace the old one, on explicit permission from the previous
publisher that added the old one.</P
><P
>The author(s) and publisher(s) of the Document do not by
this License give permission to use their names for publicity for
or to assert or imply endorsement of any Modified Version.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-3.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-5.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>COPYING IN QUANTITY</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COMBINING DOCUMENTS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

159
webtools/bugzilla/docs/html/gfdl-5.html Normal file
View File

@ -0,0 +1,159 @@
<HTML
><HEAD
><TITLE
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="MODIFICATIONS"
HREF="gfdl-4.html"><LINK
REL="NEXT"
TITLE="COLLECTIONS OF DOCUMENTS"
HREF="gfdl-6.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-4.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-6.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-5"
>5. COMBINING DOCUMENTS</A
></H1
><P
>You may combine the Document with other documents released
under this License, under the terms defined in section 4 above for
modified versions, provided that you include in the combination
all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice.</P
><P
>The combined work need only contain one copy of this
License, and multiple identical Invariant Sections may be replaced
with a single copy. If there are multiple Invariant Sections with
the same name but different contents, make the title of each such
section unique by adding at the end of it, in parentheses, the
name of the original author or publisher of that section if known,
or else a unique number. Make the same adjustment to the section
titles in the list of Invariant Sections in the license notice of
the combined work.</P
><P
>In the combination, you must combine any sections entitled
"History" in the various original documents, forming one section
entitled "History"; likewise combine any sections entitled
"Acknowledgements", and any sections entitled "Dedications". You
must delete all sections entitled "Endorsements."</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-4.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-6.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>MODIFICATIONS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COLLECTIONS OF DOCUMENTS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

149
webtools/bugzilla/docs/html/gfdl-6.html Normal file
View File

@ -0,0 +1,149 @@
<HTML
><HEAD
><TITLE
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="COMBINING DOCUMENTS"
HREF="gfdl-5.html"><LINK
REL="NEXT"
TITLE="AGGREGATION WITH INDEPENDENT WORKS"
HREF="gfdl-7.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-5.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-7.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-6"
>6. COLLECTIONS OF DOCUMENTS</A
></H1
><P
>You may make a collection consisting of the Document and
other documents released under this License, and replace the
individual copies of this License in the various documents with a
single copy that is included in the collection, provided that you
follow the rules of this License for verbatim copying of each of
the documents in all other respects.</P
><P
>You may extract a single document from such a collection,
and distribute it individually under this License, provided you
insert a copy of this License into the extracted document, and
follow this License in all other respects regarding verbatim
copying of that document.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-5.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-7.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>COMBINING DOCUMENTS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>AGGREGATION WITH INDEPENDENT WORKS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

153
webtools/bugzilla/docs/html/gfdl-7.html Normal file
View File

@ -0,0 +1,153 @@
<HTML
><HEAD
><TITLE
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="COLLECTIONS OF DOCUMENTS"
HREF="gfdl-6.html"><LINK
REL="NEXT"
TITLE="TRANSLATION"
HREF="gfdl-8.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-6.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-8.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-7"
>7. AGGREGATION WITH INDEPENDENT WORKS</A
></H1
><P
>A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of
a storage or distribution medium, does not as a whole count as a
Modified Version of the Document, provided no compilation
copyright is claimed for the compilation. Such a compilation is
called an "aggregate", and this License does not apply to the
other self-contained works thus compiled with the Document, on
account of their being thus compiled, if they are not themselves
derivative works of the Document.</P
><P
>If the Cover Text requirement of section 3 is applicable to
these copies of the Document, then if the Document is less than
one quarter of the entire aggregate, the Document's Cover Texts
may be placed on covers that surround only the Document within the
aggregate. Otherwise they must appear on covers around the whole
aggregate.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-6.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-8.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>COLLECTIONS OF DOCUMENTS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>TRANSLATION</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
webtools/bugzilla/docs/html/gfdl-8.html Normal file
View File

@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="AGGREGATION WITH INDEPENDENT WORKS"
HREF="gfdl-7.html"><LINK
REL="NEXT"
TITLE="TERMINATION"
HREF="gfdl-9.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-7.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-9.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-8"
>8. TRANSLATION</A
></H1
><P
>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section
4. Replacing Invariant Sections with translations requires
special permission from their copyright holders, but you may
include translations of some or all Invariant Sections in addition
to the original versions of these Invariant Sections. You may
include a translation of this License provided that you also
include the original English version of this License. In case of
a disagreement between the translation and the original English
version of this License, the original English version will
prevail.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-7.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-9.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>AGGREGATION WITH INDEPENDENT WORKS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>TERMINATION</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

145
webtools/bugzilla/docs/html/gfdl-9.html Normal file
View File

@ -0,0 +1,145 @@
<HTML
><HEAD
><TITLE
>TERMINATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="TRANSLATION"
HREF="gfdl-8.html"><LINK
REL="NEXT"
TITLE="FUTURE REVISIONS OF THIS LICENSE"
HREF="gfdl-10.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-8.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-10.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-9"
>9. TERMINATION</A
></H1
><P
>You may not copy, modify, sublicense, or distribute the
Document except as expressly provided for under this License. Any
other attempt to copy, modify, sublicense or distribute the
Document is void, and will automatically terminate your rights
under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses
terminated so long as such parties remain in full
compliance.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-8.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-10.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>TRANSLATION</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>FUTURE REVISIONS OF THIS LICENSE</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

167
webtools/bugzilla/docs/html/gfdl-howto.html Normal file
View File

@ -0,0 +1,167 @@
<HTML
><HEAD
><TITLE
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"><LINK
REL="PREVIOUS"
TITLE="FUTURE REVISIONS OF THIS LICENSE"
HREF="gfdl-10.html"><LINK
REL="NEXT"
TITLE="Glossary"
HREF="glossary.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-10.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="glossary.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-howto"
>How to use this License for your documents</A
></H1
><P
>To use this License in a document you have written, include
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
NAME="AEN2673"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13; Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1
or any later version published by the Free Software Foundation;
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
</P
></BLOCKQUOTE
><P
>If you have no Invariant Sections, write "with no Invariant
Sections" instead of saying which ones are invariant. If you have
no Front-Cover Texts, write "no Front-Cover Texts" instead of
"Front-Cover Texts being LIST"; likewise for Back-Cover
Texts.</P
><P
>If your document contains nontrivial examples of program
code, we recommend releasing these examples in parallel under your
choice of free software license, such as the GNU General Public
License, to permit their use in free software.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-10.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="glossary.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>FUTURE REVISIONS OF THIS LICENSE</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="gfdl.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Glossary</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

38
webtools/bugzilla/docs/html/gfdl.html
View File

@ -14,9 +14,9 @@ TITLE="Hacking Bugzilla"
HREF="bzhacking.html"><LINK
REL="NEXT"
TITLE="PREAMBLE"
HREF="gfdl_0.html"></HEAD
HREF="gfdl-0.html"></HEAD
><BODY
CLASS="APPENDIX"
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl_0.html"
HREF="gfdl-0.html"
>Next</A
></TD
></TR
@ -63,10 +63,10 @@ HREF="gfdl_0.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
CLASS="appendix"
><H1
><A
NAME="GFDL"
NAME="gfdl"
>Appendix E. GNU Free Documentation License</A
></H1
><DIV
@ -78,62 +78,62 @@ CLASS="TOC"
></DT
><DT
>0. <A
HREF="gfdl_0.html"
HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
HREF="gfdl_1.html"
HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
HREF="gfdl_2.html"
HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
HREF="gfdl_3.html"
HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
HREF="gfdl_4.html"
HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
HREF="gfdl_5.html"
HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="gfdl_6.html"
HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="gfdl_7.html"
HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="gfdl_8.html"
HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="gfdl_9.html"
HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="gfdl_10.html"
HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="gfdl_howto.html"
HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
@ -141,7 +141,7 @@ HREF="gfdl_howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2550"
NAME="AEN2583"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
@ -183,7 +183,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl_0.html"
HREF="gfdl-0.html"
>Next</A
></TD
></TR

168
webtools/bugzilla/docs/html/glossary.html
View File

@ -11,9 +11,9 @@ TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="How to use this License for your documents"
HREF="gfdl_howto.html"></HEAD
HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="GLOSSARY"
CLASS="glossary"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -38,7 +38,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl_howto.html"
HREF="gfdl-howto.html"
>Prev</A
></TD
><TD
@ -60,15 +60,15 @@ WIDTH="100%"></DIV
CLASS="GLOSSARY"
><H1
><A
NAME="GLOSSARY"
NAME="glossary"
>Glossary</A
></H1
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="AEN2645"
NAME="AEN2678"
>0-9, high ascii</A
></H1
><DL
@ -78,17 +78,17 @@ NAME="AEN2645"
></DT
><DD
><P
> Apache web server, and other NCSA-compliant web servers,
>&#13; Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories
called <TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
> files. These
restrict parameters of the web server. In Bugzilla, they
are used to restrict access to certain files which would
otherwise compromise your installation. For instance, the
<TT
CLASS="FILENAME"
CLASS="filename"
>localconfig</TT
> file contains the
password to your database. If this information were
@ -100,11 +100,11 @@ CLASS="FILENAME"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_A"
NAME="gloss-a"
>A</A
></H1
><DL
@ -117,7 +117,7 @@ NAME="GLOSS_A"
>In this context, Apache is the web server most
commonly used for serving up
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Bugzilla</I
> pages. Contrary to
popular belief, the apache web server has nothing to do
@ -128,18 +128,18 @@ CLASS="QUOTE"
>"a patchy"</SPAN
> version of the original
<SPAN
CLASS="ACRONYM"
CLASS="acronym"
>NCSA</SPAN
> world-wide-web server.</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_B"
NAME="gloss-b"
>B</A
></H1
><DL
@ -149,7 +149,7 @@ NAME="GLOSS_B"
></DT
><DD
><P
> A <SPAN
>&#13; A <SPAN
CLASS="QUOTE"
>"Bug"</SPAN
> in Bugzilla refers to an issue
@ -171,7 +171,7 @@ CLASS="QUOTE"
></DT
><DD
><P
> Each Bugzilla Bug is assigned a number that uniquely
>&#13; Each Bugzilla Bug is assigned a number that uniquely
identifies that Bug. The Bug associated with a Bug Number
can be pulled up via a query, or easily from the very
front page by typing the number in the "Find" box.
@ -201,31 +201,31 @@ CLASS="QUOTE"
></DT
><DD
><P
> Bugzilla is the industry-standard bug tracking system. It
>&#13; Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_C"
NAME="gloss-c"
></A
></H1
><DL
><DT
><A
NAME="GLOSS_COMPONENT"
NAME="gloss-component"
><B
>Component</B
></A
></DT
><DD
><P
> A Component is a subsection of a Product. It should be a
>&#13; A Component is a subsection of a Product. It should be a
narrow category, tailored to your organization. All
Products must contain at least one Component (and, as a
matter of fact, creating a Product with no Components will
@ -234,10 +234,10 @@ NAME="GLOSS_COMPONENT"
></DD
><DT
><A
NAME="GLOSS_CPAN"
NAME="gloss-cpan"
><B
><SPAN
CLASS="ACRONYM"
CLASS="acronym"
>CPAN</SPAN
></B
></A
@ -245,7 +245,7 @@ CLASS="ACRONYM"
><DD
><P
><SPAN
CLASS="ACRONYM"
CLASS="acronym"
>CPAN</SPAN
> stands for the
<SPAN
@ -254,7 +254,7 @@ CLASS="QUOTE"
>. CPAN
maintains a large number of extremely useful
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Perl</I
> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
@ -264,11 +264,11 @@ CLASS="GLOSSTERM"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_D"
NAME="gloss-d"
>D</A
></H1
><DL
@ -282,11 +282,11 @@ NAME="GLOSS_D"
background. In general, most daemons are started at boot
time via System V init scripts, or through RC scripts on
BSD-based systems. <I
CLASS="GLOSSTERM"
CLASS="glossterm"
>mysqld</I
>, the
MySQL server, and <I
CLASS="GLOSSTERM"
CLASS="glossterm"
>apache</I
>, a web
server, are generally run as daemons.</P
@ -294,11 +294,11 @@ CLASS="GLOSSTERM"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_G"
NAME="gloss-g"
></A
></H1
><DL
@ -316,32 +316,32 @@ CLASS="QUOTE"
comes by lumping users into groups, and assigning those
groups certain privileges to
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Products</I
> and
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Components</I
> in the
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Bugzilla</I
> database.</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_I"
NAME="gloss-i"
>I</A
></H1
><DL
><DT
><A
NAME="GLOSS_INFINITELOOP"
NAME="gloss-infiniteloop"
><B
>Infinite Loop</B
></A
@ -353,11 +353,11 @@ NAME="GLOSS_INFINITELOOP"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_M"
NAME="gloss-m"
>M</A
></H1
><DL
@ -369,7 +369,7 @@ NAME="GLOSS_M"
><P
>mysqld is the name of the
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
>daemon</I
> for the MySQL database. In
general, it is invoked automatically through the use of
@ -380,11 +380,11 @@ CLASS="GLOSSTERM"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_P"
NAME="gloss-p"
>P</A
></H1
><DL
@ -400,9 +400,9 @@ NAME="GLOSS_P"
Security) for all bugs entered into components beneath
it.</P
><DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN2736"
NAME="AEN2769"
></A
><P
><B
@ -457,7 +457,7 @@ CLASS="QUOTE"
of an interpreted scripting language (such as shell
script), combined with the speed and power of a compiled
language, such as C. <I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Bugzilla</I
> is
maintained in Perl.</P
@ -465,11 +465,11 @@ CLASS="GLOSSTERM"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_Q"
NAME="gloss-q"
>Q</A
></H1
><DL
@ -506,17 +506,17 @@ CLASS="QUOTE"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_R"
NAME="gloss-r"
>R</A
></H1
><DL
><DT
><A
NAME="GLOSS_RECURSION"
NAME="gloss-recursion"
><B
>Recursion</B
></A
@ -538,25 +538,25 @@ CLASS="QUOTE"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_S"
NAME="gloss-s"
>S</A
></H1
><DL
><DT
><B
><SPAN
CLASS="ACRONYM"
CLASS="acronym"
>SGML</SPAN
></B
></DT
><DD
><P
><SPAN
CLASS="ACRONYM"
CLASS="acronym"
>SGML</SPAN
> stands for <SPAN
CLASS="QUOTE"
@ -566,14 +566,14 @@ CLASS="QUOTE"
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<SPAN
CLASS="ACRONYM"
CLASS="acronym"
>SGML</SPAN
> has withstood the test of time as
a robust, powerful language.
<I
CLASS="GLOSSTERM"
CLASS="glossterm"
><SPAN
CLASS="ACRONYM"
CLASS="acronym"
>XML</SPAN
></I
> is the
@ -582,20 +582,20 @@ CLASS="QUOTE"
>"baby brother"</SPAN
> of SGML; any valid
<SPAN
CLASS="ACRONYM"
CLASS="acronym"
>XML</SPAN
> document it, by definition, a valid
<SPAN
CLASS="ACRONYM"
CLASS="acronym"
>SGML</SPAN
> document. The document you are
reading is written and maintained in
<SPAN
CLASS="ACRONYM"
CLASS="acronym"
>SGML</SPAN
>, and is also valid
<SPAN
CLASS="ACRONYM"
CLASS="acronym"
>XML</SPAN
> if you modify the Document Type
Definition.</P
@ -603,24 +603,24 @@ CLASS="ACRONYM"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_T"
NAME="gloss-t"
>T</A
></H1
><DL
><DT
><A
NAME="GLOSS_TARGET_MILESTONE"
NAME="gloss-target-milestone"
><B
>Target Milestone</B
></A
></DT
><DD
><P
> Target Milestones are Product goals. They are
>&#13; Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<SPAN
@ -636,17 +636,17 @@ CLASS="QUOTE"
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
CLASS="glossdiv"
><H1
CLASS="GLOSSDIV"
CLASS="glossdiv"
><A
NAME="GLOSS_Z"
NAME="gloss-z"
>Z</A
></H1
><DL
><DT
><A
NAME="ZARRO-BOOGS-FOUND"
NAME="zarro-boogs-found"
><B
>Zarro Boogs Found</B
></A
@ -675,7 +675,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl_howto.html"
HREF="gfdl-howto.html"
>Prev</A
></TD
><TD

19
webtools/bugzilla/docs/html/granttables.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,19 +66,19 @@ HREF="patches.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="GRANTTABLES"
NAME="granttables"
>C.3. MySQL Permissions &#38; Grant Tables</A
></H1
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -107,7 +107,7 @@ VALIGN="TOP"
troubles to work on : ) Although it is of limited use, it
still has SOME use, thus it's still included.</P
><P
> Please note, however, that I was a relatively new user to
>&#13; Please note, however, that I was a relatively new user to
MySQL at the time. Some of my suggestions, particularly in
how to set up security, showed a terrible lack of
security-related database experience.
@ -117,8 +117,9 @@ VALIGN="TOP"
></TABLE
></DIV
><P
CLASS="LITERALLAYOUT"
>From&nbsp;matt_barnson@singletrac.com&nbsp;Wed&nbsp;Jul&nbsp;&nbsp;7&nbsp;09:00:07&nbsp;1999<br>
CLASS="literallayout"
><br>
From&nbsp;matt_barnson@singletrac.com&nbsp;Wed&nbsp;Jul&nbsp;&nbsp;7&nbsp;09:00:07&nbsp;1999<br>
Date:&nbsp;Mon,&nbsp;1&nbsp;Mar&nbsp;1999&nbsp;21:37:04&nbsp;-0700&nbsp;<br>
From:&nbsp;Matthew&nbsp;Barnson&nbsp;matt_barnson@singletrac.com<br>
To:&nbsp;keystone-users@homeport.org<br>

242
webtools/bugzilla/docs/html/how.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Where can I find my user preferences?"
HREF="init4me.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="init4me.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="HOW"
NAME="how"
>2.3. How do I use Bugzilla?</A
></H1
><TABLE
@ -97,7 +97,7 @@ VALIGN="TOP"
></TR
></TABLE
><P
> Bugzilla is a large, complex system. Describing how to use it
>&#13; Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or
administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
@ -107,19 +107,19 @@ VALIGN="TOP"
software.
</P
><P
> Throughout this portion of the Guide, we will refer to user
>&#13; Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation,
<A
HREF="http://landfill.tequilarista.org/"
TARGET="_top"
> landfill.tequilarista.org</A
>&#13; landfill.tequilarista.org</A
>.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -135,7 +135,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Some people have run into difficulties completing this
>&#13; Some people have run into difficulties completing this
tutorial. If you run into problems, please check the
updated online documentation available at <A
HREF="http://www.trilobyte.net/barnsons/"
@ -160,15 +160,15 @@ TARGET="_top"
mentioned here.
</P
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="MYACCOUNT"
NAME="myaccount"
>2.3.1. Create a Bugzilla Account</A
></H2
><P
> First things first! If you want to use Bugzilla, first you
>&#13; First things first! If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
should use to access it. If you're test-driving the end-user
@ -184,19 +184,19 @@ TARGET="_top"
TYPE="1"
><LI
><P
> Click the "Open a new Bugzilla account" link.
>&#13; Click the "Open a new Bugzilla account" link.
</P
></LI
><LI
><P
> Enter your "E-mail address" and "Real Name" (or whatever
>&#13; Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided,
then select the "Create Account" button.
</P
></LI
><LI
><P
> Within moments, you should receive an email to the address
>&#13; Within moments, you should receive an email to the address
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
@ -206,7 +206,7 @@ TYPE="1"
></LI
><LI
><P
> Click the <SPAN
>&#13; Click the <SPAN
CLASS="QUOTE"
>"Log In"</SPAN
> link in the yellow area at
@ -224,12 +224,12 @@ CLASS="QUOTE"
>"Login"</SPAN
>.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -244,7 +244,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> If you ever forget your password, you can come back to
>&#13; If you ever forget your password, you can come back to
this page, enter your <SPAN
CLASS="QUOTE"
>"E-mail address"</SPAN
@ -262,12 +262,12 @@ CLASS="QUOTE"
></DIV
>
<DIV
CLASS="CAUTION"
CLASS="caution"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="90%"
CLASS="caution"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -282,7 +282,7 @@ ALT="Caution"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Many modern browsers include an
>&#13; Many modern browsers include an
<SPAN
CLASS="QUOTE"
>"Auto-Complete"</SPAN
@ -307,7 +307,7 @@ CLASS="QUOTE"
></LI
></OL
><P
> Congratulations! If you followed these directions, you now
>&#13; Congratulations! If you followed these directions, you now
are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the
@ -319,46 +319,46 @@ CLASS="QUOTE"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="QUERY"
NAME="query"
>2.3.2. The Bugzilla Query Page</A
></H2
><P
> The Bugzilla Query Page is the heart and soul of the Bugzilla
>&#13; The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug
report later on.
</P
><P
> There are efforts underway to simplify query usage. If you
>&#13; There are efforts underway to simplify query usage. If you
have a local installation of Bugzilla 2.12 or higher, you
should have <TT
CLASS="FILENAME"
CLASS="filename"
>quicksearch.html</TT
> available to
use and simplify your searches. There is also a helper for
the query interface, called
<TT
CLASS="FILENAME"
CLASS="filename"
>queryhelp.cgi</TT
>. Landfill tends to run the
latest code, so these two utilities should be available there
for your perusal.
</P
><P
> At this point, please visit the main Bugzilla site,
>&#13; At this point, let's visit the query page.
<A
HREF="http://bugzilla.mozilla.org/query.cgi"
HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi"
TARGET="_top"
> bugzilla.mozilla.org</A
>, to see a more fleshed-out query page.
>&#13; landfill.tequilarista.org/bugzilla-tip/query.cgi</A
>
</P
><P
> The first thing you need to notice about the Bugzilla Query
>&#13; The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should
@ -368,7 +368,7 @@ CLASS="QUOTE"
> underlined. Select it.
</P
><P
> Notice the page that popped up? Every underlined word you see
>&#13; Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface
@ -379,7 +379,7 @@ CLASS="QUOTE"
button in your browser.
</P
><P
> I'm sure that after checking out the online help, you are now
>&#13; I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the
@ -391,7 +391,7 @@ CLASS="QUOTE"
TYPE="1"
><LI
><P
> Ensure you are back on the <SPAN
>&#13; Ensure you are back on the <SPAN
CLASS="QUOTE"
>"Bugzilla Query
Page"</SPAN
@ -407,7 +407,7 @@ CLASS="QUOTE"
figured out.
</P
><P
> Basically, selecting <EM
>&#13; Basically, selecting <EM
>anything</EM
> on the
query page narrows your search down. Leaving stuff
@ -416,7 +416,7 @@ CLASS="QUOTE"
></LI
><LI
><P
> You see the box immediately below the top six boxes that
>&#13; You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to
@ -424,12 +424,12 @@ CLASS="QUOTE"
put my email address in there, and see what happens.
</P
><P
> Type "barnboy@trilobyte.net" in the top Email text box.
>&#13; Type "barnboy@trilobyte.net" in the top Email text box.
</P
></LI
><LI
><P
> Let's narrow the search some more. Scroll down until you
>&#13; Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only
specific products (software programs or product lines) in
@ -443,13 +443,13 @@ CLASS="QUOTE"
></LI
><LI
><P
> Did you notice that some of the boxes to the right changed
>&#13; Did you notice that some of the boxes to the right changed
when you selected "Bugzilla"? Every Program (or Product)
has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a
software program.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN307"
></A
@ -458,14 +458,14 @@ NAME="AEN307"
>Example 2-1. Some Famous Software Versions</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN309"
></A
><P
></P
><P
> Do you remember the hype in 1995 when Microsoft
>&#13; Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software.
@ -475,7 +475,7 @@ NAME="AEN309"
ME(Millenium Edition)(r).
</P
><P
> Software "Versions" help a manufacturer
>&#13; Software "Versions" help a manufacturer
differentiate their current product from their
previous products. Most do not identify their
products by the year they were released. Instead,
@ -492,7 +492,7 @@ NAME="AEN309"
version than 1.1.1.
</P
><P
> In general, a "Version" in Bugzilla should refer to
>&#13; In general, a "Version" in Bugzilla should refer to
<EM
>released</EM
> products, not products
@ -507,13 +507,13 @@ NAME="AEN309"
>
</P
><P
> A "Component" is a piece of a Product.
>&#13; A "Component" is a piece of a Product.
It may be a standalone program, or some other logical
division of a Product or Program.
Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN317"
></A
@ -522,14 +522,14 @@ NAME="AEN317"
>Example 2-2. Mozilla's Bugzilla Components</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN319"
></A
><P
></P
><P
> Mozilla's "Bugzilla" Product is composed of several pieces (Components):
>&#13; Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<P
></P
><TABLE
@ -542,35 +542,35 @@ BORDER="0"
>,
Administration of a bugzilla installation, including
<TT
CLASS="FILENAME"
CLASS="filename"
>editcomponents.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>editgroups.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>editkeywords.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>editparams.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>editproducts.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>editusers.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>editversions.cgi,</TT
> and
<TT
CLASS="FILENAME"
CLASS="filename"
>sanitycheck.cgi</TT
>.
</TD
@ -591,19 +591,19 @@ CLASS="FILENAME"
>,
Creating, changing, and viewing bugs.
<TT
CLASS="FILENAME"
CLASS="filename"
>enter_bug.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>post_bug.cgi</TT
>,
<TT
CLASS="FILENAME"
CLASS="filename"
>show_bug.cgi</TT
> and
<TT
CLASS="FILENAME"
CLASS="filename"
>process_bug.cgi</TT
>.
</TD
@ -615,7 +615,7 @@ CLASS="FILENAME"
>,
The bugzilla documentation, including anything in the
<TT
CLASS="FILENAME"
CLASS="filename"
>docs/</TT
> directory and The Bugzilla Guide
(This document :)
@ -628,7 +628,7 @@ CLASS="FILENAME"
>,
Anything to do with email sent by Bugzilla.
<TT
CLASS="FILENAME"
CLASS="filename"
>processmail</TT
>
</TD
@ -640,7 +640,7 @@ CLASS="FILENAME"
>,
The installation process of Bugzilla. This includes
<TT
CLASS="FILENAME"
CLASS="filename"
>checksetup.pl</TT
> and whatever else it evolves into.
</TD
@ -652,11 +652,11 @@ CLASS="FILENAME"
>,
Anything to do with searching for bugs and viewing the buglists.
<TT
CLASS="FILENAME"
CLASS="filename"
>query.cgi</TT
> and
<TT
CLASS="FILENAME"
CLASS="filename"
>buglist.cgi</TT
>
</TD
@ -668,11 +668,11 @@ CLASS="FILENAME"
>,
Getting reports from Bugzilla.
<TT
CLASS="FILENAME"
CLASS="filename"
>reports.cgi</TT
> and
<TT
CLASS="FILENAME"
CLASS="filename"
>duplicates.cgi</TT
>
</TD
@ -684,7 +684,7 @@ CLASS="FILENAME"
>,
Anything about managing a user account from the user's perspective.
<TT
CLASS="FILENAME"
CLASS="filename"
>userprefs.cgi</TT
>, saved queries, creating accounts,
changing passwords, logging in, etc.
@ -712,7 +712,7 @@ CLASS="FILENAME"
>
</P
><P
> A "Milestone", or "Target Milestone" is a often a planned
>&#13; A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a
developer. Having certain features in your Product is
@ -727,7 +727,7 @@ CLASS="FILENAME"
of reach by the time the important day arrives.
</P
><P
> The Bugzilla Project has set up Milestones for future
>&#13; The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19".
@ -735,19 +735,19 @@ CLASS="FILENAME"
></LI
><LI
><P
> OK, now let's select the "Bugzilla" component from its scrollbox.
>&#13; OK, now let's select the "Bugzilla" component from its scrollbox.
</P
></LI
><LI
><P
> Skip down the page a bit -- do you see the "submit query" button?
>&#13; Skip down the page a bit -- do you see the "submit query" button?
Select it, and let's run
this query!
</P
></LI
><LI
><P
> Congratulations! You've completed your first Query, and
>&#13; Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on
@ -759,7 +759,7 @@ CLASS="FILENAME"
></LI
></OL
><P
> I encourage you to click the bug numbers in the left-hand
>&#13; I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the
@ -768,7 +768,7 @@ CLASS="FILENAME"
this is a tremendous timesaver.
</P
><P
> A couple more interesting things about the Bug List page:
>&#13; A couple more interesting things about the Bug List page:
<P
></P
><TABLE
@ -817,11 +817,11 @@ BORDER="0"
>
</P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -837,7 +837,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> There are many more options to the Bugzilla Query Page and
>&#13; There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to
check out the <A
@ -852,11 +852,11 @@ TARGET="_top"
></DIV
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="BUGREPORTS"
NAME="bugreports"
>2.3.3. Creating and Managing Bug Reports</A
></H2
><TABLE
@ -885,15 +885,15 @@ VALIGN="TOP"
></TR
></TABLE
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="BUG_WRITING"
NAME="bug-writing"
>2.3.3.1. Writing a Great Bug Report</A
></H3
><P
> Before we plunge into writing your first bug report, I
>&#13; Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to
@ -908,7 +908,7 @@ TARGET="_top"
>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</P
><P
> While you are at it, why not learn how to find previously
>&#13; While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <A
HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
@ -917,7 +917,7 @@ TARGET="_top"
>.
</P
><P
> I realize this was a lot to read. However, understanding
>&#13; I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on
the next part!
</P
@ -927,7 +927,7 @@ TARGET="_top"
TYPE="1"
><LI
><P
> Go back to <A
>&#13; Go back to <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A
@ -936,7 +936,7 @@ TARGET="_top"
></LI
><LI
><P
> Select the <A
>&#13; Select the <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top"
> Enter a new bug report</A
@ -945,12 +945,12 @@ TARGET="_top"
></LI
><LI
><P
> Select a product.
>&#13; Select a product.
</P
></LI
><LI
><P
> Now you should be at the "Enter Bug" form. The
>&#13; Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password,
@ -959,12 +959,12 @@ TARGET="_top"
></LI
><LI
><P
> Select a Component in the scrollbox.
>&#13; Select a Component in the scrollbox.
</P
></LI
><LI
><P
> Bugzilla should have made reasonable guesses, based upon
>&#13; Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know!
@ -972,7 +972,7 @@ TARGET="_top"
></LI
><LI
><P
> Fill in the "Assigned To" box with the email address you
>&#13; Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's
just a test bug.
@ -980,33 +980,33 @@ TARGET="_top"
></LI
><LI
><P
> Leave the "CC" text box blank. Fill in the "URL" box
>&#13; Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org".
</P
></LI
><LI
><P
> Enter "The Bugzilla Guide" in the Summary text box, and
>&#13; Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the
Guide in general, into the Description box.
</P
></LI
></OL
><P
> Voila! Select "Commit" and send in your bug report! Next
>&#13; Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs.
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="BUG_MANAGE"
NAME="bug-manage"
>2.3.3.2. Managing your Bug Reports</A
></H3
><P
> OK, you should have a link to the bug you just created near
>&#13; OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this
link.
@ -1017,7 +1017,7 @@ NAME="BUG_MANAGE"
TYPE="1"
><LI
><P
> Scroll down a bit on the subsequent page, until you see
>&#13; Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case,
@ -1029,7 +1029,7 @@ TYPE="1"
></LI
><LI
><P
> Hey! It said it couldn't take the change in a big red
>&#13; Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with
@ -1038,40 +1038,40 @@ TYPE="1"
></LI
></OL
><P
> You have now learned the basics of Bugzilla navigation,
>&#13; You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there.
</P
><P
> But I'll give a few last hints!
>&#13; But I'll give a few last hints!
</P
><P
> There is a <A
HREF="http://bugzilla.mozilla.org/help.html"
>&#13; There is a <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/help.html"
TARGET="_top"
>CLUE</A
> on the Query page that will teach you more how to use the form.
</P
><P
> If you click the hyperlink on the <A
HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
>&#13; If you click the hyperlink on the <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi"
TARGET="_top"
>Component</A
> box of the Query page, you will be presented a form that will describe what all the components are.
</P
><P
> Possibly the most powerful feature of the Query page is the
>&#13; Possibly the most powerful feature of the Query page is the
<A
HREF="http://bugzilla.mozilla.org/booleanchart.html"
HREF="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html"
TARGET="_top"
>Boolean Chart</A
> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</P
><P
> Finally, you can build some nifty <A
HREF="http://bugzilla.mozilla.org/reports.cgi"
>&#13; Finally, you can build some nifty <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi"
TARGET="_top"
>Reports</A
> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.

176
webtools/bugzilla/docs/html/index.html
View File

@ -28,7 +28,7 @@ CONTENT="Mozilla"><META
NAME="KEYWORD"
CONTENT="webtools"></HEAD
><BODY
CLASS="BOOK"
CLASS="book"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -37,48 +37,48 @@ ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
NAME="INDEX"
NAME="index"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
CLASS="title"
><A
NAME="AEN2"
>The Bugzilla Guide</A
></H1
><H3
CLASS="AUTHOR"
CLASS="author"
><A
NAME="AEN27"
>Matthew P. Barnson</A
></H3
><DIV
CLASS="AFFILIATION"
CLASS="affiliation"
><DIV
CLASS="ADDRESS"
CLASS="address"
><P
CLASS="ADDRESS"
CLASS="address"
>barnboy@trilobyte.net</P
></DIV
></DIV
><SPAN
CLASS="COLLAB"
CLASS="collab"
><SPAN
CLASS="COLLABNAME"
CLASS="collabname"
>Zach Lipton</SPAN
><DIV
CLASS="AFFILIATION"
CLASS="affiliation"
><DIV
CLASS="ADDRESS"
CLASS="address"
><P
CLASS="ADDRESS"
CLASS="address"
>zach AT zachlipton DOT com</P
></DIV
></DIV
><BR></SPAN
><DIV
CLASS="REVHISTORY"
CLASS="revhistory"
><TABLE
WIDTH="100%"
BORDER="0"
@ -184,30 +184,30 @@ COLSPAN="3"
></DIV
><DIV
><DIV
CLASS="ABSTRACT"
CLASS="abstract"
><A
NAME="AEN39"
></A
><P
></P
><P
> This is the documentation for Bugzilla, the Mozilla
>&#13; This is the documentation for Bugzilla, the Mozilla
bug-tracking system.
</P
><P
> Bugzilla is an enterprise-class set of software utilities
>&#13; Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
While it is easy to use and quite flexible, it is very
While it is easy to use and quite flexible, it is
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
professional on operating system upon which you install
professional for the operating system upon which you install
Bugzilla.
</P
><P
> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
>&#13; THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
@ -304,29 +304,29 @@ HREF="how.html"
><DL
><DT
>2.3.1. <A
HREF="how.html#MYACCOUNT"
HREF="how.html#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>2.3.2. <A
HREF="how.html#QUERY"
HREF="how.html#query"
>The Bugzilla Query Page</A
></DT
><DT
>2.3.3. <A
HREF="how.html#BUGREPORTS"
HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>2.3.3.1. <A
HREF="how.html#BUG_WRITING"
HREF="how.html#bug-writing"
>Writing a Great Bug Report</A
></DT
><DT
>2.3.3.2. <A
HREF="how.html#BUG_MANAGE"
HREF="how.html#bug-manage"
>Managing your Bug Reports</A
></DT
></DL
@ -342,41 +342,41 @@ HREF="init4me.html"
><DL
><DT
>2.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS"
HREF="init4me.html#accountsettings"
>Account Settings</A
></DT
><DT
>2.4.2. <A
HREF="init4me.html#EMAILSETTINGS"
HREF="init4me.html#emailsettings"
>Email Settings</A
></DT
><DD
><DL
><DT
>2.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
HREF="init4me.html#notification"
>Email Notification</A
></DT
><DT
>2.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
HREF="init4me.html#newemailtech"
>New Email Technology</A
></DT
><DT
>2.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
HREF="init4me.html#watchsettings"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>2.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
HREF="init4me.html#footersettings"
>Page Footer</A
></DT
><DT
>2.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS"
HREF="init4me.html#permissionsettings"
>Permissions</A
></DT
></DL
@ -419,12 +419,12 @@ HREF="stepbystep.html#AEN515"
></DT
><DT
>3.2.3. <A
HREF="stepbystep.html#INSTALL-MYSQL"
HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A
></DT
><DT
>3.2.4. <A
HREF="stepbystep.html#INSTALL-PERL"
HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A
></DT
><DT
@ -481,7 +481,7 @@ HREF="stepbystep.html#AEN721"
>3.2.15. <A
HREF="stepbystep.html#AEN768"
>Tweaking <TT
CLASS="FILENAME"
CLASS="filename"
>localconfig</TT
></A
></DT
@ -536,28 +536,28 @@ HREF="geninstall.html#AEN948"
></DT
><DT
>3.5.3. <A
HREF="geninstall.html#HTACCESS"
HREF="geninstall.html#htaccess"
><TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
> files and security</A
></DT
><DT
>3.5.4. <A
HREF="geninstall.html#MOD_THROTTLE"
HREF="geninstall.html#mod-throttle"
><TT
CLASS="FILENAME"
CLASS="filename"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
HREF="geninstall.html#CONTENT_TYPE"
HREF="geninstall.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
HREF="geninstall.html#UNIXHISTORY"
HREF="geninstall.html#unixhistory"
>UNIX Installation Instructions History</A
></DT
></DL
@ -571,17 +571,17 @@ HREF="win32.html"
><DL
><DT
>3.6.1. <A
HREF="win32.html#WININSTALL"
HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A
></DT
><DT
>3.6.2. <A
HREF="win32.html#ADDLWINTIPS"
HREF="win32.html#addlwintips"
>Additional Windows Tips</A
></DT
><DT
>3.6.3. <A
HREF="win32.html#BZLDAP"
HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A
></DT
></DL
@ -609,34 +609,34 @@ HREF="useradmin.html"
><DL
><DT
>4.2.1. <A
HREF="useradmin.html#DEFAULTUSER"
HREF="useradmin.html#defaultuser"
>Creating the Default User</A
></DT
><DT
>4.2.2. <A
HREF="useradmin.html#MANAGEUSERS"
HREF="useradmin.html#manageusers"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>4.2.2.1. <A
HREF="useradmin.html#LOGIN"
HREF="useradmin.html#login"
>Logging In</A
></DT
><DT
>4.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
HREF="useradmin.html#createnewusers"
>Creating new users</A
></DT
><DT
>4.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
HREF="useradmin.html#disableusers"
>Disabling Users</A
></DT
><DT
>4.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
HREF="useradmin.html#modifyusers"
>Modifying Users</A
></DT
></DL
@ -653,32 +653,32 @@ HREF="programadmin.html"
><DL
><DT
>4.3.1. <A
HREF="programadmin.html#PRODUCTS"
HREF="programadmin.html#products"
>Products</A
></DT
><DT
>4.3.2. <A
HREF="programadmin.html#COMPONENTS"
HREF="programadmin.html#components"
>Components</A
></DT
><DT
>4.3.3. <A
HREF="programadmin.html#VERSIONS"
HREF="programadmin.html#versions"
>Versions</A
></DT
><DT
>4.3.4. <A
HREF="programadmin.html#MILESTONES"
HREF="programadmin.html#milestones"
>Milestones</A
></DT
><DT
>4.3.5. <A
HREF="programadmin.html#VOTING"
HREF="programadmin.html#voting"
>Voting</A
></DT
><DT
>4.3.6. <A
HREF="programadmin.html#GROUPS"
HREF="programadmin.html#groups"
>Groups and Group Security</A
></DT
></DL
@ -738,27 +738,27 @@ HREF="rhbugzilla.html"
></DT
><DT
>7.2. <A
HREF="variant_fenris.html"
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
HREF="variant_issuezilla.html"
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
HREF="variant_scarab.html"
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
HREF="variant_perforce.html"
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
HREF="variant_sourceforge.html"
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
></DL
@ -794,14 +794,14 @@ HREF="dbdoc.html"
><DL
><DT
>C.2.1. <A
HREF="dbdoc.html#AEN2331"
HREF="dbdoc.html#AEN2340"
>Bugzilla Database Basics</A
></DT
><DD
><DL
><DT
>C.2.1.1. <A
HREF="dbdoc.html#AEN2360"
HREF="dbdoc.html#AEN2369"
>Bugzilla Database Tables</A
></DT
></DL
@ -826,7 +826,7 @@ HREF="patches.html"
>D.1. <A
HREF="rewrite.html"
>Apache <TT
CLASS="FILENAME"
CLASS="filename"
>mod_rewrite</TT
> magic</A
></DT
@ -854,12 +854,12 @@ HREF="bzhacking.html"
><DL
><DT
>D.5.1. <A
HREF="bzhacking.html#AEN2495"
HREF="bzhacking.html#AEN2504"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
HREF="bzhacking.html#AEN2509"
HREF="bzhacking.html#AEN2518"
>Coding Style for Bugzilla</A
></DT
></DL
@ -875,62 +875,62 @@ HREF="gfdl.html"
><DL
><DT
>0. <A
HREF="gfdl_0.html"
HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
HREF="gfdl_1.html"
HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
HREF="gfdl_2.html"
HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
HREF="gfdl_3.html"
HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
HREF="gfdl_4.html"
HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
HREF="gfdl_5.html"
HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="gfdl_6.html"
HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="gfdl_7.html"
HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="gfdl_8.html"
HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="gfdl_9.html"
HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="gfdl_10.html"
HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="gfdl_howto.html"
HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
@ -972,58 +972,58 @@ HREF="stepbystep.html#AEN799"
></DT
><DT
>3-3. <A
HREF="win32.html#AEN1038"
HREF="win32.html#AEN1048"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
HREF="win32.html#AEN1224"
HREF="win32.html#AEN1233"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
HREF="programadmin.html#AEN1461"
HREF="programadmin.html#AEN1470"
>Creating some Components</A
></DT
><DT
>4-2. <A
HREF="programadmin.html#AEN1490"
HREF="programadmin.html#AEN1499"
>Common Use of Versions</A
></DT
><DT
>4-3. <A
HREF="programadmin.html#AEN1494"
HREF="programadmin.html#AEN1503"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
HREF="programadmin.html#AEN1522"
HREF="programadmin.html#AEN1531"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
HREF="programadmin.html#AEN1558"
HREF="programadmin.html#AEN1567"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
HREF="programadmin.html#AEN1575"
HREF="programadmin.html#AEN1584"
>Creating a New Group</A
></DT
><DT
>4-7. <A
HREF="programadmin.html#AEN1592"
HREF="programadmin.html#AEN1601"
>Bugzilla Groups</A
></DT
><DT
>D-1. <A
HREF="setperl.html#AEN2439"
HREF="setperl.html#AEN2448"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
HREF="glossary.html#AEN2736"
HREF="glossary.html#AEN2769"
>A Sample Product</A
></DT
></DL

88
webtools/bugzilla/docs/html/init4me.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Using Bugzilla-Conclusion"
HREF="usingbz-conc.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="usingbz-conc.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="INIT4ME"
NAME="init4me"
>2.4. Where can I find my user preferences?</A
></H1
><TABLE
@ -101,7 +101,7 @@ VALIGN="TOP"
></TR
></TABLE
><P
> Customized User Preferences offer tremendous versatility to your
>&#13; Customized User Preferences offer tremendous versatility to your
individual Bugzilla experience. Let's plunge into what you can
do! The first step is to click the "Edit prefs" link at the
footer of each page once you have logged in to <A
@ -111,15 +111,15 @@ TARGET="_top"
>.
</P
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="ACCOUNTSETTINGS"
NAME="accountsettings"
>2.4.1. Account Settings</A
></H2
><P
> On this page, you can change your basic Account Settings,
>&#13; On this page, you can change your basic Account Settings,
including your password and full name. For security reasons,
in order to change anything on this page you must type your
<EM
@ -146,23 +146,23 @@ CLASS="QUOTE"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="EMAILSETTINGS"
NAME="emailsettings"
>2.4.2. Email Settings</A
></H2
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="NOTIFICATION"
NAME="notification"
>2.4.2.1. Email Notification</A
></H3
><P
> Here you can reduce or increase the amount of email sent you
>&#13; Here you can reduce or increase the amount of email sent you
from Bugzilla. Although this is referred to as
<SPAN
CLASS="QUOTE"
@ -188,19 +188,19 @@ HREF="tinderbox.html"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="NEWEMAILTECH"
NAME="newemailtech"
>2.4.2.2. New Email Technology</A
></H3
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -216,7 +216,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This option may not be available in all Bugzilla
>&#13; This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
@ -229,13 +229,13 @@ VALIGN="TOP"
></TABLE
></DIV
><P
> Disregard the warnings about "experimental and bleeding
>&#13; Disregard the warnings about "experimental and bleeding
edge"; the code to handle email in a cleaner manner than
that historically used for Bugzilla is quite robust and
well-tested now.
</P
><P
> I recommend you enable the option, "Click here to sign up
>&#13; I recommend you enable the option, "Click here to sign up
(and risk any bugs)". Your email-box will thank you for it.
The fundamental shift in "newemailtech" is away from
standard UNIX "diff" output, which is quite ugly, to a
@ -243,19 +243,19 @@ VALIGN="TOP"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="WATCHSETTINGS"
NAME="watchsettings"
>2.4.2.3. "Watching" Users</A
></H3
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -271,7 +271,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This option may not be available in all Bugzilla
>&#13; This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
@ -282,7 +282,7 @@ VALIGN="TOP"
></TABLE
></DIV
><P
> By entering user email names into the "Users to watch" text
>&#13; By entering user email names into the "Users to watch" text
entry box, delineated by commas, you can watch bugs of other
users. This powerful functionality enables seamless
transitions as developers change projects, managers wish to
@ -294,19 +294,19 @@ VALIGN="TOP"
></DIV
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="FOOTERSETTINGS"
NAME="footersettings"
>2.4.3. Page Footer</A
></H2
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -322,7 +322,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> By default, this page is quite barren. However, go explore
>&#13; By default, this page is quite barren. However, go explore
the Query Page some more; you will find that you can store
numerous queries on the server, so if you regularly run a
particular query it is just a drop-down menu away. On this
@ -334,7 +334,7 @@ VALIGN="TOP"
></TABLE
></DIV
><P
> If you have many stored queries on the server, here you will
>&#13; If you have many stored queries on the server, here you will
find individual drop-downs for each stored query. Each
drop-down gives you the option of that query appearing on the
footer of every page in Bugzilla! This gives you powerful
@ -342,11 +342,11 @@ VALIGN="TOP"
is an excellent way to impress your boss...
</P
><DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
@ -380,15 +380,15 @@ VALIGN="TOP"
></DIV
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="PERMISSIONSETTINGS"
NAME="permissionsettings"
>2.4.4. Permissions</A
></H2
><P
> This is a purely informative page which outlines your current
>&#13; This is a purely informative page which outlines your current
permissions on this installation of Bugzilla. If you have
permissions to grant certain permissions to other users, the
"other users" link appears on this page as well as the footer.

32
webtools/bugzilla/docs/html/installation.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="ERRATA"
HREF="errata.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="errata.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="INSTALLATION"
NAME="installation"
>Chapter 3. Installation</A
></H1
><DIV
@ -100,12 +100,12 @@ HREF="stepbystep.html#AEN515"
></DT
><DT
>3.2.3. <A
HREF="stepbystep.html#INSTALL-MYSQL"
HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A
></DT
><DT
>3.2.4. <A
HREF="stepbystep.html#INSTALL-PERL"
HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A
></DT
><DT
@ -162,7 +162,7 @@ HREF="stepbystep.html#AEN721"
>3.2.15. <A
HREF="stepbystep.html#AEN768"
>Tweaking <TT
CLASS="FILENAME"
CLASS="filename"
>localconfig</TT
></A
></DT
@ -217,28 +217,28 @@ HREF="geninstall.html#AEN948"
></DT
><DT
>3.5.3. <A
HREF="geninstall.html#HTACCESS"
HREF="geninstall.html#htaccess"
><TT
CLASS="FILENAME"
CLASS="filename"
>.htaccess</TT
> files and security</A
></DT
><DT
>3.5.4. <A
HREF="geninstall.html#MOD_THROTTLE"
HREF="geninstall.html#mod-throttle"
><TT
CLASS="FILENAME"
CLASS="filename"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
HREF="geninstall.html#CONTENT_TYPE"
HREF="geninstall.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
HREF="geninstall.html#UNIXHISTORY"
HREF="geninstall.html#unixhistory"
>UNIX Installation Instructions History</A
></DT
></DL
@ -252,17 +252,17 @@ HREF="win32.html"
><DL
><DT
>3.6.1. <A
HREF="win32.html#WININSTALL"
HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A
></DT
><DT
>3.6.2. <A
HREF="win32.html#ADDLWINTIPS"
HREF="win32.html#addlwintips"
>Additional Windows Tips</A
></DT
><DT
>3.6.3. <A
HREF="win32.html#BZLDAP"
HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A
></DT
></DL
@ -270,7 +270,7 @@ HREF="win32.html#BZLDAP"
></DL
></DIV
><P
> These installation instructions are presented assuming you are
>&#13; These installation instructions are presented assuming you are
installing on a UNIX or completely POSIX-compliant system. If
you are installing on Microsoft Windows or another oddball
operating system, please consult the appropriate sections in

6
webtools/bugzilla/docs/html/integration.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Bonsai"
HREF="bonsai.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="bonsai.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="INTEGRATION"
NAME="integration"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</A
></H1
><DIV

22
webtools/bugzilla/docs/html/newversions.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Credits"
HREF="credits.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,29 +66,29 @@ HREF="credits.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="NEWVERSIONS"
NAME="newversions"
>1.4. New Versions</A
></H1
><P
> This is the 2.14 version of The Bugzilla Guide. If you are
>&#13; This is the 2.14 version of The Bugzilla Guide. If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.
</P
><P
> This document can be found in the following places:
>&#13; This document can be found in the following places:
</P
><P
> <P
>&#13; <P
></P
><UL
><LI
><P
> <A
>&#13; <A
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>TriloBYTE</A
@ -97,7 +97,7 @@ TARGET="_top"
></LI
><LI
><P
> <A
>&#13; <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
>Mozilla.org</A
@ -106,7 +106,7 @@ TARGET="_top"
></LI
><LI
><P
> <A
>&#13; <A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>The Linux
@ -118,7 +118,7 @@ TARGET="_top"
>
</P
><P
> The latest version of this document can be checked out via CVS.
>&#13; The latest version of this document can be checked out via CVS.
Please follow the instructions available at <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"

49
webtools/bugzilla/docs/html/osx.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="BSD Installation Notes"
HREF="bsdinstall.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,40 +66,40 @@ HREF="bsdinstall.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="OSX"
NAME="osx"
>3.3. Mac OS X Installation Notes</A
></H1
><P
> There are a lot of common libraries and utilities out there
>&#13; There are a lot of common libraries and utilities out there
that Apple did not include with Mac OS X, but which run
perfectly well on it. The GD library, which Bugzilla needs to
do bug graphs, is one of these.
</P
><P
> The easiest way to get a lot of these is with a program called
>&#13; The easiest way to get a lot of these is with a program called
Fink, which is similar in nature to the CPAN installer, but
installs common GNU utilities. Fink is available from
&#60;http://sourceforge.net/projects/fink/&#62;.
</P
><P
> Follow the instructions for setting up Fink. Once it's
>&#13; Follow the instructions for setting up Fink. Once it's
installed, you'll want to run the following as root:
<B
CLASS="COMMAND"
CLASS="command"
>fink install gd</B
>
</P
><P
> It will prompt you for a number of dependencies, type 'y' and
>&#13; It will prompt you for a number of dependencies, type 'y' and
hit enter to install all of the dependencies. Then watch it
work.
</P
><P
> To prevent creating conflicts with the software that Apple
>&#13; To prevent creating conflicts with the software that Apple
installs by default, Fink creates its own directory tree at
/sw where it installs most of the software that it installs.
This means your libraries and headers for libgd will be at
@ -111,15 +111,15 @@ CLASS="COMMAND"
:-)
</P
><P
> Instead of typing <SPAN
>&#13; Instead of typing <SPAN
CLASS="QUOTE"
>"install GD"</SPAN
> at the
<TT
CLASS="PROMPT"
CLASS="prompt"
>cpan&#62;</TT
> prompt, type <B
CLASS="COMMAND"
CLASS="command"
>look
GD</B
>. This should go through the motions of
@ -127,13 +127,13 @@ CLASS="COMMAND"
open a shell and drop you into the build directory. Apply the
following patch to the Makefile.PL file (save the patch into a
file and use the command <B
CLASS="COMMAND"
CLASS="command"
>patch &#60;
patchfile</B
>:
</P
><P
> <TABLE
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
@ -142,8 +142,9 @@ WIDTH="100%"
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>
CLASS="programlisting"
>&#13;
--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000
+++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001
@@ -3,8 +3,8 @@
@ -176,7 +177,7 @@ CLASS="PROGRAMLISTING"
>
</P
><P
> Then, run these commands to finish the installation of the perl module:
>&#13; Then, run these commands to finish the installation of the perl module:
<P
></P
><TABLE
@ -185,35 +186,35 @@ BORDER="0"
><TR
><TD
><B
CLASS="COMMAND"
CLASS="command"
>perl Makefile.PL</B
></TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
CLASS="command"
>make</B
></TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
CLASS="command"
>make test</B
></TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
CLASS="command"
>make install</B
></TD
></TR
><TR
><TD
>And don't forget to run <B
CLASS="COMMAND"
CLASS="command"
>exit</B
> to get back to cpan.</TD
></TR
@ -224,7 +225,7 @@ CLASS="COMMAND"
>
</P
><P
> Happy Hacking!
>&#13; Happy Hacking!
</P
></DIV
><DIV

14
webtools/bugzilla/docs/html/patches.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Apache mod_rewrite magic"
HREF="rewrite.html"></HEAD
><BODY
CLASS="APPENDIX"
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="rewrite.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
CLASS="appendix"
><H1
><A
NAME="PATCHES"
NAME="patches"
>Appendix D. Useful Patches and Utilities for Bugzilla</A
></H1
><DIV
@ -80,7 +80,7 @@ CLASS="TOC"
>D.1. <A
HREF="rewrite.html"
>Apache <TT
CLASS="FILENAME"
CLASS="filename"
>mod_rewrite</TT
> magic</A
></DT
@ -108,12 +108,12 @@ HREF="bzhacking.html"
><DL
><DT
>D.5.1. <A
HREF="bzhacking.html#AEN2495"
HREF="bzhacking.html#AEN2504"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
HREF="bzhacking.html#AEN2509"
HREF="bzhacking.html#AEN2518"
>Coding Style for Bugzilla</A
></DT
></DL
@ -174,7 +174,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Apache <TT
CLASS="FILENAME"
CLASS="filename"
>mod_rewrite</TT
> magic</TD
></TR

66
webtools/bugzilla/docs/html/postinstall-check.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="User Administration"
HREF="useradmin.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,28 +66,28 @@ HREF="useradmin.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="POSTINSTALL-CHECK"
NAME="postinstall-check"
>4.1. Post-Installation Checklist</A
></H1
><P
> After installation, follow the checklist below to help ensure
>&#13; After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla
setup.
</P
><DIV
CLASS="PROCEDURE"
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
> Bring up <TT
CLASS="FILENAME"
>&#13; Bring up <TT
CLASS="filename"
>editparams.cgi</TT
> in your web
browser. This should be available as the <SPAN
@ -110,7 +110,7 @@ CLASS="QUOTE"
will be sent with the maintainer as the return email
address.</P
><P
> Set <SPAN
>&#13; Set <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> to <EM
@ -129,7 +129,7 @@ CLASS="QUOTE"
qualified domain name and web server path to your Bugzilla
installation.</P
><P
> For example, if your bugzilla query page is
>&#13; For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<SPAN
CLASS="QUOTE"
@ -148,7 +148,7 @@ CLASS="QUOTE"
which groups of users are allowed to see and edit the
bug.</P
><P
> Set "usebuggroups" to "on" <EM
>&#13; Set "usebuggroups" to "on" <EM
>only</EM
> if you
may wish to restrict access to products. I suggest leaving
@ -160,7 +160,7 @@ CLASS="QUOTE"
></LI
><LI
><P
> <SPAN
>&#13; <SPAN
CLASS="QUOTE"
>"usebuggroupsentry"</SPAN
>, when set to
@ -172,7 +172,7 @@ CLASS="QUOTE"
installations where product isolation is a necessity.
</P
><P
> Set "usebuggroupsentry" to "on" if you absolutely need to
>&#13; Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter
@ -182,7 +182,7 @@ CLASS="QUOTE"
></LI
><LI
><P
> You run into an interesting problem when Bugzilla reaches a
>&#13; You run into an interesting problem when Bugzilla reaches a
high level of continuous activity. MySQL supports only
table-level write locking. What this means is that if
someone needs to make a change to a bug, they will lock the
@ -200,16 +200,16 @@ CLASS="QUOTE"
extremely high-traffic Bugzilla databases.
</P
><P
> Set "shadowdb" to "bug_shadowdb" if you will be running a
>&#13; Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database
enables many simultaneous users to read and write to the
database without interfering with one another.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -225,7 +225,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Enabling "shadowdb" can adversely affect the stability
>&#13; Enabling "shadowdb" can adversely affect the stability
of your installation of Bugzilla. You should regularly
check that your database is in sync. It is often
advisable to force a shadow database sync nightly via
@ -253,7 +253,7 @@ CLASS="QUOTE"
comments per day.
</P
><P
> If you use the "shadowdb" option, it is only natural that
>&#13; If you use the "shadowdb" option, it is only natural that
you should turn the "queryagainstshadowdb" option "On" as
well. Otherwise you are replicating data into a shadow
database for no reason!
@ -284,27 +284,27 @@ CLASS="QUOTE"
these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy
your <TT
CLASS="FILENAME"
CLASS="filename"
>data/params</TT
> file somewhere safe
before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have
restored your <TT
CLASS="FILENAME"
CLASS="filename"
>data/params</TT
> file.</P
><P
> If you have custom logos or HTML you must put in place to
>&#13; If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in
the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
or "blurbhtml" text boxes.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -320,7 +320,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> The "headerhtml" text box is the HTML printed out
>&#13; The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page,
@ -346,7 +346,7 @@ CLASS="QUOTE"
is read as the text to send to the new user along with their
password message.</P
><P
> Add any text you wish to the "passwordmail" parameter box.
>&#13; Add any text you wish to the "passwordmail" parameter box.
For instance, many people choose to use this box to give a
quick training blurb about how to use Bugzilla at your site.
</P
@ -389,7 +389,7 @@ CLASS="QUOTE"
their status even more than that which can be indicated by
the Resolution fields.</P
><P
> Do you want to use the QA Contact ("useqacontact") and
>&#13; Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance
@ -399,7 +399,7 @@ CLASS="QUOTE"
></LI
><LI
><P
> Set "whinedays" to the amount of days you want to let bugs
>&#13; Set "whinedays" to the amount of days you want to let bugs
go in the "New" or "Reopened" state before notifying people
they have untouched new bugs. If you do not plan to use
this feature, simply do not set up the whining cron job
@ -421,15 +421,15 @@ CLASS="QUOTE"
require that most other changes come with an
explanation.</P
><P
> Set the "commenton" options according to your site policy.
>&#13; Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users resolve,
reassign, or reopen bugs at the very least.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -445,7 +445,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> It is generally far better to require a developer
>&#13; It is generally far better to require a developer
comment when resolving bugs than not. Few things are
more annoying to bug database users than having a
developer mark a bug "fixed" without any comment as to
@ -482,7 +482,7 @@ CLASS="QUOTE"
security to prevent snooping, watchers are not a good
idea.</P
><P
> However, for most sites you should set
>&#13; However, for most sites you should set
<SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN

353
webtools/bugzilla/docs/html/programadmin.html
View File

@ -20,7 +20,7 @@ REL="NEXT"
TITLE="Bugzilla Security"
HREF="security.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -67,11 +67,11 @@ HREF="security.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="PROGRAMADMIN"
NAME="programadmin"
>4.3. Product, Component, Milestone, and Version
Administration</A
></H1
@ -99,11 +99,11 @@ VALIGN="TOP"
></TR
></TABLE
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="PRODUCTS"
NAME="products"
>4.3.1. Products</A
></H2
><FONT
@ -111,10 +111,10 @@ COLOR="RED"
>Formerly, and in some spots still, called
"Programs"</FONT
><P
> <A
HREF="glossary.html#GLOSS_PRODUCT"
>&#13; <A
HREF="glossary.html#gloss-product"
><I
CLASS="GLOSSTERM"
CLASS="glossterm"
>Products</I
></A
> are
@ -124,7 +124,7 @@ CLASS="GLOSSTERM"
products (website, meetings...)
</P
><P
> A Product (formerly called "Program", and still referred to
>&#13; A Product (formerly called "Program", and still referred to
that way in some portions of the source code) controls some
very important functions. The number of "votes" available for
users to vote for the most important bugs is set per-product,
@ -141,57 +141,14 @@ CLASS="GLOSSTERM"
TYPE="1"
><LI
><P
> Select "components" from the yellow footer
>&#13; Select "components" from the yellow footer
</P
><DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="90%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> It may seem counterintuitive to click "components" when
you want to edit the properties associated with
Products. This is one of a long list of things we want
in Bugzilla 3.0...
</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
> Select the "Add" link to the right of "Add a new product".
</P
></LI
><LI
><P
> Enter the name of the product and a description. The
Description field is free-form.
</P
></LI
></OL
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
@ -207,7 +164,50 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Don't worry about the "Closed for bug entry", "Maximum Votes
>&#13; It may seem counterintuitive to click "components" when
you want to edit the properties associated with
Products. This is one of a long list of things we want
in Bugzilla 3.0...
</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13; Select the "Add" link to the right of "Add a new product".
</P
></LI
><LI
><P
>&#13; Enter the name of the product and a description. The
Description field is free-form.
</P
></LI
></OL
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Don't worry about the "Closed for bug entry", "Maximum Votes
per person", "Maximum votes a person can put on a single
bug", "Number of votes a bug in this Product needs to
automatically get out of the UNCOMFIRMED state", and
@ -219,34 +219,34 @@ VALIGN="TOP"
></DIV
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="COMPONENTS"
NAME="components"
>4.3.2. Components</A
></H2
><P
> Components are subsections of a Product.
>&#13; Components are subsections of a Product.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1461"
NAME="AEN1470"
></A
><P
><B
>Example 4-1. Creating some Components</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN1463"
NAME="AEN1472"
></A
><P
></P
><P
> The computer game you are designing may have a "UI"
>&#13; The computer game you are designing may have a "UI"
component, an "API" component, a "Sound System"
component, and a "Plugins" component, each overseen by
a different programmer. It often makes sense to divide
@ -272,7 +272,7 @@ NAME="AEN1463"
to the Component.
</P
><P
> To create a new Component:
>&#13; To create a new Component:
</P
><P
></P
@ -280,31 +280,31 @@ NAME="AEN1463"
TYPE="1"
><LI
><P
> Select the "Edit components" link from the "Edit product"
>&#13; Select the "Edit components" link from the "Edit product"
page
</P
></LI
><LI
><P
> Select the "Add" link to the right of the "Add a new
>&#13; Select the "Add" link to the right of the "Add a new
component" text on the "Select Component" page.
</P
></LI
><LI
><P
> Fill out the "Component" field, a short "Description", and
>&#13; Fill out the "Component" field, a short "Description", and
the "Initial Owner". The Component and Description fields
are free-form; the "Initial Owner" field must be that of a
user ID already existing in the database. If the initial
owner does not exist, Bugzilla will refuse to create the
component.
<DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="90%"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -319,7 +319,7 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Is your "Default Owner" a user who is not yet in the
>&#13; Is your "Default Owner" a user who is not yet in the
database? No problem.
<P
></P
@ -327,19 +327,19 @@ VALIGN="TOP"
TYPE="a"
><LI
><P
> Select the "Log out" link on the footer of the
>&#13; Select the "Log out" link on the footer of the
page.
</P
></LI
><LI
><P
> Select the "New Account" link on the footer of
>&#13; Select the "New Account" link on the footer of
the "Relogin" page
</P
></LI
><LI
><P
> Type in the email address of the default owner
>&#13; Type in the email address of the default owner
you want to create in the "E-mail address"
field, and her full name in the "Real name"
field, then select the "Submit Query" button.
@ -347,7 +347,7 @@ TYPE="a"
></LI
><LI
><P
> Now select "Log in" again, type in your login
>&#13; Now select "Log in" again, type in your login
information, and you can modify the product to
use the Default Owner information you require.
</P
@ -364,7 +364,7 @@ TYPE="a"
></LI
><LI
><P
> Either Edit more components or return to the Bugzilla
>&#13; Either Edit more components or return to the Bugzilla
Query Page. To return to the Product you were editing, you
must select the Components link as before.
</P
@ -372,36 +372,36 @@ TYPE="a"
></OL
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="VERSIONS"
NAME="versions"
>4.3.3. Versions</A
></H2
><P
> Versions are the revisions of the product, such as "Flinders
>&#13; Versions are the revisions of the product, such as "Flinders
3.1", "Flinders 95", and "Flinders 2000". Using Versions
helps you isolate code changes and are an aid in reporting.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1490"
NAME="AEN1499"
></A
><P
><B
>Example 4-2. Common Use of Versions</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN1492"
NAME="AEN1501"
></A
><P
></P
><P
> A user reports a bug against Version "Beta 2.0" of your
>&#13; A user reports a bug against Version "Beta 2.0" of your
product. The current Version of your software is
"Release Candidate 1", and no longer has the bug. This
will help you triage and classify bugs according to
@ -416,23 +416,23 @@ NAME="AEN1492"
></DIV
>
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1494"
NAME="AEN1503"
></A
><P
><B
>Example 4-3. A Different Use of Versions</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN1496"
NAME="AEN1505"
></A
><P
></P
><P
> This field has been used to good effect by an online
>&#13; This field has been used to good effect by an online
service provider in a slightly different way. They had
three versions of the product: "Production", "QA", and
"Dev". Although it may be the same product, a bug in
@ -450,7 +450,7 @@ NAME="AEN1496"
>
</P
><P
> To create and edit Versions:
>&#13; To create and edit Versions:
</P
><P
></P
@ -458,32 +458,32 @@ NAME="AEN1496"
TYPE="1"
><LI
><P
> From the "Edit product" screen, select "Edit Versions"
>&#13; From the "Edit product" screen, select "Edit Versions"
</P
></LI
><LI
><P
> You will notice that the product already has the default
>&#13; You will notice that the product already has the default
version "undefined". If your product doesn't use version
numbers, you may want to leave this as it is or edit it so
that it is "---". You can then go back to the edit
versions page and add new versions to your product.
</P
><P
> Otherwise, click the "Add" button to the right of the "Add
>&#13; Otherwise, click the "Add" button to the right of the "Add
a new version" text.
</P
></LI
><LI
><P
> Enter the name of the Version. This can be free-form
>&#13; Enter the name of the Version. This can be free-form
characters up to the limit of the text box. Then select
the "Add" button.
</P
></LI
><LI
><P
> At this point you can select "Edit" to edit more Versions,
>&#13; At this point you can select "Edit" to edit more Versions,
or return to the "Query" page, from which you can navigate
back to the product through the "components" link at the
foot of the Query page.
@ -492,26 +492,26 @@ TYPE="1"
></OL
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="MILESTONES"
NAME="milestones"
>4.3.4. Milestones</A
></H2
><P
> Milestones are "targets" that you plan to get a bug fixed by.
>&#13; Milestones are "targets" that you plan to get a bug fixed by.
For example, you have a bug that you plan to fix for your 3.0
release, it would be assigned the milestone of 3.0. Or, you
have a bug that you plan to fix for 2.8, this would have a
milestone of 2.8.
</P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -527,7 +527,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Milestone options will only appear for a Product if you
>&#13; Milestone options will only appear for a Product if you
turned the "usetargetmilestone" field in the "Edit
Parameters" screen "On".
</P
@ -536,7 +536,7 @@ VALIGN="TOP"
></TABLE
></DIV
><P
> To create new Milestones, set Default Milestones, and set
>&#13; To create new Milestones, set Default Milestones, and set
Milestone URL:
</P
><P
@ -545,40 +545,40 @@ VALIGN="TOP"
TYPE="1"
><LI
><P
> Select "edit milestones"
>&#13; Select "edit milestones"
</P
></LI
><LI
><P
> Select "Add" to the right of the "Add a new milestone"
>&#13; Select "Add" to the right of the "Add a new milestone"
text
</P
></LI
><LI
><P
> Enter the name of the Milestone in the "Milestone" field.
>&#13; Enter the name of the Milestone in the "Milestone" field.
You can optionally set the "Sortkey", which is a positive
or negative number (-255 to 255) that defines where in the
list this particular milestone appears. Select "Add".
</P
><DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1522"
NAME="AEN1531"
></A
><P
><B
>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN1524"
NAME="AEN1533"
></A
><P
></P
><P
> Let's say you create a target milestone called
>&#13; Let's say you create a target milestone called
"Release 1.0", with Sortkey set to "0". Later, you
realize that you will have a public beta, called
"Beta1". You can create a Milestone called "Beta1",
@ -593,17 +593,17 @@ NAME="AEN1524"
></LI
><LI
><P
> If you want to add more milestones, select the "Edit"
>&#13; If you want to add more milestones, select the "Edit"
link. If you don't, well shoot, you have to go back to the
"query" page and select "components" again, and make your
way back to the Product you were editing.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -618,7 +618,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This is another in the list of unusual user interface
>&#13; This is another in the list of unusual user interface
decisions that we'd like to get cleaned up. Shouldn't
there be a link to the effect of "edit the Product I
was editing when I ended up here"? In any case,
@ -635,21 +635,21 @@ VALIGN="TOP"
></LI
><LI
><P
> From the Edit product screen again (once you've made your
>&#13; From the Edit product screen again (once you've made your
way back), enter the URL for a description of what your
milestones are for this product in the "Milestone URL"
field. It should be of the format
"http://www.foo.com/bugzilla/product_milestones.html"
</P
><P
> Some common uses of this field include product
>&#13; Some common uses of this field include product
descriptions, product roadmaps, and of course a simple
description of the meaning of each milestone.
</P
></LI
><LI
><P
> If you're using Target Milestones, the "Default Milestone"
>&#13; If you're using Target Milestones, the "Default Milestone"
field must have some kind of entry. If you really don't
care if people set coherent Target Milestones, simply
leave this at the default, "---". However, controlling
@ -662,15 +662,15 @@ VALIGN="TOP"
></OL
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="VOTING"
NAME="voting"
>4.3.5. Voting</A
></H2
><P
> The concept of "voting" is a poorly understood, yet powerful
>&#13; The concept of "voting" is a poorly understood, yet powerful
feature for the management of open-source projects. Each user
is assigned so many Votes per product, which they can freely
reassign (or assign multiple votes to a single bug). This
@ -681,7 +681,7 @@ NAME="VOTING"
attention so they don't sit for a long time awaiting triage.
</P
><P
> The daunting challenge of Votes is deciding where you draw the
>&#13; The daunting challenge of Votes is deciding where you draw the
line for a "vocal majority". If you only have a user base of
100 users, setting a low threshold for bugs to move from
UNCONFIRMED to NEW makes sense. As the Bugzilla user base
@ -698,19 +698,19 @@ NAME="VOTING"
TYPE="1"
><LI
><P
> Navigate to the "Edit product" screen for the Product you
>&#13; Navigate to the "Edit product" screen for the Product you
wish to modify
</P
></LI
><LI
><P
> Set "Maximum Votes per person" to your calculated value.
>&#13; Set "Maximum Votes per person" to your calculated value.
Setting this field to "0" disables voting.
</P
></LI
><LI
><P
> Set "Maximum Votes a person can put on a single bug" to
>&#13; Set "Maximum Votes a person can put on a single bug" to
your calculated value. It should probably be some number
lower than the "Maximum votes per person". Setting this
field to "0" disables voting, but leaves the voting
@ -719,7 +719,7 @@ TYPE="1"
></LI
><LI
><P
> Set "Number of votes a bug in this product needs to
>&#13; Set "Number of votes a bug in this product needs to
automatically get out of the UNCONFIRMED state" to your
calculated number. Setting this field to "0" disables
the automatic move of bugs from UNCONFIRMED to NEW. Some
@ -727,12 +727,12 @@ TYPE="1"
Votes if your Bugzilla user base is unable to affect which
bugs appear on Development radar?
<DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="90%"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -747,7 +747,7 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> You should probably set this number to higher than a
>&#13; You should probably set this number to higher than a
small coalition of Bugzilla users can influence it.
Most sites use this as a "referendum" mechanism -- if
users are able to vote a bug out of UNCONFIRMED, it is
@ -764,44 +764,44 @@ VALIGN="TOP"
></LI
><LI
><P
> Once you have adjusted the values to your preference,
>&#13; Once you have adjusted the values to your preference,
select the "Update" button.
</P
></LI
></OL
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="GROUPS"
NAME="groups"
>4.3.6. Groups and Group Security</A
></H2
><P
> Groups can be very useful in bugzilla, because they allow
>&#13; Groups can be very useful in bugzilla, because they allow
users to isolate bugs or products that should only be seen by
certain people. Groups can also be a complicated minefield of
interdependencies and weirdness if mismanaged.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1558"
NAME="AEN1567"
></A
><P
><B
>Example 4-5. When to Use Group Security</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN1560"
NAME="AEN1569"
></A
><P
></P
><P
> Many Bugzilla sites isolate "Security-related" bugs from
>&#13; Many Bugzilla sites isolate "Security-related" bugs from
all other bugs. This way, they can have a fix ready
before the security vulnerability is announced to the
world. You can create a "Security" product which, by
@ -825,11 +825,11 @@ NAME="AEN1560"
into two categories: Generic and Product-Based.
</P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -845,7 +845,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Groups in Bugzilla are a complicated beast that evolved out
>&#13; Groups in Bugzilla are a complicated beast that evolved out
of very simple user permission bitmasks, apparently itself
derived from common concepts in UNIX access controls. A
"bitmask" is a fixed-length number whose value can describe
@ -863,7 +863,7 @@ VALIGN="TOP"
next 32, etc.
</P
><P
> Similarly, Bugzilla offers a bitmask to define group
>&#13; Similarly, Bugzilla offers a bitmask to define group
permissions, with an internal limit of 64. Several are
already occupied by built-in permissions. The way around
this limitation is to avoid assigning groups to products if
@ -879,7 +879,7 @@ VALIGN="TOP"
></TABLE
></DIV
><P
> To enable Generic Group Security ("usebuggroups"):
>&#13; To enable Generic Group Security ("usebuggroups"):
</P
><P
></P
@ -887,47 +887,47 @@ VALIGN="TOP"
TYPE="1"
><LI
><P
> Turn "On" "usebuggroups" in the "Edit Parameters" screen.
>&#13; Turn "On" "usebuggroups" in the "Edit Parameters" screen.
</P
></LI
><LI
><P
> You will generally have no groups set up. Select the
>&#13; You will generally have no groups set up. Select the
"groups" link in the footer.
</P
></LI
><LI
><P
> Take a moment to understand the instructions on the "Edit
>&#13; Take a moment to understand the instructions on the "Edit
Groups" screen. Once you feel confident you understand
what is expected of you, select the "Add Group" link.
</P
></LI
><LI
><P
> Fill out the "New Name" (remember, no spaces!), "New
>&#13; Fill out the "New Name" (remember, no spaces!), "New
Description", and "New User RegExp" fields. "New User
RegExp" allows you to automatically place all users who
fulfill the Regular Expression into the new group.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1575"
NAME="AEN1584"
></A
><P
><B
>Example 4-6. Creating a New Group</B
></P
><DIV
CLASS="INFORMALEXAMPLE"
CLASS="informalexample"
><A
NAME="AEN1577"
NAME="AEN1586"
></A
><P
></P
><P
> I created a group called DefaultGroup with a
>&#13; I created a group called DefaultGroup with a
description of <SPAN
CLASS="QUOTE"
>"This is simply a group to play
@ -950,14 +950,14 @@ CLASS="QUOTE"
></LI
></OL
><P
> To enable Product-Based Group Security (usebuggroupsentry):
>&#13; To enable Product-Based Group Security (usebuggroupsentry):
</P
><DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
@ -973,7 +973,7 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Don't forget that you only have 64 groups masks available,
>&#13; Don't forget that you only have 64 groups masks available,
total, for your installation of Bugzilla! If you plan on
having more than 50 products in your individual Bugzilla
installation, and require group security for your products,
@ -991,16 +991,16 @@ VALIGN="TOP"
TYPE="1"
><LI
><P
> Turn "On" "usebuggroups" and "usebuggroupsentry" in the
>&#13; Turn "On" "usebuggroups" and "usebuggroupsentry" in the
"Edit Parameters" screen.
</P
><DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="90%"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -1015,7 +1015,7 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> "usebuggroupsentry" has the capacity to prevent the
>&#13; "usebuggroupsentry" has the capacity to prevent the
administrative user from directly altering bugs because
of conflicting group permissions. If you plan on using
"usebuggroupsentry", you should plan on restricting
@ -1031,7 +1031,7 @@ VALIGN="TOP"
></LI
><LI
><P
> You will generally have no Groups set up, unless you
>&#13; You will generally have no Groups set up, unless you
enabled "usebuggroupsentry" prior to creating any
Products. To create "Generic Group Security" groups,
follow the instructions given above. To create
@ -1044,19 +1044,20 @@ VALIGN="TOP"
></LI
></OL
><P
> You may find this example illustrative for how bug groups work.
>&#13; You may find this example illustrative for how bug groups work.
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN1592"
NAME="AEN1601"
></A
><P
><B
>Example 4-7. Bugzilla Groups</B
></P
><P
CLASS="LITERALLAYOUT"
>Bugzilla&nbsp;Groups&nbsp;example<br>
CLASS="literallayout"
><br>
Bugzilla&nbsp;Groups&nbsp;example<br>
-----------------------<br>
<br>
For&nbsp;this&nbsp;example,&nbsp;let&nbsp;us&nbsp;suppose&nbsp;we&nbsp;have&nbsp;four&nbsp;groups,&nbsp;call&nbsp;them<br>

20
webtools/bugzilla/docs/html/quicksearch.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Hacking Bugzilla"
HREF="bzhacking.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,30 +66,30 @@ HREF="bzhacking.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="QUICKSEARCH"
NAME="quicksearch"
>D.4. The Quicksearch Utility</A
></H1
><P
> Quicksearch is a new, experimental feature of the 2.12 release.
>&#13; Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
</P
><P
> The index.html page has been updated to include the QuickSearch
>&#13; The index.html page has been updated to include the QuickSearch
text box.
</P
><P
> To take full advantage of the query power, the Bugzilla
>&#13; To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
</P
><P
> Currently, keywords must be hard-coded in localconfig.js. If
>&#13; Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo"
@ -97,7 +97,7 @@ NAME="QUICKSEARCH"
but not those with the keyword "foo".
</P
><P
> Workarounds for Bugzilla users:
>&#13; Workarounds for Bugzilla users:
<P
></P
><TABLE
@ -120,7 +120,7 @@ BORDER="0"
>
</P
><P
> When this tool is ported from client-side JavaScript to
>&#13; When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can
be fixed. <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=70907"

24
webtools/bugzilla/docs/html/rewrite.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,19 +66,19 @@ HREF="setperl.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="REWRITE"
NAME="rewrite"
>D.1. Apache <TT
CLASS="FILENAME"
CLASS="filename"
>mod_rewrite</TT
> magic</A
></H1
><P
>Apache's <TT
CLASS="FILENAME"
CLASS="filename"
>mod_rewrite</TT
> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</P
><P
@ -87,9 +87,9 @@ CLASS="FILENAME"
TYPE="1"
><LI
><P
> Make it so if someone types
>&#13; Make it so if someone types
<TT
CLASS="COMPUTEROUTPUT"
CLASS="computeroutput"
>http://www.foo.com/12345</TT
>,
Bugzilla spits back
@ -99,17 +99,19 @@ CLASS="COMPUTEROUTPUT"
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>&#60;VirtualHost 12.34.56.78&#62;
CLASS="programlisting"
>&#13;
&#60;VirtualHost 12.34.56.78&#62;
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
&#60;/VirtualHost&#62;
</PRE
></FONT
></TD

16
webtools/bugzilla/docs/html/rhbugzilla.html
View File

@ -17,9 +17,9 @@ TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="NEXT"
TITLE="Loki Bugzilla (Fenris)"
HREF="variant_fenris.html"></HEAD
HREF="variant-fenris.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -57,7 +57,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant_fenris.html"
HREF="variant-fenris.html"
>Next</A
></TD
></TR
@ -66,15 +66,15 @@ HREF="variant_fenris.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="RHBUGZILLA"
NAME="rhbugzilla"
>7.1. Red Hat Bugzilla</A
></H1
><P
> Red Hat Bugzilla is probably the most popular Bugzilla variant
>&#13; Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
@ -120,7 +120,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant_fenris.html"
HREF="variant-fenris.html"
>Next</A
></TD
></TR

12
webtools/bugzilla/docs/html/scm.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,15 +66,15 @@ HREF="tinderbox.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="SCM"
NAME="scm"
>5.3. Perforce SCM</A
></H1
><P
> You can find the project page for Bugzilla and Teamtrack
>&#13; You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
@ -89,7 +89,7 @@ TARGET="_top"
>.
</P
><P
> Integration of Perforce with Bugzilla, once patches are applied,
>&#13; Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is

66
webtools/bugzilla/docs/html/security.html
View File

@ -20,7 +20,7 @@ REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -67,11 +67,11 @@ HREF="integration.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="SECURITY"
NAME="security"
>4.4. Bugzilla Security</A
></H1
><TABLE
@ -100,11 +100,11 @@ VALIGN="TOP"
></TR
></TABLE
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -120,7 +120,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Poorly-configured MySQL, Bugzilla, and FTP installations have
>&#13; Poorly-configured MySQL, Bugzilla, and FTP installations have
given attackers full access to systems in the past. Please
take these guidelines seriously, even for Bugzilla machines
hidden away behind your firewall. 80% of all computer
@ -131,13 +131,13 @@ VALIGN="TOP"
></TABLE
></DIV
><P
> Secure your installation.
>&#13; Secure your installation.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
@ -153,7 +153,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> These instructions must, of necessity, be somewhat vague
>&#13; These instructions must, of necessity, be somewhat vague
since Bugzilla runs on so many different platforms. If you
have refinements of these directions for specific platforms,
please submit them to <A
@ -173,7 +173,7 @@ TARGET="_top"
TYPE="1"
><LI
><P
> Ensure you are running at least MysQL version 3.22.32 or
>&#13; Ensure you are running at least MysQL version 3.22.32 or
newer. Earlier versions had notable security holes and
poorly secured default configuration choices.
</P
@ -189,7 +189,7 @@ TARGET="_top"
> The MySQL Privilege System</A
> until you can recite it from memory!</P
><P
> At the very least, ensure you password the "mysql -u root"
>&#13; At the very least, ensure you password the "mysql -u root"
account and the "bugs" account, establish grant table
rights (consult the Keystone guide in Appendix C: The
Bugzilla Database for some easy-to-use details) that do
@ -200,14 +200,14 @@ TARGET="_top"
></LI
><LI
><P
> Lock down /etc/inetd.conf. Heck, disable inet entirely on
>&#13; Lock down /etc/inetd.conf. Heck, disable inet entirely on
this box. It should only listen to port 25 for Sendmail
and port 80 for Apache.
</P
></LI
><LI
><P
> Do not run Apache as <SPAN
>&#13; Do not run Apache as <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>. This will
@ -215,12 +215,12 @@ CLASS="QUOTE"
Run it, instead, as a user with a name, set via your
httpd.conf file.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -235,7 +235,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> <SPAN
>&#13; <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> is a real user on UNIX systems.
@ -259,7 +259,7 @@ CLASS="QUOTE"
></LI
><LI
><P
> Ensure you have adequate access controls for the
>&#13; Ensure you have adequate access controls for the
$BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
directories, as well as the $BUGZILLA_HOME/localconfig and
$BUGZILLA_HOME/globals.pl files. The localconfig file
@ -274,12 +274,12 @@ CLASS="QUOTE"
bug information to those who may not be allowed to see it.
</P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -294,7 +294,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Bugzilla provides default .htaccess files to protect the
>&#13; Bugzilla provides default .htaccess files to protect the
most common Apache installations. However, you should
verify these are adequate according to the site-wide
security policy of your web server, and ensure that the
@ -305,7 +305,7 @@ VALIGN="TOP"
details.
</P
><P
> If you are using a web server that does not support the
>&#13; If you are using a web server that does not support the
.htaccess control method, <EM
>you are at
risk!</EM
@ -322,7 +322,7 @@ TARGET="_top"
></TABLE
></DIV
><P
> On Apache, you can use .htaccess files to protect access
>&#13; On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
TARGET="_top"
@ -334,34 +334,34 @@ TARGET="_top"
> for adequate protection in your data/ and shadow/ directories.
</P
><P
> Note the instructions which follow are Apache-specific.
>&#13; Note the instructions which follow are Apache-specific.
If you use IIS, Netscape, or other non-Apache web servers,
please consult your system documentation for how to secure
these files from being transmitted to curious users.
</P
><P
> Place the following text into a file named ".htaccess",
>&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/data
directory. <P
CLASS="LITERALLAYOUT"
CLASS="literallayout"
>&nbsp;&#60;Files&nbsp;comments&#62;&nbsp;allow<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
>
</P
><P
> Place the following text into a file named ".htaccess",
>&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/
directory. <P
CLASS="LITERALLAYOUT"
CLASS="literallayout"
>&nbsp;&#60;Files&nbsp;localconfig&#62;&nbsp;deny<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;</P
>
</P
><P
> Place the following text into a file named ".htaccess",
>&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/shadow
directory. <P
CLASS="LITERALLAYOUT"
CLASS="literallayout"
>&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
>
</P

92
webtools/bugzilla/docs/html/setperl.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="cmdline.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="SETPERL"
NAME="setperl"
>D.2. The setperl.csh Utility</A
></H1
><P
@ -80,12 +80,12 @@ NAME="SETPERL"
search path on your system, it will not work!
</P
><DIV
CLASS="PROCEDURE"
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
> Download the "setperl.csh" utility to your Bugzilla
>&#13; Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</P
><OL
@ -93,14 +93,14 @@ CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="COMMAND"
CLASS="command"
>cd /your/path/to/bugzilla</B
>
</TT
@ -109,13 +109,13 @@ CLASS="COMMAND"
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash#</TT
> <B
CLASS="COMMAND"
CLASS="command"
>wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
@ -125,13 +125,13 @@ CLASS="COMMAND"
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash#</TT
> <B
CLASS="COMMAND"
CLASS="command"
>chmod
u+x setperl.csh</B
> </TT
@ -142,21 +142,21 @@ CLASS="COMMAND"
></LI
><LI
><P
> Prepare (and fix) Bugzilla file permissions.
>&#13; Prepare (and fix) Bugzilla file permissions.
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="COMMAND"
CLASS="command"
>chmod u+w *</B
>
</TT
@ -165,13 +165,13 @@ CLASS="COMMAND"
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash#</TT
> <B
CLASS="COMMAND"
CLASS="command"
>chmod
u+x duplicates.cgi</B
> </TT
@ -180,14 +180,14 @@ CLASS="COMMAND"
></LI
><LI
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="COMMAND"
CLASS="command"
>chmod a-x bug_status.html</B
>
</TT
@ -198,39 +198,39 @@ CLASS="COMMAND"
></LI
><LI
><P
> Run the script:
>&#13; Run the script:
</P
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash#</TT
>
<B
CLASS="COMMAND"
CLASS="command"
>./setperl.csh /your/path/to/perl</B
>
</TT
>
<DIV
CLASS="EXAMPLE"
CLASS="example"
><A
NAME="AEN2439"
NAME="AEN2448"
></A
><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><P
> <TT
CLASS="COMPUTEROUTPUT"
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="PROMPT"
CLASS="prompt"
>bash#</TT
>
<B
CLASS="COMMAND"
CLASS="command"
>./setperl.csh /usr/bin/perl</B
>
</TT
@ -284,7 +284,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Apache <TT
CLASS="FILENAME"
CLASS="filename"
>mod_rewrite</TT
> magic</TD
><TD

669
webtools/bugzilla/docs/html/stepbystep.html
View File

File diff suppressed because it is too large Load Diff

8
webtools/bugzilla/docs/html/tinderbox.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="The Future of Bugzilla"
HREF="future.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="future.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="TINDERBOX"
NAME="tinderbox"
>5.4. Tinderbox/Tinderbox2</A
></H1
><P

12
webtools/bugzilla/docs/html/translations.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Document Conventions"
HREF="conventions.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,20 +66,20 @@ HREF="conventions.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="TRANSLATIONS"
NAME="translations"
>1.8. Translations</A
></H1
><P
> The Bugzilla Guide needs translators! Please volunteer your
>&#13; The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will
translate this Guide, please notify the members of the
mozilla-webtools mailing list at
<TT
CLASS="EMAIL"
CLASS="email"
>&#60;<A
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A

179
webtools/bugzilla/docs/html/useradmin.html
View File

@ -20,7 +20,7 @@ TITLE="Product, Component, Milestone, and Version
Administration"
HREF="programadmin.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -67,28 +67,28 @@ HREF="programadmin.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="USERADMIN"
NAME="useradmin"
>4.2. User Administration</A
></H1
><P
> User administration is one of the easiest parts of Bugzilla.
>&#13; User administration is one of the easiest parts of Bugzilla.
Keeping it from getting out of hand, however, can become a
challenge.
</P
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="DEFAULTUSER"
NAME="defaultuser"
>4.2.1. Creating the Default User</A
></H2
><P
> When you first run checksetup.pl after installing Bugzilla, it
>&#13; When you first run checksetup.pl after installing Bugzilla, it
will prompt you for the administrative username (email
address) and password for this "super user". If for some
reason you were to delete the "super user" account, re-running
@ -96,11 +96,11 @@ NAME="DEFAULTUSER"
password.
</P
><DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
@ -116,21 +116,21 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> If you wish to add more administrative users, you must use the
>&#13; If you wish to add more administrative users, you must use the
MySQL interface. Run "mysql" from the command line, and use
these commands ("mysql&#62;" denotes the mysql prompt, not
something you should type in):
<B
CLASS="COMMAND"
CLASS="command"
><TT
CLASS="PROMPT"
CLASS="prompt"
>mysql&#62;</TT
> use bugs;</B
>
<B
CLASS="COMMAND"
CLASS="command"
><TT
CLASS="PROMPT"
CLASS="prompt"
>mysql&#62;</TT
> update profiles set
groupset=0x7ffffffffffffff where login_name = "(user's
@ -152,19 +152,19 @@ CLASS="QUOTE"
></DIV
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H2
CLASS="SECTION"
CLASS="section"
><A
NAME="MANAGEUSERS"
NAME="manageusers"
>4.2.2. Managing Other Users</A
></H2
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="LOGIN"
NAME="login"
>4.2.2.1. Logging In</A
></H3
><P
@ -173,23 +173,23 @@ NAME="LOGIN"
TYPE="1"
><LI
><P
> Open the index.html page for your Bugzilla installation
>&#13; Open the index.html page for your Bugzilla installation
in your browser window.
</P
></LI
><LI
><P
> Click the "Query Existing Bug Reports" link.
>&#13; Click the "Query Existing Bug Reports" link.
</P
></LI
><LI
><P
> Click the "Log In" link at the foot of the page.
>&#13; Click the "Log In" link at the foot of the page.
</P
></LI
><LI
><P
> Type your email address, and the password which was
>&#13; Type your email address, and the password which was
emailed to you when you created your Bugzilla account,
into the spaces provided.
</P
@ -199,15 +199,15 @@ TYPE="1"
>Congratulations, you are logged in!</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="CREATENEWUSERS"
NAME="createnewusers"
>4.2.2.2. Creating new users</A
></H3
><P
> Your users can create their own user accounts by clicking
>&#13; Your users can create their own user accounts by clicking
the "New Account" link at the bottom of each page. However,
should you desire to create user accounts ahead of time,
here is how you do it.
@ -218,24 +218,24 @@ NAME="CREATENEWUSERS"
TYPE="1"
><LI
><P
> After logging in, click the "Users" link at the footer
>&#13; After logging in, click the "Users" link at the footer
of the query page.
</P
></LI
><LI
><P
> To see a specific user, type a portion of their login
>&#13; To see a specific user, type a portion of their login
name in the box provided and click "submit". To see all
users, simply click the "submit" button. You must click
"submit" here to be able to add a new user.
</P
><DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="90%"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -250,12 +250,12 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> More functionality is available via the list on the
>&#13; More functionality is available via the list on the
right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive
regular expression (please see the <B
CLASS="COMMAND"
CLASS="command"
>man
regexp</B
> manual page for details on regular
@ -272,22 +272,22 @@ CLASS="COMMAND"
></LI
><LI
><P
> Click the "Add New User" link at the bottom of the user
>&#13; Click the "Add New User" link at the bottom of the user
list
</P
></LI
><LI
><P
> Fill out the form presented. This page is
>&#13; Fill out the form presented. This page is
self-explanatory. When done, click "submit".
</P
><DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -302,7 +302,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Adding a user this way will <EM
>&#13; Adding a user this way will <EM
>not</EM
>
send an email informing them of their username and
@ -326,15 +326,15 @@ CLASS="QUOTE"
></OL
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="DISABLEUSERS"
NAME="disableusers"
>4.2.2.3. Disabling Users</A
></H3
><P
> I bet you noticed that big "Disabled Text" entry box
>&#13; I bet you noticed that big "Disabled Text" entry box
available from the "Add New User" screen, when you edit an
account? By entering any text in this box and selecting
"submit", you have prevented the user from using Bugzilla
@ -342,11 +342,11 @@ NAME="DISABLEUSERS"
text box, will be presented to the user the next time she
attempts to use the system.
<DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
@ -362,7 +362,7 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Don't disable your own administrative account, or you
>&#13; Don't disable your own administrative account, or you
will hate life!
</P
><P
@ -382,15 +382,15 @@ CLASS="QUOTE"
</P
></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H3
CLASS="SECTION"
CLASS="section"
><A
NAME="MODIFYUSERS"
NAME="modifyusers"
>4.2.2.4. Modifying Users</A
></H3
><P
> Here I will attempt to describe the function of each option
>&#13; Here I will attempt to describe the function of each option
on the Edit User screen.
</P
><P
@ -398,19 +398,19 @@ NAME="MODIFYUSERS"
><UL
><LI
><P
> <EM
>&#13; <EM
>Login Name</EM
>: This is generally the
user's email address. However, if you have edited your
system parameters, this may just be the user's login
name or some other identifier.
<DIV
CLASS="TIP"
CLASS="tip"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="90%"
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -425,7 +425,7 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> For compatability reasons, you should probably stick
>&#13; For compatability reasons, you should probably stick
with email addresses as user login names. It will
make your life easier.
</P
@ -438,14 +438,14 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Real Name</EM
>: Duh!
</P
></LI
><LI
><P
> <EM
>&#13; <EM
>Password</EM
>: You can change the user
password here. It is normal to only see asterisks.
@ -453,7 +453,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Email Notification</EM
>: You may choose
from one of three options:
@ -463,7 +463,7 @@ VALIGN="TOP"
TYPE="1"
><LI
><P
> All qualifying bugs except those which I change:
>&#13; All qualifying bugs except those which I change:
The user will be notified of any change to any bug
for which she is the reporter, assignee, QA
Contact, CC recipient, or "watcher".
@ -471,18 +471,18 @@ TYPE="1"
></LI
><LI
><P
> Only those bugs which I am listed on the CC line:
>&#13; Only those bugs which I am listed on the CC line:
The user will not be notified of changes to bugs
where she is the assignee, reporter, or QA
Contact, but will receive them if she is on the CC
list.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -497,7 +497,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> She will still receive whining cron emails if
>&#13; She will still receive whining cron emails if
you set up the "whinemail" feature.
</P
></TD
@ -509,7 +509,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>All Qualifying Bugs</EM
>: This
user is a glutton for punishment. If her name is
@ -519,9 +519,10 @@ VALIGN="TOP"
</P
></LI
></OL
></P
>
</P
><P
> <EM
>&#13; <EM
>Disable Text</EM
>: If you type anything
in this box, including just a space, the user account is
@ -529,12 +530,12 @@ VALIGN="TOP"
interface, and what you type in this box is presented as
the reason.
<DIV
CLASS="WARNING"
CLASS="warning"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="90%"
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -556,12 +557,12 @@ VALIGN="TOP"
></DIV
>
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -576,7 +577,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> As of this writing, the user can still submit bugs
>&#13; As of this writing, the user can still submit bugs
via the e-mail gateway, if you set it up, despite
the disabled text field. The e-mail gateway should
<EM
@ -593,7 +594,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>CanConfirm</EM
>: This field is only used
if you have enabled "unconfirmed" status in your
@ -606,7 +607,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Creategroups</EM
>: This option will
allow a user to create and destroy groups in Bugzilla.
@ -617,18 +618,18 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Editbugs</EM
>: Unless a user has this
bit set, they can only edit those bugs for which they
are the assignee or the reporter.
<DIV
CLASS="NOTE"
CLASS="note"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
@ -643,7 +644,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Leaving this option unchecked does not prevent users
>&#13; Leaving this option unchecked does not prevent users
from adding comments to a bug! They simply cannot
change a bug priority, severity, etc. unless they
are the assignee or reporter.
@ -657,7 +658,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Editcomponents</EM
>: This flag allows a
user to create new products and components, as well as
@ -673,7 +674,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Editkeywords</EM
>: If you use Bugzilla's
keyword functionality, enabling this feature allows a
@ -690,7 +691,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>Editusers</EM
>: This flag allows a user
do what you're doing right now: edit other users. This
@ -701,7 +702,7 @@ VALIGN="TOP"
></LI
><LI
><P
> <EM
>&#13; <EM
>PRODUCT</EM
>: PRODUCT bugs access. This
allows an administrator, with product-level granularity,

30
webtools/bugzilla/docs/html/using.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="What is Bugzilla?"
HREF="whatis.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="whatis.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="USING"
NAME="using"
>Chapter 2. Using Bugzilla</A
></H1
><TABLE
@ -118,29 +118,29 @@ HREF="how.html"
><DL
><DT
>2.3.1. <A
HREF="how.html#MYACCOUNT"
HREF="how.html#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>2.3.2. <A
HREF="how.html#QUERY"
HREF="how.html#query"
>The Bugzilla Query Page</A
></DT
><DT
>2.3.3. <A
HREF="how.html#BUGREPORTS"
HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>2.3.3.1. <A
HREF="how.html#BUG_WRITING"
HREF="how.html#bug-writing"
>Writing a Great Bug Report</A
></DT
><DT
>2.3.3.2. <A
HREF="how.html#BUG_MANAGE"
HREF="how.html#bug-manage"
>Managing your Bug Reports</A
></DT
></DL
@ -156,41 +156,41 @@ HREF="init4me.html"
><DL
><DT
>2.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS"
HREF="init4me.html#accountsettings"
>Account Settings</A
></DT
><DT
>2.4.2. <A
HREF="init4me.html#EMAILSETTINGS"
HREF="init4me.html#emailsettings"
>Email Settings</A
></DT
><DD
><DL
><DT
>2.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
HREF="init4me.html#notification"
>Email Notification</A
></DT
><DT
>2.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
HREF="init4me.html#newemailtech"
>New Email Technology</A
></DT
><DT
>2.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
HREF="init4me.html#watchsettings"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>2.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
HREF="init4me.html#footersettings"
>Page Footer</A
></DT
><DT
>2.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS"
HREF="init4me.html#permissionsettings"
>Permissions</A
></DT
></DL

10
webtools/bugzilla/docs/html/usingbz-conc.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Installation"
HREF="installation.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,15 +66,15 @@ HREF="installation.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="USINGBZ-CONC"
NAME="usingbz-conc"
>2.5. Using Bugzilla-Conclusion</A
></H1
><P
> Thank you for reading through this portion of the Bugzilla
>&#13; Thank you for reading through this portion of the Bugzilla
Guide. I anticipate it may not yet meet the needs of all
readers. If you have additional comments or corrections to
make, please submit your contributions to the <A

142
webtools/bugzilla/docs/html/variant-fenris.html Normal file
View File

@ -0,0 +1,142 @@
<HTML
><HEAD
><TITLE
>Loki Bugzilla (Fenris)</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"><LINK
REL="NEXT"
TITLE="Issuezilla"
HREF="variant-issuezilla.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-issuezilla.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-fenris"
>7.2. Loki Bugzilla (Fenris)</A
></H1
><P
>Fenris can be found at <A
HREF="http://fenris.lokigames.com/"
TARGET="_top"
>http://fenris.lokigames.com</A
>. It is a fork from Bugzilla.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-issuezilla.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Red Hat Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Issuezilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

153
webtools/bugzilla/docs/html/variant-issuezilla.html Normal file
View File

@ -0,0 +1,153 @@
<HTML
><HEAD
><TITLE
>Issuezilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Loki Bugzilla (Fenris)"
HREF="variant-fenris.html"><LINK
REL="NEXT"
TITLE="Scarab"
HREF="variant-scarab.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant-fenris.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-scarab.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-issuezilla"
>7.3. Issuezilla</A
></H1
><P
>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <A
HREF="variant-scarab.html"
>Scarab, a newfangled Java-based issue tracker</A
>, is under heavy development
and looks promising!</P
><P
>URL: <A
HREF="http://issuezilla.tigris.org/servlets/ProjectHome"
TARGET="_top"
>http://issuezilla.tigris.org/servlets/ProjectHome</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-fenris.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-scarab.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Loki Bugzilla (Fenris)</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Scarab</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
webtools/bugzilla/docs/html/variant-perforce.html Normal file
View File

@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Scarab"
HREF="variant-scarab.html"><LINK
REL="NEXT"
TITLE="SourceForge"
HREF="variant-sourceforge.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant-scarab.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-sourceforge.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-perforce"
>7.5. Perforce SCM</A
></H1
><P
>Although Perforce isn't really a bug tracker, it can be used
as such through the <SPAN
CLASS="QUOTE"
>"jobs"</SPAN
> functionality.</P
><P
><A
HREF="http://www.perforce.com/perforce/technotes/note052.html"
TARGET="_top"
>http://www.perforce.com/perforce/technotes/note052.html</A
>http://www.perforce.com/perforce/technotes/note052.html</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-scarab.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-sourceforge.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Scarab</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>SourceForge</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
webtools/bugzilla/docs/html/variant-scarab.html Normal file
View File

@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>Scarab</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Issuezilla"
HREF="variant-issuezilla.html"><LINK
REL="NEXT"
TITLE="Perforce SCM"
HREF="variant-perforce.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant-issuezilla.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant-perforce.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-scarab"
>7.4. Scarab</A
></H1
><P
>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
</P
><P
>URL: <A
HREF="http://scarab.tigris.org/"
TARGET="_top"
>http://scarab.tigris.org</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-issuezilla.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant-perforce.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Issuezilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Perforce SCM</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
webtools/bugzilla/docs/html/variant-sourceforge.html Normal file
View File

@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>SourceForge</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="variant-perforce.html"><LINK
REL="NEXT"
TITLE="The Bugzilla FAQ"
HREF="faq.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant-perforce.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="faq.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-sourceforge"
>7.6. SourceForge</A
></H1
><P
>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</P
><P
>URL: <A
HREF="http://www.sourceforge.net"
TARGET="_top"
>http://www.sourceforge.net</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant-perforce.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="faq.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Perforce SCM</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla FAQ</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

16
webtools/bugzilla/docs/html/variants.html
View File

@ -16,7 +16,7 @@ REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
><BODY
CLASS="CHAPTER"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -63,10 +63,10 @@ HREF="rhbugzilla.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
CLASS="chapter"
><H1
><A
NAME="VARIANTS"
NAME="variants"
>Chapter 7. Bugzilla Variants and Competitors</A
></H1
><DIV
@ -83,27 +83,27 @@ HREF="rhbugzilla.html"
></DT
><DT
>7.2. <A
HREF="variant_fenris.html"
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
HREF="variant_issuezilla.html"
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
HREF="variant_scarab.html"
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
HREF="variant_perforce.html"
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
HREF="variant_sourceforge.html"
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
></DL

36
webtools/bugzilla/docs/html/whatis.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,15 +66,15 @@ HREF="why.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="WHATIS"
NAME="whatis"
>2.1. What is Bugzilla?</A
></H1
><P
> Bugzilla is one example of a class of programs called "Defect
>&#13; Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
@ -89,48 +89,48 @@ project, Mozilla). It is now the de-facto standard defect-tracking
system against which all others are measured.
</P
><P
> Bugzilla has matured immensely, and now boasts many advanced features. These include:
>&#13; Bugzilla has matured immensely, and now boasts many advanced features. These include:
<P
></P
><UL
><LI
><P
> integrated, product-based granular security schema
>&#13; integrated, product-based granular security schema
</P
></LI
><LI
><P
> inter-bug dependencies and dependency graphing
>&#13; inter-bug dependencies and dependency graphing
</P
></LI
><LI
><P
> advanced reporting capabilities
>&#13; advanced reporting capabilities
</P
></LI
><LI
><P
> a robust, stable RDBMS back-end
>&#13; a robust, stable RDBMS back-end
</P
></LI
><LI
><P
> extensive configurability
>&#13; extensive configurability
</P
></LI
><LI
><P
> a very well-understood and well-thought-out natural bug resolution protocol
>&#13; a very well-understood and well-thought-out natural bug resolution protocol
</P
></LI
><LI
><P
> email, XML, console, and HTTP APIs
>&#13; email, XML, console, and HTTP APIs
</P
></LI
><LI
><P
> available integration with automated software
>&#13; available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
@ -138,14 +138,14 @@ system against which all others are measured.
></LI
><LI
><P
> too many more features to list
>&#13; too many more features to list
</P
></LI
></UL
>
</P
><P
> Despite its current robustness and popularity, Bugzilla faces
>&#13; Despite its current robustness and popularity, Bugzilla faces
some near-term challenges, such as reliance on a single
database, a lack of abstraction of the user interface and
program logic, verbose email bug notifications, a powerful but
@ -156,7 +156,7 @@ system against which all others are measured.
some nonstandard libraries.
</P
><P
> Some recent headway has been made on the query front, however.
>&#13; Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see
a <SPAN
CLASS="QUOTE"
@ -167,7 +167,7 @@ CLASS="QUOTE"
available as "queryhelp.cgi".
</P
><P
> Despite these small problems, Bugzilla is very hard to beat. It
>&#13; Despite these small problems, Bugzilla is very hard to beat. It
is under <EM
>very</EM
> active development to address

20
webtools/bugzilla/docs/html/why.html
View File

@ -19,7 +19,7 @@ REL="NEXT"
TITLE="How do I use Bugzilla?"
HREF="how.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -66,11 +66,11 @@ HREF="how.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="WHY"
NAME="why"
>2.2. Why Should We Use Bugzilla?</A
></H1
><TABLE
@ -97,7 +97,7 @@ VALIGN="TOP"
></TR
></TABLE
><P
> For many years, defect-tracking software has remained
>&#13; For many years, defect-tracking software has remained
principally the domain of large software development houses.
Even then, most shops never bothered with bug-tracking software,
and instead simply relied on shared lists and email to monitor
@ -106,7 +106,7 @@ VALIGN="TOP"
dropped or ignored.
</P
><P
> These days, many companies are finding that integrated
>&#13; These days, many companies are finding that integrated
defect-tracking systems reduce downtime, increase productivity,
and raise customer satisfaction with their systems. Along with
full disclosure, an open bug-tracker allows manufacturers to
@ -118,12 +118,12 @@ VALIGN="TOP"
system for accounting for unusual system or software issues.
</P
><P
> But why should <EM
>&#13; But why should <EM
>you</EM
> use Bugzilla?
</P
><P
> Bugzilla is very adaptable to various situations. Known uses
>&#13; Bugzilla is very adaptable to various situations. Known uses
currently include IT support queues, Systems Administration
deployment management, chip design and development problem
tracking (both pre-and-post fabrication), and software and
@ -134,7 +134,7 @@ VALIGN="TOP"
replication problems
</P
><P
> Bugzilla can dramatically increase the productivity and
>&#13; Bugzilla can dramatically increase the productivity and
accountability of individual employees by providing a documented
workflow and positive feedback for good performance. How many
times do you wake up in the morning, remembering that you were
@ -148,7 +148,7 @@ VALIGN="TOP"
led to critical decisions.
</P
><P
> Ultimately, Bugzilla puts the power in your hands to improve
>&#13; Ultimately, Bugzilla puts the power in your hands to improve
your value to your employer or business while providing a usable
framework for your natural attention to detail and knowledge
store to flourish.

453
webtools/bugzilla/docs/html/win32.html
View File

File diff suppressed because it is too large Load Diff

98
webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
View File

@ -41,14 +41,14 @@ Matthew P. Barnson
Bugzilla is an enterprise-class set of software utilities that, when
used together, power issue-tracking for hundreds of organizations
around the world, tracking millions of bugs. While it is easy to use
and quite flexible, it is very difficult for a novice to install and
and quite flexible, it is difficult for a novice to install and
maintain. Although we have provided step-by-step directions, Bugzilla
is not always easy to get working. Please be sure the person
responsible for installing and maintaining this software is a
qualified professional on operating system upon which you install
qualified professional for the operating system upon which you install
Bugzilla.
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. IF YOU
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT. IF YOU
WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN TEXT OR SGML DIFFS
AGAINST THE SOURCE. I CANNOT ACCEPT ADDITIONS TO THE GUIDE WRITTEN IN
HTML!
@ -649,8 +649,8 @@ Chapter 2. Using Bugzilla
tends to run the latest code, so these two utilities should be
available there for your perusal.
At this point, please visit the main Bugzilla site,
bugzilla.mozilla.org, to see a more fleshed-out query page.
At this point, let's visit the query page.
landfill.tequilarista.org/bugzilla-tip/query.cgi
The first thing you need to notice about the Bugzilla Query Page is
that nearly every box you see on your screen has a hyperlink nearby,
@ -1823,6 +1823,23 @@ sr/local/lib);
will need to change the ip address in data/webdot/.htaccess to the ip
address of the webdot server that you are using.
The default .htaccess file may not provide adequate access
restrictions, depending on your web server configuration. Be sure to
check the <Directory> entries for your Bugzilla directory so that the
.htaccess file is allowed to override web server defaults. For
instance, let's assume your installation of Bugzilla is installed to
/usr/local/bugzilla. You should have this <Directory> entry in your
httpd.conf file:
<Directory /usr/local/bugzilla/>
Options +FollowSymLinks +Indexes +Includes +ExecCGI
AllowOverride All
</Directory>
The important part above is "AllowOverride All". Without that,
the .htaccess file created by checksetup.pl will not have sufficient
permissions to protect your Bugzilla installation.
If you are using Internet Information Server or other web server which
does not observe .htaccess conventions, you can disable their creation
by editing localconfig and setting the $create_htaccess variable to 0.
@ -2082,6 +2099,7 @@ log";
Some people have suggested using the Net::SMTP Perl module instead of
NTsendmail or the other options listed here. You can change
processmail.pl to make this work.
my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP ser
ver
$smtp->mail('<your name>@<you smpt server>');# use the sender's adress here
@ -2093,7 +2111,9 @@ $smtp->quit; # Close the SMTP connection
$logstr = "$logstr; mail sent to $tolist $cclist";
}
here is a test mail program for Net::SMTP:
use Net::SMTP;
my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
=> 1, ); # connect to SMTP server
@ -2108,6 +2128,7 @@ recipient's address
$smtp->quit; # Close the SMTP connection
exit;
12.
Note
@ -2125,17 +2146,15 @@ exit;
in order to work. See http://www.cygwin.com/ for details on
obtaining Cygwin.
13. Modify the invocation of all system() calls in all perl scripts in
your Bugzilla directory. For instance, change this line in
your Bugzilla directory. You should specify the full path to perl
for each system() call. For instance, change this line in
processmail:
system ("./processmail.pl",@ARGLIST);
to
system ("perl processmail.pl",@ARGLIST);
system ("./processmail",@ARGLIST);
</programlisting> to
<programlisting>
system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
14. Add binmode() calls so attachments will work (bug 62000).
@ -4520,7 +4539,7 @@ if ($::FORM{sub} eq 'PutFooter') {
}
and then put this line in index.shtml.
<!--#include virtual="api.cgi?sub=PutFooter"-->
<!--#include virtual="api.cgi?sub=PutFooter"-->
Note
@ -5165,24 +5184,21 @@ Appendix B. Software Download Links
CPAN: http://www.cpan.org/
DBI Perl module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
DBI Perl module: http://www.cpan.org/modules/by-module/DBI/
Data::Dumper module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
Data::Dumper module: http://www.cpan.org/modules/by-module/Data/
MySQL related Perl modules:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/
http://www.cpan.org/modules/by-module/Mysql/
TimeDate Perl module collection:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/
http://www.cpan.org/modules/by-module/Date/
GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
Alternately, you should be able to find the latest version of GD at
GD Perl module: http://www.cpan.org/modules/by-module/GD/ Alternately,
you should be able to find the latest version of GD at
http://www.boutell.com/gd/
Chart::Base module:
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
Chart::Base module: http://www.cpan.org/modules/by-module/Chart/
LinuxDoc Software: http://www.linuxdoc.org/ (for documentation
maintenance)
@ -5751,10 +5767,10 @@ RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
</VirtualHost>
2. There are many, many more things you can do with mod_rewrite. As
time goes on, I will include many more in the Guide. For now,
though, please refer to the mod_rewrite documentation at
http://www.apache.org
2. There are many, many more things you can do with
mod_rewrite. As time goes on, I will include many more in the
Guide. For now, though, please refer to the mod_rewrite
documentation at http://www.apache.org
_________________________________________________________________
D.2. The setperl.csh Utility
@ -5899,7 +5915,10 @@ D.5.2. Coding Style for Bugzilla
favorite shell prompt.
What appears below if a brief summary, please refer to the perl style
guide if you don't see your question covered here.
guide if you don't see your question covered here. It is much better
to submit a patch which fails these criteria than no patch at all, but
please try to meet these minimum standards when submitting code to
Bugzilla.
* Whitespace
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
@ -5928,12 +5947,33 @@ else
}
* Cookies
Bugzilla uses cookies to ease the user experience, but no new
patches should require user-side cookies.
* File Names
File names for bugzilla code and support documention should be
legal across multiple platforms. \ / : * ? " < > and | are all
illegal characters for filenames on various platforms. Also, file
names should not have spaces in them as they can cause confusion
in CVS and other mozilla.org utilities.
* Javascript dependencies
While Bugzilla uses Javascript to make the user experience easier,
no patch to Bugzilla should require Javascript.
* Patch Format
All patches submitted for inclusion into Bugzilla should be in the
form of a "unified diff". This comes from using "diff -u" instead
of simply "diff" when creating your patch. This will result in
quicker acceptance of the patch.
* Schema Changes
If you make schema changes, you should modify sanitycheck.cgi to
support the new schema. All referential columns should be checked.
* Taint Mode
All new cgis must run in Taint mode (Perl taint and DBI taint),
and existing cgi's which run in taint mode must not have taint
mode turned off.
* Templatization
Patches to Bugzilla need to support templates so they do not force
user interface choices on Bugzilla administrators.
* Variable Names
If a variable is scoped globally ($::variable) its name should be
descriptive of what it contains. Local variables can be named a