Debbugs since ~1993
there's a soap interface, mainly used by reportbug-ng

People that knows sth. about debbugs:
 - Colin Watson (cjwatson), U.K.
 - Blars Blarson (blarson), US
 - Don Armstrong (don, dondelelcaro), US
 - Ian Jackson

source:
 * bzr branch http://bugs.debian.org/debbugs-source/mainline/
   (could this be migrated to GIT? Don would rather not like to change.)
 * divided in email and web processing
 * should have a link to its own source

each bug is its own mailinglist

where are things persisted?
  there's a big spool dir with 4 files per bug:
   - a .log file, where all mails gets appended to
   - .summary, updated with bug metadata (package name, reporter, severity, etc.)
   - .report, containing the original report
   - the 4. file is .status, but it's obsolete, please don't use it :-)
   there are also many indices:
   - index.db and index.archive
   - by-*.idx
   - should eventually be replaced with a real database
   - would benefit from a real DBA

Performance problems with debbugs
  - Don is working on this; mostly by an extra MLDBM index containing bug titles and such

Intro tasks
 mostly involve CGI fixes, since those don't affect core functionality of the BTS
 check bug list, look for presentation issues
 modifying bug display templates
 searching can be done with local-debbugs


What does it mean, if a bug is "archived"?
   - moved from the normal database to archive/
   - don't accept emails anymore, important to fight spam, so that old reports 
   - don't appear in regular searches
   - Unarchive command reopens bugs that have been archived
   http://www.debian.org/Bugs/server-control

machine that hosts debbugs (busoni) should be accessible to DDs
 master: busoni
 mirrors: duarte, lindberg
 full text search: glinka (as soon as I get finished)
 /srv/bugs.debian.org/

debbugs-local/experimental
 - local-debbugs --mirror

debian packages related to debbugs
 - debbugs - The bug tracking system based on the active Debian BTS
     ancient version in unstable/stable, more recent but not current in experimental
 - python-btsutils - Python module to interact with debbugs servers
 - python-debianbts - Python interface to Debian's Bug Tracking System
 - debian-bts-applet - GNOME panel applet for monitoring the status of Debian bugs
 - reportbug - reports bugs in the Debian distribution
 - reportbug-ng - An easy to use alternative to Debian's classic reportbug
 - debbugs-el -> debian-el

Main email-handling code is in scripts/
Two main interesting scripts there:
  service - handles mail to control@, request@ (most actual code now in Debbugs::Control)
  process - handles mail to NNN@, submit@, etc.
  spamscan - horrible code by Blars, runs spamassassin, multi-threaded program, nowadays DSA do greylisting etc.; also does cross-assassin (first 4 copies of borderline mails)
As email comes in:
  procmail -> spool/incoming -> spamscan -> processall -> process/service
  
Web processing is in cgi/
  bugreport.cgi - shows an individual bug


lists has an svn repository with spamassassin rules, shared by the BTS
some rules only apply to lists or only to bugs

Workflow of a bug mail coming in: ...? See above ^
  1. 
  2.
  3.
  
  
bug subscriptions handled by forwarding e-mails to a configured list domain (smartlist)
bugs themselves handled by enemies-of-carlotta (blame liw)
automatically creates a bug mailing list every time a new subscription comes up
externally implemented to avoid having to have complications of bounce handling etc.
subscription database is on liszt
 /var/list/bin/checklists ?
 would need to be sent back to debbugs in order for pkgreport to find it
 /var/list/buglists/subscriber.list is the file that actually has the buglist
 assistance from DSA/listmaster to sync file across, then update index
  
http://bugs.debian.org/pseudopackages/ is the master location for pseudo package descriptions and maintainers
  
What's the package name for bugs against debian's bugtracker?
  http://bugs.debian.org/bugs.debian.org	issues with our bugs database, etc
  http://bugs.debian.org/debbugs		issues with the software

Mailing list of people responsible for debian's bugtracker?
    owner@bugs.debian.org
	Don Armstrong -- most of the code
	Blars Blarson <blarson@d.o> -- spam handling
    debian-debbugs@lists.debian.org -- open discussion of debbugs

Other debbugs deployment:
  - kde used it
  - emacs