-
-
Notifications
You must be signed in to change notification settings - Fork 651
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update documentation in 2 places: new security team and setting up in…
…itial nvda development git repo (#16091) Closes issue number: #16088 # Summary of the issue / description of user facing changes This PR is to update the documentation in 2 places: * include information on the NVDA security team * for consistency, show the git clone command explicity when initially creating your nvda environment Code Review Checklist: No code changes. Commits: * Added additional content to docs * Added forking before cloning * Moved comments to text
- Loading branch information
1 parent
3d64cf9
commit dc23f9c
Showing
2 changed files
with
20 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,3 +20,16 @@ This information will help us triage your report more quickly. | |
* If there is a known solution or approach to fixing this issue | ||
|
||
Examples of handled security issues in NVDA can be found in the [NVDA GitHub Security Advisories page](https://github.com/nvaccess/nvda/security/advisories). | ||
|
||
## Security Advisory Group | ||
|
||
NV Access is committed to maintaining the highest standards of security in NVDA. In line with this commitment, we have established a Security Advisory Group. This group plays a pivotal role in enhancing the security of NVDA. | ||
|
||
Objectives and Functioning: | ||
|
||
* The group is composed of dedicated users and security enthusiasts who volunteer their expertise. | ||
* It focuses on identifying, analysing and resolving security issues in a collaborative manner. | ||
* The group's contributions are instrumental in maintaining and elevating our security standards. | ||
* Their insights and recommendations are directly incorporated into our development process, leading to more secure and reliable software. | ||
|
||
We welcome participation from our user community. If you have a keen interest in security and wish to contribute, please [contact us](mailto:[email protected]]). |