From 78e29c8900fa96d67163a34a0c02c7cecb31b55f Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Wed, 23 Apr 2003 09:04:01 +0000 Subject: The source files for the Bugzilla Guide have long been using the XML version of DocBook but still residing in the sgml/ directory with an extension of .sgml. In an effort to maintain CVS history, the raw files were copied on the CVS server to the xml/ directory and renamed to have .xml for the extension; any checkins before this one did have the .sgml extension. --- docs/sgml/about.sgml | 227 --------------------------------------------------- 1 file changed, 227 deletions(-) delete mode 100644 docs/sgml/about.sgml (limited to 'docs/sgml/about.sgml') diff --git a/docs/sgml/about.sgml b/docs/sgml/about.sgml deleted file mode 100644 index ccfcdd23e..000000000 --- a/docs/sgml/about.sgml +++ /dev/null @@ -1,227 +0,0 @@ - - - -About This Guide - - - -
- Disclaimer - - No liability for the contents of this document can be accepted. - Use the concepts, examples, and other content 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, - 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 - your security needs are met. - -
- - - -
- New Versions - - 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 bugzilla.org; 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. - - - The latest version of this document can always be checked out via CVS. - Please follow the instructions available at - the Mozilla CVS page, - and check out the mozilla/webtools/bugzilla/docs/ - subtree. - - - The Bugzilla Guide is currently only available in English. - If you would like to volunteer to translate it, please contact - Dave Miller. - -
- -
- Credits - - The people listed below have made enormous contributions to the - creation of this Guide, through their writing, dedicated hacking efforts, - numerous e-mail and IRC support sessions, and overall excellent - contribution to the Bugzilla community: - - - - - - 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 - Ben FrantzDale - Eric Hanson - Gervase Markham - Joe Robins - Kevin Brannen - Ron Teitelbaum - Spencer Smith - Zach Liption - - . - -
- - -&conventions; - - - -- cgit v1.2.3-24-g4f1b