Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-03-26 08:18:09 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update links

Browse Source
This commit is contained in:
Andrew David Wong 2021-06-21 00:38:18 -07:00
parent f860726c93
commit 527a2eb339
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
6 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
developer/general/doc-guidelines.md
View File

@ -54,7 +54,7 @@ send it to the appropriate [mailing list](/support/). If you see that something
in the documentation should be fixed or improved, please in the documentation should be fixed or improved, please
[contribute](#how-to-contribute) the change yourself. To report an issue with [contribute](#how-to-contribute) the change yourself. To report an issue with
the documentation, please follow our standard [issue reporting the documentation, please follow our standard [issue reporting
guidelines](/doc/reporting-bugs/). (If you report an issue with the guidelines](/doc/issue-tracking/). (If you report an issue with the
documentation, you will likely be asked to address it, unless there is a clear documentation, you will likely be asked to address it, unless there is a clear
indication in your report that you are not willing or able to do so.) indication in your report that you are not willing or able to do so.)
@ -70,7 +70,7 @@ A few notes before we get started:
and protect our users. and protect our users.
* We don't want you to spend time and effort on a contribution that we can't * We don't want you to spend time and effort on a contribution that we can't
accept. If your contribution would take a lot of time, please [file an accept. If your contribution would take a lot of time, please [file an
issue](/doc/reporting-bugs/) for it first so that we can make sure we're on issue](/doc/issue-tracking/) for it first so that we can make sure we're on
the same page before significant works begins. the same page before significant works begins.
* Alternatively, you may already have written content that doesn't conform to * Alternatively, you may already have written content that doesn't conform to
these guidelines, but you'd be willing to modify it so that it does. In this these guidelines, but you'd be willing to modify it so that it does. In this

2
introduction/contributing.md
View File

@ -18,7 +18,7 @@ ways in which you can help:
* [Send patches](/doc/source-code/#how-to-send-patches) to fix bugs or * [Send patches](/doc/source-code/#how-to-send-patches) to fix bugs or
implement features implement features
* [Contribute packages](/doc/package-contributions) * [Contribute packages](/doc/package-contributions)
* [Report bugs](/doc/reporting-bugs/) * [Report bugs](/doc/issue-tracking/)
* [Test new releases and updates](/doc/testing/) * [Test new releases and updates](/doc/testing/)
* Submit [HCL reports](/doc/hcl/) for your hardware * Submit [HCL reports](/doc/hcl/) for your hardware
* Record [video tours](/video-tours/) * Record [video tours](/video-tours/)

2
introduction/faq.md
View File

@ -311,7 +311,7 @@ So, if feature X isn't enabled, it's most likely for one of three reasons:
2. Our platform supports it, but we've decided not to enable it. 2. Our platform supports it, but we've decided not to enable it.
3. Our platform supports it, but we're not aware that we can enable it or have forgotten to do so. 3. Our platform supports it, but we're not aware that we can enable it or have forgotten to do so.
If it seems like a feature that we can and should enable, please [let us know](/doc/reporting-bugs/)! If it seems like a feature that we can and should enable, please [let us know](/doc/issue-tracking/)!
## Users ## Users

10
introduction/support.md
View File

@ -23,10 +23,10 @@ Before asking for help, please check the [troubleshooting](/doc/#troubleshooting
Your question may already be answered there. Your question may already be answered there.
If you're looking for known issues or would like to file a bug report, please If you're looking for known issues or would like to file a bug report, please
see the [issue tracker](/doc/reporting-bugs/). These issues are constantly being updated and may 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 contain workarounds for problems that you're experiencing, so it's worth
[searching the issue tracker](/doc/reporting-bugs/#search-tips) as a first step. However, please note that [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/reporting-bugs/#the-issue-tracker-is-not-a-discussion-forum). [the issue tracker is not a discussion forum](/doc/issue-tracking/#the-issue-tracker-is-not-a-discussion-forum).
## Staying safe ## Staying safe
@ -141,8 +141,8 @@ Conduct](/code-of-conduct/) for more information.
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 discuss
things. However, if you're submitting a more formal report, we'd prefer that things. However, if you're submitting a more formal report, we'd prefer that
you submit it to our [issue tracker](/doc/reporting-bugs/) so that it doesn't get overlooked. 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/reporting-bugs/#the-issue-tracker-is-not-a-discussion-forum).) (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/).

4
user/downloading-installing-upgrading/testing.md
View File

@ -24,7 +24,7 @@ How to test upcoming Qubes OS releases:
* (No support) Experiment with devel alpha ISOs found from time to time at * (No support) Experiment with devel alpha ISOs found from time to time at
[Qubes OpenQA](https://openqa.qubes-os.org/). [Qubes OpenQA](https://openqa.qubes-os.org/).
Please make sure to [report any bugs you encounter](/doc/reporting-bugs/). Please make sure to [report any bugs you encounter](/doc/issue-tracking/).
See [Version Scheme](/doc/version-scheme/) for details about release versions See [Version Scheme](/doc/version-scheme/) for details about release versions
and schedules. See [Release Checklist](/doc/releases/todo/) for details about and schedules. See [Release Checklist](/doc/releases/todo/) for details about
@ -80,6 +80,6 @@ testing repository. Even a simple <span class="fa fa-thumbs-up" title="Thumbs
Up"></span> or <span class="fa fa-thumbs-down" title="Thumbs Down"></span> on Up"></span> or <span class="fa fa-thumbs-down" title="Thumbs Down"></span> on
the package's associated issue would help us to decide whether the package is the package's associated issue would help us to decide whether the package is
ready to be migrated to a stable repository. If you [report a ready to be migrated to a stable repository. If you [report a
bug](/doc/reporting-bugs/) in a package that is in a testing repository, please bug](/doc/issue-tracking/) in a package that is in a testing repository, please
reference the appropriate issue in reference the appropriate issue in
[updates-status](https://github.com/QubesOS/updates-status/issues). [updates-status](https://github.com/QubesOS/updates-status/issues).

2
user/security-in-qubes/u2f-proxy.md
View File

@ -131,5 +131,5 @@ The large number of possible combinations of template (Fedora 27, 28; Debian 8,
In some cases, you may be the first person to try a particular combination. In some cases, you may be the first person to try a particular combination.
Consequently (and as with any new feature), users will inevitably encounter bugs. Consequently (and as with any new feature), users will inevitably encounter bugs.
We ask for your patience and understanding in this regard. We ask for your patience and understanding in this regard.
As always, please [report any bugs you encounter](/doc/reporting-bugs/). As always, please [report any bugs you encounter](/doc/issue-tracking/).