Documentation update; added docs/sgml, docs/html, docs/txt.

No text version of The Bugzilla Guide availabe yet, however.

17 files changed, 6956 insertions, 0 deletions

diff --git a/docs/sgml/Bugzilla-Guide.sgml b/docs/sgml/Bugzilla-Guide.sgml
new file mode 100644
index 000000000..a6bcaaeca
--- /dev/null
+++ b/docs/sgml/Bugzilla-Guide.sgml
@@ -0,0 +1,177 @@
+<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+
+<!-- Include macros -->
+<!ENTITY about SYSTEM "about.sgml">
+<!ENTITY conventions SYSTEM "conventions.sgml">
+<!ENTITY doc-index SYSTEM "index.sgml">
+<!ENTITY faq SYSTEM "faq.sgml">
+<!ENTITY gfdl SYSTEM "gfdl.sgml">
+<!ENTITY glossary SYSTEM "glossary.sgml">
+<!ENTITY installation SYSTEM "installation.sgml">
+<!ENTITY administration SYSTEM "administration.sgml">
+<!ENTITY using SYSTEM "using.sgml">
+<!ENTITY integration SYSTEM "integration.sgml">
+<!ENTITY future SYSTEM "future.sgml">
+<!ENTITY index SYSTEM "index.sgml">
+<!ENTITY database SYSTEM "database.sgml">
+<!ENTITY patches SYSTEM "patches.sgml">
+<!ENTITY variants SYSTEM "variants.sgml">
+
+]>
+
+<!-- Coding standards for this document 
+
+1.  Preface new or modified sections with a comment stating who
+ modified it and when; please also use the "authorinitials" tag.
+
+2.  There is no "two".
+
+3.  Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
+
+4.  Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
+
+5.  Ensure all documents compile cleanly to HTML after modification.
+  The errors "DTD Declaration not allowed here" and "DTDDECL catalog types not supported"
+ are normal errors to be expected when compiling the whole guide.
+
+6.  Try to index important terms wherever possible.
+
+7.  Follow coding standards at http://www.linuxdoc.org.
+
+8.  All tags should be lowercase (needsfix)
+
+9.  Code being submitted for review should use the 
+"review" tag. Documentation on this is available at 
+http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
+ under section 4.9.4, "Making notes on the text while it's being written".
+
+10.  Please use sensible spacing.  The comments at the very end of each Guide
+ file define reasonable defaults for PSGML mode in EMACS.
+  Double-indent tags, use double spacing whenever possible,
+ try to avoid clutter and feel free to waste space in the code to make it more readable.
+
+-->
+
+<BOOK ID="index">
+
+<!-- Header -->
+
+  <BOOKINFO>
+    <TITLE>The Bugzilla Guide</TITLE>
+    <PUBDATE>v2.11.1, 06 March 2001</PUBDATE>
+    <AUTHOR>
+      <FIRSTNAME>Matthew</FIRSTNAME>
+      <OTHERNAME>P.</OTHERNAME>
+      <SURNAME>Barnson</SURNAME>
+      <affiliation>
+	<address><email>barnboy@trilobyte.net</email></address>
+      </affiliation>
+    </AUTHOR>
+
+    <ABSTRACT>
+      <PARA>This is the documentation for Bugzilla, the Mozilla bug-tracking system.</PARA>
+    </ABSTRACT>
+
+    <REVHISTORY>
+      <REVISION>
+	<REVNUMBER>v2.11</REVNUMBER>
+	<DATE>20 December 2000</DATE>
+	<AUTHORINITIALS>MPB</AUTHORINITIALS>
+	<REVREMARK>Converted the README, FAQ, and DATABASE information into SGML
+	  docbook format.</REVREMARK>
+      </REVISION>
+
+      <revision>
+	<revnumber>2.11.1</revnumber>
+	<date>06 March 2001</date>
+	<revremark>
+	  Took way too long to revise this for 2.12 release.
+	  Updated FAQ to use qandaset tags instead of literallayout,
+	  cleaned up administration section, added User Guide section,
+	  miscellaneous FAQ updates and third-party integration information.
+	  From this point on all new tags are lowercase in preparation for the
+	  2.13 release of the Guide in XML format instead of SGML.
+	</revremark>
+      </revision>
+    </REVHISTORY>
+
+    <KEYWORDSET>
+      <KEYWORD>Bugzilla</KEYWORD>
+      <KEYWORD>Guide</KEYWORD>
+      <KEYWORD>installation</KEYWORD>
+      <KEYWORD>FAQ</KEYWORD>
+      <KEYWORD>administration</KEYWORD>
+      <KEYWORD>integration</KEYWORD>
+      <KEYWORD>MySQL</KEYWORD>
+      <KEYWORD>Mozilla</KEYWORD>
+      <KEYWORD>webtools</KEYWORD>
+    </KEYWORDSET>
+  </BOOKINFO>
+
+<!-- About This Guide -->
+&about;
+
+<!-- Installing Bugzilla -->
+&installation;
+
+<!-- Administering Bugzilla -->
+&administration;
+
+<!-- Using Bugzilla -->
+&using;
+
+<!-- Integrating Bugzilla with Third-Party Tools -->
+&integration;
+
+<!-- The Future of Bugzilla -->
+&future;
+
+<!-- Appendix: The Frequently Asked Questions -->
+&faq;
+
+<!-- Appendix: The Database Schema -->
+&database;
+
+<!-- Appendix: Major Bugzilla Variants -->
+&variants;
+
+<!-- Appendix: Custom Patches -->
+&patches;
+
+<!-- Appendix: The GNU Free Documentation License -->
+&gfdl;
+
+<!-- Glossary -->
+&glossary;
+
+<!-- Index -->
+&index;
+
+</BOOK>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
+
+
+
+
+
+
+
+
+
diff --git a/docs/sgml/about.sgml b/docs/sgml/about.sgml
new file mode 100644
index 000000000..d83d7d0e5
--- /dev/null
+++ b/docs/sgml/about.sgml
@@ -0,0 +1,235 @@
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
+
+<CHAPTER ID="about">
+<TITLE>About This Guide</TITLE>
+
+  <SECTION ID="aboutthisguide">
+    <TITLE>Purpose and Scope of this Guide</TITLE>
+    <PARA>
+      This document was started on September 17, 2000
+      by Matthew P. Barnson after a great deal of procrastination updating the Bugzilla FAQ,
+      which I left untouched for nearly half a year.
+      After numerous complete rewrites and reformatting, it is the document you see today.
+    </PARA>
+    <PARA>
+      Despite the lack of updates, 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>2.11</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 will follow the numbering conventions of
+      the main-tree Bugzilla releases, available at
+      <ULINK URL="http://www.mozilla.org/bugs/source.html">Mozilla.org</ULINK>, with
+      the exception that intermediate releases will have a minor revision number
+      following a period.  For instance, if the current version of Bugzilla is 4.2,
+      the current "stable" version of the Bugzilla guide, in, say, it's fifth revision,
+      would be numbered "4.2.5".  Got it?  Good.
+    </PARA>
+    <PARA>
+      I wrote this in response to the enormous demand for decent Bugzilla documentation.
+      I have incorporated instructions from the Bugzilla README, Frequently Asked Questions,
+      Database Schema Document, and various mailing lists to create it.
+      Chances are, there are glaring errors in this documentation; please contact
+      <EMAIL>barnboy@trilobyte.net</EMAIL> to correct them.
+    </PARA>
+  </SECTION>
+
+  <SECTION ID="copyright">
+    <TITLE>Copyright Information</TITLE>
+    <BLOCKQUOTE>
+      <ATTRIBUTION>Copyright (c) 2000-2001 Matthew P. Barnson</ATTRIBUTION>
+      <PARA>
+	Permission is granted to copy, distribute and/or modify this document under thei
+	terms of the GNU Free Documentation License, Version 1.1 or any later version published 
+	by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and 
+	with no Back-Cover Texts.  A copy of the license is included in the section entitled 
+	"GNU Free Documentation LIcense".
+      </PARA>
+    </BLOCKQUOTE>
+    <PARA>
+      If you have any questions regarding this document, its' copyright, or publishing this
+      document in non-electronic form, please contact <EMAIL>barnboy@trilobyte.net</EMAIL>
+    </PARA>
+  </SECTION>
+
+  <SECTION ID="disclaimer">
+    <TITLE>Disclaimer</TITLE>
+    <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.
+    </PARA>
+    <PARA>
+      All copyrights are held by their respective owners, unless specifically
+      noted otherwise.  Use of a term in this document should not be regarded
+      as affecting the validity of any trademark or service mark.
+      In particular, I like to put down Microsoft(tm).  Live with it.
+    </PARA>
+    <PARA>
+      Naming of particular products or brands should not be seen as endorsements,
+      with the exception of the term "GNU/Linux".
+      Use GNU/Linux.  Love it.  Bathe with it.  It is life and happiness.
+      I endorse it wholeheartedly and encourage you to do the same.
+    </PARA>
+    <PARA>
+      You are strongly recommended to make a backup of your system before
+      installing Bugzilla and at regular intervals thereafter.  Heaven knows
+      it's saved my bacon time after time; if you implement any suggestion in 
+      this Guide, implement this one!
+    </PARA>
+    <PARA>
+      Bugzilla has not undergone a complete security review.
+      Security holes probably 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.
+    </PARA>
+  </SECTION>
+
+<!-- Section 2: New Versions -->
+
+  <SECTION ID="newversions">
+    <TITLE>New Versions</TITLE>
+    <PARA>
+      This is the initial release of the Bugzilla Guide.
+    </PARA>
+    <PARA>
+      This document can be found in the following places:
+    </PARA>
+    <PARA>
+      <ITEMIZEDLIST>
+	<LISTITEM>
+	  <PARA>
+	    <ULINK URL="http://www.trilobyte.net/barnsons/">TriloBYTE</ULINK>
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    <ULINK URL="http://www.mozilla.org/projects/bugzilla/">Mozilla.org</ULINK>
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    <ULINK URL="http://www.linuxdoc.org/">The Linux Documentation Project</ULINK>
+	  </PARA>
+	</LISTITEM>
+      </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 mozilla/webtools/bugzilla/docs/ branch.
+    </PARA>
+  </SECTION>
+
+  <SECTION ID="credits">
+    <TITLE>Credits</TITLE>
+    <PARA>
+      The people listed below have made enormous contributions to the creation
+      of this Guide, through their dedicated hacking efforts,
+      numerous e-mail and IRC support sessions,
+      and overall excellent contribution to the Bugzilla community:
+    </PARA>
+    <PARA>
+      <ULINK URL="mailto://terry@mozilla.org">Terry Weissman</ULINK>
+      for initially converting Bugzilla from BugSplat!
+      and writing the README upon which this 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
+    </PARA>
+    <PARA>
+      <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>
+    <PARA>
+      <ULINK URL="mailto://endico@mozilla.org">Dawn Endico</ULINK>
+      for being a hacker extraordinaire and putting up with my incessant
+      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.
+    </PARA>
+  </SECTION>
+  <SECTION id="contributors">
+<TITLE>Contributors</TITLE>
+    <PARA>
+      Thanks go to these people for significant contributions to this documentation:
+    </PARA>
+    <PARA>
+      Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
+    </PARA>
+  </SECTION>
+  <SECTION ID="feedback">
+    <TITLE>Feedback</TITLE>
+    <PARA>
+      I welcome feedback on this document.  Without your submissions and input,
+      this Guide cannot continue to exist.  Please mail additions, comments, criticisms, etc.
+      to <EMAIL>barnboy@trilobyte.net</EMAIL>.  Please send flames to 
+      <EMAIL>devnull@localhost</EMAIL>
+    </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>
+    </PARA>
+  </SECTION>
+
+  <!-- conventions used here (didn't want to give it a chapter of its own) -->
+&conventions;
+
+</CHAPTER>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:upper
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:Bugzilla-Guide\.sgml
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+sgml-doctype:"<!DOCTYPE chapter PUBLIC \"-//OASIS//DTD DocBook V4.1//EN\">"
+End:
+-->
+
+
+
+
+
+
+
+
diff --git a/docs/sgml/administration.sgml b/docs/sgml/administration.sgml
new file mode 100644
index 000000000..3ab02653b
--- /dev/null
+++ b/docs/sgml/administration.sgml
@@ -0,0 +1,1107 @@
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<!-- TOC
+Chapter: Administration
+ Localconfig and Checksetup.pl customizations
+ The Email Gateway
+ Editing parameters
+  Deciding your site policies
+  The Shadow Database
+  Customizing password mail & layout
+  The Whining Cron
+  Why you shouldn't allow deletion
+ User administration
+  Creating Users
+  Disabling Users
+  User Permissions
+ Product Administration
+  Creating products
+  Creating components
+  Assigning default owners and Q/A contacts to components
+  Product Milestones
+  Product Versions
+  Voting
+-->
+
+<CHAPTER id="administration">
+  <TITLE>Administering Bugzilla</TITLE>
+<SUBTITLE>Or, I just got this cool thing installed.  Now what the heck do I do with it?</SUBTITLE>
+
+<PARA>
+So you followed the README isntructions to the letter, and
+just logged into bugzilla with your super-duper god account and you are sitting at the query
+screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
+operating parameters for bugzilla.</PARA>
+
+  <SECTION id="postinstall-check">
+    <TITLE>Post-Installation Checklist</TITLE>
+    <PARA>
+      After installation, follow the checklist below to 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.
+    </PARA>
+      <INDEXTERM>
+	<PRIMARY>checklist</PRIMARY>
+      </INDEXTERM>
+    <PROCEDURE>
+      <STEP>
+	<PARA>
+	  Set "maintainer" to <EMPHASIS>your</EMPHASIS> email address.
+	  This allows Bugzilla's error messages
+	  to display your email
+	  address and allow people to contact you for help.
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  Set "urlbase" to the URL reference for your Bugzilla installation.
+	  If your bugzilla query page is at http://www.foo.com/bugzilla/query.cgi,
+	  your url base is http://www.foo.com/bugzilla/
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  Set "usebuggroups" to "1" <EMPHASIS>only</EMPHASIS>
+	  if you need to restrict access to products.
+	  I suggest leaving this parameter <EMPHASIS>off</EMPHASIS>
+	  while initially testing your Bugzilla.
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
+	  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.
+	</PARA>
+      </STEP>
+      <STEP>
+        <PARA>
+	  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.  
+	  <NOTE>
+	    <PARA>
+	      Enabling "shadowdb" can adversely affect the stability
+	      of your installation of Bugzilla.
+	      You may frequently need to manually synchronize your databases,
+	      or schedule nightly syncs
+	      via "cron"
+	    </PARA>
+	  </NOTE>
+	  Once again, in testing you should
+	  avoid this option -- use it if or when you <EMPHASIS>need</EMPHASIS> 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.
+        </PARA>
+	<PARA>
+	  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!
+	</PARA>
+      </STEP>
+      <STEP>
+        <PARA>
+	  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.
+	  <NOTE>
+	    <PARA>
+	      The "headerhtml" text box is the HTML printed out <EMPHASIS>before</EMPHASIS> any other code on the page.
+	      If you have a special banner, put the code for it in "bannerhtml".  You may want to leave these
+	      settings at the defaults initially.
+	    </PARA>
+	  </NOTE>
+	</PARA>
+      </STEP>
+      <STEP>
+        <PARA>
+	  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.
+        </PARA>
+      </STEP>
+      <STEP>
+        <PARA>
+	  Set "newemailtech" to "on".  Your users will thank you.  This is the default in the post-2.12 world.
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  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 smaller installations.
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  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 README, or set this value to "0".
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  Set the "commenton" options according to your site policy.  It is a wise idea to require comments when users
+	  resolve, reassign, or reopen bugs.
+	  <NOTE>
+	    <PARA>
+	      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!)
+	    </PARA>
+	  </NOTE>
+	</PARA>
+      </STEP>
+      <STEP>
+	<PARA>
+	  Set "supportwatchers" 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.
+	</PARA>
+      </STEP>
+    </PROCEDURE>
+  </SECTION>
+
+  <SECTION id="useradmin">
+    <TITLE>User Administration</TITLE>
+    <PARA>
+      User administration is one of the easiest parts of Bugzilla.
+      Keeping it from getting out of hand, however, can become a challenge.
+    </PARA>
+
+    <SECTION id="defaultuser">
+      <TITLE>Creating the Default User</TITLE>
+
+      <PARA>
+	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.
+      </PARA>
+      <TIP>
+	<PARA>
+       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>" denotes the 
+	mysql prompt, not something you should type in):
+	<COMMAND><PROMPT>mysql></PROMPT> use bugs;</COMMAND>
+	<COMMAND><PROMPT>mysql></PROMPT> update profiles set groupset=0x7ffffffffffffff
+	  where login_name = "(user's login name)"; </COMMAND>
+	</PARA>
+      </TIP>
+    </SECTION>
+
+    <SECTION id="manageusers">
+      <TITLE>Managing Other Users</TITLE>
+
+      <SECTION id="login">
+	<TITLE>Logging In</TITLE>
+	<ORDEREDLIST>
+	  <LISTITEM>
+	    <PARA>
+	      Open the index.html page for your Bugzilla installation in your browser window.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      Click the "Query Existing Bug Reports" link.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      Click the "Log In" link at the foot of the page.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      Type your email address, and the password which was emailed to you when you
+	      created your Bugzilla account, into the spaces provided.
+	    </PARA>
+	  </LISTITEM>
+	</ORDEREDLIST>
+	<PARA>Congratulations, you are logged in!</PARA>
+      </SECTION>
+
+      <SECTION id="createnewusers">
+	<TITLE>Creating new users</TITLE>
+	<PARA>
+	  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.
+	</PARA>
+	<ORDEREDLIST>
+	  <LISTITEM>
+	    <PARA>
+	      After logging in, click the "Users" link at the footer of the query page.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      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.
+	    </PARA>
+	    <TIP>
+	      <PARA>
+		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 "man regexp" manual page for details on regular expression syntax),
+		or a <EMPHASIS>reverse</EMPHASIS> regular expression match,
+		where every user name which does NOT match the regular expression
+		is selected.
+	      </PARA>
+	    </TIP>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      Click the "Add New User" link at the bottom of the user list
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      Fill out the form presented.  This page is self-explanatory.  When done, click "submit".
+	    </PARA>
+	    <NOTE>
+	      <PARA>
+		Adding a user this way will <EMPHASIS>not</EMPHASIS> send an email
+		informing them of their username and password.
+		In general, it is preferable to log out and use the "New Account"
+		button to create users, as it will pre-populate all the required fields and also notify 
+		the user of her account name and password.
+	      </PARA>
+	    </NOTE>
+	  </LISTITEM>
+	</ORDEREDLIST>
+      </SECTION>
+
+      <SECTION id="disableusers">
+	<TITLE>Disabling Users</TITLE>
+	<PARA>
+	  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.
+	  <WARNING>
+	    <PARA>
+	      Don't disable your own administrative account, or you will hate life!
+	    </PARA>
+	  </WARNING>
+	</PARA>
+      </SECTION>
+
+      <SECTION id="modifyusers">
+	<TITLE>Modifying Users</TITLE>
+	<PARA>
+	  Here I will attempt to describe the function of each option on the user edit screen.
+	</PARA>
+	<ITEMIZEDLIST>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Login Name</EMPHASIS>: 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.
+	      <TIP>
+		<PARA>
+		  For compatability reasons, you should probably
+		  stick with email addresses as user login names.  It will make your life easier.
+		</PARA>
+	      </TIP>
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Real Name</EMPHASIS>: Duh!
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Password</EMPHASIS>: You will only see asterisks in versions
+	      of Bugzilla newer than 2.10 or early 2.11.  You can change the user password here.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Email Notification</EMPHASIS>: You may choose from one of three options:
+	      <ORDEREDLIST>
+		<LISTITEM>
+		  <PARA>
+		    All qualifying bugs except those which I change:
+		    The user will be notified of any change to any bug
+		    for which she is the reporter, assignee, Q/A contact, CC recipient, or "watcher".
+		  </PARA>
+		</LISTITEM>
+		<LISTITEM>
+		  <PARA>
+		    Only those bugs which I am listed on the CC line:
+		    The user will not be notified of changes to bugs where she is the assignee,
+		    reporter, or Q/A contact, but will receive them if she is on the CC list.
+		    <NOTE>
+		      <PARA>
+			She will still receive whining cron emails if you set up the "whinemail" feature.
+		      </PARA>
+		    </NOTE>
+		  </PARA>
+		</LISTITEM>
+		<LISTITEM>
+		  <PARA>
+		    <EMPHASIS>All Qualifying Bugs</EMPHASIS>: This user is a glutton for punishment.
+		    If her name is in the reporter, Q/A contact, CC, assignee, or is a "watcher",
+		    she will get email updates regarding the bug.
+		  </PARA>
+		</LISTITEM>
+	      </ORDEREDLIST>
+</PARA>
+	    <PARA>
+	      <EMPHASIS>Disable Text</EMPHASIS>: 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.
+	      <WARNING>
+		<PARA>Don't disable the administrator account!</PARA>
+	      </WARNING>
+	      <NOTE>
+		<PARA>
+		  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
+		  <EMPHASIS>not</EMPHASIS> be enabled for secure installations of Bugzilla.
+		</PARA>
+	      </NOTE>
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>CanConfirm</EMPHASIS>: 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 (ergo: "New" status).
+	      Be judicious about allowing users to turn this bit on for other users.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Creategroups</EMPHASIS>: 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.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Editbugs</EMPHASIS>: Unless a user has this bit set, they can only edit
+	      those bugs for which they are the assignee or the reporter.  
+	      <NOTE>
+		<PARA>
+		  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.
+		</PARA>
+	      </NOTE>
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Editcomponents</EMPHASIS>: 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.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Editkeywords</EMPHASIS>: 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.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>Editusers</EMPHASIS>: 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
+	      priveleges from other users or grant them to themselves.  Enable with care.
+	    </PARA>
+	  </LISTITEM>
+	  <LISTITEM>
+	    <PARA>
+	      <EMPHASIS>PRODUCT</EMPHASIS>: 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.
+	    </PARA>
+	  </LISTITEM>
+	</ITEMIZEDLIST>
+      </SECTION>
+    </SECTION>
+  </SECTION>
+
+  <SECTION id="programadmin">
+    <TITLE>Product, Component, Milestone, and Version Administration</TITLE>
+    <EPIGRAPH>
+      <PARA>
+	Dear Lord, we have to get our users to do WHAT?
+      </PARA>
+    </EPIGRAPH>
+    <REMARK>
+      Many thanks to Zach Lipton for his contributions to this section
+    </REMARK>
+
+    <SECTION id="products">
+      <TITLE>Products</TITLE>
+      <SUBTITLE>Formerly, and in some spots still, called "Programs"</SUBTITLE>
+      <PARA>
+	<GLOSSTERM baseform="product" linkend="gloss_product">Products</GLOSSTERM> are the
+	broadest category in Bugzilla, and you should have the least of these.
+	If your company makes computer games, you should have one product per game,
+	and possibly a few special products
+	(website, meetings...)
+      </PARA>
+      <PARA>
+	A Product (formerly called "Program", and still referred to that way
+	in some portions of the source code) controls some very important functions.
+	The number of "votes" available for users to vote for the most important bugs
+	is set per-product, as is the number of votes required to move a bug automatically
+	from the UNCONFIRMED status to the NEW status.  One can close a Product for further
+	bug entry and define various Versions available from the Edit Product screen.
+      </PARA>
+      <PARA>To create a new product:</PARA>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    Select "components" from the yellow footer
+	  </PARA>
+	  <TIP>
+	    <PARA>
+	      It may seem counterintuitive to click "components" when you want
+	      to edit the properties associated with Products.  This is one of a long
+	      list of things we want in Bugzilla 3.0...
+	    </PARA>
+	  </TIP>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Select the "Add" link to the right of "Add a new product".
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Enter the name of the product and a description.
+	    The Description field is free-form.
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+      <TIP>
+	<PARA>
+	  Don't worry about the "Closed for bug entry", "Maximum Votes per person", 
+	  "Maximum votes a person can put on a single bug", "Number of votes a bug in
+	  this Product needs to automatically get out of the UNCOMFIRMED state",
+	  and "Version" options yet.
+	  We'll cover those in a few moments.
+	</PARA>
+      </TIP>
+    </SECTION>
+    
+    <SECTION id="components">
+      <TITLE>Components</TITLE>
+      <PARA>
+	Components are subsections of a Product. 
+
+	<EXAMPLE>
+	  <TITLE>Creating some Components</TITLE>
+	  <INFORMALEXAMPLE>
+	    <PARA>
+	      The computer game you are designing may a "UI" component, an "API" component,
+	      a "Sound System" component, and a "Plugins" component, each overseen by a different
+	      programmer.  It often makes sense to divide Components in Bugzilla according to the
+	      natural divisions of responsibility within your Product or company.
+	    </PARA>
+	  </INFORMALEXAMPLE>
+	</EXAMPLE>
+
+	Each component has a owner and (if you turned it on in the parameters), a qa
+	contact. The owner should be the primary person who fixes bugs in that component.  The  QA
+	Contact should be the person who will ensure these bugs are completely fixed. The Owner,
+	QA Contact, and Reporter will get email when new bugs are created in this Component and
+	when these bugs change. Default Owner and Default QA Contact fields only dictate the
+	<EMPHASIS>default assignments</EMPHASIS>; the Owner and Q/A Contact fields in a bug 
+	are otherwise unrelated to the Component.
+      </PARA>
+
+      <PARA>
+	To create a new Component:
+      </PARA>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    Select the "Edit components" link from the "Edit Product" page
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Select the "Add" link to the right of the "Add a new component" text
+	    on the "Select Component" page.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Fill out the "Component" field, a short "Description", and the "Initial Owner".
+	    The "Component" field should not contain a space.  The "Description" field is
+	    free-form.  The "Initial Owner" field must be that of a valid user already
+	    existing in the database.  If the initial owner does not exist, Bugzilla
+	    will refuse to create the component.
+	    <TIP>
+	      <PARA>
+		Is your "Default Owner" a user who is not yet in the database?
+		No problem.
+		<ORDEREDLIST>
+		  <LISTITEM>
+		    <PARA>
+		      Select the "Log out" link on the footer of the page.
+		    </PARA>
+		  </LISTITEM>
+		  <LISTITEM>
+		    <PARA>
+		      Select the "New Account" link on the footer of the "Relogin" page
+		    </PARA>
+		  </LISTITEM>
+		  <LISTITEM>
+		    <PARA>
+		      Type in the email address of the default owner you want to create
+		      in the "E-mail address" field, and her full name in the "Real name"
+		      field, then select the "Submit Query" button.
+		    </PARA>
+		  </LISTITEM>
+		  <LISTITEM>
+		    <PARA>
+		      Now select "Log in" again, type in your login information, and you
+		      can modify the product to use the Default Owner information
+		      you require.
+		    </PARA>
+		  </LISTITEM>
+		</ORDEREDLIST>
+	      </PARA>
+	    </TIP>
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Either "edit" more components or return to the "query" page on the ensuing
+	    "Addming new component" page.  To return to the Product you were editing, you
+	    must select the "components" link as before.
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+    </SECTION>
+    
+    <SECTION id="versions">
+      <TITLE>Versions</TITLE>
+      <PARA>
+	Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95",
+	and "Flinders 2000".  Using Versions helps you isolate code changes and are an aid
+	in reporting.
+
+	<EXAMPLE>
+	  <TITLE>Common Use of Versions</TITLE>
+	  <INFORMALEXAMPLE>
+	    <PARA>
+	      A user reports a bug
+	      against Version "Beta 2.0" of your product.  The current Version of your software
+	      is "Release Candidate 1", and no longer has the bug.  This will
+	      help you triage and classify bugs according to their relevance.  It is also
+	      possible people may report bugs against bleeding-edge beta versions that are
+	    not evident in older versions of the software.  This can help isolate code
+	      changes that caused the bug
+	    </PARA>
+	  </INFORMALEXAMPLE>
+	</EXAMPLE>
+	<EXAMPLE>
+	  <TITLE>A Different Use of Versions</TITLE>
+	  <INFORMALEXAMPLE>
+	    <PARA>
+	      This field has been used to good effect by an online service provider in a slightly
+	      different way.  They had three versions of the product: "Production", "QA",
+	      and "Dev".  Although it may be the same product, a bug in the development
+	      environment is not normally as critical as a Production bug, nor does it
+	      need to be reported publicly.  When used in conjunction with Target Milestones,
+	      one can easily specify the environment where a bug can be reproduced, and
+	      the Milestone by which it will be fixed.
+	    </PARA>
+	  </INFORMALEXAMPLE>
+	</EXAMPLE>
+       </PARA>
+      <PARA>
+	To create and edit Versions:
+      </PARA>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    From the "Edit Product" screen, select "Edit Versions"
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    You will notice that the product already has the default version "undefined".
+	    If your product doesn't use version numbers, you may want to leave this as it is
+	    or edit it so that it is "---". You can then go back to the edit versions page
+	    and add new versions to your product.
+	  </PARA>
+	  <PARA>
+	    Otherwise, click the "Add" button to the right of the "Add a new version" text.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Enter the name of the Version.  This can be free-form characters up to the limit of the
+	    text box.  Then select the "Add" button.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    At this point you can select "Edit" to edit more Versions, or return to the "Query"
+	    page, from which you can navigate back to the product through the "components" link
+	    at the foot of the Query page.
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+    </SECTION>
+    
+    <SECTION id="milestones">
+      <TITLE>Milestones</TITLE>
+      <PARA>
+	Milestones are "targets" that you plan to get a bug fixed by. For example, you have a bug that
+	you plan to fix for your 3.0 release, it would be assigned the milestone of 3.0. Or, you have a
+	bug that you plan to fix for 2.8, this would have a milestone of 2.8.
+      </PARA>
+      <NOTE>
+	<PARA>
+	  Milestone options will only appear for a Product if you turned the "usetargetmilestone" field
+	  in the "Edit Parameters" screen "On".
+	</PARA>
+      </NOTE>
+      <PARA>
+	To create new Milestones, set Default Milestones, and set Milestone URL: 
+      </PARA>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    Select "edit milestones"
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Select "Add" to the right of the "Add a new milestone" text
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Enter the name of the Milestone in the "Milestone" field.
+	    You can optionally set the "Sortkey", which is a positive or negative number (-255 to 255)
+	    that defines where in the list this particular milestone appears.
+	    Select "Add".
+	  </PARA>
+	  <EXAMPLE>
+	    <TITLE>Using SortKey with Target Milestone</TITLE>
+	    <INFORMALEXAMPLE>
+	      <PARA>
+		Let's say you create a target milestone called "Release 1.0", with Sortkey set to "0".
+		Later, you realize that you will have a public beta, called "Beta1".
+		You can create a Milestone called "Beta1", with a Sortkey of "-1" in order to ensure
+		people will see the Target Milestone of "Beta1" earlier on the list than "Release 1.0"
+	      </PARA>
+	    </INFORMALEXAMPLE>
+	  </EXAMPLE>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    If you want to add more milestones, select the "Edit" link.
+	    If you don't, well shoot, you have to go back to the "query" page and select "components"
+	    again, and make your way back to the Product you were editing.
+	    <NOTE>
+	      <PARA>
+		This is another in the list of unusual user interface decisions that
+		we'd like to get cleaned up.  Shouldn't there be a link to the effect of
+		"edit the Product I was editing when I ended up here"?  In any case,
+		clicking "components" in the footer takes you back to the "Select product"
+		screen, from which you can begin editing your product again.
+	      </PARA>
+	    </NOTE>
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    From the Edit Product screen again (once you've made your way back), enter the URL
+	    for a description of what your milestones are for this product in the "Milestone URL" field.
+	    It should be of the format "http://www.foo.com/bugzilla/product_milestones.html"
+	  </PARA>
+	  <PARA>
+	    Some common uses of this field include product descriptions, product roadmaps,
+	    and of course a simple description of the meaning of each milestone.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    If you're using Target Milestones, the "Default Milestone" field must have some
+	    kind of entry.  If you really don't care if people set coherent Target Milestones, 
+	    simply leave this at the default, "---".  However, controlling and regularly updating the Default
+	    Milestone field is a powerful tool when reporting the status of projects.
+	  </PARA>
+	  <PARA>Select the "Update" button when you are done.</PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+    </SECTION>
+    
+    <SECTION id="voting">
+      <TITLE>Voting</TITLE>
+      <PARA>
+	The concept of "voting" is a poorly understood, yet powerful feature for the management
+	of open-source projects.  Each user is assigned so many Votes per product, which they can
+	freely reassign (or assign multiple votes to a single bug).
+	This 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.
+      </PARA>
+      <PARA>
+	The daunting challenge of Votes is deciding where you draw the line for a "vocal majority".  If you
+	only have a user base of 100 users, setting a low threshold for bugs to move from UNCONFIRMED
+	to NEW makes sense.  As the Bugzilla user base expands, however, these thresholds must be
+	re-evaluated.  You should gauge whether this feature is worth the time and close monitoring involved,
+	and perhaps forego implementation until you have a critical mass of users who demand it.
+      </PARA>
+      <PARA>To modify Voting settings:</PARA>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    Navigate to the "Edit Product" screen for the Product you wish to modify
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Set "Maximum Votes per person" to your calculated value.  Setting this field
+	    to "0" disables voting.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Set "Maximum Votes a person can put on a single bug" to your calculated value.  It
+	    should probably be some number lower than the "Maximum votes per person".
+	    Setting this field to "0" disables voting, but leaves the voting options open
+	    to the user.  This is confusing.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Set "Number of votes a bug in this product needs to automatically get out of the
+	    UNCONFIRMED state" to your calculated number.  Setting this field to "0" 
+	    disables the automatic move of bugs from UNCONFIRMED to NEW.  Some people
+	    advocate leaving this at "0", but of what use are Votes if your Bugzilla
+	    user base is unable to affect which bugs appear on Development radar?
+	    <TIP>
+	      <PARA>
+		You should probably set this number to higher than a small coalition of
+		Bugzilla users can influence it.  Most sites use this as a "referendum"
+		mechanism -- if users are able to vote a bug out of UNCONFIRMED, it
+		is a <EMPHASIS>really</EMPHASIS> bad bug!
+	      </PARA>
+	    </TIP>
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Once you have adjusted the values to your preference, select the "Update" button.
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+    </SECTION>    
+
+    <SECTION id="groups">
+      <TITLE>Groups and Group Security</TITLE>
+      <PARA>
+	Groups can be very useful in bugzilla, because they allow users to isolate
+	bugs or products that should only be seen by certain people.  Groups can also
+	be a complicated minefield of interdependencies and weirdness if mismanaged.
+
+	<EXAMPLE>
+	  <TITLE>When to Use Group Security</TITLE>
+	  <INFORMALEXAMPLE>
+	    <PARA>
+	      Many Bugzilla sites isolate "Security-related" bugs from all other bugs.
+	      This way, they can have a fix ready before the security vulnerability
+	      is announced to the world.  You can create a "Security" product which, by
+	      default, has no members, and only add members to the group (in their individual
+	      User page, as described under User Administration) who should have
+	      priveleged access to "Security" bugs.  Alternately, you may create a Group
+	      independently of any Product, and change the Group mask on individual bugs
+	      to restrict access to members only of certain Groups.
+	    </PARA>
+	  </INFORMALEXAMPLE>
+	</EXAMPLE>
+	
+	Groups only work if you enable the "usebuggroups" paramater.
+	In addition, if the "usebuggroupsentry" parameter is "On", one can restrict access
+	to products by groups, so that only members of a product group are able to view
+	bugs within that product.
+	Group security in Bugzilla can be divided into two categories:
+	Generic and Product-Based.
+      </PARA>
+      <NOTE>
+	<PARA>
+	  Groups in Bugzilla are a complicated beast that evolved out of very simple user
+	  permission bitmasks, apparently itself derived from common concepts in UNIX access
+	  controls.  A "bitmask" is a fixed-length number whose value can describe one, and
+	  only one, set of states.  For instance, UNIX file permissions are assigned bitmask
+	  values:  "execute" has a value of 1, "write" has a value of 2, 
+	  and "read" has a value of 4.  Add them together,
+	  and a file can be read, written to, and executed if it has a bitmask of "7". (This
+	  is a simplified example -- anybody who knows UNIX security knows there is much
+	  more to it than this.  Please bear with me for the purpose of this note.)  The only
+	  way a bitmask scheme can work is by doubling the bit count for each value.  Thus
+	  if UNIX wanted to offer another file permission, the next would have to be a value of
+	  8, then the next 16, the next 32, etc.
+	</PARA>
+	<PARA>
+	  Similarly, Bugzilla offers a bitmask to define group permissions, with an internal
+	  limit of 64.  Several are already occupied
+	  by built-in permissions.  The way around this limitation is
+	  to avoid assigning groups to products if you have many products, avoid bloating
+	  of group lists, and religiously prune irrelevant groups.  In reality, most installations
+	  of Bugzilla support far fewer than 64 groups, so this limitation has not hit
+	  for most sites, but it is on the table to be revised for Bugzilla 3.0
+	  because it interferes with the security schemes of some administrators.
+	</PARA>
+      </NOTE>
+      <PARA>
+	To enable Generic Group Security ("usebuggroups"):
+      </PARA>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    Turn "On" "usebuggroups" in the "Edit Parameters" screen.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    You will generally have no groups set up.  Select the "groups" link
+	    in the footer.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Take a moment to understand the instructions on the "Edit Groups" screen.
+	    Once you feel confident you understand what is expected of you, select the
+	    "Add Group" link.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Fill out the "New Name" (remember, no spaces!), "New Description", and "New
+	    User RegExp" fields.  "New User RegExp" allows you to automatically place
+	    all users who fulfill the Regular Expression into the new group.
+
+	    <EXAMPLE>
+	      <TITLE>Creating a New Group</TITLE>
+	      <INFORMALEXAMPLE>
+		<PARA>
+		  I created a group called "DefaultGroup" with a description of "This is simply
+		  a group to play with", and a "New User RegExp" of "*@velio.com".  This
+		  new group automatically includes all Bugzilla users with "@velio.com" at the
+		  end of their user id.  When I finished, my new group was assigned bit #128.
+		</PARA>
+	      </INFORMALEXAMPLE>
+	    </EXAMPLE>
+	    
+	    When you have finished, select the "Add" button.
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+
+      <PARA>
+	To enable Product-Based Group Security ("usebuggroupsentry"):
+      </PARA>
+      <WARNING>
+	<PARA>
+	  Don't forget that you only have 64 groups masks available, total, for
+	  your installation of Bugzilla!  If you plan on having more than 50
+	  products in your individual Bugzilla installation, and require group
+	  security for your products, you should
+	  consider either running multiple Bugzillas or using Generic Group Security
+	  instead of Product-Based ("usebuggroupsentry") Group Security.
+	</PARA>
+      </WARNING>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit Parameters" screen.
+	  </PARA>
+	  <WARNING>
+	    <PARA>
+	      "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.
+	    </PARA>
+	  </WARNING>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    You will generally have no Groups set up, unless you enabled "usebuggroupsentry"
+	    prior to creating any Products.  To create "Generic Group Security" groups,
+	    follow the instructions given above.  To create Product-Based Group security,
+	    simply follow the instructions for creating a new Product.  If you need to
+	    add users to these new groups as you create them, you will find the option
+	    to add them to the group available under the "Edit User" screens.
+	  </PARA>
+	</LISTITEM>
+      </ORDEREDLIST>
+    </SECTION>
+  </SECTION>
+  
+  <SECTION id="security">
+    <TITLE>Bugzilla Security</TITLE>
+    <EPIGRAPH>
+      <PARA>
+	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.
+      </PARA>
+    </EPIGRAPH>
+    <NOTE>
+      <PARA>
+	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.
+      </PARA>
+    </NOTE>
+    <PARA>
+      First thing's first: Secure your installation.
+      <NOTE>
+	<PARA>
+	  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 <ULINK URL="mailto://mozilla-webtools@mozilla.org">mozilla-webtools@mozilla.org</ULINK>
+	</PARA>
+      </NOTE>
+      <ORDEREDLIST>
+	<LISTITEM>
+	  <PARA>
+	    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.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA><EMPHASIS>There is no substitute for understanding the tools on your system!</EMPHASIS>
+	    Read <ULINK URL="http://www.mysql.com/documentation/mysql/bychapter/manual_Privilege_system.html">
+	  The MySQL Privelege System</ULINK> until you can recite it from memory!</PARA>
+	  <PARA>
+	    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 : )
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    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.
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>Do not run Apache as "nobody".  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.</PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
+	    The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
+	    of a criminal.  Also some files under $BUGZILLA_HOME/data store sensitive information.
+	  </PARA>
+	  <PARA>
+	    On Apache, you can use .htaccess files to protect access to these directories, as outlined
+	    in <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ULINK> for the
+	    localconfig file, and <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">
+	    Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories. 
+	  </PARA>
+	  <PARA>
+	    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.
+	  </PARA>
+	  <PARA>
+	    Place the following text into a file named ".htaccess", readable by your web server,
+	    in your $BUGZILLA_HOME/data directory.
+	    <LITERALLAYOUT>
+	      &lt;Files comments&gt;
+	      allow from all
+	      &lt;/Files&gt;
+	      deny from all
+	    </LITERALLAYOUT>
+	  </PARA>
+	  <PARA>
+	    Place the following text into a file named ".htaccess", readable by your web server,
+	    in your $BUGZILLA_HOME/ directory.
+	    <LITERALLAYOUT>
+	      &lt;Files localconfig&gt;
+	      deny from all
+	      &lt;/Files&gt;
+	      allow from all
+	    </LITERALLAYOUT>
+	  </PARA>
+	  <PARA>
+	    Place the following text into a file named ".htaccess", readable by your web server,
+	    in your $BUGZILLA_HOME/shadow directory.
+	    <LITERALLAYOUT>
+	      deny from all
+	    </LITERALLAYOUT>
+	  </PARA>
+	</LISTITEM>
+	<LISTITEM>
+	  <PARA>
+	    
+	  </PARA>
+	</LISTITEM>
+
+      </ORDEREDLIST>
+    </PARA>
+  </SECTION>
+</CHAPTER>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:upper
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/conventions.sgml b/docs/sgml/conventions.sgml
new file mode 100644
index 000000000..66f72303c
--- /dev/null
+++ b/docs/sgml/conventions.sgml
@@ -0,0 +1,111 @@
+<!-- <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
+
+<section id="conventions">
+  <title>Document Conventions</title>
+  
+  <indexterm zone="conventions">
+    <primary>conventions</primary>
+  </indexterm>
+  
+  <para>
+    This document uses the following conventions
+  </para>
+  
+  <informaltable frame="none">
+    <tgroup cols="2">
+      <thead>
+        <row>
+          <entry>Descriptions</entry>
+          <entry>Appearance</entry>
+        </row>
+      </thead>
+      <tbody>
+        <row>
+          <entry>Warnings</entry>
+          <entry><caution>
+              <para>Warnings.</para>
+            </caution></entry>
+        </row>
+        <row>
+          <entry>Hint</entry>
+          <entry><tip>
+              <para>Hint.</para>
+            </tip></entry>
+        </row>
+        <row>
+          <entry>Notes</entry>
+          <entry><note>
+              <para>Note.</para>
+            </note></entry>
+        </row>
+        <row>
+          <entry>Information requiring special attention</entry>
+          <entry><warning>
+              <para>Warning.</para>
+            </warning></entry>
+        </row>
+        <row>
+          <entry>File Names</entry>
+          <entry><filename>file.extension</filename></entry>
+        </row>
+        <row>
+          <entry>Directory Names</entry>
+          <entry><filename class="directory">directory</filename></entry>
+        </row>
+        <row>
+          <entry>Commands to be typed</entry>
+          <entry><command>command</command></entry>
+        </row>
+        <row>
+          <entry>Applications Names</entry>
+          <entry><application>application</application></entry>
+        </row>
+        <row>
+          <entry><foreignphrase>Prompt</foreignphrase> of users command under bash shell</entry>
+          <entry>bash$</entry>
+        </row>
+        <row>
+          <entry><foreignphrase>Prompt</foreignphrase> of root users command under bash shell</entry>
+          <entry>bash#</entry>
+        </row>
+	<row>
+	  <entry><foreignphrase>Prompt</foreignphrase> of user command under tcsh shell</entry>
+	  <entry>tcsh$</entry>
+	</row>
+        <row>
+          <entry>Environment Variables</entry>
+          <entry><envar>VARIABLE</envar></entry>
+        </row>
+        <row>
+          <entry>Emphasized word</entry>
+          <entry><emphasis>word</emphasis></entry>
+        </row>
+        <row>
+          <entry>Code Example</entry>
+          <entry><programlisting><sgmltag class="starttag">para</sgmltag>Beginning and end of paragraph<sgmltag class="endtag">para</sgmltag></programlisting></entry> 
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+  
+</section>
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:upper
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
+
+
+
diff --git a/docs/sgml/database.sgml b/docs/sgml/database.sgml
new file mode 100644
index 000000000..16c72494e
--- /dev/null
+++ b/docs/sgml/database.sgml
@@ -0,0 +1,629 @@
+<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
+
+<APPENDIX id="database">
+
+<TITLE>The Bugzilla Database</TITLE>
+<NOTE>
+<PARA>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? <REMARK>MPB</REMARK></PARA>
+</NOTE>
+  <SECTION id="dbschema">
+    <TITLE>Database Schema Chart</TITLE>
+    <PARA>
+      <MEDIAOBJECT>
+	<IMAGEOBJECT>
+	  <IMAGEDATA FILEREF="dbschema.jpg" FORMAT="jpg">
+	</IMAGEOBJECT>
+
+	<TEXTOBJECT>
+	  <PHRASE>Database Relationships</PHRASE>
+	</TEXTOBJECT>
+
+	<CAPTION>
+	  <PARA>Bugzilla database relationships chart</PARA>
+	</CAPTION>
+      </MEDIAOBJECT>
+    </PARA>
+  </SECTION>
+
+  <SECTION id="dbdoc">
+<TITLE>MySQL Bugzilla Database Introduction</TITLE>
+<LITERALLAYOUT>
+
+Contributor(s):  Matthew P. Barnson (mbarnson@excitehome.net)
+
+Last update: May 16, 2000
+
+Changes:
+Version 1.0: Initial public release (May 16, 2000)
+
+Maintainer:  Matthew P. Barnson (mbarnson@excitehome.net)
+
+
+===
+Table Of Contents
+===
+
+FOREWORD
+INTRODUCTION
+THE BASICS
+THE TABLES
+THE DETAILS
+
+
+
+===
+FOREWORD
+===
+
+  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.
+
+  I'm sorry this version is plain text.  I can whip this info out a lot faster
+if I'm not concerned about complex formatting.  I'll get it into sgml for easy
+portability as time permits.
+
+  The Bugzilla Database Schema has a home!  In addition to availability via CVS
+and released versions 2.12 and higher of Bugzilla, you can find the latest &
+greatest version of the Bugzilla Database Schema at
+http://www.trilobyte.net/barnsons/. This is a living document; please be sure
+you are up-to-date with the latest version before mirroring.
+
+  The Bugzilla Database Schema is designed to provide vital information
+regarding the structure of the MySQL database.  Where appropriate, this
+document will refer to URLs rather than including documents in their entirety
+to ensure completeness even should this paper become out of date.
+
+  This document is not maintained by Netscape or Netscape employees, so please
+do not contact them regarding errors or omissions contained herein. Please
+direct all questions, comments, updates, flames, etc. to Matthew P. Barnson
+mbarnson@excitehome.net) (barnboy or barnhome on irc.mozilla.org in
+#mozwebtools).
+
+  I'm sure I've made some glaring errors or omissions in this paper -- please
+email me corrections or post corrections to the
+netscape.public.mozilla.webtools newsgroup.
+
+
+
+===
+INTRODUCTION
+===
+
+
+
+  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.
+
+  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.
+
+  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!
+
+  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'.
+
+  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."
+
+  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...
+
+  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!
+
+
+
+===
+The Basics
+===
+
+  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 "bigint" and a
+"tinyint" entry in MySQL.  I'd refer you first to the MySQL documentation,
+available at http://www.mysql.com/doc.html, but that's mostly a confusing
+morass of high-level database jargon.  Here are the basics you need to know
+about the database to proceed:
+
+1.  To connect to your database, type "mysql -u root" at the command prompt as
+any user. If this works without asking you for a password, SHAME ON YOU!  You
+should have locked your security down like the README 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 .
+
+2.  You should now be at a prompt that looks like this:
+
+mysql>
+	
+	At the prompt, if "bugs" is the name of your Bugzilla database, type:
+	
+mysql> use bugs;
+	
+	(don't forget the ";" at the end of each line, or you'll be kicking yourself
+all the way through this documentation)
+  Young Grasshopper, you are now ready for the unveiling of the Bugzilla
+database, in the next section...
+
+
+
+===
+THE TABLES
+===
+
+  Imagine your MySQL database as a series of spreadsheets, and you won't be too
+far off.  If you use this command:
+
+mysql> show tables from bugs;
+	
+	you'll be able to see all the "spreadsheets" (tables) in your database.  Cool,
+huh?  It's kinda' like a filesystem, only much faster and more robust.  Come
+on, I'll show you more!
+
+  From the command issued above, you should now have some output that looks
+like this:
+
++-------------------+
+| Tables in bugs    |
++-------------------+
+| attachments       |
+| bugs              |
+| bugs_activity     |
+| cc                |
+| components        |
+| dependencies      |
+| fielddefs         |
+| groups            |
+| keyworddefs       |
+| keywords          |
+| logincookies      |
+| longdescs         |
+| milestones        |
+| namedqueries      |
+| products          |
+| profiles          |
+| profiles_activity |
+| shadowlog         |
+| versions          |
+| votes             |
+| watch             |
++-------------------+
+
+
+          If it doesn't look quite the same, that probably means it's time to
+update this documentation :)
+
+  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> 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?
+
+  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>
+  </SECTION>
+
+  <SECTION id="granttables">
+    <TITLE>MySQL Permissions & Grant Tables</TITLE>
+
+    <NOTE>
+      <PARA>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments.  I wrote this post to the Keynote 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 : )</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> mysql --user=root keystone
+
+mysql> GRANT
+SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
+FILE,
+           ON keystone.*
+           TO <$sys_dbuser name>@localhost
+           IDENTIFIED BY '(password)'
+	     WITH GRANT OPTION;
+
+OR
+
+mysql> GRANT ALL PRIVELEGES 
+		ON keystone.*
+		TO <$sys_dbuser name>@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.
+
+----------------------------------------------------------------------------
+10/12/2000
+Matthew sent in some mail with updated contact information:
+NEW CONTACT INFORMATION: 
+
+                        ------------------------ 
+                        Matthew P. Barnson 
+                        Manager, Systems Administration 
+                        Excite@Home Business Applications 
+                        mbarnson@excitehome.net 
+                        (801)234-8300 
+
+
+    </LITERALLAYOUT>
+  </SECTION>
+  <SECTION id="cleanupwork">
+    <TITLE>Cleaning up after mucking with Bugzilla</TITLE>
+    <LITERALLAYOUT>
+Contributed by Eric Hansen:
+There are several things, and one trick.  There is a small tiny piece of
+documentation I saw once that said something very important.
+1)  After pretty much any manual working of the Mysql db, you must
+delete a file in the bugzilla directory: data/versioncache
+Versioncache basically is a way to speed up bugzilla (from what I
+understand).  It stores a lot of commonly used information.  However,
+this file is refreshed every so often (I can't remember the time
+interval though).  So eventually all changes do propogate out, so you
+may see stuff suddenly working.
+2)  Assuming that failed, you will also have to check something with the
+checksetup.pl file.  It actually is run twice.  The first time it
+creates the file: localconfig.  You can modify localconfig, (or not if
+you are doing bug_status stuff) or you should delete localconfig and
+rerun your modified checksetup.pl.  Since I don't actually see anything
+in localconfig pertaining to bug_status, this point is mainly a FYI.
+    </LITERALLAYOUT>
+  </SECTION>
+
+</APPENDIX>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:upper
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/dbschema.jpg b/docs/sgml/dbschema.jpg
new file mode 100644
index 000000000..17e2422e5
--- /dev/null
+++ b/docs/sgml/dbschema.jpg
diff --git a/docs/sgml/faq.sgml b/docs/sgml/faq.sgml
new file mode 100644
index 000000000..c10efec42
--- /dev/null
+++ b/docs/sgml/faq.sgml
@@ -0,0 +1,1845 @@
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<appendix id="faq">
+  <title>The Bugzilla FAQ</title>
+
+  <qandaset>
+
+
+    <qandadiv id="faq_general">
+      <title>General Questions</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Where can I find information about Bugzilla?</para>
+	</question>
+	<answer>
+	  <para>
+	    You can stay up-to-date with the latest Bugzilla
+	    information at <ulink url="http://www.mozilla.org/projects/bugzilla/">
+	    http://www.mozilla.org/projects/bugzilla/</ulink>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What license is Bugzilla distributed under?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Bugzilla is covered by the Mozilla Public License.
+	    See details at <ulink url="http://www.mozilla.org/MPL/">
+	    http://www.mozilla.org/MPL/</ulink>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How do I get commercial support for Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    <ulink url="http://www.collab.net/">www.collab.net</ulink> offers
+	    Bugzilla as part of their standard offering to large projects.
+	    They do have some minimum fees that are pretty hefty, and generally
+	    aren't interested in small projects.
+	  </para>
+	  <para>
+	    There are several experienced
+	    Bugzilla hackers on the mailing list/newsgroup who are willing
+	    to whore themselves out for generous compensation.
+	    Try sending a message to the mailing list asking for a volunteer.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What major companies or projects are currently using Bugzilla
+	    for bug-tracking?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    There are <emphasis>dozens</emphasis> of major comapanies with public
+	    Bugzilla sites to track bugs in their products.  A few include:
+	    <simplelist>
+	      <member>Netscape/AOL</member>
+	      <member>Mozilla.org</member>
+	      <member>AtHome Corporation</member>
+	      <member>Red Hat Software</member>
+	      <member>Loki Entertainment Software</member>
+	      <member>SuSe Corp</member>
+	      <member>The Horde Project</member>
+	      <member>The Eazel Project</member>
+	      <member>AbiSource</member>
+	      <member>Real Time Enterprises, Inc</member>
+	      <member>Eggheads.org</member>
+	      <member>Strata Software</member>
+	      <member>RockLinux</member>
+	      <member>Creative Labs (makers of SoundBlaster)</member>
+	      <member>The Apache Foundation</member>
+	      <member>The Gnome Foundation</member>
+	      <member>Linux-Mandrake</member>
+	    </simplelist>
+	  </para>
+	  <para>
+	    Suffice to say, there are more than enough huge projects using Bugzilla
+	    that we can safely say it's extremely popular.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Who maintains Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    There are many, many contributors from around the world maintaining Bugzilla.
+	    The designated "Maintainer" is Tara Hernandez, with QA support by Matthew Tuck.
+	    Dan Mosedale and Dawn Endico are employees of Mozilla.org responsible for the
+	    installation of Bugzilla there, and are very frequent code contributors.
+	    Terry Weissman originally ported Bugzilla, but "these days, Terry just hangs around
+	    and heckles."  The rest of us are mostly transient developers; Bugzilla suits
+	    our needs, and we contribute code as we have needs for updates.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How does Bugzilla stack up against other bug-tracking databases?
+	  </para>
+	</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 experience with other bug-trackers, Bugzilla offers
+	    superior performance on commodity hardware, better price (free!), more developer-
+	    friendly features (such as stored queries, email integration, and platform
+	    independence), improved scalability, open source code, greater flexibility,
+	    and superior ease-of-use.
+	  </para>
+	  <para>
+	    If you happen to be a commercial Bugzilla 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 in Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    You can't.  However, the administrative account can, by simply opening
+	    your user account in editusers.cgi and changing the login name.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Why doesn't Bugzilla offer this or that feature or compatability
+	    with this other tracking software?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    It may be that the support has not been built yet, or that you
+	    have not yet found it.  Bugzilla is making tremendous strides in
+	    usability, customizability, scalability, and user interface.  It
+	    is widely considered the most complete and popular open-source
+	    bug-tracking software in existence.
+	  </para>
+	  <para>
+	    That doesn't mean it can't use improvement!
+	    You can help the project along by either hacking a patch yourself
+	    that supports the functionality you require, or else submitting a
+	    "Request for Enhancement" (RFE) using the bug submission interface
+	    at <ulink url="http://bugzilla.mozilla.org/">bugzilla.mozilla.org</ulink>.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Why MySQL?  I'm interested in seeing Bugzilla run on
+	    Oracle/Sybase/Msql/PostgreSQL/MSSQL?
+	  </para>
+	</question>
+	<answer>
+	  <para>Terry Weissman answers,
+	  <blockquote>
+	    <para>
+	      You're not the only one. But <emphasis>I</emphasis> am not very interested. I'm not
+	      a real SQL or database person. I just wanted to make a useful tool,
+	      and build it on top of free software. So, I picked MySQL, and
+	      learned SQL by staring at the MySQL manual and some code lying
+	      around here, and
+	      wrote Bugzilla. I didn't know that Enum's were non-standard SQL.
+	      I'm not sure if I would have cared, but I didn't even know. So, to
+	      me, things are "portable" because it uses MySQL, and MySQL is
+	      portable enough. I fully understand (now) that people want to be
+	      portable to other databases, but that's never been a real concern
+	      of mine.
+	    </para>
+	  </blockquote>
+	  </para>
+	  <para>
+	    Things aren't quite that grim these days, however.  Terry pretty much
+	    sums up much of the thinking many of us have for Bugzilla, but there
+	    is light on the horizon for database-independence!  Here are some options:
+	  </para>
+	  <simplelist>
+	    <member>
+	      <emphasis><ulink url="http://bugzilla.redhat.com/">Red Hat Bugzilla</ulink></emphasis>:
+	      Runs a modified Bugzilla 2.8 atop an Oracle database.
+	    </member>
+	    <member>
+	      <emphasis><ulink url="http://sourceforge.net/projects/interzilla">Interzilla</ulink></emphasis>:
+	      A project to run Bugzilla on Interbase.  No code released yet, however.
+	    </member>
+	    <member>
+	      <emphasis>Bugzilla 3.0</emphasis>: One of the primary stated goals
+	      is multiple database support.
+	    </member>
+	  </simplelist>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Why do the scripts say "/usr/bonsaitools/bin/perl" instead of
+	    "/usr/bin/perl" or something else?
+	  </para>
+	</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>
+		<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
+		  your Bugzilla much easier in the future.
+		</para>
+		<para>
+		  Obviously, if you do not have root access to your Bugzilla
+		  box, our suggestion is irrelevant.
+		</para>
+	      </note>
+	    </blockquote>
+	  </para>
+	</answer>
+      </qandaentry>
+
+    </qandadiv>
+
+
+    <qandadiv id="faq_redhat">
+      <title>Red Hat Bugzilla</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What about Red Hat Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable
+	    than stock Bugzilla. Check it out at
+	    http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/.
+	    They've set their Bugzilla up to work with Oracle out of the box.
+	    Note that Redhat Bugzilla is based upon the 2.8 Bugzilla tree;
+	    Bugzilla has made some tremendous advances since the 2.8 release.
+	    Why not download both Bugzillas to check out the differences for
+	    yourself?
+	  </para>
+	  <para>
+	    Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
+	    <blockquote>
+	      <para>
+		Somebody needs to take the ball and run with it.  I'm the only
+		maintainer and am very pressed for time.
+	      </para>
+	    </blockquote>
+	    If you, or someone you know, has the time and expertise to do the integration
+	    work so main-tree Bugzilla 2.12 and higher integrates the Red
+	    Hat Bugzilla Oracle modifications, please donate your
+	    time to supporting the Bugzilla project.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What are the primary benefits of Red Hat Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    <emphasis>Dave Lawrence</emphasis>:
+	    <blockquote>
+	      <para>
+		For the record, we are not using any template type implementation for
+		the cosmetic changes maded to Bugzilla.  It is just alot of html changes
+		in the code itself.  I admit I may have gotten a little carried away with it
+		but the corporate types asked for a more standardized interface to match up
+		with other projects relating to Red Hat web sites.  A lot of other web based
+		internal tools I am working on also look like Bugzilla.
+	      </para>
+	      <para>
+		I do want to land the changes that I have made to Bugzilla but I may
+		have to back out a good deal and make a different version of Red Hat's
+		Bugzilla for checking in to CVS. Especially the cosmetic changes because it
+		seems they may not fit the general public.  I will do that as soon as I can.
+		I also still do my regular QA responsibilities along with Bugzilla so time
+		is difficult sometimes to come by.
+	      </para>
+	      <para>
+		There are also a good deal of other changes that were requested by
+		management for things like support contracts and different permission
+		groups for making bugs private. Here is a short list of the major
+		changes that have been made:
+	      </para>
+	      <orderedlist>
+		<listitem>
+		  <para>
+		    No enum types. All old enum types are now separate smaller tables.
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    No bit wise operations. Not all databases support this so they were
+		    changed to a more generic way of doing this task
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    Bug reports can only be altered by the reporter, assignee, or a
+		    privileged bugzilla user. The rest of the world can see the bug but in
+		    a non-changeable format (unless the bug has been marked private).  They
+		    can however add comments, add and remove themselves from the CC list
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    Different group scheme. Each group has an id number related to it.
+		    There is a user_group table which contains userid to groupid mappings
+		    to determine which groups each user belongs to.  Additionally there is
+		    a bug_group table that has bugid to groupid mappings to show which
+		    groups can see a particular bug. If there are no entries for a bug in
+		    this table then the bug is public.
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    Product groups. product_table created to only allow certain products to
+		    be visible for certain groups in both bug entry and query. This was
+		    particulary helpful for support contracts.
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    Of course many (too many) changes to Bugzilla code itself to allow use
+		    with Oracle and still allow operation with Mysql if so desired.
+		    Currently if you use Mysql it is set to use Mysql's old permission
+		    scheme to keep breakage to a minimum. Hopefully one day this will
+		    standardize on one style which may of course be something completely
+		    different.
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    Uses Text::Template perl module for rendering of the dynamic HTML pages
+		    such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and
+		    footer parts of the page. This allows the html to be separate from the
+		    perl code for customizing the look and feel of the page to one's
+		    preference.
+		  </para>
+		</listitem>
+		<listitem>
+		  <para>
+		    There are many other smaller changes. There is also a port to Oracle
+		    that I have been working on as time permits but is not completely
+		    finished but somewhat usable. I will merge it into our standard code
+		    base when it becomes production quality. Unfortunately there will have
+		    to be some conditionals in the code to make it work with other than
+		    Oracle due to some differences between Oracle and Mysql.
+		  </para>
+		</listitem>
+	      </orderedlist>
+	      <para>
+		Both the Mysql and Oracle versions of our current code base are
+		available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit
+		patch files for all of the changes I have made and he can determine what is
+		suitable for addition to the main bugzilla cade base. But for me to commit
+		changes to the actual CVS I will need to back out alot of things that are
+		not suitable for the rest of the Bugzilla community. I am open to
+		suggestions.
+	      </para>
+	    </blockquote>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What's the current status of Red Hat Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    <note>
+	      <para>
+		This information is somewhat dated; I last updated it
+		7 June 2000.
+	      </para>
+	    </note>
+	    <emphasis>Dave Lawrence</emphasis>:
+	    <blockquote>
+	      <para>
+		     I suppose the current thread warrants an update on the status of
+		Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on
+		Oracle for the last two days in our production environment. I
+		tried to do as much testing as possible with it before going live
+		which is some of the reason for the long delay. I did not get
+		enough feedback as I would have liked from internal developers to
+		help weed out any bugs still left so I said "Fine, i will take it
+		live and then I will get the feedback I want :)" So it is now
+		starting to stabilize and it running quite well after working
+		feverishly the last two days fixing problems as soon as they came
+		in from the outside world. The current branch in cvs is up2date if
+		anyone would like to grab it and try it out. The oracle _setup.pl
+		is broken right now due to some last minute changes but I will
+		update that soon. Therefore you would probably need to create the
+		database tables the old fashioned way using the supplied sql
+		creation scripts located in the ./oracle directory. We have heavy
+		optimizations in the database it self thanks to the in-house DBA
+		here at Red Hat so it is running quite fast. The database itself
+		is located on a dual PII450 with 1GB ram and 14 high voltage
+		differential raided scsi drives. The tables and indexes are
+		partitioned in 4 chuncks across the raided drive which is nice
+		because when ever you need to do a full table scan, it is actually
+		starting in 4 different locations on 4 different drives
+		simultaneously. And the indexes of course are on separate drives
+		from the data so that speeds things up tremendously. When  I can
+		find the time I will document all that we have done to get this
+		thing going to help others that may need it.
+	      </para>
+	      <para>
+		     As Matt has mentioned it is still using out-dated code and with a
+		little help I would like to bring everything up to date for
+		eventual  incorporation with the main cvs tree. Due to other
+		duties I have with the company any help with this wiould be
+		appreciated. What we are using  now is what I call a best first
+		effort. It definitely can be improved on and may even need
+		complete rewrites in a lot of areas. A lot of changes may have to
+		be made in the way Bugzilla does things currently  to make this
+		transition to a more generic database interface.  Fortunately when
+		making the Oracle changes I made sure I didn't do  anything that I
+		would consider Oracle specific and could not be easily done with
+		other databases. Alot of the sql statements need to be broken up
+		into smaller utilities that themselves would need to make
+		decisions on what database they are using but the majority of the
+		code can be made database neutral.
+	      </para>
+	    </blockquote>
+	  </para>
+	</answer>
+      </qandaentry>
+    </qandadiv>
+
+
+    <qandadiv id="faq_loki">
+      <title>Loki Bugzilla (AKA Fenris)</title>
+      <note>
+	<para>
+	  Loki's "Fenris" Bugzilla is no longer actively maintained.
+	  It works well enough for Loki.  Additionally, the major
+	  differences in Fenris have now been integrated into
+	  the main source tree of Bugzilla, so there's not much
+	  reason to go grab the source.  I left this section of the
+	  FAQ principally for historical interest.
+	</para>
+      </note>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What about Loki Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Loki Games has a customized version of Bugzilla available at
+	    http://fenris.lokigames.com.  From that page,
+	    <blockquote>
+	      <para>
+		     You may have noticed that Fenris is a fork from Bugzilla-- our
+		patches weren't suitable for integration --and a few people have
+		expressed interest in the code. Fenris has one major  improvement
+		over Bugzilla, and that is individual comments are not appended
+		onto a string blob, they are stored as a record in a separate
+		table. This allows you to, for instance, separate comments out
+		according to privilege levels in case your bug database could
+		contain sensitive information not for public eyes. We also provide
+		things like email hiding to protect user's privacy, additional
+		fields such as 'user_affected' in case someone enters someone
+		else's bug, comment editing and deletion, and more conditional
+		system variables than Bugzilla does (turn off attachments,
+		qacontact, etc.).
+	      </para>
+	    </blockquote>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Who maintains Fenris (Loki Bugzilla) now?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Raphael Barrerro &lt;raistlin@lokigames.com&gt;.
+	    Michael Vance created the initial fork, but no longer
+	    maintains the project.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    
+	  </para>
+	</question>
+      </qandaentry>
+    </qandadiv>
+
+    <qandadiv id="faq_phb">
+      <title>Pointy-Haired-Boss Questions</title>
+      <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 :)
+	</para>
+      </note>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Is Bugzilla web-based or do you have to have specific software or
+	    specific operating system on your machine?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    It is web and e-mail based.  You can edit bugs by sending specially
+	    formatted email to a properly configured Bugzilla, or control via the web.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Has anyone you know of already done any Bugzilla integration with
+	    Perforce (SCM software)?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes!  You can find more information elsewhere in "The Bugzilla
+	    Guide" in the "Integration with Third-Party Products" section.
+	    The section on Perforce isn't very large, but as the maintainer
+	    of the Guide is charged with Perforce/Bugzilla integration by
+	    his company, you can expect this section to grow.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Does Bugzilla allow the user to track multiple projects?
+	  </para>
+	</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.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    If I am on many projects, and search for all bugs assigned to me, will
+	    Bugzilla list them for me and allow me to sort by project, severity etc?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes,
+	    are there any that are NOT allowed?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.  There are many specific MIME-types that are pre-defined by Bugzilla,
+	    but you may specify any arbitrary MIME-type you need when you
+	    upload the file.  Since all attachments are stored in the database,
+	    however, I recommend storing large binary attachments elsewhere
+	    in the web server's file system and providing a hyperlink
+	    as a comment, or in the provided "URL" field in the bug report.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Does Bugzilla allow us to define our own priorities and levels? Do we
+	    have complete freedom to change the labels of fields and format of them, and
+	    the choice of acceptable values?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.  However, modifying some fields, notably those related to bug
+	    progression states, also require adjusting the program logic to
+	    compensate for the change.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Does Bugzilla provide any reporting features, metrics, graphs, etc? You
+	    know, the type of stuff that management likes to see. :)
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.  Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi">
+	    http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting
+	    facilities.
+	  </para>
+	  <para>
+	    For more advanced reporting, I recommend hooking up a professional
+	    reporting package, such as Crystal Reports, and use ODBC to access
+	    the MySQL database.  You can do a lot through the Query page of
+	    Bugzilla as well, but right now Advanced Reporting is much
+	    better accomplished through third-party utilities that can
+	    interface with the database directly.
+	  </para>
+	  <para>
+	    Advanced Reporting is a Bugzilla 3.X proposed feature.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<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?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Email notification is user-configurable.  The bug id and Topic
+	    of the bug report accompany each email notification, along with
+	    a list of the changes made.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Can email notification be set up to send to multiple
+	    people, some on the To List, CC List, BCC List etc?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    If there is email notification, do users have to have any particular
+	    type of email application?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Bugzilla email is sent in plain text, the most compatible mail format
+	    on the planet.
+	    <note>
+	      <para>
+		If you decide to use the bugzilla_email integration features
+		to allow Bugzilla to record responses to mail with the associated bug,
+		you may need to caution your users to set their mailer to "respond
+		to messages in the format in which they were sent".  For security reasons
+		Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
+		email into Bugzilla the resulting comment looks downright awful.
+	      </para>
+	    </note>
+	  </para>
+	</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>
+	    Does Bugzilla allow data to be imported and exported? If I had outsiders
+	    write up a bug report using a MS Word bug template, could that template be
+	    imported into "matching" fields? If I wanted to take the results of a query
+	    and export that data to MS Excel, could I do that?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Mozilla allows data export through a custom DTD in XML format.
+	    It does not, however, export to specific formats other than the
+	    XML Mozilla DTD.  Importing the data into Excel or any other application
+	    is left as an exercise for the reader.
+	  </para>
+	  <para>
+	    If you create import filters to other applications from Mozilla's XML,
+	    please submit your modifications for inclusion in future Bugzilla
+	    distributions.
+	  </para>
+	  <para>
+	    As for data import, any application can send data to Bugzilla through
+	    the HTTP protocol, or through Mozilla's XML API.  However, it seems
+	    kind of silly to put another front-end in front of Bugzilla;
+	    it makes more sense to create a simplified bug submission form in
+	    HTML.  You can find an excellent example at
+	    <ulink url="http://www.mozilla.org/quality/help/bugzilla-helper.html">
+	    http://www.mozilla.org/quality/help/bugzilla-helper.html</ulink>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Does Bugzilla allow fields to be added, changed or deleted? If I want to
+	    customize the bug submission form to meet our needs, can I do that using our
+	    terminology?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Has anyone converted Bugzilla to another language to be used in other
+	    countries? Is it localizable?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Currently, no.  Internationalization support for Perl did not
+	    exist in a robust fashion until the recent release of version 5.6.0;
+	    Bugzilla is, and likely will remain (until 3.X) completely
+	    non-localized.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Can a user create and save reports? Can they do this in Word format?
+	    Excel format?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.  No.  No.
+	  </para>
+	</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>
+	    Does Bugzilla have the ability to search by word, phrase, compound
+	    search?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    You have no idea.  Bugzilla's query interface, particularly with the
+	    advanced Boolean operators, is incredibly versatile.
+	  </para>
+	</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>
+	     Does Bugzilla provide record locking when there is simultaneous access
+	    to the same bug? Does the second person get a notice that the bug is in use
+	    or how are they notified?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Bugzilla does not lock records.  It provides mid-air collision detection,
+	    and offers the offending user a choice of options to deal with the conflict.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Are there any backup features provided?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    MySQL, the database back-end for Bugzilla, allows hot-backup of data.
+	    You can find strategies for dealing with backup considerations
+	    at <ulink url="http://www.mysql.com/doc/B/a/Backup.html">
+	    http://www.mysql.com/doc/B/a/Backup.html</ulink>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Can users be on the system while a backup is in progress?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Yes.  However, commits to the database must wait
+	    until the tables are unlocked.  Bugzilla databases are typically
+	    very small, and backups routinely take less than a minute.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What type of human resources are needed to be on staff to install and
+	    maintain Bugzilla? Specifically, what type of skills does the person need to
+	    have? I need to find out if we were to go with Bugzilla, what types of
+	    individuals would we need to hire and how much would that cost vs buying an
+	    "Out-of-the-Box" solution.
+	  </para>
+	</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".
+	  </para>
+	  <para>
+	    Commercial Bug-tracking software typically costs somewhere upwards
+	    of $20,000 or more for 5-10 floating licenses.  Bugzilla consultation
+	    is available from skilled members of the newsgroup.
+	  </para>
+	  <para>
+	    As an example, as of this writing I typically charge
+	     $115 for the first hour, and $89 each hour thereafter
+	    for consulting work.  It takes me three to five hours to make Bugzilla
+	    happy on a Development installation of Linux-Mandrake.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What time frame are we looking at if we decide to hire people to install
+	    and maintain the Bugzilla? Is this something that takes hours or weeks to
+	    install and a couple of hours per week to maintain and customize or is this
+	    a multi-week install process, plus a full time job for 1 person, 2 people,
+	    etc?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    It all depends on your level of commitment.  Someone with much Bugzilla
+	    experience can get you up and running in less than a day, and
+	    your Bugzilla install can run untended for years.  If your
+	    Bugzilla strategy is critical to your business workflow, hire somebody
+	    with reasonable UNIX or Perl skills to handle your process management and
+	    bug-tracking maintenance & customization.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Is there any licensing fee or other fees for using Bugzilla? Any
+	    out-of-pocket cost other than the bodies needed as identified above?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    No.  MySQL asks, if you find their product valuable, that you purchase
+	    a support contract from them that suits your needs.
+	  </para>
+	</answer>
+      </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.mozilla.org/projects/bugzilla/">
+	    http://www.mozilla.org/projects/bugzilla/</ulink> for details.
+	    Once you download it, untar it, read the README and 
+	    the Bugzilla Guide.
+	  </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
+	    "The Bugzilla Guide".
+	  </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>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How do I completely disable MySQL security if it's giving me problems
+	    (I've followed the instructions in the README!)?
+	  </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.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Are there any security problems with Bugzilla?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    The Bugzilla code has not undergone a complete security audit.
+	    It is recommended that you closely examine permissions on your Bugzilla
+	    installation, and follow the recommended security guidelines found
+	    in the README and in The Bugzilla Guide.
+	  </para>
+	</answer>
+      </qandaentry>
+
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I've implemented the security fixes mentioned in Chris Yeh's security
+	    advisory of 5/10/2000 advising not to run MySQL as root, and am running into
+	    problems with MySQL no longer working correctly.
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    This is a common problem, related to running out of file descriptors.
+	    Simply add "ulimit -n unlimited" to the script which starts
+	    mysqld.
+	  </para>
+	</answer>
+      </qandaentry>
+    </qandadiv>
+
+    <qandadiv id="faq_email">
+      <title>Bugzilla Email</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I have a user who doesn't want to receive any more email from Bugzilla.
+	    How do I stop it entirely for this user?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    With the email changes to 2.12, the user should be able to set
+	    this in user email preferences.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I'm evaluating/testing Bugzilla, and don't want it to send email to
+	    anyone but me. How do I do it?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Edit the param for the mail text. Replace "To:" with "X-Real-To:",
+	    replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)".
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I want whineatnews.pl to whine at something more, or other than, only new
+	    bugs. How do I do it?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
+	    You can find it at<ulink url=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679">
+	      http://bugzilla.mozilla.org/show_bug.cgi?id=6679</ulink>. This
+	    patch is against an older version of Bugzilla, so you must apply
+	    the diffs manually.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I don't like/want to use Procmail to hand mail off to bug_email.pl.
+	    What alternatives do I have?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    You can call bug_email.pl directly from your aliases file, with
+	    an entry like this:
+	    <blockquote>
+	      <para>
+		bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"
+	      </para>
+	    </blockquote>
+	    However, this is fairly nasty and subject to problems; you also
+	    need to set up your smrsh (sendmail restricted shell) to allow
+	    it.  In a pinch, though, it can work.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How do I set up the email interface to submit/change bugs via email?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    You can find an updated README.mailif file in the contrib/ directory
+	    of your Bugzilla distribution that walks you through the setup.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Email takes FOREVER to reach me from bugzilla -- it's extremely slow.
+	    What gives?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    If you are using an alternate Mail Transport Agent (MTA other than
+	    sendmail), make sure the options given in the "processmail" script for all
+	    instances of "sendmail" are correct for your MTA. If you are using Sendmail,
+	    you may wish to delete the "-ODeliveryMode=deferred" option in the
+	    "processmail" script for every invocation of "sendmail". (Be sure and leave
+	    the "-t" option, though!)
+	  </para>
+	  <para>
+	    A better alternative is to change the "-O" option to
+	    "-ODeliveryMode=background".  This prevents Sendmail from hanging your
+	    Bugzilla Perl processes if the domain to which it must send mail
+	    is unavailable.
+	  </para>
+	  <para>
+	    This is now a configurable parameter called "sendmailparm", available
+	    from editparams.cgi.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	     How come email never reaches me from bugzilla changes?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Double-check that you have not turned off email in your user preferences.
+	    Confirm that Bugzilla is able to send email by visiting the "Log In"
+	    link of your Bugzilla installation and clicking the "Email me a password"
+	    button after entering your email address.
+	  </para>
+	  <para>
+	    If you never receive mail from Bugzilla, chances you do not have
+	    sendmail in "/usr/lib/sendmail".  Ensure sendmail lives in, or is symlinked
+	    to, "/usr/lib/sendmail".
+	  </para>
+	</answer>
+      </qandaentry>
+    </qandadiv>
+
+    <qandadiv id="faq_db">
+      <title>Bugzilla Database</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I've heard Bugzilla can be used with Oracle?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Red Hat Bugzilla, mentioned above, works with Oracle.  The current version
+	    from Mozilla.org does not have this capability.  Unfortunately, though
+	    you will sacrifice a lot of the really great features available in
+	    Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Bugs are missing from queries, but exist in the database (and I can pull
+	    them up by specifying the bug ID). What's wrong?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	     You've almost certainly enabled the "shadow database", but for some
+	    reason it hasn't been updated for all your bugs. This is the database
+	    against which queries are run, so that really complex or slow queries won't
+	    lock up portions of the database for other users. You can turn off the
+	    shadow database in editparams.cgi. If you wish to continue using the shadow
+	    database, then as your "bugs" user run "./syncshadowdb -syncall" from the
+	    command line in the bugzilla installation directory to recreate your shadow
+	    database. After it finishes, be sure to check the params and make sure that
+	    "queryagainstshadowdb" is still turned on. The syncshadowdb program turns it
+	    off if it was on, and is supposed to turn it back on when completed; that
+	    way, if it crashes in the middle of recreating the database, it will stay
+	    off forever until someone turns it back on by hand. Apparently, it doesn't
+	    always do that yet.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I think my database might be corrupted, or contain invalid entries. What
+	    do I do?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home
+	    directory) to see! If it all comes back, you're OK.  If it doesn't come back
+	    OK (i.e. any red letters), there are certain things Bugzilla can recover
+	    from and certain things it can't.  If it can't auto-recover, I hope you're
+	    familiar with mysqladmin commands or have installed another way to manage
+	    your database...
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I want to manually edit some entries in my database. How?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	     There is no facility in Bugzilla itself to do this. It's also generally
+	    not a smart thing to do if you don't know exactly what you're doing.
+	    However, if you understand SQL you can use the mysqladmin utility to
+	    manually insert, delete, and modify table information. Personally, I
+	    use "phpMyAdmin". You have to compile a PHP module with MySQL
+	    support to make it work, but it's very clean and easy to use.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I try to add myself as a user, but Bugzilla always tells me my password is wrong.
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled
+	    the "crypt()" function.  This prevented MySQL from storing encrypted passwords.
+	    Upgrade to the "3.23 stable" version of MySQL and you should be good to go.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I think I've set up MySQL permissions correctly, but bugzilla still can't
+	    connect.
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Try running MySQL from its binary: "mysqld --skip-grant-tables". This
+	    will allow you to completely rule out grant tables as the cause of your
+	    frustration. However, I do not recommend you run it this way on a regular
+	    basis, unless you really want your web site defaced and your machine
+	    cracked.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How do I synchronize bug information among multiple different Bugzilla
+	    databases?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Well, you can synchronize or you can move bugs.  Synchronization will
+	    only work one way -- you can create a read-only copy of the database
+	    at one site, and have it regularly updated at intervals from the main
+	    database.
+	  </para>
+	  <para>
+	    MySQL has some synchronization features builtin to the latest releases.
+	    It would be great if someone looked into the possibilities there
+	    and provided a report to the newsgroup on how to effectively
+	    synchronize two Bugzilla installations.
+	  </para>
+	  <para>
+	    If you simply need to transfer bugs from one Bugzilla to another,
+	    checkout the "move.pl" script in the Bugzilla distribution.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Why do I get bizarre errors when trying to submit data, particularly problems
+	    with "groupset"?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    If you're sure your MySQL parameters are correct, you might want turn
+	    "strictvaluechecks" OFF in editparams.cgi.  If you have "usebugsentry" set
+	    "On", you also cannot submit a bug as readable by more than one group with
+	    "strictvaluechecks" ON.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How come even after I delete bugs, the long descriptions show up?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Delete everything from $BUZILLA_HOME/shadow.  Bugzilla creates shadow
+	    files there, with each filename corresponding to a
+	    bug number.  Also be sure to run syncshadowdb to make sure, if you are using
+	    a shadow database, that the shadow database is current.
+	  </para>
+	</answer>
+      </qandaentry>
+
+    </qandadiv>
+
+    <qandadiv id="faq_nt">
+      <title>Bugzilla and Win32</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Remove Windows. Install Linux. Install Bugzilla.
+	    The boss will never know the difference.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Is there a "Bundle::Bugzilla" equivalent for Win32?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Not currently.  Bundle::Bugzilla enormously simplifies Bugzilla
+	    installation on UNIX systems.  If someone can volunteer to
+	    create a suitable PPM bundle for Win32, it would be appreciated.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    CGI's are failing with a "something.cgi is not a valid Windows NT
+	    application" error. Why?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Depending on what Web server you are using, you will have to configure
+	    the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by
+	    adding *.cgi to the App Mappings with the &lt;path&gt;\perl.exe %s %s as the
+	    executable.
+	  </para>
+	  <para>
+	    Microsoft has some advice on this matter, as well:
+	    <blockquote>
+	      <para>
+		"Set application mappings. In the ISM, map the extension for the script
+		file(s) to the executable for the script interpreter. For example, you might
+		map the extension .py to Python.exe, the executable for the Python script
+		interpreter. Note For the ActiveState Perl script interpreter, the extension
+		.pl is associated with PerlIS.dll by default. If you want to change the
+		association of .pl to perl.exe, you need to change the application mapping.
+		In the mapping, you must add two percent (%) characters to the end of the
+		pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s"
+	      </para>
+	    </blockquote>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Can I have some general instructions on how to make Bugzilla on Win32 work?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    The following couple entries are deprecated in favor of the Windows installation
+	    instructions available in the "Administration" portion of "The Bugzilla Guide".
+	    However, they are provided here for historical interest and insight.
+	    <literallayout>
+  1. #!C:/perl/bin/perl had to be added to every perl file.
+  2. Converted to Net::SMTP to handle mail messages instead of
+     /usr/bin/sendmail.
+  3. The crypt function isn't available on Windows NT (at least none that I
+     am aware), so I made encrypted passwords = plaintext passwords.
+  4. The system call to diff had to be changed to the Cygwin diff.
+  5. This was just to get a demo running under NT, it seems to be working
+     good, and I have inserted almost 100 bugs from another bug tracking
+     system. Since this work was done just to get an in-house demo, I am NOT
+     planning on making a patch for submission to Bugzilla. If you would
+     like a zip file, let me know.
+
+Q: Hmm, couldn't figure it out from the general instructions above.  How
+about step-by-step?
+A: Sure! Here ya go!
+
+  1. Install IIS 4.0 from the NT Option Pack #4.
+  2. Download and install Active Perl.
+  3. Install the Windows GNU tools from Cygwin. Make sure to add the bin
+     directory to your system path. (Everyone should have these, whether
+     they decide to use Bugzilla or not. :-) )
+  4. Download relevant packages from ActiveState at
+     http://www.activestate.com/packages/zips/. + DBD-Mysql.zip
+  5. Extract each zip file with WinZip, and install each ppd file using the
+     notation: ppm install &lt;module&gt;.ppd
+  6. Install Mysql.  *Note: If you move the default install from c:\mysql,
+     you must add the appropriate startup parameters to the NT service. (ex.
+     -b e:\\programs\\mysql)
+  7. Download any Mysql client. http://www.mysql.com/download_win.html
+  8. Setup MySql. (These are the commands that I used.)
+
+          I. Cleanup default database settings.
+           C:\mysql\bin\mysql -u root mysql
+           mysql> DELETE FROM user WHERE Host='localhost' AND User='';
+           mysql> quit
+          C:\mysql\bin\mysqladmin reload
+
+          II. Set password for root.
+           C:\mysql\bin\mysql -u root mysql
+           mysql> UPDATE user SET Password=PASSWORD('new_password')
+           WHERE user='root';
+           mysql> FLUSH PRIVILEGES;
+           mysql> quit
+           C:\mysql\bin\mysqladmin -u root reload
+
+          III. Create bugs user.
+           C:\mysql\bin\mysql -u root -p
+           mysql> insert into user (host,user,password)
+          values('localhost','bugs','');
+           mysql> quit
+           C:\mysql\bin\mysqladmin -u root reload
+
+          IV. Create the bugs database.
+           C:\mysql\bin\mysql -u root -p
+           mysql> create database bugs;
+
+          V. Give the bugs user access to the bugs database.
+           mysql> insert into db
+          (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv)
+          values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N')
+           mysql> quit
+           C:\mysql\bin\mysqladmin -u root reload
+  9. Run the table scripts to setup the bugs database.
+ 10. Change CGI.pm to use the following regular expression because of
+     differing backslashes in NT versus UNIX.
+        o $0 =~ m:[^\\]*$:;
+ 11. Had to make the crypt password = plain text password in the database.
+     (Thanks to Andrew Lahser" &lt;andrew_lahser@merck.com&gt;" on this one.) The
+     files that I changed were:
+        o globals.pl
+        o CGI.pl
+        o alternately, you can try commenting all references to 'crypt'
+          string and replace them with similar lines but without encrypt()
+          or crypr() functions insida all files.
+ 12. Replaced sendmail with Windmail. Basically, you have to come up with a
+     sendmail substitute for NT. Someone said that they used a Perl module
+     (Net::SMTP), but I was trying to save time and do as little Perl coding
+     as possible.
+ 13. Added "perl" to the beginning of all Perl system calls that use a perl
+     script as an argument and renamed processmail to processmail.pl.
+ 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm
+     not sure about this one, but the read() under NT wasn't counting the
+     EOLs without the binary read."
+	    </literallayout>
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I'm having trouble with the perl modules for NT not being able to talk to
+	    to the database.
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Your modules may be outdated or inaccurate. Try:
+	    <orderedlist>
+	      <listitem>
+		<para>
+		  Hitting http://www.activestate.com/ActivePerl
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  Download ActivePerl
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  Go to your prompt
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  Type 'ppm'
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  <prompt>PPM></prompt> <command>install DBI DBD-mysql GD</command>
+		</para>
+	      </listitem>
+	    </orderedlist>
+	    I reckon TimeDate and Data::Dumper come with the activeperl. You can check
+	    the ActiveState site for packages for installation through PPM.
+	    <ulink url=" http://www.activestate.com/Packages/">
+	      http://www.activestate.com/Packages/</ulink>
+	  </para>
+	</answer>
+      </qandaentry>
+
+    </qandadiv>
+
+    <qandadiv id="faq_use">
+      <title>Bugzilla Usage</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    The query page is very confusing.  Isn't there a simpler way to query?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    We are developing in that direction.  You can follow progress on this
+	    at <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=16775">
+	      http://bugzilla.mozilla.org/show_bug.cgi?id=16775</ulink>.  Some functionality
+	    is available in Bugzilla 2.12, and is available as "quicksearch.html"
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I'm confused by the behavior of the "accept" button in the Show Bug form.
+	    Why doesn't it assign the bug to me when I accept it?
+	  </para>
+	</question>
+	<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
+	    to change this behavior, however.
+	    <simplelist>
+	      <member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029">
+		Add a "and accept bug" radio button</ulink></member>
+	      <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.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    I can't upload anything into the database via the "Create Attachment"
+	    link.  What am I doing wrong?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    The most likely cause is a very old browser or a browser that is
+	    incompatible with file upload via POST.  Download the latest Netscape,
+	    Microsoft, or Mozilla browser to handle uploads correctly.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    Email submissions to Bugzilla that have attachments end up asking me to
+	    save it as a "cgi" file.
+	  </para>
+	</question>
+	<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
+	    cripple some other functionality.
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    How do I change a keyword in Bugzilla, once some bugs are using it?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    In the Bugzilla administrator UI, edit the keyword and it will let you
+	    replace the old keyword name with a new one.  This will cause a problem
+	    with the keyword cache.  Run sanitycheck.cgi to fix it.
+	  </para>
+	</answer>
+      </qandaentry>
+
+    </qandadiv>
+
+    <qandadiv id="faq_hacking">
+      <title>Bugzilla Hacking</title>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What bugs are in Bugzilla right now?
+	  </para>
+	</question>
+	<answer>
+	  <para>
+	    Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;product=Webtools&amp;component=Bugzilla">
+	    this link</ulink> to view current bugs or requests for
+	    enhancement for Bugzilla.
+	  </para>
+	  <para>
+	    You can view bugs marked for 2.14 release
+	    <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&amp;component=Bugzilla&amp;target_milestone=Bugzilla+2.14">here</ulink>.
+	    This list includes bugs for the 2.14 release that have already
+	    been fixed and checked into CVS.  Please consult the
+	    <ulink url="http://www.mozilla.org/projects/bugzilla/">
+	      Bugzilla Project Page</ulink> for details on how to
+	    check current sources out of CVS so you can have these
+	    bug fixes early!
+	  </para>
+	</answer>
+      </qandaentry>
+
+      <qandaentry>
+	<question>
+	  <para>
+	    What's the best way to submit patches?  What guidelines should I follow?
+	  </para>
+	</question>
+	<answer>
+	  <blockquote>
+	    <orderedlist>
+	      <listitem>
+		<para>
+		  Enter a bug into bugzilla.mozilla.org for the "Webtools" product,
+		  "Bugzilla" component.
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  Upload your patch as a unified DIFF (having used "diff -u" against
+		  the <emphasis>current sources</emphasis> checked out of CVS),
+		  or new source file by clicking
+		  "Create a new attachment" link on the bug page you've just created, and
+		  include any descriptions of database changes you may make, into the bug
+		  ID you submitted in step #1.  Be sure and click the "Patch" radio
+		  button to indicate the text you are sending is a patch!
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  Announce your patch and the associated URL
+		  (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) 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
+		  be.
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  If it passes muster with minimal modification, the person to whom
+		  the bug is assigned in Bugzilla is responsible for seeing the patch
+		  is checked into CVS.
+		</para>
+	      </listitem>
+	      <listitem>
+		<para>
+		  Bask in the glory of the fact that you helped write the most successful
+		  open-source bug-tracking software on the planet :)
+		</para>
+	      </listitem>
+	    </orderedlist>
+	  </blockquote>
+	</answer>
+      </qandaentry>
+
+
+    </qandadiv>
+
+  </qandaset>
+
+</APPENDIX>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/future.sgml b/docs/sgml/future.sgml
new file mode 100644
index 000000000..db3c071b2
--- /dev/null
+++ b/docs/sgml/future.sgml
@@ -0,0 +1,324 @@
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
+
+<chapter id="future">
+  <title>The Future of Bugzilla</title>
+  <synopsis>This section largely contributed by Matthew Tuck</synopsis>
+  <section id="spamlite">
+    <title>Reducing Spam</title>
+    <para><literallayout>
+Those who use Bugzilla frequently are probably used to notification spam
+- unwanted or unnecessary notifications.  A number of proposals have
+been put forward to attempt to reduce this.
+
+1. Reduce CC Spam
+
+Some of you probably know me as that guy who CCs on heaps and heaps of
+bugs.  Just as you get a lot of CC changes from me, so do I get a lot
+from others.  Why should CC changes send out email notifications?
+
+It's not necessarily the best idea to just remove the CC spam, there are
+other issues too, like the difficulty of adding to large CC fields.
+
+For these reasons and more, an RFE for a per user "BCC" facility exists
+that people could use to silently and privately track bugs, in a similar
+way to voting today, but applying to an unlimited number of bugs.  See
+"http://bugzilla.mozilla.org/show_bug.cgi?id=7345".
+
+2. Bulk Changes
+
+You know the drill - a large milestone change, a component movement,
+whatever, and lots of notifications are generated.  If there's enough
+maybe you'll just go delete, delete, delete, whoops, there goes another
+notification that wasn't from the bulk change you missed.
+
+Shouldn't bulk changes send out one notification?  A proposal for this
+is at "http://bugzilla.mozilla.org/show_bug.cgi?id=26943".
+
+3. Configurable Notification Criteria
+
+It would be good if you could choose what you want to receive.  There
+are two parts to this.
+
+(a) Choose a selection of bugs you're interested in.  This would be
+similar to CC except you let the set be computed from selection criteria
+rather than limited to the bugs your name is on.  There is currently a
+limited version of this in the bugzilla preferences, ie "all qualifying
+bugs"/"all qualifying bugs except the ones I change"/"only those bugs
+which I am listed on the cc line".
+(b) Choose what changes will trigger a notification for the bugs you are
+watching.  With this, you could choose whether you want to receive cc,
+dependency and keyword changes, for example.
+
+Both of these proposals live at
+"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
+</literallayout></para>
+  </section>
+
+  <section id="searching">
+    <title>Better Searching</title>
+    <para><literallayout>
+Current searching tools in Bugzilla include the querying mechanism,
+special summary reports and dependency trees.  This message is about new
+facilities.
+
+1. General Summary Reports
+
+For some time now it has been apparent to me that the query bug list
+leaves a little to be desired in its linear nature.  There is a need to
+have categorised subsets, and counts of each category.  If you don't
+believe me, how about these facilities already in place or which people
+have asked for:
+
+Most Doomed Reports - Categorised On Assignee, Shows and Counts Number
+of Bugs For Each Assignee
+Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs
+Voters Most Want Fixed
+Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset),
+Counts Number of Bugs
+Bug #9409 and #9411 - The desire to be able to report on more subsets.
+
+Hopefully you can see the gist of what is desired here.  It's a general
+reporting mechanism.
+
+This mechanism lets you choose the subset of bugs to operate on (like
+query), let's you categorise them, possibly along with subcategories and
+counts the number of bugs within each category.  It might or might not
+show the actual bugs themselves, and it might limit the number of bugs
+within a category, or categories to report on.
+
+I'm further sure that many applications of this mechanism would only be
+recognised once it was implemented.
+
+The general summary reports bug is at
+"http://bugzilla.mozilla.org/show_bug.cgi?id=12282".
+
+2. Related Bugs
+
+It would be nice to have a field where you could enter other bugs
+related to the current bug - it would be handy for navigation and
+possibly even finding duplicates.  See
+"http://bugzilla.mozilla.org/show_bug.cgi?id=12286".
+
+3. Column Specification Support
+
+Currently query seems to get what columns to report on from whatever the
+user last used.  This doesn't work well for "prepackaged queries", where
+you followed a link.  You can probably add a column by specifying a sort
+column, but this is difficult and suboptimal.
+
+Furthermore, I find that when I want to add a column to a query, it's
+usually a one off and I would prefer it to go away for the next query. 
+Hence, it would be nice to specify the columns that appear on the query
+(and general summary report) pages.  The default query mechanism should
+be able to let you specify your default columns.
+
+This proposal lives at
+"http://bugzilla.mozilla.org/show_bug.cgi?id=12284".
+</literallayout></para>
+  </section>
+
+  <section id="trackingbugs">
+    <title>Description Flags and Tracking Bugs</title>
+    <para><literallayout>
+Since I last posted on this issue, we now have "keywords" that solve
+many of the issues of description and status whiteboard keywords.  We
+have seen a migration towards keywords, but there is still further to
+go.
+
+Description ( + Status Whiteboard ) Keywords
+--------------------------------------------
+
+Some description keywords remain.  I'd like to hear what reasons, other
+than time, there are for these staying as they are.  I'm suspecting many
+are not really being used.  Hopefully we can totally remove these
+eventually.
+
+Tracking Bugs
+-------------
+
+When I suggested keywords, I did so to get rid of tracking bugs too,
+though we've had less success on that front.
+
+There are many disadvantages to tracking bugs.
+
+- They can pollute bugs counts, and you must make sure you exclude
+them.  I believe the meta keyword might be used for this purpose.
+- They have an assignee but there is nothing to fix, and that person can
+get whined at by Bugzilla.
+- It would be better to craft your own "dependency tree" rather than
+rely on a fixed hierachy in the bug system.
+- In creating a nice little hierachy, many bugs duplicate information
+that should be available in other ways, eg
+"http://bugzilla.mozilla.org/show_bug.cgi?id=12833" which is
+about beta 1 networking issues.  These could fall behind the actual
+data.  What tracking bugs are good for, ad hoc lists, is what keywords
+are better for.
+- An automatically generated dependency structure between one "tracking
+bug" and another would be better than a manual one, since it gives exact
+rather than manually set up classifications.
+
+Probably the only feature preventing tracking bugs being replaced is the
+dependency tree.  The quintessential tracking bug seems to be bug #7229
+"chofmann's watch list", which probably has about a couple of hundred
+bugs at various levels, which allows a nice visualisation.
+
+Before keywords can replace tracking bugs better visualisation is going
+to be required.  General summary reports and dependency forests of a bug
+list ("http://bugzilla.mozilla.org/show_bug.cgi?id=12992") could both
+help, but neither solves the problem totally.  Perhaps keywords within
+keywords would help here.  In any case, I'm still thinking about this
+one.
+
+Some tracking bugs could definitely be turned into keywords immediately
+though, and I'll point the finger at
+"http://bugzilla.mozilla.org/show_bug.cgi?id=7954" here since that's
+what came to mind first.
+</literallayout></para>
+  </section>
+
+  <section id="bugprobs">
+    <title>Bug Issues</title>
+    <para><literallayout>
+1. Inline Bug Changes
+
+Why do I see so many "moving to M5" and "reassigning to blahblah"
+messages, and in other circumstances none are entered?  Why aren't these
+automatically generated?  A comment should be only necessary when there
+is something to add, and if I'm not interested in this sort of
+information, I should be able to hide it.
+
+At the moment we're in a hybrid world where we don't get everything, but
+we can't get rid of the bug change "messages" either.  Furthermore,
+"View Bug Activity" requires me to manually cross reference events on
+another page, rather than being able to visually see the chronological
+order.  Shouldn't I be able to see all the information on one page?
+
+A proposal to allow bugs to be shown either way is at
+"http://bugzilla.mozilla.org/show_bug.cgi?id=11368".
+
+2.  Hard Wrapping Comments
+
+One thing that annoys me is the fact that comments are "hard wrapped" to
+a certain column width.  This is a mistake Internet Mail and News has
+made, unlike every word processor in existence, and as a consequence,
+Usenet suffers to this day from bad software.  Why has Bugzilla repeated
+the problem?
+
+Hard wrapping to a certain column width is open to abuse (see old
+Mozilla browsers that didn't wrap properly, resulting in many ugly bug
+reports we have to read to this day), and furthermore doesn't expand to
+fill greater screen sizes.  I'm also under the impression the current
+hard wrap uses a non-standard HTML facility.  See
+"http://bugzilla.mozilla.org/show_bug.cgi?id=11901".
+
+3. REMIND and LATER Are Evil
+
+I really hate REMIND and LATER.  Not because they mean something
+won't be implemented, but because they aren't the best solutions.
+
+Why are they bad?  Well, basically because they are not resolved, yet
+they are marked as such.  Hence queries have to be well crafted to
+include them.
+
+LATER, according to Bugzilla, means it won't be done this release. 
+There is a better mechanism of doing this, that is assigning to
+nobody@mozilla.org and making the milestone blank.  It's more likely to
+appear in a casual query, and it doesn't resolve the bug.
+
+REMIND, according to Bugzilla, means it might still be implemented this
+release.  Well, why not just move it to a later milestone then?  You're
+a lot less likely to forget it.  If it's really needed, a keyword would
+be better.
+
+Some people can't use blank milestones to mean an untargetted milestone,
+since they use this to assess new bugs that have no target.  Hence, it
+would be nice to distinguish between bugs that have not yet been
+considered, and those that really are not assigned to any milestone in
+the future (assumedly beyond).
+
+All this is covered at
+"http://bugzilla.mozilla.org/show_bug.cgi?id=13534".
+
+4. Create An Enhancement Field
+
+Currently enhancement is an option in severity.  This means that
+important enhancements (like for example, POP3 support) are not properly
+distinguished as such, because they need a proper severity.  This
+dilutes the meaning of enhancement.
+
+If enhancement was separated, we could properly see what was an
+enhancement.  See "http://bugzilla.mozilla.org/show_bug.cgi?id=9412".  I
+see keywords like [RFE] and [FEATURE] that seem to be compensating for
+this problem.
+</literallayout></para>
+  </section>
+
+  <section id="dbaseintegrity">
+    <title>Database Integrity</title>
+    <para><literallayout>
+Bugzilla could be more proactive in detecting suboptimal situations and
+prevent them or whine about them.
+
+1. Bugzilla Crime #1: Marking A Bug Fixed With Unresolved Dependencies
+
+It can't be marked fixed with unresolved dependencies.  Either mark it
+INVALID (tracking bugs), fix the dependencies at the same time, or
+resolve the blockers.
+
+See "http://bugzilla.mozilla.org/show_bug.cgi?id=24496".
+
+2. Keyword Restrictions
+
+Some keywords should only apply in certain circumstances, eg beta1 =>
+Milestone <
+M14, css1 => Component = Style System are possibilities.  See
+"http://bugzilla.mozilla.org/show_bug.cgi?id=26940".
+
+3. Whine About Old Votes
+
+Old votes can just sit on resolved bugs.  This is problematic with
+duplicates especially.  Automatic transferral/removal is not
+appropriate since bugs can be reopened, but a whining solution might
+work.  See "http://bugzilla.mozilla.org/show_bug.cgi?id=27553".
+
+4. Whine And Warn About Milestone Mismatches
+
+Here's a fun one.  Bug X (M17) depends on Bug Y (M15).  Bug Y gets moved
+out to M19.  The notification to the assignee of Bug X gets ignored (of
+course) and Bug X is now due to be fixed before one of its blockers.
+
+Warnings about this when it is detected as well as whining about it in
+email would help bring these issues to the attention of people sooner.
+
+Note that this would be less of a problem if we didn't have so many
+tracking bugs since they aren't updated that often and often have this
+problem.
+
+See "http://bugzilla.mozilla.org/show_bug.cgi?id=16743".
+</literallayout></para>
+  </section>
+
+  <section id="bz30">
+    <title>Bugzilla 3.0</title>
+    <para>One day, Bugzilla 3.0 will have lots of cool stuff.</para>
+  </section>
+
+</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/gfdl.sgml b/docs/sgml/gfdl.sgml
new file mode 100644
index 000000000..1091631d4
--- /dev/null
+++ b/docs/sgml/gfdl.sgml
@@ -0,0 +1,468 @@
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<appendix id="gfdl">
+<title>GNU Free Documentation License</title>
+<!-- - GNU Project - Free Software Foundation (FSF) -->
+<!-- LINK REV="made" HREF="mailto:webmasters@gnu.org" -->
+
+
+  <!-- sect1>
+    <title>GNU Free Documentation License</title -->
+
+    <para>Version 1.1, March 2000</para>
+
+    <blockquote>
+      <para>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.</para>
+    </blockquote>
+
+  <sect1 label="0" id="gfdl_0">
+    <title>PREAMBLE</title>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="1" id="gfdl_1">
+    <title>APPLICABILITY AND DEFINITIONS</title>
+
+    <para>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".</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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".</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="2" id="gfdl_2">
+    <title>VERBATIM COPYING</title>
+
+    <para>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.</para>
+
+    <para>You may also lend copies, under the same conditions stated
+    above, and you may publicly display copies.</para>
+  </sect1>
+
+  <sect1 label="3" id="gfdl_3">
+    <title>COPYING IN QUANTITY</title>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="4" id="gfdl_4">
+    <title>MODIFICATIONS</title>
+
+    <para>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:</para>
+
+    <orderedlist numeration="upperalpha">
+      <listitem><para>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.</para>
+      </listitem>
+
+      <listitem><para>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).</para>
+      </listitem>
+
+      <listitem><para>State on the Title page
+      the name of the publisher of the Modified Version, as the
+      publisher.</para>
+      </listitem>
+
+      <listitem><para>Preserve all the
+      copyright notices of the Document.</para>
+      </listitem>
+
+      <listitem><para>Add an appropriate
+      copyright notice for your modifications adjacent to the other
+      copyright notices.</para>
+      </listitem>
+
+      <listitem><para>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.</para>
+      </listitem>
+
+      <listitem><para>Preserve in that license
+      notice the full lists of Invariant Sections and required Cover
+      Texts given in the Document's license notice.</para>
+      </listitem>
+
+      <listitem><para>Include an unaltered
+      copy of this License.</para>
+      </listitem>
+
+      <listitem><para>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.</para>
+      </listitem>
+
+      <listitem><para>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.</para>
+      </listitem>
+
+      <listitem><para>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.</para>
+      </listitem>
+
+      <listitem><para>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.</para>
+      </listitem>
+
+      <listitem><para>Delete any section
+      entitled "Endorsements".  Such a section may not be included in
+      the Modified Version.</para>
+      </listitem>
+
+      <listitem><para>Do not retitle any
+      existing section as "Endorsements" or to conflict in title with
+      any Invariant Section.</para>
+      </listitem>
+    </orderedlist>
+    
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <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>
+
+  <sect1 label="5" id="gfdl_5">
+    <title>COMBINING DOCUMENTS</title>
+
+    <para>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.</para>
+
+    <para>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.</para>
+
+    <para>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."</para>
+  </sect1>
+
+  <sect1 label="6" id="gfdl_6">
+    <title>COLLECTIONS OF DOCUMENTS</title>
+
+    <para>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.</para>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="7" id="gfdl_7">
+    <title>AGGREGATION WITH INDEPENDENT WORKS</title>
+    
+    <para>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.</para>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="8" id="gfdl_8">
+    <title>TRANSLATION</title>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="9" id="gfdl_9">
+    <title>TERMINATION</title>
+    
+    <para>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.</para>
+  </sect1>
+
+  <sect1 label="10" id="gfdl_10">
+    <title>FUTURE REVISIONS OF THIS LICENSE</title>
+
+    <para>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 <ulink
+    url="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</ulink>.</para>
+
+    <para>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.</para>
+  </sect1>
+
+  <sect1 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 of the License in the document and put the following
+    copyright and license notices just after the title page:</para>
+
+<blockquote><para>
+      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".
+</para></blockquote>
+
+    <para>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.</para>
+
+    <para>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.</para>
+  </sect1>
+
+</appendix>
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-parent-document: ("Bugzilla-Guide.sgml" "appendix")
+sgml-exposed-tags:nil
+sgml-local-ecat-files:nil
+sgml-local-catalogs: CATALOG
+sgml-validate-command: "nsgmls -s gfdl.sgml"
+ispell-skip-sgml: t
+End:
+-->
diff --git a/docs/sgml/glossary.sgml b/docs/sgml/glossary.sgml
new file mode 100644
index 000000000..32525f737
--- /dev/null
+++ b/docs/sgml/glossary.sgml
@@ -0,0 +1,108 @@
+<!-- <!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
+
+<glossary id="glossary">
+
+  <glossdiv id="gloss_a">
+    <title>A</title>
+    <glossentry>
+      <glossterm>There are no entries for A</glossterm>
+      <glossdef>
+	<para></para>
+      </glossdef>
+    </glossentry>
+  </glossdiv>
+
+  <glossdiv id="gloss_b">
+    <title>B</title>
+    <glossentry>
+      <glossterm>Bug</glossterm>
+      <glossdef>
+	<para>A "Bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc.  Many also refer to a "Ticket" or "Issue"; in this context, they are synonymous.</para>
+      </glossdef>
+    </glossentry>
+
+    <glossentry>
+      <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 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 "closed bug", including acceptance, resolution, and verification.  The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though.</para>
+      </glossdef>
+    </glossentry>
+  </glossdiv>
+
+  <glossdiv id="gloss_i">
+    <title>I</title>
+    <glossentry id="gloss_infiniteloop">
+      <glossterm>Infinite Loop</glossterm>
+      <glosssee otherterm="gloss_recursion">
+    </glossentry>
+  </glossdiv>
+
+<glossdiv id="gloss_p">
+    <title>P</title>
+    <glossentry>
+      <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 also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</para>
+	<example>
+	  <title>A Sample Product</title>
+	  <para>A company sells a software product called "X".  They also maintain some older software called "Y", and have a secret project "Z".  An effective use of Products might be to create Products "X", "Y", and "Z", each with Components "User Interface", "Database", and "Business Logic".  They might also change group permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z".</para>
+	</example>
+      </glossdef>
+    </glossentry>
+  </glossdiv>
+
+  <glossdiv id="gloss_q">
+    <title>Q</title>
+    <glossentry>
+      <glossterm>Q/A</glossterm>
+      <glossdef>
+	<para>"Q/A" is short for "Quality Assurance".  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 "Q/A Contact" field in a Bug.</para>
+      </glossdef>
+    </glossentry>
+  </glossdiv>
+
+<glossdiv id="gloss_r">
+    <title>R</title>
+    <glossentry>
+      <glossterm id="gloss_recursion">Recursion</glossterm>
+      <glosssee otherterm="gloss_infiniteloop">
+    </glossentry>
+  </glossdiv>
+
+<glossdiv id="gloss_z">
+    <title>Z</title>
+    <glossentry>
+      <glossterm>Zarro Boogs Found</glossterm>
+      <glossdef>
+	<para>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".</para>
+      </glossdef>
+    </glossentry>
+</glossdiv>
+
+</glossary>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/index.sgml b/docs/sgml/index.sgml
new file mode 100644
index 000000000..e69de29bb
--- /dev/null
+++ b/docs/sgml/index.sgml
diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml
new file mode 100644
index 000000000..f29ba953d
--- /dev/null
+++ b/docs/sgml/installation.sgml
@@ -0,0 +1,347 @@
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<CHAPTER id="installation">
+  <TITLE>Installing Bugzilla</TITLE>
+  
+  <SECTION id="README.unix">
+    <TITLE>UNIX Installation</TITLE>
+    <NOTE>
+      <PARA>
+	Please consult the README included with the Bugzilla distribution
+	as the current canonical source for UNIX installation instructions.
+	We do, however, have some installation notes for errata from the README.
+      </PARA>
+    </NOTE>
+
+    <NOTE>
+      <PARA>
+	If you are installing Bugzilla on S.u.S.e. Linux, or some other
+	distributions with "paranoid" security options, it is possible
+	that the checksetup.pl script may fail with the error:
+	<ERRORNAME>cannot chdir(/var/spool/mqueue): Permission denied</ERRORNAME>
+	This is because your
+	/var/spool/mqueue directory has a mode of "drwx------".  Type
+	<COMMAND>chmod 755 /var/spool/mqueue</COMMAND> as root to fix this problem.
+      </PARA>
+    </NOTE>
+
+    <NOTE>
+      <PARA>
+	
+      </PARA>
+    </NOTE>
+  </SECTION>
+
+  <SECTION id="README.windows">
+    <TITLE>Win32 (Win98+/NT/2K) Installation</TITLE>
+    <PARA>
+      These directions have <EMPHASIS>not</EMPHASIS> been extensively tested.
+      We need testers!  Please try these out and post any changes to the
+      newsgroup.
+    </PARA>
+    <SECTION id="ntverified">
+      <TITLE>Win32 Installation: Step-by-step</TITLE>
+      <NOTE>
+	<PARA>
+	  You should be familiar with, and cross-reference, the UNIX README
+	  while performing your Win32 installation.  Unfortunately, Win32
+	  directions are not yet as detailed as those for UNIX.
+	</PARA>
+	<PARA>
+	  The <EMPHASIS>most critical</EMPHASIS> difference for Win32 users is
+	  the lack of support for a crypt() function in MySQL for Windows.  It does not
+	  have it!  All ENCRYPT statements must be modified.
+	</PARA>
+      </NOTE>
+
+      <PROCEDURE>
+	<STEP>
+	  <PARA>
+	    Install <ULINK URL="http://www.apache.org/">Apache Web Server</ULINK>
+	    for Windows.
+	  </PARA>
+	  <NOTE>
+	    <PARA>
+	      You may also use Internet Information Server or Personal Web
+	      Server for this purpose.  However, setup is slightly more
+	      difficult.  If ActivePerl doesn't seem to handle your file
+	      associations correctly (for .cgi and .pl files), please
+	      consult the FAQ, in the "Win32" section.
+	    </PARA>
+	    <PARA>
+	      If you are going to use IIS, if on Windows NT you must be updated
+	      to at least Service Pack 4.
+	    </PARA>
+	  </NOTE>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Install <ULINK URL="http://www.activestate.com/">ActivePerl</ULINK>
+	  </PARA>
+	  <PARA>
+	    Please also check the following links to fully understand the status
+	    of ActivePerl on Win32:
+	    <ULINK URL="http://language.perl.com/newdocs/pod/perlport.html">
+	      Perl Porting</ULINK>, and
+	    <ULINK URL="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html">
+	      Hixie Click Here</ULINK>
+	  </PARA>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Use ppm from your perl\bin directory to install the following packs: DBI,
+	    DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD.  You may need
+	    to extract them from .zip format using Winzip or other unzip program first.
+	    These additional ppm modules can be downloaded from ActiveState.
+	  </PARA>
+	  <PARA>
+	    The syntax for ppm is:
+	    <COMPUTEROUTPUT>
+	      <PROMPT>C:> </PROMPT><COMMAND>ppm install &lt;module&gt;.ppd</COMMAND>
+	    </COMPUTEROUTPUT>
+	  </PARA>
+	  <PARA>
+	    You can find ActiveState ppm modules at
+	    <ULINK URL="http://www.activestate.com/PPMPackages/5.6plus/">
+	      http://www.activestate.com/PPMPackages/5.6plus</ULINK>
+	  </PARA>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Download and install the Windows GNU tools from
+	    <ULINK URL="http://www.cygwin.com/">www.cygwin.com</ULINK>.
+	    Make sure the GNU utilities are in your $PATH.
+	  </PARA>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Install MySQL for NT.
+	    <NOTE>
+	      <PARA>
+		Your configuration file for MySQL <EMPHASIS>must</EMPHASIS> be named C:\MY.CNF.
+	      </PARA>
+	    </NOTE>
+	  </PARA>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Setup MySQL
+	  </PARA>
+	  <SUBSTEPS>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>C:> </PROMPT>
+		  <COMMAND>C:\mysql\bin\mysql -u root mysql</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>mysql></PROMPT>
+		  <COMMAND>DELETE FROM user WHERE Host='localhost' AND User='';</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>mysql></PROMPT>
+		  <COMMAND>UPDATE user SET Password=PASSWORD ('new_password')
+		    WHERE user='root';</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>mysql></PROMPT>
+		  <COMMAND>GRANT SELECT, INSERT, UPDATE, DELETE,
+		    INDEX, ALTER, CREATE, DROP, REFERENCES
+		    ON bugs.* to bugs@localhost
+		    IDENTIFIED BY 'bugs_password';</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>mysql></PROMPT>
+		  <COMMAND>FLUSH PRIVILEGES;</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>mysql></PROMPT>
+		  <COMMAND>create database bugs;</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>mysql></PROMPT>
+		  <COMMAND>exit</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	    <STEP>
+	      <PARA>
+		<COMPUTEROUTPUT>
+		  <PROMPT>C:></PROMPT>
+		  <COMMAND>C:\mysql\bin\mysqladmin -u root -p reload</COMMAND>
+		</COMPUTEROUTPUT>
+	      </PARA>
+	    </STEP>
+	  </SUBSTEPS>
+	</STEP>
+
+	<STEP>
+	  <PARA>
+	    Configure Bugzilla.  For Win32, this involves editing "defparams.pl"
+	    and "localconfig" to taste.  Running "checksetup.pl" should create
+	    localconfig for you.  Note that getgrnam() doesn't work, and should be
+	    deleted.  Change this line:
+	    "my $webservergid = getgrnam($my_webservergroup); "
+	    to
+	    "my $webservergid = $my_webservergroup; "
+	  </PARA>
+	</STEP>
+
+	<STEP>
+	  <NOTE>
+	    <PARA>
+	      There are several alternatives to Sendmail that will work on Win32.
+	      The one mentioned here is a <EMPHASIS>suggestion</EMPHASIS>, not
+	      a requirement.  Some other mail packages that can work include
+	      <ULINK URL="http://www.blat.net/">BLAT</ULINK>,
+	      <ULINK URL="http://www.geocel.com/windmail/">Windmail</ULINK>,
+	      <ULINK URL="http://www.dynamicstate.com/">Mercury Sendmail</ULINK>,
+	      and the CPAN Net::SMTP Perl module (available in .ppm).
+	      Every option requires some hacking of the Perl scripts for Bugzilla
+	      to make it work.  The option here simply requires the least.
+	    </PARA>
+	  </NOTE>
+	  <PARA>
+	    Download NTsendmail, available from<ULINK URL="http://www.ntsendmail.com/">
+	    www.ntsendmail.com</ULINK>.  In order for it to work, you must set up some
+	    new environment variables (detailed on the ntsendmail home page).  Figuring
+	    out where to put those variables is left as an exercise for the reader.
+	    You must have a "real" mail server which allows you to relay off it
+	    in your $ENV{"NTsendmail"} (which you should probably place in globals.pl)
+	  </PARA>
+	  <PARA>
+	    Once downloaded and installed, modify all open(SENDMAIL) calls to open
+	    "| c:\ntsendmail\ntsendmail -t" instead of "|/usr/lib/sendmail -t".
+	  </PARA>
+	  <NOTE>
+	    <PARA>
+	      We need someone to test this and make sure this works as advertised.
+	    </PARA>
+	  </NOTE>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Modify globals.pl and CGI.pl to remove the word "encrypt".
+	  </PARA>
+	  <NOTE>
+	    <PARA>
+	      I'm not sure this is all that is involved to remove crypt.  Any
+	      NT Bugzilla hackers want to pipe up?
+	    </PARA>
+	  </NOTE>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Change all references to "processmail" to "processmail.pl" in
+	    all files, and rename "processmail" to "processmail.pl"
+	  </PARA>
+	  <NOTE>
+	    <PARA>
+	      I really think this may be a change we want to make for
+	      main-tree Bugzilla.  It's painless for the UNIX folks,
+	      and will make the Win32 people happier.
+	    </PARA>
+	  </NOTE>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    Modify the path to perl on the first line (#!) of all files
+	    to point to your Perl installation, and
+	    add "perl" to the beginning of all Perl system calls that
+	    use a perl script as an argument.  This may take you a while.
+	    There is a "setperl.pl" utility to speed part of this procedure,
+	    available in the "Patches and Utilities" section of The Bugzilla Guide.
+	  </PARA>
+	</STEP>
+	<STEP>
+	  <PARA>
+	    In processmail.pl, add "binmode(HANDLE)" before all read() calls.
+	    This may not be necessary, but in some cases the read() under
+	    Win32 doesn't count the EOL's without using a binary read().
+	  </PARA>
+	</STEP>
+      </PROCEDURE>
+
+    </SECTION>
+
+    <SECTION id="addlwintips">
+      <TITLE>Additional Windows Tips</TITLE>
+      <TIP>
+	<PARA>
+	  From Andrew Pearson:
+	  <BLOCKQUOTE>
+	    <PARA>
+	      "You can make Bugzilla work with Personal Web Server for
+	      Windows 98 and higher, as well as for IIS 4.0.  Microsoft has
+	      information available at
+	      <ULINK URL=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP">
+		http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ULINK>
+	    </PARA>
+	    <PARA>
+	      Basically you need to add two String Keys in the
+	      registry at the following location:
+	    </PARA>
+	    <PARA>
+	      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
+	    </PARA>
+	    <PARA>
+	      The keys should be called ".pl" and ".cgi", and both
+	      should have a value something like:
+	      <COMMAND>c:/perl/bin/perl.exe "%s" "%s"</COMMAND>
+	    </PARA>
+	    <PARA>
+	      The KB article only talks about .pl, but it goes into
+	      more detail and provides a perl test script.
+	    </PARA>
+	  </BLOCKQUOTE>
+	</PARA>
+      </TIP>
+    </SECTION>
+  </SECTION>
+</CHAPTER>
+
+
+
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:upper
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/integration.sgml b/docs/sgml/integration.sgml
new file mode 100644
index 000000000..68f5c5717
--- /dev/null
+++ b/docs/sgml/integration.sgml
@@ -0,0 +1,54 @@
+<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
+
+<!-- Keep these tools listings in alphabetical order please. -MPB -->
+
+<chapter id="integration">
+  <title>Integrating Bugzilla with Third-Party Tools</title>
+
+  <section id="bonsai">
+    <title>Bonsai</title>
+    <para>We need Bonsai integration information.</para>
+  </section>
+
+  <section id="cvs">
+    <title>CVS</title>
+    <para>We need CVS integration information</para>
+  </section>
+
+  <section id="scm">
+    <title>Perforce SCM</title>
+    <para>
+      Richard Brooksby and his team have an integration tool
+      in public beta.  You can find it at
+      <ulink url="http://www.ravenbrook.com/project/p4dt">
+	http://www.ravenbrook.com/project/p4dti</ulink>.
+    </para>
+  </section>
+
+  <section id="tinderbox">
+    <title>Tinderbox</title>
+    <para>We need Tinderbox integration information</para>
+  </section>
+
+</chapter>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
+
+
diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml
new file mode 100644
index 000000000..0992bde0d
--- /dev/null
+++ b/docs/sgml/patches.sgml
@@ -0,0 +1,209 @@
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<appendix id="patches">
+  <title>Useful Patches and Utilities for Bugzilla</title>		
+
+<section id="setperl">
+    <title>The setperl.pl Utility</title>
+    <para>	
+      You can use the "setperl.pl" utility to quickly and easily
+      change the path to perl on all your Bugzilla files.
+    </para>	
+    <procedure>
+      <step>
+	<para>
+	  Download the "setperl.pl" 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.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
+	      </computeroutput>
+	    </para>
+	  </step>
+	<step>
+	    <para>
+	      <computeroutput>
+		<prompt>bash#</prompt>
+		<command>chmod u+x setperl.pl</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.pl /your/path/to/perl</command>
+	  </computeroutput>
+	</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
+      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>
+    <para>
+      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=".
+    </para>
+    <para>
+      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
+      <command>grep COLUMLIST ~/.netscape/cookies</command> to see
+      your current COLUMNLIST setting.
+    </para>
+    <para>
+      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
+      <command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command>
+    </para>
+    <para>
+      Akkana says she has good results piping buglist 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>
\ No newline at end of file
diff --git a/docs/sgml/readme.sgml b/docs/sgml/readme.sgml
new file mode 100644
index 000000000..cdbd22878
--- /dev/null
+++ b/docs/sgml/readme.sgml
@@ -0,0 +1,496 @@
+This is Bugzilla.  See <http://www.mozilla.org/bugs/>.
+
+
+        ==========
+        DISCLAIMER
+        ==========
+
+   This is not very well packaged code.  It's not packaged at all.  Don't
+come here expecting something you plop in a directory, twiddle a few
+things, and you're off and using it.  Work has to be done to get there.  
+We'd like to get there, but it wasn't clear when that would be, and so we
+decided to let people see it first.
+
+   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.
+
+
+        ============
+        INSTALLATION
+        ============
+
+0. Introduction
+
+   Installation of bugzilla is pretty straight forward, especially if your
+machine already has MySQL and the MySQL-related perl packages installed.
+If those aren't installed yet, then that's the first order of business.  The
+other necessary ingredient is a web server set up to run cgi scripts.
+
+   Bugzilla has been successfully installed under Solaris and Linux. Windows NT
+is not officially supported. There have been a few successful installations
+of Bugzilla under Windows NT. Please see this article for a discussion of what
+one person hacked together to get it to work.
+
+news://news.mozilla.org/19990913183810.SVTR29939.mta02@onebox.com
+
+1. Installing the Prerequisites
+
+   The software packages necessary for the proper running of bugzilla are:
+
+        1. MySQL database server and the mysql client (3.22.5 or greater)
+        2. Perl (5.004 or greater)
+        3. DBI Perl module 
+        4. Data::Dumper Perl module
+        5. MySQL related Perl module collection
+        6. TimeDate Perl module collection
+        7. GD perl module (1.18 or 1.19)
+        8. Chart::Base Perl module (0.99 through 0.99b)
+        9. The web server of your choice
+
+   Bugzilla has quite a few prerequisites, but none of them are TCL.
+Previous versions required TCL, but it no longer needed (or used).
+
+1.1. Getting and setting up MySQL database (3.22.5 or greater)
+
+   Visit MySQL homepage at http://www.mysql.org and grab the latest stable
+release of the server.  Both binaries and source are available and which
+you get shouldn't matter.  Be aware that many of the binary versions
+of MySQL store their data files in /var which on many installations
+(particularly common with linux installations) is part of a smaller
+root partition.  If you decide to build from sources you can easily set
+the dataDir as an option to configure.
+
+  If you've installed from source or non-package (RPM, deb, etc.) binaries
+you'll want to make sure to add mysqld to your init scripts so the server
+daemon will come back up whenever your machine reboots.
+
+  You also may want to edit those init scripts, to make sure that
+mysqld will accept large packets.  By default, mysqld is set up to only
+accept packets up to 64K long.  This limits the size of attachments you
+may put on bugs.  If you add something like "-O max_allowed_packet=1M"
+to the command that starts mysqld (or safe_mysqld), then you will be
+able to have attachments up to about 1 megabyte.
+
+1.2. Perl (5.004 or greater)
+
+  Any machine that doesn't have perl on it is a sad machine indeed.  Perl
+for *nix systems can be gotten in source form from http://www.perl.com.
+
+  Perl is now a far cry from the the single compiler/interpreter binary it
+once was. It now includes a great many required modules and quite a
+few other support files.  If you're not up to or not inclined to build
+perl from source, you'll want to install it on your machine using some
+sort of packaging system (be it RPM, deb, or what have you) to ensure
+a sane install.  In the subsequent sections you'll be installing quite
+a few perl modules; this can be quite ornery if your perl installation
+isn't up to snuff.
+
+1.3. DBI Perl module
+
+   The DBI module is a generic Perl module used by other database related
+Perl modules.  For our purposes it's required by the MySQL-related
+modules.  As long as your Perl installation was done correctly the
+DBI module should be a breeze.  It's a mixed Perl/C module, but Perl's
+MakeMaker system simplifies the C compilation greatly.
+
+  Like almost all Perl modules DBI can be found on the Comprehensive Perl
+Archive Network (CPAN) at http://www.cpan.org .  The CPAN servers have a
+real tendency to bog down, so please use mirrors.  The current location
+at the time of this writing (02/17/99) can be found in Appendix A.
+
+  Quality, general Perl module installation instructions can be found on
+the CPAN website, but basically you'll just need to:
+
+        1. Untar the module tarball -- it should create its own directory
+        2. Enter the following commands:
+                perl Makefile.PL
+                make
+                make test
+                make install
+
+   If everything went ok that should be all it takes.  For the vast
+majority of perl modules this is all that's required.
+
+1.4 Data::Dumper Perl module
+
+   The Data::Dumper module provides data structure persistence for Perl
+(similar to Java's serialization).  It comes with later sub-releases of
+Perl 5.004, but a re-installation just to be sure it's available won't
+hurt anything.
+
+   Data::Dumper is used by the MySQL related Perl modules.  It can be
+found on CPAN (link in Appendix A) and can be installed by following
+the same four step make sequence used for the DBI module.
+
+1.5. MySQL related Perl module collection
+
+   The Perl/MySQL interface requires a few mutually-dependent perl
+modules.  These modules are grouped together into the the
+Msql-Mysql-modules package.  This package can be found at CPAN (link
+in Appendix A).  After the archive file has been downloaded it should
+be untarred.
+
+   The MySQL modules are all build using one make file which is generated
+by running:
+
+        perl Makefile.PL
+
+   The MakeMaker process will ask you a few questions about the desired
+compilation target and your MySQL installation.  For many of the questions
+the provided default will be adequate.
+
+   When asked if your desired target is the MySQL or mSQL packages
+selected the MySQL related ones.  Later you will be asked if you wish
+to provide backwards compatibility with the older MySQL packages; you
+must answer YES to this question.  The default will be no, and if you
+select it things won't work later.
+
+   A host of 'localhost' should be fine and a testing user of 'test' and
+a null password should find itself with sufficient access to run tests
+on the 'test' database which MySQL created upon installation.  If 'make
+test' and 'make install' go through without errors you should be ready
+to go as far as database connectivity is concerned.
+
+1.6. TimeDate Perl module collection
+
+   Many of the more common date/time/calendar related Perl modules have
+been grouped into a bundle similar to the MySQL modules bundle. This
+bundle is stored on the CPAN under the name TimeDate.  A (hopefully
+current) link can be found in Appendix A.  The component module we're
+most interested in is the Date::Format module, but installing all of them
+is probably a good idea anyway.  The standard Perl module installation
+instructions should work perfectly for this simple package.
+
+1.7. GD Perl module (1.18 or 1.19)
+
+   The GD library was written by Thomas Boutell a long while ago to
+programatically generate images in C.  Since then it's become almost a
+defacto standard for programatic image construction.  The Perl bindings
+to it found in the GD library are used on a million web pages to generate
+graphs on the fly.  That's what bugzilla will be using it for so you'd
+better install it if you want any of the graphing to work.
+    Actually bugzilla uses the Graph module which relies on GD itself,
+but isn't that always the way with OOP.  At any rate, you can find the
+GD library on CPAN (link in Appendix A).  Note, however, that you MUST
+use version 1.18 or 1.19, because newer versions have dropped support
+for GIFs in favor of PNGs, and bugzilla has not yet been updated to
+deal with this.
+
+1.8. Chart::Base Perl module (0.99 through 0.99b)
+
+   The Chart module provides bugzilla with on-the-fly charting
+abilities.  It can be installed in the usual fashion after it has been
+fetched from CPAN where it is found as the Chart-x.x... tarball in a
+directory to be listed in Appendix A.  Note that as with the GD perl
+module, only the specific versions listed above will work.
+
+1.9. HTTP server
+
+   You have a freedom of choice here - Apache, Netscape or any other
+server on UNIX would do. You can easily run the web server on a different
+machine than MySQL, but that makes MySQL permissions harder to manage.
+
+   You'll want to make sure that your web server will run any file
+with the .cgi extension as a cgi and not just display it.  If you're using
+apache that means uncommenting the following line in the srm.conf file:
+
+        AddHandler cgi-script .cgi
+
+   With apache you'll also want to make sure that within the access.conf
+file the line:
+
+        Options ExecCGI
+
+is in the stanza that covers the directories you intend to put the
+bugzilla .html and .cgi files into.
+
+2. Installing the Bugzilla Files
+
+   You should untar the bugzilla files into a directory that you're
+willing to make writable by the default web server user (probably
+'nobody').  You may decide to put the files off of the main web space
+for your web server or perhaps off of /usr/local with a symbolic link
+in the web space that points to the bugzilla directory.  At any rate,
+just dump all the files in the same place (optionally omitting the CVS
+directory if it accidentally got tarred up with the rest of bugzilla)
+and make sure you can get at the files in that directory through your
+web server.
+
+   Once all the files are in a web accessible directory, make that
+directory writable by your webserver's user (which may require just
+making it world writable).  
+        
+   Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin
+to the correct location of your perl executable (probably /usr/bin/perl).
+Or, you'll have to hack all the .cgi files to change where they look
+for perl.
+
+3. Setting Up the MySQL database
+
+   After you've gotten all the software installed and working you're ready
+to start preparing the database for its life as a the back end to a high
+quality bug tracker.
+
+    First, you'll want to fix MySQL permissions.  Bugzilla always logs
+in as user "bugs", with no password.  That needs to work.  MySQL
+permissions are a deep, nasty complicated thing.  I've just turned
+them off.  If you want to do that, too, then the magic is to do run
+"mysql mysql", and feed it commands like this (replace all instances of
+HOSTNAME with the name of the machine mysql is running on):
+
+        DELETE FROM host;
+        DELETE FROM user;
+        INSERT INTO host VALUES
+          ('localhost','%','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');
+        INSERT INTO host VALUES
+          (HOSTNAME,'%','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y');
+        INSERT INTO user VALUES
+          ('localhost','root','','Y','Y','Y','Y','Y','Y','Y','Y','Y',
+          'Y','Y','Y','Y','Y');
+        INSERT INTO user VALUES
+          (HOSTNAME,'','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y',
+          'Y','Y','Y');
+        INSERT INTO user VALUES
+          (HOSTNAME,'root','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y',
+          'Y','Y','Y','Y');
+        INSERT INTO user VALUES
+          ('localhost','','','Y','Y','Y','Y','Y','Y','Y','Y','Y','Y',
+          'Y','Y','Y','Y');
+
+The number of 'Y' entries to use varies with the version of MySQL; they
+keep adding columns.  The list here should work with version 3.22.23b.
+
+This run of "mysql mysql" may need some extra parameters to deal with
+whatever database permissions were set up previously.  In particular,
+you might have to say "mysql -uroot mysql", and give it an appropriate
+password.
+
+For much more information about MySQL permissions, see the MySQL
+documentation.
+
+After you've tweaked the permissions, run "mysqladmin reload" to make
+sure that the database server knows to look at your new permission list.
+
+Or, at the mysql prompt:
+
+mysql> flush privileges;
+
+You must explictly tell mysql to reload permissions before running checksetup.pl.
+
+Next, you can just run the magic checksetup.pl script.  (Many thanks
+to Holger Schurig <holgerschurig@nikocity.de> for writing this script!)
+It will make sure things have reasonable permissions, set up the "data"
+directory, and create all the MySQL tables.  Just run:
+
+        ./checksetup.pl
+
+The first time you run it, it will create a file called "localconfig"
+which you should examine and perhaps tweak a bit.  Then re-run
+checksetup.pl and it will do the real work.
+
+
+At ths point, you should have a nearly empty copy of the bug tracking
+setup.
+
+4. Tweaking the Bugzilla->MySQL Connection Data
+
+   If you have played with MySQL permissions, rather than just opening it
+wide open as described above, then you may need to tweak the Bugzilla
+code to connect appropriately.
+
+   In order for bugzilla to be able to connect to the MySQL database
+you'll have to tell bugzilla where the database server is, what
+database you're connecting to, and whom to connect as.  Simply open up
+the globals.pl file in the bugzilla directory and find the line that
+begins like:
+
+        $::db = Mysql->Connect("
+
+   That line does the actual database connection.  The Connect method
+takes four parameters which are (with appropriate values):
+
+        1. server's host: just use "localhost"
+        2. database name: "bugs" if you're following these directions
+        3. MySQL username: whatever you created for your webserver user
+                probably "nobody"
+        4. Password for the MySQL account in item 3.
+
+Just fill in those values and close up globals.pl
+
+5. Setting up yourself as Maintainer
+
+    Start by creating your own bugzilla account.  To do so, just try to
+"add a bug" from the main bugzilla menu (now available from your system
+through your web browser!).  You'll be prompted for logon info, and you
+should enter your email address and then select 'mail me my password'.
+When you get the password mail, log in with it.  Don't finish entering
+that new bug.
+
+    Now, add yourself to every group.  The magic checksetup.pl script
+can do this for you, if you run it again now.  That script will notice
+if there's exactly one user in the database, and if so, add that person
+to every group.
+
+    If you want to add someone to every group by hand, you can do it by
+typing the appropriate MySQL commands.  Run mysql, and type:
+
+        update profiles set groupset=0x7fffffffffffffff
+        where login_name = 'XXX';
+
+replacing XXX with your Bugzilla email address.
+
+Now, if you go to the query page (off of the bugzilla main menu) where
+you'll now find a 'edit parameters' option which is filled with editable
+treats.
+
+6. Setting Up the Whining Cron Job (Optional)
+
+   By now you've got 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.  This can be done by adding
+the following command as a daily crontab entry (for help on that see that
+crontab man page):
+
+        cd <your-bugzilla-directory> ; ./whineatnews.pl
+
+7. Bug Graphs (Optional)
+
+   As long as you installed the GD and Graph::Base Perl modules you might
+as well turn on the nifty bugzilla bug reporting graphs.  Just add
+the command:
+
+        cd <your-bugzilla-directory> ; ./collectstats.pl
+
+as a nightly entry to your crontab and after two days have passed you'll
+be able to view bug graphs from the Bug Reports page.
+
+8. Real security for MySQL
+
+MySQL has "interesting" default security parameters:
+        mysqld defaults to running as root
+        it defaults to allowing external network connections
+        it has a known port number, and is easy to detect
+        it defaults to no passwords whatsoever
+        it defaults to allowing "File_Priv"
+This means anyone from anywhere on the internet can not only drop the
+database with one SQL command, and they can write as root to the system.
+
+To see your permissions do:
+        > mysql -u root -p
+        use mysql;
+        show tables;
+        select * from user;
+        select * from db;
+
+To fix the gaping holes:
+        DELETE FROM user WHERE User='';
+        UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';
+        FLUSH PRIVILEGES;
+
+If you're not running "mit-pthreads" you can use:
+        GRANT USAGE ON *.* TO bugs@localhost;
+        GRANT ALL ON bugs.* TO bugs@localhost;
+        REVOKE DROP ON bugs.* FROM bugs@localhost;
+        FLUSH PRIVILEGES;
+
+With "mit-pthreads" you'll need to modify the "globals.pl" Mysql->Connect
+line to specify a specific host name instead of "localhost", and accept
+external connections:
+        GRANT USAGE ON *.* TO bugs@bounce.hop.com;
+        GRANT ALL ON bugs.* TO bugs@bounce.hop.com;
+        REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;
+        FLUSH PRIVILEGES;
+
+Consider also:
+        o Turning off external networking with "--skip-networking",
+          unless you have "mit-pthreads", in which case you can't.
+          Without networking, MySQL connects with a Unix domain socket.
+
+        o using the --user= option to mysqld to run it as an unprivileged
+          user.
+
+        o starting MySQL in a chroot jail
+
+        o running the httpd in a jail
+
+        o making sure the MySQL passwords are different from the OS
+          passwords (MySQL "root" has nothing to do with system "root").
+
+        o running MySQL on a separate untrusted machine
+
+        o making backups ;-)
+
+
+
+---------[ Appendices ]-----------------------
+
+Appendix A. Required Software Download Links
+
+   All of these sites are current as of February 17, 1999.  Hopefully
+they'll stay current for a while.
+
+MySQL: http://www.mysql.org
+
+Perl: http://www.perl.org
+
+CPAN: http://www.cpan.org
+
+DBI Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/
+
+Data::Dumper module:
+        ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/
+
+MySQL related Perl modules:
+        ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/
+
+TimeDate Perl module collection:
+        ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/
+
+GD Perl module: ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/
+
+Chart::Base module:
+        ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/
+
+
+Appendix B. Modifying Your Running System
+
+   Bugzilla optimizes database lookups by storing all relatively static
+information in the versioncache file, located in the data/ subdirectory
+under your installation directory (we said before it needs to be writable,
+right?!)
+
+   If you make a change to the structural data in your database (the
+versions table for example), or to the "constants" encoded in
+defparams.pl, you will need to remove the cached content from the data
+directory (by doing a "rm data/versioncache"), or your changes won't show
+up!
+
+   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.
+
+
+Appendix C. Upgrading from previous versions of Bugzilla
+
+The developers of Bugzilla are constantly adding new tables, columns and
+fields.  You'll get SQL errors if you just update the code.  The strategy
+to update is to simply always run the checksetup.pl script whenever
+you upgrade your installation of Bugzilla.  If you want to see what has
+changed, you can read the comments in that file, starting from the end.
+
+
+Appendix D. History
+
+   This document was originally adapted from the Bonsai installation
+instructions by Terry Weissman <terry@mozilla.org>.
+
+   The February 25, 1999 re-write of this page was done by Ry4an Brase
+<ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt,
+Martin Pool, & Dan Mosedale (But don't send bug reports to them!
+Report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
+project Webtools, component Bugzilla).
+
+   Comments from people using this document for the first time are
+especially welcomed.
diff --git a/docs/sgml/using.sgml b/docs/sgml/using.sgml
new file mode 100644
index 000000000..606dca8c2
--- /dev/null
+++ b/docs/sgml/using.sgml
@@ -0,0 +1,846 @@
+<!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>
+  <epigraph>
+    <para>
+      What, Why, How, & What's in it for me?
+    </para>
+  </epigraph>
+
+  <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.
+      At the time Bugzilla was originally written, as a port from Netscape Communications'
+      "Bugsplat!" program to Perl from TCL, there were very few competitors in the market
+      for bug-tracking software.  Most commercial defect-tracking software vendors at the
+      time charged enormous licensing fees.  Bugzilla quickly became a favorite of the
+      open-source crowd (with its genesis in the open-source browser project, Mozilla) and
+      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>
+	    integrated, product-based granular security schema
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    inter-bug dependencies and dependency graphing
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    advanced reporting capabilities
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    a robust, stable RDBMS back-end
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    extensive configurability
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    a very well-understood and well-thought-out natural bug resolution protocol
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    email, XML, and HTTP APIs
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    integration with several automated software configuration management systems
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    too many more features to list
+	  </para>
+	</listitem>
+      </itemizedlist>
+    </para>
+    <para>
+      Despite its current robustness and popularity, however, Bugzilla
+      faces some near-term challenges, such as reliance on a single database, a lack of
+      abstraction of the user interface and program logic, verbose email bug
+      notifications, a powerful but daunting query interface, little reporting configurability,
+      problems with extremely large queries, some unsupportable bug resolution options,
+      no internationalization, and dependence on some nonstandard libraries.
+    </para>
+    <para>
+      Despite these small problems, Bugzilla is very hard to beat.  It is under <emphasis>very</emphasis>
+      active development to address the current issues, and a long-awaited overhaul in the form
+      of Bugzilla 3.0 is expected sometime later this year.
+    </para>
+  </section>
+  
+  <section id="why">
+    <title>Why Should We Use Bugzilla?</title>
+    <epigraph>
+      <para>
+	No, Who's on first...
+      </para>
+    </epigraph>
+    <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 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 *something* 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>
+    <epigraph>
+      <para>
+	Hey!  I'm Woody!  Howdy, Howdy, Howdy!
+      </para>
+    </epigraph>
+    
+    <para>
+      Bugzilla is a large and complex system.  Describing how to use it
+      requires some time.  If you are only interested in installing or administering
+      a Bugzilla installation, please consult the Installing and Administering
+      Bugzilla portions of this Guide.  This section is principally aimed towards
+      developing end-user mastery of Bugzilla, so you may fully enjoy the benefits
+      afforded by using this reliable open-source bug-tracking software.
+    </para>
+    <para>
+      Throughout this portion of the Guide, we will refer to user account
+      options available at the Bugzilla test installation,
+      <ulink url="http://landfill.tequilarista.org/">
+      landfill.tequilarista.org</ulink>.
+      Although Landfill serves as a great introduction to Bugzilla, it does not offer
+      all the options you would have as a user on your own installation of Bugzilla,
+      nor can it do more than serve as a general introduction to Bugzilla.
+  However, please use it if you want to
+      follow this tutorial.
+    </para>
+    
+    <section id="myaccount">
+      <title>Create a Bugzilla Account</title>
+      <para>
+	First thing's first!  If you want to use Bugzilla, first you need to create
+	an account.  Consult with the administrator responsible for your installation
+	of Bugzilla for the URL you should use to access it.
+	If you're test-driving the end-user Bugzilla experience, use this URL:
+	<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
+	  http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
+      </para>
+      <orderedlist>
+	<listitem>
+	  <para>
+	    Click the "Open a new Bugzilla account" link.
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself)
+	    in the spaces provided, then select the "Create Account" button.
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    Within 5-10 minutes, you should receive an email to the address you provided above,
+	    which contains your login name (generally the same as the email address), and
+	    a password you can use to access your account.  This password is randomly generated,
+	    and should be changed at your nearest opportunity (we'll go into how to do it later).
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    Click the "Log In" link in the yellow area at the bottom of the page in your browser,
+	    then enter your "E-mail address" and "Password" you just received into the spaces provided,
+	    and select "Login".
+	    <note>
+	      <para>
+		If you ever forget your password, you can come back to this page, enter your
+		"E-mail address", then select the "E-mail me a password" button to have your password
+		mailed to you again so that you can login.
+	      </para>
+	    </note>
+	    <caution>
+	      <para>
+		Many modern browsers include an "Auto-Complete" or "Form Fill" feature to
+		remember the user names and passwords you type in at many sites.  Unfortunately,
+		sometimes they attempt to "guess" what you will put in as your password, and guess
+		wrong.  If you notice a text box is already filled out, please overwrite the contents
+		of the text box so you can be sure to input the correct information.
+	      </para>
+	    </caution>
+	  </para>
+	</listitem>
+      </orderedlist>
+      <para>
+	Congratulations!  If you followed these directions, you now are the
+	proud owner of a user account on landfill.tequilarista.org (Landfill) or
+	your local Bugzilla install.  You should now see in your browser a
+	page called the "Bugzilla Query Page".  It may look daunting, but
+	with this Guide to walk you through it, you will master it in no time.
+      </para>
+    </section>
+    
+    <section id="query">
+      <title>The Bugzilla Query Page</title>
+      <para>
+	The Bugzilla Query Page is the heart and soul of Bugzilla.  It is the master
+	interface where you can find any bug report, comment, or patch currently in the Bugzilla
+	system.  We'll go into how to create your own bug report later on.
+      </para>
+      <para>
+	There are efforts underway to simplify query usage.  If you have a local installation
+	of Bugzilla 2.12 or higher, you should have "quicksearch.html" available
+	to use and simplify your searches.  There is also, or shortly will be, a helper
+	for the query interface, called "queryhelp.cgi".  Landfill tends to run the latest code,
+	so these two utilities should be available there for your perusal.
+      </para>
+      <para>
+	At this point, please visit the main Bugzilla site,
+	<ulink url="http://bugzilla.mozilla.org/query.cgi">
+	bugzilla.mozilla.org</ulink>, to see a more fleshed-out query page.
+      </para>
+      <para>
+	The first thing you need to notice about the Bugzilla Query Page is that
+	nearly every box you see on your screen has a hyperlink nearby, explaining what
+	it is or what it does.  Near the upper-left-hand corner of your browser window
+	you should see the word "Status" underlined.  Select it.
+      </para>
+      <para>
+	Notice the page that popped up?  Every underlined word you see on your screen
+	is a hyperlink that will take you to context-sensitive help.
+	Click around for a while, and learn what everything here does.  To return
+	to the query interface after pulling up a help page, use the "Back" button in
+	your browser.
+      </para>
+      <para>
+	I'm sure that after checking out the online help, you are now an Expert
+	on the Bugzilla Query Page.  If, however, you feel you haven't mastered it yet,
+	let me walk you through making a few successful queries to find out what there
+	are in the Bugzilla bug-tracking system itself.
+      </para>
+      <orderedlist>
+	<listitem>
+	  <para>
+	    Ensure you are back on the "Bugzilla Query Page"
+	    Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys",
+	    "Priority", or "Severity".  The default query for "Status" is to find all bugs that
+	    are NEW, ASSIGNED, or REOPENED, which is what we want.  If you don't select anything
+	    in the other 5 scrollboxes there, then you are saying that "any of these are OK";
+	    we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95"
+	    OpSys (Operating System).  You're smart, I think you have it figured out.
+	  </para>
+	  <para>
+	    Basically, selecting <emphasis>anything</emphasis> on the query page narrows your search
+	    down.  Leaving stuff unselected, or text boxes unfilled, broadens your search!
+	  </para>
+	</listitem>
+
+	<listitem>
+	  <para>
+	    You see the box immediately below the top six boxes that contains an "Email" text box, 
+	    with the words "matching as", a drop-down selection box, then some checkboxes with
+	    "Assigned To" checked by default?  This allows you to filter your search down based upon
+	    email address.  Let's put my email address in there, and see what happens.
+	  </para>
+	  <para>
+	    Type "barnboy@trilobyte.net" in the top Email text box.
+	  </para>
+	</listitem>
+
+	<listitem>
+	  <para>
+	    Let's narrow the search some more.  Scroll down until you find the box with the word
+	    "Program" over the top of it.  This is where we can narrow our search down to only
+	    specific products (software programs or product lines) in our Bugzilla database.
+	    Please notice the box is a <emphasis>scrollbox</emphasis>.  Using the down arrow on the
+	    scrollbox, scroll down until you can see an entry called "Webtools".  Select this entry.
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    Did you notice that some of the boxes to the right changed when you selected "Webtools"?
+	    Every Program (or Product) has different Versions, Components, and Target Milestones associated
+	    with it.  A "Version" is the number of a software program.
+	    <example>
+	      <title>Some Famous Software Versions</title>
+	      <informalexample>
+		<para>
+		  Do you remember the hype in 1995 when Microsoft Windows 95(r) was released?
+		  It may have been several years
+		  ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their
+		  software.  Three years later, they released Microsoft Windows 98(r),
+		  another new version, to great fanfare, and then in 2000 quietly 
+		  released Microsoft Windows ME(Millenium Edition)(r). 
+		</para>
+		<para>
+		  Software "Versions" help a manufacturer differentiate
+		  their current product from their
+		  previous products.  Most do not identify their products
+		  by the year they were released.
+		  Instead, the "original" version of their software will
+		  often be numbered "1.0", with
+		  small bug-fix releases on subsequent tenths of a digit.  In most cases, it's not
+		  a decimal number; for instance, often 1.9 is an <emphasis>older</emphasis> version
+		  of the software than 1.11,
+		  but is a <emphasis>newer</emphasis> version than 1.1.1.
+		</para>
+		<para>
+		  In general, a "Version" in Bugzilla should refer to 
+		  <emphasis>released</emphasis>
+		  products, not products that have not yet been released 
+		  to the public.  Forthcoming products
+		  are what the Target Milestone field is for.
+		</para>
+	      </informalexample>
+	    </example>
+	  </para>
+	  <para>
+	    A "Component" is a piece of a Product.
+	    It may be a standalone program, or some other logical
+	    division of a Product or Program. 
+	    Normally, a Component has a single Owner, who is responsible
+	    for overseeing efforts to improve that Component.
+	    <example>
+	      <title>Mozilla Webtools Components</title>
+	      <informalexample>
+		<para>
+		  Mozilla's "Webtools" Product is composed of several pieces (Components):
+		  <simplelist>
+		    <member><emphasis>Bonsai</emphasis>,
+		      a tool to show recent changes to Mozilla</member>
+		    <member><emphasis>Bugzilla</emphasis>,
+		      a defect-tracking tool</member>
+		    <member><emphasis>Build</emphasis>,
+		      a tool to automatically compile source code
+		      into machine-readable form</member>
+		    <member><emphasis>Despot</emphasis>,
+		      a program that controls access to the other Webtools</member>
+		    <member><emphasis>LXR</emphasis>,
+		      a utility that automatically marks up text files
+		    to make them more readable</member>
+		    <member><emphasis>MozBot</emphasis>,
+		      a "robot" that announces changes to Mozilla in Chat</member>
+		    <member><emphasis>TestManager</emphasis>,
+		      a tool to help find bugs in Mozilla</member>
+		    <member><emphasis>Tinderbox</emphasis>,
+		      which displays reports from Build</member>
+		  </simplelist>
+		</para>
+		<para>
+		  A different person is responsible for each of these Components.
+		  Tara Hernandez keeps
+		  the "Bugzilla" component up-to-date.
+		</para>
+	      </informalexample>
+	    </example>
+	  </para>
+	  <para>
+	    A "Milestone", or "Target Milestone" is a often a planned future "Version" of a
+	    product.  In many cases, though, Milestones simply represent significant dates for
+	    a developer.  Having certain features in your Product is frequently
+	    tied to revenue (money)
+	    the developer will receive if the features work by the time she 
+	    reaches the Target Milestone.
+	    Target Milestones are a great tool to organize your time.
+	    If someone will pay you $100,000 for
+	    incorporating certain features by a certain date,
+	    those features by that Milestone date become
+	    a very high priority.  Milestones tend to be highly malleable creatures,
+	    though, that appear
+	    to be in reach but are out of reach by the time the important day arrives.
+	  </para>
+	  <para>
+	    The Bugzilla Project has set up Milestones for future 
+	    Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc.  However,
+	    a Target Milestone can just as easily be a specific date,
+	    code name, or weird alphanumeric
+	    combination, like "M19".
+	  </para>
+	</listitem>
+
+	<listitem>
+	  <para>
+	    OK, now let's select the "Bugzilla" component from its scrollbox.
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    Skip down the page a bit -- do you see the "submit query" button?
+	    Select it, and let's run
+	    this query!
+	  </para>
+	</listitem>
+	<listitem>
+	  <para>
+	    Congratulations!  You've completed your first Query, and have before you the Bug List
+	    of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net).  If I'm
+	    doing well,
+	    you'll have a cryptic "Zarro Boogs Found" message on your screen.  It is just
+	    a happy hacker's way of saying "Zero Bugs Found".  However, I am fairly certain I will
+	    always have some bugs assigned to me that aren't done yet,
+	    so you won't often see that message!
+	  </para>
+	</listitem>
+      </orderedlist>
+      <para>
+	I encourage you to click the bug numbers in the left-hand column and examine
+	my bugs.  Also notice that if you click the underlined 
+	links near the top of this page, they do
+	not take you to context-sensitive help here,
+	but instead sort the columns of bugs on the screen!
+	When you need to sort your bugs by priority, severity,
+	or the people they are assigned to, this
+	is a tremendous timesaver.
+      </para>
+      <para>
+	A couple more interesting things about the Bug List page:
+	<simplelist>
+	  <member><emphasis>Change Columns</emphasis>:
+	    by selecting this link, you can show all kinds
+	    of information in the Bug List</member>
+	  <member><emphasis>Change several bugs at once</emphasis>:
+	    If you have sufficient rights to change all
+	    the bugs shown in the Bug List, you can mass-modify them.
+	    This is a big time-saver.</member>
+	  <member><emphasis>Send mail to bug owners</emphasis>:
+	    If you have many related bugs, you can request
+	    an update from every person who owns the bugs in
+	    the Bug List asking them the status.</member>
+	  <member><emphasis>Edit this query</emphasis>:
+	    If you didn't get exactly the results you were looking for,
+	    you can return to the Query page through this link and make
+	    small revisions to the query you just made so
+	    you get more accurate results.</member>
+	</simplelist>
+      </para>
+      <note>
+	<para>
+	  There are many more options to the Bugzilla Query Page 
+	  and the Bug List than I have shown you.
+	  But this should be enough for you to learn to get around.
+	  I encourage you to check out the
+	  <ulink url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink>
+	  to learn about the Anatomy
+	  and Life Cycle of a Bug before continuing.
+	</para>
+      </note>
+    </section>
+    
+    
+    <section id="bugreports">
+      <title>Creating and Managing Bug Reports</title>
+      <epigraph>
+	<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
+      </epigraph>
+      
+      <section id="bug_writing">
+	<title>Writing a Great Bug Report</title>
+	<para>
+	  Before we plunge into writing your first bug report, I encourage you to read 
+	  <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">Mozilla.org's 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 the failure go a long way toward ensuring accurate,
+	  responsible fixes for the bug that bit you.
+	</para>
+	<para>
+	  While you are at it, why not learn how to find previously reported bugs?  Mozilla.org
+	  has published a great tutorial on finding duplicate bugs, available at
+	  <ulink url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html">
+	    http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
+	</para>
+	<para>
+	  I realize this was a lot to read.  However, understanding the mentality of writing
+	  great bug reports will help us on the next part!
+	</para>
+	<orderedlist>
+	  <listitem>
+	    <para>
+	      Go back to <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
+		http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
+	      in your browser.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Select the 
+	      <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi">
+		Enter a new bug report</ulink> link.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Select a product.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Now you should be at the "Enter Bug" form.
+	      The "reporter" should have been automatically filled out
+	      for you (or else Bugzilla prompted you to Log In again
+	      -- you did keep the email with your username
+	      and password, didn't you?).
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Select a Component in the scrollbox.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Bugzilla should have made reasonable guesses, based upon your browser,
+	      for the "Platform" and "OS" drop-down
+	      boxes.  If those are wrong, change them -- if you're on an SGI box
+	      running IRIX, we want to know!
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Fill in the "Assigned To" box with the email address you provided earlier. 
+	      This way you don't end up sending copies of your bug to lots of other people,
+	      since it's just a test bug.
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Leave the "CC" text box blank. 
+	      Fill in the "URL" box with "http://www.mozilla.org".
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Enter "The Bugzilla Guide" in the Summary text box,
+	      and place any comments you have on this
+	      tutorial, or the Guide in general, into the Description box.
+	    </para>
+	  </listitem>
+	</orderedlist>
+	<para>
+	  Voila!  Select "Commit" and send in your bug report!
+	  Next we'll look at resolving bugs.
+	</para>
+      </section>
+
+      <section id="bug_manage">
+	<title>Managing your Bug Reports</title>
+	<para>
+	  OK, you should have a link to the bug you just created near the top of your page.
+	  It should say
+	  "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX".
+	  Select this link.
+	</para>
+	<orderedlist>
+	  <listitem>
+	    <para>
+	      Scroll down a bit on the subsequent page,
+	      until you see the "Resolve bug, changing resolution to (dropdown box).
+	      Normally, you would
+	      "Accept bug (change status to ASSIGNED)", fix it, and then resolve.
+	      But in this case, we're
+	      going to short-circuit the process because this wasn't a real bug.
+	      Change the dropdown next to
+	      "Resolve Bug" to "INVALID", make sure the radio button is
+	      marked next to "Resolve Bug", then
+	      click "Commit".
+	    </para>
+	  </listitem>
+	  <listitem>
+	    <para>
+	      Hey!  It said it couldn't take the change in a big red box!
+	      That's right, you must specify
+	      a Comment in order to make this change.  Select the "Back"
+	      button in your browser, add a
+	      Comment, then try Resolving the bug with INVALID status again.
+	      This time it should work.
+	    </para>
+	  </listitem>
+	</orderedlist>
+	<para>
+	  You have now learned the basics of Bugzilla navigation,
+	  entering a bug, and bug maintenance.
+	  I encourage you to explore these features, and see what you can do with them!
+	  We'll spend no more time on individual Bugs or Queries from this point on, so you are
+	  on your own there.
+	</para>
+	<para>
+	  But I'll give a few last hints!
+	</para>
+	<para>
+	  There is a <ulink url="http://bugzilla.mozilla.org/help.html">CLUE</ulink>
+	  on the Query page
+	  that will teach you more how to use the form.
+	</para>
+	<para>
+	  If you click the hyperlink on the
+	  <ulink url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink>
+	  box of the Query page, you will be presented a form that will describe what all
+	  the components are.
+	</para>
+	<para>
+	  Possibly the most powerful feature of the Query page is the 
+	  <ulink url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section.
+	  It's a bit confusing to use the first time, but can provide unparalleled
+	  flexibility in your queries,
+	  allowing you to build extremely powerful requests.
+	</para>
+	<para>
+	  Finally, you can build some nifty 
+	  <ulink url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink>
+	  using the "Bug Reports" link near the bottom of the query page, and also
+	  available via the "Reports" link
+	  at the footer of each page.
+	</para>
+      </section>
+    </section>
+
+  </section>
+
+  <section id="init4me">
+    <title>What's in it for me?</title>
+    <epigraph>
+      <para>
+	Indiana, it feels like we walking on fortune cookies!
+      </para>
+      <para>
+	These ain't fortune cookies, kid...
+      </para>
+    </epigraph>
+    <para>
+      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
+      <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1">
+      Landfill</ulink>.
+    </para>
+    <section id="accountsettings">
+      <title>Account Settings</title>
+      <para>
+	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 <emphasis>current</emphasis>
+	password into the "Old Password" field. 
+	If you wish to change your password, type the new password you
+	want into the "New Password" field and again into the "Re-enter 
+	new password" field to ensure
+	you typed your new password correctly.  Select the "Submit" button and you're done!
+      </para>
+    </section>
+    <section id="emailsettings">
+      <title>Email Settings</title>
+      <section id="notification">
+	<title>Email Notification</title>
+	<para>
+	  Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
+	  In the drop-down "Notify me of changes to", select one of
+	  <simplelist>
+	    <member><emphasis>All qualifying bugs</emphasis>: sends you every change to every bug
+	      where your name is somewhere on it, regardless of who changed it.</member>
+	    <member><emphasis>Only those bugs which I am listed in the CC line</emphasis>: prevents
+	      you from receiving mail for which you are the reporter,'
+	      owner, or QA contact.  If you are on the CC
+	      list, presumably someone had a <emphasis>good</emphasis>
+	      reason for you to get the email.</member>
+	    <member><emphasis>All qulifying bugs except those which I change</emphasis>:
+	      This is the default, and
+	      a sensible setting.  If someone else changes your bugs, you will get emailed,
+	      but if you change bugs
+	      yourself you will receive no notification of the change.</member>
+	  </simplelist>
+	</para>
+      </section>
+      <section id="newemailtech">
+	<title>New Email Technology</title>
+	<note>
+	  <para>
+	    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.
+	  </para>
+	</note>
+	<para>
+	  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.
+	</para>
+	<para>
+	  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.
+	</para>
+      </section>
+      <section id="watchsettings">
+	<title>"Watching" Users</title>
+	<note>
+	  <para>
+	    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".
+	  </para>
+	</note>
+	<para>
+	  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.
+	</para>
+      </section>
+    </section>
+    <section id="footersettings">
+      <title>Page Footer</title>
+      <note>
+	<para>
+	  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!
+	</para>
+      </note>
+      <para>
+	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...
+      </para>
+      <tip>
+	<para>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.</para>
+      </tip>
+    </section>
+    <section id="permissionsettings">
+      <title>Permissions</title>
+      <para>
+	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.
+      </para>
+    </section>
+  </section>
+
+  <section id="usingbz-conc">
+    <title>Using Bugzilla-Conclusion</title>
+    <para>
+      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
+      <ulink url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink>
+      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
+    </para>
+  </section>
+</chapter>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:Bugzilla-Guide\.sgml
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
diff --git a/docs/sgml/variants.sgml b/docs/sgml/variants.sgml
new file mode 100644
index 000000000..e69de29bb
--- /dev/null
+++ b/docs/sgml/variants.sgml