diff --git a/webtools/bugzilla/docs/sgml/about.sgml b/webtools/bugzilla/docs/sgml/about.sgml index c6c849539cd..e69de29bb2d 100644 --- a/webtools/bugzilla/docs/sgml/about.sgml +++ b/webtools/bugzilla/docs/sgml/about.sgml @@ -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; - - - diff --git a/webtools/bugzilla/docs/sgml/variants.sgml b/webtools/bugzilla/docs/sgml/variants.sgml index 056ef7d36be..e69de29bb2d 100644 --- a/webtools/bugzilla/docs/sgml/variants.sgml +++ b/webtools/bugzilla/docs/sgml/variants.sgml @@ -1,123 +0,0 @@ - - - Bugzilla Variants and Competitors - - I created this section to answer questions about Bugzilla competitors - and variants, then found a wonderful site which covers an awful lot of what - I wanted to discuss. Rather than quote it in its entirety, I'll simply - refer you here: - - http://linas.org/linux/pm.html - - -
- Red Hat Bugzilla - - Red Hat's old fork of Bugzilla which was based on version 2.8 is now - obsolete. The newest version in use is based on version 2.17.1 and is in - the process of being integrated into the main Bugzilla source tree. The - back-end is modified to work with PostgreSQL instead of MySQL and they have - custom templates to get their desired look and feel, but other than that it - is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of - effort to make sure that the changes he made could be integrated back into - the main tree. - Bug - 98304 exists to track this integration. - - - URL: - - http://bugzilla.redhat.com/bugzilla/ - - - This section last updated 24 Dec 2002 -
- -
- Loki Bugzilla (Fenris) - - Fenris was a fork from Bugzilla made by Loki Games; when - Loki went into receivership, it died. While Loki's other code lives on, - its custodians recommend Bugzilla for future bug-tracker deployments. - - - This section last updated 27 Jul 2002 -
- -
- Issuezilla - - Issuezilla was another fork from Bugzilla, made by collab.net and - hosted at tigris.org. It is also dead; the primary focus of bug-tracking - at tigris.org is their Java-based bug-tracker, - . - - This section last updated 27 Jul 2002 -
- -
- Scarab - - Scarab is a new open source bug-tracking system built using Java - Servlet technology. It is currently at version 1.0 beta 13. - - URL: - http://scarab.tigris.org - - - This section last updated 18 Jan 2003 -
- -
- Perforce SCM - - Although Perforce isn't really a bug tracker, it can be used as - such through the jobs - functionality. - - URL: - - http://www.perforce.com/perforce/technotes/note052.html - - - - This section last updated 27 Jul 2002 -
- -
- SourceForge - - SourceForge is a way of coordinating geographically - distributed free software and open source projects over the Internet. - It has a built-in bug tracker, but it's not highly thought of. - - URL: - - http://www.sourceforge.net - - - This section last updated 27 Jul 2002 -
- - - - diff --git a/webtools/bugzilla/docs/xml/about.xml b/webtools/bugzilla/docs/xml/about.xml index c6c849539cd..ccfcdd23eba 100644 --- a/webtools/bugzilla/docs/xml/about.xml +++ b/webtools/bugzilla/docs/xml/about.xml @@ -153,7 +153,7 @@ for providing insight into the key differences between Red Hat's customized Bugzilla, and being largely responsible for - . + . diff --git a/webtools/bugzilla/docs/xml/variants.xml b/webtools/bugzilla/docs/xml/variants.xml index 056ef7d36be..3a7fd67434d 100644 --- a/webtools/bugzilla/docs/xml/variants.xml +++ b/webtools/bugzilla/docs/xml/variants.xml @@ -10,7 +10,7 @@ http://linas.org/linux/pm.html -
+
Red Hat Bugzilla Red Hat's old fork of Bugzilla which was based on version 2.8 is now