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.
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:
Documentation writers coordinate themselves using our usual development communication channels.
Documentation writers should also read our documentation guidelines.
If you want to test your contributions before to sharing them with us, you can build and update the documentation offline.
If you want to talk in public with other Tails developers and users:
- you can subscribe or write to the firstname.lastname@example.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 email@example.com 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.