[Collab-qa-commits] r1083 - udd/doc/sources
he at alioth.debian.org
he at alioth.debian.org
Tue Aug 12 09:03:39 UTC 2008
Author: he
Date: 2008-08-12 09:03:38 +0000 (Tue, 12 Aug 2008)
New Revision: 1083
Added:
udd/doc/sources/carnivore
udd/doc/sources/lintian
Log:
Add documentation for the carnivore/lintian gatherers
Added: udd/doc/sources/carnivore
===================================================================
--- udd/doc/sources/carnivore (rev 0)
+++ udd/doc/sources/carnivore 2008-08-12 09:03:38 UTC (rev 1083)
@@ -0,0 +1,25 @@
+DESCRIPTION
+ The carnivore source type handles the data provided by the carnivore
+ QA-subproject, aiming to connect several identities of the same
+ person (ie, different mail addresses, variants of the same name,
+ OpenPGP key IDs) with each other.
+
+ The imported data is the carnivore report created on a regular basis
+ in merkel.debian.org:/org/qa.debian.org/carnivore (see the README
+ files there for more information on the project).
+
+ We import all relevant carnivore data, by assigning a unique integer
+ ID to each carnivore entity (who can have several names, mail addresses
+ and keys) ad then pushing all that data to the DB. Four tables are
+ created:
+ * emails-table: (ID, mail) mapping
+ * names-table: (ID, name) mapping
+ * keys-table: (ID, key) mapping
+ * login-table: (ID, login) mapping, login being the debian.org login
+
+ _keys and _login are only set for full Debian Developers.
+
+CONFIGURATION:
+ path: The path of the carnivore report to be read
+ emails-table, names-tables, key-table, login-table: The names of the
+ database tables used for the different mappings
Added: udd/doc/sources/lintian
===================================================================
--- udd/doc/sources/lintian (rev 0)
+++ udd/doc/sources/lintian 2008-08-12 09:03:38 UTC (rev 1083)
@@ -0,0 +1,15 @@
+DESCRIPTION
+ The lintian source type handles lintian log files.
+
+ The raw data of a (full, hopefully) lintian run, for example from
+ http://lintian.debian.org/lintian.log, is parsed, all important
+ bits get extracted and put in the DB.
+
+ Each emitted tag is imported to the DB, together with it's type
+ (one of error, warning, information, experimental or overriden),
+ the affected package and the package type (source, udeb and NULL
+ for binary packages).
+
+CONFIGURATION:
+ path: The path of the lintian raw data to be read
+ table: The name of the database table
More information about the Collab-qa-commits
mailing list