History: Anonymity Tools Packaging Team & OTR Team
This team was previously the Anonymity Tools Packaging Team and the OTR Team.
There are still some packages using those as a maintainer addresses but we are slowly migrating all of them to the Privacy Maintainers Team.
All technical information is valid for all three teams.
Anonymity Tools packaging team
OTR packaging team
Email contact: firstname.lastname@example.org
Public IRC channel: #otr on irc.oftc.net (general OTR discussion channel)
We are now: Debian Privacy Tools Maintainers
This packaging team takes care of privacy and anonymity related packages.
Interacting with the team
Email contact: email@example.com
We invite all maintainers of privacy & anonymity related packages to join the team!
Joining the team is not done by joining the alioth project (technically you can do this, but it's rather pointless), but rather by putting the pkg-privacy-maintainers mailing list (firstname.lastname@example.org) into the "Maintainer:" field of your package (and yourself and other people into the "Uploaders:" field) and subscribing to our mailing list.
There is also a mailing list which receives commits related to these packages: email@example.com // http://lists.alioth.debian.org/pipermail/pkg-privacy-commits
Help squash bugs
Triaging bugs is welcome!
We like to fix bugs in anonymity software. If it's not Debian specific, we'll forward it to upstream. An example of a bug email can be found below.
To: firstname.lastname@example.org From: email@example.com Subject: Cannot launch the Tor Browser Package: torbrowser-launcher Version: 0.1.0-1.2 Severity: serious There is some sort of error with twisted preventing the version check information from being downloaded, which in turn prevents the Tor Browser from starting at all. Here is my output: <output> I am using Debian GNU/Linux 7, Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores).
Tools and processes
We are maintaining the packaging in Git, using gbp.
- Whenever possible, use the upstream signed Git tag as the canonical upstream release, and generate the tarball ourselves.
- We are using source format 3.0 (quilt).
Git branch layout shoudl follow gbp's recommendations and defaults if possible, see file:///usr/share/doc/git-buildpackage/manual-html/gbp.intro.html#GBP.REPOSITORY
- We don't apply patches to the upstream source that have not been submitted upstream yet.