[[!meta title="Improve the infrastructure behind Tails"]]
<p>So you want to help improve the infrastructure behind Tails.<br />
Welcome aboard! Please read-on.</p>
# Read this first
First of all, please read the [[goals and
principles|contribute/working_together/roles/sysadmins#goals]] of the
Tails system administration team.
# Skills needed
Essential skills for participating in the Tails infrastructure include
basic Unix system administration knowledge and good
Depending on the task, you may also need to be knowledgeable in either
Debian system administration, scripting in Perl, Python, Ruby or shell,
or one of the [[services we
<li>To complete most tasks, some amount of Puppet work must be done.
However, it is possible to participate without knowing Puppet, at
least for your first contributions.</li>
<li>Being an expert beforehand is not required, as long as you are
ready to learn whatever you need to know :)</li>
# How to choose a task
We use Redmine to manage our list of tasks:
* [tasks that require *Sysadmin*
* [tasks that belong to the *Infrastructure*
Here are a few tips to pick a task:
* Focus on the issues marked as *[[Starter|starter_tasks]]* on Redmine.
* Choose something that matters for you.
* Choose something where your singular skills are put to work.
Do not hesitate to request our advice: tell us about your skills, and
we will try to match it to a task.
If anything is unclear, ask us to specify the desired outcome in more
details *before* you start working: this will save time to
# How to implement and propose changes
Thanks to the [[tools we
use|contribute/working_together/roles/sysadmins#tools]], you can
contribute usefully without having an account on the actual systems.
## If you don't know Puppet
A few tasks in Redmine can be fulfilled by testing something, and then
reporting your results on the relevant ticket.
However, most tasks are a bit more complicated. Follow these steps to
contribute useful bits, that someone else can then integrate into
1. Prepare configuration, scripts and whatever is needed. During this
* Write down every setup step needed to deploy the whole thing.
* In particular, take note of any dependency you install.
Better work in a minimal Debian stable system to avoid missing
some (hint: virtual machine, pbuilder chroot or alike).
* Document how the whole thing is supposed to be used.
1. Test, hack, test, [...]
1. Publish your work somewhere, preferably in a Git repository to
smooth any further iteration our first review pass may require.
If you already know where to host your personal repositories, this
is great; or else you may ask us to host your repository.
1. Tell us what problem you tried to solve, and where we can find
## If you know Puppet, or want to learn it
To solve a problem with Puppet, you need to:
* Either, improve a Puppet module. If we are not the original authors
of this module, please contribute your changes upstream: we don't
want to maintain forks forever.
* Or, create a new Puppet module. But first, try to find an existing
module that can be adapted to our needs.
Many Puppet modules can be found in the [shared Puppet
the [Puppet Forge](https://forge.puppetlabs.com/), and on GitHub.
To smooth the reviewing and merging process: create atomic commits,
document your changes in details, follow the Puppet [style
carefully test your changes.
Once ready, you can submit trivial changes over email, in the form of
Git patches prepared with `git-format-patch(1)`.
For anything more substantial, please publish your work as a Git topic
branch. If you already know where to host your personal repositories,
this is great; or else you may ask us to host your repository.
# Contact information
Email us at [[firstname.lastname@example.org|about/contact#tails-sysadmins]]. We prefer receiving email
encrypted with [[our OpenPGP key|doc/about/openpgp_keys#sysadmins]],
that is certified by the Tails signing key.