Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • tpa-rfc-80-merge-tor-and-tails-support-policies
  • puppet-merge-costs
  • rfc-77-improv
  • tails-merge-admin-mailing-lists
  • mkdocs
  • new-blog-doc
7 results
Blame Permalink
  • anarcat's avatar
    ce53bb7b
    create a new "support" page · ce53bb7b
    anarcat authored 
    The support page is the go-to page for the "how to get help" question,
which previously was hidden inside the TPA-RFC-2 standard.

This basically copies that part of the TPA-RFC-2 policy, but could
eventually diverge without needing to update the policy, for informal
stuff.

I started working on this page while trying to address
team#40382 ("document the triage process"), but I'm not
actually sure triage documentation should go there, as this page feels
more targeted at users, and only users.

howto/incident-response.md would seem like a better space for this.

Also, this is a toplevel page because it's more important than
everything else, so it warrants its own special space.
    Verified
    ce53bb7b
    History
    create a new "support" page
    anarcat authored 
    The support page is the go-to page for the "how to get help" question,
which previously was hidden inside the TPA-RFC-2 standard.

This basically copies that part of the TPA-RFC-2 policy, but could
eventually diverge without needing to update the policy, for informal
stuff.

I started working on this page while trying to address
team#40382 ("document the triage process"), but I'm not
actually sure triage documentation should go there, as this page feels
more targeted at users, and only users.

howto/incident-response.md would seem like a better space for this.

Also, this is a toplevel page because it's more important than
everything else, so it warrants its own special space.
support.md 1.70 KiB

Need help?

If you need help from the sysadmin team (or even if you're not sure which team!), please do contact us using one of the following mechanisms:

Quick question: chat

If you have "just a quick question" or some quick thing we can help you with, ask us on IRC: you can find us in #tpo-admin on irc.oftc.net and in other tor channels.

It's possible we ask you to create a ticket if we're in a pinch. It's also a good way to bring your attention to some emergency or ticket that was filed elsewhere.

Bug reports, feature requests and others: issue tracker

Most requests and questions should go into the issue tracker, which is currently GitLab (direct link to a new ticket form). Try to find a good label describing the service you're having a problem with, but in doubt, just file the issue with as much details as you can.

You can also mark an issue as confidential, in which case only members of the team (and the larger "tpo" organisation on GitLab) will be able to read it.

Private question and fallback: email

If you want to discuss a sensitive matter that requires privacy or are unsure how to reach us, you can always write to us by email, at torproject-admin@torproject.org.

For details on those options and our support policy, including support levels, supported services and timelines, see the TPA-RFC-2: support policy.