summaryrefslogtreecommitdiffstats
path: root/docs/en
diff options
context:
space:
mode:
authorgerv%gerv.net <>2008-04-04 13:48:21 +0200
committergerv%gerv.net <>2008-04-04 13:48:21 +0200
commit4878c5574882984a422443f98b24a35580c031b1 (patch)
tree21d94f090182d39b3378726ac19a394222e48cd2 /docs/en
parent60ef8361065fceca296fcc8b53fe4434a2d57e53 (diff)
downloadbugzilla-4878c5574882984a422443f98b24a35580c031b1.tar.gz
bugzilla-4878c5574882984a422443f98b24a35580c031b1.tar.xz
Merging from 2.16 branch.
Diffstat (limited to 'docs/en')
-rw-r--r--docs/en/xml/introduction.xml92
1 files changed, 60 insertions, 32 deletions
diff --git a/docs/en/xml/introduction.xml b/docs/en/xml/introduction.xml
index 3968702c6..33907552b 100644
--- a/docs/en/xml/introduction.xml
+++ b/docs/en/xml/introduction.xml
@@ -1,39 +1,25 @@
<chapter id="introduction">
<title>Introduction</title>
- <section id="what-is-bugzilla">
+ <section id="whatis">
<title>What is Bugzilla?</title>
<para>
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 products.
+ of outstanding problems with their product.
+ 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
+ at the time charged enormous licensing fees, and Bugzilla quickly became
+ a favorite of the open-source crowd (with its genesis in the open-source
+ browser project, Mozilla). It is now the de-facto standard
+ defect-tracking system against which all others are measured.
</para>
-
- <para><emphasis>Do we need more here?</emphasis></para>
-
- </section>
-
- <section id="why-tracking">
- <title>Why use a bug-tracking system?</title>
-
- <para>Those who do not use a bug-tracking system tend to rely on
- shared lists, email, spreadsheets and/or Post-It notes to monitor the
- status of defects. This procedure
- is usually error-prone and tends to cause those bugs judged least
- significant by developers to be dropped or ignored.</para>
-
- <para>Integrated defect-tracking systems make sure that nothing gets
- swept under the carpet; they provide a method of creating, storing,
- arranging and processing defect reports and enhancement requests.</para>
-
- </section>
-
- <section id="why-bugzilla">
- <title>Why use Bugzilla?</title>
- <para>Bugzilla is the leading open-source/free software bug tracking
- system. It boasts many advanced features, including:
+ <para>Bugzilla boasts many advanced features. These include:
<itemizedlist>
<listitem>
<para>Powerful searching</para>
@@ -68,12 +54,12 @@
</listitem>
<listitem>
- <para>Completely customizable and/or localizable web user
- interface</para>
+ <para>Web, XML, email and console interfaces</para>
</listitem>
<listitem>
- <para>Additional XML, email and console interfaces</para>
+ <para>Completely customisable and/or localisable web user
+ interface</para>
</listitem>
<listitem>
@@ -85,7 +71,34 @@
</listitem>
</itemizedlist>
</para>
-
+ </section>
+
+ <section id="why">
+ <title>Why Should We Use Bugzilla?</title>
+
+ <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
@@ -95,7 +108,22 @@
<ulink url="http://www.cvshome.org">CVS</ulink>,
<ulink url="http://www.mozilla.org/bonsai.html">Bonsai</ulink>, or
<ulink url="http://www.perforce.com">Perforce SCM</ulink>, Bugzilla
- provides a powerful, easy-to-use configuration management solution.</para>
+ 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
+ <emphasis>something</emphasis>
+ 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 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>
</chapter>
@@ -114,7 +142,7 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
-sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter")
+sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End: