yes, the reporter should open a ticket and if desired, someone could wright an addon if the requested feature won't get in to nvda. In this case the devs could add a roadmap for wanted addons or something like that.
An example for this you'll find on the pidgin developer website. best regards Bernd Dorer Am 23.05.2013 15:28, schrieb Mesar Hameed:
To maximize organization and trackability, we should be using the nvda bug tracker for requests, end user does not know if what he is asking for is appModule globalPlugin or whatever. A particular addon request may not be interesting for an author today but maybe in two months time it might be, so if he goes to the ticket he can see the discussion up to that point, this is doable with mailing lists/mail archives, but is harder because its hard to keep strict subjects. We can probably ask Jamie to add addon/addonRequest as a component. if its against a particular addon bitbucket allows for issues, if the person experiences the problem is not able to use bitbucket then any of the addon authors can do that for him. Hopefully trying to follow this should produce less emails. thanks, Mesar On Thu 23/05/13,02:58, Joseph Lee wrote:Dear NVDA users and add-on writers: Would like to receive your comments on the following survey questions about add-on suggestion procedure: 1. For appModules, should a potential suggestion go through the following: a. The user would search NVDA ticket to see if an issue has been raised for the app in question. b. If there's no ticket, then the user should (if possible) ask the app developer to make the particular app accessible for NVDA and other screen readers. c. If that doesn't work, then post a ticket requesting support for this app. d. After getting some comments, if it is determined that an appModule is needed and if it cannot be added to sore NVDA code then, then suggest the add-on here so people can investigate and work on it. Is this a reasonable procedure? If not, please suggest alternate procedures that we can follow. 2. In case of global plugins: a. User would search tickets for the features he or she wants. b. If the feature is not there, suggest the idea here. c. If the community believes that it is something that should be added to core NVDA code, then create a ticket for this new idea. Is this a reasonable procedure? If not, please suggest alternates we can follow. Thanks. Looking forward to your comments. Cheers, Joseph ---------------------------------------------------------------- NVDA add-ons Central: A list for discussing NVDA add-ons To post a message, send an email to nvda-addons@xxxxxxxxxxxxx. To unsubscribe, send an email with the subject line of "unsubscribe" (without quotes) to nvda-addons-request@xxxxxxxxxxxxx. If you have questions for list moderators, please send a message to nvda-addons-moderators@xxxxxxxxxxxxx. Community addons can be found here: http://addons.nvda-project.org---------------------------------------------------------------- NVDA add-ons Central: A list for discussing NVDA add-ons To post a message, send an email to nvda-addons@xxxxxxxxxxxxx. To unsubscribe, send an email with the subject line of "unsubscribe" (without quotes) to nvda-addons-request@xxxxxxxxxxxxx. If you have questions for list moderators, please send a message to nvda-addons-moderators@xxxxxxxxxxxxx. Community addons can be found here: http://addons.nvda-project.org
---------------------------------------------------------------- NVDA add-ons Central: A list for discussing NVDA add-ons To post a message, send an email to nvda-addons@xxxxxxxxxxxxx. To unsubscribe, send an email with the subject line of "unsubscribe" (without quotes) to nvda-addons-request@xxxxxxxxxxxxx. If you have questions for list moderators, please send a message to nvda-addons-moderators@xxxxxxxxxxxxx. Community addons can be found here: http://addons.nvda-project.org
