From a7781cd3d23af10bac7cc0cf878120479f6269b8 Mon Sep 17 00:00:00 2001 From: Sean Budd Date: Thu, 19 Dec 2024 13:16:43 +1100 Subject: [PATCH] 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 | 26 ++++++++++++++++++++++++++ projectDocs/community/readme.md | 12 +++++++++++- projectDocs/issues/triage.md | 2 +- readme.md | 8 ++++++-- 4 files changed, 44 insertions(+), 4 deletions(-) create mode 100644 projectDocs/community/expertsList.md diff --git a/projectDocs/community/expertsList.md b/projectDocs/community/expertsList.md new file mode 100644 index 00000000000..2e1244d107f --- /dev/null +++ b/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 . + +| GitHub | email | topics | +|---|---|---| +| @gerald-hartig | | Controversial product decisions | +| @seanbudd | | Issue triage, technical decisions | +| @SaschaCowley | | Issue triage, technical decisions | +| @michaelDCurran | | Advanced technical consulting | +| @Qchristensen | | User documentation, user support | + +## Community + +| GitHub | email | topics | +|---|---|---| +| @codeofdusk | | Windows Terminal and console, Microsoft UI Automation | +| @nvdaes | | Add-on store, braille | +| @michaelweghorn | | LibreOffice | +| @jcsteh | | Mozilla Firefox | diff --git a/projectDocs/community/readme.md b/projectDocs/community/readme.md index ff80c12eadb..69606b6c3cc 100644 --- a/projectDocs/community/readme.md +++ b/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,6 +15,7 @@ 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) @@ -19,16 +23,22 @@ This includes information on reporting issues, triaging issues, testing, transla * [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) diff --git a/projectDocs/issues/triage.md b/projectDocs/issues/triage.md index 48af30e98aa..df2850b088b 100644 --- a/projectDocs/issues/triage.md +++ b/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 . +You can do this by tagging [relevant NV Access employees](../community/expertsList.md#nv-access) or emailing . A `triaged` issue that requires a complex fix may require advice from NV Access, such as a project plan, before implementation is started. diff --git a/readme.md b/readme.md index bad02a50240..94fc7b15969 100644 --- a/readme.md +++ b/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)