Hi everyone,
Just a couple of housekeeping issues from reading recent posts:
If you read a post on the group and want to pull out one peripheral aspect of it, that's fine, but please ensure the subject is relevant. People will read the subject, decide they're not interested, and miss content they may have been interested in because it actually wasn't about the subject at all.
One thread in particular has evolved several times, and started to get a bit snappy in parts - let's just let that one end please. As well as that, at some point it ended up being marked as spam by someone's email service. It has ever been an issue with email services that group messages (to any group) sometimes end up in spam. I know myself sometimes I tell it that isn't spam and sometimes I just ignore it. At the very least, if you are going to reply to the message, please mark it as not spam and check it has removed the label from the subject, otherwise even if you reply IS related to the topic, it will often get split off into a different thread.
And finally on issues, I saw a comment recently saying that someone had reported something here and they hoped it was being looked into. That is not the purpose of the group, and developers do not necessarily monitor the group (even though I know we have a few in here, both NV Access staff and community developers). If you have a clear idea of a bug in NVDA or something which isn't working, OR an idea for a cool new feature, please ensure it is reported on GitHub. That is what it is for:
https://github.com/nvaccess/nvda/issues
If you are encountering something and aren't sure if it's a bug or if you just need to learn how to use a feature, then please do ask here. Once one or two others confirm that yes that's how it works - if that's not how you WANT it to work, then please create a GitHub issue. Our next In-Process will be out in a few days and I'm going to write a new guide to creating issues with the updated template in that.
And finally, please try to refrain from degenerating conversations into disagreements - Are there things NVDA could do better? Absolutely - please see previous point about issues. Are there things you have a steadfast and unchangeable view about? Fantastic! Someone else has the opposite view. Please don't argue about it. Do you love synthesizer X? That's great. I can't stand it myself, I love synthesizer Y! And you know what, both are fine. Things like sluggishness are very arbitrary - Some things we all face (Yes things in Outlook, and complex spreadsheets in Excel, looking at both of you) - and some things work vastly differently from one PC to the next, or depending on what your setup is or how you have things setup. if you want to confirm how smoothly something works for different people before creating an issue, wonderful! - Every bit of knowledge helps when tracking down bugs - but the end goal in those situations should be to inform a GitHub issue.
But of course, conversations about all things NVDA are welcome. Do you want to just post to say you are using XYZ add-on and you love it? Please do! Developers love knowing their hard work is being appreciated. Did you just discover a more accessible way of doing something, or an NVDA keystroke you never knew existed? Please share it - others probably don't know how to do that either :)
Ok that's enough rambling from me - have a great day / night / evening / morning / as appropriate!
--
Quentin Christensen
Training and Support Manager
NV Access
