Re: Notes from a developer: what do developers really want in an NVDA GitHub issue
Thank you so very much for taking the time and effort to put this together and present it. It is invaluable information and it is essential information as well.
You have mentioned my tutorial, Creating an Issue in GitHub for NVDA, so I am posting a direct link to it. In the context of your own offering, I think it is even more important for those who are considering becoming bug report contributors, who may not as yet have a GitHub Account, or wish to create one prior to making up their minds, download my MS-Word template for a GitHub Bug Report, activate that template to open a new, blank fillable form, and have a look around. It is based, precisely, on the GitHub template that is used, but is a bit more user friendly (in my opinion) to fill out. But even if you don't want to use the template once you "take the plunge" and become a bug reporter, this is still an excellent way to familiarize yourself with each and every part of the bug report and what you need to fill out to the maximum extent possible (there will, on occasion, be something that's either not applicable or which you simply cannot fill out initially, but those should be few). Here are the two bug report templates I created:
MS-Word Fillable Form for an NVDA Bug Report Including Only Post Filling-Out Instructions
Brian - Windows 10, 64-Bit, Version 21H2, Build 19044
I neither need nor want to be appeased, but apprised. Inconvenient truth is preferable to convenient (for the liar) lies.
~ Brian Vogel