summaryrefslogtreecommitdiffstats
path: root/docs/html/glossary.html
blob: 376c259e22908b66dcd198d3454e074b2d8b08db (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
<HTML
><HEAD
><TITLE
>Glossary</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="How to use this License for your documents"
HREF="gfdl-howto.html"></HEAD
><BODY
CLASS="glossary"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="gfdl-howto.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
>&nbsp;</TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="GLOSSARY"
><H1
><A
NAME="glossary"
>Glossary</A
></H1
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2678"
>0-9, high ascii</A
></H1
><DL
><DT
><B
>.htaccess</B
></DT
><DD
><P
>&#13;	    Apache web server, and other NCSA-compliant web servers,
	    observe the convention of using files in directories
	    called <TT
CLASS="filename"
>.htaccess</TT
> files.  These
	    restrict parameters of the web server.  In Bugzilla, they
	    are used to restrict access to certain files which would
	    otherwise compromise your installation.  For instance, the
	    <TT
CLASS="filename"
>localconfig</TT
> file contains the
	    password to your database.  If this information were
	    generally available, and remote access to your database
	    turned on, you risk corruption of your database by
	    computer criminals or the curious.
	  </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-a"
>A</A
></H1
><DL
><DT
><B
>Apache</B
></DT
><DD
><P
>In this context, Apache is the web server most
	    commonly used for serving up
	    <I
CLASS="glossterm"
>Bugzilla</I
> pages.  Contrary to
	    popular belief, the apache web server has nothing to do
	    with the ancient and noble Native American tribe, but
	    instead derived its name from the fact that it was
	    <SPAN
CLASS="QUOTE"
>"a patchy"</SPAN
> version of the original
	    <SPAN
CLASS="acronym"
>NCSA</SPAN
> world-wide-web server.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-b"
>B</A
></H1
><DL
><DT
><B
>Bug</B
></DT
><DD
><P
>&#13;	    A <SPAN
CLASS="QUOTE"
>"Bug"</SPAN
> in Bugzilla refers to an issue
	    entered into the database which has an associated number,
	    assignments, comments, etc. Some also refer to a
	    <SPAN
CLASS="QUOTE"
>"tickets"</SPAN
> or <SPAN
CLASS="QUOTE"
>"issues"</SPAN
>; in the
	    context of Bugzilla, they are synonymous.
	  </P
></DD
><DT
><B
>Bug Number</B
></DT
><DD
><P
>&#13;	    Each Bugzilla Bug is assigned a number that uniquely
	    identifies that Bug.  The Bug associated with a Bug Number
	    can be pulled up via a query, or easily from the very
	    front page by typing the number in the "Find" box.
	  </P
></DD
><DT
><B
>Bug Life Cycle</B
></DT
><DD
><P
>A Bug has stages through which it must pass before
	    becoming a <SPAN
CLASS="QUOTE"
>"closed bug"</SPAN
>, including
	    acceptance, resolution, and verification.  The <SPAN
CLASS="QUOTE"
>"Bug
	      Life Cycle"</SPAN
> is moderately flexible according to
	    the needs of the organization using it, though.</P
></DD
><DT
><B
>Bugzilla</B
></DT
><DD
><P
>&#13;	    Bugzilla is the industry-standard bug tracking system.  It
	    is quite popular among Open Source enthusiasts.
	  </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-c"
></A
></H1
><DL
><DT
><A
NAME="gloss-component"
><B
>Component</B
></A
></DT
><DD
><P
>&#13;	    A Component is a subsection of a Product.  It should be a
	    narrow category, tailored to your organization.  All
	    Products must contain at least one Component (and, as a
	    matter of fact, creating a Product with no Components will
	    create an error in Bugzilla).
	  </P
></DD
><DT
><A
NAME="gloss-cpan"
><B
><SPAN
CLASS="acronym"
>CPAN</SPAN
></B
></A
></DT
><DD
><P
><SPAN
CLASS="acronym"
>CPAN</SPAN
> stands for the
	    <SPAN
CLASS="QUOTE"
>"Comprehensive Perl Archive Network"</SPAN
>.  CPAN
	    maintains a large number of extremely useful
	    <I
CLASS="glossterm"
>Perl</I
> modules.  By themselves, Perl
	    modules generally do nothing, but when used as part of a
	    larger program, they provide much-needed algorithms and
	    functionality.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-d"
>D</A
></H1
><DL
><DT
><B
>daemon</B
></DT
><DD
><P
>A daemon is a computer program which runs in the
	    background.  In general, most daemons are started at boot
	    time via System V init scripts, or through RC scripts on
	    BSD-based systems.  <I
CLASS="glossterm"
>mysqld</I
>, the
	    MySQL server, and <I
CLASS="glossterm"
>apache</I
>, a web
	    server, are generally run as daemons.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-g"
></A
></H1
><DL
><DT
><B
>Groups</B
></DT
><DD
><P
>The word <SPAN
CLASS="QUOTE"
>"Groups"</SPAN
> has a very special
	    meaning to Bugzilla.  Bugzilla's main security mechanism
	    comes by lumping users into groups, and assigning those
	    groups certain privileges to
	    <I
CLASS="glossterm"
>Products</I
> and
	    <I
CLASS="glossterm"
>Components</I
> in the
	    <I
CLASS="glossterm"
>Bugzilla</I
> database.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-i"
>I</A
></H1
><DL
><DT
><A
NAME="gloss-infiniteloop"
><B
>Infinite Loop</B
></A
></DT
><DD
><P
>A loop of information that never ends; see recursion.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-m"
>M</A
></H1
><DL
><DT
><B
>mysqld</B
></DT
><DD
><P
>mysqld is the name of the
	    <I
CLASS="glossterm"
>daemon</I
> for the MySQL database.  In
	    general, it is invoked automatically through the use of
	    the System V init scripts on GNU/Linux and AT&#38;T System
	    V-based systems, such as Solaris and HP/UX, or through the
	    RC scripts on BSD-based systems.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-p"
>P</A
></H1
><DL
><DT
><B
>Product</B
></DT
><DD
><P
>A Product is a broad category of types of bugs.  In
	    general, there are several Components to a Product.  A
	    Product also defines a default Group (used for Bug
	    Security) for all bugs entered into components beneath
	    it.</P
><DIV
CLASS="example"
><A
NAME="AEN2769"
></A
><P
><B
>Example 1. A Sample Product</B
></P
><P
>A company sells a software product called
	      <SPAN
CLASS="QUOTE"
>"X"</SPAN
>.  They also maintain some older
	      software called <SPAN
CLASS="QUOTE"
>"Y"</SPAN
>, and have a secret
	      project <SPAN
CLASS="QUOTE"
>"Z"</SPAN
>.  An effective use of Products
	      might be to create Products <SPAN
CLASS="QUOTE"
>"X"</SPAN
>,
	      <SPAN
CLASS="QUOTE"
>"Y"</SPAN
>, <SPAN
CLASS="QUOTE"
>"Z"</SPAN
>, each with Components
	      of User Interface, Database, and Business Logic.  They
	      might also change group permissions so that only those
	      people who are members of Group <SPAN
CLASS="QUOTE"
>"Z"</SPAN
> can see
	      components and bugs under Product
	      <SPAN
CLASS="QUOTE"
>"Z"</SPAN
>.</P
></DIV
></DD
><DT
><B
>Perl</B
></DT
><DD
><P
>First written by Larry Wall, Perl is a remarkable
	    program language.  It has the benefits of the flexibility
	    of an interpreted scripting language (such as shell
	    script), combined with the speed and power of a compiled
	    language, such as C.  <I
CLASS="glossterm"
>Bugzilla</I
> is
	    maintained in Perl.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-q"
>Q</A
></H1
><DL
><DT
><B
>QA</B
></DT
><DD
><P
><SPAN
CLASS="QUOTE"
>"QA"</SPAN
>, <SPAN
CLASS="QUOTE"
>"Q/A"</SPAN
>, and
	    <SPAN
CLASS="QUOTE"
>"Q.A."</SPAN
> are short for <SPAN
CLASS="QUOTE"
>"Quality
	      Assurance"</SPAN
>.  In most large software development
	    organizations, there is a team devoted to ensuring the
	    product meets minimum standards before shipping.  This
	    team will also generally want to track the progress of
	    bugs over their life cycle, thus the need for the
	    <SPAN
CLASS="QUOTE"
>"QA Contact"</SPAN
> field in a Bug.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-r"
>R</A
></H1
><DL
><DT
><A
NAME="gloss-recursion"
><B
>Recursion</B
></A
></DT
><DD
><P
>The property of a function looking back at itself for
	    something.  <SPAN
CLASS="QUOTE"
>"GNU"</SPAN
>, for instance, stands for
	    <SPAN
CLASS="QUOTE"
>"GNU's Not UNIX"</SPAN
>, thus recursing upon itself
	    for definition.  For further clarity, see Infinite
	    Loop.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-s"
>S</A
></H1
><DL
><DT
><B
><SPAN
CLASS="acronym"
>SGML</SPAN
></B
></DT
><DD
><P
><SPAN
CLASS="acronym"
>SGML</SPAN
> stands for <SPAN
CLASS="QUOTE"
>"Standard
	      Generalized Markup Language"</SPAN
>.  Created in the
	    1980's to provide an extensible means to maintain
	    documentation based upon content instead of presentation,
	    <SPAN
CLASS="acronym"
>SGML</SPAN
> has withstood the test of time as
	    a robust, powerful language.
	    <I
CLASS="glossterm"
><SPAN
CLASS="acronym"
>XML</SPAN
></I
> is the
	    <SPAN
CLASS="QUOTE"
>"baby brother"</SPAN
> of SGML; any valid
	    <SPAN
CLASS="acronym"
>XML</SPAN
> document it, by definition, a valid
	    <SPAN
CLASS="acronym"
>SGML</SPAN
> document.  The document you are
	    reading is written and maintained in
	    <SPAN
CLASS="acronym"
>SGML</SPAN
>, and is also valid
	    <SPAN
CLASS="acronym"
>XML</SPAN
> if you modify the Document Type
	    Definition.</P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-t"
>T</A
></H1
><DL
><DT
><A
NAME="gloss-target-milestone"
><B
>Target Milestone</B
></A
></DT
><DD
><P
>&#13;	    Target Milestones are Product goals.  They are
	    configurable on a per-Product basis.  Most software
	    development houses have a concept of
	    <SPAN
CLASS="QUOTE"
>"milestones"</SPAN
> where the people funding a
	    project expect certain functionality on certain dates.
	    Bugzilla facilitates meeting these milestones by giving
	    you the ability to declare by which milestone a bug will be
	    fixed, or an enhancement will be implemented.
	  </P
></DD
></DL
></DIV
><DIV
CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="gloss-z"
>Z</A
></H1
><DL
><DT
><A
NAME="zarro-boogs-found"
><B
>Zarro Boogs Found</B
></A
></DT
><DD
><P
>This is the cryptic response sent by Bugzilla when a
	    query returned no results.  It is just a goofy way of
	    saying "Zero Bugs Found".</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="gfdl-howto.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to use this License for your documents</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>