Tails documentation would greatly benefit from your help.

Good documentation is difficult to keep up-to-date. If you find a typo or an error in the documentation please let us know — ideally, by submitting a patch with your correction.

Writing

The documentation on the website is not freely editable. The way we document things has serious security implications. People should be able to trust the Tails website as much as they trust Tails itself. Furthermore, every change in the documentation possibly breaks the translations that were made of the previous version.

But there are still many ways you can start contributing:

  • We maintain a list of documentation tasks. You can start writing a draft in the corresponding ticket and then ask us for review.

  • Small fixes and enhancements to the current documentation are greatly welcome. This can be done by sending Git patches to the tails-dev mailing list or by publishing a Git branch (for example to a fork on GitLab). In general, documentation changes should be based on the master branch.

Documentation writers coordinate themselves using our usual development communication channels.

Documentation writers should also read our documentation guidelines.

New documentation should be wrapped to 80 characters; however, please do not submit patches that merely re-wrap existing text, as this makes it harder to read the git history.

We recommend you to build an offline version of the documentation to test your contributions before sharing them with us.

Tools

  • Images on our website are compressed and cleaned using the compress-image.sh script. To run this script you need the optipng, advancecomp, and mat packages.

  • To encode and decode QR codes, you can use the qrcode-encode.sh and qrcode-decode.sh scripts. To run these scripts you need to install the qrencode and zbar-tools packages.

    For example:

    qrcode-encode https://tails.boum.org/
    

    Creates a QR code in tails_boum_org.png. And:

    qrcode-decode tails_boum_org.png
    

    Outputs:

    QR-Code:https://tails.boum.org/
    

Translating

We want Tails end-user documentation to be translated in as many languages as possible. See the guidelines for translators for details.

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 user support IRC chatroom, or the tails-dev XMPP one (server: conference.riseup.net) that is meant for discussion among contributors; 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 user experience and user interface related matters, you can subscribe or write to the tails-ux@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.