你有很多種向Tails做貢獻的途徑。 任何嘗試都不會微不足道，且無論你給社區帶來什麼都會被認可。 所以請繼續讀下去，看看有沒有你給Tails帶來不一樣的地方。

Ways to contribute

Share your experience

Every user can help others or provide developers with useful information.

• Report errors
• Test experimental Tails images
• Provide input to developers
• Help other Tails users

Donate

Donating speeds up the development of Tails.

Donate

Contribute your language skills

Writer

好的寫手能讓 Tails 得到更多的人認識。

• 改進文檔

翻譯人員

譯者能讓世界上更多的人使用 Tails。

• 用你的母語裝備 Tails

演講者

做演講可以向所有不同類型的公衆宣傳 Tails。

• 在活動中宣講

Contribute your computer skills

Developer or maintainer

具有多種不同技能的軟件專業人士可以改進 Tails。

• 在源代碼上工作
• 通過在 Debian 上工作來改進 Tails

系統管理員

系統管理員可以爲 Tails背後的基礎設施做貢獻。

• 運行一個 HTTP 鏡像
• 改進 Tails 的基礎設施

設計師

Designers can make Tails easier to use and more appealing.

• Improve the website
• Design graphics
• Improve the Tails user experience

Reference documents

• Mission and values

• Design documents

• Blueprints to help structuring ideas for future improvements

• Merge policy

• Logo

• Personas

Tools for contributors

• Source code: Git repositories

• GitLab source code and bug tracker

• Starter tasks for new contributors

• Building a Tails image

  • Build a local copy of the website

  • Customize Tails

  • Nightly Tails image builds

  • Jenkins CI

• Debian packages

  • APT repository, to store our custom Debian packages

  • How we manage and upgrade the Linux kernel.

  • How we manage and upgrade tor.

• Tips to develop and debug Tor Connection

• Tips to develop Persistent Storage

• Glossary for contributors

Release cycle

• Release schedule

• Release process

  • Manual test suite

  • Automated test suite

  • Verification JavaScript

Relationship with upstream and derivatives

• Relationship with upstream

• Improve Tails by working on Debian

• About creating Tails derivatives

Collective process

• Calendar of releases

• Code of conduct

• Social contract

• People

• Marking a task as Starter

• Document progress

• Reimbursements

  • Organizing a sprint

  • Sponsorship to attend events on behalf of Tails

  • Hardware and other reimbursements

• Teams

  • Accounting team

  • Community Health team

  • Foundations team

  • Fundraising team

  • Help desk

  • Management team

  • Release managers

  • Ticket gardeners

  • Sysadmins

  • Technical writers

  • Test suite maintainers

  • Translation platform maintainers

  • UX designers

• Interfaces between roles and teams

  • Developers and Release Managers

• Roles for sponsor deliverables (internal documentation):

  • tails/summit/-/wikis/Handbook/Grant contract management

Getting credits

We're ok with people getting credits for whatever contribution they did to Tails. Sometimes this is publicly available (for example: in issues, git history, etc.), in which case this is enough for us.

In some cases such info might not be publicly visible (for example: facilitation work done for meetings or data that was deleted for some reason). In this case, if the contributor so wish, we're ok with adding explicit public credit somewhere they can link to. If that's your case, please contact us.

Contact us

To talk to other Tails contributors, subscribe to the relevant mailing lists.