Notes from DebConf12

Apertium

  • Language pairs:
    • apertium-en-ca install -> BUG
    • apertium-en-es install -> BUG
    • apertium-eo-ca install -> BUG
    • apertium-eo-es install -> BUG
    • apertium-es-ca install
    • apertium-es-gl install
    • apertium-es-pt install
    • apertium-es-ro install
    • apertium-eu-es install -> BUG
    • apertium-fr-ca install
    • apertium-fr-es install -> BUG
    • apertium-oc-ca install -> BUG
    • apertium-oc-es install -> BUG
    • apertium-pt-ca install
    • apertium-pt-gl install

Debian Science

Lighting Talk

ML Talk

  • maxmind: source free, pay for data (from zigo)

Email Talk

  • debian-user-spanish -> twitter (2 slides)
  • listoso reader (11 slides)
    • use the QA page
    • show it
    • describe it
    • roadmap
  • linux kernel mailing list (2 slides)
    • mention resource, paper

Ouroborus

Collaboration with jergas, el_erno and pankx

Sagemath

Collaboration with thepunisher

NLTK

DebExpo

Tasks

  • Write debian/control
    • Get dependencies
  • Files for installing it

Other pylons projects already in the archive?

Sid Install

(in a virtualenv)

  • Documentation error:
You should use the ‘devel’ branch:

git checkout devel

that branch doesn't exist

  • missing dependent package: iso-codes

#313271 Lost password feature fails

The reset link should activate the account, too.

Well, it actually does remove the activation verification entry there.

BTS

Possible collaborators: ararstafiel, dondelelcaro, paulproteus, arastafiel

Papers

  • What Makes a Good Bug Report?
  Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiss, Rahul Premraj, Thomas Zimmermann
  SIGSOFT 2008/FSE-16, November 9–15, Atlanta, Georgia, USA

2008

  • What Makes a Good Bug Report?
  Thomas Zimmermann, Rahul Premraj, Nicolas Bettenburg, Sascha Just, Adrian Schroter, and Cathrin Weiss
  IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 36, NO. 5, SEPTEMBER/OCTOBER 2010

Cloning

rsync -a bugs-mirror.debian.org::bts-spool-archive bts-spool-archive
rsync -a bugs-mirror.debian.org::bts-spool-db bts-spool-db

Sampling

  • Read all .report files, filter the ones with only one bug on the BTS
  • Sample 50% fixed, 50% not-fixed

Criteria

  • Expected behavior vs. observed behavior
  • Reproducible?
    • Test case?
    • How long it'll take to reproduce it?
  • Stack trace?
  • Screenshot?
  • Error message?
    • Localized error
  • Severity
    • Could be done automatically using downgrading?
  • Rudeness?
  • Missing config files
    • Follow up emails saying "can you send me...?"

Interesting Bugs

Implementation

  • From CueZilla
    • Detect itemizations
    • Keyword completeness
      • action items (e.g., open, select, click)
      • expected and observed behavior (e.g., error, missing)
      • steps to reproduce (e.g., steps, repro)
      • build-related (e.g., build)
      • user interface elements (e.g., toolbar, menu, dialog)
    • Attachements
      • Code samples (likely not that important in Debian context)
      • Stack traces
      • Patches
      • Screenshots (using file)
    • Readability (using style)