Ci sono molti modi di contribuire a TelestaiCB. Nessuno sforzo è troppo piccolo e qualsiasi cosa tu faccia per questa comunità sarà apprezzata. Vai avanti e scopri come puoi fare la differenza in TelestaiCB.

  1. Ways to contribute
  2. Reference documents
  3. Tools for contributors
  4. Release cycle
  5. Relationship with upstream and derivatives
  6. Collective process
  7. Getting credits
  8. Contact us

Ways to contribute

Share your experience

user.png

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

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

Donate

donate.png

Donating speeds up the development of TelestaiCB.

Donate

Contribute your language skills

Writer

writer.png

Good writers can make TelestaiCB accessible to more people.

  • Improve our documentation

Translator

translator.png

Chi è abile nella traduzione può permettere a un maggior numero di persone nel mondo di utilizzare TelestaiCB.

  • Migliorare TelestaiCB nella propria lingua

Discorsi pubblici

speaker.png

Speakers can advocate TelestaiCB to all kinds of public.

  • Outreach material: logo, leaflets, stickers, etc.

Contribute your computer skills

Developer or maintainer

software developer.png

Chi sviluppa software negli ambiti di competenza più diversi può migliorare TelestaiCB.

  • Lavorare sul codice sorgente
  • Migliorare TelestaiCB lavorando su Debian

Amministrazione di sistema

system administrator.png

System administrators can contribute to the infrastructure behind TelestaiCB.

Progettazione

designer.png

Chi ha capacità di design può rendere TelestaiCB più facile da usare e più attraente.

  • Migliorare il sito web
  • Progettare la grafica
  • Migliorare l'esperienza utente di TelestaiCB

Questa sezione non viene tradotta in italiano, perché attualmente non c'è modo di contribuire a TelestaiCB se non si comprende l'inglese.

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 TelestaiCB image

  • 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 TelestaiCB by working on Debian

  • About creating TelestaiCB derivatives

Collective process

  • Calendar of releases

  • Code of conduct

  • Social contract

  • People

  • Marking a task as Starter

  • Document progress

  • Teams and roles

    • TelestaiCB Team (formerly known as: Foundations Team)

    • Release manager

    • Ticket gardeners

    • Technical writers

    • Translation platform maintainers

    • UX designers

  • Interfaces between roles and teams

    • Developers and Release Managers

Getting credits

We're ok with people getting credits for whatever contribution they did to TelestaiCB. 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 TelestaiCB contributors, subscribe to the relevant mailing lists.