ref: 6ba85d233013a33eba2f931ba96e9482d17d9a38 sr.ht-docs/support.md -rw-r--r-- 2.5 KiB View raw
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
---
title: Getting support
---

# Asking the community

A great place to ask for general questions with using sr.ht, starting
discussions about your ideas and feature requests, and generally getting to know
the sr.ht community is the
[sr.ht-discuss](https://lists.sr.ht/~sircmpwn/sr.ht-discuss) mailing list. You
can post here by writing an email to
[~sircmpwn/sr.ht-discuss@lists.sr.ht](mailto:~sircmpwn/sr.ht-discuss@lists.sr.ht).
Please review the [mailing list etiquette guide](lists.sr.ht/etiquette.md)
first! Be sure to search through the archives, as your question may have been
asked before.

# Asking the admins

You can reach Drew DeVault, the maintainer of sr.ht and your friendly
neighborhood sysadmin, by sending an email to
[sir@cmpwn.com](mailto:sir@cmpwn.com). Feel free to email him for any reason,
but this is your best bet with account-related problems, billing issues, and
similar woes.

# Real time chat

Both community members and admins hang out at [#sr.ht on
irc.freenode.net][webchat], where you're welcome to ask questions and have
discussions in a more free-form, real-time context. There's not always someone
paying attention here, so be prepared to wait or follow-up with an email if
necessary.

[webchat]: http://webchat.freenode.net/?channels=%23sr.ht&uio=d4

# Paid support

Normally, support is provided at the best effort of the sysadmins, which may be
impacted by time and resource constraints. However, paid support options are
available for organizations and businesses hoping to get to the front of the
queue. For details, [send me an email](mailto:sir@cmpwn.com).

# Submitting bug reports

Each service of sr.ht has a dedicated bug tracker:

- [git.sr.ht](https://todo.sr.ht/~sircmpwn/git.sr.ht)
- [builds.sr.ht](https://todo.sr.ht/~sircmpwn/builds.sr.ht)
- [todo.sr.ht](https://todo.sr.ht/~sircmpwn/todo.sr.ht)
- [lists.sr.ht](https://todo.sr.ht/~sircmpwn/lists.sr.ht)
- [man.sr.ht](https://todo.sr.ht/~sircmpwn/man.sr.ht)
- [dispatch.sr.ht](https://todo.sr.ht/~sircmpwn/dispatch.sr.ht)
- [meta.sr.ht](https://todo.sr.ht/~sircmpwn/meta.sr.ht)

There is also a [general-purpose bug
tracker](https://todo.sr.ht/~sircmpwn/sr.ht) for issues that fit nowhere else,
or that you're unsure of the appropriate place to report your bug:


# Security vulnerabilities

Please send an email to [sir@cmpwn.com](mailto:sir@cmpwn.com), optionally using
the public key [7BC79407090047CA](https://drewdevault.com/publickey.txt). Please
do not discuss security vulnerabilities in public until a fix has been developed
and deployed.