From 0701f196c8c2686cc5e4bcfc9bbb179c49989e42 Mon Sep 17 00:00:00 2001 From: Andrew David Wong Date: Mon, 21 Jun 2021 02:55:53 -0700 Subject: [PATCH] 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 --- introduction/support.md | 426 +++++++++++++++++++++++++--------------- 1 file changed, 268 insertions(+), 158 deletions(-) diff --git a/introduction/support.md b/introduction/support.md index 1f57b8b0..3422239a 100644 --- a/introduction/support.md +++ b/introduction/support.md @@ -15,66 +15,134 @@ ref: 122 title: Help, Support, Mailing Lists, and Forum --- -Help and support for Qubes OS is available from the [documentation](/doc/), the -[mailing lists](#mailing-lists), and our [forum](#forum) which are explained below. The Qubes OS -Project does not offer paid support services. +The Qubes community is here to help! Since Qubes is a security-oriented +operating system, we want to make sure you [stay safe](#staying-safe) as you +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/). -Your question may already be answered there. +## How to get help and support -If you're looking for known issues or would like to file a bug report, please -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 -[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). +First, let's see what kind of help you need. + +### I would like to report a security vulnerability + +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 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 -control. Please do not send or post anything that you are not comfortable seeing -discussed in public. If confidentiality is a concern, please use PGP encryption -in an off-list email. +control. Please do not send or post anything that you are not comfortable +seeing discussed in public. If confidentiality is a concern, please use PGP +encryption in an off-list email. 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 -will come into contact with others whose views and agendas differ from your own. -Everyone is free to write what they please, as long as it doesn't violate our -[Code of Conduct](/code-of-conduct/). Be friendly and open, but do not believe everything you -read. Use good judgment, and be especially careful when following instructions -(e.g., copying commands) given by others on the lists. +will come into contact with others whose views and agendas differ from your +own. Everyone is free to write what they please, as long as it doesn't violate +our [Code of Conduct](/code-of-conduct/). Be friendly and open, but do not +believe everything you read. Use good judgment, and be especially careful when +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 -signed by the PGP key belonging to the team member who sends the announcement. -However, anyone on a mailing list can choose to sign their messages, so the -presence of a PGP signature does not indicate authority. How, then, 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. Typically, 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/). +It's always possible that a bad actor could try to impersonate any member of +the [Qubes team](/team/) anywhere on the Internet. Please don't assume that +someone who claims to be an official Qubes team member really is one without an +appropriate form of authentication, such as a [verified PGP-signed +message](/security/verifying-signatures/). (But bear in mind that anyone can +generate a key with any name on it and use it to PGP-sign a message, so the +mere presence of a PGP signature does not indicate authority. Successful +[verification](/security/verifying-signatures/) is what counts.) All official +[news](/news/) can be authenticated by [verifying the +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 -proven track record of [contributing software packages](/doc/package-contributions/) or [contributing to the -documentation](/doc/doc-guidelines/). It's unlikely that individuals who have worked hard to build -good reputations for themselves through their contributions over the years would -risk giving malicious advice in signed messages to public mailing lists. Since -every contribution to the Qubes OS 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. +proven track record of [contributing software +packages](/doc/package-contributions/) or [contributing to the +documentation](/doc/doc-guidelines/). It's unlikely that individuals who have +worked hard to build good reputations for themselves through their +contributions over the years would risk giving malicious advice in signed +messages to public mailing lists. Since every contribution to the Qubes OS +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 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 -`qubes-users` or the [forum](#forum). **Please do not send questions to individual -Qubes developers.** By sending a message to the appropriate mailing list, you -are not only giving others a chance to help you, but you may also be helping -others by starting a public discussion about a shared problem or interest. +[forum](#forum), all of which are explained below. Most questions should be +directed to `qubes-users` or the [forum](#forum). **Please do not send +questions to individual Qubes developers.** By sending a message to the +appropriate mailing list, you are not only giving others a chance to help you, +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 -and voluntarily help each other out of mutual interest and good will. They are +These are open venues where people freely come together to discuss Qubes and +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 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. @@ -85,38 +153,38 @@ guidelines. ### Be polite and respectful -Remember, no one here is under any obligation -to reply to you. Think about your readers. Most of them are coming home after -a long, hard day at work. The last thing they need is someone's temper -tantrum. If you are rude and disrespectful, you are very -likely to be ignored. +Remember, no one here is under any obligation to reply to you. Think about your +readers. Most of them are coming home after a long, hard day at work. The last +thing they need is someone's temper tantrum. If you are rude and disrespectful, +you are very likely to be ignored. ### Be concise -Include only essential information. Most of your readers lead -busy lives and have precious little time. We *want* to spend some of that -time helping you, if we can. But if you ramble, it will be easier to skip -over you and help someone else who gets right to the point. +Include only essential information. Most of your readers lead busy lives and +have precious little time. We *want* to spend some of that time helping you, if +we can. But if you ramble, it will be easier to skip over you and help someone +else who gets right to the point. ### Help us help you -Tell us what you've already tried, and which -documentation pages you've already read. Put yourself in your readers' shoes. -What essential information would they require in order to be able to help -you? Make sure to include that information in your message. A great way to -provide your hardware details is by [generating and submitting a Hardware -Compatibility List (HCL) report](/doc/hcl/#generating-and-submitting-new-reports), then linking to it in your -message. [Ask questions the smart way.](http://www.catb.org/esr/faqs/smart-questions.html) +Tell us what you've already tried, and which documentation pages you've already +read. Put yourself in your readers' shoes. What essential information would +they require in order to be able to help you? Make sure to include that +information in your message. A great way to provide your hardware details is by +[generating and submitting a Hardware Compatibility List (HCL) +report](/doc/hcl/#generating-and-submitting-new-reports), then linking to it in +your message. [Ask questions the smart +way.](http://www.catb.org/esr/faqs/smart-questions.html) ### Be patient -Do not "bump" a thread more than once every three days *at -most*. If it seems like your messages to the mailing lists are consistently -being ignored, make sure you're following the guidelines explained on this -page. If you're already doing so but still not getting any replies, then it's -likely that no one who knows the answer has had time to reply yet. Remember -that the devs are very busy working on Qubes. They usually only have a chance -to answer questions on the mailing lists once every several days. +Do not "bump" a thread more than once every three days *at most*. If it seems +like your messages to the mailing lists are consistently being ignored, make +sure you're following the guidelines explained on this page. If you're already +doing so but still not getting any replies, then it's likely that no one who +knows the answer has had time to reply yet. Remember that the devs are very +busy working on Qubes. They usually only have a chance to answer questions on +the mailing lists once every several days. ### 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 understanding community that many of them spend hours of their personal time helping complete strangers, including many who post anonymously. (Given the -integration of Qubes with [Whonix](/doc/whonix/), we understand better than most the -complexities of privacy and anonymity, and we know that many users have no -other choice but to post anonymously.) You can read our project's [Code of -Conduct](/code-of-conduct/) for more information. +integration of Qubes with [Whonix](/doc/whonix/), we understand better than +most the complexities of privacy and anonymity, and we know that many users +have no other choice but to post anonymously.) You can read our project's [Code +of Conduct](/code-of-conduct/) for more information. ### Report issues and submit changes in the right places -The mailing lists and [forum](#forum) are good places to ask questions and discuss -things. However, if you're submitting a more formal report, we'd prefer that -you submit it to our [issue tracker](/doc/issue-tracking/) so that it 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).) +The mailing lists and [forum](#forum) are good places to ask questions and +discuss things. However, if you're submitting a more formal report, we'd prefer +that you submit it to our [issue tracker](/doc/issue-tracking/) so that it +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, don't simply point it out in a discussion venue. Instead, [submit the change](/doc/doc-guidelines/). @@ -150,9 +220,11 @@ change](/doc/doc-guidelines/). ### Moderation 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. -Specifically, users should not request that posts or messages be deleted 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. +Beyond this, users should not expect any specific action from the moderation +team. Specifically, users should not request that posts or messages be deleted +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 @@ -163,11 +235,14 @@ which list is correct for your message. #### 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 -replying. Please refrain from doing this. Instead, either [interleave](https://en.wikipedia.org/wiki/Posting_style#Interleaved_style) 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. +[Top-posting](https://en.wikipedia.org/wiki/Posting_style#Top-posting) is +placing your reply above the quoted message to which you're replying. Please +refrain from doing this. Instead, either +[interleave](https://en.wikipedia.org/wiki/Posting_style#Interleaved_style) +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 @@ -178,73 +253,79 @@ in installer.") #### Do not send duplicates -If your message is not successfully sent to the list, it probably got caught -in the spam filter. We check the spam filter regularly, so please be patient, -and your message should be approved (and your email address added to the -whitelist) within a few days. +If your message is not successfully sent to the list, it probably got caught in +the spam filter. We check the spam filter regularly, so please be patient, and +your message should be approved (and your email address added to the whitelist) +within a few days. #### Keep the list CCed -Keep the mailing list CCed throughout the conversation unless there's a -special need for privacy (in which case, use PGP encryption). This increases -the likelihood that a greater quantity of useful information will be -available to everyone in the future. +Keep the mailing list CCed throughout the conversation unless there's a special +need for privacy (in which case, use PGP encryption). This increases the +likelihood that a greater quantity of useful information will be available to +everyone in the future. #### Quote appropriately -If you're replying to a thread (whether your own or -someone else's), you should make sure to quote enough from previous messages -in the thread so that people reading your message can understand the context -without having to find and read earlier messages from that thread. Each reply -should continue the conversation and, ideally, be readable as a conversation -in itself. Do not quote advertisements in signatures or inline PGP signature -blocks. (Quoting the latter interferes with the ability of programs like -Enigmail to properly quote replies thereafter). +If you're replying to a thread (whether your own or someone else's), you should +make sure to quote enough from previous messages in the thread so that people +reading your message can understand the context without having to find and read +earlier messages from that thread. Each reply should continue the conversation +and, ideally, be readable as a conversation in itself. Do not quote +advertisements in signatures or inline PGP signature blocks. (Quoting the +latter interferes with the ability of programs like Enigmail to properly quote +replies thereafter). #### English not required -If you do not speak English, you should feel free to post in your own -language. However, bear in mind that most members of the list can only read -English. You may wish to include an automated translation in your message out -of consideration for those readers. If you choose to write in English, please -do not apologize for doing so poorly, as it is unnecessary. We understand and -will ask for clarification if needed. +If you do not speak English, you should feel free to post in your own language. +However, bear in mind that most members of the list can only read English. You +may wish to include an automated translation in your message out of +consideration for those readers. If you choose to write in English, please do +not apologize for doing so poorly, as it is unnecessary. We understand and will +ask for clarification if needed. #### Suggestions -While we're generally open to hearing suggestions for new features, please -note that we already have a pretty well defined [roadmap](https://github.com/QubesOS/qubes-issues/milestones), and it's rather -unlikely that we will change our schedule in order to accommodate your -request. If there's a particular feature you'd like to see in Qubes, a much -more effective way to make it happen is to contribute a patch that implements -it. We happily accept such contributions, provided they meet our standards. -Please note, however, that it's always a good idea to field a discussion of -your idea 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. +While we're generally open to hearing suggestions for new features, please note +that we already have a pretty well defined +[roadmap](https://github.com/QubesOS/qubes-issues/milestones), and it's rather +unlikely that we will change our schedule in order to accommodate your request. +If there's a particular feature you'd like to see in Qubes, a much more +effective way to make it happen is to contribute a patch that implements it. We +happily accept such contributions, provided they meet our standards. Please +note, however, that it's always a good idea to field a discussion of your idea +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 While the mailing lists are implemented as Google Group web forums, a Google account is in no way required, expected, or encouraged. Many discussants (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 -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 -free infrastructure, and we [distrust the 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](https://en.wikipedia.org/wiki/Electronic_mailing_list), +interacting with them solely through plain text email 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 free infrastructure, and we [distrust the +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 -This section covers each of our individual [mailing lists](https://en.wikipedia.org/wiki/Electronic_mailing_list), with -details about the purpose of each list and how to use it. +This section covers each of our individual [mailing +lists](https://en.wikipedia.org/wiki/Electronic_mailing_list), with details +about the purpose of each list and how to use it. ### qubes-announce 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 -[Qubes Security Bulletins (QSBs)](/security/bulletins/), new stable releases, and end-of-life -notices are announced here. +[Qubes Security Bulletins (QSBs)](/security/bulletins/), new stable releases, +and end-of-life notices are announced here. To subscribe, send a blank email to `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 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) * The [User FAQ](/faq/#users) * 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 appear immediately, please allow time for moderation to occur. To unsubscribe, 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 -[traditional mail archive](https://www.mail-archive.com/qubes-users@googlegroups.com/). +also has an optional [Google Groups web +interface](https://groups.google.com/group/qubes-users) and [traditional mail +archive](https://www.mail-archive.com/qubes-users@googlegroups.com/). ### qubes-devel -This list is primarily intended for people who are interested in contributing to -Qubes or who are willing to learn more about its architecture and -implementation. Examples of topics and questions suitable for this list include: +This list is primarily intended for people who are interested in contributing +to Qubes or who are willing to learn more about its architecture and +implementation. Examples of topics and questions suitable for this list +include: * Questions about why we made certain architecture or implementation decisions. * 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 does not appear immediately, please allow time for moderation to occur. To 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) -and [traditional mail archive](https://www.mail-archive.com/qubes-devel@googlegroups.com/). +This list also has an optional [Google Groups web +interface](https://groups.google.com/group/qubes-devel) and [traditional mail +archive](https://www.mail-archive.com/qubes-devel@googlegroups.com/). ### qubes-project -This list is for non-technical discussion and coordination around the -Qubes OS project. +This list is for non-technical discussion and coordination around the Qubes OS +project. Examples of topics or question suitable for this list include: * Participation (talks, workshops, etc.) at upcoming events * Project funding applications and strategies * 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 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 immediately, please allow time for moderation to occur. To unsubscribe, send a 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 -This list is for discussion around the localization and translation of Qubes OS, -its documentation, and the website. +This list is for discussion around the localization and translation of Qubes +OS, its documentation, and the website. 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 -* 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 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 unsubscribe, send a blank email to `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 -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 -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. +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. ### 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 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, -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. ### 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 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 -was introduced. We believe that this additional venue fosters the continued -growth of community participation and improves everyone's experience. In -addition, we fully expect that many community members -- especially the most -active ones -- will choose 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)!) +non-mailing-list discussion venues such as [IRC](#unofficial-chat-channels) and +[Reddit](https://www.reddit.com/r/Qubes/) before this forum was introduced. We +believe that this additional venue fosters the continued growth of community +participation and improves everyone's experience. In addition, we fully expect +that many community members -- especially the most active ones -- will choose +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) * [Reddit](https://www.reddit.com/r/Qubes/) * [Facebook](https://www.facebook.com/QubesOS/) * [LinkedIn](https://www.linkedin.com/company/qubes-os/) -Generally speaking, these are not intended to be primary support venues. -(Those would be [qubes-users](#qubes-users) and the [forum](#forum).) -Rather, these are primarily intended to be a way to more widely disseminate items published 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. +Generally speaking, these are not intended to be primary support venues. (Those +would be [qubes-users](#qubes-users) and the [forum](#forum).) Rather, these +are primarily intended to be a way to more widely disseminate items published +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: * Matrix, strictly Qubes: * `#qubes` channel on libera.chat via traditional IRC clients -