Foreword

Our relationship with upstream statement defines our relationship with Debian.

Tasks

• Work on the Debian bugs that affect Tails.
• Work on our tickets about Debian work.
• Help maintain backports for Wheezy:
  • i18nspector
  • liferea
  • monkeysign
  • pidgin
  • poedit
  • redmine
  • ruby-libvirt
  • ruby-passenger
  • ruby-rjb
  • seahorse-nautilus
  • Xorg stack (at least the foundations and the major drivers)
• Help maintain packages:
  • libgsecuredelete
  • mat
  • nautilus-wipe
  • OTR-related packages (pidgin-otr, libotr, and more) in the Debian OTR Team
  • torsocks
  • vidalia
• Help with distribution-wide improvements:
  • AppArmor support
  • Hardening
  • Reproducible builds
• Set up automated QA of Debian Live development branches, and/or change the workflow of this project so that one can backport improvements into the stable branches.

Want more?

You might want to subscribe to the tails-dev mailing list.

Talk to us

If you want to talk in public with other Tails developers and users:

• you can subscribe or write to the tails-dev@boum.org mailing-list; any message sent to this list is stored in a public archive, so beware of what your email content and headers reveal about yourself: location, IP address, etc.;
• you can join our #tails and #tails-dev chatrooms; note: only a few Tails core developers hang out there, so email is preferred for anything that might be of interest for the larger Tails development community;
• for translation-related matters, you can subscribe or write to the tails-l10n@boum.org mailing-list; any message sent to this list is stored in a public archive, so beware of what your email content and headers reveal about yourself: location, IP address, etc.

For matters that need to be hidden from the public eyes, email the private development mailing list: tails@boum.org; to achieve end-to-end encryption, encrypt such email with our OpenPGP key.