[Collab-qa-commits] r857 - in udd: . doc
neronus-guest at alioth.debian.org
neronus-guest at alioth.debian.org
Sat May 24 12:02:40 UTC 2008
Author: neronus-guest
Date: 2008-05-24 12:02:33 +0000 (Sat, 24 May 2008)
New Revision: 857
Added:
udd/doc/
udd/doc/bugs.debian.org.doc
udd/doc/bugs.debian.org.otl
udd/doc/config.README
udd/doc/database.dia
udd/doc/nnnnnn.css
udd/doc/scripts.README
Log:
Added documentation directory
Created some documentation
Added: udd/doc/bugs.debian.org.doc
===================================================================
--- udd/doc/bugs.debian.org.doc (rev 0)
+++ udd/doc/bugs.debian.org.doc 2008-05-24 12:02:33 UTC (rev 857)
@@ -0,0 +1,246 @@
+<?xml version="1.0"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
+
+<article class="whitepaper">
+ <section>
+ <title>Overview of information contained in bugs.debian.org</title>
+ <para />
+ </section>
+ <section>
+ <title>Structure</title>
+ <para />
+ </section>
+ <section>
+ <title>; The database consists of a number of bugs</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug belongs to exactly one package and version</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug is identified by a number - its ID</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has a time when in arrived</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has a status</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has a severity</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has zero or more tags attached to him</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has been submitted by a person (Identified per email and name</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has an owner</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has a title</title>
+ <para />
+ </section>
+ <section>
+ <title>; Each bug has a initial report, and possibly further conversation</title>
+ <para />
+ </section>
+ <section>
+ <title>; For each bug and user, there are zero or more usertags</title>
+ <para />
+ </section>
+ <section>
+ <title>; There is some hidden additional information</title>
+ <para />
+ </section>
+ <section>
+ <title>Status</title>
+ <para>A bug's status is one of:</para>
+ </section>
+ <section>
+ <title>| open | The bug is still open and has to be processed |</title>
+ <para />
+ </section>
+ <section>
+ <title>| forwarded | The bug has been forwarded |</title>
+ <para />
+ </section>
+ <section>
+ <title>| pending |</title>
+ <para />
+ </section>
+ <section>
+ <title>| fixed |</title>
+ <para />
+ </section>
+ <section>
+ <title>| done |</title>
+ <para />
+ </section>
+ <section>
+ <title>Severity</title>
+ <para>Each bug's severity is one of:</para>
+ </section>
+ <section>
+ <title>| critical |</title>
+ <para />
+ </section>
+ <section>
+ <title>| grave |</title>
+ <para />
+ </section>
+ <section>
+ <title>| serious |</title>
+ <para />
+ </section>
+ <section>
+ <title>| important |</title>
+ <para />
+ </section>
+ <section>
+ <title>| normal |</title>
+ <para />
+ </section>
+ <section>
+ <title>| minor |</title>
+ <para />
+ </section>
+ <section>
+ <title>| wishlist |</title>
+ <para />
+ </section>
+ <section>
+ <title>| fixed |</title>
+ <para />
+ </section>
+ <section>
+ <title>Tags</title>
+ <para>Each bug has a zero or more tags attached to him</para>
+ </section>
+ <section>
+ <title>| potato |</title>
+ <para />
+ </section>
+ <section>
+ <title>| woody |</title>
+ <para />
+ </section>
+ <section>
+ <title>| sarge |</title>
+ <para />
+ </section>
+ <section>
+ <title>| sarge-ignore |</title>
+ <para />
+ </section>
+ <section>
+ <title>| etch |</title>
+ <para />
+ </section>
+ <section>
+ <title>| etch-ignore |</title>
+ <para />
+ </section>
+ <section>
+ <title>| lenny |</title>
+ <para />
+ </section>
+ <section>
+ <title>| lenny-ignore |</title>
+ <para />
+ </section>
+ <section>
+ <title>| sid |</title>
+ <para />
+ </section>
+ <section>
+ <title>| experimental |</title>
+ <para />
+ </section>
+ <section>
+ <title>| confirmed |</title>
+ <para />
+ </section>
+ <section>
+ <title>| d-i |</title>
+ <para />
+ </section>
+ <section>
+ <title>| fixed |</title>
+ <para />
+ </section>
+ <section>
+ <title>| fixed-in-experimental |</title>
+ <para />
+ </section>
+ <section>
+ <title>| fixed-upstream |</title>
+ <para />
+ </section>
+ <section>
+ <title>| help |</title>
+ <para />
+ </section>
+ <section>
+ <title>| l10n |</title>
+ <para />
+ </section>
+ <section>
+ <title>| moreinfo |</title>
+ <para />
+ </section>
+ <section>
+ <title>| patch |</title>
+ <para />
+ </section>
+ <section>
+ <title>| pending |</title>
+ <para />
+ </section>
+ <section>
+ <title>| security |</title>
+ <para />
+ </section>
+ <section>
+ <title>| unreproducible |</title>
+ <para />
+ </section>
+ <section>
+ <title>| upstream |</title>
+ <para />
+ </section>
+ <section>
+ <title>| wontfix |</title>
+ <para />
+ </section>
+ <section>
+ <title>| ipv6 |</title>
+ <para />
+ </section>
+ <section>
+ <title>| lfs |</title>
+ <para />
+ </section>
+ <section>
+ <title>Usertags</title>
+ <para>Each user can define their own usertags. These usertags then can be
+applied to packages of their own choosing. It is very convenient to
+get the usertags of a specific user, but expensive to get the usertags
+of a specific package</para>
+ </section>
+ <section>
+ <title>Hidden information</title>
+ <para>Each bug has been found for a specific version, and is possibly fixed
+for some other version. Bugs can be fixed in more the one version of a
+package. So for each package, debian release and bug, the bug can affect
+the package in the given release.</para>
+ </section>
\ No newline at end of file
Added: udd/doc/bugs.debian.org.otl
===================================================================
--- udd/doc/bugs.debian.org.otl (rev 0)
+++ udd/doc/bugs.debian.org.otl 2008-05-24 12:02:33 UTC (rev 857)
@@ -0,0 +1,71 @@
+ Overview of information contained in bugs.debian.org
+
+ Structure
+ ; The database consists of a number of bugs
+ ; Each bug belongs to exactly one package and version
+ ; Each bug is identified by a number - its ID
+ ; Each bug has a time when in arrived
+ ; Each bug has a status
+ ; Each bug has a severity
+ ; Each bug has zero or more tags attached to him
+ ; Each bug has been submitted by a person (Identified per email and name
+ ; Each bug has an owner
+ ; Each bug has a title
+ ; Each bug has a initial report, and possibly further conversation
+ ; For each bug and user, there are zero or more usertags
+ ; There is some hidden additional information
+ Status
+ : A bug's status is one of:
+ | open | The bug is still open and has to be processed |
+ | forwarded | The bug has been forwarded |
+ | pending |
+ | fixed |
+ | done |
+ Severity
+ : Each bug's severity is one of:
+ | critical |
+ | grave |
+ | serious |
+ | important |
+ | normal |
+ | minor |
+ | wishlist |
+ | fixed |
+ Tags
+ : Each bug has a zero or more tags attached to him
+ | potato |
+ | woody |
+ | sarge |
+ | sarge-ignore |
+ | etch |
+ | etch-ignore |
+ | lenny |
+ | lenny-ignore |
+ | sid |
+ | experimental |
+ | confirmed |
+ | d-i |
+ | fixed |
+ | fixed-in-experimental |
+ | fixed-upstream |
+ | help |
+ | l10n |
+ | moreinfo |
+ | patch |
+ | pending |
+ | security |
+ | unreproducible |
+ | upstream |
+ | wontfix |
+ | ipv6 |
+ | lfs |
+ Usertags
+ : Each user can define their own usertags. These usertags then can be
+ : applied to packages of their own choosing. It is very convenient to
+ : get the usertags of a specific user, but expensive to get the usertags
+ : of a specific package
+ Hidden information
+ : Each bug has been found for a specific version, and is possibly fixed
+ : for some other version. Bugs can be fixed in more the one version of a
+ : package. So for each package, debian release and bug, the bug can affect
+ : the package in the given release.
Added: udd/doc/config.README
===================================================================
--- udd/doc/config.README (rev 0)
+++ udd/doc/config.README 2008-05-24 12:02:33 UTC (rev 857)
@@ -0,0 +1,14 @@
+The configuration file is in YAML format.
+
+On the toplevel, dbname maps to the name of the database.
+
+Then there is a nested map called types. This maps to a map, which
+map types of data-sources to the scripts to execute to update these sources.
+
+archs maps to a sequence containing the possible architectures.
+
+The other entries all describe a data source. These are maps
+from source names to mappings. These nested mappings are required
+to have a filed that maps type to the type of the data source.
+How the other entries in the nested maps are interpreted depends on the
+type of the source. See the matching gatherer script for information.
Added: udd/doc/database.dia
===================================================================
(Binary files differ)
Property changes on: udd/doc/database.dia
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: udd/doc/nnnnnn.css
===================================================================
--- udd/doc/nnnnnn.css (rev 0)
+++ udd/doc/nnnnnn.css 2008-05-24 12:02:33 UTC (rev 857)
@@ -0,0 +1,244 @@
+ /* copyright notice and filename */
+body {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 10pt;
+}
+ /* title at the top of the page */
+H1 {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 14pt;
+ font-weight: bold;
+ text-align: center;
+ color: black;
+ background-color: #ddddee;
+ padding-top: 20px;
+ padding-bottom: 20px;
+}
+H2 {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 12pt;
+ font-weight: bold;
+ text-align: left;
+ color: black;
+}
+H3 {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 12pt;
+ text-align: left;
+ color: black;
+}
+H4 {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 12pt;
+ text-align: left;
+ color: black;
+}
+H5 {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 10pt;
+ text-align: left;
+ color: black;
+}
+ /* outline level spacing */
+OL {
+ padding-bottom: 8pt;
+}
+ /* global heading settings */
+LI {
+ font-family: helvetica,arial,sans-serif;
+ color: black;
+ font-weight: normal;
+ list-style: lower-alpha;
+ padding-top: 4px;
+}
+ /* level 1 heading overrides */
+LI.L1 {
+ font-size: 12pt;
+ font-weight: bold;
+ list-style: none;
+}
+ /* level 2 heading overrides */
+LI.L2 {
+ font-size: 10pt;
+ font-weight: bold;
+ list-style: none;
+}
+ /* level 3 heading overrides */
+LI.L3 {
+ font-size: 10pt;
+ list-style: none;
+}
+ /* level 4 heading overrides */
+LI.L4 {
+ font-size: 10pt;
+ list-style: none;
+}
+ /* level 5 heading overrides */
+LI.L5 {
+ font-size: 10pt;
+ list-style: none;
+}
+ /* level 6 heading overrides */
+LI.L6 {
+ font-size: 10pt;
+ list-style: none;
+}
+ /* level 7 heading overrides */
+LI.L7 {
+ font-size: 10pt;
+ list-style: none;
+}
+ /* level 1 bullet heading overrides */
+LI.LB1 {
+ font-size: 12pt;
+ font-weight: bold;
+ list-style: disc;
+}
+ /* level 2 bullet heading overrides */
+LI.LB2 {
+ font-size: 10pt;
+ font-weight: bold;
+ list-style: disc;
+}
+ /* level 3 bullet heading overrides */
+LI.LB3 {
+ font-size: 10pt;
+ list-style: disc;
+}
+ /* level 4 bullet heading overrides */
+LI.LB4 {
+ font-size: 10pt;
+ list-style: disc;
+}
+ /* level 5 bullet heading overrides */
+LI.LB5 {
+ font-size: 10pt;
+ list-style: disc;
+}
+ /* level 6 bullet heading overrides */
+LI.LB6 {
+ font-size: 10pt;
+ list-style: disc;
+}
+ /* level 7 bullet heading overrides */
+LI.LB7 {
+ font-size: 10pt;
+ list-style: disc;
+}
+ /* level 1 numeric heading overrides */
+LI.LN1 {
+ font-size: 12pt;
+ font-weight: bold;
+ list-style: decimal;
+}
+ /* level 2 numeric heading overrides */
+LI.LN2 {
+ font-size: 10pt;
+ font-weight: bold;
+ list-style: decimal;
+}
+ /* level 3 numeric heading overrides */
+LI.LN3 {
+ font-size: 10pt;
+ list-style: decimal;
+}
+ /* level 4 numeric heading overrides */
+LI.LN4 {
+ font-size: 10pt;
+ list-style: decimal;
+}
+ /* level 5 numeric heading overrides */
+LI.LN5 {
+ font-size: 10pt;
+ list-style: decimal;
+}
+ /* level 6 numeric heading overrides */
+LI.LN6 {
+ font-size: 10pt;
+ list-style: decimal;
+}
+ /* level 7 numeric heading overrides */
+LI.LN7 {
+ font-size: 10pt;
+ list-style: decimal;
+}
+ /* body text */
+P {
+ font-family: helvetica,arial,sans-serif;
+ font-size: 9pt;
+ font-weight: normal;
+ color: darkgreen;
+}
+ /* preformatted text */
+PRE {
+ font-family: fixed;
+ font-size: 9pt;
+ font-weight: normal;
+ color: darkblue;
+}
+
+TABLE {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 12pt;
+ font-weight: normal;
+ border-collapse: collapse;
+}
+
+TH {
+ border: 1px solid black;
+ padding: 0.5em;
+ background-color: #eeddee;
+}
+
+TD {
+ border: 1px solid black;
+ padding: 0.5em;
+ background-color: #ddeeee;
+}
+
+CODE {
+ background-color: yellow;
+}
+
+TABLE.TAB1 {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 12pt;
+ font-weight: normal;
+ border-collapse: collapse;
+}
+TABLE.TAB2 {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 11pt;
+ font-weight: normal;
+ border-collapse: collapse;
+}
+TABLE.TAB3 {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 10pt;
+ font-weight: normal;
+ border-collapse: collapse;
+}
+TABLE.TAB4 {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 10pt;
+ font-weight: normal;
+ border-collapse: collapse;
+}
+TABLE.TAB5 {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 10pt;
+ font-weight: normal;
+ border-collapse: collapse;
+}
+TABLE.TAB6 {
+ margin-top: 1em;
+ font-family: helvetica,arial,sans-serif;
+ font-size: 10pt;
+ font-weight: normal;
+ border-collapse: collapse;
Added: udd/doc/scripts.README
===================================================================
--- udd/doc/scripts.README (rev 0)
+++ udd/doc/scripts.README 2008-05-24 12:02:33 UTC (rev 857)
@@ -0,0 +1,13 @@
+There will be the following scripts:
+ - One script to setup the database from an empty database.
+ This script has to create the tables and fill in some
+ source-independent values
+ - One script to dispatch the other scripts, based on the source
+ to gather
+ - For every source type a gatherer
+
+All these scripts accept as their first argument the path of the configuration file.
+The setup script doesn't accept any other arguments.
+The dispatch script accepts as arguments names of sources to gather
+The gatherer scripts accept exactly two arguments: The path of the configuration
+file and the name of the source to gather
More information about the Collab-qa-commits
mailing list