From 4bbb07e8048ef859cfc29c6b9d221840f2c6aed1 Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Fri, 16 Jan 2004 06:34:12 +0000 Subject: Phase 1 of a big documentation update before 2.17.6. --- docs/xml/about.xml | 147 +++++++++++++---------------------------------------- 1 file changed, 34 insertions(+), 113 deletions(-) (limited to 'docs/xml/about.xml') diff --git a/docs/xml/about.xml b/docs/xml/about.xml index 3b0f18e0f..28cc9d8c7 100644 --- a/docs/xml/about.xml +++ b/docs/xml/about.xml @@ -7,7 +7,7 @@ @@ -28,43 +28,28 @@ Disclaimer No liability for the contents of this document can be accepted. - Use the concepts, examples, and other content at your own risk. + Follow the instructions herein at your own risk. This document may contain errors and inaccuracies that may damage your system, cause your partner to leave you, your boss to fire you, your cats to pee on your furniture and clothing, and global thermonuclear war. Proceed with caution. - - 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. - Naming of particular products or brands should not be seen as endorsements, with the exception of the term "GNU/Linux". We - wholeheartedly endorse the use of GNU/Linux in every situation - where it is appropriate. It is an extremely versatile, stable, + wholeheartedly endorse the use of GNU/Linux; it is an extremely + versatile, stable, and robust operating system that offers an ideal operating environment for Bugzilla. - - You are strongly recommended to make a backup of your system - before installing Bugzilla and at regular intervals thereafter. - If you implement any suggestion in this Guide, implement this one! - Although the Bugzilla development team has taken great care to - ensure that all easily-exploitable bugs or options are - documented or fixed in the code, security holes surely exist. - Great care should be taken both in the installation and usage of - this software. Carefully consider the implications of installing - other network services with Bugzilla. The Bugzilla development - team members, Netscape Communications, America Online Inc., and - any affiliated developers or sponsors assume no liability for - your use of this product. You have the source code to this - product, and are responsible for auditing it yourself to ensure + ensure that all exploitable bugs or options have been + fixed, security holes surely exist. Great care should be taken both in + the installation and usage of this software. The Bugzilla development + team members assume no liability for your use of this software. You have + the source code, and are responsible for auditing it yourself to ensure your security needs are met. @@ -77,24 +62,14 @@ This is the &bz-ver; version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. - If you are - reading this from any source other than those below, please - check one of these mirrors to make sure you are reading an - up-to-date version of the Guide. The newest version of this guide can always be found at ; including - documentation for past releases and the current development version. - - - The documentation for the most recent stable release of Bugzilla can also - be found at - The Linux Documentation Project. + url="http://www.bugzilla.org"/>; however, you should read the version + which came with the Bugzilla release you are using. The latest version of this document can always be checked out via CVS. @@ -118,87 +93,33 @@ contribution to the Bugzilla community: - - - - Matthew P. Barnson mbarnson@sisna.com - - for the Herculaean task of pulling together the Bugzilla Guide - and shepherding it to 2.14. - - - - - - Terry Weissman terry@mozilla.org - - for initially writing Bugzilla and creating the README upon - which the UNIX installation documentation is largely based. - - - - - - Tara Hernandez tara@tequilarists.org - - for keeping Bugzilla development going strong after Terry left - mozilla.org and for running landfill. - - - - - - Dave Lawrence dkl@redhat.com - - for providing insight into the key differences between Red - Hat's customized Bugzilla, and being largely responsible for - . - - - - - - Dawn Endico endico@mozilla.org - - for being a hacker extraordinaire and putting up with Matthew's - incessant questions and arguments on irc.mozilla.org in #mozwebtools - - - - - - Jacob Steenhagen jake@bugzilla.org - - for taking over documentation during the 2.17 development - period. - - - - - - - Last but not least, all the members of the - - newsgroup. Without your discussions, insight, suggestions, and patches, - this could never have happened. - - - Thanks also go to the following people for significant contributions - to this documentation (in alphabetical order): - Andrew Pearson + Matthew P. Barnson + Kevin Brannen + Dawn Endico Ben FrantzDale Eric Hanson + Tara Hernandez + Dave Lawrence + Zach Lipton Gervase Markham + Andrew Pearson Joe Robins - Kevin Brannen - Martin Wulffeld - Ron Teitelbaum Spencer Smith - Zach Liption - - . + Jacob Steenhagen + Ron Teitelbaum + Terry Weissman + Martin Wulffeld + . + + + + Last but not least, all the members of the + + netscape.public.mozilla.webtools + newsgroup. Without your discussions, insight, suggestions, and patches, + this could never have happened. -- cgit v1.2.3-24-g4f1b