From 4df3f60fbd218552e023b0f34b6e576df2a3dcef Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Tue, 22 Apr 2003 23:12:22 +0000 Subject: [PATCH] Rewrite the Credits page to match what's on the tip. Also, add a couple glossary links. --- docs/sgml/about.sgml | 132 +++++++++++++++++++++++------------- docs/sgml/conventions.sgml | 12 +++- docs/sgml/glossary.sgml | 2 +- docs/sgml/introduction.sgml | 4 +- docs/xml/about.xml | 132 +++++++++++++++++++++++------------- docs/xml/conventions.xml | 12 +++- docs/xml/glossary.xml | 2 +- docs/xml/introduction.xml | 4 +- 8 files changed, 194 insertions(+), 106 deletions(-) diff --git a/docs/sgml/about.sgml b/docs/sgml/about.sgml index 6413e7205f..f345dc35e9 100644 --- a/docs/sgml/about.sgml +++ b/docs/sgml/about.sgml @@ -76,29 +76,22 @@ New Versions This is the &bzg-ver; version of The Bugzilla Guide. It is so named - to match the current version of Bugzilla. If you are + to match the version of Bugzilla it is disributed with. 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. - This document can be found in the following places: + The newest version of this guide can always be found at bugzilla.org; including + documentation for past releases and the current development version. - - - - bugzilla.org - - - - - The Linux - Documentation Project - - - + 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 @@ -121,44 +114,87 @@ numerous e-mail and IRC support sessions, and overall excellent contribution to the Bugzilla community: - - Matthew P. Barnson - for the Herculaean task of pulling together the Bugzilla Guide and - shepherding it to 2.14. - - - Terry Weissman - for initially writing Bugzilla and creating the - README upon which the UNIX installation documentation is largely based. - - - Tara Hernandez - for keeping Bugzilla development going - strong after Terry left mozilla.org - - - Dave Lawrence - for providing insight into the key differences between Red Hat's - customized Bugzilla, and being largely responsible for the "Red - Hat Bugzilla" appendix - - - Dawn Endico for - being a hacker extraordinaire and putting up with my incessant - questions and arguments on irc.mozilla.org in #mozwebtools - + + + + 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 and backporting relevent docs changes to this 2.16 branch. + + + + + + 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. + + 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 no particular order): - - - Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, - Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham. - + to this documentation (in alphabetical order): + + Andrew Pearson + Ben FrantzDale + Eric Hanson + Gervase Markham + Joe Robins + Kevin Brannen + Ron Teitelbaum + Spencer Smith + Zach Liption + + . + diff --git a/docs/sgml/conventions.sgml b/docs/sgml/conventions.sgml index 7334b02b8b..2dc1911151 100644 --- a/docs/sgml/conventions.sgml +++ b/docs/sgml/conventions.sgml @@ -20,7 +20,7 @@ - Warnings + Use caution @@ -50,7 +50,7 @@ - Information requiring special attention + Warnings @@ -134,6 +134,14 @@ + + Term found in the glossary + + + Bugzilla + + + Code Example diff --git a/docs/sgml/glossary.sgml b/docs/sgml/glossary.sgml index f698c73dc5..929dba4ac0 100644 --- a/docs/sgml/glossary.sgml +++ b/docs/sgml/glossary.sgml @@ -119,7 +119,7 @@ - + Bugzilla diff --git a/docs/sgml/introduction.sgml b/docs/sgml/introduction.sgml index 33907552b5..9e4b5f4b00 100644 --- a/docs/sgml/introduction.sgml +++ b/docs/sgml/introduction.sgml @@ -8,8 +8,8 @@ Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track of outstanding problems with their product. - Bugzilla was originally - written by Terry Weissman in a programming language called TCL, to + Bugzilla was originally written by Terry Weissman in a programming language + called TCL, to replace a rudimentary bug-tracking database used internally by Netscape Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl it remains to this day. Most commercial defect-tracking software vendors diff --git a/docs/xml/about.xml b/docs/xml/about.xml index 6413e7205f..f345dc35e9 100644 --- a/docs/xml/about.xml +++ b/docs/xml/about.xml @@ -76,29 +76,22 @@ New Versions This is the &bzg-ver; version of The Bugzilla Guide. It is so named - to match the current version of Bugzilla. If you are + to match the version of Bugzilla it is disributed with. 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. - This document can be found in the following places: + The newest version of this guide can always be found at bugzilla.org; including + documentation for past releases and the current development version. - - - - bugzilla.org - - - - - The Linux - Documentation Project - - - + 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 @@ -121,44 +114,87 @@ numerous e-mail and IRC support sessions, and overall excellent contribution to the Bugzilla community: - - Matthew P. Barnson - for the Herculaean task of pulling together the Bugzilla Guide and - shepherding it to 2.14. - - - Terry Weissman - for initially writing Bugzilla and creating the - README upon which the UNIX installation documentation is largely based. - - - Tara Hernandez - for keeping Bugzilla development going - strong after Terry left mozilla.org - - - Dave Lawrence - for providing insight into the key differences between Red Hat's - customized Bugzilla, and being largely responsible for the "Red - Hat Bugzilla" appendix - - - Dawn Endico for - being a hacker extraordinaire and putting up with my incessant - questions and arguments on irc.mozilla.org in #mozwebtools - + + + + 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 and backporting relevent docs changes to this 2.16 branch. + + + + + + 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. + + 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 no particular order): - - - Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, - Ron Teitelbaum, Jacob Steenhagen, Joe Robins, Gervase Markham. - + to this documentation (in alphabetical order): + + Andrew Pearson + Ben FrantzDale + Eric Hanson + Gervase Markham + Joe Robins + Kevin Brannen + Ron Teitelbaum + Spencer Smith + Zach Liption + + . + diff --git a/docs/xml/conventions.xml b/docs/xml/conventions.xml index 7334b02b8b..2dc1911151 100644 --- a/docs/xml/conventions.xml +++ b/docs/xml/conventions.xml @@ -20,7 +20,7 @@ - Warnings + Use caution @@ -50,7 +50,7 @@ - Information requiring special attention + Warnings @@ -134,6 +134,14 @@ + + Term found in the glossary + + + Bugzilla + + + Code Example diff --git a/docs/xml/glossary.xml b/docs/xml/glossary.xml index f698c73dc5..929dba4ac0 100644 --- a/docs/xml/glossary.xml +++ b/docs/xml/glossary.xml @@ -119,7 +119,7 @@ - + Bugzilla diff --git a/docs/xml/introduction.xml b/docs/xml/introduction.xml index 33907552b5..9e4b5f4b00 100644 --- a/docs/xml/introduction.xml +++ b/docs/xml/introduction.xml @@ -8,8 +8,8 @@ Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track of outstanding problems with their product. - Bugzilla was originally - written by Terry Weissman in a programming language called TCL, to + Bugzilla was originally written by Terry Weissman in a programming language + called TCL, to replace a rudimentary bug-tracking database used internally by Netscape Communications. Terry later ported Bugzilla to Perl from TCL, and in Perl it remains to this day. Most commercial defect-tracking software vendors -- 2.47.2