mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
Update "Help, Support, Mailing Lists, and Forum"
- Revamp intro to make it (hopefully) more user-friendly - Generalize last section into "Unofficial venues" - Warn that we do not monitor or moderate unofficial venues - Warn more explicitly about possible Qubes team impostors - Miscellaneous updates and improvements
This commit is contained in:
parent
0c3c2aa82d
commit
0701f196c8
@ -15,66 +15,134 @@ ref: 122
|
|||||||
title: Help, Support, Mailing Lists, and Forum
|
title: Help, Support, Mailing Lists, and Forum
|
||||||
---
|
---
|
||||||
|
|
||||||
Help and support for Qubes OS is available from the [documentation](/doc/), the
|
The Qubes community is here to help! Since Qubes is a security-oriented
|
||||||
[mailing lists](#mailing-lists), and our [forum](#forum) which are explained below. The Qubes OS
|
operating system, we want to make sure you [stay safe](#staying-safe) as you
|
||||||
Project does not offer paid support services.
|
get the support you need, and we want to make sure our community remains a
|
||||||
|
friendly place by ensuring we all follow the [Code of
|
||||||
|
Conduct](/code-of-conduct/).
|
||||||
|
|
||||||
Before asking for help, please check the [troubleshooting](/doc/#troubleshooting) section, the [FAQ](/faq/), and the rest of the [documentation](/doc/).
|
## How to get help and support
|
||||||
Your question may already be answered there.
|
|
||||||
|
|
||||||
If you're looking for known issues or would like to file a bug report, please
|
First, let's see what kind of help you need.
|
||||||
see the [issue tracker](/doc/issue-tracking/). These issues are constantly being updated and may
|
|
||||||
contain workarounds for problems that you're experiencing, so it's worth
|
### I would like to report a security vulnerability
|
||||||
[searching the issue tracker](/doc/issue-tracking/#search-tips) as a first step. However, please note that
|
|
||||||
[the issue tracker is not a discussion forum](/doc/issue-tracking/#the-issue-tracker-is-not-a-discussion-forum).
|
That sounds more like you helping us! Thanks! Please see [Reporting Security
|
||||||
|
Issues in Qubes OS](/security/#reporting-security-issues-in-qubes-os).
|
||||||
|
|
||||||
|
### I have a problem or a question
|
||||||
|
|
||||||
|
No worries! Here's how we recommend proceeding:
|
||||||
|
|
||||||
|
1. Check the [documentation](/doc/). There may already be a page about it.
|
||||||
|
Specifically, check out the [How-to Guides](/doc/#how-to-guides) and
|
||||||
|
[Troubleshooting](/doc/#troubleshooting) sections.
|
||||||
|
|
||||||
|
2. Search the [FAQ](/faq/). Your question might already be answered.
|
||||||
|
|
||||||
|
3. Try [searching the issue tracker](/doc/issue-tracking/#search-tips). There
|
||||||
|
may already be an open **or closed** issue about your problem. The issue
|
||||||
|
tracker is constantly being updated with known bugs and may contain
|
||||||
|
workarounds for problems you're experiencing. If there any pinned issues at
|
||||||
|
the top, make sure to check them first!
|
||||||
|
|
||||||
|
4. Try [searching the Qubes Forum](https://qubes-os.discourse.group/). There
|
||||||
|
may already be a matching topic.
|
||||||
|
|
||||||
|
5. Try [searching the `qubes-users`
|
||||||
|
archives](https://www.mail-archive.com/qubes-users@googlegroups.com/). There
|
||||||
|
may have already been a relevant thread.
|
||||||
|
|
||||||
|
### I didn't find a solution or an answer!
|
||||||
|
|
||||||
|
Sorry to hear that! In that case, we recommend asking for help on the [Qubes
|
||||||
|
Forum](https://qubes-os.discourse.group/) or on the [`qubes-users` mailing
|
||||||
|
list](#qubes-users). Choose the venue you prefer, but please don't ask on both
|
||||||
|
at the same time! Before you ask, please review our [discussion
|
||||||
|
guidelines](#discusion-guidelines) and StackOverflow's advice on [how to ask
|
||||||
|
good questions](https://stackoverflow.com/help/how-to-ask). Don't forget to
|
||||||
|
[stay safe](#staying-safe)!
|
||||||
|
|
||||||
|
### I don't need support, but I think I found a bug
|
||||||
|
|
||||||
|
We'd be grateful if you reported it (but please make sure no one else has
|
||||||
|
already reported it first)! Please see [Issue Tracking](/doc/issue-tracking/)
|
||||||
|
for details.
|
||||||
|
|
||||||
|
### I don't need support, but I'd like to request a feature
|
||||||
|
|
||||||
|
No promises, but we'd be happy to consider it! Please see [Issue
|
||||||
|
Tracking](/doc/issue-tracking/) for details.
|
||||||
|
|
||||||
|
### I just want to discuss Qubes!
|
||||||
|
|
||||||
|
Great! Head on over to the [Qubes Forum](https://qubes-os.discourse.group/) or
|
||||||
|
on the [`qubes-users` mailing list](#qubes-users).
|
||||||
|
|
||||||
|
### How can I get involved and contribute?
|
||||||
|
|
||||||
|
Thank you for asking! Please see [How to Contribute](/doc/contributing/) for
|
||||||
|
all the ways you can do so.
|
||||||
|
|
||||||
## Staying safe
|
## Staying safe
|
||||||
|
|
||||||
The Qubes mailing lists and forum are open to the public. The contents are
|
The Qubes mailing lists and forum are open to the public. The contents are
|
||||||
crawled by search engines and archived by third-party services outside of our
|
crawled by search engines and archived by third-party services outside of our
|
||||||
control. Please do not send or post anything that you are not comfortable seeing
|
control. Please do not send or post anything that you are not comfortable
|
||||||
discussed in public. If confidentiality is a concern, please use PGP encryption
|
seeing discussed in public. If confidentiality is a concern, please use PGP
|
||||||
in an off-list email.
|
encryption in an off-list email.
|
||||||
|
|
||||||
The Qubes community includes people from all walks of life and from around the
|
The Qubes community includes people from all walks of life and from around the
|
||||||
world. Individuals differ in areas of experience and technical expertise. You
|
world. Individuals differ in areas of experience and technical expertise. You
|
||||||
will come into contact with others whose views and agendas differ from your own.
|
will come into contact with others whose views and agendas differ from your
|
||||||
Everyone is free to write what they please, as long as it doesn't violate our
|
own. Everyone is free to write what they please, as long as it doesn't violate
|
||||||
[Code of Conduct](/code-of-conduct/). Be friendly and open, but do not believe everything you
|
our [Code of Conduct](/code-of-conduct/). Be friendly and open, but do not
|
||||||
read. Use good judgment, and be especially careful when following instructions
|
believe everything you read. Use good judgment, and be especially careful when
|
||||||
(e.g., copying commands) given by others on the lists.
|
following instructions (e.g., copying commands) given by others on the lists.
|
||||||
|
|
||||||
All official announcements from the [Qubes team](/team/) to a mailing list will be
|
It's always possible that a bad actor could try to impersonate any member of
|
||||||
signed by the PGP key belonging to the team member who sends the announcement.
|
the [Qubes team](/team/) anywhere on the Internet. Please don't assume that
|
||||||
However, anyone on a mailing list can choose to sign their messages, so the
|
someone who claims to be an official Qubes team member really is one without an
|
||||||
presence of a PGP signature does not indicate authority. How, then, should you
|
appropriate form of authentication, such as a [verified PGP-signed
|
||||||
sort the good advice from the bad?
|
message](/security/verifying-signatures/). (But bear in mind that anyone can
|
||||||
This is up to each individual to decide, but it helps to know that many members
|
generate a key with any name on it and use it to PGP-sign a message, so the
|
||||||
of our community have proven themselves knowledgeable through their
|
mere presence of a PGP signature does not indicate authority. Successful
|
||||||
[contributions](/doc/contributing/) to the project. Typically, these individuals sign their messages
|
[verification](/security/verifying-signatures/) is what counts.) All official
|
||||||
with the same key as (or another key authenticated by) the one they use to
|
[news](/news/) can be authenticated by [verifying the
|
||||||
[sign their contributions](/doc/code-signing/).
|
signatures](/security/verifying-signatures/) on the relevant tags or commits in
|
||||||
|
the [qubes-posts](https://github.com/QubesOS/qubes-posts) repository.
|
||||||
|
|
||||||
|
Given that there may be impostors and others trying to lead you astray, how
|
||||||
|
should you sort the good advice from the bad? This is up to each individual to
|
||||||
|
decide, but it helps to know that many members of our community have proven
|
||||||
|
themselves knowledgeable through their [contributions](/doc/contributing/) to
|
||||||
|
the project. Often, these individuals sign their messages with the same key as
|
||||||
|
(or another key authenticated by) the one they use to [sign their
|
||||||
|
contributions](/doc/code-signing/).
|
||||||
|
|
||||||
For example, you might find it easier to trust advice from someone who has a
|
For example, you might find it easier to trust advice from someone who has a
|
||||||
proven track record of [contributing software packages](/doc/package-contributions/) or [contributing to the
|
proven track record of [contributing software
|
||||||
documentation](/doc/doc-guidelines/). It's unlikely that individuals who have worked hard to build
|
packages](/doc/package-contributions/) or [contributing to the
|
||||||
good reputations for themselves through their contributions over the years would
|
documentation](/doc/doc-guidelines/). It's unlikely that individuals who have
|
||||||
risk giving malicious advice in signed messages to public mailing lists. Since
|
worked hard to build good reputations for themselves through their
|
||||||
every contribution to the Qubes OS Project is publicly visible and
|
contributions over the years would risk giving malicious advice in signed
|
||||||
cryptographically signed, anyone would be in a position to [verify](/security/verifying-signatures/) that these
|
messages to public mailing lists. Since every contribution to the Qubes OS
|
||||||
came from the same keyholder.
|
Project is publicly visible and cryptographically signed, anyone would be in a
|
||||||
|
position to [verify](/security/verifying-signatures/) that these came from the
|
||||||
|
same keyholder.
|
||||||
|
|
||||||
## Discussion guidelines
|
## Discussion guidelines
|
||||||
|
|
||||||
Qubes discussions mainly take place on `qubes-users`, `qubes-devel`, and our
|
Qubes discussions mainly take place on `qubes-users`, `qubes-devel`, and our
|
||||||
[forum](#forum), all of which are explained below. Most questions should be directed to
|
[forum](#forum), all of which are explained below. Most questions should be
|
||||||
`qubes-users` or the [forum](#forum). **Please do not send questions to individual
|
directed to `qubes-users` or the [forum](#forum). **Please do not send
|
||||||
Qubes developers.** By sending a message to the appropriate mailing list, you
|
questions to individual Qubes developers.** By sending a message to the
|
||||||
are not only giving others a chance to help you, but you may also be helping
|
appropriate mailing list, you are not only giving others a chance to help you,
|
||||||
others by starting a public discussion about a shared problem or interest.
|
but you may also be helping others by starting a public discussion about a
|
||||||
|
shared problem or interest.
|
||||||
|
|
||||||
These are open venues where people freely come together to discuss Qubes
|
These are open venues where people freely come together to discuss Qubes and
|
||||||
and voluntarily help each other out of mutual interest and good will. They are
|
voluntarily help each other out of mutual interest and good will. They are
|
||||||
*not* your personal, paid support service. **No one owes you a reply.** No one
|
*not* your personal, paid support service. **No one owes you a reply.** No one
|
||||||
here is responsible for solving your problems for you. Nonetheless, there are
|
here is responsible for solving your problems for you. Nonetheless, there are
|
||||||
many things you can do to make it more likely that you will receive a reply.
|
many things you can do to make it more likely that you will receive a reply.
|
||||||
@ -85,38 +153,38 @@ guidelines.
|
|||||||
|
|
||||||
### Be polite and respectful
|
### Be polite and respectful
|
||||||
|
|
||||||
Remember, no one here is under any obligation
|
Remember, no one here is under any obligation to reply to you. Think about your
|
||||||
to reply to you. Think about your readers. Most of them are coming home after
|
readers. Most of them are coming home after a long, hard day at work. The last
|
||||||
a long, hard day at work. The last thing they need is someone's temper
|
thing they need is someone's temper tantrum. If you are rude and disrespectful,
|
||||||
tantrum. If you are rude and disrespectful, you are very
|
you are very likely to be ignored.
|
||||||
likely to be ignored.
|
|
||||||
|
|
||||||
### Be concise
|
### Be concise
|
||||||
|
|
||||||
Include only essential information. Most of your readers lead
|
Include only essential information. Most of your readers lead busy lives and
|
||||||
busy lives and have precious little time. We *want* to spend some of that
|
have precious little time. We *want* to spend some of that time helping you, if
|
||||||
time helping you, if we can. But if you ramble, it will be easier to skip
|
we can. But if you ramble, it will be easier to skip over you and help someone
|
||||||
over you and help someone else who gets right to the point.
|
else who gets right to the point.
|
||||||
|
|
||||||
### Help us help you
|
### Help us help you
|
||||||
|
|
||||||
Tell us what you've already tried, and which
|
Tell us what you've already tried, and which documentation pages you've already
|
||||||
documentation pages you've already read. Put yourself in your readers' shoes.
|
read. Put yourself in your readers' shoes. What essential information would
|
||||||
What essential information would they require in order to be able to help
|
they require in order to be able to help you? Make sure to include that
|
||||||
you? Make sure to include that information in your message. A great way to
|
information in your message. A great way to provide your hardware details is by
|
||||||
provide your hardware details is by [generating and submitting a Hardware
|
[generating and submitting a Hardware Compatibility List (HCL)
|
||||||
Compatibility List (HCL) report](/doc/hcl/#generating-and-submitting-new-reports), then linking to it in your
|
report](/doc/hcl/#generating-and-submitting-new-reports), then linking to it in
|
||||||
message. [Ask questions the smart way.](http://www.catb.org/esr/faqs/smart-questions.html)
|
your message. [Ask questions the smart
|
||||||
|
way.](http://www.catb.org/esr/faqs/smart-questions.html)
|
||||||
|
|
||||||
### Be patient
|
### Be patient
|
||||||
|
|
||||||
Do not "bump" a thread more than once every three days *at
|
Do not "bump" a thread more than once every three days *at most*. If it seems
|
||||||
most*. If it seems like your messages to the mailing lists are consistently
|
like your messages to the mailing lists are consistently being ignored, make
|
||||||
being ignored, make sure you're following the guidelines explained on this
|
sure you're following the guidelines explained on this page. If you're already
|
||||||
page. If you're already doing so but still not getting any replies, then it's
|
doing so but still not getting any replies, then it's likely that no one who
|
||||||
likely that no one who knows the answer has had time to reply yet. Remember
|
knows the answer has had time to reply yet. Remember that the devs are very
|
||||||
that the devs are very busy working on Qubes. They usually only have a chance
|
busy working on Qubes. They usually only have a chance to answer questions on
|
||||||
to answer questions on the mailing lists once every several days.
|
the mailing lists once every several days.
|
||||||
|
|
||||||
### Be a good community member
|
### Be a good community member
|
||||||
|
|
||||||
@ -132,17 +200,19 @@ to earn the good will of others. This does not mean that you will not receive
|
|||||||
help. On the contrary, we are fortunate to have such a helpful and
|
help. On the contrary, we are fortunate to have such a helpful and
|
||||||
understanding community that many of them spend hours of their personal time
|
understanding community that many of them spend hours of their personal time
|
||||||
helping complete strangers, including many who post anonymously. (Given the
|
helping complete strangers, including many who post anonymously. (Given the
|
||||||
integration of Qubes with [Whonix](/doc/whonix/), we understand better than most the
|
integration of Qubes with [Whonix](/doc/whonix/), we understand better than
|
||||||
complexities of privacy and anonymity, and we know that many users have no
|
most the complexities of privacy and anonymity, and we know that many users
|
||||||
other choice but to post anonymously.) You can read our project's [Code of
|
have no other choice but to post anonymously.) You can read our project's [Code
|
||||||
Conduct](/code-of-conduct/) for more information.
|
of Conduct](/code-of-conduct/) for more information.
|
||||||
|
|
||||||
### Report issues and submit changes in the right places
|
### Report issues and submit changes in the right places
|
||||||
|
|
||||||
The mailing lists and [forum](#forum) are good places to ask questions and discuss
|
The mailing lists and [forum](#forum) are good places to ask questions and
|
||||||
things. However, if you're submitting a more formal report, we'd prefer that
|
discuss things. However, if you're submitting a more formal report, we'd prefer
|
||||||
you submit it to our [issue tracker](/doc/issue-tracking/) so that it doesn't get overlooked.
|
that you submit it to our [issue tracker](/doc/issue-tracking/) so that it
|
||||||
(However, please remember that [the issue tracker is not a discussion forum](/doc/issue-tracking/#the-issue-tracker-is-not-a-discussion-forum).)
|
doesn't get overlooked. (However, please remember that [the issue tracker is
|
||||||
|
not a discussion
|
||||||
|
forum](/doc/issue-tracking/#the-issue-tracker-is-not-a-discussion-forum).)
|
||||||
Likewise, if you see that something in the documentation should be changed,
|
Likewise, if you see that something in the documentation should be changed,
|
||||||
don't simply point it out in a discussion venue. Instead, [submit the
|
don't simply point it out in a discussion venue. Instead, [submit the
|
||||||
change](/doc/doc-guidelines/).
|
change](/doc/doc-guidelines/).
|
||||||
@ -150,9 +220,11 @@ change](/doc/doc-guidelines/).
|
|||||||
### Moderation
|
### Moderation
|
||||||
|
|
||||||
The moderation team aims to enforce our [Code of Conduct](/code-of-conduct/).
|
The moderation team aims to enforce our [Code of Conduct](/code-of-conduct/).
|
||||||
Beyond this, users should not expect any specific action from the moderation team.
|
Beyond this, users should not expect any specific action from the moderation
|
||||||
Specifically, users should not request that posts or messages be deleted or edited by a moderator.
|
team. Specifically, users should not request that posts or messages be deleted
|
||||||
Users are reminded that, in most venues, anything posted will be sent out as an email to other others, and these emails cannot be deleted from others' inboxes.
|
or edited by a moderator. Users are reminded that, in most venues, anything
|
||||||
|
posted will be sent out as an email to other others, and these emails cannot be
|
||||||
|
deleted from others' inboxes.
|
||||||
|
|
||||||
### Specific mailing list rules and notes
|
### Specific mailing list rules and notes
|
||||||
|
|
||||||
@ -163,11 +235,14 @@ which list is correct for your message.
|
|||||||
|
|
||||||
#### Do not top-post
|
#### Do not top-post
|
||||||
|
|
||||||
[Top-posting](https://en.wikipedia.org/wiki/Posting_style#Top-posting) is placing your reply above the quoted message to which you're
|
[Top-posting](https://en.wikipedia.org/wiki/Posting_style#Top-posting) is
|
||||||
replying. Please refrain from doing this. Instead, either [interleave](https://en.wikipedia.org/wiki/Posting_style#Interleaved_style) your
|
placing your reply above the quoted message to which you're replying. Please
|
||||||
reply by placing parts of your message immediately below each quoted portion
|
refrain from doing this. Instead, either
|
||||||
to which it is replying, or [bottom-post](https://en.wikipedia.org/wiki/Posting_style#Bottom-posting) by placing your entire reply below
|
[interleave](https://en.wikipedia.org/wiki/Posting_style#Interleaved_style)
|
||||||
the quoted message to which you're replying.
|
your reply by placing parts of your message immediately below each quoted
|
||||||
|
portion to which it is replying, or
|
||||||
|
[bottom-post](https://en.wikipedia.org/wiki/Posting_style#Bottom-posting) by
|
||||||
|
placing your entire reply below the quoted message to which you're replying.
|
||||||
|
|
||||||
#### Use proper subject lines
|
#### Use proper subject lines
|
||||||
|
|
||||||
@ -178,73 +253,79 @@ in installer.")
|
|||||||
|
|
||||||
#### Do not send duplicates
|
#### Do not send duplicates
|
||||||
|
|
||||||
If your message is not successfully sent to the list, it probably got caught
|
If your message is not successfully sent to the list, it probably got caught in
|
||||||
in the spam filter. We check the spam filter regularly, so please be patient,
|
the spam filter. We check the spam filter regularly, so please be patient, and
|
||||||
and your message should be approved (and your email address added to the
|
your message should be approved (and your email address added to the whitelist)
|
||||||
whitelist) within a few days.
|
within a few days.
|
||||||
|
|
||||||
#### Keep the list CCed
|
#### Keep the list CCed
|
||||||
|
|
||||||
Keep the mailing list CCed throughout the conversation unless there's a
|
Keep the mailing list CCed throughout the conversation unless there's a special
|
||||||
special need for privacy (in which case, use PGP encryption). This increases
|
need for privacy (in which case, use PGP encryption). This increases the
|
||||||
the likelihood that a greater quantity of useful information will be
|
likelihood that a greater quantity of useful information will be available to
|
||||||
available to everyone in the future.
|
everyone in the future.
|
||||||
|
|
||||||
#### Quote appropriately
|
#### Quote appropriately
|
||||||
|
|
||||||
If you're replying to a thread (whether your own or
|
If you're replying to a thread (whether your own or someone else's), you should
|
||||||
someone else's), you should make sure to quote enough from previous messages
|
make sure to quote enough from previous messages in the thread so that people
|
||||||
in the thread so that people reading your message can understand the context
|
reading your message can understand the context without having to find and read
|
||||||
without having to find and read earlier messages from that thread. Each reply
|
earlier messages from that thread. Each reply should continue the conversation
|
||||||
should continue the conversation and, ideally, be readable as a conversation
|
and, ideally, be readable as a conversation in itself. Do not quote
|
||||||
in itself. Do not quote advertisements in signatures or inline PGP signature
|
advertisements in signatures or inline PGP signature blocks. (Quoting the
|
||||||
blocks. (Quoting the latter interferes with the ability of programs like
|
latter interferes with the ability of programs like Enigmail to properly quote
|
||||||
Enigmail to properly quote replies thereafter).
|
replies thereafter).
|
||||||
|
|
||||||
#### English not required
|
#### English not required
|
||||||
|
|
||||||
If you do not speak English, you should feel free to post in your own
|
If you do not speak English, you should feel free to post in your own language.
|
||||||
language. However, bear in mind that most members of the list can only read
|
However, bear in mind that most members of the list can only read English. You
|
||||||
English. You may wish to include an automated translation in your message out
|
may wish to include an automated translation in your message out of
|
||||||
of consideration for those readers. If you choose to write in English, please
|
consideration for those readers. If you choose to write in English, please do
|
||||||
do not apologize for doing so poorly, as it is unnecessary. We understand and
|
not apologize for doing so poorly, as it is unnecessary. We understand and will
|
||||||
will ask for clarification if needed.
|
ask for clarification if needed.
|
||||||
|
|
||||||
#### Suggestions
|
#### Suggestions
|
||||||
|
|
||||||
While we're generally open to hearing suggestions for new features, please
|
While we're generally open to hearing suggestions for new features, please note
|
||||||
note that we already have a pretty well defined [roadmap](https://github.com/QubesOS/qubes-issues/milestones), and it's rather
|
that we already have a pretty well defined
|
||||||
unlikely that we will change our schedule in order to accommodate your
|
[roadmap](https://github.com/QubesOS/qubes-issues/milestones), and it's rather
|
||||||
request. If there's a particular feature you'd like to see in Qubes, a much
|
unlikely that we will change our schedule in order to accommodate your request.
|
||||||
more effective way to make it happen is to contribute a patch that implements
|
If there's a particular feature you'd like to see in Qubes, a much more
|
||||||
it. We happily accept such contributions, provided they meet our standards.
|
effective way to make it happen is to contribute a patch that implements it. We
|
||||||
Please note, however, that it's always a good idea to field a discussion of
|
happily accept such contributions, provided they meet our standards. Please
|
||||||
your idea on the `qubes-devel` list before putting in a lot of hard work on
|
note, however, that it's always a good idea to field a discussion of your idea
|
||||||
something that we may not be able or willing to accept.
|
on the `qubes-devel` list before putting in a lot of hard work on something
|
||||||
|
that we may not be able or willing to accept.
|
||||||
|
|
||||||
#### Google Groups
|
#### Google Groups
|
||||||
|
|
||||||
While the mailing lists are implemented as Google Group web forums, a Google
|
While the mailing lists are implemented as Google Group web forums, a Google
|
||||||
account is in no way required, expected, or encouraged. Many discussants
|
account is in no way required, expected, or encouraged. Many discussants
|
||||||
(including most members of the Qubes team) treat these lists as conventional
|
(including most members of the Qubes team) treat these lists as conventional
|
||||||
[mailing lists](https://en.wikipedia.org/wiki/Electronic_mailing_list), interacting with them solely through plain text email
|
[mailing lists](https://en.wikipedia.org/wiki/Electronic_mailing_list),
|
||||||
with [MUAs](https://en.wikipedia.org/wiki/Email_client) like [Thunderbird](https://www.thunderbird.net/) and [Mutt](http://www.mutt.org/). The Google Groups service is just
|
interacting with them solely through plain text email with
|
||||||
free infrastructure, and we [distrust the infrastructure](/faq/#what-does-it-mean-to-distrust-the-infrastructure). This is why, for
|
[MUAs](https://en.wikipedia.org/wiki/Email_client) like
|
||||||
example, we encourage discussants to use [Split GPG](/doc/split-gpg/) to sign all of their
|
[Thunderbird](https://www.thunderbird.net/) and [Mutt](http://www.mutt.org/).
|
||||||
messages to the lists, but we do not endorse the use of these Google Groups
|
The Google Groups service is just free infrastructure, and we [distrust the
|
||||||
as web forums. For that, we have a separate, dedicated [forum](#forum).
|
infrastructure](/faq/#what-does-it-mean-to-distrust-the-infrastructure). This
|
||||||
|
is why, for example, we encourage discussants to use [Split
|
||||||
|
GPG](/doc/split-gpg/) to sign all of their messages to the lists, but we do not
|
||||||
|
endorse the use of these Google Groups as web forums. For that, we have a
|
||||||
|
separate, dedicated [forum](#forum).
|
||||||
|
|
||||||
## Mailing lists
|
## Mailing lists
|
||||||
|
|
||||||
This section covers each of our individual [mailing lists](https://en.wikipedia.org/wiki/Electronic_mailing_list), with
|
This section covers each of our individual [mailing
|
||||||
details about the purpose of each list and how to use it.
|
lists](https://en.wikipedia.org/wiki/Electronic_mailing_list), with details
|
||||||
|
about the purpose of each list and how to use it.
|
||||||
|
|
||||||
### qubes-announce
|
### qubes-announce
|
||||||
|
|
||||||
This is a read-only list for those who wish to receive only very important,
|
This is a read-only list for those who wish to receive only very important,
|
||||||
infrequent messages. Only the core Qubes team can post to this list. Only
|
infrequent messages. Only the core Qubes team can post to this list. Only
|
||||||
[Qubes Security Bulletins (QSBs)](/security/bulletins/), new stable releases, and end-of-life
|
[Qubes Security Bulletins (QSBs)](/security/bulletins/), new stable releases,
|
||||||
notices are announced here.
|
and end-of-life notices are announced here.
|
||||||
|
|
||||||
To subscribe, send a blank email to
|
To subscribe, send a blank email to
|
||||||
`qubes-announce+subscribe@googlegroups.com`. (Note: A Google account is *not*
|
`qubes-announce+subscribe@googlegroups.com`. (Note: A Google account is *not*
|
||||||
@ -267,7 +348,8 @@ lists before sending a question. In addition, please make sure that you have
|
|||||||
read and understood the following basic documentation prior to posting to the
|
read and understood the following basic documentation prior to posting to the
|
||||||
list:
|
list:
|
||||||
|
|
||||||
* The [Installation Guide](/doc/installation-guide/), [System Requirements](/doc/system-requirements/), and [HCL](/doc/hcl/) (for problems
|
* The [Installation Guide](/doc/installation-guide/), [System
|
||||||
|
Requirements](/doc/system-requirements/), and [HCL](/doc/hcl/) (for problems
|
||||||
related to installing Qubes OS)
|
related to installing Qubes OS)
|
||||||
* The [User FAQ](/faq/#users)
|
* The [User FAQ](/faq/#users)
|
||||||
* The [documentation](/doc/) (for questions about how to use Qubes OS)
|
* The [documentation](/doc/) (for questions about how to use Qubes OS)
|
||||||
@ -280,14 +362,16 @@ email to `qubes-users+subscribe@googlegroups.com`. (Note: A Google account is
|
|||||||
address your email to `qubes-users@googlegroups.com`. If your post does not
|
address your email to `qubes-users@googlegroups.com`. If your post does not
|
||||||
appear immediately, please allow time for moderation to occur. To unsubscribe,
|
appear immediately, please allow time for moderation to occur. To unsubscribe,
|
||||||
send a blank email to `qubes-users+unsubscribe@googlegroups.com`. This list
|
send a blank email to `qubes-users+unsubscribe@googlegroups.com`. This list
|
||||||
also has an optional [Google Groups web interface](https://groups.google.com/group/qubes-users) and
|
also has an optional [Google Groups web
|
||||||
[traditional mail archive](https://www.mail-archive.com/qubes-users@googlegroups.com/).
|
interface](https://groups.google.com/group/qubes-users) and [traditional mail
|
||||||
|
archive](https://www.mail-archive.com/qubes-users@googlegroups.com/).
|
||||||
|
|
||||||
### qubes-devel
|
### qubes-devel
|
||||||
|
|
||||||
This list is primarily intended for people who are interested in contributing to
|
This list is primarily intended for people who are interested in contributing
|
||||||
Qubes or who are willing to learn more about its architecture and
|
to Qubes or who are willing to learn more about its architecture and
|
||||||
implementation. Examples of topics and questions suitable for this list include:
|
implementation. Examples of topics and questions suitable for this list
|
||||||
|
include:
|
||||||
|
|
||||||
* Questions about why we made certain architecture or implementation decisions.
|
* Questions about why we made certain architecture or implementation decisions.
|
||||||
* For example: "Why did you implement XYZ this way and not the other way?"
|
* For example: "Why did you implement XYZ this way and not the other way?"
|
||||||
@ -303,20 +387,24 @@ account is *not* required. Any email address will work.) To post a message to
|
|||||||
the list, address your email to `qubes-devel@googlegroups.com`. If your post
|
the list, address your email to `qubes-devel@googlegroups.com`. If your post
|
||||||
does not appear immediately, please allow time for moderation to occur. To
|
does not appear immediately, please allow time for moderation to occur. To
|
||||||
unsubscribe, send a blank email to `qubes-devel+unsubscribe@googlegroups.com`.
|
unsubscribe, send a blank email to `qubes-devel+unsubscribe@googlegroups.com`.
|
||||||
This list also has an optional [Google Groups web interface](https://groups.google.com/group/qubes-devel)
|
This list also has an optional [Google Groups web
|
||||||
and [traditional mail archive](https://www.mail-archive.com/qubes-devel@googlegroups.com/).
|
interface](https://groups.google.com/group/qubes-devel) and [traditional mail
|
||||||
|
archive](https://www.mail-archive.com/qubes-devel@googlegroups.com/).
|
||||||
|
|
||||||
### qubes-project
|
### qubes-project
|
||||||
|
|
||||||
This list is for non-technical discussion and coordination around the
|
This list is for non-technical discussion and coordination around the Qubes OS
|
||||||
Qubes OS project.
|
project.
|
||||||
|
|
||||||
Examples of topics or question suitable for this list include:
|
Examples of topics or question suitable for this list include:
|
||||||
|
|
||||||
* Participation (talks, workshops, etc.) at upcoming events
|
* Participation (talks, workshops, etc.) at upcoming events
|
||||||
* Project funding applications and strategies
|
* Project funding applications and strategies
|
||||||
* FOSS governance discussions
|
* FOSS governance discussions
|
||||||
* Most Github issues tagged "[business](https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Abusiness)"
|
* Most Github issues tagged
|
||||||
|
[business](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+label%3Abusiness)
|
||||||
|
or
|
||||||
|
[project management](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22project+management%22)
|
||||||
|
|
||||||
You don't have to subscribe in order to post to this list. However, subscribing
|
You don't have to subscribe in order to post to this list. However, subscribing
|
||||||
makes your messages less likely to be marked as spam and allows you to receive
|
makes your messages less likely to be marked as spam and allows you to receive
|
||||||
@ -326,18 +414,21 @@ required. Any email address will work.) To post a message to the list, address
|
|||||||
your email to `qubes-project@googlegroups.com`. If your post does not appear
|
your email to `qubes-project@googlegroups.com`. If your post does not appear
|
||||||
immediately, please allow time for moderation to occur. To unsubscribe, send a
|
immediately, please allow time for moderation to occur. To unsubscribe, send a
|
||||||
blank email to `qubes-project+unsubscribe@googlegroups.com`. This list also
|
blank email to `qubes-project+unsubscribe@googlegroups.com`. This list also
|
||||||
also has an optional [Google Groups web interface](https://groups.google.com/group/qubes-project).
|
also has an optional [Google Groups web
|
||||||
|
interface](https://groups.google.com/group/qubes-project).
|
||||||
|
|
||||||
### qubes-translation
|
### qubes-translation
|
||||||
|
|
||||||
This list is for discussion around the localization and translation of Qubes OS,
|
This list is for discussion around the localization and translation of Qubes
|
||||||
its documentation, and the website.
|
OS, its documentation, and the website.
|
||||||
|
|
||||||
Examples of topics or question suitable for this list include:
|
Examples of topics or question suitable for this list include:
|
||||||
|
|
||||||
* Questions about or issues with [Transifex](https://www.transifex.com/), the translation platform we use
|
* Questions about or issues with [Transifex](https://www.transifex.com/), the
|
||||||
|
translation platform we use
|
||||||
* Who is managing localization for a given language
|
* Who is managing localization for a given language
|
||||||
* Most Github issues tagged "[localization](https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Alocalization)"
|
* Most Github issues tagged
|
||||||
|
[localization](https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Alocalization)
|
||||||
|
|
||||||
You don't have to subscribe in order to post to this list. However, subscribing
|
You don't have to subscribe in order to post to this list. However, subscribing
|
||||||
makes your messages less likely to be marked as spam and allows you to receive
|
makes your messages less likely to be marked as spam and allows you to receive
|
||||||
@ -348,12 +439,17 @@ address your email to `qubes-translation@googlegroups.com`. If your post does
|
|||||||
not appear immediately, please allow time for moderation to occur. To
|
not appear immediately, please allow time for moderation to occur. To
|
||||||
unsubscribe, send a blank email to
|
unsubscribe, send a blank email to
|
||||||
`qubes-translation+unsubscribe@googlegroups.com`. This list also has an
|
`qubes-translation+unsubscribe@googlegroups.com`. This list also has an
|
||||||
optional [Google Groups web interface](https://groups.google.com/group/qubes-translation).
|
optional [Google Groups web
|
||||||
|
interface](https://groups.google.com/group/qubes-translation).
|
||||||
|
|
||||||
## Forum
|
## Forum
|
||||||
|
|
||||||
The official [Qubes Forum](https://qubes-os.discourse.group) is a place where you can ask questions, get help, share tips and experiences, and more! For a long time, members of our community have sought a privacy-respecting forum experience with modern features that traditional mailing lists do not support. The open-source [Discourse](https://www.discourse.org/) platform fills this need for us, as it does for many other open-source projects. Thanks
|
The official [Qubes Forum](https://qubes-os.discourse.group) is a place where
|
||||||
to their generous [free hosting for open source projects](https://blog.discourse.org/2018/11/free-hosting-for-open-source-v2/), we're pleased to be able to create this space for our community.
|
you can ask questions, get help, share tips and experiences, and more! For a
|
||||||
|
long time, members of our community have sought a privacy-respecting forum
|
||||||
|
experience with modern features that traditional mailing lists do not support.
|
||||||
|
The open-source [Discourse](https://www.discourse.org/) platform fills this
|
||||||
|
need for us, as it does for many other open-source projects.
|
||||||
|
|
||||||
### Why was this forum created?
|
### Why was this forum created?
|
||||||
|
|
||||||
@ -363,7 +459,8 @@ privacy implications and user experience were unacceptable for many members of
|
|||||||
our community, especially with the recent addition of a sign-in requirement to
|
our community, especially with the recent addition of a sign-in requirement to
|
||||||
view threads. Many of you value the lower barrier to entry, organization,
|
view threads. Many of you value the lower barrier to entry, organization,
|
||||||
ease-of-use, and modern social features that today's forums support. Moreover,
|
ease-of-use, and modern social features that today's forums support. Moreover,
|
||||||
Discourse [features email integration](https://qubes-os.discourse.group/t/using-the-forum-via-email/533/1)
|
Discourse [features email
|
||||||
|
integration](https://qubes-os.discourse.group/t/using-the-forum-via-email/533/1)
|
||||||
for those who still prefer the traditional mailing list format.
|
for those who still prefer the traditional mailing list format.
|
||||||
|
|
||||||
### How is this different from our mailing lists?
|
### How is this different from our mailing lists?
|
||||||
@ -383,33 +480,46 @@ decide where and how you want to join the conversation.
|
|||||||
|
|
||||||
Many open-source projects (such as Fedora and Debian) have both mailing lists
|
Many open-source projects (such as Fedora and Debian) have both mailing lists
|
||||||
and forums (and additional discussion venues). In fact, Qubes already had
|
and forums (and additional discussion venues). In fact, Qubes already had
|
||||||
non-mailing-list discussion venues such as [IRC](#unofficial-chat-channels) and [Reddit](https://www.reddit.com/r/Qubes/) before this forum
|
non-mailing-list discussion venues such as [IRC](#unofficial-chat-channels) and
|
||||||
was introduced. We believe that this additional venue fosters the continued
|
[Reddit](https://www.reddit.com/r/Qubes/) before this forum was introduced. We
|
||||||
growth of community participation and improves everyone's experience. In
|
believe that this additional venue fosters the continued growth of community
|
||||||
addition, we fully expect that many community members -- especially the most
|
participation and improves everyone's experience. In addition, we fully expect
|
||||||
active ones -- will choose to participate in both venues. (Again, for those who
|
that many community members -- especially the most active ones -- will choose
|
||||||
still prefer interacting via email, [Discourse supports that too](https://qubes-os.discourse.group/t/using-the-forum-via-email/533/1)!)
|
to participate in both venues. (Again, for those who still prefer interacting
|
||||||
|
via email, [Discourse supports that
|
||||||
|
too](https://qubes-os.discourse.group/t/using-the-forum-via-email/533/1)!)
|
||||||
|
|
||||||
|
## Social media
|
||||||
|
|
||||||
## Social media ##
|
The Qubes OS Project has a presence on several social media platforms,
|
||||||
|
including:
|
||||||
The Qubes OS Project has a presence on several social media platforms, including:
|
|
||||||
|
|
||||||
* [Twitter](https://twitter.com/QubesOS)
|
* [Twitter](https://twitter.com/QubesOS)
|
||||||
* [Reddit](https://www.reddit.com/r/Qubes/)
|
* [Reddit](https://www.reddit.com/r/Qubes/)
|
||||||
* [Facebook](https://www.facebook.com/QubesOS/)
|
* [Facebook](https://www.facebook.com/QubesOS/)
|
||||||
* [LinkedIn](https://www.linkedin.com/company/qubes-os/)
|
* [LinkedIn](https://www.linkedin.com/company/qubes-os/)
|
||||||
|
|
||||||
Generally speaking, these are not intended to be primary support venues.
|
Generally speaking, these are not intended to be primary support venues. (Those
|
||||||
(Those would be [qubes-users](#qubes-users) and the [forum](#forum).)
|
would be [qubes-users](#qubes-users) and the [forum](#forum).) Rather, these
|
||||||
Rather, these are primarily intended to be a way to more widely disseminate items published on the [news](/news/) page.
|
are primarily intended to be a way to more widely disseminate items published
|
||||||
If you use one of these platforms, you may find it convenient to follow the Qubes OS Project there as a way of receiving Qubes news.
|
on the [news](/news/) page. If you use one of these platforms, you may find it
|
||||||
|
convenient to follow the Qubes OS Project there as a way of receiving Qubes
|
||||||
|
news.
|
||||||
|
|
||||||
## Unofficial chat channels
|
## Unofficial venues
|
||||||
|
|
||||||
The following unofficial chat channels are maintained by the community:
|
If you find another venue on the Internet that is not listed here, it is
|
||||||
|
**unofficial**, which means that the Qubes team does **not** monitor or
|
||||||
|
moderate it. Please be especially careful in unofficial venues.
|
||||||
|
|
||||||
|
(Note: If a Qubes team member discovers the venue and decides to pop in, that
|
||||||
|
should not be taken as a commitment to monitor or moderate the venue. It still
|
||||||
|
remains unofficial. Also, please make sure someone claiming to be a Qubes team
|
||||||
|
member really is one. It could be an impostor!)
|
||||||
|
|
||||||
|
For example, here are some unofficial chat channels we know about that are
|
||||||
|
maintained by the community:
|
||||||
|
|
||||||
* Matrix, Qubes-related: <https://matrix.to/#/#cybersec-qubes_os:matrix.org>
|
* Matrix, Qubes-related: <https://matrix.to/#/#cybersec-qubes_os:matrix.org>
|
||||||
* Matrix, strictly Qubes: <https://matrix.to/#/#Qubes-OS:matrix.org>
|
* Matrix, strictly Qubes: <https://matrix.to/#/#Qubes-OS:matrix.org>
|
||||||
* `#qubes` channel on libera.chat via traditional IRC clients
|
* `#qubes` channel on libera.chat via traditional IRC clients
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user