2
0
mirror of https://github.com/sudo-project/sudo.git synced 2025-08-22 01:49:11 +00:00

Make the sections on bug reporting consistent with each other.

GitHub issue #292
This commit is contained in:
Todd C. Miller 2023-07-27 09:51:57 -06:00
parent 857653f9f5
commit 50fde5d815
2 changed files with 33 additions and 25 deletions

View File

@ -79,23 +79,27 @@ fairly low traffic lists so the digest versions are not a significant win.
Mailing list archives are also available. See the mailing list web sites Mailing list archives are also available. See the mailing list web sites
for the appropriate links. for the appropriate links.
## Web page ## Sudo web page
There is a sudo web page at https://www.sudo.ws/ that contains an overview There is a sudo web page at https://www.sudo.ws/ that contains
of sudo, documentation, downloads, a bug tracker, the sudo blog, information documentation, downloads, a bug tracker, the source repo, the sudo
about beta versions and other useful info. blog, information about beta versions and other useful info.
## Bug reports ## Filing bug reports/issues
If you have found what you believe to be a bug, you can file a bug If you believe you have found a bug, you can either file a bug
report in the sudo bug database, at https://bugzilla.sudo.ws/. report in the sudo bug database, https://bugzilla.sudo.ws/, or open
Alternately, you can file a GitHub issue if that is easier for you a [GitHub issue](https://github.com/sudo-project/sudo/issues),
at https://github.com/sudo-project/sudo/issues/. whichever you find easier. If you would prefer to use email,
messages may be sent to the [sudo-workers@sudo.ws mailing
list](https://www.sudo.ws/mailman/listinfo/sudo-workers) (public)
or to sudo@sudo.ws (private).
See [docs/SECURITY.md](docs/SECURITY.md) for our security policy For sudo's security policy and how to report security issues, see
and how to report security issues. [docs/SECURITY.md](docs/SECURITY.md).
Check [docs/TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md) *before* Please check [docs/TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md)
submitting a bug report. When reporting bugs, be sure to include *before* submitting a bug report. When reporting bugs, be sure to
the version of sudo you are using as well as the platform you are include the version of sudo you are using, the operating system
running it on. and/or distro that is affected, and, if possible, step-by-step
instructions to reproduce the problem.

View File

@ -12,18 +12,22 @@ writing a single line of code.
## Filing bug reports/issues ## Filing bug reports/issues
If you find a bug in Sudo, you may open a [GitHub If you believe you have found a bug, you can either file a bug
issue](https://github.com/sudo-project/sudo/issues) or file a report in the sudo bug database, https://bugzilla.sudo.ws/, or open
[Bugzilla bug](https://bugzilla.sudo.ws). If you would rather use a [GitHub issue](https://github.com/sudo-project/sudo/issues),
email, messages may be sent to the [sudo-workers@sudo.ws whichever you find easier. If you would prefer to use email,
mailing list](https://www.sudo.ws/mailman/listinfo/sudo-workers) messages may be sent to the [sudo-workers@sudo.ws mailing
(public) or to sudo@sudo.ws (private). list](https://www.sudo.ws/mailman/listinfo/sudo-workers) (public)
or to sudo@sudo.ws (private).
For information on reporting security issues, see [SECURITY.md](SECURITY.md). For sudo's security policy and how to report security issues, see
[SECURITY.md](SECURITY.md).
Include the version of sudo you are using, the operating system Please check [TROUBLESHOOTING.md](TROUBLESHOOTING.md) *before*
and/or distro that is affected, and, if possible, step-by-step submitting a bug report. When reporting bugs, be sure to include
instructions to reproduce the problem. the version of sudo you are using, the operating system and/or
distro that is affected, and, if possible, step-by-step instructions
to reproduce the problem.
## Making changes to Sudo ## Making changes to Sudo