NVAccess and the slow Erosion of trust: I still believe that NVDA is the best available screen reader, and I still donate monthly.
-
@NVAccess @cachondo @prism The hate isn’t the service itself. It’s that the results are being displayed in the store. I believe that this is false reassurance, that makes everyone less secure just by existing. Best case, it will always return nothing, because no attacker would upload a virus directly to the store; they’ll have their addon download the virus days later, once it’s gotten some installs. Worst case, it makes someone think “Oh, NVDA virus scans its addons. So they’re fine.” Given the best case is nothing happens, and the worst case is someone is less secure, why do it? What problem is NVAccess trying to solve?
@fastfinge @cachondo @prism What do you propose? At the end of the day, add-ons are potentially a risk & I think we are clear in warning users about that. If a bad add-on has to download code days later to avoid detection, at least we've made it harder for them. The add-on community itself keeps an eye on add-ons & would hopefully quite quickly alert us to any issue such as this. The alternative would be extremely tightly restricting what add-ons could do - maybe to Braille drivers & synths?
-
@fastfinge @cachondo @prism What do you propose? At the end of the day, add-ons are potentially a risk & I think we are clear in warning users about that. If a bad add-on has to download code days later to avoid detection, at least we've made it harder for them. The add-on community itself keeps an eye on add-ons & would hopefully quite quickly alert us to any issue such as this. The alternative would be extremely tightly restricting what add-ons could do - maybe to Braille drivers & synths?
@NVAccess @cachondo @prism Well, I would first propose not doing something “because the service exists and we can”. This was the kind of thinking I tried, and seem to have failed, to hilight in the article. Next, I would propose not getting stuck in an either or mindset. The duality of “we do nothing” or “we restrict all addons forever” is a false one.What about tracking reputation of addon authors and making sure that, at least, NV Access can guarantee that the author of an addon is who they say they are. Then making it extremely clear to users who they’re trusting and how much trust they’re handing over. What about having a set of “reviewed addons” and then a set of “unreviewed addons” and listing them in different places, with different levels of warning, and different corporate controls? What about some sort of sandboxing, and prompting the user “Do you want to allow this addon to X?” Where X is dangerous things like download and execute a third party program, read and write files outside of the addon directory, and so on. There are all sorts of possible solutions, some easier, and some harder, that would actually do something other than “Maybe inconvenience an attacker who knows nothing about NVDA Store security someday”. -
@NVAccess @cachondo @prism Well, I would first propose not doing something “because the service exists and we can”. This was the kind of thinking I tried, and seem to have failed, to hilight in the article. Next, I would propose not getting stuck in an either or mindset. The duality of “we do nothing” or “we restrict all addons forever” is a false one.What about tracking reputation of addon authors and making sure that, at least, NV Access can guarantee that the author of an addon is who they say they are. Then making it extremely clear to users who they’re trusting and how much trust they’re handing over. What about having a set of “reviewed addons” and then a set of “unreviewed addons” and listing them in different places, with different levels of warning, and different corporate controls? What about some sort of sandboxing, and prompting the user “Do you want to allow this addon to X?” Where X is dangerous things like download and execute a third party program, read and write files outside of the addon directory, and so on. There are all sorts of possible solutions, some easier, and some harder, that would actually do something other than “Maybe inconvenience an attacker who knows nothing about NVDA Store security someday”.@NVAccess @cachondo @prism Second reply to publicly call myself out for doing exactly the thing I’m annoyed about. I just proposed a raft of solutions without taking the time to fully understand the problem I’m solving for. Is the security problem:
* NVDA needs to work with addons in sensitive enterprise environments
* users need to be able to confidently install addons from the addon store without worrying
* users need to be able to install random addons from the internet with at least some safety
* security people need to be able to audit what an addon is doing
* something else
* all of the above
The best solution is going to depend on what the problem is, and what the available resources are for solving it.I shouldn’t have offered any solutions at all without understanding the shape of the problem. Because otherwise we’re just doing things because we feel like things should be done. Leading me to another question: does NVAccess clearly define what its problems are before it starts planning solutions to them? Or do planning and roadmaps start from the solution, rather than the problem to be solved? Because starting from the solution leads to decisions like scanning addons with an antivirus because it exists and you can. -
Ok just to satisfy you that it isn't only my time you've taken up this morning, but our other staff who also tried to work through your post, here is a comment from one of our developers:
Also I don't understand why he thinks this stuff was not discussed.
https://github.com/nvaccess/nvda/discussions/19462
https://github.com/nvaccess/nvda/discussions/19807
https://github.com/nvaccess/nvda/discussions/14912
https://github.com/nvaccess/nvda/discussions/16304and a lot of the discussion can be found from the issues/PRs linked in the change log
@NVAccess @cachondo @prism And let's get into it:
* NVDA Magnifier available for early testing and feedback: This presents a fait accompli. It doesn't answer questions like "Why did NV Access decide to do this? Why now? Why part of NVDA and not a separate app?" Yes, I realize someone else is doing the initial work. But NV Access still needs to review it, merge it, maintain it, and so on. Just because someone does a thing doesn't mean it's in the project scope. I've refused fully formed pull requests for being out of scope. I'm sure NV Access has, too.
* AI Image descriptions progress: once again, discussion of a thing that's already happening. Not a discussion of why it's happening, or why it was done as part of core and not an addon, and no record of the reasoning and discussion behind the decision. This answers none of the questions I asked.
* Add-on store discussion: this, and the pr linked from it, get way closer to the sort of thing I'm looking for, and the sort of thing I saw all the time from NVAccess in the 2010's and early 2020's, but see much less of now. We get some insight into the thinking. Though we still don't get insight into why NVDA wanted to control the source of addons, and not leave it to the Spanish community, or discussion of the proes and cons of changing the review process for addon developers and how that decision was achieved.
* [Project] Convert NVDA to 64 bit #16304: And right here, we see the user story "Create a 32bit backwards compatible API for synth drivers and braille displays". With a five day final estimate. What happened here? Is this still happening? I did try to find out before I wrote anything at all. It remained unclear. So I'm still in a state where NV Access said a thing was going to happen, the thing did not happen, and I can't tell why or if it will happen later or never. -
@NVAccess @cachondo @prism And let's get into it:
* NVDA Magnifier available for early testing and feedback: This presents a fait accompli. It doesn't answer questions like "Why did NV Access decide to do this? Why now? Why part of NVDA and not a separate app?" Yes, I realize someone else is doing the initial work. But NV Access still needs to review it, merge it, maintain it, and so on. Just because someone does a thing doesn't mean it's in the project scope. I've refused fully formed pull requests for being out of scope. I'm sure NV Access has, too.
* AI Image descriptions progress: once again, discussion of a thing that's already happening. Not a discussion of why it's happening, or why it was done as part of core and not an addon, and no record of the reasoning and discussion behind the decision. This answers none of the questions I asked.
* Add-on store discussion: this, and the pr linked from it, get way closer to the sort of thing I'm looking for, and the sort of thing I saw all the time from NVAccess in the 2010's and early 2020's, but see much less of now. We get some insight into the thinking. Though we still don't get insight into why NVDA wanted to control the source of addons, and not leave it to the Spanish community, or discussion of the proes and cons of changing the review process for addon developers and how that decision was achieved.
* [Project] Convert NVDA to 64 bit #16304: And right here, we see the user story "Create a 32bit backwards compatible API for synth drivers and braille displays". With a five day final estimate. What happened here? Is this still happening? I did try to find out before I wrote anything at all. It remained unclear. So I'm still in a state where NV Access said a thing was going to happen, the thing did not happen, and I can't tell why or if it will happen later or never.@fastfinge @cachondo @NVAccess @prism this is very clearly an emotional conversation where both parties are wrong.
Samuel is a confused user who wrote what reads like a frustrated takedown piece, having hit a straw that broke the camel’s back moment in perceived lack of transparency.
NVAcess doesn’t have a public relations person, but its account that relates to the public is doing that job in a defensive stance.
You guys should kiss and make up.
You’re also kind of both right. Let’s look at the magnifier, since I consider myself an expert user of Windows Magnifier and ZoomIt:
There was no back room decision, it’s all very transparent. Here’s the GitHub issue where it was discussed:
Allow Windows Magnifier to follow NVDA virtual cursor · Issue #12539 · nvaccess/nvda
Is your feature request related to a problem? Please describe. As a visually impaired person, I am using NVDA in conjunction with Windows Magnifier. That works quite smoothly in applications such as Windows Explorer or text editors, sinc...
GitHub (github.com)
A low vision user reported that Windows Magnifier was not following the NVDA virtual cursor.
My instant thought? No big deal, Magnifier can already follow keyboard focus, just have an option to move to mouse to the virtual cursor all the time and leverage the existing tool.
There was a discussion on the Windows Magnifier to Narrator private APIs and then the decision was make to add a magnifier solution to NVDA.
About a year later an add-on author said they’d addressed this issue by moving the mouse cursor and only had a pending problem with tabbing. They were advised the team was already working on a magnifier, but that they could open a PR for this issue.
The issue was ultimately closed by the PR that introduced the magnifier implementation.
This was discussed, decided and implemented completely in the open, and prioritized in a very surprising way.
“I can’t keep my pants up with this belt.”
“We’ll make you a new pair of pants.”
“I have this hole punch I used to tighten my belt.”
“We’re already making the new pants.”There are valid criticisms to make here, but they had their time and place: that issue.
I know a lot of people have accessibility and other issues with GitHub, but that is where this FOSS project is developed and that’s where enthusiastic community members should contribute. I also know there have been discussions about how to make that process more approachable for more people. That’s good, keep doing that.
Just my two cents. I hope this can put things into perspective for you guys and turn this to a more productive direction.
-
@fastfinge @cachondo @NVAccess @prism this is very clearly an emotional conversation where both parties are wrong.
Samuel is a confused user who wrote what reads like a frustrated takedown piece, having hit a straw that broke the camel’s back moment in perceived lack of transparency.
NVAcess doesn’t have a public relations person, but its account that relates to the public is doing that job in a defensive stance.
You guys should kiss and make up.
You’re also kind of both right. Let’s look at the magnifier, since I consider myself an expert user of Windows Magnifier and ZoomIt:
There was no back room decision, it’s all very transparent. Here’s the GitHub issue where it was discussed:
Allow Windows Magnifier to follow NVDA virtual cursor · Issue #12539 · nvaccess/nvda
Is your feature request related to a problem? Please describe. As a visually impaired person, I am using NVDA in conjunction with Windows Magnifier. That works quite smoothly in applications such as Windows Explorer or text editors, sinc...
GitHub (github.com)
A low vision user reported that Windows Magnifier was not following the NVDA virtual cursor.
My instant thought? No big deal, Magnifier can already follow keyboard focus, just have an option to move to mouse to the virtual cursor all the time and leverage the existing tool.
There was a discussion on the Windows Magnifier to Narrator private APIs and then the decision was make to add a magnifier solution to NVDA.
About a year later an add-on author said they’d addressed this issue by moving the mouse cursor and only had a pending problem with tabbing. They were advised the team was already working on a magnifier, but that they could open a PR for this issue.
The issue was ultimately closed by the PR that introduced the magnifier implementation.
This was discussed, decided and implemented completely in the open, and prioritized in a very surprising way.
“I can’t keep my pants up with this belt.”
“We’ll make you a new pair of pants.”
“I have this hole punch I used to tighten my belt.”
“We’re already making the new pants.”There are valid criticisms to make here, but they had their time and place: that issue.
I know a lot of people have accessibility and other issues with GitHub, but that is where this FOSS project is developed and that’s where enthusiastic community members should contribute. I also know there have been discussions about how to make that process more approachable for more people. That’s good, keep doing that.
Just my two cents. I hope this can put things into perspective for you guys and turn this to a more productive direction.
@MostlyBlindGamer @fastfinge @cachondo @prism Always happy to acknowledge where I can do better, and I must admit, logging on to a flood of messages and a 6,000+ word essay attacking us, most of which was not accurate, it was difficult to know where to start. In any case, I definitely don't have any animosity to Sam. Indeed, I appreciate Sam's passion and enthusiasm. Albeit it was a bit .... overwhelming all at once
-
@MostlyBlindGamer @fastfinge @cachondo @prism Always happy to acknowledge where I can do better, and I must admit, logging on to a flood of messages and a 6,000+ word essay attacking us, most of which was not accurate, it was difficult to know where to start. In any case, I definitely don't have any animosity to Sam. Indeed, I appreciate Sam's passion and enthusiasm. Albeit it was a bit .... overwhelming all at once
@NVAccess @MostlyBlindGamer @cachondo @prism I’ve been using and watching NVDA since back in the source forge days. And the change in the decision making still feels obvious to me. The magnifier issue unearthed adds to the point I’m making, not detracts from it. There was no central strategy thought behind it. It just sort of happened. It’s also alarming that any public criticism, no matter how frequently couched in my love and respect for NVDA, is an “attack” that must be “defended” against. I’ll sign off this thread by saying that framing criticism as a battle with winners and losers makes healthy and productive discourse impossible. -
R relay@relay.infosec.exchange shared this topic
-
@NVAccess @MostlyBlindGamer @cachondo @prism I’ve been using and watching NVDA since back in the source forge days. And the change in the decision making still feels obvious to me. The magnifier issue unearthed adds to the point I’m making, not detracts from it. There was no central strategy thought behind it. It just sort of happened. It’s also alarming that any public criticism, no matter how frequently couched in my love and respect for NVDA, is an “attack” that must be “defended” against. I’ll sign off this thread by saying that framing criticism as a battle with winners and losers makes healthy and productive discourse impossible.
@fastfinge Sam, I respect you a lot, but you are misrepresenting the situation. You say decisions were made with no public discussion, then when people point out the very public discussion that happened, you call it an attack. No one attacked you. No one said you have to email anyone to get a response, or take the discussion private. You made that up, like the rest of your six thousand word treatous railing against the only free and open source screenreader in the known universe, which boils down to "things just aint how they use to be."
NVAccess can't say this, so I will: if you don't like the decisions made, you're welcome to use something else, or create it.
@cachondo @NVAccess @MostlyBlindGamer -
@fastfinge Sam, I respect you a lot, but you are misrepresenting the situation. You say decisions were made with no public discussion, then when people point out the very public discussion that happened, you call it an attack. No one attacked you. No one said you have to email anyone to get a response, or take the discussion private. You made that up, like the rest of your six thousand word treatous railing against the only free and open source screenreader in the known universe, which boils down to "things just aint how they use to be."
NVAccess can't say this, so I will: if you don't like the decisions made, you're welcome to use something else, or create it.
@cachondo @NVAccess @MostlyBlindGamer@prism @cachondo @NVAccess @MostlyBlindGamer Huh? NVAccess repeatedly complained that I was attacking them. As have you. That was my complaint. I never framed anything as an attack. Everyone else put on that framing, and it immediately killed all useful discussion. And that was my complaint. The fact that folks are so defensive about NVDA that you can’t have this discussion without putting words in my mouth means the entire thread is useless. Because this is a battle that you have to win by defeating me. So nothing can or will ever change, and nothing useful will happen, until that framing (that I never once placed or agreed to) is gone. -
@fastfinge Sam, I respect you a lot, but you are misrepresenting the situation. You say decisions were made with no public discussion, then when people point out the very public discussion that happened, you call it an attack. No one attacked you. No one said you have to email anyone to get a response, or take the discussion private. You made that up, like the rest of your six thousand word treatous railing against the only free and open source screenreader in the known universe, which boils down to "things just aint how they use to be."
NVAccess can't say this, so I will: if you don't like the decisions made, you're welcome to use something else, or create it.
@cachondo @NVAccess @MostlyBlindGamer@prism @cachondo @NVAccess @MostlyBlindGamer I’m also unsure how opening an article stating that NVDA is still the best screen reader available, before criticizing the way it seems to make recent decisions, then closing with a plea for people to donate more money to it, counts as “railing against it”. -
@prism @cachondo @NVAccess @MostlyBlindGamer Huh? NVAccess repeatedly complained that I was attacking them. As have you. That was my complaint. I never framed anything as an attack. Everyone else put on that framing, and it immediately killed all useful discussion. And that was my complaint. The fact that folks are so defensive about NVDA that you can’t have this discussion without putting words in my mouth means the entire thread is useless. Because this is a battle that you have to win by defeating me. So nothing can or will ever change, and nothing useful will happen, until that framing (that I never once placed or agreed to) is gone.
@fastfinge Again, the reason no discussion is happening is because you keep circling back to "no discussion can happen" after being pointed you to the discussion that happened, and being invited to ingage further on said discussions. You don't like that the magnifier is in core? Okay. I don't like that the magnifier is in core. So leave an issue comment. A response will be forethcoming. If the nature of that response is unsatisfactory, then you write the blog post.
I don't think you are being intentionally disingenuous, I'm sorry I said you made up the stuff in your post. I should not have. But imagine if someone, out of nowhere, wrote up a huge essay about something you did a year and a half ago, didn't ask you about it first, and signed off with "ultimately, the problem is trust." You would feel attacked by that, especially if it was your livelyhood. An open letter format comes off very aggressive to me, as an observer. I'm clearly not the only one who took it that way.
-
@fastfinge Again, the reason no discussion is happening is because you keep circling back to "no discussion can happen" after being pointed you to the discussion that happened, and being invited to ingage further on said discussions. You don't like that the magnifier is in core? Okay. I don't like that the magnifier is in core. So leave an issue comment. A response will be forethcoming. If the nature of that response is unsatisfactory, then you write the blog post.
I don't think you are being intentionally disingenuous, I'm sorry I said you made up the stuff in your post. I should not have. But imagine if someone, out of nowhere, wrote up a huge essay about something you did a year and a half ago, didn't ask you about it first, and signed off with "ultimately, the problem is trust." You would feel attacked by that, especially if it was your livelyhood. An open letter format comes off very aggressive to me, as an observer. I'm clearly not the only one who took it that way.
@prism @cachondo @NVAccess @MostlyBlindGamer And doing so misses the point entirely. Past decisions were made. The work is done, now. As I stated both in the introduction and the conclusion, the thing that concerns me is the pattern of decision making without strategic discussion I couldn’t find. When I point it out, I get pointed to implementation level discussion, IE the “how” and not the “why” or the “should we”. Re-litigating past decisions gets no closer to being more strategic about future decisions. There purpose is, once again, as I said in the article, to demonstrate the pattern I’ve noticed. -
@fastfinge Again, the reason no discussion is happening is because you keep circling back to "no discussion can happen" after being pointed you to the discussion that happened, and being invited to ingage further on said discussions. You don't like that the magnifier is in core? Okay. I don't like that the magnifier is in core. So leave an issue comment. A response will be forethcoming. If the nature of that response is unsatisfactory, then you write the blog post.
I don't think you are being intentionally disingenuous, I'm sorry I said you made up the stuff in your post. I should not have. But imagine if someone, out of nowhere, wrote up a huge essay about something you did a year and a half ago, didn't ask you about it first, and signed off with "ultimately, the problem is trust." You would feel attacked by that, especially if it was your livelyhood. An open letter format comes off very aggressive to me, as an observer. I'm clearly not the only one who took it that way.
@prism @cachondo @NVAccess @MostlyBlindGamer A practical example, because you’re trying to understand. If I propose a feature request to add a full fledged email client into core, I do all the work myself, and I create the pull request, does it get merged? What I’m hearing is that maybe it does, because someone else did all the work. This is my understanding of how both screen mag and on device image descriptions got into core. If it doesn’t, and obviously it shouldn’t, I can’t find the strategic direction around questions like “What belongs in NVDA at all?” That would make stopping this work quick and easy. Without this strong overarching strategic discussion, the discussion I pointed out I wasn’t finding in my article, and that is not just a pull request for a feature or change with no discussion of “why do this” or “should this be done at all”, only “how should we do this” discussion that takes the other two questions as assumed, eventually everything gets into core. And making changes and fixes gets harder and harder. At some point (maybe years from now, but eventually) everything just grinds to a halt. -
@prism @cachondo @NVAccess @MostlyBlindGamer A practical example, because you’re trying to understand. If I propose a feature request to add a full fledged email client into core, I do all the work myself, and I create the pull request, does it get merged? What I’m hearing is that maybe it does, because someone else did all the work. This is my understanding of how both screen mag and on device image descriptions got into core. If it doesn’t, and obviously it shouldn’t, I can’t find the strategic direction around questions like “What belongs in NVDA at all?” That would make stopping this work quick and easy. Without this strong overarching strategic discussion, the discussion I pointed out I wasn’t finding in my article, and that is not just a pull request for a feature or change with no discussion of “why do this” or “should this be done at all”, only “how should we do this” discussion that takes the other two questions as assumed, eventually everything gets into core. And making changes and fixes gets harder and harder. At some point (maybe years from now, but eventually) everything just grinds to a halt.
@fastfinge The "magnifier" (which mostly extends the windows magnifier and then calls it, as I understand) got into core because people asked for it. Image descriptions were taken out of core, because people didn't like them. All of which happened in public.
I do take your point about it being hard to predict the outcome of decisions made about what is or isn't accepted. But there is also the roadmap, product vision, and contributor guide, which seems like a reasonable place to frame any future discussions on what should or should not go into core, which you are of course free to start whenever you feel the need. 1/2
-
@fastfinge The "magnifier" (which mostly extends the windows magnifier and then calls it, as I understand) got into core because people asked for it. Image descriptions were taken out of core, because people didn't like them. All of which happened in public.
I do take your point about it being hard to predict the outcome of decisions made about what is or isn't accepted. But there is also the roadmap, product vision, and contributor guide, which seems like a reasonable place to frame any future discussions on what should or should not go into core, which you are of course free to start whenever you feel the need. 1/2
@prism @cachondo @NVAccess @MostlyBlindGamer I read those, in the course of writing up a feature request for PGP signing of addons. Then I scrapped the feature, because I realized I have no idea what a feature request needs to go ahead, how priority is decided, etc. My fear was that it would happen if someone decided to code it, and not happen if nobody wanted to code it. And that’s just not how to build complicated things. So I decided it’d be better not to waste even more developer time by submitting the feature request at all and risking someone just does it and things get even more bogged down. -
@prism @cachondo @NVAccess @MostlyBlindGamer A practical example, because you’re trying to understand. If I propose a feature request to add a full fledged email client into core, I do all the work myself, and I create the pull request, does it get merged? What I’m hearing is that maybe it does, because someone else did all the work. This is my understanding of how both screen mag and on device image descriptions got into core. If it doesn’t, and obviously it shouldn’t, I can’t find the strategic direction around questions like “What belongs in NVDA at all?” That would make stopping this work quick and easy. Without this strong overarching strategic discussion, the discussion I pointed out I wasn’t finding in my article, and that is not just a pull request for a feature or change with no discussion of “why do this” or “should this be done at all”, only “how should we do this” discussion that takes the other two questions as assumed, eventually everything gets into core. And making changes and fixes gets harder and harder. At some point (maybe years from now, but eventually) everything just grinds to a halt.
@fastfinge How-ever, if I understand correctly, you want them to be more proactive about solicitting community feedback. Frankly there are pros and cons to this approach: it slows down development and leads to fiascos like when they tried adding a sound pack, everyone faffed around for months without settling on something they liked, and ultimately it got closed with no action taken. Maybe you liked that outcome because it's better suited for an add-on. In any case.
As I said earlier, public communications can be a job in itself. Considering the size of the team and the various tasks they have before them, what level of reach-out do you consider appropriate?
-
@fastfinge How-ever, if I understand correctly, you want them to be more proactive about solicitting community feedback. Frankly there are pros and cons to this approach: it slows down development and leads to fiascos like when they tried adding a sound pack, everyone faffed around for months without settling on something they liked, and ultimately it got closed with no action taken. Maybe you liked that outcome because it's better suited for an add-on. In any case.
As I said earlier, public communications can be a job in itself. Considering the size of the team and the various tasks they have before them, what level of reach-out do you consider appropriate?
@prism @cachondo @NVAccess @MostlyBlindGamer Hmm, no. I want them to be more proactive about strategic direction. Getting a feature or pull request, and deciding each time “does this belong in NVDA” is going to lead to problems. The questions like what should addons do? What should be in core? What should addons not do? Why is NVDA deciding to do what it’s doing this year? Should all be clearly understood by everyone. When the strategic direction is set, we can all make decisions about what to work on, what to request, etc, based on that direction. Without it, things just…kind of happen. And that’s not sustainable. -
@prism @cachondo @NVAccess @MostlyBlindGamer Hmm, no. I want them to be more proactive about strategic direction. Getting a feature or pull request, and deciding each time “does this belong in NVDA” is going to lead to problems. The questions like what should addons do? What should be in core? What should addons not do? Why is NVDA deciding to do what it’s doing this year? Should all be clearly understood by everyone. When the strategic direction is set, we can all make decisions about what to work on, what to request, etc, based on that direction. Without it, things just…kind of happen. And that’s not sustainable.@prism @cachondo @NVAccess @MostlyBlindGamer Another example of the lack in overall direction. NVDA seems to have no policy that I can find about AI generated code. But looking at the open pull requests, nobody has submitted any fully AI generated code. Waiting until it happens and then deciding is the kind of reactive stance that leads to bad, poorly thought out decisions. And this is strategic direction that needs to be provided by NV Access, not me, some random dude online.
-
@prism @cachondo @NVAccess @MostlyBlindGamer Hmm, no. I want them to be more proactive about strategic direction. Getting a feature or pull request, and deciding each time “does this belong in NVDA” is going to lead to problems. The questions like what should addons do? What should be in core? What should addons not do? Why is NVDA deciding to do what it’s doing this year? Should all be clearly understood by everyone. When the strategic direction is set, we can all make decisions about what to work on, what to request, etc, based on that direction. Without it, things just…kind of happen. And that’s not sustainable.
@fastfinge NVDA publishes in-process updates every month and a roadmap at least once a year, describing their plans for future work. In fact they just posted the most recent one this month https://www.nvaccess.org/post/nvda-roadmap/
-
@fastfinge NVDA publishes in-process updates every month and a roadmap at least once a year, describing their plans for future work. In fact they just posted the most recent one this month https://www.nvaccess.org/post/nvda-roadmap/
@prism @cachondo @NVAccess @MostlyBlindGamer Yes, I subscribe it and read every issue. And again, that documents how they’re doing the work, and the progress of that work. Not why it was decided to do that work at all. The soundpack thing is actually a good example. More community feedback is fine. But eventually, there needs to be a decider. Who can say “Doing X is most in line with NVDA’s mission, vision and strategy because of Y. So we’ve decided that we’re doing X.” I might disagree with either X or Y. But the reasoning is there. The strategy is there. Without that overall vision and strategy, what happened, happens. Everyone argues for months and nobody does anything. Or someone just decides and does something for reasons only clear to them, and outside of any framework or overall goal for the project.
