Create experts contact list (#17511)

Summary of the issue:
It is unclear who to tag on issues and pull requests.
Contributors require insider knowledge on who should be tagged on relevant issues/PRs.
Other projects such as Python and wxWidgets maintain experts lists to make communicating with the community easier.

Description of user facing changes
Add an experts list for community contact

projectDocs/community/expertsList.md

@@ -0,0 +1,26 @@
+# Community experts list
+
+This document outlines NV Access employees and community contributors.
+This can be used as a reference for people to contact or tag in regard to relevant issues and pull requests.
+
+## NV Access
+
+For optimal responses, please avoid tagging NV Access employees on unrelated tickets.
+General enquiries should be directed to <[email protected]>.
+
+| GitHub | email | topics |
+|---|---|---|
+| @gerald-hartig | <[email protected]> | Controversial product decisions |
+| @seanbudd | <[email protected]> | Issue triage, technical decisions |
+| @SaschaCowley | <[email protected]> | Issue triage, technical decisions |
+| @michaelDCurran | <[email protected]> | Advanced technical consulting |
+| @Qchristensen | <[email protected]> | User documentation, user support |
+
+## Community
+
+| GitHub | email | topics |
+|---|---|---|
+| @codeofdusk | <[email protected]> | Windows Terminal and console, Microsoft UI Automation |
+| @nvdaes | <[email protected]> | Add-on store, braille |
+| @michaelweghorn | <[email protected]> | LibreOffice |
+| @jcsteh | <[email protected]> | Mozilla Firefox |

projectDocs/community/readme.md

@@ -1,7 +1,10 @@
 ## Get support
-Whether you are a beginner, an advanced user, a new or a long time developer; or if you represent an organization wishing to know more or to contribute to NVDA: you can get support through the included documentation as well as several communication channels dedicated to the NVDA screen reader. Here is an overview of the most important support sources.
+
+Whether you are a beginner, an advanced user, a new or a long time developer; or if you represent an organization wishing to know more or to contribute to NVDA: you can get support through the included documentation as well as several communication channels dedicated to the NVDA screen reader.
+Here is an overview of the most important support sources.
 
 ### Important links
+
 * You can find information on user support on the [NV Access website](https://www.nvaccess.org/get-help/).
 * [Reporting issues on GitHub](../issues/readme.md)
 * [NVDA on GitHub](https://github.com/nvaccess/nvda)
@@ -12,23 +15,30 @@ This includes information on reporting issues, triaging issues, testing, transla
 * [Translating NVDA](../translating/readme.md): Information about how to translate NVDA into another language
 
 ### Documentation
+
 * [NVDA User Guide](https://www.nvaccess.org/files/nvda/documentation/userGuide.html)
 * [NVDA Developer Guide](https://www.nvaccess.org/files/nvda/documentation/developerGuide.html)
 * [Key Commands](https://www.nvaccess.org/files/nvda/documentation/keyCommands.html)
 * [Changes in the latest release](https://www.nvaccess.org/files/nvda/documentation/changes.html)
 * [Release process](./releaseProcess.md)
 
 ### Add-ons
+
 * [The NVDA Add-on store](https://www.nvaccess.org/files/nvda/documentation/userGuide.html#AddonsManager)
 * [Community add-ons website](https://addons.nvda-project.org/).
 This website is considered legacy software, using the NVDA Add-on Store instead is encouraged.
 
 ### Communication channels
+
+* [Experts list](./expertsList.md) for finding experts in the NVDA community
+
 #### NV Access
+
 * See the [NV Access](https://www.nvaccess.org/contact-us/) website for our social media accounts and other contact information.
 * [NVDA Add-on API Mailing List](https://groups.google.com/a/nvaccess.org/g/nvda-api)
 
 #### NVDA Community
+
 * [NVDA Users Mailing List](https://nvda.groups.io/g/nvda)
 * [NVDA Developers Mailing List](https://groups.io/g/nvda-devel)
 * [NVDA Translators list](https://groups.io/g/nvda-translations)

projectDocs/issues/triage.md

@@ -157,7 +157,7 @@ Community members should apply the `triaged` label where an issue is a well form
 
 If an issue has been checked by NV Access, and needs further triage, the `needs-triage` label will be applied.
 Please notify NV Access when you believe the issue is ready for the `triaged` label.
-You can do this by tagging `@nvaccess/developers` or emailing <[email protected]>.
+You can do this by tagging [relevant NV Access employees](../community/expertsList.md#nv-access) or emailing <[email protected]>.
 
 A `triaged` issue that requires a complex fix may require advice from NV Access, such as a project plan, before implementation is started.
 

readme.md

@@ -14,23 +14,27 @@ NVDA is available under a modified GNU General Public License version 2.
 Please refer to [our license](./copying.txt) for more information.
 
 ## Acknowledgements
+
 We would like to extend our sincere gratitude to [SignPath](https://www.signpath.io/) for their generous support in providing code signing services to many open source projects, including NVDA.
 Their contribution helps us maintain the security and integrity of our releases.
 
 ## NVDA Community
+
 * [Support and information for NVDA users](https://www.nvaccess.org/get-help/)
 * [Report an issue or feature request](./projectDocs/issues/readme.md)
 * [Getting add-ons](https://www.nvaccess.org/files/nvda/documentation/userGuide.html#AddonsManager)
+* [Contact list](./projectDocs/community/expertsList.md) for NV Access and community experts.
 * [More important links and community information](./projectDocs/community/readme.md)
 
 ## Contributing to NVDA
+
 If you would like to contribute to NVDA, you can read more information in our [contributing guide](./.github/CONTRIBUTING.md).
 This includes information on reporting issues, triaging issues, testing, translating, contributing code/documentation and creating add-ons.
 
 ## Status checks
 
 * AppVeyor
-   * Alpha build status: [![view latest alpha builds](https://ci.appveyor.com/api/projects/status/sqeer6p8lc80lvqe/branch/master?svg=true)](https://ci.appveyor.com/project/NVAccess/nvda/branch/master)
-   * Beta build status: [![view latest beta builds](https://ci.appveyor.com/api/projects/status/sqeer6p8lc80lvqe/branch/beta?svg=true)](https://ci.appveyor.com/project/NVAccess/nvda/branch/beta)
+  * Alpha build status: [![view latest alpha builds](https://ci.appveyor.com/api/projects/status/sqeer6p8lc80lvqe/branch/master?svg=true)](https://ci.appveyor.com/project/NVAccess/nvda/branch/master)
+  * Beta build status: [![view latest beta builds](https://ci.appveyor.com/api/projects/status/sqeer6p8lc80lvqe/branch/beta?svg=true)](https://ci.appveyor.com/project/NVAccess/nvda/branch/beta)
 * Pre-commit status (master): [![view pre-commit checks on master](https://results.pre-commit.ci/badge/github/nvaccess/nvda/master.svg)](https://results.pre-commit.ci/latest/github/nvaccess/nvda/master)
 * CodeQL security analysis status (master): [![view CodeQL security analysis checks on master](https://github.com/nvaccess/nvda/actions/workflows/github-code-scanning/codeql/badge.svg?branch=master)](https://github.com/nvaccess/nvda/actions/workflows/github-code-scanning/codeql?query=branch%3Amaster)