mir/sudo
2
0
Fork 0
mirror of https://github.com/sudo-project/sudo.git synced 2025-08-28 21:07:55 +00:00
Code Issues Releases Wiki Activity

Fix formatting of links.

Browse Source
This commit is contained in:
Todd C. Miller 2021-11-11 14:19:22 -07:00
parent 781a4fb691
commit 3ab280fc61
1 changed files with 19 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
docs/CONTRIBUTING.md
View File

@ -5,21 +5,21 @@ number of way you can help make Sudo better.
## Getting started ## Getting started
To get an overview of Sudo, please read the [README](README). There To get an overview of Sudo, please read the [README](../README). There
are multiple ways to contribute, some of which don't require writing are multiple ways to contribute, some of which don't require writing
a single line of code. 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 issue] If you find a bug in Sudo, you may open a [GitHub
(https://github.com/sudo-project/sudo/issues) or file a [Bugzilla bug] issue](https://github.com/sudo-project/sudo/issues) or file a
(https://bugzilla.sudo.ws). If you would rather use email, messages [Bugzilla bug](https://bugzilla.sudo.ws). If you would rather use
may be sent to the [sudo-workers@sudo.ws mailing list] email, messages may be sent to the [sudo-workers@sudo.ws
(https://www.sudo.ws/mailman/listinfo/sudo-workers) \(public\) or to mailing list](https://www.sudo.ws/mailman/listinfo/sudo-workers)
[sudo@sudo.ws] \(private\). (public) or to sudo@sudo.ws (private).
For information on reporting security issues, please see the [SECURITY] For information on reporting security issues, please see the
(docs/SECURITY.md) file. [SECURITY](docs/SECURITY.md) file.
Please include the version of sudo you are using, the operating Please include the version of sudo you are using, the operating
system and/or distro that is affected, and step-by-step instructions system and/or distro that is affected, and step-by-step instructions
@ -33,25 +33,26 @@ work flows:
* clone the [sudo repo](https://github.com/sudo-project/sudo), make * clone the [sudo repo](https://github.com/sudo-project/sudo), make
your changes, and submit a Pull Request (PR). your changes, and submit a Pull Request (PR).
* send a diff with your changes to the [sudo-workers@sudo.ws mailing list] * send a diff with your changes to the [sudo-workers@sudo.ws mailing
(https://www.sudo.ws/mailman/listinfo/sudo-workers) to start a discussion. list](https://www.sudo.ws/mailman/listinfo/sudo-workers) to start
a discussion.
In addition to the [GitHub repo](https://github.com/sudo-project/sudo), In addition to the [GitHub repo](https://github.com/sudo-project/sudo),
there is also a [mercurial repo](https://www.sudo.ws/repos/sudo). there is also a [mercurial repo](https://www.sudo.ws/repos/sudo).
## sudo-workers mailing list ## sudo-workers mailing list
If you would like to discuss your changes before submitting a PR, If you would like to discuss your changes before submitting a
you may do so on the [sudo-workers@sudo.ws mailing list] PR, you may do so on the [sudo-workers@sudo.ws mailing
(https://www.sudo.ws/mailman/listinfo/sudo-workers). list](https://www.sudo.ws/mailman/listinfo/sudo-workers).
Otherwise, discussion can simply occur as part of the PR work flow. Otherwise, discussion can simply occur as part of the PR work flow.
## Fuzzing ## Fuzzing
Sudo uses the [oss-fuzz project](https://github.com/google/oss-fuzz.git) Sudo uses the [oss-fuzz project](https://github.com/google/oss-fuzz.git)
to perform fuzzing. Each commit to the _main_ branch will trigger to perform fuzzing. Each commit to the _main_ branch will trigger
a short fuzzing run via the [CIFuzz action] a short fuzzing run via the [CIFuzz
(https://github.com/sudo-project/sudo/actions/workflows/main.yml). action](https://github.com/sudo-project/sudo/actions/workflows/main.yml).
The history of that action shows successful and failed fuzzing runs. The history of that action shows successful and failed fuzzing runs.
Longer fuzzing runs occur using the ClusterFuzz infrastructure. These Longer fuzzing runs occur using the ClusterFuzz infrastructure. These
@ -59,8 +60,8 @@ fuzzing runs are longer than those used by CIFuzz. A [public list of
failures](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=sudoers) failures](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=sudoers)
is available. is available.
For more information on fuzzing sudo, see the [fuzzing blog post] For more information on fuzzing sudo, see the [fuzzing blog
(https://blog.sudo.ws/posts/2021/03/fuzz-testing-sudo/). post](https://blog.sudo.ws/posts/2021/03/fuzz-testing-sudo/).
## Translations ## Translations