mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Merging new docs from 2.16 branch.

This commit is contained in:
gerv%gerv.net 2002-07-27 22:01:14 +00:00
Родитель 1516db315c
Коммит 5c46bde5fe
104 изменённых файлов: 23573 добавлений и 37683 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

17524
webtools/bugzilla/docs/html/Bugzilla-Guide.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

28
webtools/bugzilla/docs/html/about.html
Просмотреть файл

@ -13,8 +13,8 @@ REL="PREVIOUS"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Purpose and Scope of this Guide"
HREF="aboutthisguide.html"></HEAD
TITLE="Copyright Information"
HREF="copyright.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="aboutthisguide.html"
HREF="copyright.html"
ACCESSKEY="N"
>Next</A
></TD
@ -79,36 +79,26 @@ CLASS="TOC"
></DT
><DT
>1.1. <A
HREF="aboutthisguide.html"
>Purpose and Scope of this Guide</A
></DT
><DT
>1.2. <A
HREF="copyright.html"
>Copyright Information</A
></DT
><DT
>1.3. <A
>1.2. <A
HREF="disclaimer.html"
>Disclaimer</A
></DT
><DT
>1.4. <A
>1.3. <A
HREF="newversions.html"
>New Versions</A
></DT
><DT
>1.5. <A
>1.4. <A
HREF="credits.html"
>Credits</A
></DT
><DT
>1.6. <A
HREF="translations.html"
>Translations</A
></DT
><DT
>1.7. <A
>1.5. <A
HREF="conventions.html"
>Document Conventions</A
></DT
@ -149,7 +139,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="aboutthisguide.html"
HREF="copyright.html"
ACCESSKEY="N"
>Next</A
></TD
@ -169,7 +159,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Purpose and Scope of this Guide</TD
>Copyright Information</TD
></TR
></TABLE
></DIV

184
webtools/bugzilla/docs/html/aboutthisguide.html
Просмотреть файл

@ -1,184 +0,0 @@
<HTML
><HEAD
><TITLE
>Purpose and Scope of this Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="NEXT"
TITLE="Copyright Information"
HREF="copyright.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="about.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. About This Guide</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="copyright.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="aboutthisguide">1.1. Purpose and Scope of this Guide</H1
><P
>&#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
>&#13; This release of the Bugzilla Guide is the
<EM
>2.16</EM
> release. It is so named that it
may match the current version of Bugzilla. The numbering
tradition stems from that used for many free software projects,
in which <EM
>even-numbered</EM
> point releases (1.2,
1.14, etc.) are considered "stable releases", intended for
public consumption; on the other hand,
<EM
>odd-numbered</EM
> point releases (1.3, 2.09,
etc.) are considered unstable <EM
>development</EM
>
releases intended for advanced users, systems administrators,
developers, and those who enjoy a lot of pain.
</P
><P
>&#13; Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<A
HREF="http://www.bugzilla.org/"
TARGET="_top"
>http://www.bugzilla.org/</A
>. Intermediate releases will have
a minor revision number following a period. The current version
of Bugzilla, as of this writing (April 2nd, 2002) is 2.16; if
something were seriously wrong with that edition of the Guide,
subsequent releases would receive an additional dotted-decimal
digit to indicate the update (2.16.1, 2.16.2, etc.).
Got it? Good.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="about.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="copyright.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>About This Guide</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="about.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Copyright Information</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

153
webtools/bugzilla/docs/html/administration.html
Просмотреть файл

@ -10,11 +10,11 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Win32 Installation Notes"
HREF="win32.html"><LINK
TITLE="Troubleshooting"
HREF="troubleshooting.html"><LINK
REL="NEXT"
TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"></HEAD
TITLE="Bugzilla Configuration"
HREF="parameters.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="win32.html"
HREF="troubleshooting.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="postinstall-check.html"
HREF="parameters.html"
ACCESSKEY="N"
>Next</A
></TD
@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="administration">Chapter 4. Administering Bugzilla</H1
NAME="administration">Chapter 5. Administering Bugzilla</H1
><DIV
CLASS="TOC"
><DL
@ -78,97 +78,138 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>4.1. <A
HREF="postinstall-check.html"
>Post-Installation Checklist</A
>5.1. <A
HREF="parameters.html"
>Bugzilla Configuration</A
></DT
><DT
>4.2. <A
>5.2. <A
HREF="useradmin.html"
>User Administration</A
></DT
><DD
><DL
><DT
>4.2.1. <A
>5.2.1. <A
HREF="useradmin.html#defaultuser"
>Creating the Default User</A
></DT
><DT
>4.2.2. <A
>5.2.2. <A
HREF="useradmin.html#manageusers"
>Managing Other Users</A
></DT
></DL
></DD
><DT
>4.3. <A
>5.3. <A
HREF="programadmin.html"
>Product, Component, Milestone, and Version
Administration</A
>Product, Component, Milestone, and Version Administration</A
></DT
><DD
><DL
><DT
>4.3.1. <A
>5.3.1. <A
HREF="programadmin.html#products"
>Products</A
></DT
><DT
>4.3.2. <A
>5.3.2. <A
HREF="programadmin.html#components"
>Components</A
></DT
><DT
>4.3.3. <A
>5.3.3. <A
HREF="programadmin.html#versions"
>Versions</A
></DT
><DT
>4.3.4. <A
>5.3.4. <A
HREF="programadmin.html#milestones"
>Milestones</A
></DT
><DT
>4.3.5. <A
HREF="programadmin.html#voting"
>Voting</A
></DT
><DT
>4.3.6. <A
HREF="programadmin.html#groups"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
>4.4. <A
>5.4. <A
HREF="voting.html"
>Voting</A
></DT
><DT
>5.5. <A
HREF="groups.html"
>Groups and Group Security</A
></DT
><DT
>5.6. <A
HREF="security.html"
>Bugzilla Security</A
></DT
><DT
>5.7. <A
HREF="cust-templates.html"
>Template Customisation</A
></DT
><DD
><DL
><DT
>5.7.1. <A
HREF="cust-templates.html#AEN1539"
>What to Edit</A
></DT
><DT
>5.7.2. <A
HREF="cust-templates.html#AEN1558"
>How To Edit Templates</A
></DT
><DT
>5.7.3. <A
HREF="cust-templates.html#AEN1568"
>Template Formats</A
></DT
><DT
>5.7.4. <A
HREF="cust-templates.html#AEN1581"
>Particular Templates</A
></DT
></DL
></DD
><DT
>5.8. <A
HREF="upgrading.html"
>Upgrading to New Releases</A
></DT
><DT
>5.9. <A
HREF="integration.html"
>Integrating Bugzilla with Third-Party Tools</A
></DT
><DD
><DL
><DT
>5.9.1. <A
HREF="integration.html#bonsai"
>Bonsai</A
></DT
><DT
>5.9.2. <A
HREF="integration.html#cvs"
>CVS</A
></DT
><DT
>5.9.3. <A
HREF="integration.html#scm"
>Perforce SCM</A
></DT
><DT
>5.9.4. <A
HREF="integration.html#tinderbox"
>Tinderbox/Tinderbox2</A
></DT
></DL
></DD
></DL
></DIV
><FONT
COLOR="RED"
>&#13; Or, I just got this cool thing installed. Now what the heck do I
do with it?
</FONT
><P
>&#13; So you followed <SPAN
CLASS="QUOTE"
>"<A
HREF="installation.html"
>Bugzilla Installation</A
>"</SPAN
> to the
letter, and logged into Bugzilla for the very first time with your
super-duper god account. You sit, contentedly staring at the
Bugzilla Query Screen, the worst of the whole mad business of
installing this terrific program behind you. It seems, though, you
have nothing yet to query! Your first act of business should be to
setup the operating parameters for Bugzilla so you can get busy
getting data into your bug tracker.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -186,7 +227,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="win32.html"
HREF="troubleshooting.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -204,7 +245,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="postinstall-check.html"
HREF="parameters.html"
ACCESSKEY="N"
>Next</A
></TD
@ -214,7 +255,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Win32 Installation Notes</TD
>Troubleshooting</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -224,7 +265,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Post-Installation Checklist</TD
>Bugzilla Configuration</TD
></TR
></TABLE
></DIV

160
webtools/bugzilla/docs/html/bonsai.html
Просмотреть файл

@ -1,160 +0,0 @@
<HTML
><HEAD
><TITLE
>Bonsai</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"><LINK
REL="PREVIOUS"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"><LINK
REL="NEXT"
TITLE="CVS"
HREF="cvs.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="integration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="cvs.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="bonsai">5.1. Bonsai</H1
><P
>Bonsai is a web-based tool for managing <A
HREF="cvs.html"
>CVS, the Concurrent Versioning System</A
>
. Using Bonsai, administrators can control open/closed status
of trees, query a fast relational database back-end for change,
branch, and comment information, and view changes made since the
last time the tree was closed. These kinds of changes cause the
engineer responsible to be <SPAN
CLASS="QUOTE"
>"on the hook"</SPAN
> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <A
HREF="tinderbox.html"
>Tinderbox, the Mozilla automated build management system</A
> and Bugzilla </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="integration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="cvs.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Integrating Bugzilla with Third-Party Tools</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="integration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>CVS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

149
webtools/bugzilla/docs/html/bsdinstall.html
Просмотреть файл

@ -1,149 +0,0 @@
<HTML
><HEAD
><TITLE
>BSD Installation Notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Mac OS X Installation Notes"
HREF="osx.html"><LINK
REL="NEXT"
TITLE="Installation General Notes"
HREF="geninstall.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="osx.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="geninstall.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="bsdinstall">3.4. BSD Installation Notes</H1
><P
>&#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
>.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="osx.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="geninstall.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Mac OS X Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Installation General Notes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

492
webtools/bugzilla/docs/html/bzhacking.html
Просмотреть файл

@ -1,492 +0,0 @@
<HTML
><HEAD
><TITLE
>Hacking Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="The Quicksearch Utility"
HREF="quicksearch.html"><LINK
REL="NEXT"
TITLE="GNU Free Documentation License"
HREF="gfdl.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="quicksearch.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="bzhacking">D.5. Hacking Bugzilla</H1
><P
>&#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"
><H2
CLASS="section"
><A
NAME="AEN2436">D.5.1. Things that have caused problems and should be avoided</H2
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Usage of variables in Regular Expressions
</P
><P
>&#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
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;grep ($_ eq $value, @array);
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13; -- NOT THIS --
</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;grep (/$value/, @array);
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; If you need to use a non-expression variable inside of an expression, be
sure to quote it properly (using <TT
CLASS="function"
>\Q..\E</TT
>).
</P
></TD
></TR
></TABLE
></DIV
></LI
></OL
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN2450">D.5.2. Coding Style for Bugzilla</H2
><P
>&#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
>&#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"
>man perlstyle</B
> at
your favorite shell prompt.
</P
><P
>&#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
>&#13; Whitespace
</P
><P
>&#13; Bugzilla's preferred indentation is 4 spaces (no tabs, please).
</P
></LI
><LI
><P
>&#13; Curly braces.
</P
><P
>&#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
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;if ($var) {
print "The variable is true";
}
else {
print "Try again";
}
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13; -- NOT THIS --
</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;if ($var)
{
print "The variable is true";
}
else
{
print "Try again";
}
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>&#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
>&#13; File names for bugzilla code and support documention should be legal across
multiple platforms. <TT
CLASS="computeroutput"
>\ / : * ? " &#60; &#62;</TT
>
and <TT
CLASS="computeroutput"
>|</TT
> 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.
</P
></LI
><LI
><P
>&#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
>&#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"
>$ret</TT
> could be used as a staging variable for a
routine's return value as the line <TT
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"
>my $ret = "";</TT
>.
</P
></LI
><LI
><P
>&#13; Cross Database Compatability
</P
><P
>&#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"
>encrypt()</TT
>.
</P
></LI
><LI
><P
>&#13; Cross Platform Compatability
</P
><P
>&#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
that break Bugzilla's ability to run on multiple operating systems.
</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="quicksearch.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Quicksearch Utility</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="patches.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>GNU Free Documentation License</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

209
webtools/bugzilla/docs/html/cmdline.html
Просмотреть файл

@ -13,11 +13,14 @@ REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="The setperl.csh Utility"
HREF="setperl.html"><LINK
TITLE="Apache
mod_rewrite
magic"
HREF="rewrite.html"><LINK
REL="NEXT"
TITLE="The Quicksearch Utility"
HREF="quicksearch.html"></HEAD
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -45,7 +48,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="setperl.html"
HREF="rewrite.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -53,13 +56,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="quicksearch.html"
HREF="variants.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,134 +76,80 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="cmdline">D.3. Command-line Bugzilla Queries</H1
NAME="cmdline">C.2. Command-line Bugzilla Queries</H1
><P
>&#13; Users can query Bugzilla from the command line using this suite
of utilities.
</P
>There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
<TT
CLASS="filename"
>contrib/cmdline</TT
>
directory. However, they
have not yet been updated to work with 2.16 (post-templatisation.).
There are three files - <TT
CLASS="filename"
>query.conf</TT
>,
<TT
CLASS="filename"
>buglist</TT
> and <TT
CLASS="filename"
>bugs</TT
>.</P
><P
>&#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
><TT
CLASS="filename"
>query.conf</TT
>
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
>&#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
character of an option is not "-", it is treated as if it were
prefixed with "--default=".
</P
><TT
CLASS="filename"
>buglist</TT
>
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 character of an option is not "-", it is
treated as if it were prefixed with "--default=".</P
><P
>&#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
>The column list 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, grep for COLUMNLIST
in your cookies file to see your current COLUMNLIST setting.</P
><P
><TT
CLASS="filename"
>bugs</TT
> is a simple shell script which calls
<TT
CLASS="filename"
>buglist</TT
> 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"
>grep COLUMLIST ~/.netscape/cookies</B
> to see
your current COLUMNLIST setting.
</P
><P
>&#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"
>sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</B
>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</B
>
</P
><P
>&#13; Akkana says she has good results piping buglist output through
<B
>Akkana Peck says she has good results piping
<TT
CLASS="filename"
>buglist</TT
> output through
<B
CLASS="command"
>w3m -T text/html -dump</B
>
</P
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
>&#13; Download three files:
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash$</TT
> <B
CLASS="command"
>wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</B
> </TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash$</TT
> <B
CLASS="command"
>wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</B
> </TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</B
> </TT
>
</P
></LI
></OL
></LI
><LI
><P
>&#13; Make your utilities executable:
<TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash$</TT
>
<B
CLASS="command"
>chmod u+x buglist bugs</B
>
</TT
>
</P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
@ -218,7 +167,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="setperl.html"
HREF="rewrite.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -236,7 +185,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="quicksearch.html"
HREF="variants.html"
ACCESSKEY="N"
>Next</A
></TD
@ -246,7 +195,13 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The setperl.csh Utility</TD
>Apache
<TT
CLASS="filename"
>mod_rewrite</TT
>
magic</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -260,7 +215,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Quicksearch Utility</TD
>Bugzilla Variants and Competitors</TD
></TR
></TABLE
></DIV

150
webtools/bugzilla/docs/html/contributors.html
Просмотреть файл

@ -1,150 +0,0 @@
<HTML
><HEAD
><TITLE
>Contributors</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="Credits"
HREF="credits.html"><LINK
REL="NEXT"
TITLE="Feedback"
HREF="feedback.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. About This Guide</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="feedback.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="contributors">1.6. Contributors</H1
><P
>&#13; Thanks go to these people for significant contributions to this
documentation (in no particular order):
</P
><P
>&#13; Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron
Teitelbaum, Jacob Steenhagen, Joe Robins
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="feedback.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Credits</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="about.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Feedback</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

108
webtools/bugzilla/docs/html/conventions.html
Просмотреть файл

@ -13,11 +13,11 @@ REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="Translations"
HREF="translations.html"><LINK
TITLE="Credits"
HREF="credits.html"><LINK
REL="NEXT"
TITLE="Using Bugzilla"
HREF="using.html"></HEAD
TITLE="Introduction"
HREF="introduction.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="translations.html"
HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="using.html"
HREF="introduction.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,14 +73,13 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="conventions">1.7. Document Conventions</H1
NAME="conventions">1.5. Document Conventions</H1
><P
>&#13; This document uses the following conventions
</P
>This document uses the following conventions:</P
><DIV
CLASS="informaltable"
><A
NAME="AEN91"><P
NAME="AEN178"><P
></P
><TABLE
BORDER="0"
@ -106,7 +105,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><DIV
>&#13; <DIV
CLASS="caution"
><P
></P
@ -132,7 +131,8 @@ VALIGN="TOP"
></TR
></TABLE
></DIV
></TD
>
</TD
></TR
><TR
><TD
@ -142,7 +142,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><DIV
>&#13; <DIV
CLASS="tip"
><P
></P
@ -163,12 +163,13 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Warm jar lids under the hot tap to loosen them.</P
>Would you like a breath mint?</P
></TD
></TR
></TABLE
></DIV
></TD
>
</TD
></TR
><TR
><TD
@ -178,7 +179,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><DIV
>&#13; <DIV
CLASS="note"
><P
></P
@ -204,7 +205,8 @@ VALIGN="TOP"
></TR
></TABLE
></DIV
></TD
>
</TD
></TR
><TR
><TD
@ -214,7 +216,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><DIV
>&#13; <DIV
CLASS="warning"
><P
></P
@ -240,7 +242,8 @@ VALIGN="TOP"
></TR
></TABLE
></DIV
></TD
>
</TD
></TR
><TR
><TD
@ -250,10 +253,11 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><TT
>&#13; <TT
CLASS="filename"
>file.extension</TT
></TD
>filename</TT
>
</TD
></TR
><TR
><TD
@ -263,10 +267,11 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><TT
>&#13; <TT
CLASS="filename"
>directory</TT
></TD
>
</TD
></TR
><TR
><TD
@ -276,10 +281,11 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><B
>&#13; <B
CLASS="command"
>command</B
></TD
>
</TD
></TR
><TR
><TD
@ -289,19 +295,22 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><SPAN
>&#13; <SPAN
CLASS="application"
>application</SPAN
></TD
>
</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><I
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
> of users command under bash shell</TD
>
of users command under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
@ -311,10 +320,12 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><I
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
> of root users command under bash shell</TD
>
of root users command under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
@ -324,10 +335,12 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><I
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
> of user command under tcsh shell</TD
>
of user command under tcsh shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
@ -341,10 +354,11 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><TT
>&#13; <TT
CLASS="envar"
>VARIABLE</TT
></TD
>
</TD
></TR
><TR
><TD
@ -354,9 +368,10 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><EM
>&#13; <EM
>word</EM
></TD
>
</TD
></TR
><TR
><TD
@ -366,7 +381,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
><TABLE
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
@ -379,7 +394,9 @@ CLASS="programlisting"
><TT
CLASS="sgmltag"
>&#60;para&#62;</TT
>Beginning and end of paragraph<TT
>
Beginning and end of paragraph
<TT
CLASS="sgmltag"
>&#60;/para&#62;</TT
></PRE
@ -387,7 +404,8 @@ CLASS="sgmltag"
></TD
></TR
></TABLE
></TD
>
</TD
></TR
></TBODY
></TABLE
@ -411,7 +429,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="translations.html"
HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -429,7 +447,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="using.html"
HREF="introduction.html"
ACCESSKEY="N"
>Next</A
></TD
@ -439,7 +457,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Translations</TD
>Credits</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -453,7 +471,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using Bugzilla</TD
>Introduction</TD
></TR
></TABLE
></DIV

488
webtools/bugzilla/docs/html/copyright.html
Просмотреть файл

@ -13,8 +13,8 @@ REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="Purpose and Scope of this Guide"
HREF="aboutthisguide.html"><LINK
TITLE="About This Guide"
HREF="about.html"><LINK
REL="NEXT"
TITLE="Disclaimer"
HREF="disclaimer.html"></HEAD
@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="aboutthisguide.html"
HREF="about.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -73,9 +73,9 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="copyright">1.2. Copyright Information</H1
NAME="copyright">1.1. Copyright Information</H1
><A
NAME="AEN39"><TABLE
NAME="AEN31"><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
@ -95,8 +95,7 @@ VALIGN="TOP"
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
the license is included in the section entitled "GNU Free
Documentation License".
the license is included below.
</P
></TD
><TD
@ -123,6 +122,477 @@ WIDTH="10%"
copyright, or publishing this document in non-electronic form,
please contact The Bugzilla Team.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="gfdl">1.1.1. GNU Free Documentation License</H2
><P
>Version 1.1, March 2000</P
><A
NAME="AEN38"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and
distribute verbatim copies of this license document, but changing it is
not allowed.</P
></BLOCKQUOTE
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gfdl-0">0. PREAMBLE</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-1">1. APPLICABILITY AND DEFINITIONS</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-2">2. VERBATIM COPYING</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-3">3. COPYING IN QUANTITY</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-4">4. MODIFICATIONS</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-5">5. COMBINING DOCUMENTS</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-6">6. COLLECTIONS OF DOCUMENTS</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-7">7. AGGREGATION WITH INDEPENDENT WORKS</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-8">8. TRANSLATION</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-9">9. TERMINATION</H3
><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="section"
><H3
CLASS="section"
><A
NAME="gfdl-10">10. FUTURE REVISIONS OF THIS LICENSE</H3
><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"
>&#13; 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="section"
><H3
CLASS="section"
><A
NAME="gfdl-howto">How to use this License for your documents</H3
><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="AEN128"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>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
></DIV
><DIV
CLASS="NAVFOOTER"
@ -140,7 +610,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="aboutthisguide.html"
HREF="about.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -168,7 +638,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Purpose and Scope of this Guide</TD
>About This Guide</TD
><TD
WIDTH="34%"
ALIGN="center"

34
webtools/bugzilla/docs/html/credits.html
Просмотреть файл

@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="New Versions"
HREF="newversions.html"><LINK
REL="NEXT"
TITLE="Translations"
HREF="translations.html"></HEAD
TITLE="Document Conventions"
HREF="conventions.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="translations.html"
HREF="conventions.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,10 +73,10 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="credits">1.5. Credits</H1
NAME="credits">1.4. Credits</H1
><P
>&#13; The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts,
creation of this Guide, through their writing, dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</P
@ -86,7 +86,8 @@ HREF="mailto://mbarnson@sisna.com"
TARGET="_top"
>Matthew P. Barnson</A
>
for pulling together the Bugzilla Guide and shepherding it to 2.14.
for the Herculaean task of pulling together the Bugzilla Guide and
shepherding it to 2.14.
</P
><P
>&#13; <A
@ -101,18 +102,18 @@ TARGET="_top"
>&#13; <A
HREF="mailto://tara@tequilarista.org"
TARGET="_top"
>Tara
Hernandez</A
> for keeping Bugzilla development going
strong after Terry left Mozilla.org
>Tara Hernandez</A
>
for keeping Bugzilla development going
strong after Terry left mozilla.org
</P
><P
>&#13; <A
HREF="mailto://dkl@redhat.com"
TARGET="_top"
>Dave Lawrence</A
> for
providing insight into the key differences between Red Hat's
>
for providing insight into the key differences between Red Hat's
customized Bugzilla, and being largely responsible for the "Red
Hat Bugzilla" appendix
</P
@ -126,7 +127,8 @@ TARGET="_top"
questions and arguments on irc.mozilla.org in #mozwebtools
</P
><P
>&#13; 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
@ -138,7 +140,7 @@ TARGET="_top"
</P
><P
>&#13; Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
</P
></DIV
><DIV
@ -175,7 +177,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="translations.html"
HREF="conventions.html"
ACCESSKEY="N"
>Next</A
></TD
@ -199,7 +201,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Translations</TD
>Document Conventions</TD
></TR
></TABLE
></DIV

585
webtools/bugzilla/docs/html/cust-templates.html Normal file
Просмотреть файл

@ -0,0 +1,585 @@
<HTML
><HEAD
><TITLE
>Template Customisation</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Security"
HREF="security.html"><LINK
REL="NEXT"
TITLE="Upgrading to New Releases"
HREF="upgrading.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="security.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="upgrading.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="cust-templates">5.7. Template Customisation</H1
><P
>&#13; One of the large changes for 2.16 was the templatisation of the
entire user-facing UI, using the
<A
HREF="http://www.template-toolkit.org"
TARGET="_top"
>Template Toolkit</A
>.
Administrators can now configure the look and feel of Bugzilla without
having to edit Perl files or face the nightmare of massive merge
conflicts when they upgrade to a newer version in the future.
</P
><P
>&#13; Templatisation also makes localised versions of Bugzilla possible,
for the first time. In the future, a Bugzilla installation may
have templates installed for multiple localisations, and select
which ones to use based on the user's browser language setting.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1539">5.7.1. What to Edit</H2
><P
>&#13; There are two different ways of editing of Bugzilla's templates,
and which you use depends mainly on how you upgrade Bugzilla. The
template directory structure is that there's a top level directory,
<TT
CLASS="filename"
>template</TT
>, which contains a directory for
each installed localisation. The default English templates are
therefore in <TT
CLASS="filename"
>en</TT
>. Underneath that, there
is the <TT
CLASS="filename"
>default</TT
> directory and optionally the
<TT
CLASS="filename"
>custom</TT
> directory. The <TT
CLASS="filename"
>default</TT
>
directory contains all the templates shipped with Bugzilla, whereas
the <TT
CLASS="filename"
>custom</TT
> directory does not exist at first and
must be created if you want to use it.
</P
><P
>&#13; The first method of making customisations is to directly edit the
templates in <TT
CLASS="filename"
>template/en/default</TT
>. This is
probably the best method for small changes if you are going to use
the CVS method of upgrading, because if you then execute a
<B
CLASS="command"
>cvs update</B
>, any template fixes will get
automagically merged into your modified versions.
</P
><P
>&#13; If you use this method, your installation will break if CVS conflicts
occur.
</P
><P
>&#13; The other method is to copy the templates into a mirrored directory
structure under <TT
CLASS="filename"
>template/en/custom</TT
>. The templates
in this directory automatically override those in default.
This is the technique you
need to use if you use the overwriting method of upgrade, because
otherwise your changes will be lost. This method is also better if
you are using the CVS method of upgrading and are going to make major
changes, because it is guaranteed that the contents of this directory
will not be touched during an upgrade, and you can then decide whether
to continue using your own templates, or make the effort to merge your
changes into the new versions by hand.
</P
><P
>&#13; If you use this method, your installation may break if incompatible
changes are made to the template interface. If such changes are made
they will be documented in the release notes, provided you are using a
stable release of Bugzilla. If you use using unstable code, you will
need to deal with this one yourself, although if possible the changes
will be mentioned before they occur in the deprecations section of the
previous stable release's release notes.
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Don't directly edit the compiled templates in
<TT
CLASS="filename"
>data/template/*</TT
> - your
changes will be lost when Template Toolkit recompiles them.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1558">5.7.2. How To Edit Templates</H2
><P
>&#13; The syntax of the Template Toolkit language is beyond the scope of
this guide. It's reasonably easy to pick up by looking at the current
templates; or, you can read the manual, available on the
<A
HREF="http://www.template-toolkit.org"
TARGET="_top"
>Template Toolkit home
page</A
>. However, you should particularly remember (for security
reasons) to always HTML filter things which come from the database or
user input, to prevent cross-site scripting attacks.
</P
><P
>&#13; However, one thing you should take particular care about is the need
to properly HTML filter data that has been passed into the template.
This means that if the data can possibly contain special HTML characters
such as &#60;, and the data was not intended to be HTML, they need to be
converted to entity form, ie &#38;lt;. You use the 'html' filter in the
Template Toolkit to do this. If you fail to do this, you may open up
your installation to cross-site scripting attacks.
</P
><P
>&#13; Also note that Bugzilla adds a few filters of its own, that are not
in standard Template Toolkit. In particular, the 'url_quote' filter
can convert characters that are illegal or have special meaning in URLs,
such as &#38;, to the encoded form, ie %26. This actually encodes most
characters (but not the common ones such as letters and numbers and so
on), including the HTML-special characters, so there's never a need to
HTML filter afterwards.
</P
><P
>&#13; Editing templates is a good way of doing a "poor man's custom fields".
For example, if you don't use the Status Whiteboard, but want to have
a free-form text entry box for "Build Identifier", then you can just
edit the templates to change the field labels. It's still be called
status_whiteboard internally, but your users don't need to know that.
</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; If you are making template changes that you intend on submitting back
for inclusion in standard Bugzilla, you should read the relevant
sections of the
<A
HREF="http://www.bugzilla.org/developerguide.html"
TARGET="_top"
>Developers'
Guide</A
>.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1568">5.7.3. Template Formats</H2
><P
>&#13; Some CGIs have the ability to use more than one template. For
example, buglist.cgi can output bug lists as RDF or two
different forms of HTML (complex and simple). (Try this out
by appending <TT
CLASS="filename"
>&#38;format=simple</TT
> to a buglist.cgi
URL on your Bugzilla installation.) This
mechanism, called template 'formats', is extensible.
</P
><P
>&#13; To see if a CGI supports multiple output formats, grep the
CGI for "ValidateOutputFormat". If it's not present, adding
multiple format support isn't too hard - see how it's done in
other CGIs.
</P
><P
>&#13; To make a new format template for a CGI which supports this,
open a current template for
that CGI and take note of the INTERFACE comment (if present.) This
comment defines what variables are passed into this template. If
there isn't one, I'm afraid you'll have to read the template and
the code to find out what information you get.
</P
><P
>&#13; Write your template in whatever markup or text style is appropriate.
</P
><P
>&#13; You now need to decide what content type you want your template
served as. Open up the <TT
CLASS="filename"
>localconfig</TT
> file and find the
<TT
CLASS="filename"
>$contenttypes</TT
>
variable. If your content type is not there, add it. Remember
the three- or four-letter tag assigned to you content type.
This tag will be part of the template filename.
</P
><P
>&#13; Save the template as <TT
CLASS="filename"
>&#60;stubname&#62;-&#60;formatname&#62;.&#60;contenttypetag&#62;.tmpl</TT
>.
Try out the template by calling the CGI as
<TT
CLASS="filename"
>&#60;cginame&#62;.cgi?format=&#60;formatname&#62;</TT
> .
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1581">5.7.4. Particular Templates</H2
><P
>&#13; There are a few templates you may be particularly interested in
customising for your installation.
</P
><P
>&#13; <B
CLASS="command"
>index.html.tmpl</B
>:
This is the Bugzilla front page.
</P
><P
>&#13; <B
CLASS="command"
>global/header.html.tmpl</B
>:
This defines the header that goes on all Bugzilla pages.
The header includes the banner, which is what appears to users
and is probably what you want to edit instead. However the
header also includes the HTML HEAD section, so you could for
example add a stylesheet or META tag by editing the header.
</P
><P
>&#13; <B
CLASS="command"
>global/banner.html.tmpl</B
>:
This contains the "banner", the part of the header that appears
at the top of all Bugzilla pages. The default banner is reasonably
barren, so you'll probably want to customise this to give your
installation a distinctive look and feel. It is recommended you
preserve the Bugzilla version number in some form so the version
you are running can be determined, and users know what docs to read.
</P
><P
>&#13; <B
CLASS="command"
>global/footer.html.tmpl</B
>:
This defines the footer that goes on all Bugzilla pages. Editing
this is another way to quickly get a distinctive look and feel for
your Bugzilla installation.
</P
><P
>&#13; <B
CLASS="command"
>bug/create/user-message.html.tmpl</B
>:
This is a message that appears near the top of the bug reporting page.
By modifying this, you can tell your users how they should report
bugs.
</P
><P
>&#13; <B
CLASS="command"
>bug/create/create.html.tmpl</B
> and
<B
CLASS="command"
>bug/create/comment.txt.tmpl</B
>:
You may wish to get bug submitters to give certain bits of structured
information, each in a separate input widget, for which there is not a
field in the database. The bug entry system has been designed in an
extensible fashion to enable you to define arbitrary fields and widgets,
and have their values appear formatted in the initial
Description, rather than in database fields. An example of this
is the mozilla.org
<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?format=guided"
TARGET="_top"
>guided
bug submission form</A
>.
</P
><P
>&#13; To make this work, create a custom template for
<TT
CLASS="filename"
>enter_bug.cgi</TT
> (the default template, on which you
could base it, is <TT
CLASS="filename"
>create.html.tmpl</TT
>),
and either call it <TT
CLASS="filename"
>create.html.tmpl</TT
> or use a format and
call it <TT
CLASS="filename"
>create-&#60;formatname&#62;.html.tmpl</TT
>.
Put it in the <TT
CLASS="filename"
>custom/bug/create</TT
>
directory. In it, add widgets for each piece of information you'd like
collected - such as a build number, or set of steps to reproduce.
</P
><P
>&#13; Then, create a template like
<TT
CLASS="filename"
>custom/bug/create/comment.txt.tmpl</TT
>, also named
after your format if you are using one, which
references the form fields you have created. When a bug report is
submitted, the initial comment attached to the bug report will be
formatted according to the layout of this template.
</P
><P
>&#13; For example, if your enter_bug template had a field
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#60;input type="text" name="buildid" size="30"&#62;</PRE
></FONT
></TD
></TR
></TABLE
>
and then your comment.txt.tmpl had
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>BuildID: [% form.buildid %]</PRE
></FONT
></TD
></TR
></TABLE
>
then
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>BuildID: 20020303</PRE
></FONT
></TD
></TR
></TABLE
>
would appear in the initial checkin comment.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="security.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="upgrading.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Security</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Upgrading to New Releases</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

174
webtools/bugzilla/docs/html/cvs.html
Просмотреть файл

@ -1,174 +0,0 @@
<HTML
><HEAD
><TITLE
>CVS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"><LINK
REL="PREVIOUS"
TITLE="Bonsai"
HREF="bonsai.html"><LINK
REL="NEXT"
TITLE="Perforce SCM"
HREF="scm.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="bonsai.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="scm.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="cvs">5.2. CVS</H1
><P
>CVS integration is best accomplished, at this point, using
the Bugzilla Email Gateway. There have been some files
submitted to allow greater CVS integration, but we need to make
certain that Bugzilla is not tied into one particular software
management package.</P
><P
>&#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"
>"[Bug
XXXX]"</SPAN
>, and you can have CVS check-in comments append
to your Bugzilla bug. If you have your check-in script include
an @resolution field, you can even change the Bugzilla bug
state.
</P
><P
>&#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"
>&#13; http://homepages.kcbbs.gen.nz/~tonyg/</A
>, under the
<SPAN
CLASS="QUOTE"
>"cvszilla"</SPAN
> link.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="bonsai.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="scm.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bonsai</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="integration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Perforce SCM</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

26
webtools/bugzilla/docs/html/database.html
Просмотреть файл

@ -10,8 +10,8 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Software Download Links"
HREF="downloadlinks.html"><LINK
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
REL="NEXT"
TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="downloadlinks.html"
HREF="faq.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
NAME="database">Appendix C. The Bugzilla Database</H1
NAME="database">Appendix B. The Bugzilla Database</H1
><DIV
CLASS="TOC"
><DL
@ -78,20 +78,15 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>C.1. <A
>B.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
></DT
><DT
>C.2. <A
>B.2. <A
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
><DT
>C.3. <A
HREF="granttables.html"
>MySQL Permissions &#38; Grant Tables</A
></DT
></DL
></DIV
><DIV
@ -115,8 +110,9 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
>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
></TABLE
@ -138,7 +134,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="downloadlinks.html"
HREF="faq.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -166,7 +162,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Software Download Links</TD
>The Bugzilla FAQ</TD
><TD
WIDTH="34%"
ALIGN="center"

291
webtools/bugzilla/docs/html/dbdoc.html
Просмотреть файл

@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Database Schema Chart"
HREF="dbschema.html"><LINK
REL="NEXT"
TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"></HEAD
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -53,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. The Bugzilla Database</TD
>Appendix B. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="granttables.html"
HREF="patches.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,183 +73,171 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="dbdoc">C.2. MySQL Bugzilla Database Introduction</H1
NAME="dbdoc">B.2. MySQL Bugzilla Database Introduction</H1
><P
>&#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
and will happen to you, so learn how the schema works and deal with it when it
comes.
</P
>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 and will happen to you, so learn how the schema works
and deal with it when it comes.</P
><P
>&#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
enter and edit bugs to your heart's content. Perhaps you've gone through the
trouble of setting up a gateway for people to submit bugs to your database via
email, have had a few people test it, and received rave reviews from your beta
testers.
</P
>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 enter and edit bugs to your heart's content. Perhaps
you've gone through the trouble of setting up a gateway for people to
submit bugs to your database via email, have had a few people test it,
and received rave reviews from your beta testers.</P
><P
>&#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
>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
>&#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
their pages, customize their layouts, generate reports, track status with
greater efficiency than ever before, leap tall buildings with a single bound
and rescue Jane from the clutches of Certain Death!
</P
>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 their pages, customize their layouts,
generate reports, track status with greater efficiency than ever before,
leap tall buildings with a single bound and rescue Jane from the clutches
of Certain Death!</P
><P
>&#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
>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
>&#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,
in fact, a bug is valid. I don't want to lose two years of training to a
new software product. You need to change the bug status of 'verified' to
'approved' as soon as possible. To avoid confusion, of course."
</P
>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, in fact, a bug is valid. I don't want to
lose two years of training to a new software product. You need to change
the bug status of 'verified' to 'approved' as soon as possible. To avoid
confusion, of course."</P
><P
>&#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...
no problem," All the while you quiver inside like a beached jellyfish bubbling,
burbling, and boiling on a hot Jamaican sand dune...
</P
>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... no problem," All the while you quiver
inside like a beached jellyfish bubbling, burbling, and boiling on a hot
Jamaican sand dune...</P
><P
>&#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
>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"
><H2
CLASS="section"
><A
NAME="AEN2272">C.2.1. Bugzilla Database Basics</H2
NAME="AEN2077">B.2.1. Bugzilla Database Basics</H2
><P
>&#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
>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
CLASS="QUOTE"
>"bigint"</SPAN
> and a
<SPAN
>
and a
<SPAN
CLASS="QUOTE"
>"tinyint"</SPAN
> entry in MySQL. I recommend you refer
to the MySQL documentation, available at <A
>
entry in MySQL. I recommend you refer to the MySQL documentation,
available at
<A
HREF="http://www.mysql.com/doc.html"
TARGET="_top"
>MySQL.com</A
>. Below are the basics you need to know about the Bugzilla database. Check the chart above for more details.
</P
><P
>
. Below are the basics you need to know about the Bugzilla database.
Check the chart above for more details.</P
><P
>&#13; <P
></P
><OL
TYPE="1"
><LI
><P
>&#13; To connect to your database:
</P
>To connect to your database:</P
><P
>&#13; <TT
>&#13; <TT
CLASS="prompt"
>bash#</TT
><B
>
<B
CLASS="command"
>mysql</B
><TT
>
<TT
CLASS="parameter"
><I
>-u root</I
></TT
>
</P
</P
><P
>&#13; If this works without asking you for a password,
<EM
>If this works without asking you for a password,
<EM
>shame on you</EM
>! You should have
locked your security down like the installation
instructions told you to. You can find details on
locking down your database in the Bugzilla FAQ in this
directory (under "Security"), or more robust security
generalities in the MySQL searchable documentation at
http://www.mysql.com/php/manual.php3?section=Privilege_system .
</P
>
! You should have locked your security down like the installation
instructions told you to. You can find details on locking down
your database in the Bugzilla FAQ in this directory (under
"Security"), or more robust security generalities in the
<A
HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
TARGET="_top"
>MySQL
searchable documentation</A
>.
</P
></LI
><LI
><P
>You should now be at a prompt that looks like
this:</P
>You should now be at a prompt that looks like this:</P
><P
><TT
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
></P
>
</P
><P
>At the prompt, if <SPAN
>At the prompt, if
<SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> is the name
you chose in the<TT
>
is the name you chose in the
<TT
CLASS="filename"
>localconfig</TT
> file
for your Bugzilla database, type:</P
>
file for your Bugzilla database, type:</P
><P
><TT
>&#13; <TT
CLASS="prompt"
>mysql</TT
><B
>
<B
CLASS="command"
>use bugs;</B
></P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Don't forget the <SPAN
CLASS="QUOTE"
>";"</SPAN
> at the end of
each line, or you'll be kicking yourself later.</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
></OL
>
@ -259,31 +247,31 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN2301">C.2.1.1. Bugzilla Database Tables</H3
NAME="AEN2104">B.2.1.1. Bugzilla Database Tables</H3
><P
> Imagine your MySQL database as a series of
spreadsheets, and you won't be too far off. If you use this
command:</P
>Imagine your MySQL database as a series of spreadsheets, and
you won't be too far off. If you use this command:</P
><P
><TT
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
><B
>
<B
CLASS="command"
>show tables from bugs;</B
></P
>
</P
><P
>you'll be able to see all the
<SPAN
>you'll be able to see the names of all the
<SPAN
CLASS="QUOTE"
>"spreadsheets"</SPAN
> (tables) in your database. It
is similar to a file system, only faster and more robust for
certain types of operations.</P
>
(tables) in your database.</P
><P
>From the command issued above, ou should have some
output that looks like this:
<TABLE
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
@ -319,16 +307,16 @@ CLASS="programlisting"
| votes |
| watch |
+-------------------+
</PRE
</PRE
></FONT
></TD
></TR
></TABLE
></P
>
</P
><P
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>
@ -490,21 +478,6 @@ Although&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;enum&nbsp;field,&nbs
of&nbsp;"APPROVED"&nbsp;until&nbsp;you&nbsp;make&nbsp;the&nbsp;perl&nbsp;changes.&nbsp;&nbsp;&nbsp;Note&nbsp;that&nbsp;this&nbsp;change&nbsp;I<br>
mentioned&nbsp;can&nbsp;also&nbsp;be&nbsp;done&nbsp;by&nbsp;editing&nbsp;checksetup.pl,&nbsp;which&nbsp;automates&nbsp;a&nbsp;lot&nbsp;of<br>
this.&nbsp;&nbsp;But&nbsp;you&nbsp;need&nbsp;to&nbsp;know&nbsp;this&nbsp;stuff&nbsp;anyway,&nbsp;right?<br>
<br>
&nbsp;&nbsp;I&nbsp;hope&nbsp;this&nbsp;database&nbsp;tutorial&nbsp;has&nbsp;been&nbsp;useful&nbsp;for&nbsp;you.&nbsp;&nbsp;If&nbsp;you&nbsp;have&nbsp;comments<br>
to&nbsp;add,&nbsp;questions,&nbsp;concerns,&nbsp;etc.&nbsp;please&nbsp;direct&nbsp;them&nbsp;to<br>
mbarnson@excitehome.net.&nbsp;&nbsp;Please&nbsp;direct&nbsp;flames&nbsp;to&nbsp;/dev/null&nbsp;:)&nbsp;&nbsp;Have&nbsp;a&nbsp;nice<br>
day!<br>
<br>
<br>
<br>
===<br>
LINKS<br>
===<br>
<br>
Great&nbsp;MySQL&nbsp;tutorial&nbsp;site:<br>
http://www.devshed.com/Server_Side/MySQL/<br>
<br>
</P
></DIV
></DIV
@ -543,7 +516,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="granttables.html"
HREF="patches.html"
ACCESSKEY="N"
>Next</A
></TD
@ -567,7 +540,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>MySQL Permissions &#38; Grant Tables</TD
>Useful Patches and Utilities for Bugzilla</TD
></TR
></TABLE
></DIV

4
webtools/bugzilla/docs/html/dbschema.html
Просмотреть файл

@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. The Bugzilla Database</TD
>Appendix B. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="dbschema">C.1. Database Schema Chart</H1
NAME="dbschema">B.1. Database Schema Chart</H1
><P
>&#13; <DIV
CLASS="mediaobject"

15
webtools/bugzilla/docs/html/disclaimer.html
Просмотреть файл

@ -73,16 +73,15 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="disclaimer">1.3. Disclaimer</H1
NAME="disclaimer">1.2. Disclaimer</H1
><P
>&#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
document may cause your girlfriend to leave you, your cats to
pee on your furniture and clothing, your computer to cease
functioning, your boss to fire you, and global thermonuclear
war. Proceed with caution.
This document may contain errors
and inaccuracies that may damage your system, cause your partner
to leave you, your boss to fire you, your cats to
pee on your furniture and clothing, and global thermonuclear
war. Proceed with caution.
</P
><P
>&#13; All copyrights are held by their respective owners, unless
@ -113,7 +112,7 @@ NAME="disclaimer">1.3. Disclaimer</H1
team members, Netscape Communications, America Online Inc., and
any affiliated developers or sponsors assume no liability for
your use of this product. You have the source code to this
product, and are responsible for auditing it yourself to insure
product, and are responsible for auditing it yourself to ensure
your security needs are met.
</P
></DIV

237
webtools/bugzilla/docs/html/downloadlinks.html
Просмотреть файл

@ -1,237 +0,0 @@
<HTML
><HEAD
><TITLE
>Software Download Links</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
REL="NEXT"
TITLE="The Bugzilla Database"
HREF="database.html"></HEAD
><BODY
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="faq.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="database.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="appendix"
><H1
><A
NAME="downloadlinks">Appendix B. Software Download Links</H1
><P
>&#13; All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</P
><P
>&#13; Apache Web Server: <A
HREF="http://www.apache.org/"
TARGET="_top"
>http://www.apache.org</A
>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</P
><P
>&#13; Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
>&#13; http://www.mozilla.org/projects/bugzilla/</A
>
</P
><P
>&#13; MySQL: <A
HREF="http://www.mysql.com/"
TARGET="_top"
>http://www.mysql.com/</A
>
</P
><P
>&#13; Perl: <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org/</A
>
</P
><P
>&#13; CPAN: <A
HREF="http://www.cpan.org/"
TARGET="_top"
>http://www.cpan.org/</A
>
</P
><P
>&#13; DBI Perl module:
<A
HREF="http://www.cpan.org/modules/by-module/DBI/"
TARGET="_top"
>&#13; http://www.cpan.org/modules/by-module/DBI/</A
>
</P
><P
>&#13; Data::Dumper module:
<A
HREF="http://www.cpan.org/modules/by-module/Data/"
TARGET="_top"
>&#13; http://www.cpan.org/modules/by-module/Data/</A
>
</P
><P
>&#13; MySQL related Perl modules:
<A
HREF="http://www.cpan.org/modules/by-module/Mysql/"
TARGET="_top"
>&#13; http://www.cpan.org/modules/by-module/Mysql/</A
>
</P
><P
>&#13; TimeDate Perl module collection:
<A
HREF="http://www.cpan.org/modules/by-module/Date/"
TARGET="_top"
>&#13; http://www.cpan.org/modules/by-module/Date/</A
>
</P
><P
>&#13; GD Perl module:
<A
HREF="http://www.cpan.org/modules/by-module/GD/"
TARGET="_top"
>&#13; http://www.cpan.org/modules/by-module/GD/</A
>
Alternately, you should be able to find the latest version of
GD at <A
HREF="http://www.boutell.com/gd/"
TARGET="_top"
>http://www.boutell.com/gd/</A
>
</P
><P
>&#13; Chart::Base module:
<A
HREF="http://www.cpan.org/modules/by-module/Chart/"
TARGET="_top"
>&#13; http://www.cpan.org/modules/by-module/Chart/</A
>
</P
><P
>&#13; LinuxDoc Software:
<A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>http://www.linuxdoc.org/</A
>
(for documentation maintenance)
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="faq.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="database.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Bugzilla FAQ</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla Database</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

279
webtools/bugzilla/docs/html/errata.html
Просмотреть файл

@ -1,279 +0,0 @@
<HTML
><HEAD
><TITLE
>ERRATA</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
HREF="installation.html"><LINK
REL="NEXT"
TITLE="Step-by-step Install"
HREF="stepbystep.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="installation.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="stepbystep.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="errata">3.1. ERRATA</H1
><P
>Here are some miscellaneous notes about possible issues you
main run into when you begin your Bugzilla installation.
Reference platforms for Bugzilla installation are Redhat Linux
7.2, Linux-Mandrake 8.0, and Solaris 8.</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#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"
>cannot chdir(/var/spool/mqueue):
Permission denied</SPAN
> This is because your
<TT
CLASS="filename"
>/var/spool/mqueue</TT
> directory has a mode of
<SPAN
CLASS="QUOTE"
>"drwx------"</SPAN
>. Type <B
CLASS="command"
>chmod 755
<TT
CLASS="filename"
>/var/spool/mqueue</TT
></B
> as root to
fix this problem.
</TD
></TR
><TR
><TD
>&#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
additional setup for installation. Please see the Mac OS X
installation section below for details
</TD
></TR
><TR
><TD
>&#13; Release Notes for Bugzilla 2.16 are available at
<TT
CLASS="filename"
>docs/rel_notes.txt</TT
> in your Bugzilla
source distribution.
</TD
></TR
><TR
><TD
>&#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.
</TD
></TR
></TBODY
></TABLE
><P
></P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
of third-party utilities. To install Bugzilla on Win32 requires
fair Perl proficiency, and if you use a webserver other than Apache you
should be intimately familiar with the security mechanisms and CGI
environment thereof.
</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="stepbystep.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Step-by-step Install</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

726
webtools/bugzilla/docs/html/extraconfig.html Normal file
Просмотреть файл

@ -0,0 +1,726 @@
<HTML
><HEAD
><TITLE
>Optional Additional Configuration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Step-by-step Install"
HREF="stepbystep.html"><LINK
REL="NEXT"
TITLE="Win32 Installation Notes"
HREF="win32.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="stepbystep.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="win32.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="extraconfig">4.2. Optional Additional Configuration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN845">4.2.1. Dependency Charts</H2
><P
>As well as the text-based dependency graphs, Bugzilla also
supports dependency graphing, using a package called 'dot'.
Exactly how this works is controlled by the 'webdotbase' parameter,
which can have one of three values:
</P
><P
>&#13; <P
></P
><OL
TYPE="1"
><LI
><P
>&#13; A complete file path to the command 'dot' (part of
<A
HREF="http://www.graphviz.org/"
TARGET="_top"
>GraphViz</A
>)
will generate the graphs locally
</P
></LI
><LI
><P
>&#13; A URL prefix pointing to an installation of the webdot package will
generate the graphs remotely
</P
></LI
><LI
><P
>&#13; A blank value will disable dependency graphing.
</P
></LI
></OL
>
</P
><P
>So, to get this working, install
<A
HREF="http://www.graphviz.org/"
TARGET="_top"
>GraphViz</A
>. If you
do that, you need to
<A
HREF="http://httpd.apache.org/docs/mod/mod_imap.html"
TARGET="_top"
>enable
server-side image maps</A
> in Apache.
Alternatively, you could set up a webdot server, or use the AT&#38;T
public webdot server (the
default for the webdotbase param). Note that AT&#38;T's server won't work
if Bugzilla is only accessible using HTTPS.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN860">4.2.2. Bug Graphs</H2
><P
>As long as you installed the GD and Graph::Base Perl modules you
might as well turn on the nifty Bugzilla bug reporting graphs.</P
><P
>Add a cron entry like this to run
<TT
CLASS="filename"
>collectstats.pl</TT
>
daily at 5 after midnight:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="command"
>crontab -e</B
>
</TT
>
</TD
></TR
><TR
><TD
>&#13; <TT
CLASS="computeroutput"
>5 0 * * * cd &#60;your-bugzilla-directory&#62; ;
./collectstats.pl</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
>After two days have passed you'll be able to view bug graphs from
the Bug Reports page.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN873">4.2.3. The Whining Cron</H2
><P
>By now you have a fully functional Bugzilla, but what good are
bugs if they're not annoying? To help make those bugs more annoying you
can set up Bugzilla's automatic whining system to complain at engineers
which leave their bugs in the NEW state without triaging them.
</P
><P
>&#13; This can be done by
adding the following command as a daily crontab entry (for help on that
see that crontab man page):
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <TT
CLASS="computeroutput"
>&#13; <B
CLASS="command"
>cd &#60;your-bugzilla-directory&#62; ;
./whineatnews.pl</B
>
</TT
>
</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><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
>Depending on your system, crontab may have several manpages.
The following command should lead you to the most useful page for
this purpose:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>man 5 crontab</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="bzldap">4.2.4. LDAP Authentication</H2
><P
>&#13; <DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This information on using the LDAP
authentication options with Bugzilla is old, and the authors do
not know of anyone who has tested it. Approach with caution.
</P
></TD
></TR
></TABLE
></DIV
>
</P
><P
>&#13; The existing authentication
scheme for Bugzilla uses email addresses as the primary user ID, and a
password to authenticate that user. All places within Bugzilla where
you need to deal with user ID (e.g assigning a bug) use the email
address. The LDAP authentication builds on top of this scheme, rather
than replacing it. The initial log in is done with a username and
password for the LDAP directory. This then fetches the email address
from LDAP and authenticates seamlessly in the standard Bugzilla
authentication scheme using this email address. If an account for this
address already exists in your Bugzilla system, it will log in to that
account. If no account for that email address exists, one is created at
the time of login. (In this case, Bugzilla will attempt to use the
"displayName" or "cn" attribute to determine the user's full name.)
After authentication, all other user-related tasks are still handled by
email address, not LDAP username. You still assign bugs by email
address, query on users by email address, etc.
</P
><P
>Using LDAP for Bugzilla authentication requires the
Mozilla::LDAP (aka PerLDAP) Perl module. The
Mozilla::LDAP module in turn requires Netscape's Directory SDK for C.
After you have installed the SDK, then install the PerLDAP module.
Mozilla::LDAP and the Directory SDK for C are both
<A
HREF="http://www.mozilla.org/directory/"
TARGET="_top"
>available for
download</A
> from mozilla.org.
</P
><P
>&#13; Set the Param 'useLDAP' to "On" **only** if you will be using an LDAP
directory for
authentication. Be very careful when setting up this parameter; if you
set LDAP authentication, but do not have a valid LDAP directory set up,
you will not be able to log back in to Bugzilla once you log out. (If
this happens, you can get back in by manually editing the data/params
file, and setting useLDAP back to 0.)
</P
><P
>If using LDAP, you must set the
three additional parameters: Set LDAPserver to the name (and optionally
port) of your LDAP server. If no port is specified, it defaults to the
default port of 389. (e.g "ldap.mycompany.com" or
"ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching
for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids
must be unique under the DN specified here. Set LDAPmailattribute to
the name of the attribute in your LDAP directory which contains the
primary email address. On most directory servers available, this is
"mail", but you may need to change this.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="content-type">4.2.5. Preventing untrusted Bugzilla content from executing malicious
Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious Javascript
code. Due to internationalization concerns, we are unable to
incorporate the code changes necessary to fulfill the CERT advisory
requirements mentioned in
<A
HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
TARGET="_top"
>&#13; http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
>.
Executing the following code snippet from a UNIX command shell will
rectify the problem if your Bugzilla installation is intended for an
English-speaking audience. As always, be sure your Bugzilla
installation has a good backup before making changes, and I recommend
you understand what the script is doing before executing it.</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; charset=ISO-8859-1/i" *.cgi *.pl
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>All this one-liner command does is search for all instances of
<SPAN
CLASS="QUOTE"
>"Content-type: text/html"</SPAN
>
and replaces it with
<SPAN
CLASS="QUOTE"
>"Content-Type: text/html; charset=ISO-8859-1"</SPAN
>
. This specification prevents possible Javascript attacks on the
browser, and is suggested for all English-speaking sites. For
non-English-speaking Bugzilla sites, I suggest changing
<SPAN
CLASS="QUOTE"
>"ISO-8859-1"</SPAN
>, above, to
<SPAN
CLASS="QUOTE"
>"UTF-8"</SPAN
>.</P
><P
>Note: using &#60;meta&#62; tags to set the charset is not
recommended, as there's a bug in Netscape 4.x which causes pages
marked up in this way to load twice.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="htaccess">4.2.6. <TT
CLASS="filename"
>.htaccess</TT
>
files and security</H2
><P
>To enhance the security of your Bugzilla installation, Bugzilla's
<TT
CLASS="filename"
>checksetup.pl</TT
> script will generate
<I
CLASS="glossterm"
>&#13; <TT
CLASS="filename"
>.htaccess</TT
>
</I
>
files which the Apache webserver can use to restrict access to the
bugzilla data files.
These .htaccess files will not work with Apache 1.2.x - but this
has security holes, so you shouldn't be using it anyway.
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you are using an alternate provider of
<SPAN
CLASS="productname"
>webdot</SPAN
>
services for graphing (as described when viewing
<TT
CLASS="filename"
>editparams.cgi</TT
>
in your web browser), you will need to change the ip address in
<TT
CLASS="filename"
>data/webdot/.htaccess</TT
>
to the ip address of the webdot server that you are using.</P
></TD
></TR
></TABLE
></DIV
>
</P
><P
>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
>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
>If you are using Internet Information Server (IIS) or another
web server which does not observe
<TT
CLASS="filename"
>.htaccess</TT
>
conventions, you can disable their creation by editing
<TT
CLASS="filename"
>localconfig</TT
>
and setting the
<TT
CLASS="varname"
>$create_htaccess</TT
>
variable to
<TT
CLASS="parameter"
><I
>0</I
></TT
>.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="mod-throttle">4.2.7. <TT
CLASS="filename"
>mod_throttle</TT
>
and Security</H2
><P
>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"
>mod_throttle</TT
>
which can limit connections by ip-address. You may download this module
at
<A
HREF="http://www.snert.com/Software/Throttle/"
TARGET="_top"
>&#13; http://www.snert.com/Software/Throttle/</A
>.
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"
>ThrottleClientIP</B
>
command provided by this module to accomplish this goal. See the
<A
HREF="http://www.snert.com/Software/Throttle/"
TARGET="_top"
>Module
Instructions</A
>
for more information.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="stepbystep.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="win32.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Step-by-step Install</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Win32 Installation Notes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

1942
webtools/bugzilla/docs/html/faq.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

161
webtools/bugzilla/docs/html/feedback.html
Просмотреть файл

@ -1,161 +0,0 @@
<HTML
><HEAD
><TITLE
>Feedback</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="Contributors"
HREF="contributors.html"><LINK
REL="NEXT"
TITLE="Translations"
HREF="translations.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="contributors.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. About This Guide</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="translations.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="feedback">1.7. Feedback</H1
><P
>&#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"
>&#60;<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A
>&#62;</TT
>. Please send flames to
<TT
CLASS="email"
>&#60;<A
HREF="mailto:devnull@localhost"
>devnull@localhost</A
>&#62;</TT
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="contributors.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="translations.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Contributors</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="about.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Translations</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

489
webtools/bugzilla/docs/html/geninstall.html
Просмотреть файл

@ -1,489 +0,0 @@
<HTML
><HEAD
><TITLE
>Installation General Notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="BSD Installation Notes"
HREF="bsdinstall.html"><LINK
REL="NEXT"
TITLE="Win32 Installation Notes"
HREF="win32.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="bsdinstall.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="win32.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="geninstall">3.5. Installation General Notes</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN874">3.5.1. Modifying Your Running System</H2
><P
>&#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
>&#13; If you make a change to the structural data in your database
(the versions table for example), or to the
<SPAN
CLASS="QUOTE"
>"constants"</SPAN
> encoded in defparams.pl, you will
need to remove the cached content from the data directory
(by doing a <SPAN
CLASS="QUOTE"
>"rm data/versioncache"</SPAN
>), or your
changes won't show up.
</P
><P
>&#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"
><H2
CLASS="section"
><A
NAME="AEN881">3.5.2. Upgrading From Previous Versions</H2
><P
>&#13; A plain Bugzilla is fairly easy to upgrade from one version to a newer one.
However, things get a bit more complicated if you've made changes to
Bugzilla's code. In this case, you may have to re-make or reapply those
changes.
It is recommended that you take a backup of your database and your entire
Bugzilla installation before attempting an upgrade. You can upgrade a 'clean'
installation by untarring a new tarball over the old installation. If you
are upgrading from 2.12 or later, you can type <TT
CLASS="filename"
>cvs -z3
update</TT
>, and resolve conflicts if there are any.
</P
><P
>&#13; Because the developers of Bugzilla are constantly adding new tables, columns
and fields, you'll probably get SQL errors if you just update the code and
attempt to use Bugzilla. Always run the checksetup.pl script whenever
you upgrade your installation.
</P
><P
>&#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"
><H2
CLASS="section"
><A
NAME="htaccess">3.5.3. <TT
CLASS="filename"
>.htaccess</TT
> files and security</H2
><P
>&#13; To enhance the security of your Bugzilla installation,
Bugzilla will generate
<I
CLASS="glossterm"
><TT
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"
>.htaccess</TT
> files. These .htaccess files
will not work with Apache 1.2.x - but this has security holes, so you
shouldn't be using it anyway.
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; If you are using an alternate provider of
<SPAN
CLASS="productname"
>webdot</SPAN
> services for graphing
(as described when viewing
<TT
CLASS="filename"
>editparams.cgi</TT
> in your web
browser), you will need to change the ip address in
<TT
CLASS="filename"
>data/webdot/.htaccess</TT
> to the ip
address of the webdot server that you are using.
</P
></TD
></TR
></TABLE
></DIV
>
</P
><P
>&#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"
>.htaccess</TT
>
conventions, you can disable their creation by editing
<TT
CLASS="filename"
>localconfig</TT
> and setting the
<TT
CLASS="varname"
>$create_htaccess</TT
> variable to
<TT
CLASS="parameter"
><I
>0</I
></TT
>.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="mod-throttle">3.5.4. <TT
CLASS="filename"
>mod_throttle</TT
> and Security</H2
><P
>&#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"
>mod_throttle</TT
> which can limit
connections by ip-address. You may download this module at
<A
HREF="http://www.snert.com/Software/Throttle/"
TARGET="_top"
>http://www.snert.com/Software/Throttle/</A
>. 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"
>ThrottleClientIP</B
> command provided by this module to accomplish this goal. See the <A
HREF="http://www.snert.com/Software/Throttle/"
TARGET="_top"
>Module Instructions</A
> for more information. </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="content-type">3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</H2
><P
>It is possible for a Bugzilla to execute malicious
Javascript code. Due to internationalization concerns, we are
unable to incorporate the code changes necessary to fulfill
the CERT advisory requirements mentioned in <A
HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
TARGET="_top"
>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
>. Executing the following code snippet from a UNIX command shell will rectify the problem if your Bugzilla installation is intended for an English-speaking audience. As always, be sure your Bugzilla installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. </P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
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
></FONT
></TD
></TR
></TABLE
></P
><P
>&#13; All this one-liner command does is search for all instances of
<SPAN
CLASS="QUOTE"
>"Content-type: text/html"</SPAN
> and replaces it with
<SPAN
CLASS="QUOTE"
>"Content-Type: text/html; charset=ISO-8859-1"</SPAN
>.
This specification prevents possible Javascript attacks on the
browser, and is suggested for all English-speaking sites. For
non-english-speaking Bugzilla sites, I suggest changing
<SPAN
CLASS="QUOTE"
>"ISO-8859-1"</SPAN
>, above, to <SPAN
CLASS="QUOTE"
>"UTF-8"</SPAN
>.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="unixhistory">3.5.6. UNIX Installation Instructions History</H2
><P
>&#13; This document was originally adapted from the Bonsai
installation instructions by Terry Weissman
&#60;terry@mozilla.org&#62;.
</P
><P
>&#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
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla"
TARGET="_top"
>http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla</A
> ).
</P
><P
>&#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
>&#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
>&#13; Comments from people using this Guide for the first time are
particularly welcome.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="bsdinstall.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="win32.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>BSD Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Win32 Installation Notes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

165
webtools/bugzilla/docs/html/gfdl-0.html
Просмотреть файл

@ -1,165 +0,0 @@
<HTML
><HEAD
><TITLE
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-0">0. PREAMBLE</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-1.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>APPLICABILITY AND DEFINITIONS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

206
webtools/bugzilla/docs/html/gfdl-1.html
Просмотреть файл

@ -1,206 +0,0 @@
<HTML
><HEAD
><TITLE
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>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</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-0.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-2.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>VERBATIM COPYING</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

162
webtools/bugzilla/docs/html/gfdl-10.html
Просмотреть файл

@ -1,162 +0,0 @@
<HTML
><HEAD
><TITLE
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>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</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-9.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-howto.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>How to use this License for your documents</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

156
webtools/bugzilla/docs/html/gfdl-2.html
Просмотреть файл

@ -1,156 +0,0 @@
<HTML
><HEAD
><TITLE
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-2">2. VERBATIM COPYING</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-3.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COPYING IN QUANTITY</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

180
webtools/bugzilla/docs/html/gfdl-3.html
Просмотреть файл

@ -1,180 +0,0 @@
<HTML
><HEAD
><TITLE
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>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</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-2.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-4.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>MODIFICATIONS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

286
webtools/bugzilla/docs/html/gfdl-4.html
Просмотреть файл

@ -1,286 +0,0 @@
<HTML
><HEAD
><TITLE
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-4">4. MODIFICATIONS</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-3.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-5.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COMBINING DOCUMENTS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

165
webtools/bugzilla/docs/html/gfdl-5.html
Просмотреть файл

@ -1,165 +0,0 @@
<HTML
><HEAD
><TITLE
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-5">5. COMBINING DOCUMENTS</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-4.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-6.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>COLLECTIONS OF DOCUMENTS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

155
webtools/bugzilla/docs/html/gfdl-6.html
Просмотреть файл

@ -1,155 +0,0 @@
<HTML
><HEAD
><TITLE
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>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</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-5.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-7.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>AGGREGATION WITH INDEPENDENT WORKS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

159
webtools/bugzilla/docs/html/gfdl-7.html
Просмотреть файл

@ -1,159 +0,0 @@
<HTML
><HEAD
><TITLE
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>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</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-6.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-8.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>TRANSLATION</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

154
webtools/bugzilla/docs/html/gfdl-8.html
Просмотреть файл

@ -1,154 +0,0 @@
<HTML
><HEAD
><TITLE
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-8">8. TRANSLATION</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-7.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-9.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>TERMINATION</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

151
webtools/bugzilla/docs/html/gfdl-9.html
Просмотреть файл

@ -1,151 +0,0 @@
<HTML
><HEAD
><TITLE
>TERMINATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="gfdl-9">9. TERMINATION</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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-8.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-10.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>FUTURE REVISIONS OF THIS LICENSE</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

171
webtools/bugzilla/docs/html/gfdl-howto.html
Просмотреть файл

@ -1,171 +0,0 @@
<HTML
><HEAD
><TITLE
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><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
SUMMARY="Header navigation 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"
ACCESSKEY="P"
>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"
ACCESSKEY="N"
>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</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="AEN2605"><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
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-10.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="glossary.html"
ACCESSKEY="N"
>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"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Glossary</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

214
webtools/bugzilla/docs/html/gfdl.html
Просмотреть файл

@ -1,214 +0,0 @@
<HTML
><HEAD
><TITLE
>GNU Free Documentation License</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Hacking Bugzilla"
HREF="bzhacking.html"><LINK
REL="NEXT"
TITLE="PREAMBLE"
HREF="gfdl-0.html"></HEAD
><BODY
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="bzhacking.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="gfdl-0.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="appendix"
><H1
><A
NAME="gfdl">Appendix E. GNU Free Documentation License</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>0. <A
HREF="gfdl-0.html"
>PREAMBLE</A
></DT
><DT
>1. <A
HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
></DT
><DT
>2. <A
HREF="gfdl-2.html"
>VERBATIM COPYING</A
></DT
><DT
>3. <A
HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
></DT
><DT
>4. <A
HREF="gfdl-4.html"
>MODIFICATIONS</A
></DT
><DT
>5. <A
HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="gfdl-howto.html"
>How to use this License for your documents</A
></DT
></DL
></DIV
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2515"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="bzhacking.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="gfdl-0.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Hacking Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>PREAMBLE</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

457
webtools/bugzilla/docs/html/glossary.html
Просмотреть файл

@ -10,8 +10,8 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="How to use this License for your documents"
HREF="gfdl-howto.html"></HEAD
TITLE="SourceForge"
HREF="variant-sourceforge.html"></HEAD
><BODY
CLASS="glossary"
BGCOLOR="#FFFFFF"
@ -39,7 +39,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-howto.html"
HREF="variant-sourceforge.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -68,7 +68,7 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2610">0-9, high ascii</H1
NAME="AEN2183">0-9, high ascii</H1
><DL
><DT
><B
@ -76,24 +76,22 @@ NAME="AEN2610">0-9, high ascii</H1
></DT
><DD
><P
>&#13; Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories
called <TT
>Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories called
<TT
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
>
to restrict access to certain files. In Bugzilla, they are used
to keep secret files which would otherwise
compromise your installation - e.g. the
<TT
CLASS="filename"
>localconfig</TT
> file contains the
password to your database. If this information were
generally available, and remote access to your database
turned on, you risk corruption of your database by
computer criminals or the curious.
</P
>
file contains the password to your database.
curious.</P
></DD
></DL
></DIV
@ -110,23 +108,28 @@ NAME="gloss-a">A</H1
></DT
><DD
><P
>In this context, Apache is the web server most
commonly used for serving up
<I
>In this context, Apache is the web server most commonly used
for serving up
<I
CLASS="glossterm"
>Bugzilla</I
> pages. Contrary to
popular belief, the apache web server has nothing to do
with the ancient and noble Native American tribe, but
instead derived its name from the fact that it was
<SPAN
>
pages. Contrary to popular belief, the apache web server has nothing
to do with the ancient and noble Native American tribe, but instead
derived its name from the fact that it was
<SPAN
CLASS="QUOTE"
>"a patchy"</SPAN
> version of the original
<SPAN
>
version of the original
<SPAN
CLASS="acronym"
>NCSA</SPAN
> world-wide-web server.</P
>
world-wide-web server.</P
></DD
></DL
></DIV
@ -143,21 +146,24 @@ NAME="gloss-b">B</H1
></DT
><DD
><P
>&#13; A <SPAN
>A
<SPAN
CLASS="QUOTE"
>"Bug"</SPAN
> in Bugzilla refers to an issue
entered into the database which has an associated number,
assignments, comments, etc. Some also refer to a
<SPAN
>"bug"</SPAN
>
in Bugzilla refers to an issue entered into the database which has an
associated number, assignments, comments, etc. Some also refer to a
<SPAN
CLASS="QUOTE"
>"tickets"</SPAN
> or <SPAN
>
or
<SPAN
CLASS="QUOTE"
>"issues"</SPAN
>; in the
context of Bugzilla, they are synonymous.
</P
>;
in the context of Bugzilla, they are synonymous.</P
></DD
><DT
><B
@ -165,29 +171,10 @@ CLASS="QUOTE"
></DT
><DD
><P
>&#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.
</P
></DD
><DT
><B
>Bug Life Cycle</B
></DT
><DD
><P
>A Bug has stages through which it must pass before
becoming a <SPAN
CLASS="QUOTE"
>"closed bug"</SPAN
>, including
acceptance, resolution, and verification. The <SPAN
CLASS="QUOTE"
>"Bug
Life Cycle"</SPAN
> is moderately flexible according to
the needs of the organization using it, though.</P
>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.</P
></DD
><DT
><B
@ -195,9 +182,8 @@ CLASS="QUOTE"
></DT
><DD
><P
>&#13; Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</P
>Bugzilla is the world-leading free software bug tracking system.
</P
></DD
></DL
></DIV
@ -215,39 +201,39 @@ NAME="gloss-component"><B
></DT
><DD
><P
>&#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
create an error in Bugzilla).
</P
>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 create an error in Bugzilla).</P
></DD
><DT
><A
NAME="gloss-cpan"><B
><SPAN
>&#13; <SPAN
CLASS="acronym"
>CPAN</SPAN
></B
>
</B
></DT
><DD
><P
><SPAN
>&#13; <SPAN
CLASS="acronym"
>CPAN</SPAN
> stands for the
<SPAN
>
stands for the
<SPAN
CLASS="QUOTE"
>"Comprehensive Perl Archive Network"</SPAN
>. CPAN
maintains a large number of extremely useful
<I
>.
CPAN maintains a large number of extremely useful
<I
CLASS="glossterm"
>Perl</I
> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
larger program, they provide much-needed algorithms and
functionality.</P
>
modules - encapsulated chunks of code for performing a
particular task.</P
></DD
></DL
></DIV
@ -264,18 +250,19 @@ NAME="gloss-d">D</H1
></DT
><DD
><P
>A daemon is a computer program which runs in the
background. In general, most daemons are started at boot
time via System V init scripts, or through RC scripts on
BSD-based systems. <I
>A daemon is a computer program which runs in the 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"
>mysqld</I
>, the
MySQL server, and <I
>,
the MySQL server, and
<I
CLASS="glossterm"
>apache</I
>, a web
server, are generally run as daemons.</P
>,
a web server, are generally run as daemons.</P
></DD
></DL
></DIV
@ -292,43 +279,25 @@ NAME="gloss-g"></H1
></DT
><DD
><P
>The word <SPAN
>The word
<SPAN
CLASS="QUOTE"
>"Groups"</SPAN
> has a very special
meaning to Bugzilla. Bugzilla's main security mechanism
comes by lumping users into groups, and assigning those
groups certain privileges to
<I
>
has a very special meaning to Bugzilla. Bugzilla's main security
mechanism comes by placing users in groups, and assigning those
groups certain privileges to view bugs in particular
<I
CLASS="glossterm"
>Products</I
> and
<I
CLASS="glossterm"
>Components</I
> in the
<I
>
in the
<I
CLASS="glossterm"
>Bugzilla</I
> database.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-i">I</H1
><DL
><DT
><A
NAME="gloss-infiniteloop"><B
>Infinite Loop</B
></DT
><DD
><P
>A loop of information that never ends; see recursion.</P
>
database.</P
></DD
></DL
></DIV
@ -345,15 +314,16 @@ NAME="gloss-m">M</H1
></DT
><DD
><P
>mysqld is the name of the
<I
>mysqld is the name of the
<I
CLASS="glossterm"
>daemon</I
> for the MySQL database. In
general, it is invoked automatically through the use of
the System V init scripts on GNU/Linux and AT&#38;T System
V-based systems, such as Solaris and HP/UX, or through the
RC scripts on BSD-based systems.</P
>
for the MySQL database. In general, it is invoked automatically
through the use of the System V init scripts on GNU/Linux and
AT&#38;T System V-based systems, such as Solaris and HP/UX, or
through the RC scripts on BSD-based systems.</P
></DD
></DL
></DIV
@ -370,55 +340,11 @@ NAME="gloss-p">P</H1
></DT
><DD
><P
>A Product is a broad category of types of bugs. In
general, there are several Components to a Product. A
Product also defines a default Group (used for Bug
Security) for all bugs entered into components beneath
it.</P
><DIV
CLASS="example"
><A
NAME="AEN2701"><P
><B
>Example 1. A Sample Product</B
></P
><P
>A company sells a software product called
<SPAN
CLASS="QUOTE"
>"X"</SPAN
>. They also maintain some older
software called <SPAN
CLASS="QUOTE"
>"Y"</SPAN
>, and have a secret
project <SPAN
CLASS="QUOTE"
>"Z"</SPAN
>. An effective use of Products
might be to create Products <SPAN
CLASS="QUOTE"
>"X"</SPAN
>,
<SPAN
CLASS="QUOTE"
>"Y"</SPAN
>, <SPAN
CLASS="QUOTE"
>"Z"</SPAN
>, each with Components
of User Interface, Database, and Business Logic. They
might also change group permissions so that only those
people who are members of Group <SPAN
CLASS="QUOTE"
>"Z"</SPAN
> can see
components and bugs under Product
<SPAN
CLASS="QUOTE"
>"Z"</SPAN
>.</P
></DIV
>A Product is a broad category of types of bugs, normally
representing a single piece of software or entity. In general,
there are several Components to a Product. A Product may define a
group (used for security) for all bugs entered into
its Components.</P
></DD
><DT
><B
@ -426,15 +352,16 @@ CLASS="QUOTE"
></DT
><DD
><P
>First written by Larry Wall, Perl is a remarkable
program language. It has the benefits of the flexibility
of an interpreted scripting language (such as shell
script), combined with the speed and power of a compiled
language, such as C. <I
>First written by Larry Wall, Perl is a remarkable program
language. It has the benefits of the flexibility 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"
>Bugzilla</I
> is
maintained in Perl.</P
>
is maintained in Perl.</P
></DD
></DL
></DIV
@ -451,57 +378,33 @@ NAME="gloss-q">Q</H1
></DT
><DD
><P
><SPAN
>&#13; <SPAN
CLASS="QUOTE"
>"QA"</SPAN
>, <SPAN
>,
<SPAN
CLASS="QUOTE"
>"Q/A"</SPAN
>, and
<SPAN
>, and
<SPAN
CLASS="QUOTE"
>"Q.A."</SPAN
> are short for <SPAN
>
are short for
<SPAN
CLASS="QUOTE"
>"Quality
Assurance"</SPAN
>. In most large software development
organizations, there is a team devoted to ensuring the
product meets minimum standards before shipping. This
team will also generally want to track the progress of
bugs over their life cycle, thus the need for the
<SPAN
>"Quality Assurance"</SPAN
>.
In most large software development organizations, there is a team
devoted to ensuring the product meets minimum standards before
shipping. This team will also generally want to track the progress of
bugs over their life cycle, thus the need for the
<SPAN
CLASS="QUOTE"
>"QA Contact"</SPAN
> field in a Bug.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-r">R</H1
><DL
><DT
><A
NAME="gloss-recursion"><B
>Recursion</B
></DT
><DD
><P
>The property of a function looking back at itself for
something. <SPAN
CLASS="QUOTE"
>"GNU"</SPAN
>, for instance, stands for
<SPAN
CLASS="QUOTE"
>"GNU's Not UNIX"</SPAN
>, thus recursing upon itself
for definition. For further clarity, see Infinite
Loop.</P
>
field in a bug.</P
></DD
></DL
></DIV
@ -514,57 +417,71 @@ NAME="gloss-s">S</H1
><DL
><DT
><B
><SPAN
>&#13; <SPAN
CLASS="acronym"
>SGML</SPAN
></B
>
</B
></DT
><DD
><P
><SPAN
>&#13; <SPAN
CLASS="acronym"
>SGML</SPAN
> stands for <SPAN
>
stands for
<SPAN
CLASS="QUOTE"
>"Standard
Generalized Markup Language"</SPAN
>. Created in the
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<SPAN
>"Standard Generalized Markup Language"</SPAN
>.
Created in the 1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<SPAN
CLASS="acronym"
>SGML</SPAN
> has withstood the test of time as
a robust, powerful language.
<I
>
has withstood the test of time as a robust, powerful language.
<I
CLASS="glossterm"
><SPAN
>&#13; <SPAN
CLASS="acronym"
>XML</SPAN
></I
> is the
<SPAN
>
</I
>
is the
<SPAN
CLASS="QUOTE"
>"baby brother"</SPAN
> of SGML; any valid
<SPAN
>
of SGML; any valid
<SPAN
CLASS="acronym"
>XML</SPAN
> document it, by definition, a valid
<SPAN
>
document it, by definition, a valid
<SPAN
CLASS="acronym"
>SGML</SPAN
> document. The document you are
reading is written and maintained in
<SPAN
>
document. The document you are reading is written and maintained in
<SPAN
CLASS="acronym"
>SGML</SPAN
>, and is also valid
<SPAN
>,
and is also valid
<SPAN
CLASS="acronym"
>XML</SPAN
> if you modify the Document Type
Definition.</P
>
if you modify the Document Type Definition.</P
></DD
></DL
></DIV
@ -582,18 +499,18 @@ NAME="gloss-target-milestone"><B
></DT
><DD
><P
>&#13; Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<SPAN
>Target Milestones are Product goals. They are configurable on a
per-Product basis. Most software development houses have a concept of
<SPAN
CLASS="QUOTE"
>"milestones"</SPAN
> where the people funding a
project expect certain functionality on certain dates.
Bugzilla facilitates meeting these milestones by giving
you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.
</P
>
where the people funding a project expect certain functionality on
certain dates. Bugzilla facilitates meeting these milestones by
giving you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.</P
></DD
></DL
></DIV
@ -611,9 +528,9 @@ NAME="zarro-boogs-found"><B
></DT
><DD
><P
>This is the cryptic response sent by Bugzilla when a
query returned no results. It is just a goofy way of
saying "Zero Bugs Found".</P
>This is the cryptic response sent by Bugzilla when a query
returned no results. It is just a goofy way of saying "Zero Bugs
Found".</P
></DD
></DL
></DIV
@ -634,7 +551,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-howto.html"
HREF="variant-sourceforge.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -658,7 +575,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to use this License for your documents</TD
>SourceForge</TD
><TD
WIDTH="34%"
ALIGN="center"

351
webtools/bugzilla/docs/html/granttables.html
Просмотреть файл

@ -1,351 +0,0 @@
<HTML
><HEAD
><TITLE
>MySQL Permissions &#38; Grant Tables</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="The Bugzilla Database"
HREF="database.html"><LINK
REL="PREVIOUS"
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="dbdoc.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="granttables">C.3. MySQL Permissions &#38; Grant Tables</H1
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The following portion of documentation comes from my
answer to an old discussion of Keystone, a cool product that
does trouble-ticket tracking for IT departments. I wrote this
post to the Keystone support group regarding MySQL grant
table permissions, and how to use them effectively. It is
badly in need of updating, as I believe MySQL has added a
field or two to the grant tables since this time, but it
serves as a decent introduction and troubleshooting document
for grant table issues. I used Keynote to track my troubles
until I discovered Bugzilla, which gave me a whole new set of
troubles to work on : ) Although it is of limited use, it
still has SOME use, thus it's still included.</P
><P
>&#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.
</P
></TD
></TR
></TABLE
></DIV
><P
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>
Subject:&nbsp;[keystone-users]&nbsp;Grant&nbsp;Tables&nbsp;FAQ<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;[The&nbsp;following&nbsp;text&nbsp;is&nbsp;in&nbsp;the&nbsp;"iso-8859-1"&nbsp;character&nbsp;set]<br>
&nbsp;&nbsp;&nbsp;&nbsp;[Your&nbsp;display&nbsp;is&nbsp;set&nbsp;for&nbsp;the&nbsp;"US-ASCII"&nbsp;character&nbsp;set]<br>
&nbsp;&nbsp;&nbsp;&nbsp;[Some&nbsp;characters&nbsp;may&nbsp;be&nbsp;displayed&nbsp;incorrectly]<br>
<br>
Maybe&nbsp;we&nbsp;can&nbsp;include&nbsp;this&nbsp;rambling&nbsp;message&nbsp;in&nbsp;the&nbsp;Keystone&nbsp;FAQ?&nbsp;&nbsp;It&nbsp;gets<br>
asked&nbsp;a&nbsp;lot,&nbsp;and&nbsp;the&nbsp;only&nbsp;option&nbsp;current&nbsp;listed&nbsp;in&nbsp;the&nbsp;FAQ&nbsp;is<br>
"--skip-grant-tables".<br>
<br>
Really,&nbsp;you&nbsp;can't&nbsp;go&nbsp;wrong&nbsp;by&nbsp;reading&nbsp;section&nbsp;6&nbsp;of&nbsp;the&nbsp;MySQL&nbsp;manual,&nbsp;at<br>
http://www.mysql.com/Manual/manual.html.&nbsp;&nbsp;I&nbsp;am&nbsp;sure&nbsp;their&nbsp;description&nbsp;is<br>
better&nbsp;than&nbsp;mine.<br>
<br>
MySQL&nbsp;runs&nbsp;fine&nbsp;without&nbsp;permissions&nbsp;set&nbsp;up&nbsp;correctly&nbsp;if&nbsp;you&nbsp;run&nbsp;the&nbsp;mysql<br>
daemon&nbsp;with&nbsp;the&nbsp;"--skip-grant-tables"&nbsp;option.&nbsp;&nbsp;Running&nbsp;this&nbsp;way&nbsp;denies<br>
access&nbsp;to&nbsp;nobody.&nbsp;&nbsp;Unfortunately,&nbsp;unless&nbsp;you've&nbsp;got&nbsp;yourself&nbsp;firewalled&nbsp;it<br>
also&nbsp;opens&nbsp;the&nbsp;potential&nbsp;for&nbsp;abuse&nbsp;if&nbsp;someone&nbsp;knows&nbsp;you're&nbsp;running&nbsp;it.<br>
<br>
Additionally,&nbsp;the&nbsp;default&nbsp;permissions&nbsp;for&nbsp;MySQL&nbsp;allow&nbsp;anyone&nbsp;at&nbsp;localhost<br>
access&nbsp;to&nbsp;the&nbsp;database&nbsp;if&nbsp;the&nbsp;database&nbsp;name&nbsp;begins&nbsp;with&nbsp;"test_"&nbsp;or&nbsp;is&nbsp;named<br>
"test"&nbsp;(i.e.&nbsp;"test_keystone").&nbsp;&nbsp;You&nbsp;can&nbsp;change&nbsp;the&nbsp;name&nbsp;of&nbsp;your&nbsp;database&nbsp;in<br>
the&nbsp;keystone.conf&nbsp;file&nbsp;($sys_dbname).&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;way&nbsp;I&nbsp;am&nbsp;doing&nbsp;it&nbsp;for<br>
some&nbsp;of&nbsp;my&nbsp;databases,&nbsp;and&nbsp;it&nbsp;works&nbsp;fine.<br>
<br>
The&nbsp;methods&nbsp;described&nbsp;below&nbsp;assume&nbsp;you're&nbsp;running&nbsp;MySQL&nbsp;on&nbsp;the&nbsp;same&nbsp;box&nbsp;as<br>
your&nbsp;webserver,&nbsp;and&nbsp;that&nbsp;you&nbsp;don't&nbsp;mind&nbsp;if&nbsp;your&nbsp;$sys_dbuser&nbsp;for&nbsp;Keystone&nbsp;has<br>
superuser&nbsp;access.&nbsp;&nbsp;See&nbsp;near&nbsp;the&nbsp;bottom&nbsp;of&nbsp;this&nbsp;message&nbsp;for&nbsp;a&nbsp;description&nbsp;of<br>
what&nbsp;each&nbsp;field&nbsp;does.<br>
<br>
Method&nbsp;#1:<br>
<br>
1.&nbsp;&nbsp;cd&nbsp;/var/lib<br>
#location&nbsp;where&nbsp;you'll&nbsp;want&nbsp;to&nbsp;run&nbsp;/usr/bin/mysql_install_db&nbsp;shell<br>
script&nbsp;from&nbsp;to&nbsp;get&nbsp;it&nbsp;to&nbsp;work.<br>
<br>
2.&nbsp;&nbsp;ln&nbsp;-s&nbsp;mysql&nbsp;data&nbsp;&nbsp;<br>
#&nbsp;soft&nbsp;links&nbsp;the&nbsp;"mysql"&nbsp;directory&nbsp;to&nbsp;"data",&nbsp;which&nbsp;is&nbsp;what<br>
mysql_install_db&nbsp;expects.&nbsp;&nbsp;Alternately,&nbsp;you&nbsp;can&nbsp;edit&nbsp;mysql_install_db&nbsp;and<br>
change&nbsp;all&nbsp;the&nbsp;"./data"&nbsp;references&nbsp;to&nbsp;"./mysql".<br>
<br>
3.&nbsp;&nbsp;Edit&nbsp;/usr/bin/mysql_install_db&nbsp;with&nbsp;your&nbsp;favorite&nbsp;text&nbsp;editor&nbsp;(vi,<br>
emacs,&nbsp;jot,&nbsp;pico,&nbsp;etc.)<br>
A)&nbsp;&nbsp;Copy&nbsp;the&nbsp;"INSERT&nbsp;INTO&nbsp;db&nbsp;VALUES<br>
('%','test\_%','','Y','Y','Y','Y','Y','Y');"&nbsp;and&nbsp;paste&nbsp;it&nbsp;immediately&nbsp;after<br>
itself.&nbsp;&nbsp;Chage&nbsp;the&nbsp;'test\_%'&nbsp;value&nbsp;to&nbsp;'keystone',&nbsp;or&nbsp;the&nbsp;value&nbsp;of<br>
$sys_dbname&nbsp;in&nbsp;keystone.conf.<br>
B)&nbsp;&nbsp;If&nbsp;you&nbsp;are&nbsp;running&nbsp;your&nbsp;keystone&nbsp;database&nbsp;with&nbsp;any&nbsp;user,&nbsp;you'll&nbsp;need&nbsp;to<br>
copy&nbsp;the&nbsp;"INSERT&nbsp;INTO&nbsp;user&nbsp;VALUES<br>
('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');"&nbsp;line&nbsp;after<br>
itself&nbsp;and&nbsp;change&nbsp;'root'&nbsp;to&nbsp;the&nbsp;name&nbsp;of&nbsp;the&nbsp;keystone&nbsp;database&nbsp;user<br>
($sys_dbuser)&nbsp;in&nbsp;keystone.conf.<br>
<br>
#&nbsp;adds&nbsp;entries&nbsp;to&nbsp;the&nbsp;script&nbsp;to&nbsp;create&nbsp;grant&nbsp;tables&nbsp;for&nbsp;specific<br>
hosts&nbsp;and&nbsp;users.&nbsp;&nbsp;The&nbsp;user&nbsp;you&nbsp;set&nbsp;up&nbsp;has&nbsp;super-user&nbsp;access&nbsp;($sys_dbuser)&nbsp;--<br>
you&nbsp;may&nbsp;or&nbsp;may&nbsp;not&nbsp;want&nbsp;this.&nbsp;&nbsp;The&nbsp;layout&nbsp;of&nbsp;mysql_install_db&nbsp;is&nbsp;really&nbsp;very<br>
uncomplicated.<br>
<br>
4.&nbsp;&nbsp;/usr/bin/mysqladmin&nbsp;shutdown<br>
#&nbsp;ya&nbsp;gotta&nbsp;shut&nbsp;it&nbsp;down&nbsp;before&nbsp;you&nbsp;can&nbsp;reinstall&nbsp;the&nbsp;grant&nbsp;tables!<br>
<br>
5.&nbsp;&nbsp;rm&nbsp;-i&nbsp;/var/lib/mysql/mysql/*.IS?'&nbsp;and&nbsp;answer&nbsp;'Y'&nbsp;to&nbsp;the&nbsp;deletion<br>
questions.<br>
#&nbsp;nuke&nbsp;your&nbsp;current&nbsp;grant&nbsp;tables.&nbsp;&nbsp;This&nbsp;WILL&nbsp;NOT&nbsp;delete&nbsp;any&nbsp;other<br>
databases&nbsp;than&nbsp;your&nbsp;grant&nbsp;tables.<br>
<br>
6.&nbsp;&nbsp;/usr/bin/mysql_install_db<br>
#&nbsp;run&nbsp;the&nbsp;script&nbsp;you&nbsp;just&nbsp;edited&nbsp;to&nbsp;install&nbsp;your&nbsp;new&nbsp;grant&nbsp;tables.<br>
<br>
7.&nbsp;&nbsp;mysqladmin&nbsp;-u&nbsp;root&nbsp;password&nbsp;(new_password)&nbsp;&nbsp;<br>
#&nbsp;change&nbsp;the&nbsp;root&nbsp;MySQL&nbsp;password,&nbsp;or&nbsp;else&nbsp;anyone&nbsp;on&nbsp;localhost&nbsp;can<br>
login&nbsp;to&nbsp;MySQL&nbsp;as&nbsp;root&nbsp;and&nbsp;make&nbsp;changes.&nbsp;&nbsp;You&nbsp;can&nbsp;skip&nbsp;this&nbsp;step&nbsp;if&nbsp;you&nbsp;want<br>
keystone&nbsp;to&nbsp;connect&nbsp;as&nbsp;root&nbsp;with&nbsp;no&nbsp;password.<br>
<br>
8.&nbsp;&nbsp;mysqladmin&nbsp;-u&nbsp;(webserver_user_name)&nbsp;password&nbsp;(new_password)&nbsp;&nbsp;<br>
#&nbsp;change&nbsp;the&nbsp;password&nbsp;of&nbsp;the&nbsp;$sys_dbuser.&nbsp;&nbsp;Note&nbsp;that&nbsp;you&nbsp;will&nbsp;need<br>
to&nbsp;change&nbsp;the&nbsp;password&nbsp;in&nbsp;the&nbsp;keystone.conf&nbsp;file&nbsp;as&nbsp;well&nbsp;in&nbsp;$sys_dbpasswd,<br>
and&nbsp;if&nbsp;your&nbsp;permissions&nbsp;are&nbsp;set&nbsp;up&nbsp;incorrectly&nbsp;anybody&nbsp;can&nbsp;type&nbsp;the&nbsp;URL&nbsp;to<br>
your&nbsp;keystone.conf&nbsp;file&nbsp;and&nbsp;get&nbsp;the&nbsp;password.&nbsp;&nbsp;Not&nbsp;that&nbsp;this&nbsp;will&nbsp;help&nbsp;them<br>
much&nbsp;if&nbsp;your&nbsp;permissions&nbsp;are&nbsp;set&nbsp;to&nbsp;@localhost.<br>
<br>
<br>
<br>
Method&nbsp;#2:&nbsp;&nbsp;easier,&nbsp;but&nbsp;a&nbsp;pain&nbsp;reproducing&nbsp;if&nbsp;you&nbsp;have&nbsp;to&nbsp;delete&nbsp;your&nbsp;grant<br>
tables.&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;"recommended"&nbsp;method&nbsp;for&nbsp;altering&nbsp;grant&nbsp;tables&nbsp;in<br>
MySQL.&nbsp;&nbsp;I&nbsp;don't&nbsp;use&nbsp;it&nbsp;because&nbsp;I&nbsp;like&nbsp;the&nbsp;other&nbsp;way&nbsp;:)<br>
<br>
shell&#62;&nbsp;mysql&nbsp;--user=root&nbsp;keystone<br>
<br>
mysql&#62;&nbsp;GRANT<br>
SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,<br>
FILE,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ON&nbsp;keystone.*<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TO&nbsp;&#60;$sys_dbuser&nbsp;name&#62;@localhost<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IDENTIFIED&nbsp;BY&nbsp;'(password)'<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;WITH&nbsp;GRANT&nbsp;OPTION;<br>
<br>
OR<br>
<br>
mysql&#62;&nbsp;GRANT&nbsp;ALL&nbsp;PRIVILEGES&nbsp;<br>
ON&nbsp;keystone.*<br>
TO&nbsp;&#60;$sys_dbuser&nbsp;name&#62;@localhost<br>
IDENTIFIED&nbsp;BY&nbsp;'(password)'<br>
WITH&nbsp;GRANT&nbsp;OPTION;<br>
<br>
#&nbsp;this&nbsp;grants&nbsp;the&nbsp;required&nbsp;permissions&nbsp;to&nbsp;the&nbsp;keystone&nbsp;($sys_dbuser)<br>
account&nbsp;defined&nbsp;in&nbsp;keystone.conf.&nbsp;&nbsp;However,&nbsp;if&nbsp;you&nbsp;are&nbsp;runnning&nbsp;many<br>
different&nbsp;MySQL-based&nbsp;apps,&nbsp;as&nbsp;we&nbsp;are,&nbsp;it's&nbsp;generally&nbsp;better&nbsp;to&nbsp;edit&nbsp;the<br>
mysql_install_db&nbsp;script&nbsp;to&nbsp;be&nbsp;able&nbsp;to&nbsp;quickly&nbsp;reproduce&nbsp;your&nbsp;permissions<br>
structure&nbsp;again.&nbsp;&nbsp;Note&nbsp;that&nbsp;the&nbsp;FILE&nbsp;privelege&nbsp;and&nbsp;WITH&nbsp;GRANT&nbsp;OPTION&nbsp;may&nbsp;not<br>
be&nbsp;in&nbsp;your&nbsp;best&nbsp;interest&nbsp;to&nbsp;include.<br>
<br>
<br>
GRANT&nbsp;TABLE&nbsp;FIELDS&nbsp;EXPLANATION:<br>
Quick&nbsp;syntax&nbsp;summary:&nbsp;&nbsp;"%"&nbsp;in&nbsp;MySQL&nbsp;is&nbsp;a&nbsp;wildcard.&nbsp;&nbsp;I.E.,&nbsp;if&nbsp;you&nbsp;are<br>
defining&nbsp;your&nbsp;DB&nbsp;table&nbsp;and&nbsp;in&nbsp;the&nbsp;'host'&nbsp;field&nbsp;and&nbsp;enter&nbsp;'%',&nbsp;that&nbsp;means<br>
that&nbsp;any&nbsp;host&nbsp;can&nbsp;access&nbsp;that&nbsp;database.&nbsp;&nbsp;Of&nbsp;course,&nbsp;that&nbsp;host&nbsp;must&nbsp;also&nbsp;have<br>
a&nbsp;valid&nbsp;db&nbsp;user&nbsp;in&nbsp;order&nbsp;to&nbsp;do&nbsp;anything&nbsp;useful.&nbsp;&nbsp;'db'=name&nbsp;of&nbsp;database.&nbsp;&nbsp;In<br>
our&nbsp;case,&nbsp;it&nbsp;should&nbsp;be&nbsp;"keystone".&nbsp;&nbsp;"user"&nbsp;should&nbsp;be&nbsp;your&nbsp;"$sys_dbuser"<br>
defined&nbsp;in&nbsp;keystone.conf.&nbsp;&nbsp;Note&nbsp;that&nbsp;you&nbsp;CANNOT&nbsp;add&nbsp;or&nbsp;change&nbsp;a&nbsp;password&nbsp;by<br>
using&nbsp;the&nbsp;"INSERT&nbsp;INTO&nbsp;db&nbsp;(X)"&nbsp;command&nbsp;--&nbsp;you&nbsp;must&nbsp;change&nbsp;it&nbsp;with&nbsp;the&nbsp;mysql<br>
-u&nbsp;command&nbsp;as&nbsp;defined&nbsp;above.&nbsp;&nbsp;Passwords&nbsp;are&nbsp;stored&nbsp;encrypted&nbsp;in&nbsp;the&nbsp;MySQL<br>
database,&nbsp;and&nbsp;if&nbsp;you&nbsp;try&nbsp;to&nbsp;enter&nbsp;it&nbsp;directly&nbsp;into&nbsp;the&nbsp;table&nbsp;they&nbsp;will&nbsp;not<br>
match.<br>
<br>
TABLE:&nbsp;&nbsp;USER.&nbsp;&nbsp;Everything&nbsp;after&nbsp;"password"&nbsp;is&nbsp;a&nbsp;privelege&nbsp;granted&nbsp;(Y/N).<br>
This&nbsp;table&nbsp;controls&nbsp;individual&nbsp;user&nbsp;global&nbsp;access&nbsp;rights.<br>
<br>
'host','user','password','select','insert','update','delete','index','alter'<br>
,'create','drop','grant','reload','shutdown','process','file'<br>
<br>
TABLE:&nbsp;&nbsp;DB.&nbsp;&nbsp;This&nbsp;controls&nbsp;access&nbsp;of&nbsp;USERS&nbsp;to&nbsp;databases.<br>
<br>
'host','db','user','select','insert','update','delete','index','alter','crea<br>
te','drop','grant'<br>
<br>
TABLE:&nbsp;&nbsp;HOST.&nbsp;&nbsp;This&nbsp;controls&nbsp;which&nbsp;HOSTS&nbsp;are&nbsp;allowed&nbsp;what&nbsp;global&nbsp;access<br>
rights.&nbsp;&nbsp;Note&nbsp;that&nbsp;the&nbsp;HOST&nbsp;table,&nbsp;USER&nbsp;table,&nbsp;and&nbsp;DB&nbsp;table&nbsp;are&nbsp;very&nbsp;closely<br>
connected&nbsp;--&nbsp;if&nbsp;an&nbsp;authorized&nbsp;USER&nbsp;attempts&nbsp;an&nbsp;SQL&nbsp;request&nbsp;from&nbsp;an<br>
unauthorized&nbsp;HOST,&nbsp;she's&nbsp;denied.&nbsp;&nbsp;If&nbsp;a&nbsp;request&nbsp;from&nbsp;an&nbsp;authorized&nbsp;HOST&nbsp;is<br>
not&nbsp;an&nbsp;authorized&nbsp;USER,&nbsp;it&nbsp;is&nbsp;denied.&nbsp;&nbsp;If&nbsp;a&nbsp;globally&nbsp;authorized&nbsp;USER&nbsp;does<br>
not&nbsp;have&nbsp;rights&nbsp;to&nbsp;a&nbsp;certain&nbsp;DB,&nbsp;she's&nbsp;denied.&nbsp;&nbsp;Get&nbsp;the&nbsp;picture?<br>
<br>
'host','db','select','insert','update','delete','index','alter','create','dr<br>
op','grant'<br>
<br>
<br>
You&nbsp;should&nbsp;now&nbsp;have&nbsp;a&nbsp;working&nbsp;knowledge&nbsp;of&nbsp;MySQL&nbsp;grant&nbsp;tables.&nbsp;&nbsp;If&nbsp;there&nbsp;is<br>
anything&nbsp;I've&nbsp;left&nbsp;out&nbsp;of&nbsp;this&nbsp;answer&nbsp;that&nbsp;you&nbsp;feel&nbsp;is&nbsp;pertinent,&nbsp;or&nbsp;if&nbsp;my<br>
instructions&nbsp;don't&nbsp;work&nbsp;for&nbsp;you,&nbsp;please&nbsp;let&nbsp;me&nbsp;know&nbsp;and&nbsp;I'll&nbsp;re-post&nbsp;this<br>
letter&nbsp;again,&nbsp;corrected.&nbsp;&nbsp;I&nbsp;threw&nbsp;it&nbsp;together&nbsp;one&nbsp;night&nbsp;out&nbsp;of&nbsp;exasperation<br>
for&nbsp;all&nbsp;the&nbsp;newbies&nbsp;who&nbsp;don't&nbsp;know&nbsp;squat&nbsp;about&nbsp;MySQL&nbsp;yet,&nbsp;so&nbsp;it&nbsp;is&nbsp;almost<br>
guaranteed&nbsp;to&nbsp;have&nbsp;errors.<br>
<br>
Once&nbsp;again,&nbsp;you&nbsp;can't&nbsp;go&nbsp;wrong&nbsp;by&nbsp;reading&nbsp;section&nbsp;6&nbsp;of&nbsp;the&nbsp;MySQL&nbsp;manual.&nbsp;&nbsp;It<br>
is&nbsp;more&nbsp;detailed&nbsp;than&nbsp;I!<br>
http://www.mysql.com/Manual/manual.html.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="dbdoc.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="patches.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>MySQL Bugzilla Database Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="database.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

276
webtools/bugzilla/docs/html/groups.html Normal file
Просмотреть файл

@ -0,0 +1,276 @@
<HTML
><HEAD
><TITLE
>Groups and Group Security</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Voting"
HREF="voting.html"><LINK
REL="NEXT"
TITLE="Bugzilla Security"
HREF="security.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="voting.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="security.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="groups">5.5. Groups and Group Security</H1
><P
>Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
There are two types of group - Generic Groups, and Product-Based Groups.
</P
><P
>&#13; Product-Based Groups are matched with products, and allow you to restrict
access to bugs on a per-product basis. They are enabled using the
usebuggroups Param. Turning on the usebuggroupsentry
Param will mean bugs automatically get added to their product group when
filed.
</P
><P
>&#13; Generic Groups have no special relationship to products;
you create them, and put bugs in them
as required. One example of the use of Generic Groups
is Mozilla's "Security" group,
into which security-sensitive bugs are placed until fixed. Only the
Mozilla Security Team are members of this group.
</P
><P
>To create Generic Groups:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Select the "groups"
link in the footer.</P
></LI
><LI
><P
>Take a moment to understand the instructions on the "Edit
Groups" screen, then select the "Add Group" link.</P
></LI
><LI
><P
>Fill out the "New Name", "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.
When you have finished, click "Add".</P
></LI
></OL
><P
>To use Product-Based Groups:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
Parameters" screen.</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>XXX is this still true?
"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
administrative account usage to administrative duties only. In
other words, manage bugs with an unpriveleged user account, and
manage users, groups, Products, etc. with the administrative
account.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>In future, when you create a Product, a matching group will be
automatically created. If you need to add a Product Group to
a Product which was created before you turned on usebuggroups,
then simply create a new group, as outlined above, with the
same name as the Product.</P
></LI
></OL
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Bugzilla currently has a limit of 64 groups per installation. If
you have more than about 50 products, you should consider
running multiple Bugzillas. Ask in the newsgroup for other
suggestions for working around this restriction.</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Note that group permissions are such that you need to be a member
of <EM
>all</EM
> the groups a bug is in, for whatever
reason, to see that bug.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="voting.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="security.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Voting</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Bugzilla Security</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

308
webtools/bugzilla/docs/html/hintsandtips.html Normal file
Просмотреть файл

@ -0,0 +1,308 @@
<HTML
><HEAD
><TITLE
>Hints and Tips</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="How do I use Bugzilla?"
HREF="how.html"><LINK
REL="NEXT"
TITLE="User Preferences"
HREF="userpreferences.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="how.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="userpreferences.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="hintsandtips">3.2. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN434">3.2.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
However, Bugzilla will automatically make hyperlinks out of certain
sorts of text in comments. For example, the text
http://www.bugzilla.org will be turned into
<A
HREF="http://www.bugzilla.org"
TARGET="_top"
>http://www.bugzilla.org</A
>.
Other strings which get linkified in the obvious manner are:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>bug 12345</TD
></TR
><TR
><TD
>bug 23456, comment 53</TD
></TR
><TR
><TD
>attachment 4321</TD
></TR
><TR
><TD
>mailto:george@example.com</TD
></TR
><TR
><TD
>george@example.com</TD
></TR
><TR
><TD
>ftp://ftp.mozilla.org</TD
></TR
><TR
><TD
>Most other sorts of URL</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
>A corollary here is that if you type a bug number in a comment,
you should put the word "bug" before it, so it gets autolinkified
for the convenience of others.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="quicksearch">3.2.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
"<TT
CLASS="filename"
>foo|bar</TT
>"
into Quicksearch would search for "foo" or "bar" in the
summary and status whiteboard of a bug; adding
"<TT
CLASS="filename"
>:BazProduct</TT
>" would
search only in that product.
</P
><P
>You'll find the Quicksearch box on Bugzilla's
front page, along with a
<A
HREF="../../quicksearch.html"
TARGET="_top"
>Help</A
>
link which details how to use it.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="commenting">3.2.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
Otherwise, you may spam people unnecessarily with bug mail.
To take an example: a user can set up their account to filter out messages
where someone just adds themselves to the CC field of a bug
(which happens a lot.) If you come along, add yourself to the CC field,
and add a comment saying "Adding self to CC", then that person
gets a pointless piece of mail they would otherwise have avoided.
</P
><P
>&#13; Don't use sigs in comments. Signing your name ("Bill") is acceptable,
particularly if you do it out of habit, but full mail/news-style
four line ASCII art creations are not.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="attachments">3.2.4. Attachments</H2
><P
>&#13; Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
bloat the bug for everyone who wants to read it, and cause people to
receive fat, useless mails.
</P
><P
>Trim screenshots. There's no need to show the whole screen if
you are pointing out a single-pixel problem.
</P
><P
>Don't attach simple test cases (e.g. one HTML file, one
CSS file and an image) as a ZIP file. Instead, upload them in
reverse order and edit the referring file so that they point to the
attached files. This way, the test case works immediately
out of the bug.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN463">3.2.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="how.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="userpreferences.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How do I use Bugzilla?</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>User Preferences</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

787
webtools/bugzilla/docs/html/how.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

411
webtools/bugzilla/docs/html/index.html
Просмотреть файл

@ -47,32 +47,33 @@ NAME="AEN2">The Bugzilla Guide</H1
CLASS="author"
><A
NAME="AEN5">Matthew P. Barnson</H3
><DIV
CLASS="affiliation"
><DIV
CLASS="address"
><P
CLASS="address"
>mbarnson@sisna.com</P
></DIV
></DIV
><H3
CLASS="author"
><A
NAME="AEN9">The Bugzilla Team</H3
><DIV
><DIV
CLASS="abstract"
><A
NAME="AEN12"><P
NAME="AEN13"><P
></P
><P
>&#13; This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
>&#13; This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
</P
><P
>&#13; This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a Bugzilla bug.
>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a bug filed in
<A
HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"
TARGET="_top"
>mozilla.org's Bugzilla</A
>.
</P
><P
></P
@ -95,36 +96,26 @@ HREF="about.html"
><DL
><DT
>1.1. <A
HREF="aboutthisguide.html"
>Purpose and Scope of this Guide</A
></DT
><DT
>1.2. <A
HREF="copyright.html"
>Copyright Information</A
></DT
><DT
>1.3. <A
>1.2. <A
HREF="disclaimer.html"
>Disclaimer</A
></DT
><DT
>1.4. <A
>1.3. <A
HREF="newversions.html"
>New Versions</A
></DT
><DT
>1.5. <A
>1.4. <A
HREF="credits.html"
>Credits</A
></DT
><DT
>1.6. <A
HREF="translations.html"
>Translations</A
></DT
><DT
>1.7. <A
>1.5. <A
HREF="conventions.html"
>Document Conventions</A
></DT
@ -132,8 +123,8 @@ HREF="conventions.html"
></DD
><DT
>2. <A
HREF="using.html"
>Using Bugzilla</A
HREF="introduction.html"
>Introduction</A
></DT
><DD
><DL
@ -147,157 +138,117 @@ HREF="whatis.html"
HREF="why.html"
>Why Should We Use Bugzilla?</A
></DT
><DT
>2.3. <A
HREF="how.html"
>How do I use Bugzilla?</A
></DT
><DT
>2.4. <A
HREF="init4me.html"
>Where can I find my user preferences?</A
></DT
><DT
>2.5. <A
HREF="usingbz-conc.html"
>Using Bugzilla-Conclusion</A
></DT
></DL
></DD
><DT
>3. <A
HREF="using.html"
>Using Bugzilla</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="how.html"
>How do I use Bugzilla?</A
></DT
><DT
>3.2. <A
HREF="hintsandtips.html"
>Hints and Tips</A
></DT
><DT
>3.3. <A
HREF="userpreferences.html"
>User Preferences</A
></DT
></DL
></DD
><DT
>4. <A
HREF="installation.html"
>Installation</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="errata.html"
>ERRATA</A
></DT
><DT
>3.2. <A
>4.1. <A
HREF="stepbystep.html"
>Step-by-step Install</A
></DT
><DT
>3.3. <A
>4.2. <A
HREF="extraconfig.html"
>Optional Additional Configuration</A
></DT
><DT
>4.3. <A
HREF="win32.html"
>Win32 Installation Notes</A
></DT
><DT
>4.4. <A
HREF="osx.html"
>Mac OS X Installation Notes</A
></DT
><DT
>3.4. <A
HREF="bsdinstall.html"
>BSD Installation Notes</A
></DT
><DT
>3.5. <A
HREF="geninstall.html"
>Installation General Notes</A
></DT
><DT
>3.6. <A
HREF="win32.html"
>Win32 Installation Notes</A
>4.5. <A
HREF="troubleshooting.html"
>Troubleshooting</A
></DT
></DL
></DD
><DT
>4. <A
>5. <A
HREF="administration.html"
>Administering Bugzilla</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="postinstall-check.html"
>Post-Installation Checklist</A
>5.1. <A
HREF="parameters.html"
>Bugzilla Configuration</A
></DT
><DT
>4.2. <A
>5.2. <A
HREF="useradmin.html"
>User Administration</A
></DT
><DT
>4.3. <A
HREF="programadmin.html"
>Product, Component, Milestone, and Version
Administration</A
></DT
><DT
>4.4. <A
HREF="security.html"
>Bugzilla Security</A
></DT
></DL
></DD
><DT
>5. <A
HREF="integration.html"
>Integrating Bugzilla with Third-Party Tools</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="bonsai.html"
>Bonsai</A
></DT
><DT
>5.2. <A
HREF="cvs.html"
>CVS</A
></DT
><DT
>5.3. <A
HREF="scm.html"
>Perforce SCM</A
HREF="programadmin.html"
>Product, Component, Milestone, and Version Administration</A
></DT
><DT
>5.4. <A
HREF="tinderbox.html"
>Tinderbox/Tinderbox2</A
></DT
></DL
></DD
><DT
>6. <A
HREF="variants.html"
>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
HREF="voting.html"
>Voting</A
></DT
><DT
>6.2. <A
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
>5.5. <A
HREF="groups.html"
>Groups and Group Security</A
></DT
><DT
>6.3. <A
HREF="variant-issuezilla.html"
>Issuezilla</A
>5.6. <A
HREF="security.html"
>Bugzilla Security</A
></DT
><DT
>6.4. <A
HREF="variant-scarab.html"
>Scarab</A
>5.7. <A
HREF="cust-templates.html"
>Template Customisation</A
></DT
><DT
>6.5. <A
HREF="variant-perforce.html"
>Perforce SCM</A
>5.8. <A
HREF="upgrading.html"
>Upgrading to New Releases</A
></DT
><DT
>6.6. <A
HREF="variant-sourceforge.html"
>SourceForge</A
>5.9. <A
HREF="integration.html"
>Integrating Bugzilla with Third-Party Tools</A
></DT
></DL
></DD
@ -308,136 +259,84 @@ HREF="faq.html"
></DT
><DT
>B. <A
HREF="downloadlinks.html"
>Software Download Links</A
></DT
><DT
>C. <A
HREF="database.html"
>The Bugzilla Database</A
></DT
><DD
><DL
><DT
>C.1. <A
>B.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
></DT
><DT
>C.2. <A
>B.2. <A
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
><DT
>C.3. <A
HREF="granttables.html"
>MySQL Permissions &#38; Grant Tables</A
></DT
></DL
></DD
><DT
>D. <A
>C. <A
HREF="patches.html"
>Useful Patches and Utilities for Bugzilla</A
></DT
><DD
><DL
><DT
>D.1. <A
>C.1. <A
HREF="rewrite.html"
>Apache <TT
>Apache
<TT
CLASS="filename"
>mod_rewrite</TT
> magic</A
>
magic</A
></DT
><DT
>D.2. <A
HREF="setperl.html"
>The setperl.csh Utility</A
></DT
><DT
>D.3. <A
>C.2. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>D.4. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
><DT
>D.5. <A
HREF="bzhacking.html"
>Hacking Bugzilla</A
></DT
></DL
></DD
><DT
>E. <A
HREF="gfdl.html"
>GNU Free Documentation License</A
>D. <A
HREF="variants.html"
>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
><DT
>0. <A
HREF="gfdl-0.html"
>PREAMBLE</A
>D.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
>1. <A
HREF="gfdl-1.html"
>APPLICABILITY AND DEFINITIONS</A
>D.2. <A
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>2. <A
HREF="gfdl-2.html"
>VERBATIM COPYING</A
>D.3. <A
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>3. <A
HREF="gfdl-3.html"
>COPYING IN QUANTITY</A
>D.4. <A
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>4. <A
HREF="gfdl-4.html"
>MODIFICATIONS</A
>D.5. <A
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>5. <A
HREF="gfdl-5.html"
>COMBINING DOCUMENTS</A
></DT
><DT
>6. <A
HREF="gfdl-6.html"
>COLLECTIONS OF DOCUMENTS</A
></DT
><DT
>7. <A
HREF="gfdl-7.html"
>AGGREGATION WITH INDEPENDENT WORKS</A
></DT
><DT
>8. <A
HREF="gfdl-8.html"
>TRANSLATION</A
></DT
><DT
>9. <A
HREF="gfdl-9.html"
>TERMINATION</A
></DT
><DT
>10. <A
HREF="gfdl-10.html"
>FUTURE REVISIONS OF THIS LICENSE</A
></DT
><DT
><A
HREF="gfdl-howto.html"
>How to use this License for your documents</A
>D.6. <A
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
></DL
></DD
@ -457,76 +356,22 @@ CLASS="LOT"
>List of Examples</B
></DT
><DT
>3-1. <A
HREF="stepbystep.html#AEN641"
>Setting up bonsaitools symlink</A
></DT
><DT
>3-2. <A
HREF="stepbystep.html#AEN732"
>Running checksetup.pl as the web user</A
></DT
><DT
>3-3. <A
HREF="win32.html#AEN985"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
HREF="win32.html#AEN998"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>3-5. <A
HREF="win32.html#AEN1180"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
HREF="programadmin.html#AEN1405"
>Creating some Components</A
HREF="win32.html#AEN989"
>Installing ActivePerl ppd Modules on Microsoft
Windows</A
></DT
><DT
>4-2. <A
HREF="programadmin.html#AEN1434"
>Common Use of Versions</A
HREF="win32.html#AEN1002"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>4-3. <A
HREF="programadmin.html#AEN1438"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
HREF="programadmin.html#AEN1466"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
HREF="programadmin.html#AEN1502"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
HREF="programadmin.html#AEN1519"
>Creating a New Group</A
></DT
><DT
>4-7. <A
HREF="programadmin.html#AEN1536"
>Bugzilla Groups</A
></DT
><DT
>D-1. <A
HREF="setperl.html#AEN2380"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
HREF="glossary.html#AEN2701"
>A Sample Product</A
HREF="win32.html#AEN1184"
>Removing encrypt() for Windows NT Bugzilla version 2.12 or
earlier</A
></DT
></DL
></DIV

451
webtools/bugzilla/docs/html/init4me.html
Просмотреть файл

@ -1,451 +0,0 @@
<HTML
><HEAD
><TITLE
>Where can I find my user preferences?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="How do I use Bugzilla?"
HREF="how.html"><LINK
REL="NEXT"
TITLE="Using Bugzilla-Conclusion"
HREF="usingbz-conc.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="how.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="usingbz-conc.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="init4me">2.4. Where can I find my user preferences?</H1
><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
CELLPADDING="0"
CLASS="EPIGRAPH"
><TR
><TD
WIDTH="45%"
>&nbsp;</TD
><TD
WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
><I
><P
><I
>Indiana, it feels like we walking on fortune cookies!</I
></P
><P
><I
>These ain't fortune cookies, kid...</I
></P
></I
></TD
></TR
></TABLE
><P
>&#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
HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"
TARGET="_top"
> Landfill</A
>.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="accountsettings">2.4.1. Account Settings</H2
><P
>&#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
>current</EM
> password into the <SPAN
CLASS="QUOTE"
>"Old
Password"</SPAN
> field. If you wish to change your
password, type the new password you want into the <SPAN
CLASS="QUOTE"
>"New
Password"</SPAN
> field and again into the <SPAN
CLASS="QUOTE"
>"Re-enter
new password"</SPAN
> field to ensure you typed your new
password correctly. Select the <SPAN
CLASS="QUOTE"
>"Submit"</SPAN
> button
and you are done.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="emailsettings">2.4.2. Email Settings</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="notification">2.4.2.1. Email Notification</H3
><P
>&#13; Here you can reduce or increase the amount of email sent you
from Bugzilla. Although this is referred to as
<SPAN
CLASS="QUOTE"
>"Advanced Email Filtering Options"</SPAN
>, they are,
in fact, the standard email filter set. All of them are
self-explanatory, but you can use the filters in interesting
ways. For instance, some people (notably Quality Assurance
personnel) often only care to receive updates regarding a
bug when the bug changes state, so they can track bugs on
their flow charts and know when it is time to pull the bug
onto a quality assurance platform for inspection. Other
people set up email gateways to
<A
HREF="bonsai.html"
>Bonsai, the Mozilla automated CVS management system</A
> or <A
HREF="tinderbox.html"
>Tinderbox, the Mozilla automated build management system</A
>, and
restrict which types of Bugzilla information are fed to
these systems..
</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="newemailtech">2.4.2.2. New Email Technology</H3
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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,
ask her to "enable newemailtech in Params" and "make it
the default for all new users", referring her to the
Administration section of this Guide.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#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
>&#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
prettier, better laid-out email.
</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="watchsettings">2.4.2.3. "Watching" Users</H3
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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,
ask her to "enable watchers in Params".
</P
></TD
></TR
></TABLE
></DIV
><P
>&#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
get in touch with the issues faced by their direct reports,
or users go on vacation. If any of these three situations
apply to you, you will undoubtedly find this feature quite
convenient.
</P
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="footersettings">2.4.3. Page Footer</H2
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
page of Preferences, if you have many stored queries you can
elect to have them always one-click away!
</P
></TD
></TR
></TABLE
></DIV
><P
>&#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
one-click access to any complex searches you may set up, and
is an excellent way to impress your boss...
</P
><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
>By default, the "My Bugs" link appears at the bottom of
each page. However, this query gives you both the bugs you
have reported, as well as those you are assigned. One of
the most common uses for this page is to remove the "My
Bugs" link, replacing it with two other queries, commonly
called "My Bug Reports" and "My Bugs" (but only referencing
bugs assigned to you). This allows you to distinguish those
bugs you have reported from those you are assigned. I
commonly set up complex Boolean queries in the Query page
and link them to my footer in this page. When they are
significantly complex, a one-click reference can save hours
of work.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="permissionsettings">2.4.4. Permissions</H2
><P
>&#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.
For more information regarding user administration, please
consult the Administration section of this Guide.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="how.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="usingbz-conc.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How do I use Bugzilla?</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using Bugzilla-Conclusion</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

241
webtools/bugzilla/docs/html/installation.html
Просмотреть файл

@ -10,11 +10,11 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Using Bugzilla-Conclusion"
HREF="usingbz-conc.html"><LINK
TITLE="User Preferences"
HREF="userpreferences.html"><LINK
REL="NEXT"
TITLE="ERRATA"
HREF="errata.html"></HEAD
TITLE="Step-by-step Install"
HREF="stepbystep.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="usingbz-conc.html"
HREF="userpreferences.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="errata.html"
HREF="stepbystep.html"
ACCESSKEY="N"
>Next</A
></TD
@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="installation">Chapter 3. Installation</H1
NAME="installation">Chapter 4. Installation</H1
><DIV
CLASS="TOC"
><DL
@ -78,205 +78,176 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>3.1. <A
HREF="errata.html"
>ERRATA</A
></DT
><DT
>3.2. <A
>4.1. <A
HREF="stepbystep.html"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
>3.2.1. <A
HREF="stepbystep.html#AEN441"
>4.1.1. <A
HREF="stepbystep.html#AEN492"
>Introduction</A
></DT
><DT
>3.2.2. <A
HREF="stepbystep.html#AEN447"
>Installing the Prerequisites</A
>4.1.2. <A
HREF="stepbystep.html#AEN496"
>Package List</A
></DT
><DT
>3.2.3. <A
>4.1.3. <A
HREF="stepbystep.html#install-mysql"
>Installing MySQL Database</A
>MySQL</A
></DT
><DT
>3.2.4. <A
>4.1.4. <A
HREF="stepbystep.html#install-perl"
>Perl (5.004 or greater)</A
>Perl</A
></DT
><DT
>3.2.5. <A
HREF="stepbystep.html#AEN534"
>DBI Perl Module</A
>4.1.5. <A
HREF="stepbystep.html#perl-modules"
>Perl Modules</A
></DT
><DT
>3.2.6. <A
HREF="stepbystep.html#AEN572"
>Data::Dumper Perl Module</A
></DT
><DT
>3.2.7. <A
HREF="stepbystep.html#AEN577"
>MySQL related Perl Module Collection</A
></DT
><DT
>3.2.8. <A
HREF="stepbystep.html#AEN586"
>TimeDate Perl Module Collection</A
></DT
><DT
>3.2.9. <A
HREF="stepbystep.html#AEN590"
>GD Perl Module (1.8.3)</A
></DT
><DT
>3.2.10. <A
HREF="stepbystep.html#AEN599"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>3.2.11. <A
HREF="stepbystep.html#AEN603"
>DB_File Perl Module</A
></DT
><DT
>3.2.12. <A
HREF="stepbystep.html#AEN606"
>4.1.6. <A
HREF="stepbystep.html#AEN669"
>HTTP Server</A
></DT
><DT
>3.2.13. <A
HREF="stepbystep.html#AEN625"
>Installing the Bugzilla Files</A
>4.1.7. <A
HREF="stepbystep.html#AEN688"
>Bugzilla</A
></DT
><DT
>3.2.14. <A
HREF="stepbystep.html#AEN654"
>4.1.8. <A
HREF="stepbystep.html#AEN705"
>Setting Up the MySQL Database</A
></DT
><DT
>3.2.15. <A
HREF="stepbystep.html#AEN701"
>Tweaking <TT
>4.1.9. <A
HREF="stepbystep.html#AEN741"
><TT
CLASS="filename"
>localconfig</TT
>checksetup.pl</TT
></A
></DT
><DT
>3.2.16. <A
HREF="stepbystep.html#AEN739"
>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
>3.2.17. <A
HREF="stepbystep.html#AEN750"
>The Whining Cron (Optional)</A
></DT
><DT
>3.2.18. <A
HREF="stepbystep.html#AEN760"
>Bug Graphs (Optional)</A
></DT
><DT
>3.2.19. <A
HREF="stepbystep.html#AEN772"
>4.1.10. <A
HREF="stepbystep.html#AEN773"
>Securing MySQL</A
></DT
><DT
>4.1.11. <A
HREF="stepbystep.html#AEN839"
>Configuring Bugzilla</A
></DT
></DL
></DD
><DT
>3.3. <A
HREF="osx.html"
>Mac OS X Installation Notes</A
></DT
><DT
>3.4. <A
HREF="bsdinstall.html"
>BSD Installation Notes</A
></DT
><DT
>3.5. <A
HREF="geninstall.html"
>Installation General Notes</A
>4.2. <A
HREF="extraconfig.html"
>Optional Additional Configuration</A
></DT
><DD
><DL
><DT
>3.5.1. <A
HREF="geninstall.html#AEN874"
>Modifying Your Running System</A
>4.2.1. <A
HREF="extraconfig.html#AEN845"
>Dependency Charts</A
></DT
><DT
>3.5.2. <A
HREF="geninstall.html#AEN881"
>Upgrading From Previous Versions</A
>4.2.2. <A
HREF="extraconfig.html#AEN860"
>Bug Graphs</A
></DT
><DT
>3.5.3. <A
HREF="geninstall.html#htaccess"
>4.2.3. <A
HREF="extraconfig.html#AEN873"
>The Whining Cron</A
></DT
><DT
>4.2.4. <A
HREF="extraconfig.html#bzldap"
>LDAP Authentication</A
></DT
><DT
>4.2.5. <A
HREF="extraconfig.html#content-type"
>Preventing untrusted Bugzilla content from executing malicious
Javascript code</A
></DT
><DT
>4.2.6. <A
HREF="extraconfig.html#htaccess"
><TT
CLASS="filename"
>.htaccess</TT
> files and security</A
>
files and security</A
></DT
><DT
>3.5.4. <A
HREF="geninstall.html#mod-throttle"
>4.2.7. <A
HREF="extraconfig.html#mod-throttle"
><TT
CLASS="filename"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
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"
>UNIX Installation Instructions History</A
>
and Security</A
></DT
></DL
></DD
><DT
>3.6. <A
>4.3. <A
HREF="win32.html"
>Win32 Installation Notes</A
></DT
><DD
><DL
><DT
>3.6.1. <A
>4.3.1. <A
HREF="win32.html#wininstall"
>Win32 Installation: Step-by-step</A
></DT
><DT
>3.6.2. <A
>4.3.2. <A
HREF="win32.html#addlwintips"
>Additional Windows Tips</A
></DT
></DL
></DD
><DT
>3.6.3. <A
HREF="win32.html#bzldap"
>Bugzilla LDAP Integration</A
>4.4. <A
HREF="osx.html"
>Mac OS X Installation Notes</A
></DT
><DT
>4.5. <A
HREF="troubleshooting.html"
>Troubleshooting</A
></DT
><DD
><DL
><DT
>4.5.1. <A
HREF="troubleshooting.html#AEN1218"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.5.2. <A
HREF="troubleshooting.html#AEN1223"
>DBD::Sponge::db prepare failed</A
></DT
><DT
>4.5.3. <A
HREF="troubleshooting.html#paranoid-security"
>cannot chdir(/var/spool/mqueue)</A
></DT
></DL
></DD
></DL
></DIV
><P
>&#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
this installation guide for notes on how to be successful.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -294,7 +265,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="usingbz-conc.html"
HREF="userpreferences.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -312,7 +283,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="errata.html"
HREF="stepbystep.html"
ACCESSKEY="N"
>Next</A
></TD
@ -322,7 +293,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using Bugzilla-Conclusion</TD
>User Preferences</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -332,7 +303,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>ERRATA</TD
>Step-by-step Install</TD
></TR
></TABLE
></DIV

165
webtools/bugzilla/docs/html/integration.html
Просмотреть файл

@ -9,14 +9,17 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Security"
HREF="security.html"><LINK
TITLE="Upgrading to New Releases"
HREF="upgrading.html"><LINK
REL="NEXT"
TITLE="Bonsai"
HREF="bonsai.html"></HEAD
TITLE="The Bugzilla FAQ"
HREF="faq.html"></HEAD
><BODY
CLASS="chapter"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="security.html"
HREF="upgrading.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -50,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="bonsai.html"
HREF="faq.html"
ACCESSKEY="N"
>Next</A
></TD
@ -66,38 +69,112 @@ ACCESSKEY="N"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
CLASS="section"
><H1
CLASS="section"
><A
NAME="integration">Chapter 5. Integrating Bugzilla with Third-Party Tools</H1
NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>5.1. <A
HREF="bonsai.html"
>Bonsai</A
></DT
><DT
>5.2. <A
HREF="cvs.html"
>CVS</A
></DT
><DT
>5.3. <A
HREF="scm.html"
>Perforce SCM</A
></DT
><DT
>5.4. <A
HREF="tinderbox.html"
>Tinderbox/Tinderbox2</A
></DT
></DL
CLASS="section"
><H2
CLASS="section"
><A
NAME="bonsai">5.9.1. Bonsai</H2
><P
>Bonsai is a web-based tool for managing
<A
HREF="integration.html#cvs"
>CVS, the Concurrent Versioning System</A
>
. Using Bonsai, administrators can control open/closed status of trees,
query a fast relational database back-end for change, branch, and comment
information, and view changes made since the last time the tree was
closed. Bonsai
also integrates with
<A
HREF="integration.html#tinderbox"
>Tinderbox, the Mozilla automated build management system</A
>.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="cvs">5.9.2. CVS</H2
><P
>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway.</P
><P
>Follow the instructions in this Guide 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"
>"[Bug XXXX]"</SPAN
>,
and you can have CVS check-in comments append to your Bugzilla bug. If
you have your check-in script include an @resolution field, you can even
change the Bugzilla bug state.</P
><P
>There is also a CVSZilla 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"
>&#13; http://homepages.kcbbs.gen.nz/~tonyg/</A
>.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="scm">5.9.3. Perforce SCM</H2
><P
>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
<A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
>&#13; http://www.ravenbrook.com/project/p4dti</A
>
.
<SPAN
CLASS="QUOTE"
>"p4dti"</SPAN
>
is now an officially supported product from Perforce, and you can find
the "Perforce Public Depot" p4dti page at
<A
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
TARGET="_top"
>&#13; http://public.perforce.com/public/perforce/p4dti/index.html</A
>
.</P
><P
>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 designed to support
multiple defect trackers, and maintains its own documentation for it.
Please consult the pages linked above for further information.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
><P
>We need Tinderbox integration information.</P
></DIV
></DIV
><DIV
@ -116,7 +193,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="security.html"
HREF="upgrading.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -134,7 +211,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="bonsai.html"
HREF="faq.html"
ACCESSKEY="N"
>Next</A
></TD
@ -144,17 +221,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Security</TD
>Upgrading to New Releases</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Bonsai</TD
>The Bugzilla FAQ</TD
></TR
></TABLE
></DIV

61
webtools/bugzilla/docs/html/tinderbox.html → webtools/bugzilla/docs/html/introduction.html
Просмотреть файл

@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
>Tinderbox/Tinderbox2</TITLE
>Introduction</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
@ -9,17 +9,14 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"><LINK
REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="scm.html"><LINK
TITLE="Document Conventions"
HREF="conventions.html"><LINK
REL="NEXT"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD
TITLE="What is Bugzilla?"
HREF="whatis.html"></HEAD
><BODY
CLASS="section"
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -45,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="scm.html"
HREF="conventions.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -53,13 +50,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variants.html"
HREF="whatis.html"
ACCESSKEY="N"
>Next</A
></TD
@ -69,13 +66,29 @@ ACCESSKEY="N"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
CLASS="chapter"
><H1
CLASS="section"
><A
NAME="tinderbox">5.4. Tinderbox/Tinderbox2</H1
><P
>We need Tinderbox integration information.</P
NAME="introduction">Chapter 2. Introduction</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>2.1. <A
HREF="whatis.html"
>What is Bugzilla?</A
></DT
><DT
>2.2. <A
HREF="why.html"
>Why Should We Use Bugzilla?</A
></DT
></DL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
@ -93,7 +106,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="scm.html"
HREF="conventions.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -111,7 +124,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variants.html"
HREF="whatis.html"
ACCESSKEY="N"
>Next</A
></TD
@ -121,21 +134,17 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Perforce SCM</TD
>Document Conventions</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="integration.html"
ACCESSKEY="U"
>Up</A
></TD
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Bugzilla Variants and Competitors</TD
>What is Bugzilla?</TD
></TR
></TABLE
></DIV

25
webtools/bugzilla/docs/html/newversions.html
Просмотреть файл

@ -73,9 +73,10 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="newversions">1.4. New Versions</H1
NAME="newversions">1.3. New Versions</H1
><P
>&#13; This is the 2.16 version of The Bugzilla Guide. If you are
>&#13; This is the 2.16 version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. 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.
@ -110,15 +111,27 @@ TARGET="_top"
>
</P
><P
>&#13; The latest version of this document can be checked out via CVS.
Please follow the instructions available at <A
>&#13; The latest version of this document can always be checked out via CVS.
Please follow the instructions available at
<A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>the Mozilla CVS page</A
>, and check out the <TT
>,
and check out the <TT
CLASS="filename"
>mozilla/webtools/bugzilla/docs/</TT
> branch.
>
subtree.
</P
><P
>&#13; The Bugzilla Guide is currently only available in English.
If you would like to volunteer to translate it, please contact
<A
HREF="mailto:justdave@syndicomm.com"
TARGET="_top"
>Dave Miller</A
>.
</P
></DIV
><DIV

190
webtools/bugzilla/docs/html/osx.html
Просмотреть файл

@ -13,11 +13,11 @@ REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Step-by-step Install"
HREF="stepbystep.html"><LINK
TITLE="Win32 Installation Notes"
HREF="win32.html"><LINK
REL="NEXT"
TITLE="BSD Installation Notes"
HREF="bsdinstall.html"></HEAD
TITLE="Troubleshooting"
HREF="troubleshooting.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="stepbystep.html"
HREF="win32.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -53,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Installation</TD
>Chapter 4. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="bsdinstall.html"
HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,151 +73,116 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="osx">3.3. Mac OS X Installation Notes</H1
NAME="osx">4.4. Mac OS X Installation Notes</H1
><P
>&#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
>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
>&#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
>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
>&#13; Follow the instructions for setting up Fink. Once it's
installed, you'll want to run the following as root:
<B
>Follow the instructions for setting up Fink. Once it's installed,
you'll want to run the following as root:
<B
CLASS="command"
>fink install gd</B
>
</P
><P
>&#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
>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
>&#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
/sw/lib and /sw/include instead of /usr/lib and
/usr/local/include. Because of these changed locations for
the libraries, the Perl GD module will not install directly
via CPAN (it looks for the specific paths instead of getting
them from your environment). But there's a way around that
:-)
</P
>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 /sw/lib and /sw/include instead of /usr/lib
and /usr/local/include. Because of these changed locations for the
libraries, the Perl GD module will not install directly via CPAN, because it
looks for the specific paths instead of getting them from your
environment. But there's a way around that :-)</P
><P
>&#13; Instead of typing <SPAN
>Instead of typing
<SPAN
CLASS="QUOTE"
>"install GD"</SPAN
> at the
<TT
>
at the
<TT
CLASS="prompt"
>cpan&#62;</TT
> prompt, type <B
CLASS="command"
>look
GD</B
>. This should go through the motions of
downloading the latest version of the GD module, then it will
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"
>patch &#60;
patchfile</B
>:
</P
><P
>&#13; <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
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 @@
warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n";
# =====&#62; PATHS: CHECK AND ADJUST &#60;=====
-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd);
-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib );
+my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd);
+my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib);
my @LIBS = qw(-lgd -lpng -lz);
# FEATURE FLAGS
@@ -23,7 +23,7 @@
push @LIBS,'-lttf' if $TTF;
push @LIBS,'-ljpeg' if $JPEG;
-push @LIBS, '-lm' unless $^O eq 'MSWin32';
+push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/);
# FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified
if ($^O ne 'freebsd' &#38;&#38; $^O ne 'MSWin32') {
</PRE
></FONT
></TD
></TR
></TABLE
>
prompt, type
<B
CLASS="command"
>look GD</B
>.
This should go through the motions of downloading the latest version of
the GD module, then it will open a shell and drop you into the build
directory. Apply <A
HREF="../sgml/gd-makefile.patch"
TARGET="_top"
>this patch</A
>
to the Makefile.PL file (save the
patch into a file and use the command
<B
CLASS="command"
>patch &#60; patchfile</B
>.)
</P
><P
>&#13; Then, run these commands to finish the installation of the perl module:
<P
>Then, run these commands to finish the installation of the GD
module:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
><B
>&#13; <B
CLASS="command"
>perl Makefile.PL</B
></TD
>
</TD
></TR
><TR
><TD
><B
>&#13; <B
CLASS="command"
>make</B
></TD
>
</TD
></TR
><TR
><TD
><B
>&#13; <B
CLASS="command"
>make test</B
></TD
>
</TD
></TR
><TR
><TD
><B
>&#13; <B
CLASS="command"
>make install</B
></TD
>
</TD
></TR
><TR
><TD
>And don't forget to run <B
>And don't forget to run
<B
CLASS="command"
>exit</B
> to get back to cpan.</TD
>
to get back to CPAN.</TD
></TR
></TBODY
></TABLE
@ -225,9 +190,6 @@ CLASS="command"
></P
>
</P
><P
>&#13; Happy Hacking!
</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -245,7 +207,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="stepbystep.html"
HREF="win32.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -263,7 +225,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="bsdinstall.html"
HREF="troubleshooting.html"
ACCESSKEY="N"
>Next</A
></TD
@ -273,7 +235,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Step-by-step Install</TD
>Win32 Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -287,7 +249,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>BSD Installation Notes</TD
>Troubleshooting</TD
></TR
></TABLE
></DIV

435
webtools/bugzilla/docs/html/parameters.html Normal file
Просмотреть файл

@ -0,0 +1,435 @@
<HTML
><HEAD
><TITLE
>Bugzilla Configuration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="NEXT"
TITLE="User Administration"
HREF="useradmin.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="administration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="useradmin.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="parameters">5.1. Bugzilla Configuration</H1
><P
>Bugzilla is configured by changing various parameters, accessed
from the "Edit parameters" link in the page footer. Here are
some of the key parameters on that page. You should run down this
list and set them appropriately after installing Bugzilla.</P
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
>
<B
CLASS="command"
>maintainer</B
>:
The maintainer parameter is the email address of the person
responsible for maintaining this
Bugzilla installation. The address need not be that of a valid Bugzilla
account.</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>urlbase</B
>:
This parameter defines the fully qualified domain name and web
server path to your Bugzilla installation.</P
><P
>For example, if your Bugzilla query page is
<TT
CLASS="filename"
>http://www.foo.com/bugzilla/query.cgi</TT
>,
set your <SPAN
CLASS="QUOTE"
>"urlbase"</SPAN
>
to <TT
CLASS="filename"
>http://www.foo.com/bugzilla/</TT
>.</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>usebuggroups</B
>:
This dictates whether or not to implement group-based security for
Bugzilla. If set, Bugzilla bugs can have an associated 'group',
defining which users are allowed to see and edit the
bug.</P
><P
>Set "usebuggroups" to "on"
<EM
>only</EM
>
if you may wish to restrict access to particular bugs to certain
groups of users. I suggest leaving
this parameter <EM
>off</EM
>
while initially testing your Bugzilla.</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>usebuggroupsentry</B
>:
Bugzilla Products can have a group associated with them, so that
certain users can only see bugs in certain products. When this parameter
is set to <SPAN
CLASS="QUOTE"
>"on"</SPAN
>, this places all newly-created bugs in the
group for their product immediately.</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>shadowdb</B
>:
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 entire table until the operation
is complete. Locking for write also blocks reads until the write is
complete. The
<SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
>
parameter was designed to get around this limitation. While only a
single user is allowed to write to a table at a time, reads can
continue unimpeded on a read-only shadow copy of the database.
Although your database size will double, a shadow database can cause
an enormous performance improvement when implemented on extremely
high-traffic Bugzilla databases.</P
><P
>&#13; As a guide, mozilla.org began needing
<SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
>
when they reached around 40,000 Bugzilla users with several hundred
Bugzilla bug changes and comments per day.</P
><P
>The value of the parameter defines the name of the
shadow bug database.
Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla.
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>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
<SPAN
CLASS="QUOTE"
>"cron"</SPAN
>.
</P
></TD
></TR
></TABLE
></DIV
>
</P
><P
>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!</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>shutdownhtml</B
>:
If you need to shut down Bugzilla to perform administration, enter
some descriptive HTML here and anyone who tries to use Bugzilla will
receive a page to that effect. Obviously, editparams.cgi will
still be accessible so you can remove the HTML and re-enable Bugzilla.
:-)
</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>passwordmail</B
>:
Every time a user creates an account, the text of
this parameter (with substitutions) is sent to the new user along with
their password message.</P
><P
>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
></LI
><LI
><P
>&#13; <B
CLASS="command"
>useqacontact</B
>:
This allows you to define an email address for each component, in
addition
to that of the default owner, who will be sent carbon copies of
incoming bugs.</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>usestatuswhiteboard</B
>:
This defines whether you wish to have a free-form, overwritable field
associated with each bug. The advantage of the Status Whiteboard is
that it can be deleted or modified with ease, and provides an
easily-searchable field for indexing some bugs that have some trait
in common.
</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>whinedays</B
>:
Set this to the number 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 described in the installation
instructions, or set this value to "0" (never whine).</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>commenton*</B
>:
All these
fields allow you to dictate what changes can pass without comment,
and which must have a comment from the person who changed them.
Often, administrators will allow users to add themselves to the CC
list, accept bugs, or change the Status Whiteboard without adding a
comment as to their reasons for the change, yet require that most
other changes come with an explanation.</P
><P
>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"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>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 what the fix was (or even that it was truly
fixed!)</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
>&#13; <B
CLASS="command"
>supportwatchers</B
>:
Turning on this option allows users to ask to receive copies of
all a particular other user's bug email. This is, of
course, subject to the groupset restrictions on the bug; if the
<SPAN
CLASS="QUOTE"
>"watcher"</SPAN
>
would not normally be allowed to view a bug, the watcher cannot get
around the system by setting herself up to watch the bugs of someone
with bugs outside her privileges. They would still only receive email
updates for those bugs she could normally view.</P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="useradmin.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Administering Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>User Administration</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

67
webtools/bugzilla/docs/html/patches.html
Просмотреть файл

@ -10,10 +10,13 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"><LINK
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"><LINK
REL="NEXT"
TITLE="Apache mod_rewrite magic"
TITLE="Apache
mod_rewrite
magic"
HREF="rewrite.html"></HEAD
><BODY
CLASS="appendix"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="granttables.html"
HREF="dbdoc.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -69,7 +72,7 @@ WIDTH="100%"></DIV
CLASS="appendix"
><H1
><A
NAME="patches">Appendix D. Useful Patches and Utilities for Bugzilla</H1
NAME="patches">Appendix C. Useful Patches and Utilities for Bugzilla</H1
><DIV
CLASS="TOC"
><DL
@ -78,51 +81,26 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>D.1. <A
>C.1. <A
HREF="rewrite.html"
>Apache <TT
>Apache
<TT
CLASS="filename"
>mod_rewrite</TT
> magic</A
>
magic</A
></DT
><DT
>D.2. <A
HREF="setperl.html"
>The setperl.csh Utility</A
></DT
><DT
>D.3. <A
>C.2. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>D.4. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
><DT
>D.5. <A
HREF="bzhacking.html"
>Hacking Bugzilla</A
></DT
><DD
><DL
><DT
>D.5.1. <A
HREF="bzhacking.html#AEN2436"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
HREF="bzhacking.html#AEN2450"
>Coding Style for Bugzilla</A
></DT
></DL
></DD
></DL
></DIV
><P
>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</P
>Are you looking for a way to put your Bugzilla into overdrive? Catch
some of the niftiest tricks here in this section.</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -140,7 +118,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="granttables.html"
HREF="dbdoc.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -168,7 +146,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>MySQL Permissions &#38; Grant Tables</TD
>MySQL Bugzilla Database Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -178,10 +156,13 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Apache <TT
>Apache
<TT
CLASS="filename"
>mod_rewrite</TT
> magic</TD
>
magic</TD
></TR
></TABLE
></DIV

565
webtools/bugzilla/docs/html/postinstall-check.html
Просмотреть файл

@ -1,565 +0,0 @@
<HTML
><HEAD
><TITLE
>Post-Installation Checklist</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="NEXT"
TITLE="User Administration"
HREF="useradmin.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="administration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="useradmin.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="postinstall-check">4.1. Post-Installation Checklist</H1
><P
>&#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"
><OL
TYPE="1"
><LI
><P
>&#13; Bring up <TT
CLASS="filename"
>editparams.cgi</TT
> in your web
browser. This should be available as the <SPAN
CLASS="QUOTE"
>"edit
parameters"</SPAN
> link from any Bugzilla screen once you
have logged in.
</P
></LI
><LI
><P
>The <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> is the email address of
the person responsible for maintaining this Bugzilla
installation. The maintainer need not be a valid Bugzilla
user. Error pages, error emails, and administrative mail
will be sent with the maintainer as the return email
address.</P
><P
>&#13; Set <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> to <EM
>your</EM
> email address.
This allows Bugzilla's error messages to display your email
address and allow people to contact you for help.
</P
></LI
><LI
><P
>The <SPAN
CLASS="QUOTE"
>"urlbase"</SPAN
> parameter defines the fully
qualified domain name and web server path to your Bugzilla
installation.</P
><P
>&#13; For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<SPAN
CLASS="QUOTE"
>"urlbase"</SPAN
> is http://www.foo.com/bugzilla/.
</P
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"usebuggroups"</SPAN
> dictates whether or not to
implement group-based security for Bugzilla. If set,
Bugzilla bugs can have an associated groupmask defining
which groups of users are allowed to see and edit the
bug.</P
><P
>&#13; Set "usebuggroups" to "on" <EM
>only</EM
> if you
may wish to restrict access to products. I suggest leaving
this parameter <EM
>off</EM
> while initially
testing your Bugzilla.
</P
></LI
><LI
><P
>&#13; <SPAN
CLASS="QUOTE"
>"usebuggroupsentry"</SPAN
>, when set to
<SPAN
CLASS="QUOTE"
>"on"</SPAN
>, requires that all bugs have an associated
groupmask when submitted. This parameter is made for those
installations where product isolation is a necessity.
</P
><P
>&#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
on; the strict security checking may stop you from being
able to modify your new entries.
</P
></LI
><LI
><P
>&#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
entire table until the operation is complete. Locking for
write also blocks reads until the write is complete. The
<SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
> parameter was designed to get around
this limitation. While only a single user is allowed to
write to a table at a time, reads can continue unimpeded on
a read-only shadow copy of the database. Although your
database size will double, a shadow database can cause an
enormous performance improvement when implemented on
extremely high-traffic Bugzilla databases.
</P
><P
>&#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"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
<SPAN
CLASS="QUOTE"
>"cron"</SPAN
>.
</P
></TD
></TR
></TABLE
></DIV
> Once again, in testing you should avoid this option
-- use it if or when you <EM
>need</EM
> to use
it, and have repeatedly run into the problem it was designed
to solve -- very long wait times while attempting to commit
a change to the database. Mozilla.org began needing
<SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
> when they reached around 40,000
Bugzilla users with several hundred Bugzilla bug changes and
comments per day.
</P
><P
>&#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!
</P
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"headerhtml"</SPAN
>, <SPAN
CLASS="QUOTE"
>"footerhtml"</SPAN
>,
<SPAN
CLASS="QUOTE"
>"errorhtml"</SPAN
>, <SPAN
CLASS="QUOTE"
>"bannerhtml"</SPAN
>, and
<SPAN
CLASS="QUOTE"
>"blurbhtml"</SPAN
> are all templates which control
display of headers, footers, errors, banners, and additional
data. We could go into some detail regarding the usage of
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"
>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"
>data/params</TT
> file.</P
><P
>&#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"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page,
except the CONTENT-TYPE header sent by the Bugzilla
engine. If you have a special banner, put the code for
it in "bannerhtml". You may want to leave these settings
at the defaults initially.
</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"passwordmail"</SPAN
> is rather simple. Every
time a user creates an account, the text of this parameter
is read as the text to send to the new user along with their
password message.</P
><P
>&#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
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"useqacontact"</SPAN
> allows you to define an
email address for each component, in addition to that of the
default owner, who will be sent carbon copies of incoming
bugs. The critical difference between a QA Contact and an
Owner is that the QA Contact follows the component. If you
reassign a bug from component A to component B, the QA
Contact for that bug will change with the reassignment,
regardless of owner.</P
><P
><SPAN
CLASS="QUOTE"
>"usestatuswhiteboard"</SPAN
> defines whether you
wish to have a free-form, overwritable field associated with
each bug. The advantage of the Status Whiteboard is that it
can be deleted or modified with ease, and provides an
easily-searchable field for indexing some bugs that have
some trait in common. Many people will put <SPAN
CLASS="QUOTE"
>"help
wanted"</SPAN
>, <SPAN
CLASS="QUOTE"
>"stalled"</SPAN
>, or <SPAN
CLASS="QUOTE"
>"waiting
on reply from somebody"</SPAN
> messages into the Status
Whiteboard field so those who peruse the bugs are aware of
their status even more than that which can be indicated by
the Resolution fields.</P
><P
>&#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
and/or Release Engineering team, but they may not be needed
for many smaller installations.
</P
></LI
><LI
><P
>&#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
described in the installation instructions, or set this
value to "0" (never whine).
</P
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"commenton"</SPAN
> fields allow you to dictate
what changes can pass without comment, and which must have a
comment from the person who changed them. Often,
administrators will allow users to add themselves to the CC
list, accept bugs, or change the Status Whiteboard without
adding a comment as to their reasons for the change, yet
require that most other changes come with an
explanation.</P
><P
>&#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"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
what the fix was (or even that it was truly fixed!)
</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
>The <SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN
> option can be an
exceptionally powerful tool in the hands of a power Bugzilla
user. By enabling this option, you allow users to receive
email updates whenever other users receive email updates.
This is, of course, subject to the groupset restrictions on
the bug; if the <SPAN
CLASS="QUOTE"
>"watcher"</SPAN
> would not normally be
allowed to view a bug, the watcher cannot get around the
system by setting herself up to watch the bugs of someone
with bugs outside her privileges. She would still only
receive email updates for those bugs she could normally
view.</P
><P
>For Bugzilla sites which require strong inter-Product
security to prevent snooping, watchers are not a good
idea.</P
><P
>&#13; However, for most sites you should set
<SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN
> to "On". This feature is
helpful for team leads to monitor progress in their
respective areas, and can offer many other benefits, such as
allowing a developer to pick up a former engineer's bugs
without requiring her to change all the information in the
bug.
</P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="useradmin.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Administering Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>User Administration</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

1143
webtools/bugzilla/docs/html/programadmin.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

197
webtools/bugzilla/docs/html/quicksearch.html
Просмотреть файл

@ -1,197 +0,0 @@
<HTML
><HEAD
><TITLE
>The Quicksearch Utility</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"><LINK
REL="NEXT"
TITLE="Hacking Bugzilla"
HREF="bzhacking.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="cmdline.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="bzhacking.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="quicksearch">D.4. The Quicksearch Utility</H1
><P
>&#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
>&#13; The index.html page has been updated to include the QuickSearch
text box.
</P
><P
>&#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
>&#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"
in the summary, status whiteboard, product or component name,
but not those with the keyword "foo".
</P
><P
>&#13; Workarounds for Bugzilla users:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>search for '!foo' (this will find only bugs with the
keyword "foo"</TD
></TR
><TR
><TD
>search 'foo,!foo' (equivalent to 'foo OR
keyword:foo')</TD
></TR
></TBODY
></TABLE
><P
></P
>
</P
><P
>&#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"
TARGET="_top"
>This bug</A
> has details.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cmdline.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="bzhacking.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Command-line Bugzilla Queries</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="patches.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Hacking Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

62
webtools/bugzilla/docs/html/rewrite.html
Просмотреть файл

@ -1,7 +1,10 @@
<HTML
><HEAD
><TITLE
>Apache mod_rewrite magic</TITLE
>Apache
mod_rewrite
magic</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
@ -16,8 +19,8 @@ REL="PREVIOUS"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="NEXT"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -53,13 +56,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="setperl.html"
HREF="cmdline.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,30 +76,37 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="rewrite">D.1. Apache <TT
NAME="rewrite">C.1. Apache
<TT
CLASS="filename"
>mod_rewrite</TT
> magic</H1
>
magic</H1
><P
>Apache's <TT
>Apache's
<TT
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
>
module lets you do some truly amazing things with URL rewriting. Here are
a couple of examples of what you can do.</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Make it so if someone types
<TT
>Make it so if someone types
<TT
CLASS="computeroutput"
>http://www.foo.com/12345</TT
>,
Bugzilla spits back
http://www.foo.com/show_bug.cgi?id=12345. Try setting up
your VirtualHost section for Bugzilla with a rule like
this:</P
>
, Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try
setting up your VirtualHost section for Bugzilla with a rule like
this:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
@ -107,13 +117,11 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;
&#60;VirtualHost 12.34.56.78&#62;
>&#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
</PRE
></FONT
></TD
></TR
@ -121,14 +129,14 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
></LI
><LI
><P
>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 <A
>There are many, many more things you can do with mod_rewrite.
Please refer to the mod_rewrite documentation at
<A
HREF="http://www.apache.org"
TARGET="_top"
>http://www.apache.org</A
></P
>.
</P
></LI
></OL
></DIV
@ -166,7 +174,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="setperl.html"
HREF="cmdline.html"
ACCESSKEY="N"
>Next</A
></TD
@ -190,7 +198,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The setperl.csh Utility</TD
>Command-line Bugzilla Queries</TD
></TR
></TABLE
></DIV

26
webtools/bugzilla/docs/html/rhbugzilla.html
Просмотреть файл

@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Bugzilla Variants and Competitors</TD
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -73,22 +73,22 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="rhbugzilla">6.1. Red Hat Bugzilla</H1
NAME="rhbugzilla">D.1. Red Hat Bugzilla</H1
><P
>&#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
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
</P
>Red Hat Bugzilla is a fork of Bugzilla 2.8.
One of its major benefits is the ability
to work with Oracle, MySQL, and PostGreSQL databases serving as the
back-end, instead of just MySQL. Dave Lawrence of Red Hat is
active in the Bugzilla community, and we hope to see a reunification
of the fork before too long.</P
><P
>URL: <A
>URL:
<A
HREF="http://bugzilla.redhat.com/bugzilla/"
TARGET="_top"
>http://bugzilla.redhat.com/bugzilla/</A
></P
>&#13; http://bugzilla.redhat.com/bugzilla/</A
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"

166
webtools/bugzilla/docs/html/scm.html
Просмотреть файл

@ -1,166 +0,0 @@
<HTML
><HEAD
><TITLE
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"><LINK
REL="PREVIOUS"
TITLE="CVS"
HREF="cvs.html"><LINK
REL="NEXT"
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="cvs.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="tinderbox.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="scm">5.3. Perforce SCM</H1
><P
>&#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"
> http://www.ravenbrook.com/project/p4dti</A
> . <SPAN
CLASS="QUOTE"
>"p4dti"</SPAN
> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <A
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
TARGET="_top"
> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
><P
>&#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
designed to support multiple defect trackers, and maintains its
own documentation for it. Please consult the pages linked above
for further information.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cvs.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="tinderbox.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>CVS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="integration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Tinderbox/Tinderbox2</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

376
webtools/bugzilla/docs/html/security.html
Просмотреть файл

@ -13,12 +13,11 @@ REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Product, Component, Milestone, and Version
Administration"
HREF="programadmin.html"><LINK
TITLE="Groups and Group Security"
HREF="groups.html"><LINK
REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"></HEAD
TITLE="Template Customisation"
HREF="cust-templates.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -46,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="programadmin.html"
HREF="groups.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -54,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Administering Bugzilla</TD
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="integration.html"
HREF="cust-templates.html"
ACCESSKEY="N"
>Next</A
></TD
@ -74,32 +73,37 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="security">4.4. Bugzilla Security</H1
NAME="security">5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
></P
><TABLE
BORDER="0"
CLASS="warning"
WIDTH="100%"
CELLSPACING="0"
CELLPADDING="0"
CLASS="EPIGRAPH"
BORDER="0"
><TR
><TD
WIDTH="45%"
>&nbsp;</TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
><I
><P
><I
>Putting your money in a wall safe is better protection than
depending on the fact that no one knows that you hide your
money in a mayonnaise jar in your fridge.</I
></P
></I
>Poorly-configured MySQL and Bugzilla 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 trespassers are insiders, not
anonymous crackers.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
@ -121,101 +125,65 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
trespassers are insiders, not anonymous crackers.
>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
HREF="mailto://mozilla-webtools@mozilla.org"
TARGET="_top"
>&#13; mozilla-webtools@mozilla.org</A
>
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; Secure your installation.
<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
HREF="mailto://mozilla-webtools@mozilla.org"
TARGET="_top"
>mozilla-webtools@mozilla.org</A
>
</P
></TD
></TR
></TABLE
></DIV
>
<P
>To secure your installation:
<P
></P
><OL
TYPE="1"
><LI
><P
>&#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
>Ensure you are running at least MysQL version 3.22.32 or newer.
Earlier versions had notable security holes and (from a security
point of view) poor default configuration choices.</P
></LI
><LI
><P
><EM
>There is no substitute for understanding the
tools on your system!</EM
> Read <A
HREF="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html"
>&#13; <EM
>There is no substitute for understanding the tools on your
system!</EM
>
Read
<A
HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
TARGET="_top"
> The MySQL Privilege System</A
> until you can recite it from memory!</P
><P
>&#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
not allow CREATE, DROP, RELOAD, SHUTDOWN, and PROCESS for
user "bugs". I wrote up the Keystone advice back when I
knew far less about security than I do now : )
</P
>&#13; The MySQL Privilege System</A
>
until you can recite it from memory!</P
></LI
><LI
><P
>&#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
>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
>&#13; Do not run Apache as <SPAN
>Do not run Apache as
<SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>. This will
require very lax permissions in your Bugzilla directories.
Run it, instead, as a user with a name, set via your
httpd.conf file.
<DIV
>
. This will require very lax permissions in your Bugzilla
directories. Run it, instead, as a user with a name, set via your
httpd.conf file.
<DIV
CLASS="note"
><P
></P
@ -236,102 +204,77 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
> is a real user on UNIX systems.
Having a process run as user id <SPAN
>&#13; <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>
is absolutely no protection against system crackers
versus using any other user account. As a general
security measure, I recommend you create unique user
ID's for each daemon running on your system and, if
possible, use "chroot" to jail that process away from
the rest of your system.
</P
is a real user on UNIX systems. Having a process run as user id
<SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>
is absolutely no protection against system crackers versus using
any other user account. As a general security measure, I recommend
you create unique user ID's for each daemon running on your system
and, if possible, use "chroot" to jail that process away from the
rest of your system.</P
></TD
></TR
></TABLE
></DIV
>
</P
</P
></LI
><LI
><P
>&#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
stores your "bugs" user password, which would be terrible
to have in the hands of a criminal, while the "globals.pl"
stores some default information regarding your
installation which could aid a system cracker. In
addition, some files under $BUGZILLA_HOME/data/ store
sensitive information, and $BUGZILLA_HOME/shadow/ stores
bug information for faster retrieval. If you fail to
secure these directories and this file, you will expose
bug information to those who may not be allowed to see it.
</P
><DIV
CLASS="note"
>Ensure you have adequate access controls for the
$BUGZILLA_HOME/data/ directory, as well as the
$BUGZILLA_HOME/localconfig file.
The localconfig file stores your "bugs" database account password.
In addition, some
files under $BUGZILLA_HOME/data/ store sensitive information.
</P
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>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 .htaccess files are allowed to
"override" default permissions set in your Apache configuration
files. Covering Apache security is beyond the scope of this Guide;
please consult the Apache documentation for details.</P
><P
>&#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
.htaccess files are allowed to "override" default
permissions set in your Apache configuration files.
Covering Apache security is beyond the scope of this
Guide; please consult the Apache documentation for
details.
</P
><P
>&#13; If you are using a web server that does not support the
.htaccess control method, <EM
>you are at
risk!</EM
> After installing, check to see if
you can view the file "localconfig" in your web browser
(e.g.: <A
>If you are using a web server that does not support the
.htaccess control method,
<EM
>you are at risk!</EM
>
After installing, check to see if you can view the file
"localconfig" in your web browser (e.g.:
<A
HREF="http://bugzilla.mozilla.org/localconfig"
TARGET="_top"
> http://bugzilla.mozilla.org/localconfig</A
>). If you can read the contents of this file, your web server has not secured your bugzilla directory properly and you must fix this problem before deploying Bugzilla. If, however, it gives you a "Forbidden" error, then it probably respects the .htaccess conventions and you are good to go.
</P
></TD
></TR
></TABLE
></DIV
>&#13; http://bugzilla.mozilla.org/localconfig</A
>
). If you can read the contents of this file, your web server has
not secured your bugzilla directory properly and you must fix this
problem before deploying Bugzilla. If, however, it gives you a
"Forbidden" error, then it probably respects the .htaccess
conventions and you are good to go.</P
><P
>&#13; When you run checksetup.pl, the script will attempt to modify various
permissions on files which Bugzilla uses. If you do not have a
webservergroup set in the localconfig file, then Bugzilla will have to
make certain files world readable and/or writable. <EM
>THIS IS
INSECURE!</EM
>. This means that anyone who can get access to
your system can do whatever they want to your Bugzilla installation.
</P
>When you run checksetup.pl, the script will attempt to modify
various permissions on files which Bugzilla uses. If you do not have
a webservergroup set in the localconfig file, then Bugzilla will have
to make certain files world readable and/or writable.
<EM
>THIS IS INSECURE!</EM
>
. This means that anyone who can get access to your system can do
whatever they want to your Bugzilla installation.</P
><DIV
CLASS="note"
><P
@ -353,58 +296,56 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will
be able to take control of your Bugzilla installation.
</P
>This also means that if your webserver runs all cgi scripts
as the same user/group, anyone on the system who can run cgi
scripts will be able to take control of your Bugzilla
installation.</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A
>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"
>Bug 57161</A
> for the localconfig file, and <A
>Bug
57161</A
>
for the localconfig file, and
<A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
TARGET="_top"
> Bug 65572</A
> for adequate protection in your data/ and shadow/ directories.
</P
><P
>&#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
>&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/data
directory. <P
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
>Bug
65572</A
>
</P
for adequate protection in your data/ directory.</P
><P
>&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/
directory. <P
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
>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
>&#13; Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/shadow
directory. <P
>Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/data directory.
<P
CLASS="literallayout"
>&nbsp;deny&nbsp;from&nbsp;all&nbsp;</P
>&#60;Files&nbsp;comments&#62;&nbsp;allow&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;deny&nbsp;from&nbsp;all</P
>
</P
</P
><P
>Place the following text into a file named ".htaccess",
readable by your web server, in your $BUGZILLA_HOME/ directory.
<P
CLASS="literallayout"
>&#60;Files&nbsp;localconfig&#62;&nbsp;deny&nbsp;from&nbsp;all&nbsp;&#60;/Files&#62;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;allow&nbsp;from&nbsp;all</P
>
</P
></LI
></OL
>
@ -426,7 +367,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="programadmin.html"
HREF="groups.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -444,7 +385,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="integration.html"
HREF="cust-templates.html"
ACCESSKEY="N"
>Next</A
></TD
@ -454,8 +395,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Product, Component, Milestone, and Version
Administration</TD
>Groups and Group Security</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -469,7 +409,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Integrating Bugzilla with Third-Party Tools</TD
>Template Customisation</TD
></TR
></TABLE
></DIV

312
webtools/bugzilla/docs/html/setperl.html
Просмотреть файл

@ -1,312 +0,0 @@
<HTML
><HEAD
><TITLE
>The setperl.csh Utility</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="Apache mod_rewrite magic"
HREF="rewrite.html"><LINK
REL="NEXT"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="rewrite.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="cmdline.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="setperl">D.2. The setperl.csh Utility</H1
><P
> You can use the "setperl.csh" utility to quickly and
easily change the path to perl on all your Bugzilla files. This
is a C-shell script; if you do not have "csh" or "tcsh" in the
search path on your system, it will not work!
</P
><DIV
CLASS="procedure"
><OL
TYPE="1"
><LI
><P
>&#13; Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="command"
>cd /your/path/to/bugzilla</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
> </TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>chmod
u+x setperl.csh</B
> </TT
>
</P
></LI
></OL
></LI
><LI
><P
>&#13; Prepare (and fix) Bugzilla file permissions.
</P
><OL
CLASS="SUBSTEPS"
TYPE="a"
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="command"
>chmod u+w *</B
>
</TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>chmod
u+x duplicates.cgi</B
> </TT
>
</P
></LI
><LI
><P
>&#13; <TT
CLASS="computeroutput"
>&#13; <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="command"
>chmod a-x bug_status.html</B
>
</TT
>
</P
></LI
></OL
></LI
><LI
><P
>&#13; Run the script:
</P
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="command"
>./setperl.csh /your/path/to/perl</B
>
</TT
>
<DIV
CLASS="example"
><A
NAME="AEN2380"><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><P
>&#13; <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
>
<B
CLASS="command"
>./setperl.csh /usr/bin/perl</B
>
</TT
>
</P
></DIV
>
</P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="rewrite.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="cmdline.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Apache <TT
CLASS="filename"
>mod_rewrite</TT
> magic</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="patches.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Command-line Bugzilla Queries</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

2130
webtools/bugzilla/docs/html/stepbystep.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

156
webtools/bugzilla/docs/html/translations.html
Просмотреть файл

@ -1,156 +0,0 @@
<HTML
><HEAD
><TITLE
>Translations</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="Credits"
HREF="credits.html"><LINK
REL="NEXT"
TITLE="Document Conventions"
HREF="conventions.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. About This Guide</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="conventions.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="translations">1.6. Translations</H1
><P
>&#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"
>&#60;<A
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
>&#62;</TT
>, and arrange with
The Bugzilla Team to check it into CVS.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="conventions.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Credits</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="about.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Document Conventions</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

309
webtools/bugzilla/docs/html/troubleshooting.html Normal file
Просмотреть файл

@ -0,0 +1,309 @@
<HTML
><HEAD
><TITLE
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="Mac OS X Installation Notes"
HREF="osx.html"><LINK
REL="NEXT"
TITLE="Administering Bugzilla"
HREF="administration.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="osx.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="administration.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="troubleshooting">4.5. Troubleshooting</H1
><P
>This section gives solutions to common Bugzilla installation
problems.
</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1218">4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
>&#13; Try executing <B
CLASS="command"
>perl -MCPAN -e 'install CPAN'</B
>
and then continuing.
</P
><P
>&#13; Certain older versions of the CPAN toolset were somewhat naive about how
to upgrade Perl modules. When a couple of modules got rolled into the core
Perl distribution for 5.6.1, CPAN thought that the best way to get those
modules up to date was to haul down the Perl distribution itself and
build it. Needless to say, this has caused headaches for just about
everybody. Upgrading to a newer version of CPAN with the
commandline above should fix things.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1223">4.5.2. DBD::Sponge::db prepare failed</H2
><P
>&#13; The following error message may appear due to a bug in DBD::mysql
(over which the Bugzilla team have no control):
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> DBD::Sponge::db prepare failed: Cannot determine NUM_OF_FIELDS at D:/Perl/site/lib/DBD/mysql.pm line 248.
SV = NULL(0x0) at 0x20fc444
REFCNT = 1
FLAGS = (PADBUSY,PADMY)
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; To fix this, go to
<TT
CLASS="filename"
>&#60;path-to-perl&#62;/lib/DBD/sponge.pm</TT
>
in your Perl installation and replace
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> my $numFields;
if ($attribs-&#62;{'NUM_OF_FIELDS'}) {
$numFields = $attribs-&#62;{'NUM_OF_FIELDS'};
} elsif ($attribs-&#62;{'NAME'}) {
$numFields = @{$attribs-&#62;{NAME}};
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; by
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> my $numFields;
if ($attribs-&#62;{'NUM_OF_FIELDS'}) {
$numFields = $attribs-&#62;{'NUM_OF_FIELDS'};
} elsif ($attribs-&#62;{'NAMES'}) {
$numFields = @{$attribs-&#62;{NAMES}};
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; (note the S added to NAME.)
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="paranoid-security">4.5.3. cannot chdir(/var/spool/mqueue)</H2
><P
>If you are installing Bugzilla on SuSE 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:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>cannot chdir(/var/spool/mqueue): Permission denied
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
>&#13; This is because your
<TT
CLASS="filename"
>/var/spool/mqueue</TT
>
directory has a mode of
<SPAN
CLASS="QUOTE"
>"drwx------"</SPAN
>. Type
<B
CLASS="command"
>chmod 755
<TT
CLASS="filename"
>/var/spool/mqueue</TT
>
</B
>
as root to fix this problem.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="osx.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Mac OS X Installation Notes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Administering Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

178
webtools/bugzilla/docs/html/upgrading.html Normal file
Просмотреть файл

@ -0,0 +1,178 @@
<HTML
><HEAD
><TITLE
>Upgrading to New Releases</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Template Customisation"
HREF="cust-templates.html"><LINK
REL="NEXT"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="cust-templates.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="integration.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="upgrading">5.8. Upgrading to New Releases</H1
><P
>A plain Bugzilla is fairly easy to upgrade from one version to a
newer one. Always read the release notes to see if there are any issues
that you might need to take note of. It is recommended that you take a
backup of your database and your entire Bugzilla installation before attempting an
upgrade. You can upgrade a 'clean' installation by untarring a new
tarball over the old installation. If you are upgrading from 2.12 or
later, and have cvs installed, you can type <TT
CLASS="filename"
>cvs -z3 update</TT
>,
and resolve conflicts if there are any.
</P
><P
>However, things get a bit more complicated if you've made
changes to Bugzilla's code. In this case, you may have to re-make or
reapply those changes. One good method is to take a diff of your customised
version against the original, so you can survey all that you've changed.
Hopefully, templatisation will reduce the need for
this in the future.</P
><P
>From version 2.8 onwards, Bugzilla databases can be automatically
carried forward during an upgrade. However, because the developers of
Bugzilla are constantly adding new
tables, columns and fields, you'll probably get SQL errors if you just
update the code and attempt to use Bugzilla. Always run the
<TT
CLASS="filename"
>checksetup.pl</TT
>
script whenever you upgrade your installation.</P
><P
>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="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cust-templates.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="integration.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Template Customisation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Integrating Bugzilla with Third-Party Tools</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

582
webtools/bugzilla/docs/html/useradmin.html
Просмотреть файл

@ -13,11 +13,10 @@ REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Post-Installation Checklist"
HREF="postinstall-check.html"><LINK
TITLE="Bugzilla Configuration"
HREF="parameters.html"><LINK
REL="NEXT"
TITLE="Product, Component, Milestone, and Version
Administration"
TITLE="Product, Component, Milestone, and Version Administration"
HREF="programadmin.html"></HEAD
><BODY
CLASS="section"
@ -46,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="postinstall-check.html"
HREF="parameters.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -54,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 4. Administering Bugzilla</TD
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -74,26 +73,19 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="useradmin">4.2. User Administration</H1
><P
>&#13; User administration is one of the easiest parts of Bugzilla.
Keeping it from getting out of hand, however, can become a
challenge.
</P
NAME="useradmin">5.2. User Administration</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="defaultuser">4.2.1. Creating the Default User</H2
NAME="defaultuser">5.2.1. Creating the Default User</H2
><P
>&#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
checksetup.pl will again prompt you for this username and
password.
</P
>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 delete
the "super user" account, re-running checksetup.pl will again prompt
you for this username and password.</P
><DIV
CLASS="tip"
><P
@ -115,36 +107,60 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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"
><TT
>If you wish to add more administrative users, you must use the
MySQL interface. Run "mysql" from the command line, and use these
commands:
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
> use bugs;</B
>
<B
<B
CLASS="command"
><TT
>use bugs;</B
>
</TD
></TR
><TR
><TD
>&#13; <TT
CLASS="prompt"
>mysql&#62;</TT
> update profiles set
groupset=0x7ffffffffffffff where login_name = "(user's
login name)"; </B
>
</P
<B
CLASS="command"
>&#13; update profiles set groupset=0x7ffffffffffffff where login_name =
"(user's login name)";
</B
>
</TD
></TR
></TBODY
></TABLE
><P
>Yes, that is <EM
></P
>
</P
><P
>Yes, that is
<EM
>fourteen</EM
>
<SPAN
<SPAN
CLASS="QUOTE"
>"f"</SPAN
>'s. A whole lot of f-ing going on if you
want to create a new administator.</P
>
's. A whole lot of f-ing going on if you want to create a new
administator.</P
></TD
></TR
></TABLE
@ -155,125 +171,32 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="manageusers">4.2.2. Managing Other Users</H2
NAME="manageusers">5.2.2. Managing Other Users</H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="login">4.2.2.1. Logging In</H3
NAME="createnewusers">5.2.2.1. Creating new users</H3
><P
>Your users can create their own user accounts by clicking the
"New Account" link at the bottom of each page (assuming they
aren't logged in as someone else already.) However, should you
desire to create user accounts ahead of time, here is how you do
it.</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; Open the index.html page for your Bugzilla installation
in your browser window.
</P
>After logging in, click the "Users" link at the footer of
the query page, and then click "Add a new user".</P
></LI
><LI
><P
>&#13; Click the "Query Existing Bug Reports" link.
</P
></LI
><LI
><P
>&#13; Click the "Log In" link at the foot of the page.
</P
></LI
><LI
><P
>&#13; Type your email address, and the password which was
emailed to you when you created your Bugzilla account,
into the spaces provided.
</P
></LI
></OL
><P
>Congratulations, you are logged in!</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="createnewusers">4.2.2.2. Creating new users</H3
><P
>&#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.
</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; After logging in, click the "Users" link at the footer
of the query page.
</P
></LI
><LI
><P
>&#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"
><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; 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"
>man
regexp</B
> manual page for details on regular
expression syntax), or a <EM
>reverse</EM
>
regular expression match, where every user name which
does NOT match the regular expression is selected.
</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13; Click the "Add New User" link at the bottom of the user
list
</P
></LI
><LI
><P
>&#13; Fill out the form presented. This page is
self-explanatory. When done, click "submit".
</P
>Fill out the form presented. This page is self-explanatory.
When done, click "Submit".</P
><DIV
CLASS="note"
><P
@ -295,22 +218,24 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Adding a user this way will <EM
>Adding a user this way will
<EM
>not</EM
>
send an email informing them of their username and
password. While useful for creating dummy accounts
(watchers which shuttle mail to another system, for
instance, or email addresses which are a mailing
list), in general it is preferable to log out and use
the <SPAN
send an email informing them of their username and password.
While useful for creating dummy accounts (watchers which
shuttle mail to another system, for instance, or email
addresses which are a mailing list), in general it is
preferable to log out and use the
<SPAN
CLASS="QUOTE"
>"New Account"</SPAN
> button to create users,
as it will pre-populate all the required fields and
also notify the user of her account name and
password.
</P
>
button to create users, as it will pre-populate all the
required fields and also notify the user of her account name
and password.</P
></TD
></TR
></TABLE
@ -323,133 +248,73 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="disableusers">4.2.2.3. Disabling Users</H3
NAME="modifyusers">5.2.2.2. Modifying Users</H3
><P
>&#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
via the web interface. Your explanation, written in this
text box, will be presented to the user the next time she
attempts to use the system.
<DIV
CLASS="warning"
>To see a specific user, search for their login name
in the box provided on the "Edit Users" page. To see all users,
leave the box blank.</P
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13; Don't disable your own administrative account, or you
will hate life!
</P
><P
>At this time, <SPAN
CLASS="QUOTE"
>"Disabled Text"</SPAN
> does not
prevent a user from using the email interface. If you
have the email interface enabled, they can still
continue to submit bugs and comments that way. We need
a patch to fix this.</P
></TD
></TR
></TABLE
></DIV
>You can search in different ways the listbox to the right
of the text entry box. You can match by
case-insensitive substring (the default),
regular expression, or a
<EM
>reverse</EM
>
</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="modifyusers">4.2.2.4. Modifying Users</H3
regular expression match, which finds every user name which does NOT
match the regular expression. (Please see
the <B
CLASS="command"
>man regexp</B
>
manual page for details on regular expression syntax.)
</P
><P
>&#13; Here I will attempt to describe the function of each option
on the Edit User screen.
</P
>Once you have found your user, you can change the following
fields:</P
><P
></P
><UL
><LI
><P
>&#13; <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"
><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; For compatability reasons, you should probably stick
with email addresses as user login names. It will
make your life easier.
</P
></TD
></TR
></TABLE
></DIV
>
</P
>:
This is generally the user's full email address. However, if you
have are using the emailsuffix Param, this may just be the user's
login name. Note that users can now change their login names
themselves (to any valid email address.)
</P
></LI
><LI
><P
>&#13; <EM
>&#13; <EM
>Real Name</EM
>: Duh!
</P
>: The user's real name. Note that
Bugzilla does not require this to create an account.</P
></LI
><LI
><P
>&#13; <EM
>&#13; <EM
>Password</EM
>: You can change the user
password here. It is normal to only see asterisks.
</P
>:
You can change the user's password here. Users can automatically
request a new password, so you shouldn't need to do this often.
If you want to disable an account, see Disable Text below.
</P
></LI
><LI
><P
>&#13; <EM
>&#13; <EM
>Disable Text</EM
>: If you type anything
in this box, including just a space, the user account is
disabled from making any changes to bugs via the web
interface, and what you type in this box is presented as
the reason.
<DIV
>:
If you type anything in this box, including just a space, the
user is prevented from logging in, or making any changes to
bugs via the web interface.
The HTML you type in this box is presented to the user when
they attempt to perform these actions, and should explain
why the account was disabled.
<DIV
CLASS="warning"
><P
></P
@ -476,7 +341,8 @@ VALIGN="TOP"
></TABLE
></DIV
>
<DIV
<DIV
CLASS="note"
><P
></P
@ -497,143 +363,110 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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
>The user can still submit bugs via
the e-mail gateway, if you set it up, even if the disabled text
field is filled in. The e-mail gateway should
<EM
>not</EM
> be enabled for secure
installations of Bugzilla.
</P
>
be enabled for secure installations of Bugzilla.</P
></TD
></TR
></TABLE
></DIV
>
</P
</P
></LI
><LI
><P
>&#13; <EM
>CanConfirm</EM
>: This field is only used
if you have enabled "unconfirmed" status in your
parameters screen. If you enable this for a user, that
user can then move bugs from "Unconfirmed" to
"Confirmed" status (e.g.: "New" status). Be judicious
about allowing users to turn this bit on for other
users.
</P
>&#13; <EM
>&#60;groupname&#62;</EM
>:
If you have created some groups, e.g. "securitysensitive", then
checkboxes will appear here to allow you to add users to, or
remove them from, these groups.
</P
></LI
><LI
><P
>&#13; <EM
>Creategroups</EM
>: This option will
allow a user to create and destroy groups in Bugzilla.
Unless you are using the Bugzilla GroupSentry security
option "usebuggroupsentry" in your parameters, this
setting has no effect.
</P
>&#13; <EM
>canconfirm</EM
>:
This field is only used if you have enabled the "unconfirmed"
status. If you enable this for a user,
that user can then move bugs from "Unconfirmed" to a "Confirmed"
status (e.g.: "New" status).</P
></LI
><LI
><P
>&#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"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#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.
</P
></TD
></TR
></TABLE
></DIV
>
</P
>&#13; <EM
>creategroups</EM
>:
This option will allow a user to create and destroy groups in
Bugzilla.</P
></LI
><LI
><P
>&#13; <EM
>Editcomponents</EM
>: This flag allows a
user to create new products and components, as well as
modify and destroy those that have no bugs associated
with them. If a product or component has bugs
associated with it, those bugs must be moved to a
different product or component before Bugzilla will
allow them to be destroyed. The name of a product or
component can be changed without affecting the
associated bugs, but it tends to annoy the hell out of
your users when these change a lot.
</P
>&#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. Even if this
option is unchecked, users can still add comments to bugs.
</P
></LI
><LI
><P
>&#13; <EM
>Editkeywords</EM
>: If you use Bugzilla's
keyword functionality, enabling this feature allows a
user can create and destroy keywords. As always, the
keywords for existing bugs containing the keyword the
user wishes to destroy must be changed before Bugzilla
will allow it to die. You must be very careful about
creating too many new keywords if you run a very large
Bugzilla installation; keywords are global variables
across products, and you can often run into a phenomenon
called "keyword bloat". This confuses users, and then
the feature goes unused.
</P
>&#13; <EM
>editcomponents</EM
>:
This flag allows a user to create new products and components,
as well as modify and destroy those that have no bugs associated
with them. If a product or component has bugs associated with it,
those bugs must be moved to a different product or component
before Bugzilla will allow them to be destroyed.
</P
></LI
><LI
><P
>&#13; <EM
>Editusers</EM
>: This flag allows a user
do what you're doing right now: edit other users. This
will allow those with the right to do so to remove
administrator privileges from other users or grant them
to themselves. Enable with care.
</P
>&#13; <EM
>editkeywords</EM
>:
If you use Bugzilla's keyword functionality, enabling this
feature allows a user to create and destroy keywords. As always,
the keywords for existing bugs containing the keyword the user
wishes to destroy must be changed before Bugzilla will allow it
to die.</P
></LI
><LI
><P
>&#13; <EM
>PRODUCT</EM
>: PRODUCT bugs access. This
allows an administrator, with product-level granularity,
to specify in which products a user can edit bugs. The
user must still have the "editbugs" privelege to edit
bugs in this area; this simply restricts them from even
seeing bugs outside these boundaries if the
administrator has enabled the group sentry parameter
"usebuggroupsentry". Unless you are using bug groups,
this option has no effect.
</P
>&#13; <EM
>editusers</EM
>:
This flag allows a user to do what you're doing right now: edit
other users. This will allow those with the right to do so to
remove administrator privileges from other users or grant them to
themselves. Enable with care.</P
></LI
><LI
><P
>&#13; <EM
>tweakparams</EM
>:
This flag allows a user to change Bugzilla's Params
(using <TT
CLASS="filename"
>editparams.cgi</TT
>.)</P
></LI
><LI
><P
>&#13; <EM
>&#60;productname&#62;</EM
>:
This allows an administrator to specify the products in which
a user can see bugs. The user must still have the
"editbugs" privilege to edit bugs in these products.</P
></LI
></UL
></DIV
@ -655,7 +488,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="postinstall-check.html"
HREF="parameters.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -683,7 +516,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Post-Installation Checklist</TD
>Bugzilla Configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -697,8 +530,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Product, Component, Milestone, and Version
Administration</TD
>Product, Component, Milestone, and Version Administration</TD
></TR
></TABLE
></DIV

240
webtools/bugzilla/docs/html/userpreferences.html Normal file
Просмотреть файл

@ -0,0 +1,240 @@
<HTML
><HEAD
><TITLE
>User Preferences</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="Hints and Tips"
HREF="hintsandtips.html"><LINK
REL="NEXT"
TITLE="Installation"
HREF="installation.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="hintsandtips.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="installation.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="userpreferences">3.3. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
The preferences are split into four tabs:</P
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="accountsettings">3.3.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
reasons, in order to change anything on this page you must type your
<EM
>current</EM
>
password into the
<SPAN
CLASS="QUOTE"
>"Password"</SPAN
>
field at the top of the page.
If you attempt to change your email address, a confirmation
email is sent to both the old and new addresses, with a link to use to
confirm the change. This helps to prevent account hijacking.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="emailsettings">3.3.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
the bug and the change that was made to it. (Note that you can also do
client-side filtering using the X-Bugzilla-Reason header which Bugzilla
adds to all bugmail.)</P
><P
>By entering user email names, delineated by commas, into the
"Users to watch" text entry box you can receive a copy of all the
bugmail of other users (security settings permitting.) This powerful
functionality enables seamless transitions as developers change
projects or users go on holiday.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The ability to watch other users may not be available in all
Bugzilla installations. If you can't see it, ask your
administrator.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="footersettings">3.3.3. Page Footer</H2
><P
>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
Once you have a stored query, you can come
here to request that it also be displayed in your page footer.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="permissionsettings">3.3.4. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
are in, and whether you can edit bugs or perform various administration
functions.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="hintsandtips.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Hints and Tips</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Installation</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

132
webtools/bugzilla/docs/html/using.html
Просмотреть файл

@ -10,11 +10,11 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Document Conventions"
HREF="conventions.html"><LINK
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"><LINK
REL="NEXT"
TITLE="What is Bugzilla?"
HREF="whatis.html"></HEAD
TITLE="How do I use Bugzilla?"
HREF="how.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="conventions.html"
HREF="why.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="whatis.html"
HREF="how.html"
ACCESSKEY="N"
>Next</A
></TD
@ -69,30 +69,7 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="using">Chapter 2. Using Bugzilla</H1
><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
CELLPADDING="0"
CLASS="EPIGRAPH"
><TR
><TD
WIDTH="45%"
>&nbsp;</TD
><TD
WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
><I
><P
><I
>What, Why, How, &#38; Where?</I
></P
></I
></TD
></TR
></TABLE
NAME="using">Chapter 3. Using Bugzilla</H1
><DIV
CLASS="TOC"
><DL
@ -101,83 +78,102 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>2.1. <A
HREF="whatis.html"
>What is Bugzilla?</A
></DT
><DT
>2.2. <A
HREF="why.html"
>Why Should We Use Bugzilla?</A
></DT
><DT
>2.3. <A
>3.1. <A
HREF="how.html"
>How do I use Bugzilla?</A
></DT
><DD
><DL
><DT
>2.3.1. <A
>3.1.1. <A
HREF="how.html#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>2.3.2. <A
>3.1.2. <A
HREF="how.html#bug_page"
>Anatomy of a Bug</A
></DT
><DT
>2.3.3. <A
>3.1.3. <A
HREF="how.html#query"
>Searching for Bugs</A
></DT
><DT
>2.3.4. <A
>3.1.4. <A
HREF="how.html#list"
>Bug Lists</A
></DT
><DT
>2.3.5. <A
>3.1.5. <A
HREF="how.html#bugreports"
>Filing Bugs</A
></DT
></DL
></DD
><DT
>2.4. <A
HREF="init4me.html"
>Where can I find my user preferences?</A
>3.2. <A
HREF="hintsandtips.html"
>Hints and Tips</A
></DT
><DD
><DL
><DT
>2.4.1. <A
HREF="init4me.html#accountsettings"
>Account Settings</A
>3.2.1. <A
HREF="hintsandtips.html#AEN434"
>Autolinkification</A
></DT
><DT
>2.4.2. <A
HREF="init4me.html#emailsettings"
>Email Settings</A
>3.2.2. <A
HREF="hintsandtips.html#quicksearch"
>Quicksearch</A
></DT
><DT
>2.4.3. <A
HREF="init4me.html#footersettings"
>Page Footer</A
>3.2.3. <A
HREF="hintsandtips.html#commenting"
>Comments</A
></DT
><DT
>2.4.4. <A
HREF="init4me.html#permissionsettings"
>Permissions</A
>3.2.4. <A
HREF="hintsandtips.html#attachments"
>Attachments</A
></DT
><DT
>3.2.5. <A
HREF="hintsandtips.html#AEN463"
>Filing Bugs</A
></DT
></DL
></DD
><DT
>2.5. <A
HREF="usingbz-conc.html"
>Using Bugzilla-Conclusion</A
>3.3. <A
HREF="userpreferences.html"
>User Preferences</A
></DT
><DD
><DL
><DT
>3.3.1. <A
HREF="userpreferences.html#accountsettings"
>Account Settings</A
></DT
><DT
>3.3.2. <A
HREF="userpreferences.html#emailsettings"
>Email Settings</A
></DT
><DT
>3.3.3. <A
HREF="userpreferences.html#footersettings"
>Page Footer</A
></DT
><DT
>3.3.4. <A
HREF="userpreferences.html#permissionsettings"
>Permissions</A
></DT
></DL
></DD
></DL
></DIV
></DIV
@ -197,7 +193,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="conventions.html"
HREF="why.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -215,7 +211,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="whatis.html"
HREF="how.html"
ACCESSKEY="N"
>Next</A
></TD
@ -225,7 +221,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Document Conventions</TD
>Why Should We Use Bugzilla?</TD
><TD
WIDTH="34%"
ALIGN="center"
@ -235,7 +231,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>What is Bugzilla?</TD
>How do I use Bugzilla?</TD
></TR
></TABLE
></DIV

152
webtools/bugzilla/docs/html/usingbz-conc.html
Просмотреть файл

@ -1,152 +0,0 @@
<HTML
><HEAD
><TITLE
>Using Bugzilla-Conclusion</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="Where can I find my user preferences?"
HREF="init4me.html"><LINK
REL="NEXT"
TITLE="Installation"
HREF="installation.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="init4me.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Using Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="installation.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="usingbz-conc">2.5. Using Bugzilla-Conclusion</H1
><P
>&#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
HREF="mailto://mozilla-webtools@mozilla.org"
TARGET="_top"
>mozilla-webtools</A
> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="init4me.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Where can I find my user preferences?</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Installation</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

13
webtools/bugzilla/docs/html/variant-fenris.html
Просмотреть файл

@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Bugzilla Variants and Competitors</TD
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -73,13 +73,12 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-fenris">6.2. Loki Bugzilla (Fenris)</H1
NAME="variant-fenris">D.2. Loki Bugzilla (Fenris)</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
>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
its custodians recommend Bugzilla for future bug-tracker deployments.
</P
></DIV
><DIV
CLASS="NAVFOOTER"

25
webtools/bugzilla/docs/html/variant-issuezilla.html
Просмотреть файл

@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Bugzilla Variants and Competitors</TD
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -73,24 +73,15 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-issuezilla">6.3. Issuezilla</H1
NAME="variant-issuezilla">D.3. Issuezilla</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
>Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of bug-tracking
at tigris.org is 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
>Scarab</A
>.</P
></DIV
><DIV
CLASS="NAVFOOTER"

20
webtools/bugzilla/docs/html/variant-perforce.html
Просмотреть файл

@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Bugzilla Variants and Competitors</TD
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -73,19 +73,23 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-perforce">6.5. Perforce SCM</H1
NAME="variant-perforce">D.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used
as such through the <SPAN
>Although Perforce isn't really a bug tracker, it can be used as
such through the <SPAN
CLASS="QUOTE"
>"jobs"</SPAN
> functionality.</P
>
functionality.</P
><P
><A
>URL:
<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
>&#13; http://www.perforce.com/perforce/technotes/note052.html
</A
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"

17
webtools/bugzilla/docs/html/variant-scarab.html
Просмотреть файл

@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Bugzilla Variants and Competitors</TD
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -73,19 +73,18 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-scarab">6.4. Scarab</H1
NAME="variant-scarab">D.4. Scarab</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
>Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 8.</P
><P
>URL: <A
>URL:
<A
HREF="http://scarab.tigris.org/"
TARGET="_top"
>http://scarab.tigris.org</A
></P
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"

30
webtools/bugzilla/docs/html/variant-sourceforge.html
Просмотреть файл

@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="variant-perforce.html"><LINK
REL="NEXT"
TITLE="The Bugzilla FAQ"
HREF="faq.html"></HEAD
TITLE="Glossary"
HREF="glossary.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -53,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Bugzilla Variants and Competitors</TD
>Appendix D. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="faq.html"
HREF="glossary.html"
ACCESSKEY="N"
>Next</A
></TD
@ -73,19 +73,19 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-sourceforge">6.6. SourceForge</H1
NAME="variant-sourceforge">D.6. SourceForge</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
>SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
It has a built-in bug tracker, but it's not highly thought of.</P
><P
>URL: <A
>URL:
<A
HREF="http://www.sourceforge.net"
TARGET="_top"
>http://www.sourceforge.net</A
></P
>&#13; http://www.sourceforge.net</A
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -121,7 +121,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="faq.html"
HREF="glossary.html"
ACCESSKEY="N"
>Next</A
></TD
@ -145,7 +145,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla FAQ</TD
>Glossary</TD
></TR
></TABLE
></DIV

42
webtools/bugzilla/docs/html/variants.html
Просмотреть файл

@ -10,13 +10,13 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"><LINK
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
><BODY
CLASS="chapter"
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="tinderbox.html"
HREF="cmdline.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -66,10 +66,10 @@ ACCESSKEY="N"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
CLASS="appendix"
><H1
><A
NAME="variants">Chapter 6. Bugzilla Variants and Competitors</H1
NAME="variants">Appendix D. Bugzilla Variants and Competitors</H1
><DIV
CLASS="TOC"
><DL
@ -78,46 +78,48 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>6.1. <A
>D.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
>6.2. <A
>D.2. <A
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>6.3. <A
>D.3. <A
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>6.4. <A
>D.4. <A
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>6.5. <A
>D.5. <A
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>6.6. <A
>D.6. <A
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
></DL
></DIV
><P
>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <A
>I created this section to answer questions about Bugzilla competitors
and variants, then found a wonderful site which covers an awful lot of what
I wanted to discuss. Rather than quote it in its entirety, I'll simply
refer you here:
<A
HREF="http://linas.org/linux/pm.html"
TARGET="_top"
>http://linas.org/linux/pm.html</A
></P
>&#13; http://linas.org/linux/pm.html</A
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -135,7 +137,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="tinderbox.html"
HREF="cmdline.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -163,7 +165,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Tinderbox/Tinderbox2</TD
>Command-line Bugzilla Queries</TD
><TD
WIDTH="34%"
ALIGN="center"

195
webtools/bugzilla/docs/html/voting.html Normal file
Просмотреть файл

@ -0,0 +1,195 @@
<HTML
><HEAD
><TITLE
>Voting</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Product, Component, Milestone, and Version Administration"
HREF="programadmin.html"><LINK
REL="NEXT"
TITLE="Groups and Group Security"
HREF="groups.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation 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="programadmin.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="groups.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="voting">5.4. Voting</H1
><P
>Voting allows users to be given a pot of votes which they can allocate
to bugs, to indicate that they'd like them fixed.
This allows developers to gauge
user need for a particular enhancement or bugfix. By allowing bugs with
a certain number of votes to automatically move from "UNCONFIRMED" to
"NEW", users of the bug system can help high-priority bugs garner
attention so they don't sit for a long time awaiting triage.</P
><P
>To modify Voting settings:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Navigate to the "Edit product" screen for the Product you
wish to modify</P
></LI
><LI
><P
><EM
>Maximum Votes per person</EM
>:
Setting this field to "0" disables voting.</P
></LI
><LI
><P
><EM
>Maximum Votes a person can put on a single
bug"</EM
>:
It should probably be some number lower than the
"Maximum votes per person". Don't set this field to "0" if
"Maximum votes per person" is non-zero; that doesn't make
any sense.</P
></LI
><LI
><P
><EM
>Number of votes a bug in this product needs to
automatically get out of the UNCONFIRMED state</EM
>:
Setting this field to "0" disables the automatic move of
bugs from UNCONFIRMED to NEW.
</P
></LI
><LI
><P
>Once you have adjusted the values to your preference, click
"Update".</P
></LI
></OL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="programadmin.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="groups.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Product, Component, Milestone, and Version Administration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Groups and Group Security</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

50
webtools/bugzilla/docs/html/whatis.html
Просмотреть файл

@ -10,11 +10,11 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="PREVIOUS"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="NEXT"
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"></HEAD
@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="using.html"
HREF="introduction.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Using Bugzilla</TD
>Chapter 2. Introduction</TD
><TD
WIDTH="10%"
ALIGN="right"
@ -75,23 +75,22 @@ CLASS="section"
><A
NAME="whatis">2.1. What is Bugzilla?</H1
><P
>&#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
originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy bug-tracking database used internally by
Netscape Communications. Terry later ported Bugzilla to Perl from
TCL, and in Perl it remains to this day. Most commercial
defect-tracking software vendors at the time charged enormous
licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser
project, Mozilla). It is now the de-facto standard defect-tracking
system against which all others are measured.
>&#13; Bugzilla is a bug- or issue-tracking system. Bug-tracking
systems allow individual or groups of developers effectively to keep track
of outstanding problems with their product.
Bugzilla was originally
written by Terry Weissman in a programming language called TCL, to
replace a rudimentary bug-tracking database used internally by Netscape
Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
it remains to this day. Most commercial defect-tracking software vendors
at the time charged enormous licensing fees, and Bugzilla quickly became
a favorite of the open-source crowd (with its genesis in the open-source
browser project, Mozilla). It is now the de-facto standard
defect-tracking system against which all others are measured.
</P
><P
>&#13; Bugzilla has matured immensely, and now boasts many advanced features. These include:
<P
>Bugzilla boasts many advanced features. These include:
<P
></P
><UL
><LI
@ -132,7 +131,8 @@ system against which all others are measured.
></LI
><LI
><P
>Completely customisable and/or localisable web user interface</P
>Completely customisable and/or localisable web user
interface</P
></LI
><LI
><P
@ -162,7 +162,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="using.html"
HREF="introduction.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -190,13 +190,13 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using Bugzilla</TD
>Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
HREF="introduction.html"
ACCESSKEY="U"
>Up</A
></TD

147
webtools/bugzilla/docs/html/why.html
Просмотреть файл

@ -10,14 +10,14 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
TITLE="Introduction"
HREF="introduction.html"><LINK
REL="PREVIOUS"
TITLE="What is Bugzilla?"
HREF="whatis.html"><LINK
REL="NEXT"
TITLE="How do I use Bugzilla?"
HREF="how.html"></HEAD
TITLE="Using Bugzilla"
HREF="using.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
@ -53,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Using Bugzilla</TD
>Chapter 2. Introduction</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="how.html"
HREF="using.html"
ACCESSKEY="N"
>Next</A
></TD
@ -74,86 +74,71 @@ CLASS="section"
CLASS="section"
><A
NAME="why">2.2. Why Should We Use Bugzilla?</H1
><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
CELLPADDING="0"
CLASS="EPIGRAPH"
><TR
><TD
WIDTH="45%"
>&nbsp;</TD
><TD
WIDTH="45%"
ALIGN="LEFT"
VALIGN="TOP"
><I
><P
><I
>No, Who's on first...</I
></P
></I
></TD
></TR
></TABLE
>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 the status of defects. This procedure
is error-prone and tends to cause those bugs judged least significant by
developers to be dropped or ignored.</P
><P
>&#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
the status of defects. This procedure is error-prone and tends
to cause those bugs judged least significant by developers to be
dropped or ignored.
</P
>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 keep in touch with their clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood system for accounting for unusual system or software
issues.</P
><P
>&#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
keep in touch with their clients and resellers, to communicate
about problems effectively throughout the data management chain.
Many corporations have also discovered that defect-tracking
helps reduce costs by providing IT support accountability,
telephone support knowledge bases, and a common, well-understood
system for accounting for unusual system or software issues.
</P
><P
>&#13; But why should <EM
>But why should
<EM
>you</EM
> use Bugzilla?
</P
>
use Bugzilla?</P
><P
>&#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
hardware bug tracking for luminaries such as Redhat, Loki
software, Linux-Mandrake, and VA Systems. Combined with systems
such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a
powerful, easy-to-use solution to configuration management and
replication problems
</P
>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 hardware bug tracking for
luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
Combined with systems such as
<A
HREF="http://www.cvshome.org"
TARGET="_top"
>CVS</A
>,
<A
HREF="http://www.mozilla.org/bonsai.html"
TARGET="_top"
>Bonsai</A
>, or
<A
HREF="http://www.perforce.com"
TARGET="_top"
>Perforce SCM</A
>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</P
><P
>&#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
supposed to do <EM
>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 supposed to do
<EM
>something</EM
> today, but you
just can't quite remember? Put it in Bugzilla, and you have a
record of it from which you can extrapolate milestones, predict
product versions for integration, and by using Bugzilla's e-mail
integration features be able to follow the discussion trail that
led to critical decisions.
</P
>
today, but you just can't quite remember? Put it in Bugzilla, and you
have a record of it from which you can extrapolate milestones, predict
product versions for integration, and follow the discussion trail
that led to critical decisions.</P
><P
>&#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.
</P
>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.</P
></DIV
><DIV
CLASS="NAVFOOTER"
@ -189,7 +174,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="how.html"
HREF="using.html"
ACCESSKEY="N"
>Next</A
></TD
@ -205,7 +190,7 @@ WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="using.html"
HREF="introduction.html"
ACCESSKEY="U"
>Up</A
></TD
@ -213,7 +198,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>How do I use Bugzilla?</TD
>Using Bugzilla</TD
></TR
></TABLE
></DIV

1193
webtools/bugzilla/docs/html/win32.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

54
webtools/bugzilla/docs/sgml/Bugzilla-Guide.sgml
Просмотреть файл

@ -16,7 +16,7 @@
<!ENTITY database SYSTEM "database.sgml">
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
<!ENTITY introduction SYSTEM "introduction.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!ENTITY bz "http://www.bugzilla.org/">
@ -61,33 +61,35 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<title>The Bugzilla Guide</title>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
<affiliation>
<address><email>mbarnson@sisna.com</email></address>
</affiliation>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
</author>
<author>
<firstname>The</firstname>
<othername>Bugzilla</othername>
<surname>Team</surname>
</author>
</authorgroup>
<abstract>
<para>
This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
</para>
<para>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a Bugzilla bug.
<para>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a bug filed in
<ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation">mozilla.org's Bugzilla</ulink>.
</para>
</abstract>
<keywordset>
<keyword>Bugzilla</keyword>
<keyword>Guide</keyword>
@ -104,6 +106,9 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<!-- About This Guide -->
&about;
<!-- Introduction -->
&introduction;
<!-- Using Bugzilla -->
&using;
@ -113,26 +118,17 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<!-- Administering Bugzilla -->
&administration;
<!-- Integrating Bugzilla with Third-Party Tools -->
&integration;
<!-- Major Bugzilla Variants -->
&variants;
<!-- Appendix: The Frequently Asked Questions -->
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware;
<!-- Appendix: The Database Schema -->
&database;
<!-- Appendix: Custom Patches -->
&patches;
<!-- Appendix: The GNU Free Documentation License -->
&gfdl;
<!-- Appendix: Major Bugzilla Variants -->
&variants;
<!-- Glossary -->
&glossary;

104
webtools/bugzilla/docs/sgml/about.sgml
Просмотреть файл

@ -4,40 +4,6 @@
<chapter id="about">
<title>About This Guide</title>
<section id="aboutthisguide">
<title>Purpose and Scope of this Guide</title>
<para>
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.
</para>
<para>
This release of the Bugzilla Guide is the
<emphasis>&bzg-ver;</emphasis> release. It is so named that it
may match the current version of Bugzilla. The numbering
tradition stems from that used for many free software projects,
in which <emphasis>even-numbered</emphasis> point releases (1.2,
1.14, etc.) are considered "stable releases", intended for
public consumption; on the other hand,
<emphasis>odd-numbered</emphasis> point releases (1.3, 2.09,
etc.) are considered unstable <emphasis>development</emphasis>
releases intended for advanced users, systems administrators,
developers, and those who enjoy a lot of pain.
</para>
<para>
Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<ulink url="&bz;">&bz;</ulink>. Intermediate releases will have
a minor revision number following a period. The current version
of Bugzilla, as of this writing (&bzg-date;) is &bz-ver;; if
something were seriously wrong with that edition of the Guide,
subsequent releases would receive an additional dotted-decimal
digit to indicate the update (&bzg-ver;.1, &bzg-ver;.2, etc.).
Got it? Good.
</para>
</section>
<section id="copyright">
<title>Copyright Information</title>
<blockquote>
@ -48,8 +14,7 @@
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
the license is included in the section entitled "GNU Free
Documentation License".
the license is included below.
</para>
</blockquote>
<para>
@ -57,6 +22,11 @@
copyright, or publishing this document in non-electronic form,
please contact &bzg-auth;.
</para>
<!-- The GNU Free Documentation License -->
&gfdl;
</section>
<section id="disclaimer">
@ -64,12 +34,11 @@
<para>
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
document may cause your girlfriend to leave you, your cats to
pee on your furniture and clothing, your computer to cease
functioning, your boss to fire you, and global thermonuclear
war. Proceed with caution.
This document may contain errors
and inaccuracies that may damage your system, cause your partner
to leave you, your boss to fire you, your cats to
pee on your furniture and clothing, and global thermonuclear
war. Proceed with caution.
</para>
<para>
All copyrights are held by their respective owners, unless
@ -100,7 +69,7 @@
team members, Netscape Communications, America Online Inc., and
any affiliated developers or sponsors assume no liability for
your use of this product. You have the source code to this
product, and are responsible for auditing it yourself to insure
product, and are responsible for auditing it yourself to ensure
your security needs are met.
</para>
</section>
@ -110,7 +79,8 @@
<section id="newversions">
<title>New Versions</title>
<para>
This is the &bzg-ver; version of The Bugzilla Guide. If you are
This is the &bzg-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. 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.
@ -134,9 +104,16 @@
</itemizedlist>
</para>
<para>
The latest version of this document can be checked out via CVS.
Please follow the instructions available at <ulink
url="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ulink>, and check out the <filename>mozilla/webtools/bugzilla/docs/</filename> branch.
The latest version of this document can always be checked out via CVS.
Please follow the instructions available at
<ulink url="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ulink>,
and check out the <filename>mozilla/webtools/bugzilla/docs/</filename>
subtree.
</para>
<para>
The Bugzilla Guide is currently only available in English.
If you would like to volunteer to translate it, please contact
<ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
</para>
</section>
@ -144,13 +121,14 @@
<title>Credits</title>
<para>
The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts,
creation of this Guide, through their writing, dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</para>
<para>
<ulink url="mailto://mbarnson@sisna.com">Matthew P. Barnson</ulink>
for pulling together the Bugzilla Guide and shepherding it to 2.14.
for the Herculaean task of pulling together the Bugzilla Guide and
shepherding it to 2.14.
</para>
<para>
<ulink url="mailto://terry@mozilla.org">Terry Weissman</ulink>
@ -158,13 +136,13 @@
README upon which the UNIX installation documentation is largely based.
</para>
<para>
<ulink url="mailto://tara@tequilarista.org">Tara
Hernandez</ulink> for keeping Bugzilla development going
strong after Terry left Mozilla.org
<ulink url="mailto://tara@tequilarista.org">Tara Hernandez</ulink>
for keeping Bugzilla development going
strong after Terry left mozilla.org
</para>
<para>
<ulink url="mailto://dkl@redhat.com">Dave Lawrence</ulink> for
providing insight into the key differences between Red Hat's
<ulink url="mailto://dkl@redhat.com">Dave Lawrence</ulink>
for providing insight into the key differences between Red Hat's
customized Bugzilla, and being largely responsible for the "Red
Hat Bugzilla" appendix
</para>
@ -174,8 +152,8 @@
questions and arguments on irc.mozilla.org in #mozwebtools
</para>
<para>
Last but not least, all the members of the <ulink
url="news://news.mozilla.org/netscape/public/mozilla/webtools"> netscape.public.mozilla.webtools</ulink> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
Last but not least, all the members of the
<ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools"> netscape.public.mozilla.webtools</ulink> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
</para>
<para>
Thanks also go to the following people for significant contributions
@ -183,19 +161,7 @@
</para>
<para>
Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
</para>
</section>
<section id="translations">
<title>Translations</title>
<para>
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
<email>mozilla-webtools@mozilla.org</email>, and arrange with
&bzg-auth; to check it into CVS.
Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
</para>
</section>

1628
webtools/bugzilla/docs/sgml/administration.sgml
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

15
webtools/bugzilla/docs/sgml/conventions.sgml
Просмотреть файл

@ -6,7 +6,7 @@
<primary>conventions</primary>
</indexterm>
<para>This document uses the following conventions</para>
<para>This document uses the following conventions:</para>
<informaltable frame="none">
<tgroup cols="2">
@ -34,7 +34,7 @@
<entry>
<tip>
<para>Warm jar lids under the hot tap to loosen them.</para>
<para>Would you like a breath mint?</para>
</tip>
</entry>
</row>
@ -63,7 +63,7 @@
<entry>File Names</entry>
<entry>
<filename>file.extension</filename>
<filename>filename</filename>
</entry>
</row>
@ -138,12 +138,9 @@
<entry>Code Example</entry>
<entry>
<programlisting>
<sgmltag class="starttag">para</sgmltag>
Beginning and end of paragraph
<sgmltag class="endtag">para</sgmltag>
</programlisting>
<programlisting><sgmltag class="starttag">para</sgmltag>
Beginning and end of paragraph
<sgmltag class="endtag">para</sgmltag></programlisting>
</entry>
</row>
</tbody>

466
webtools/bugzilla/docs/sgml/database.sgml
Просмотреть файл

@ -123,10 +123,10 @@
! You should have locked your security down like the installation
instructions told you to. You can find details on locking down
your database in the Bugzilla FAQ in this directory (under
"Security"), or more robust security generalities in the MySQL
searchable documentation at
http://www.mysql.com/php/manual.php3?section=Privilege_system
.</para>
"Security"), or more robust security generalities in the
<ulink url="http://www.mysql.com/php/manual.php3?section=Privilege_system">MySQL
searchable documentation</ulink>.
</para>
</listitem>
<listitem>
@ -150,13 +150,6 @@
<command>use bugs;</command>
</para>
<note>
<para>Don't forget the
<quote>;</quote>
at the end of each line, or you'll be kicking yourself
later.</para>
</note>
</listitem>
</orderedlist>
</para>
@ -169,273 +162,212 @@
<para>
<prompt>mysql&gt;</prompt>
<command>show tables from bugs;</command>
</para>
<para>you'll be able to see all the
<para>you'll be able to see the names of all the
<quote>spreadsheets</quote>
(tables) in your database.</para>
(tables) in your database. It is similar to a file system, only
faster and more robust for certain types of operations.</para>
<para>From the command issued above, ou should have some
output that looks like this:
<programlisting>
+-------------------+
| Tables in bugs |
+-------------------+
| attachments |
| bugs |
| bugs_activity |
| cc |
| components |
| dependencies |
| fielddefs |
| groups |
| keyworddefs |
| keywords |
| logincookies |
| longdescs |
| milestones |
| namedqueries |
| products |
| profiles |
| profiles_activity |
| shadowlog |
| tokens |
| versions |
| votes |
| watch |
+-------------------+
</programlisting>
</para>
<para>From the command issued above, ou should have some output that
looks like this:
<programlisting>+-------------------+ | Tables in bugs |
+-------------------+ | attachments | | bugs | | bugs_activity | | cc
| | components | | dependencies | | fielddefs | | groups | |
keyworddefs | | keywords | | logincookies | | longdescs | |
milestones | | namedqueries | | products | | profiles | |
profiles_activity | | shadowlog | | tokens | | versions | | votes | |
watch | +-------------------+</programlisting>
</para>
<literallayout>
Here's an overview of what each table does. Most columns in each table have
descriptive names that make it fairly trivial to figure out their jobs.
<literallayout>Here's an overview of what each table does. Most
columns in each table have descriptive names that make it fairly
trivial to figure out their jobs. attachments: This table stores all
attachments to bugs. It tends to be your largest table, yet also
generally has the fewest entries because file attachments are so
(relatively) large. bugs: This is the core of your system. The bugs
table stores most of the current information about a bug, with the
exception of the info stored in the other tables. bugs_activity: This
stores information regarding what changes are made to bugs when -- a
history file. cc: This tiny table simply stores all the CC
information for any bug which has any entries in the CC field of the
bug. Note that, like most other tables in Bugzilla, it does not refer
to users by their user names, but by their unique userid, stored as a
primary key in the profiles table. components: This stores the
programs and components (or products and components, in newer
Bugzilla parlance) for Bugzilla. Curiously, the "program" (product)
field is the full name of the product, rather than some other unique
identifier, like bug_id and user_id are elsewhere in the database.
dependencies: Stores data about those cool dependency trees.
fielddefs: A nifty table that defines other tables. For instance,
when you submit a form that changes the value of "AssignedTo" this
table allows translation to the actual field name "assigned_to" for
entry into MySQL. groups: defines bitmasks for groups. A bitmask is a
number that can uniquely identify group memberships. For instance,
say the group that is allowed to tweak parameters is assigned a value
of "1", the group that is allowed to edit users is assigned a "2",
and the group that is allowed to create new groups is assigned the
bitmask of "4". By uniquely combining the group bitmasks (much like
the chmod command in UNIX,) you can identify a user is allowed to
tweak parameters and create groups, but not edit users, by giving him
a bitmask of "5", or a user allowed to edit users and create groups,
but not tweak parameters, by giving him a bitmask of "6" Simple, huh?
If this makes no sense to you, try this at the mysql prompt:
mysql&gt; select * from groups; You'll see the list, it makes much
more sense that way. keyworddefs: Definitions of keywords to be used
keywords: Unlike what you'd think, this table holds which keywords
are associated with which bug id's. logincookies: This stores every
login cookie ever assigned to you for every machine you've ever
logged into Bugzilla from. Curiously, it never does any housecleaning
-- I see cookies in this file I've not used for months. However,
since Bugzilla never expires your cookie (for convenience' sake), it
makes sense. longdescs: The meat of bugzilla -- here is where all
user comments are stored! You've only got 2^24 bytes per comment
(it's a mediumtext field), so speak sparingly -- that's only the
amount of space the Old Testament from the Bible would take
(uncompressed, 16 megabytes). Each comment is keyed to the bug_id to
which it's attached, so the order is necessarily chronological, for
comments are played back in the order in which they are received.
milestones: Interesting that milestones are associated with a
specific product in this table, but Bugzilla does not yet support
differing milestones by product through the standard configuration
interfaces. namedqueries: This is where everybody stores their
"custom queries". Very cool feature; it beats the tar out of having
to bookmark each cool query you construct. products: What products
you have, whether new bug entries are allowed for the product, what
milestone you're working toward on that product, votes, etc. It will
be nice when the components table supports these same features, so
you could close a particular component for bug entry without having
to close an entire product... profiles: Ahh, so you were wondering
where your precious user information was stored? Here it is! With the
passwords in plain text for all to see! (but sshh... don't tell your
users!) profiles_activity: Need to know who did what when to who's
profile? This'll tell you, it's a pretty complete history. shadowlog:
I could be mistaken here, but I believe this table tells you when
your shadow database is updated and what commands were used to update
it. We don't use a shadow database at our site yet, so it's pretty
empty for us. versions: Version information for every product votes:
Who voted for what when watch: Who (according to userid) is watching
who's bugs (according to their userid). === THE DETAILS === Ahh, so
you're wondering just what to do with the information above? At the
mysql prompt, you can view any information about the columns in a
table with this command (where "table" is the name of the table you
wish to view): mysql&gt; show columns from table; You can also view
all the data in a table with this command: mysql&gt; select * from
table; -- note: this is a very bad idea to do on, for instance, the
"bugs" table if you have 50,000 bugs. You'll be sitting there a while
until you ctrl-c or 50,000 bugs play across your screen. You can
limit the display from above a little with the command, where
"column" is the name of the column for which you wish to restrict
information: mysql&gt; select * from table where (column = "some
info"); -- or the reverse of this mysql&gt; select * from table where
(column != "some info"); Let's take our example from the
introduction, and assume you need to change the word "verified" to
"approved" in the resolution field. We know from the above
information that the resolution is likely to be stored in the "bugs"
table. Note we'll need to change a little perl code as well as this
database change, but I won't plunge into that in this document. Let's
verify the information is stored in the "bugs" table: mysql&gt; show
columns from bugs (exceedingly long output truncated here) |
bug_status|
enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL
| UNCONFIRMED|| Sorry about that long line. We see from this that the
"bug status" column is an "enum field", which is a MySQL peculiarity
where a string type field can only have certain types of entries.
While I think this is very cool, it's not standard SQL. Anyway, we
need to add the possible enum field entry 'APPROVED' by altering the
"bugs" table. mysql&gt; ALTER table bugs CHANGE bug_status bug_status
-&gt; enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",
-&gt; "VERIFIED", "APPROVED", "CLOSED") not null; (note we can take
three lines or more -- whatever you put in before the semicolon is
evaluated as a single expression) Now if you do this: mysql&gt; show
columns from bugs; you'll see that the bug_status field has an extra
"APPROVED" enum that's available! Cool thing, too, is that this is
reflected on your query page as well -- you can query by the new
status. But how's it fit into the existing scheme of things? Looks
like you need to go back and look for instances of the word
"verified" in the perl code for Bugzilla -- wherever you find
"verified", change it to "approved" and you're in business (make sure
that's a case-insensitive search). Although you can query by the enum
field, you can't give something a status of "APPROVED" until you make
the perl changes. Note that this change I mentioned can also be done
by editing checksetup.pl, which automates a lot of this. But you need
to know this stuff anyway, right? I hope this database tutorial has
been useful for you. If you have comments to add, questions,
concerns, etc. please direct them to mbarnson@excitehome.net. Please
direct flames to /dev/null :) Have a nice day! === LINKS === Great
MySQL tutorial site:
http://www.devshed.com/Server_Side/MySQL/</literallayout>
attachments: This table stores all attachments to bugs. It tends to be your
largest table, yet also generally has the fewest entries because file
attachments are so (relatively) large.
bugs: This is the core of your system. The bugs table stores most of the
current information about a bug, with the exception of the info stored in the
other tables.
bugs_activity: This stores information regarding what changes are made to bugs
when -- a history file.
cc: This tiny table simply stores all the CC information for any bug which has
any entries in the CC field of the bug. Note that, like most other tables in
Bugzilla, it does not refer to users by their user names, but by their unique
userid, stored as a primary key in the profiles table.
components: This stores the programs and components (or products and
components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"
(product) field is the full name of the product, rather than some other unique
identifier, like bug_id and user_id are elsewhere in the database.
dependencies: Stores data about those cool dependency trees.
fielddefs: A nifty table that defines other tables. For instance, when you
submit a form that changes the value of "AssignedTo" this table allows
translation to the actual field name "assigned_to" for entry into MySQL.
groups: defines bitmasks for groups. A bitmask is a number that can uniquely
identify group memberships. For instance, say the group that is allowed to
tweak parameters is assigned a value of "1", the group that is allowed to edit
users is assigned a "2", and the group that is allowed to create new groups is
assigned the bitmask of "4". By uniquely combining the group bitmasks (much
like the chmod command in UNIX,) you can identify a user is allowed to tweak
parameters and create groups, but not edit users, by giving him a bitmask of
"5", or a user allowed to edit users and create groups, but not tweak
parameters, by giving him a bitmask of "6" Simple, huh?
If this makes no sense to you, try this at the mysql prompt:
mysql> select * from groups;
You'll see the list, it makes much more sense that way.
keyworddefs: Definitions of keywords to be used
keywords: Unlike what you'd think, this table holds which keywords are
associated with which bug id's.
logincookies: This stores every login cookie ever assigned to you for every
machine you've ever logged into Bugzilla from. Curiously, it never does any
housecleaning -- I see cookies in this file I've not used for months. However,
since Bugzilla never expires your cookie (for convenience' sake), it makes
sense.
longdescs: The meat of bugzilla -- here is where all user comments are stored!
You've only got 2^24 bytes per comment (it's a mediumtext field), so speak
sparingly -- that's only the amount of space the Old Testament from the Bible
would take (uncompressed, 16 megabytes). Each comment is keyed to the
bug_id to which it's attached, so the order is necessarily chronological, for
comments are played back in the order in which they are received.
milestones: Interesting that milestones are associated with a specific product
in this table, but Bugzilla does not yet support differing milestones by
product through the standard configuration interfaces.
namedqueries: This is where everybody stores their "custom queries". Very
cool feature; it beats the tar out of having to bookmark each cool query you
construct.
products: What products you have, whether new bug entries are allowed for the
product, what milestone you're working toward on that product, votes, etc. It
will be nice when the components table supports these same features, so you
could close a particular component for bug entry without having to close an
entire product...
profiles: Ahh, so you were wondering where your precious user information was
stored? Here it is! With the passwords in plain text for all to see! (but
sshh... don't tell your users!)
profiles_activity: Need to know who did what when to who's profile? This'll
tell you, it's a pretty complete history.
shadowlog: I could be mistaken here, but I believe this table tells you when
your shadow database is updated and what commands were used to update it. We
don't use a shadow database at our site yet, so it's pretty empty for us.
versions: Version information for every product
votes: Who voted for what when
watch: Who (according to userid) is watching who's bugs (according to their
userid).
===
THE DETAILS
===
Ahh, so you're wondering just what to do with the information above? At the
mysql prompt, you can view any information about the columns in a table with
this command (where "table" is the name of the table you wish to view):
mysql> show columns from table;
You can also view all the data in a table with this command:
mysql> select * from table;
-- note: this is a very bad idea to do on, for instance, the "bugs" table if
you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or
50,000 bugs play across your screen.
You can limit the display from above a little with the command, where
"column" is the name of the column for which you wish to restrict information:
mysql> select * from table where (column = "some info");
-- or the reverse of this
mysql> select * from table where (column != "some info");
Let's take our example from the introduction, and assume you need to change
the word "verified" to "approved" in the resolution field. We know from the
above information that the resolution is likely to be stored in the "bugs"
table. Note we'll need to change a little perl code as well as this database
change, but I won't plunge into that in this document. Let's verify the
information is stored in the "bugs" table:
mysql> show columns from bugs
(exceedingly long output truncated here)
| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||
Sorry about that long line. We see from this that the "bug status" column is
an "enum field", which is a MySQL peculiarity where a string type field can
only have certain types of entries. While I think this is very cool, it's not
standard SQL. Anyway, we need to add the possible enum field entry
'APPROVED' by altering the "bugs" table.
mysql> ALTER table bugs CHANGE bug_status bug_status
-> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",
-> "VERIFIED", "APPROVED", "CLOSED") not null;
(note we can take three lines or more -- whatever you put in before the
semicolon is evaluated as a single expression)
Now if you do this:
mysql> show columns from bugs;
you'll see that the bug_status field has an extra "APPROVED" enum that's
available! Cool thing, too, is that this is reflected on your query page as
well -- you can query by the new status. But how's it fit into the existing
scheme of things?
Looks like you need to go back and look for instances of the word "verified"
in the perl code for Bugzilla -- wherever you find "verified", change it to
"approved" and you're in business (make sure that's a case-insensitive search).
Although you can query by the enum field, you can't give something a status
of "APPROVED" until you make the perl changes. Note that this change I
mentioned can also be done by editing checksetup.pl, which automates a lot of
this. But you need to know this stuff anyway, right?
</literallayout>
</section>
</section>
</section>
<section id="granttables">
<title>MySQL Permissions &amp; Grant Tables</title>
<note>
<para>The following portion of documentation comes from my answer to an
old discussion of Keystone, a cool product that does trouble-ticket
tracking for IT departments. I wrote this post to the Keystone support
group regarding MySQL grant table permissions, and how to use them
effectively. It is badly in need of updating, as I believe MySQL has
added a field or two to the grant tables since this time, but it serves
as a decent introduction and troubleshooting document for grant table
issues. I used Keynote to track my troubles until I discovered
Bugzilla, which gave me a whole new set of troubles to work on : )
Although it is of limited use, it still has SOME use, thus it's still
included.</para>
<para>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.</para>
</note>
<literallayout>From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999
Date: Mon, 1 Mar 1999 21:37:04 -0700 From: Matthew Barnson
matt_barnson@singletrac.com To: keystone-users@homeport.org Subject:
[keystone-users] Grant Tables FAQ [The following text is in the
"iso-8859-1" character set] [Your display is set for the "US-ASCII"
character set] [Some characters may be displayed incorrectly] Maybe we
can include this rambling message in the Keystone FAQ? It gets asked a
lot, and the only option current listed in the FAQ is
"--skip-grant-tables". Really, you can't go wrong by reading section 6 of
the MySQL manual, at http://www.mysql.com/Manual/manual.html. I am sure
their description is better than mine. MySQL runs fine without
permissions set up correctly if you run the mysql daemon with the
"--skip-grant-tables" option. Running this way denies access to nobody.
Unfortunately, unless you've got yourself firewalled it also opens the
potential for abuse if someone knows you're running it. Additionally, the
default permissions for MySQL allow anyone at localhost access to the
database if the database name begins with "test_" or is named "test"
(i.e. "test_keystone"). You can change the name of your database in the
keystone.conf file ($sys_dbname). This is the way I am doing it for some
of my databases, and it works fine. The methods described below assume
you're running MySQL on the same box as your webserver, and that you
don't mind if your $sys_dbuser for Keystone has superuser access. See
near the bottom of this message for a description of what each field
does. Method #1: 1. cd /var/lib #location where you'll want to run
/usr/bin/mysql_install_db shell script from to get it to work. 2. ln -s
mysql data # soft links the "mysql" directory to "data", which is what
mysql_install_db expects. Alternately, you can edit mysql_install_db and
change all the "./data" references to "./mysql". 3. Edit
/usr/bin/mysql_install_db with your favorite text editor (vi, emacs, jot,
pico, etc.) A) Copy the "INSERT INTO db VALUES
('%','test\_%','','Y','Y','Y','Y','Y','Y');" and paste it immediately
after itself. Chage the 'test\_%' value to 'keystone', or the value of
$sys_dbname in keystone.conf. B) If you are running your keystone
database with any user, you'll need to copy the "INSERT INTO user VALUES
('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');" line
after itself and change 'root' to the name of the keystone database user
($sys_dbuser) in keystone.conf. # adds entries to the script to create
grant tables for specific hosts and users. The user you set up has
super-user access ($sys_dbuser) -- you may or may not want this. The
layout of mysql_install_db is really very uncomplicated. 4.
/usr/bin/mysqladmin shutdown # ya gotta shut it down before you can
reinstall the grant tables! 5. rm -i /var/lib/mysql/mysql/*.IS?' and
answer 'Y' to the deletion questions. # nuke your current grant tables.
This WILL NOT delete any other databases than your grant tables. 6.
/usr/bin/mysql_install_db # run the script you just edited to install
your new grant tables. 7. mysqladmin -u root password (new_password) #
change the root MySQL password, or else anyone on localhost can login to
MySQL as root and make changes. You can skip this step if you want
keystone to connect as root with no password. 8. mysqladmin -u
(webserver_user_name) password (new_password) # change the password of
the $sys_dbuser. Note that you will need to change the password in the
keystone.conf file as well in $sys_dbpasswd, and if your permissions are
set up incorrectly anybody can type the URL to your keystone.conf file
and get the password. Not that this will help them much if your
permissions are set to @localhost. Method #2: easier, but a pain
reproducing if you have to delete your grant tables. This is the
"recommended" method for altering grant tables in MySQL. I don't use it
because I like the other way :) shell&gt; mysql --user=root keystone
mysql&gt; GRANT
SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
FILE, ON keystone.* TO &lt;$sys_dbuser name&gt;@localhost IDENTIFIED BY
'(password)' WITH GRANT OPTION; OR mysql&gt; GRANT ALL PRIVILEGES ON
keystone.* TO &lt;$sys_dbuser name&gt;@localhost IDENTIFIED BY
'(password)' WITH GRANT OPTION; # this grants the required permissions to
the keystone ($sys_dbuser) account defined in keystone.conf. However, if
you are runnning many different MySQL-based apps, as we are, it's
generally better to edit the mysql_install_db script to be able to
quickly reproduce your permissions structure again. Note that the FILE
privelege and WITH GRANT OPTION may not be in your best interest to
include. GRANT TABLE FIELDS EXPLANATION: Quick syntax summary: "%" in
MySQL is a wildcard. I.E., if you are defining your DB table and in the
'host' field and enter '%', that means that any host can access that
database. Of course, that host must also have a valid db user in order to
do anything useful. 'db'=name of database. In our case, it should be
"keystone". "user" should be your "$sys_dbuser" defined in keystone.conf.
Note that you CANNOT add or change a password by using the "INSERT INTO
db (X)" command -- you must change it with the mysql -u command as
defined above. Passwords are stored encrypted in the MySQL database, and
if you try to enter it directly into the table they will not match.
TABLE: USER. Everything after "password" is a privelege granted (Y/N).
This table controls individual user global access rights.
'host','user','password','select','insert','update','delete','index','alter'
,'create','drop','grant','reload','shutdown','process','file' TABLE: DB.
This controls access of USERS to databases.
'host','db','user','select','insert','update','delete','index','alter','crea
te','drop','grant' TABLE: HOST. This controls which HOSTS are allowed
what global access rights. Note that the HOST table, USER table, and DB
table are very closely connected -- if an authorized USER attempts an SQL
request from an unauthorized HOST, she's denied. If a request from an
authorized HOST is not an authorized USER, it is denied. If a globally
authorized USER does not have rights to a certain DB, she's denied. Get
the picture?
'host','db','select','insert','update','delete','index','alter','create','dr
op','grant' You should now have a working knowledge of MySQL grant
tables. If there is anything I've left out of this answer that you feel
is pertinent, or if my instructions don't work for you, please let me
know and I'll re-post this letter again, corrected. I threw it together
one night out of exasperation for all the newbies who don't know squat
about MySQL yet, so it is almost guaranteed to have errors. Once again,
you can't go wrong by reading section 6 of the MySQL manual. It is more
detailed than I! http://www.mysql.com/Manual/manual.html.</literallayout>
</section>
</appendix>
<!-- Keep this comment at the end of the file

263
webtools/bugzilla/docs/sgml/faq.sgml
Просмотреть файл

@ -3,6 +3,10 @@
<appendix id="faq">
<title>The Bugzilla FAQ</title>
<para>
This FAQ includes questions not covered elsewhere in the Guide.
</para>
<qandaset>
@ -121,9 +125,9 @@
</question>
<answer>
<para>
A year has gone by, and I <emphasis>still</emphasis> can't
find any head-to-head comparisons of Bugzilla against
other defect-tracking software. However, from my personal
We can't find any head-to-head comparisons of Bugzilla against
other defect-tracking software. If you know of one, please
get in touch. However, from the author's personal
experience with other bug-trackers, Bugzilla offers
superior performance on commodity hardware, better price
(free!), more developer- friendly features (such as stored
@ -133,24 +137,9 @@
</para>
<para>
If you happen to be a commercial bug-tracker vendor, please
step forward with a rebuttal so I can include it in the
FAQ. We're not in pursuit of Bugzilla ueber alles; we
simply love having a powerful, open-source tool to get our
jobs done.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
How do I change my user name (email address) in Bugzilla?
</para>
</question>
<answer>
<para>
New in 2.16 - go to the Account section of the Preferences. You will
be emailed at both addresses for confirmation.
step forward with a list of advantages your product has over
Bugzilla. We'd be happy to include it in the "Competitors"
section.
</para>
</answer>
</qandaentry>
@ -184,7 +173,7 @@
<question>
<para>
Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</para>
</question>
<answer>
@ -204,42 +193,41 @@
</question>
<answer>
<para>
Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
submissions is "don't break bugzilla.mozilla.org". If it breaks it, your
patch will be reverted faster than you can do a diff.
</para>
<para>
Here's Terry Weissman's comment, for some historical context:
<blockquote>
<para>
[This was] purely my own convention. I wanted a place to put a version of
Perl and other tools that was strictly under my control for the
various webtools, and not subject to anyone else. Edit it to point
to whatever you like.
</para>
<note>
Mozilla.org uses /usr/bonsaitools/bin/perl, because originally
Terry wanted a place to put a version of Perl and other tools
that was strictly under his control.
</para>
<para>
We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version
of perl to /usr/bonsaitools/bin/perl. This will make upgrading
as /usr/bonsaitools/bin/perl, and simply add symlink.
This will make upgrading
your Bugzilla much easier in the future.
</para>
</note>
</blockquote>
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Is there an easy way to change the Bugzilla cookie name?
</para>
</question>
<answer>
<para>
At present, no.
</para>
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq-phb">
<title>Pointy-Haired-Boss Questions</title>
<title>Managerial Questions</title>
<para>
<note>
<para>
The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
Questions likely to be asked by managers. :-)
</para>
</note>
</para>
@ -247,8 +235,8 @@
<qandaentry>
<question>
<para>
Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</para>
</question>
<answer>
@ -262,7 +250,7 @@
<qandaentry>
<question>
<para>
Has anyone you know of already done any Bugzilla integration with
Can Bugzilla integrate with
Perforce (SCM software)?
</para>
</question>
@ -282,11 +270,10 @@
</question>
<answer>
<para>
Absolutely! You can track up to a "soft-limit" of around
64 individual "Products", that can each be composed of as
many "Components" as you want. Check the Administration
section of the Bugzilla Guide for more information regarding
setting up Products and Components.
Absolutely! You can track any number of Products (although you
are limited to about 55 or so if
you are using Product-Based Groups), that can each be composed of any
number of Components.
</para>
</answer>
</qandaentry>
@ -308,7 +295,7 @@
<qandaentry>
<question>
<para>
Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</para>
</question>
@ -346,19 +333,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link.
</para>
</question>
<answer>
<para>If you upgrade to 2.16, the index page has a footer.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -370,7 +344,7 @@
<para>
Yes. Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi">
http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting
facilities.
and graphing facilities.
</para>
<para>
For more advanced reporting, I recommend hooking up a professional
@ -387,7 +361,7 @@
<question>
<para>
Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
email?
</para>
</question>
<answer>
@ -416,7 +390,7 @@
<qandaentry>
<question>
<para>
If there is email notification, do users have to have any particular
Do users have to have any particular
type of email application?
</para>
</question>
@ -438,24 +412,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</para>
</question>
<answer>
<para>
Yes. Place yourself in the "cc" field of the bug you wish to monitor.
Then change your "Notify me of changes to" field in the Email Settings
tab of the User Preferences screen in Bugzilla to the "Only those
bugs which I am listed on the CC line" option.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -520,33 +476,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Can a user re-run a report with a new project, same query?
</para>
</question>
<answer>
<para>
Yes.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Can a user modify an existing report and then save it into another name?
</para>
</question>
<answer>
<para>
You can save an unlimited number of queries in Bugzilla. You are free
to modify them and rename them to your heart's desire.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -562,20 +491,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Can the admin person establish separate group and individual user
privileges?
</para>
</question>
<answer>
<para>
Yes.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -635,9 +550,8 @@
</question>
<answer>
<para>
If Bugzilla is set up correctly from the start, continuing maintenance needs
are minimal and can be completed by unskilled labor. Things like rotate
backup tapes and check log files for the word "error".
If Bugzilla is set up correctly from the start, continuing maintenance
needs are minimal and can be done easily using the web interface.
</para>
<para>
Commercial Bug-tracking software typically costs somewhere upwards
@ -686,52 +600,6 @@
</qandaentry>
</qandadiv>
<qandadiv id="faq-install">
<title>Bugzilla Installation</title>
<qandaentry>
<question>
<para>
How do I download and install Bugzilla?
</para>
</question>
<answer>
<para>
Check <ulink url="http://www.bugzilla.org/">
http://www.bugzilla.org/</ulink> for details.
Read the other parts of this Guide for installation instructions.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
How do I install Bugzilla on Windows NT?
</para>
</question>
<answer>
<para>
Installation on Windows NT has its own section in
this document.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Is there an easy way to change the Bugzilla cookie name?
</para>
</question>
<answer>
<para>
At present, no.
</para>
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq-security">
<title>Bugzilla Security</title>
@ -739,15 +607,14 @@
<question>
<para>
How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide!)?
(I've followed the instructions in the installation section of this guide)?
</para>
</question>
<answer>
<para>
Run MySQL like this: "mysqld --skip-grant-tables". Please remember <emphasis>this
makes MySQL as secure as taping a $100 to the floor of a football stadium
bathroom for safekeeping.</emphasis> Please read the Security section of the
Administration chapter of "The Bugzilla Guide" before proceeding.
bathroom for safekeeping.</emphasis>
</para>
</answer>
</qandaentry>
@ -815,8 +682,8 @@
</question>
<answer>
<para>
Edit the "changedmail" param. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)".
Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: &lt;youremailaddress&gt;".
</para>
</answer>
</qandaentry>
@ -1002,7 +869,7 @@
<qandaentry>
<question>
<para>
I think I've set up MySQL permissions correctly, but bugzilla still can't
I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</para>
</question>
@ -1159,6 +1026,20 @@
<qandadiv id="faq-use">
<title>Bugzilla Usage</title>
<qandaentry>
<question>
<para>
How do I change my user name (email address) in Bugzilla?
</para>
</question>
<answer>
<para>
New in 2.16 - go to the Account section of the Preferences. You will
be emailed at both addresses for confirmation.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -1184,7 +1065,7 @@
<answer>
<para>
The current behavior is acceptable to bugzilla.mozilla.org and most
users. I personally don't like it. You have your choice of patches
users. You have your choice of patches
to change this behavior, however.
<simplelist>
<member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029">
@ -1192,8 +1073,8 @@
<member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153">
"Accept" button automatically assigns to you</ulink></member>
</simplelist>
Note that these patches are somewhat dated. You will need to do the find
and replace manually to apply them. They are very small, though. It is easy.
Note that these patches are somewhat dated. You will need to apply
them manually.
</para>
</answer>
</qandaentry>
@ -1224,7 +1105,7 @@
<answer>
<para>
Yup. Just rename it once you download it, or save it under a different
filename. This will not be fixed anytime too soon, because it would
filename. This will not be fixed anytime soon, because it would
cripple some other functionality.
</para>
</answer>
@ -1288,9 +1169,7 @@
http://bugzilla.mozilla.org/show_bug.cgi?id=49862</ulink>. Ultimately, it's as easy
as adding the "---" priority field to your localconfig file in the appropriate area,
re-running checksetup.pl, and then changing the default priority in your browser using
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "RESOLVED WONTFIX",
there may be a better way to handle this...
"editparams.cgi".
</para>
</answer>
</qandaentry>
@ -1325,7 +1204,7 @@
<listitem>
<para>
Announce your patch and the associated URL
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
the newsgroup (netscape.public.mozilla.webtools). You'll get a really
good, fairly immediate reaction to the implications of your patch,
which will also give us an idea how well-received the change would

54
webtools/bugzilla/docs/sgml/gfdl.sgml
Просмотреть файл

@ -1,10 +1,10 @@
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="gfdl">
<section id="gfdl">
<title>GNU Free Documentation License</title>
<!-- - GNU Project - Free Software Foundation (FSF) -->
<!-- LINK REV="made" HREF="mailto:webmasters@gnu.org" -->
<!-- sect1>
<!-- section>
<title>GNU Free Documentation License</title -->
<para>Version 1.1, March 2000</para>
@ -15,7 +15,7 @@
not allowed.</para>
</blockquote>
<sect1 label="0" id="gfdl-0">
<section label="0" id="gfdl-0">
<title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook, or other
@ -38,9 +38,9 @@
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.</para>
</sect1>
</section>
<sect1 label="1" id="gfdl-1">
<section label="1" id="gfdl-1">
<title>APPLICABILITY AND DEFINITIONS</title>
<para>This License applies to any manual or other work that contains a
@ -98,9 +98,9 @@
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.</para>
</sect1>
</section>
<sect1 label="2" id="gfdl-2">
<section label="2" id="gfdl-2">
<title>VERBATIM COPYING</title>
<para>You may copy and distribute the Document in any medium, either
@ -115,9 +115,9 @@
<para>You may also lend copies, under the same conditions stated above,
and you may publicly display copies.</para>
</sect1>
</section>
<sect1 label="3" id="gfdl-3">
<section label="3" id="gfdl-3">
<title>COPYING IN QUANTITY</title>
<para>If you publish printed copies of the Document numbering more than
@ -154,9 +154,9 @@
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.</para>
</sect1>
</section>
<sect1 label="4" id="gfdl-4">
<section label="4" id="gfdl-4">
<title>MODIFICATIONS</title>
<para>You may copy and distribute a Modified Version of the Document
@ -284,9 +284,9 @@
<para>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.</para>
</sect1>
</section>
<sect1 label="5" id="gfdl-5">
<section label="5" id="gfdl-5">
<title>COMBINING DOCUMENTS</title>
<para>You may combine the Document with other documents released under
@ -310,9 +310,9 @@
"History"; likewise combine any sections entitled "Acknowledgements", and
any sections entitled "Dedications". You must delete all sections
entitled "Endorsements."</para>
</sect1>
</section>
<sect1 label="6" id="gfdl-6">
<section label="6" id="gfdl-6">
<title>COLLECTIONS OF DOCUMENTS</title>
<para>You may make a collection consisting of the Document and other
@ -326,9 +326,9 @@
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.</para>
</sect1>
</section>
<sect1 label="7" id="gfdl-7">
<section label="7" id="gfdl-7">
<title>AGGREGATION WITH INDEPENDENT WORKS</title>
<para>A compilation of the Document or its derivatives with other
@ -345,9 +345,9 @@
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.</para>
</sect1>
</section>
<sect1 label="8" id="gfdl-8">
<section label="8" id="gfdl-8">
<title>TRANSLATION</title>
<para>Translation is considered a kind of modification, so you may
@ -360,9 +360,9 @@
License. In case of a disagreement between the translation and the
original English version of this License, the original English version
will prevail.</para>
</sect1>
</section>
<sect1 label="9" id="gfdl-9">
<section label="9" id="gfdl-9">
<title>TERMINATION</title>
<para>You may not copy, modify, sublicense, or distribute the Document
@ -372,9 +372,9 @@
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.</para>
</sect1>
</section>
<sect1 label="10" id="gfdl-10">
<section label="10" id="gfdl-10">
<title>FUTURE REVISIONS OF THIS LICENSE</title>
<para>The Free Software Foundation may publish new, revised versions of
@ -394,9 +394,9 @@
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.</para>
</sect1>
</section>
<sect1 label="" id="gfdl-howto">
<section label="" id="gfdl-howto">
<title>How to use this License for your documents</title>
<para>To use this License in a document you have written, include a copy
@ -422,8 +422,8 @@
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.</para>
</sect1>
</appendix>
</section>
</section>
<!-- Keep this comment at the end of the file
Local variables:

87
webtools/bugzilla/docs/sgml/glossary.sgml
Просмотреть файл

@ -15,10 +15,7 @@
to keep secret files which would otherwise
compromise your installation - e.g. the
<filename>localconfig</filename>
file contains the password to your database. If this information were
generally available, and remote access to your database turned on,
you risk corruption of your database by computer criminals or the
file contains the password to your database.
curious.</para>
</glossdef>
</glossentry>
@ -56,7 +53,7 @@
<glossdef>
<para>A
<quote>Bug</quote>
<quote>bug</quote>
in Bugzilla refers to an issue entered into the database which has an
associated number, assignments, comments, etc. Some also refer to a
@ -71,33 +68,19 @@
<glossterm>Bug Number</glossterm>
<glossdef>
<para>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
<para>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.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Life Cycle</glossterm>
<glossdef>
<para>A Bug has stages through which it must pass before becoming a
<quote>closed bug</quote>,
including acceptance, resolution, and verification. The
<quote>Bug Life Cycle</quote>
is moderately flexible according to the needs of the organization
using it, though.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bugzilla</glossterm>
<glossdef>
<para>Bugzilla is the industry-standard bug tracking system. It is
quite popular among Open Source enthusiasts.</para>
<para>Bugzilla is the world-leading free software bug tracking system.
</para>
</glossdef>
</glossentry>
</glossdiv>
@ -127,14 +110,11 @@
<acronym>CPAN</acronym>
stands for the
<quote>Comprehensive Perl Archive Network</quote>
. CPAN maintains a large number of extremely useful
<quote>Comprehensive Perl Archive Network</quote>.
CPAN maintains a large number of extremely useful
<glossterm>Perl</glossterm>
modules. By themselves, Perl modules generally do nothing, but when
used as part of a larger program, they provide much-needed algorithms
and functionality.</para>
modules - encapsulated chunks of code for performing a
particular task.</para>
</glossdef>
</glossentry>
</glossdiv>
@ -169,33 +149,16 @@
<quote>Groups</quote>
has a very special meaning to Bugzilla. Bugzilla's main security
mechanism comes by lumping users into groups, and assigning those
groups certain privileges to
mechanism comes by placing users in groups, and assigning those
groups certain privileges to view bugs in particular
<glossterm>Products</glossterm>
and
<glossterm>Components</glossterm>
in the
<glossterm>Bugzilla</glossterm>
database.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss-i">
<title>I</title>
<glossentry id="gloss-infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glossdef>
<para>A loop of information that never ends; see recursion.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss-m">
<title>M</title>
@ -221,10 +184,11 @@
<glossterm id="gloss-product">Product</glossterm>
<glossdef>
<para>A Product is a broad category of types of bugs. In general,
there are several Components to a Product. A Product may also define a
<para>A Product is a broad category of types of bugs, normally
representing a single piece of software or entity. In general,
there are several Components to a Product. A Product may define a
group (used for security) for all bugs entered into
components beneath it.</para>
its Components.</para>
</glossdef>
</glossentry>
@ -262,24 +226,7 @@
bugs over their life cycle, thus the need for the
<quote>QA Contact</quote>
field in a Bug.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss-r">
<title>R</title>
<glossentry id="gloss-recursion" xreflabel="Recursion">
<glossterm>Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
something.
<quote>GNU</quote>, for instance, stands for
<quote>GNU's Not UNIX</quote>,
thus recursing upon itself for definition. For further clarity, see
Infinite Loop.</para>
field in a bug.</para>
</glossdef>
</glossentry>
</glossdiv>

3836
webtools/bugzilla/docs/sgml/installation.sgml
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

41
webtools/bugzilla/docs/sgml/integration.sgml
Просмотреть файл

@ -1,6 +1,6 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB -->
<chapter id="integration">
<section id="integration">
<title>Integrating Bugzilla with Third-Party Tools</title>
<section id="bonsai"
@ -13,43 +13,32 @@
. Using Bonsai, administrators can control open/closed status of trees,
query a fast relational database back-end for change, branch, and comment
information, and view changes made since the last time the tree was
closed. These kinds of changes cause the engineer responsible to be
<quote>on the hook</quote>
(include cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to
<xref linkend="tinderbox" />
and Bugzilla</para>
closed. Bonsai
also integrates with
<xref linkend="tinderbox" />.
</para>
</section>
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
<title>CVS</title>
<para>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway. There have been some files submitted to allow
greater CVS integration, but we need to make certain that Bugzilla is not
tied into one particular software management package.</para>
Bugzilla Email Gateway.</para>
<para>Follow the instructions in the FAQ for enabling Bugzilla e-mail
<para>Follow the instructions in this Guide 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
<quote>[Bug XXXX]</quote>
, and you can have CVS check-in comments append to your Bugzilla bug. If
<quote>[Bug XXXX]</quote>,
and you can have CVS check-in comments append to your Bugzilla bug. If
you have your check-in script include an @resolution field, you can even
change the Bugzilla bug state.</para>
<para>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:
<para>There is also a CVSZilla project, based upon somewhat dated
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
email. Check it out at:
<ulink url="http://homepages.kcbbs.gen.nz/~tonyg/">
http://homepages.kcbbs.gen.nz/~tonyg/</ulink>
, under the
<quote>cvszilla</quote>
link.</para>
http://homepages.kcbbs.gen.nz/~tonyg/</ulink>.
</para>
</section>
<section id="scm"
@ -86,7 +75,7 @@
<para>We need Tinderbox integration information.</para>
</section>
</chapter>
</section>
<!-- Keep this comment at the end of the file
Local variables:

241
webtools/bugzilla/docs/sgml/patches.sgml
Просмотреть файл

@ -26,160 +26,54 @@
setting up your VirtualHost section for Bugzilla with a rule like
this:</para>
<programlisting>
<![CDATA[
<programlisting><![CDATA[
<VirtualHost 12.34.56.78>
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
</VirtualHost>
]]>
</programlisting>
]]></programlisting>
</listitem>
<listitem>
<para>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
<ulink url="http://www.apache.org">http://www.apache.org</ulink>
Please refer to the mod_rewrite documentation at
<ulink url="http://www.apache.org">http://www.apache.org</ulink>.
</para>
</listitem>
</orderedlist>
</section>
<section id="setperl" xreflabel="The setperl.csh Utility">
<title>The setperl.csh Utility</title>
<para>You can use the "setperl.csh" utility to quickly and easily change
the path to perl on all your Bugzilla files. This is a C-shell script; if
you do not have "csh" or "tcsh" in the search path on your system, it
will not work!</para>
<procedure>
<step>
<para>Download the "setperl.csh" utility to your Bugzilla directory
and make it executable.</para>
<substeps>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>cd /your/path/to/bugzilla</command>
</computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.csh</command>
</computeroutput>
</para>
</step>
</substeps>
</step>
<step>
<para>Prepare (and fix) Bugzilla file permissions.</para>
<substeps>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+w *</command>
</computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x duplicates.cgi</command>
</computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod a-x bug_status.html</command>
</computeroutput>
</para>
</step>
</substeps>
</step>
<step>
<para>Run the script:</para>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
</para>
</step>
</procedure>
</section>
<section id="cmdline">
<title>Command-line Bugzilla Queries</title>
<para>Users can query Bugzilla from the command line using this suite of
utilities.</para>
<para>The query.conf file contains the mapping from options to field
<para>There are a suite of Unix utilities for querying Bugzilla from the
command line. They live in the
<filename class="directory">contrib/cmdline</filename>
directory. However, they
have not yet been updated to work with 2.16 (post-templatisation.).
There are three files - <filename>query.conf</filename>,
<filename>buglist</filename> and <filename>bugs</filename>.</para>
<para><filename>query.conf</filename>
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"</para>
make sure these lines do not contain any quoted "option".</para>
<para>buglist is a shell script which submits a Bugzilla query and writes
<para><filename>buglist</filename>
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 character of an option is not "-", it is
treated as if it were prefixed with "--default=".</para>
<para>The columlist is taken from the COLUMNLIST environment variable.
<para>The column list 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
<command>grep COLUMLIST ~/.netscape/cookies</command>
buglist.cgi. If you have already used Bugzilla, grep for COLUMNLIST
in your cookies file to see your current COLUMNLIST setting.</para>
to see your current COLUMNLIST setting.</para>
<para>bugs is a simple shell script which calls buglist and extracts the
<para><filename>bugs</filename> is a simple shell script which calls
<filename>buglist</filename> 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
@ -187,100 +81,13 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
<command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command>
</para>
<para>Akkana says she has good results piping buglist output through
<para>Akkana Peck says she has good results piping
<filename>buglist</filename> output through
<command>w3m -T text/html -dump</command>
</para>
<procedure>
<step>
<para>Download three files:</para>
<substeps>
<step>
<para>
<computeroutput>
<prompt>bash$</prompt>
<command>wget -O query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command>
</computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash$</prompt>
<command>wget -O buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command>
</computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command>
</computeroutput>
</para>
</step>
</substeps>
</step>
<step>
<para>Make your utilities executable:
<computeroutput>
<prompt>bash$</prompt>
<command>chmod u+x buglist bugs</command>
</computeroutput>
</para>
</step>
</procedure>
</section>
<section id="quicksearch">
<title>The Quicksearch Utility</title>
<para>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"</para>
<para>The index.html page has been updated to include the QuickSearch
text box.</para>
<para>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.</para>
<para>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" in the summary, status
whiteboard, product or component name, but not those with the keyword
"foo".</para>
<para>Workarounds for Bugzilla users:
<simplelist>
<member>search for '!foo' (this will find only bugs with the keyword
"foo"</member>
<member>search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</member>
</simplelist>
</para>
<para>When this tool is ported from client-side JavaScript to server-side
Perl, the requirement for hard-coding keywords can be fixed.
<ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This
bug</ulink>
has details.</para>
</section>
</appendix>
<!-- Keep this comment at the end of the file

409
webtools/bugzilla/docs/sgml/using.sgml
Просмотреть файл

@ -1,167 +1,16 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!-- TOC
Chapter: Using Bugzilla
Create an account
Logging in
Setting up preferences
Account Settings
Email Settings
Page Footer
Permissions
Life cycle of a bug
Creating a bug
Checking for duplicates
Overview of all bug fields
Setting bug permissions
The Query Interface
Standard Queries
Email Queries
Boolean Queries
Regexp Queries
The Query Results
Changing Columns
Changing sorting order
Mass changes
Miscellaneous usage hints
-->
<chapter id="using">
<title>Using Bugzilla</title>
<section id="whatis">
<title>What is Bugzilla?</title>
<para>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 originally
written by Terry Weissman in a programming language called "TCL", to
replace a crappy bug-tracking database used internally by Netscape
Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl
it remains to this day. Most commercial defect-tracking software vendors
at the time charged enormous licensing fees, and Bugzilla quickly became
a favorite of the open-source crowd (with its genesis in the open-source
browser project, Mozilla). It is now the de-facto standard
defect-tracking system against which all others are measured.</para>
<para>Bugzilla has matured immensely, and now boasts many advanced
features. These include:
<itemizedlist>
<listitem>
<para>Powerful searching</para>
</listitem>
<listitem>
<para>User-configurable email notifications of bug changes</para>
</listitem>
<listitem>
<para>Full change history</para>
</listitem>
<listitem>
<para>Inter-bug dependency tracking and graphing</para>
</listitem>
<listitem>
<para>Excellent attachment management</para>
</listitem>
<listitem>
<para>Integrated, product-based, granular security schema</para>
</listitem>
<listitem>
<para>Fully security-audited, and runs under Perl's taint mode</para>
</listitem>
<listitem>
<para>A robust, stable RDBMS back-end</para>
</listitem>
<listitem>
<para>Web, XML, email and console interfaces</para>
</listitem>
<listitem>
<para>Completely customisable and/or localisable web user
interface</para>
</listitem>
<listitem>
<para>Extensive configurability</para>
</listitem>
<listitem>
<para>Smooth upgrade pathway between versions</para>
</listitem>
</itemizedlist>
</para>
</section>
<section id="why">
<title>Why Should We Use Bugzilla?</title>
<para>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 the status of defects. This procedure
is error-prone and tends to cause those bugs judged least significant by
developers to be dropped or ignored.</para>
<para>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 keep in touch with their clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood system for accounting for unusual system or software
issues.</para>
<para>But why should
<emphasis>you</emphasis>
use Bugzilla?</para>
<para>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 hardware bug tracking for
luminaries such as Redhat, Loki software, Linux-Mandrake, and VA Systems.
Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems</para>
<para>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 supposed to do
<emphasis>something</emphasis>
today, but you just can't quite remember? Put it in Bugzilla, and you
have a record of it from which you can extrapolate milestones, predict
product versions for integration, and by using Bugzilla's e-mail
integration features be able to follow the discussion trail that led to
critical decisions.</para>
<para>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.</para>
</section>
<section id="how">
<title>How do I use Bugzilla?</title>
<para>This section contains information for end-users of Bugzilla. If you
are administering a Bugzilla installation, please consult the Installing
and Administering Bugzilla portions of this Guide.</para>
<para>There is a Bugzilla test installation, called
<ulink url="http://landfill.tequilarista.org/">Landfill</ulink>
, which you are welcome to play with. However, it does not necessarily
<para>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<ulink url="http://landfill.bugzilla.org/">Landfill</ulink>,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and often runs cutting-edge versions
of Bugzilla for testing, so some things may work slightly differently
than mentioned here.</para>
@ -173,8 +22,8 @@ Chapter: Using Bugzilla
Consult with the administrator responsible for your installation of
Bugzilla for the URL you should use to access it. If you're
test-driving Bugzilla, use this URL:
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/bugzilla-tip/</ulink>
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/">
http://landfill.bugzilla.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
@ -200,18 +49,17 @@ Chapter: Using Bugzilla
<listitem>
<para>Click the
<quote>Log In</quote>
link in the yellow area at the bottom of the page in your browser,
enter your email address and password into the spaces provided, and
click
<quote>Login</quote>
.</para>
<quote>Login</quote>.
</para>
</listitem>
</orderedlist>
<para>You are now logged in. Bugzilla uses cookies for authentication,
so (unless your IP address changes) you should not have to log in
<para>You are now logged in. Bugzilla uses cookies for authentication
so, unless your IP address changes, you should not have to log in
again.</para>
</section>
@ -221,75 +69,65 @@ Chapter: Using Bugzilla
<para>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1">
url="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1">
Bug 1 on Landfill</ulink>
is a good example. Note that the names of most fields are hyperlinks;
is a good example. Note that the labels for most fields are hyperlinks;
clicking them will take you to context-sensitive help on that
particular field.</para>
particular field. Fields marked * may not be present on every
installation of Bugzilla.</para>
<orderedlist>
<listitem>
<para>
<emphasis>Product and Component</emphasis>
: Bugs are divided up by Product and Component, with a Product
<emphasis>Product and Component</emphasis>:
Bugs are divided up by Product and Component, with a Product
having one or more Components in it. For example,
bugzilla.mozilla.org's "Bugzilla" Product is composed of several
Components:
<simplelist>
<member>
<emphasis>Administration:</emphasis>
Administration of a Bugzilla installation.</member>
<member>
<emphasis>Bugzilla-General:</emphasis>
Anything that doesn't fit in the other components, or spans
multiple components.</member>
<member>
<emphasis>Creating/Changing Bugs:</emphasis>
Creating, changing, and viewing bugs.</member>
<member>
<emphasis>Documentation:</emphasis>
The Bugzilla documentation, including The Bugzilla Guide.</member>
<member>
<emphasis>Email:</emphasis>
Anything to do with email sent by Bugzilla.</member>
<member>
<emphasis>Installation:</emphasis>
The installation process of Bugzilla.</member>
<member>
<emphasis>Query/Buglist:</emphasis>
Anything to do with searching for bugs and viewing the
buglists.</member>
<member>
<emphasis>Reporting/Charting:</emphasis>
Getting reports from Bugzilla.</member>
<member>
<emphasis>User Accounts:</emphasis>
Anything about managing a user account from the user's perspective.
Saved queries, creating accounts, changing passwords, logging in,
etc.</member>
<member>
<emphasis>User Interface:</emphasis>
General issues having to do with the user interface cosmetics (not
functionality) including cosmetic issues, HTML templates,
etc.</member>
@ -301,46 +139,41 @@ Chapter: Using Bugzilla
<para>
<emphasis>Status and Resolution:</emphasis>
A bug passes through several Statuses in its lifetime, and ends up
in the RESOLVED status, with one of a set of Resolutions (e.g.
FIXED, INVALID.) The different possible values for Status and
Resolution on your installation will be documented in the
These define exactly what state the bug is in - from not even
being confirmed as a bug, through to being fixed and the fix
confirmed by Quality Assurance. The different possible values for
Status and Resolution on your installation should be documented in the
context-sensitive help for those items.</para>
</listitem>
<listitem>
<para>
<emphasis>Assigned To:</emphasis>
The person responsible for fixing the bug.</para>
</listitem>
<listitem>
<para>
<emphasis>URL:</emphasis>
<emphasis>*URL:</emphasis>
A URL associated with the bug, if any.</para>
</listitem>
<listitem>
<para>
<emphasis>Summary:</emphasis>
A one-sentence summary of the problem.</para>
</listitem>
<listitem>
<para>
<emphasis>Status Whiteboard:</emphasis>
<emphasis>*Status Whiteboard:</emphasis>
(a.k.a. Whiteboard) A free-form text area for adding short notes
and tags to a bug.</para>
</listitem>
<listitem>
<para>
<emphasis>Keywords:</emphasis>
<emphasis>*Keywords:</emphasis>
The administrator can define keywords which you can use to tag and
categorise bugs - e.g. The Mozilla Project has keywords like crash
and regression.</para>
@ -349,7 +182,6 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Platform and OS:</emphasis>
These indicate the computing environment where the bug was
found.</para>
</listitem>
@ -357,7 +189,6 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Version:</emphasis>
The "Version" field is usually used for versions of a product which
have been released, and is set to indicate which versions of a
Component have the particular problem the bug report is
@ -367,7 +198,6 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Priority:</emphasis>
The bug assignee uses this field to prioritise his or her bugs.
It's a good idea not to change this on other people's bugs.</para>
</listitem>
@ -375,7 +205,6 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Severity:</emphasis>
This indicates how severe the problem is - from blocker
("application unusable") to trivial ("minor cosmetic issue"). You
can also use this field to indicate whether a bug is an enhancement
@ -384,8 +213,7 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Target:</emphasis>
<emphasis>*Target:</emphasis>
(a.k.a. Target Milestone) A future version by which the bug is to
be fixed. e.g. The Bugzilla Project's milestones for future
Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not
@ -396,29 +224,25 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Reporter:</emphasis>
The person who filed the bug.</para>
</listitem>
<listitem>
<para>
<emphasis>CC list:</emphasis>
A list of people who get mail when the bug changes.</para>
</listitem>
<listitem>
<para>
<emphasis>Attachments:</emphasis>
You can attach files (e.g. testcases or patches) to bugs. If there
are any attachments, they are listed in this section.</para>
</listitem>
<listitem>
<para>
<emphasis>Dependencies:</emphasis>
<emphasis>*Dependencies:</emphasis>
If this bug cannot be fixed unless other bugs are fixed (depends
on), or this bug stops other bugs being fixed (blocks), their
numbers are recorded here.</para>
@ -426,15 +250,13 @@ Chapter: Using Bugzilla
<listitem>
<para>
<emphasis>Votes:</emphasis>
<emphasis>*Votes:</emphasis>
Whether this bug has any votes.</para>
</listitem>
<listitem>
<para>
<emphasis>Additional Comments:</emphasis>
You can add your two cents to the bug discussion here, if you have
something worthwhile to say.</para>
</listitem>
@ -447,8 +269,8 @@ Chapter: Using Bugzilla
<para>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
can play with it here:
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/query.cgi">
landfill.bugzilla.org/bugzilla-tip/query.cgi</ulink>
.</para>
@ -460,7 +282,7 @@ Chapter: Using Bugzilla
<para>Highly advanced querying is done using Boolean Charts, which have
their own
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">
url="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html">
context-sensitive help</ulink>
.</para>
@ -517,10 +339,9 @@ Chapter: Using Bugzilla
<para>Years of bug writing experience has been distilled for your
reading pleasure into the
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html">
Bug Writing Guidelines</ulink>
. While some of the advice is Mozilla-specific, the basic principles of
url="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html">
Bug Writing Guidelines</ulink>.
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
@ -532,15 +353,13 @@ Chapter: Using Bugzilla
<orderedlist>
<listitem>
<para>Go to
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/">
Landfill</ulink>
in your browser and click
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report</ulink>
.</para>
url="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report</ulink>.
</para>
</listitem>
<listitem>
@ -560,29 +379,138 @@ Chapter: Using Bugzilla
</section>
</section>
<section id="init4me">
<section id="hintsandtips">
<title>Hints and Tips</title>
<para>This section distills some Bugzilla tips and best practices
that have been developed.</para>
<section>
<title>Autolinkification</title>
<para>Bugzilla comments are plain text - so posting HTML will result
in literal HTML tags rather than being interpreted by a browser.
However, Bugzilla will automatically make hyperlinks out of certain
sorts of text in comments. For example, the text
http://www.bugzilla.org will be turned into
<ulink url="http://www.bugzilla.org">http://www.bugzilla.org</ulink>.
Other strings which get linkified in the obvious manner are:
<simplelist>
<member>bug 12345</member>
<member>bug 23456, comment 53</member>
<member>attachment 4321</member>
<member>mailto:george@example.com</member>
<member>george@example.com</member>
<member>ftp://ftp.mozilla.org</member>
<member>Most other sorts of URL</member>
</simplelist>
</para>
<para>A corollary here is that if you type a bug number in a comment,
you should put the word "bug" before it, so it gets autolinkified
for the convenience of others.
</para>
</section>
<section id="quicksearch">
<title>Quicksearch</title>
<para>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
"<filename>foo|bar</filename>"
into Quicksearch would search for "foo" or "bar" in the
summary and status whiteboard of a bug; adding
"<filename>:BazProduct</filename>" would
search only in that product.
</para>
<para>You'll find the Quicksearch box on Bugzilla's
front page, along with a
<ulink url="../../quicksearch.html">Help</ulink>
link which details how to use it.</para>
</section>
<section id="commenting">
<title>Comments</title>
<para>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
Otherwise, you may spam people unnecessarily with bug mail.
To take an example: a user can set up their account to filter out messages
where someone just adds themselves to the CC field of a bug
(which happens a lot.) If you come along, add yourself to the CC field,
and add a comment saying "Adding self to CC", then that person
gets a pointless piece of mail they would otherwise have avoided.
</para>
<para>
Don't use sigs in comments. Signing your name ("Bill") is acceptable,
particularly if you do it out of habit, but full mail/news-style
four line ASCII art creations are not.
</para>
</section>
<section id="attachments">
<title>Attachments</title>
<para>
Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
bloat the bug for everyone who wants to read it, and cause people to
receive fat, useless mails.
</para>
<para>Trim screenshots. There's no need to show the whole screen if
you are pointing out a single-pixel problem.
</para>
<para>Don't attach simple test cases (e.g. one HTML file, one
CSS file and an image) as a ZIP file. Instead, upload them in
reverse order and edit the referring file so that they point to the
attached files. This way, the test case works immediately
out of the bug.
</para>
</section>
<section>
<title>Filing Bugs</title>
<para>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</para>
<para>
You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</para>
<para>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</para>
</section>
</section>
<section id="userpreferences">
<title>User Preferences</title>
<para>You can customise various aspects of Bugzilla, via the "Edit prefs"
link in the page footer, once you have logged in, e.g. to
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1">
Landfill</ulink>
. The preferences are split into four tabs.</para>
<para>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
The preferences are split into four tabs:</para>
<section id="accountsettings" xreflabel="Account Settings">
<title>Account Settings</title>
<para>On this tab, you can change your basic Account Settings,
<para>On this tab, you can change your basic account information,
including your password, email address and real name. For security
reasons, in order to change anything on this page you must type your
<emphasis>current</emphasis>
password into the
<quote>Password</quote>
field. If you attempt to change your email address, a confirmation
field at the top of the page.
If you attempt to change your email address, a confirmation
email is sent to both the old and new addresses, with a link to use to
confirm the change. This helps to prevent account hijacking.</para>
</section>
@ -600,28 +528,27 @@ Chapter: Using Bugzilla
"Users to watch" text entry box you can receive a copy of all the
bugmail of other users (security settings permitting.) This powerful
functionality enables seamless transitions as developers change
projects, managers wish to get in touch with the issues faced by their
direct reports, or users go on vacation.</para>
projects or users go on holiday.</para>
<note>
<para>This option may not be available in all Bugzilla installations.
Ask your administrator.</para>
<para>The ability to watch other users may not be available in all
Bugzilla installations. If you can't see it, ask your
administrator.</para>
</note>
</section>
<section id="footersettings">
<title>Page Footer</title>
<para>By default, this page is quite barren. However, if you explore
the Search 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. Once you have a stored query, you can come
<para>On the Search page, you can store queries in Bugzilla, so if you
regularly run a particular query it is just a drop-down menu away.
Once you have a stored query, you can come
here to request that it also be displayed in your page footer.</para>
</section>
<section id="permissionsettings">
<title>Permissions</title>
<para>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
are in, and whether you can edit bugs or perform various administration

66
webtools/bugzilla/docs/sgml/variants.sgml
Просмотреть файл

@ -1,5 +1,5 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
<appendix id="variants" xreflabel="Bugzilla Variants and Competitors">
<title>Bugzilla Variants and Competitors</title>
<para>I created this section to answer questions about Bugzilla competitors
@ -13,13 +13,12 @@
<section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>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
<para>Red Hat Bugzilla is a fork of Bugzilla 2.8.
One of its major benefits is the ability
to work with Oracle, MySQL, and PostGreSQL databases serving as the
back-end, instead of just MySQL. Dave Lawrence has worked very hard to
keep Red Hat Bugzilla up-to-date, and many people prefer the
snappier-looking page layout of Red Hat Bugzilla to the default
Mozilla-standard formatting.</para>
back-end, instead of just MySQL. Dave Lawrence of Red Hat is
active in the Bugzilla community, and we hope to see a reunification
of the fork before too long.</para>
<para>URL:
<ulink url="http://bugzilla.redhat.com/bugzilla/">
@ -30,38 +29,26 @@
<section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at
<ulink url="http://fenris.lokigames.com/">
http://fenris.lokigames.com</ulink>
. It is a fork from Bugzilla.</para>
<para>Fenris was a fork from Bugzilla made by Loki Games; when
Loki went into receivership, it died. While Loki's other code lives on,
its custodians recommend Bugzilla for future bug-tracker deployments.
</para>
</section>
<section id="variant-issuezilla" xreflabel="Issuezilla">
<title>Issuezilla</title>
<para>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,
<xref linkend="variant-scarab" />
, is under heavy development and looks promising!</para>
<para>URL:
<ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">
http://issuezilla.tigris.org/servlets/ProjectHome</ulink>
</para>
<para>Issuezilla was another fork from Bugzilla, made by collab.net and
hosted at tigris.org. It is also dead; the primary focus of bug-tracking
at tigris.org is their Java-based bug-tracker,
<xref linkend="variant-scarab"/>.</para>
</section>
<section id="variant-scarab"
xreflabel="Scarab, a newfangled Java-based issue tracker">
<section id="variant-scarab" xreflabel="Scarab">
<title>Scarab</title>
<para>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.</para>
<para>Scarab is a new open source bug-tracking system built using Java
Serlet technology. It is currently at version 1.0 beta 8.</para>
<para>URL:
<ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink>
@ -72,32 +59,29 @@
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used as
such through the
<quote>jobs</quote>
such through the <quote>jobs</quote>
functionality.</para>
<para>
<para>URL:
<ulink url="http://www.perforce.com/perforce/technotes/note052.html">
http://www.perforce.com/perforce/technotes/note052.html
</ulink>
http://www.perforce.com/perforce/technotes/note052.html</para>
</para>
</section>
<section id="variant-sourceforge" xreflabel="SourceForge">
<title>SourceForge</title>
<para>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!</para>
<para>SourceForge is a way of coordinating geographically
distributed free software and open source projects over the Internet.
It has a built-in bug tracker, but it's not highly thought of.</para>
<para>URL:
<ulink url="http://www.sourceforge.net">
http://www.sourceforge.net</ulink>
</para>
</section>
</chapter>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:

7113
webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

54
webtools/bugzilla/docs/xml/Bugzilla-Guide.xml
Просмотреть файл

@ -16,7 +16,7 @@
<!ENTITY database SYSTEM "database.sgml">
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
<!ENTITY introduction SYSTEM "introduction.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!ENTITY bz "http://www.bugzilla.org/">
@ -61,33 +61,35 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<title>The Bugzilla Guide</title>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
<affiliation>
<address><email>mbarnson@sisna.com</email></address>
</affiliation>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
</author>
<author>
<firstname>The</firstname>
<othername>Bugzilla</othername>
<surname>Team</surname>
</author>
</authorgroup>
<abstract>
<para>
This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
</para>
<para>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a Bugzilla bug.
<para>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a bug filed in
<ulink url="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation">mozilla.org's Bugzilla</ulink>.
</para>
</abstract>
<keywordset>
<keyword>Bugzilla</keyword>
<keyword>Guide</keyword>
@ -104,6 +106,9 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<!-- About This Guide -->
&about;
<!-- Introduction -->
&introduction;
<!-- Using Bugzilla -->
&using;
@ -113,26 +118,17 @@ try to avoid clutter and feel free to waste space in the code to make it more re
<!-- Administering Bugzilla -->
&administration;
<!-- Integrating Bugzilla with Third-Party Tools -->
&integration;
<!-- Major Bugzilla Variants -->
&variants;
<!-- Appendix: The Frequently Asked Questions -->
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware;
<!-- Appendix: The Database Schema -->
&database;
<!-- Appendix: Custom Patches -->
&patches;
<!-- Appendix: The GNU Free Documentation License -->
&gfdl;
<!-- Appendix: Major Bugzilla Variants -->
&variants;
<!-- Glossary -->
&glossary;

104
webtools/bugzilla/docs/xml/about.xml
Просмотреть файл

@ -4,40 +4,6 @@
<chapter id="about">
<title>About This Guide</title>
<section id="aboutthisguide">
<title>Purpose and Scope of this Guide</title>
<para>
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.
</para>
<para>
This release of the Bugzilla Guide is the
<emphasis>&bzg-ver;</emphasis> release. It is so named that it
may match the current version of Bugzilla. The numbering
tradition stems from that used for many free software projects,
in which <emphasis>even-numbered</emphasis> point releases (1.2,
1.14, etc.) are considered "stable releases", intended for
public consumption; on the other hand,
<emphasis>odd-numbered</emphasis> point releases (1.3, 2.09,
etc.) are considered unstable <emphasis>development</emphasis>
releases intended for advanced users, systems administrators,
developers, and those who enjoy a lot of pain.
</para>
<para>
Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<ulink url="&bz;">&bz;</ulink>. Intermediate releases will have
a minor revision number following a period. The current version
of Bugzilla, as of this writing (&bzg-date;) is &bz-ver;; if
something were seriously wrong with that edition of the Guide,
subsequent releases would receive an additional dotted-decimal
digit to indicate the update (&bzg-ver;.1, &bzg-ver;.2, etc.).
Got it? Good.
</para>
</section>
<section id="copyright">
<title>Copyright Information</title>
<blockquote>
@ -48,8 +14,7 @@
License, Version 1.1 or any later version published by the
Free Software Foundation; with no Invariant Sections, no
Front-Cover Texts, and with no Back-Cover Texts. A copy of
the license is included in the section entitled "GNU Free
Documentation License".
the license is included below.
</para>
</blockquote>
<para>
@ -57,6 +22,11 @@
copyright, or publishing this document in non-electronic form,
please contact &bzg-auth;.
</para>
<!-- The GNU Free Documentation License -->
&gfdl;
</section>
<section id="disclaimer">
@ -64,12 +34,11 @@
<para>
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
document may cause your girlfriend to leave you, your cats to
pee on your furniture and clothing, your computer to cease
functioning, your boss to fire you, and global thermonuclear
war. Proceed with caution.
This document may contain errors
and inaccuracies that may damage your system, cause your partner
to leave you, your boss to fire you, your cats to
pee on your furniture and clothing, and global thermonuclear
war. Proceed with caution.
</para>
<para>
All copyrights are held by their respective owners, unless
@ -100,7 +69,7 @@
team members, Netscape Communications, America Online Inc., and
any affiliated developers or sponsors assume no liability for
your use of this product. You have the source code to this
product, and are responsible for auditing it yourself to insure
product, and are responsible for auditing it yourself to ensure
your security needs are met.
</para>
</section>
@ -110,7 +79,8 @@
<section id="newversions">
<title>New Versions</title>
<para>
This is the &bzg-ver; version of The Bugzilla Guide. If you are
This is the &bzg-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla. 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.
@ -134,9 +104,16 @@
</itemizedlist>
</para>
<para>
The latest version of this document can be checked out via CVS.
Please follow the instructions available at <ulink
url="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ulink>, and check out the <filename>mozilla/webtools/bugzilla/docs/</filename> branch.
The latest version of this document can always be checked out via CVS.
Please follow the instructions available at
<ulink url="http://www.mozilla.org/cvs.html">the Mozilla CVS page</ulink>,
and check out the <filename>mozilla/webtools/bugzilla/docs/</filename>
subtree.
</para>
<para>
The Bugzilla Guide is currently only available in English.
If you would like to volunteer to translate it, please contact
<ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
</para>
</section>
@ -144,13 +121,14 @@
<title>Credits</title>
<para>
The people listed below have made enormous contributions to the
creation of this Guide, through their dedicated hacking efforts,
creation of this Guide, through their writing, dedicated hacking efforts,
numerous e-mail and IRC support sessions, and overall excellent
contribution to the Bugzilla community:
</para>
<para>
<ulink url="mailto://mbarnson@sisna.com">Matthew P. Barnson</ulink>
for pulling together the Bugzilla Guide and shepherding it to 2.14.
for the Herculaean task of pulling together the Bugzilla Guide and
shepherding it to 2.14.
</para>
<para>
<ulink url="mailto://terry@mozilla.org">Terry Weissman</ulink>
@ -158,13 +136,13 @@
README upon which the UNIX installation documentation is largely based.
</para>
<para>
<ulink url="mailto://tara@tequilarista.org">Tara
Hernandez</ulink> for keeping Bugzilla development going
strong after Terry left Mozilla.org
<ulink url="mailto://tara@tequilarista.org">Tara Hernandez</ulink>
for keeping Bugzilla development going
strong after Terry left mozilla.org
</para>
<para>
<ulink url="mailto://dkl@redhat.com">Dave Lawrence</ulink> for
providing insight into the key differences between Red Hat's
<ulink url="mailto://dkl@redhat.com">Dave Lawrence</ulink>
for providing insight into the key differences between Red Hat's
customized Bugzilla, and being largely responsible for the "Red
Hat Bugzilla" appendix
</para>
@ -174,8 +152,8 @@
questions and arguments on irc.mozilla.org in #mozwebtools
</para>
<para>
Last but not least, all the members of the <ulink
url="news://news.mozilla.org/netscape/public/mozilla/webtools"> netscape.public.mozilla.webtools</ulink> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
Last but not least, all the members of the
<ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools"> netscape.public.mozilla.webtools</ulink> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
</para>
<para>
Thanks also go to the following people for significant contributions
@ -183,19 +161,7 @@
</para>
<para>
Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
</para>
</section>
<section id="translations">
<title>Translations</title>
<para>
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
<email>mozilla-webtools@mozilla.org</email>, and arrange with
&bzg-auth; to check it into CVS.
Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham.
</para>
</section>

1628
webtools/bugzilla/docs/xml/administration.xml
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

15
webtools/bugzilla/docs/xml/conventions.xml
Просмотреть файл

@ -6,7 +6,7 @@
<primary>conventions</primary>
</indexterm>
<para>This document uses the following conventions</para>
<para>This document uses the following conventions:</para>
<informaltable frame="none">
<tgroup cols="2">
@ -34,7 +34,7 @@
<entry>
<tip>
<para>Warm jar lids under the hot tap to loosen them.</para>
<para>Would you like a breath mint?</para>
</tip>
</entry>
</row>
@ -63,7 +63,7 @@
<entry>File Names</entry>
<entry>
<filename>file.extension</filename>
<filename>filename</filename>
</entry>
</row>
@ -138,12 +138,9 @@
<entry>Code Example</entry>
<entry>
<programlisting>
<sgmltag class="starttag">para</sgmltag>
Beginning and end of paragraph
<sgmltag class="endtag">para</sgmltag>
</programlisting>
<programlisting><sgmltag class="starttag">para</sgmltag>
Beginning and end of paragraph
<sgmltag class="endtag">para</sgmltag></programlisting>
</entry>
</row>
</tbody>

466
webtools/bugzilla/docs/xml/database.xml
Просмотреть файл

@ -123,10 +123,10 @@
! You should have locked your security down like the installation
instructions told you to. You can find details on locking down
your database in the Bugzilla FAQ in this directory (under
"Security"), or more robust security generalities in the MySQL
searchable documentation at
http://www.mysql.com/php/manual.php3?section=Privilege_system
.</para>
"Security"), or more robust security generalities in the
<ulink url="http://www.mysql.com/php/manual.php3?section=Privilege_system">MySQL
searchable documentation</ulink>.
</para>
</listitem>
<listitem>
@ -150,13 +150,6 @@
<command>use bugs;</command>
</para>
<note>
<para>Don't forget the
<quote>;</quote>
at the end of each line, or you'll be kicking yourself
later.</para>
</note>
</listitem>
</orderedlist>
</para>
@ -169,273 +162,212 @@
<para>
<prompt>mysql&gt;</prompt>
<command>show tables from bugs;</command>
</para>
<para>you'll be able to see all the
<para>you'll be able to see the names of all the
<quote>spreadsheets</quote>
(tables) in your database.</para>
(tables) in your database. It is similar to a file system, only
faster and more robust for certain types of operations.</para>
<para>From the command issued above, ou should have some
output that looks like this:
<programlisting>
+-------------------+
| Tables in bugs |
+-------------------+
| attachments |
| bugs |
| bugs_activity |
| cc |
| components |
| dependencies |
| fielddefs |
| groups |
| keyworddefs |
| keywords |
| logincookies |
| longdescs |
| milestones |
| namedqueries |
| products |
| profiles |
| profiles_activity |
| shadowlog |
| tokens |
| versions |
| votes |
| watch |
+-------------------+
</programlisting>
</para>
<para>From the command issued above, ou should have some output that
looks like this:
<programlisting>+-------------------+ | Tables in bugs |
+-------------------+ | attachments | | bugs | | bugs_activity | | cc
| | components | | dependencies | | fielddefs | | groups | |
keyworddefs | | keywords | | logincookies | | longdescs | |
milestones | | namedqueries | | products | | profiles | |
profiles_activity | | shadowlog | | tokens | | versions | | votes | |
watch | +-------------------+</programlisting>
</para>
<literallayout>
Here's an overview of what each table does. Most columns in each table have
descriptive names that make it fairly trivial to figure out their jobs.
<literallayout>Here's an overview of what each table does. Most
columns in each table have descriptive names that make it fairly
trivial to figure out their jobs. attachments: This table stores all
attachments to bugs. It tends to be your largest table, yet also
generally has the fewest entries because file attachments are so
(relatively) large. bugs: This is the core of your system. The bugs
table stores most of the current information about a bug, with the
exception of the info stored in the other tables. bugs_activity: This
stores information regarding what changes are made to bugs when -- a
history file. cc: This tiny table simply stores all the CC
information for any bug which has any entries in the CC field of the
bug. Note that, like most other tables in Bugzilla, it does not refer
to users by their user names, but by their unique userid, stored as a
primary key in the profiles table. components: This stores the
programs and components (or products and components, in newer
Bugzilla parlance) for Bugzilla. Curiously, the "program" (product)
field is the full name of the product, rather than some other unique
identifier, like bug_id and user_id are elsewhere in the database.
dependencies: Stores data about those cool dependency trees.
fielddefs: A nifty table that defines other tables. For instance,
when you submit a form that changes the value of "AssignedTo" this
table allows translation to the actual field name "assigned_to" for
entry into MySQL. groups: defines bitmasks for groups. A bitmask is a
number that can uniquely identify group memberships. For instance,
say the group that is allowed to tweak parameters is assigned a value
of "1", the group that is allowed to edit users is assigned a "2",
and the group that is allowed to create new groups is assigned the
bitmask of "4". By uniquely combining the group bitmasks (much like
the chmod command in UNIX,) you can identify a user is allowed to
tweak parameters and create groups, but not edit users, by giving him
a bitmask of "5", or a user allowed to edit users and create groups,
but not tweak parameters, by giving him a bitmask of "6" Simple, huh?
If this makes no sense to you, try this at the mysql prompt:
mysql&gt; select * from groups; You'll see the list, it makes much
more sense that way. keyworddefs: Definitions of keywords to be used
keywords: Unlike what you'd think, this table holds which keywords
are associated with which bug id's. logincookies: This stores every
login cookie ever assigned to you for every machine you've ever
logged into Bugzilla from. Curiously, it never does any housecleaning
-- I see cookies in this file I've not used for months. However,
since Bugzilla never expires your cookie (for convenience' sake), it
makes sense. longdescs: The meat of bugzilla -- here is where all
user comments are stored! You've only got 2^24 bytes per comment
(it's a mediumtext field), so speak sparingly -- that's only the
amount of space the Old Testament from the Bible would take
(uncompressed, 16 megabytes). Each comment is keyed to the bug_id to
which it's attached, so the order is necessarily chronological, for
comments are played back in the order in which they are received.
milestones: Interesting that milestones are associated with a
specific product in this table, but Bugzilla does not yet support
differing milestones by product through the standard configuration
interfaces. namedqueries: This is where everybody stores their
"custom queries". Very cool feature; it beats the tar out of having
to bookmark each cool query you construct. products: What products
you have, whether new bug entries are allowed for the product, what
milestone you're working toward on that product, votes, etc. It will
be nice when the components table supports these same features, so
you could close a particular component for bug entry without having
to close an entire product... profiles: Ahh, so you were wondering
where your precious user information was stored? Here it is! With the
passwords in plain text for all to see! (but sshh... don't tell your
users!) profiles_activity: Need to know who did what when to who's
profile? This'll tell you, it's a pretty complete history. shadowlog:
I could be mistaken here, but I believe this table tells you when
your shadow database is updated and what commands were used to update
it. We don't use a shadow database at our site yet, so it's pretty
empty for us. versions: Version information for every product votes:
Who voted for what when watch: Who (according to userid) is watching
who's bugs (according to their userid). === THE DETAILS === Ahh, so
you're wondering just what to do with the information above? At the
mysql prompt, you can view any information about the columns in a
table with this command (where "table" is the name of the table you
wish to view): mysql&gt; show columns from table; You can also view
all the data in a table with this command: mysql&gt; select * from
table; -- note: this is a very bad idea to do on, for instance, the
"bugs" table if you have 50,000 bugs. You'll be sitting there a while
until you ctrl-c or 50,000 bugs play across your screen. You can
limit the display from above a little with the command, where
"column" is the name of the column for which you wish to restrict
information: mysql&gt; select * from table where (column = "some
info"); -- or the reverse of this mysql&gt; select * from table where
(column != "some info"); Let's take our example from the
introduction, and assume you need to change the word "verified" to
"approved" in the resolution field. We know from the above
information that the resolution is likely to be stored in the "bugs"
table. Note we'll need to change a little perl code as well as this
database change, but I won't plunge into that in this document. Let's
verify the information is stored in the "bugs" table: mysql&gt; show
columns from bugs (exceedingly long output truncated here) |
bug_status|
enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL
| UNCONFIRMED|| Sorry about that long line. We see from this that the
"bug status" column is an "enum field", which is a MySQL peculiarity
where a string type field can only have certain types of entries.
While I think this is very cool, it's not standard SQL. Anyway, we
need to add the possible enum field entry 'APPROVED' by altering the
"bugs" table. mysql&gt; ALTER table bugs CHANGE bug_status bug_status
-&gt; enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",
-&gt; "VERIFIED", "APPROVED", "CLOSED") not null; (note we can take
three lines or more -- whatever you put in before the semicolon is
evaluated as a single expression) Now if you do this: mysql&gt; show
columns from bugs; you'll see that the bug_status field has an extra
"APPROVED" enum that's available! Cool thing, too, is that this is
reflected on your query page as well -- you can query by the new
status. But how's it fit into the existing scheme of things? Looks
like you need to go back and look for instances of the word
"verified" in the perl code for Bugzilla -- wherever you find
"verified", change it to "approved" and you're in business (make sure
that's a case-insensitive search). Although you can query by the enum
field, you can't give something a status of "APPROVED" until you make
the perl changes. Note that this change I mentioned can also be done
by editing checksetup.pl, which automates a lot of this. But you need
to know this stuff anyway, right? I hope this database tutorial has
been useful for you. If you have comments to add, questions,
concerns, etc. please direct them to mbarnson@excitehome.net. Please
direct flames to /dev/null :) Have a nice day! === LINKS === Great
MySQL tutorial site:
http://www.devshed.com/Server_Side/MySQL/</literallayout>
attachments: This table stores all attachments to bugs. It tends to be your
largest table, yet also generally has the fewest entries because file
attachments are so (relatively) large.
bugs: This is the core of your system. The bugs table stores most of the
current information about a bug, with the exception of the info stored in the
other tables.
bugs_activity: This stores information regarding what changes are made to bugs
when -- a history file.
cc: This tiny table simply stores all the CC information for any bug which has
any entries in the CC field of the bug. Note that, like most other tables in
Bugzilla, it does not refer to users by their user names, but by their unique
userid, stored as a primary key in the profiles table.
components: This stores the programs and components (or products and
components, in newer Bugzilla parlance) for Bugzilla. Curiously, the "program"
(product) field is the full name of the product, rather than some other unique
identifier, like bug_id and user_id are elsewhere in the database.
dependencies: Stores data about those cool dependency trees.
fielddefs: A nifty table that defines other tables. For instance, when you
submit a form that changes the value of "AssignedTo" this table allows
translation to the actual field name "assigned_to" for entry into MySQL.
groups: defines bitmasks for groups. A bitmask is a number that can uniquely
identify group memberships. For instance, say the group that is allowed to
tweak parameters is assigned a value of "1", the group that is allowed to edit
users is assigned a "2", and the group that is allowed to create new groups is
assigned the bitmask of "4". By uniquely combining the group bitmasks (much
like the chmod command in UNIX,) you can identify a user is allowed to tweak
parameters and create groups, but not edit users, by giving him a bitmask of
"5", or a user allowed to edit users and create groups, but not tweak
parameters, by giving him a bitmask of "6" Simple, huh?
If this makes no sense to you, try this at the mysql prompt:
mysql> select * from groups;
You'll see the list, it makes much more sense that way.
keyworddefs: Definitions of keywords to be used
keywords: Unlike what you'd think, this table holds which keywords are
associated with which bug id's.
logincookies: This stores every login cookie ever assigned to you for every
machine you've ever logged into Bugzilla from. Curiously, it never does any
housecleaning -- I see cookies in this file I've not used for months. However,
since Bugzilla never expires your cookie (for convenience' sake), it makes
sense.
longdescs: The meat of bugzilla -- here is where all user comments are stored!
You've only got 2^24 bytes per comment (it's a mediumtext field), so speak
sparingly -- that's only the amount of space the Old Testament from the Bible
would take (uncompressed, 16 megabytes). Each comment is keyed to the
bug_id to which it's attached, so the order is necessarily chronological, for
comments are played back in the order in which they are received.
milestones: Interesting that milestones are associated with a specific product
in this table, but Bugzilla does not yet support differing milestones by
product through the standard configuration interfaces.
namedqueries: This is where everybody stores their "custom queries". Very
cool feature; it beats the tar out of having to bookmark each cool query you
construct.
products: What products you have, whether new bug entries are allowed for the
product, what milestone you're working toward on that product, votes, etc. It
will be nice when the components table supports these same features, so you
could close a particular component for bug entry without having to close an
entire product...
profiles: Ahh, so you were wondering where your precious user information was
stored? Here it is! With the passwords in plain text for all to see! (but
sshh... don't tell your users!)
profiles_activity: Need to know who did what when to who's profile? This'll
tell you, it's a pretty complete history.
shadowlog: I could be mistaken here, but I believe this table tells you when
your shadow database is updated and what commands were used to update it. We
don't use a shadow database at our site yet, so it's pretty empty for us.
versions: Version information for every product
votes: Who voted for what when
watch: Who (according to userid) is watching who's bugs (according to their
userid).
===
THE DETAILS
===
Ahh, so you're wondering just what to do with the information above? At the
mysql prompt, you can view any information about the columns in a table with
this command (where "table" is the name of the table you wish to view):
mysql> show columns from table;
You can also view all the data in a table with this command:
mysql> select * from table;
-- note: this is a very bad idea to do on, for instance, the "bugs" table if
you have 50,000 bugs. You'll be sitting there a while until you ctrl-c or
50,000 bugs play across your screen.
You can limit the display from above a little with the command, where
"column" is the name of the column for which you wish to restrict information:
mysql> select * from table where (column = "some info");
-- or the reverse of this
mysql> select * from table where (column != "some info");
Let's take our example from the introduction, and assume you need to change
the word "verified" to "approved" in the resolution field. We know from the
above information that the resolution is likely to be stored in the "bugs"
table. Note we'll need to change a little perl code as well as this database
change, but I won't plunge into that in this document. Let's verify the
information is stored in the "bugs" table:
mysql> show columns from bugs
(exceedingly long output truncated here)
| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL | UNCONFIRMED||
Sorry about that long line. We see from this that the "bug status" column is
an "enum field", which is a MySQL peculiarity where a string type field can
only have certain types of entries. While I think this is very cool, it's not
standard SQL. Anyway, we need to add the possible enum field entry
'APPROVED' by altering the "bugs" table.
mysql> ALTER table bugs CHANGE bug_status bug_status
-> enum("UNCONFIRMED", "NEW", "ASSIGNED", "REOPENED", "RESOLVED",
-> "VERIFIED", "APPROVED", "CLOSED") not null;
(note we can take three lines or more -- whatever you put in before the
semicolon is evaluated as a single expression)
Now if you do this:
mysql> show columns from bugs;
you'll see that the bug_status field has an extra "APPROVED" enum that's
available! Cool thing, too, is that this is reflected on your query page as
well -- you can query by the new status. But how's it fit into the existing
scheme of things?
Looks like you need to go back and look for instances of the word "verified"
in the perl code for Bugzilla -- wherever you find "verified", change it to
"approved" and you're in business (make sure that's a case-insensitive search).
Although you can query by the enum field, you can't give something a status
of "APPROVED" until you make the perl changes. Note that this change I
mentioned can also be done by editing checksetup.pl, which automates a lot of
this. But you need to know this stuff anyway, right?
</literallayout>
</section>
</section>
</section>
<section id="granttables">
<title>MySQL Permissions &amp; Grant Tables</title>
<note>
<para>The following portion of documentation comes from my answer to an
old discussion of Keystone, a cool product that does trouble-ticket
tracking for IT departments. I wrote this post to the Keystone support
group regarding MySQL grant table permissions, and how to use them
effectively. It is badly in need of updating, as I believe MySQL has
added a field or two to the grant tables since this time, but it serves
as a decent introduction and troubleshooting document for grant table
issues. I used Keynote to track my troubles until I discovered
Bugzilla, which gave me a whole new set of troubles to work on : )
Although it is of limited use, it still has SOME use, thus it's still
included.</para>
<para>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.</para>
</note>
<literallayout>From matt_barnson@singletrac.com Wed Jul 7 09:00:07 1999
Date: Mon, 1 Mar 1999 21:37:04 -0700 From: Matthew Barnson
matt_barnson@singletrac.com To: keystone-users@homeport.org Subject:
[keystone-users] Grant Tables FAQ [The following text is in the
"iso-8859-1" character set] [Your display is set for the "US-ASCII"
character set] [Some characters may be displayed incorrectly] Maybe we
can include this rambling message in the Keystone FAQ? It gets asked a
lot, and the only option current listed in the FAQ is
"--skip-grant-tables". Really, you can't go wrong by reading section 6 of
the MySQL manual, at http://www.mysql.com/Manual/manual.html. I am sure
their description is better than mine. MySQL runs fine without
permissions set up correctly if you run the mysql daemon with the
"--skip-grant-tables" option. Running this way denies access to nobody.
Unfortunately, unless you've got yourself firewalled it also opens the
potential for abuse if someone knows you're running it. Additionally, the
default permissions for MySQL allow anyone at localhost access to the
database if the database name begins with "test_" or is named "test"
(i.e. "test_keystone"). You can change the name of your database in the
keystone.conf file ($sys_dbname). This is the way I am doing it for some
of my databases, and it works fine. The methods described below assume
you're running MySQL on the same box as your webserver, and that you
don't mind if your $sys_dbuser for Keystone has superuser access. See
near the bottom of this message for a description of what each field
does. Method #1: 1. cd /var/lib #location where you'll want to run
/usr/bin/mysql_install_db shell script from to get it to work. 2. ln -s
mysql data # soft links the "mysql" directory to "data", which is what
mysql_install_db expects. Alternately, you can edit mysql_install_db and
change all the "./data" references to "./mysql". 3. Edit
/usr/bin/mysql_install_db with your favorite text editor (vi, emacs, jot,
pico, etc.) A) Copy the "INSERT INTO db VALUES
('%','test\_%','','Y','Y','Y','Y','Y','Y');" and paste it immediately
after itself. Chage the 'test\_%' value to 'keystone', or the value of
$sys_dbname in keystone.conf. B) If you are running your keystone
database with any user, you'll need to copy the "INSERT INTO user VALUES
('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');" line
after itself and change 'root' to the name of the keystone database user
($sys_dbuser) in keystone.conf. # adds entries to the script to create
grant tables for specific hosts and users. The user you set up has
super-user access ($sys_dbuser) -- you may or may not want this. The
layout of mysql_install_db is really very uncomplicated. 4.
/usr/bin/mysqladmin shutdown # ya gotta shut it down before you can
reinstall the grant tables! 5. rm -i /var/lib/mysql/mysql/*.IS?' and
answer 'Y' to the deletion questions. # nuke your current grant tables.
This WILL NOT delete any other databases than your grant tables. 6.
/usr/bin/mysql_install_db # run the script you just edited to install
your new grant tables. 7. mysqladmin -u root password (new_password) #
change the root MySQL password, or else anyone on localhost can login to
MySQL as root and make changes. You can skip this step if you want
keystone to connect as root with no password. 8. mysqladmin -u
(webserver_user_name) password (new_password) # change the password of
the $sys_dbuser. Note that you will need to change the password in the
keystone.conf file as well in $sys_dbpasswd, and if your permissions are
set up incorrectly anybody can type the URL to your keystone.conf file
and get the password. Not that this will help them much if your
permissions are set to @localhost. Method #2: easier, but a pain
reproducing if you have to delete your grant tables. This is the
"recommended" method for altering grant tables in MySQL. I don't use it
because I like the other way :) shell&gt; mysql --user=root keystone
mysql&gt; GRANT
SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
FILE, ON keystone.* TO &lt;$sys_dbuser name&gt;@localhost IDENTIFIED BY
'(password)' WITH GRANT OPTION; OR mysql&gt; GRANT ALL PRIVILEGES ON
keystone.* TO &lt;$sys_dbuser name&gt;@localhost IDENTIFIED BY
'(password)' WITH GRANT OPTION; # this grants the required permissions to
the keystone ($sys_dbuser) account defined in keystone.conf. However, if
you are runnning many different MySQL-based apps, as we are, it's
generally better to edit the mysql_install_db script to be able to
quickly reproduce your permissions structure again. Note that the FILE
privelege and WITH GRANT OPTION may not be in your best interest to
include. GRANT TABLE FIELDS EXPLANATION: Quick syntax summary: "%" in
MySQL is a wildcard. I.E., if you are defining your DB table and in the
'host' field and enter '%', that means that any host can access that
database. Of course, that host must also have a valid db user in order to
do anything useful. 'db'=name of database. In our case, it should be
"keystone". "user" should be your "$sys_dbuser" defined in keystone.conf.
Note that you CANNOT add or change a password by using the "INSERT INTO
db (X)" command -- you must change it with the mysql -u command as
defined above. Passwords are stored encrypted in the MySQL database, and
if you try to enter it directly into the table they will not match.
TABLE: USER. Everything after "password" is a privelege granted (Y/N).
This table controls individual user global access rights.
'host','user','password','select','insert','update','delete','index','alter'
,'create','drop','grant','reload','shutdown','process','file' TABLE: DB.
This controls access of USERS to databases.
'host','db','user','select','insert','update','delete','index','alter','crea
te','drop','grant' TABLE: HOST. This controls which HOSTS are allowed
what global access rights. Note that the HOST table, USER table, and DB
table are very closely connected -- if an authorized USER attempts an SQL
request from an unauthorized HOST, she's denied. If a request from an
authorized HOST is not an authorized USER, it is denied. If a globally
authorized USER does not have rights to a certain DB, she's denied. Get
the picture?
'host','db','select','insert','update','delete','index','alter','create','dr
op','grant' You should now have a working knowledge of MySQL grant
tables. If there is anything I've left out of this answer that you feel
is pertinent, or if my instructions don't work for you, please let me
know and I'll re-post this letter again, corrected. I threw it together
one night out of exasperation for all the newbies who don't know squat
about MySQL yet, so it is almost guaranteed to have errors. Once again,
you can't go wrong by reading section 6 of the MySQL manual. It is more
detailed than I! http://www.mysql.com/Manual/manual.html.</literallayout>
</section>
</appendix>
<!-- Keep this comment at the end of the file

263
webtools/bugzilla/docs/xml/faq.xml
Просмотреть файл

@ -3,6 +3,10 @@
<appendix id="faq">
<title>The Bugzilla FAQ</title>
<para>
This FAQ includes questions not covered elsewhere in the Guide.
</para>
<qandaset>
@ -121,9 +125,9 @@
</question>
<answer>
<para>
A year has gone by, and I <emphasis>still</emphasis> can't
find any head-to-head comparisons of Bugzilla against
other defect-tracking software. However, from my personal
We can't find any head-to-head comparisons of Bugzilla against
other defect-tracking software. If you know of one, please
get in touch. However, from the author's personal
experience with other bug-trackers, Bugzilla offers
superior performance on commodity hardware, better price
(free!), more developer- friendly features (such as stored
@ -133,24 +137,9 @@
</para>
<para>
If you happen to be a commercial bug-tracker vendor, please
step forward with a rebuttal so I can include it in the
FAQ. We're not in pursuit of Bugzilla ueber alles; we
simply love having a powerful, open-source tool to get our
jobs done.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
How do I change my user name (email address) in Bugzilla?
</para>
</question>
<answer>
<para>
New in 2.16 - go to the Account section of the Preferences. You will
be emailed at both addresses for confirmation.
step forward with a list of advantages your product has over
Bugzilla. We'd be happy to include it in the "Competitors"
section.
</para>
</answer>
</qandaentry>
@ -184,7 +173,7 @@
<question>
<para>
Why MySQL? I'm interested in seeing Bugzilla run on
Oracle/Sybase/Msql/PostgreSQL/MSSQL?
Oracle/Sybase/Msql/PostgreSQL/MSSQL.
</para>
</question>
<answer>
@ -204,42 +193,41 @@
</question>
<answer>
<para>
Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making
submissions is "don't break bugzilla.mozilla.org". If it breaks it, your
patch will be reverted faster than you can do a diff.
</para>
<para>
Here's Terry Weissman's comment, for some historical context:
<blockquote>
<para>
[This was] purely my own convention. I wanted a place to put a version of
Perl and other tools that was strictly under my control for the
various webtools, and not subject to anyone else. Edit it to point
to whatever you like.
</para>
<note>
Mozilla.org uses /usr/bonsaitools/bin/perl, because originally
Terry wanted a place to put a version of Perl and other tools
that was strictly under his control.
</para>
<para>
We always recommend that, if possible, you keep the path
as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools
and /usr/bonsaitools/bin directory, then symlink your version
of perl to /usr/bonsaitools/bin/perl. This will make upgrading
as /usr/bonsaitools/bin/perl, and simply add symlink.
This will make upgrading
your Bugzilla much easier in the future.
</para>
</note>
</blockquote>
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Is there an easy way to change the Bugzilla cookie name?
</para>
</question>
<answer>
<para>
At present, no.
</para>
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq-phb">
<title>Pointy-Haired-Boss Questions</title>
<title>Managerial Questions</title>
<para>
<note>
<para>
The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
Questions likely to be asked by managers. :-)
</para>
</note>
</para>
@ -247,8 +235,8 @@
<qandaentry>
<question>
<para>
Is Bugzilla web-based or do you have to have specific software or
specific operating system on your machine?
Is Bugzilla web-based, or do you have to have specific software or
a specific operating system on your machine?
</para>
</question>
<answer>
@ -262,7 +250,7 @@
<qandaentry>
<question>
<para>
Has anyone you know of already done any Bugzilla integration with
Can Bugzilla integrate with
Perforce (SCM software)?
</para>
</question>
@ -282,11 +270,10 @@
</question>
<answer>
<para>
Absolutely! You can track up to a "soft-limit" of around
64 individual "Products", that can each be composed of as
many "Components" as you want. Check the Administration
section of the Bugzilla Guide for more information regarding
setting up Products and Components.
Absolutely! You can track any number of Products (although you
are limited to about 55 or so if
you are using Product-Based Groups), that can each be composed of any
number of Components.
</para>
</answer>
</qandaentry>
@ -308,7 +295,7 @@
<qandaentry>
<question>
<para>
Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
Does Bugzilla allow attachments (text, screenshots, URLs etc)? If yes,
are there any that are NOT allowed?
</para>
</question>
@ -346,19 +333,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
The index.html page doesn't show the footer. It's really annoying to have
to go to the querypage just to check my "my bugs" link.
</para>
</question>
<answer>
<para>If you upgrade to 2.16, the index page has a footer.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -370,7 +344,7 @@
<para>
Yes. Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi">
http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting
facilities.
and graphing facilities.
</para>
<para>
For more advanced reporting, I recommend hooking up a professional
@ -387,7 +361,7 @@
<question>
<para>
Is there email notification and if so, what do you see when you get an
email? Do you see bug number and title or is it only the number?
email?
</para>
</question>
<answer>
@ -416,7 +390,7 @@
<qandaentry>
<question>
<para>
If there is email notification, do users have to have any particular
Do users have to have any particular
type of email application?
</para>
</question>
@ -438,24 +412,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
If I just wanted to track certain bugs, as they go through life, can I
set it up to alert me via email whenever that bug changes, whether it be
owner, status or description etc.?
</para>
</question>
<answer>
<para>
Yes. Place yourself in the "cc" field of the bug you wish to monitor.
Then change your "Notify me of changes to" field in the Email Settings
tab of the User Preferences screen in Bugzilla to the "Only those
bugs which I am listed on the CC line" option.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -520,33 +476,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Can a user re-run a report with a new project, same query?
</para>
</question>
<answer>
<para>
Yes.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Can a user modify an existing report and then save it into another name?
</para>
</question>
<answer>
<para>
You can save an unlimited number of queries in Bugzilla. You are free
to modify them and rename them to your heart's desire.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -562,20 +491,6 @@
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Can the admin person establish separate group and individual user
privileges?
</para>
</question>
<answer>
<para>
Yes.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -635,9 +550,8 @@
</question>
<answer>
<para>
If Bugzilla is set up correctly from the start, continuing maintenance needs
are minimal and can be completed by unskilled labor. Things like rotate
backup tapes and check log files for the word "error".
If Bugzilla is set up correctly from the start, continuing maintenance
needs are minimal and can be done easily using the web interface.
</para>
<para>
Commercial Bug-tracking software typically costs somewhere upwards
@ -686,52 +600,6 @@
</qandaentry>
</qandadiv>
<qandadiv id="faq-install">
<title>Bugzilla Installation</title>
<qandaentry>
<question>
<para>
How do I download and install Bugzilla?
</para>
</question>
<answer>
<para>
Check <ulink url="http://www.bugzilla.org/">
http://www.bugzilla.org/</ulink> for details.
Read the other parts of this Guide for installation instructions.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
How do I install Bugzilla on Windows NT?
</para>
</question>
<answer>
<para>
Installation on Windows NT has its own section in
this document.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
Is there an easy way to change the Bugzilla cookie name?
</para>
</question>
<answer>
<para>
At present, no.
</para>
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq-security">
<title>Bugzilla Security</title>
@ -739,15 +607,14 @@
<question>
<para>
How do I completely disable MySQL security if it's giving me problems
(I've followed the instructions in the installation section of this guide!)?
(I've followed the instructions in the installation section of this guide)?
</para>
</question>
<answer>
<para>
Run MySQL like this: "mysqld --skip-grant-tables". Please remember <emphasis>this
makes MySQL as secure as taping a $100 to the floor of a football stadium
bathroom for safekeeping.</emphasis> Please read the Security section of the
Administration chapter of "The Bugzilla Guide" before proceeding.
bathroom for safekeeping.</emphasis>
</para>
</answer>
</qandaentry>
@ -815,8 +682,8 @@
</question>
<answer>
<para>
Edit the "changedmail" param. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)".
Edit the "changedmail" Param. Replace "To:" with "X-Real-To:",
replace "Cc:" with "X-Real-CC:", and add a "To: &lt;youremailaddress&gt;".
</para>
</answer>
</qandaentry>
@ -1002,7 +869,7 @@
<qandaentry>
<question>
<para>
I think I've set up MySQL permissions correctly, but bugzilla still can't
I think I've set up MySQL permissions correctly, but Bugzilla still can't
connect.
</para>
</question>
@ -1159,6 +1026,20 @@
<qandadiv id="faq-use">
<title>Bugzilla Usage</title>
<qandaentry>
<question>
<para>
How do I change my user name (email address) in Bugzilla?
</para>
</question>
<answer>
<para>
New in 2.16 - go to the Account section of the Preferences. You will
be emailed at both addresses for confirmation.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
@ -1184,7 +1065,7 @@
<answer>
<para>
The current behavior is acceptable to bugzilla.mozilla.org and most
users. I personally don't like it. You have your choice of patches
users. You have your choice of patches
to change this behavior, however.
<simplelist>
<member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029">
@ -1192,8 +1073,8 @@
<member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153">
"Accept" button automatically assigns to you</ulink></member>
</simplelist>
Note that these patches are somewhat dated. You will need to do the find
and replace manually to apply them. They are very small, though. It is easy.
Note that these patches are somewhat dated. You will need to apply
them manually.
</para>
</answer>
</qandaentry>
@ -1224,7 +1105,7 @@
<answer>
<para>
Yup. Just rename it once you download it, or save it under a different
filename. This will not be fixed anytime too soon, because it would
filename. This will not be fixed anytime soon, because it would
cripple some other functionality.
</para>
</answer>
@ -1288,9 +1169,7 @@
http://bugzilla.mozilla.org/show_bug.cgi?id=49862</ulink>. Ultimately, it's as easy
as adding the "---" priority field to your localconfig file in the appropriate area,
re-running checksetup.pl, and then changing the default priority in your browser using
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "RESOLVED WONTFIX",
there may be a better way to handle this...
"editparams.cgi".
</para>
</answer>
</qandaentry>
@ -1325,7 +1204,7 @@
<listitem>
<para>
Announce your patch and the associated URL
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in
(http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
the newsgroup (netscape.public.mozilla.webtools). You'll get a really
good, fairly immediate reaction to the implications of your patch,
which will also give us an idea how well-received the change would

54
webtools/bugzilla/docs/xml/gfdl.xml
Просмотреть файл

@ -1,10 +1,10 @@
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="gfdl">
<section id="gfdl">
<title>GNU Free Documentation License</title>
<!-- - GNU Project - Free Software Foundation (FSF) -->
<!-- LINK REV="made" HREF="mailto:webmasters@gnu.org" -->
<!-- sect1>
<!-- section>
<title>GNU Free Documentation License</title -->
<para>Version 1.1, March 2000</para>
@ -15,7 +15,7 @@
not allowed.</para>
</blockquote>
<sect1 label="0" id="gfdl-0">
<section label="0" id="gfdl-0">
<title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook, or other
@ -38,9 +38,9 @@
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.</para>
</sect1>
</section>
<sect1 label="1" id="gfdl-1">
<section label="1" id="gfdl-1">
<title>APPLICABILITY AND DEFINITIONS</title>
<para>This License applies to any manual or other work that contains a
@ -98,9 +98,9 @@
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.</para>
</sect1>
</section>
<sect1 label="2" id="gfdl-2">
<section label="2" id="gfdl-2">
<title>VERBATIM COPYING</title>
<para>You may copy and distribute the Document in any medium, either
@ -115,9 +115,9 @@
<para>You may also lend copies, under the same conditions stated above,
and you may publicly display copies.</para>
</sect1>
</section>
<sect1 label="3" id="gfdl-3">
<section label="3" id="gfdl-3">
<title>COPYING IN QUANTITY</title>
<para>If you publish printed copies of the Document numbering more than
@ -154,9 +154,9 @@
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.</para>
</sect1>
</section>
<sect1 label="4" id="gfdl-4">
<section label="4" id="gfdl-4">
<title>MODIFICATIONS</title>
<para>You may copy and distribute a Modified Version of the Document
@ -284,9 +284,9 @@
<para>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.</para>
</sect1>
</section>
<sect1 label="5" id="gfdl-5">
<section label="5" id="gfdl-5">
<title>COMBINING DOCUMENTS</title>
<para>You may combine the Document with other documents released under
@ -310,9 +310,9 @@
"History"; likewise combine any sections entitled "Acknowledgements", and
any sections entitled "Dedications". You must delete all sections
entitled "Endorsements."</para>
</sect1>
</section>
<sect1 label="6" id="gfdl-6">
<section label="6" id="gfdl-6">
<title>COLLECTIONS OF DOCUMENTS</title>
<para>You may make a collection consisting of the Document and other
@ -326,9 +326,9 @@
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.</para>
</sect1>
</section>
<sect1 label="7" id="gfdl-7">
<section label="7" id="gfdl-7">
<title>AGGREGATION WITH INDEPENDENT WORKS</title>
<para>A compilation of the Document or its derivatives with other
@ -345,9 +345,9 @@
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.</para>
</sect1>
</section>
<sect1 label="8" id="gfdl-8">
<section label="8" id="gfdl-8">
<title>TRANSLATION</title>
<para>Translation is considered a kind of modification, so you may
@ -360,9 +360,9 @@
License. In case of a disagreement between the translation and the
original English version of this License, the original English version
will prevail.</para>
</sect1>
</section>
<sect1 label="9" id="gfdl-9">
<section label="9" id="gfdl-9">
<title>TERMINATION</title>
<para>You may not copy, modify, sublicense, or distribute the Document
@ -372,9 +372,9 @@
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.</para>
</sect1>
</section>
<sect1 label="10" id="gfdl-10">
<section label="10" id="gfdl-10">
<title>FUTURE REVISIONS OF THIS LICENSE</title>
<para>The Free Software Foundation may publish new, revised versions of
@ -394,9 +394,9 @@
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.</para>
</sect1>
</section>
<sect1 label="" id="gfdl-howto">
<section label="" id="gfdl-howto">
<title>How to use this License for your documents</title>
<para>To use this License in a document you have written, include a copy
@ -422,8 +422,8 @@
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.</para>
</sect1>
</appendix>
</section>
</section>
<!-- Keep this comment at the end of the file
Local variables:

87
webtools/bugzilla/docs/xml/glossary.xml
Просмотреть файл

@ -15,10 +15,7 @@
to keep secret files which would otherwise
compromise your installation - e.g. the
<filename>localconfig</filename>
file contains the password to your database. If this information were
generally available, and remote access to your database turned on,
you risk corruption of your database by computer criminals or the
file contains the password to your database.
curious.</para>
</glossdef>
</glossentry>
@ -56,7 +53,7 @@
<glossdef>
<para>A
<quote>Bug</quote>
<quote>bug</quote>
in Bugzilla refers to an issue entered into the database which has an
associated number, assignments, comments, etc. Some also refer to a
@ -71,33 +68,19 @@
<glossterm>Bug Number</glossterm>
<glossdef>
<para>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
<para>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.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Life Cycle</glossterm>
<glossdef>
<para>A Bug has stages through which it must pass before becoming a
<quote>closed bug</quote>,
including acceptance, resolution, and verification. The
<quote>Bug Life Cycle</quote>
is moderately flexible according to the needs of the organization
using it, though.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bugzilla</glossterm>
<glossdef>
<para>Bugzilla is the industry-standard bug tracking system. It is
quite popular among Open Source enthusiasts.</para>
<para>Bugzilla is the world-leading free software bug tracking system.
</para>
</glossdef>
</glossentry>
</glossdiv>
@ -127,14 +110,11 @@
<acronym>CPAN</acronym>
stands for the
<quote>Comprehensive Perl Archive Network</quote>
. CPAN maintains a large number of extremely useful
<quote>Comprehensive Perl Archive Network</quote>.
CPAN maintains a large number of extremely useful
<glossterm>Perl</glossterm>
modules. By themselves, Perl modules generally do nothing, but when
used as part of a larger program, they provide much-needed algorithms
and functionality.</para>
modules - encapsulated chunks of code for performing a
particular task.</para>
</glossdef>
</glossentry>
</glossdiv>
@ -169,33 +149,16 @@
<quote>Groups</quote>
has a very special meaning to Bugzilla. Bugzilla's main security
mechanism comes by lumping users into groups, and assigning those
groups certain privileges to
mechanism comes by placing users in groups, and assigning those
groups certain privileges to view bugs in particular
<glossterm>Products</glossterm>
and
<glossterm>Components</glossterm>
in the
<glossterm>Bugzilla</glossterm>
database.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss-i">
<title>I</title>
<glossentry id="gloss-infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glossdef>
<para>A loop of information that never ends; see recursion.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss-m">
<title>M</title>
@ -221,10 +184,11 @@
<glossterm id="gloss-product">Product</glossterm>
<glossdef>
<para>A Product is a broad category of types of bugs. In general,
there are several Components to a Product. A Product may also define a
<para>A Product is a broad category of types of bugs, normally
representing a single piece of software or entity. In general,
there are several Components to a Product. A Product may define a
group (used for security) for all bugs entered into
components beneath it.</para>
its Components.</para>
</glossdef>
</glossentry>
@ -262,24 +226,7 @@
bugs over their life cycle, thus the need for the
<quote>QA Contact</quote>
field in a Bug.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss-r">
<title>R</title>
<glossentry id="gloss-recursion" xreflabel="Recursion">
<glossterm>Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
something.
<quote>GNU</quote>, for instance, stands for
<quote>GNU's Not UNIX</quote>,
thus recursing upon itself for definition. For further clarity, see
Infinite Loop.</para>
field in a bug.</para>
</glossdef>
</glossentry>
</glossdiv>

3836
webtools/bugzilla/docs/xml/installation.xml
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше