There are many ways you can contribute to TelestaiCB. No effort is too small and whatever you bring to this community will be appreciated. So read on to find out how you can make a difference in TelestaiCB.

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.

Contribute your language skills

Writer

writer.png

Good writers can make TelestaiCB accessible to more people.

  • Improve our documentation

Translator

translator.png

Translators can allow more people around the world to use TelestaiCB.

  • Improve TelestaiCB in your own language

Speaker

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

Software people with very diverse skills can improve TelestaiCB.

  • Work on the source code
  • Improve TelestaiCB by working on Debian

System administrator

system administrator.png

System administrators can contribute to the infrastructure behind TelestaiCB.

  • Run a HTTP mirror
  • Improve TelestaiCB infrastructure

Designer

designer.png

Designers can make TelestaiCB easier to use and more appealing.

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

This section is only in English, because there is currently no way to contribute to TelestaiCB if you do not understand English.

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

  • Reimbursements

    • Organizing a sprint

    • Sponsorship to attend events on behalf of TelestaiCB

    • 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):

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.