[nvda-addons] Survey: add-on suggestion procedure
- From: Joseph Lee <joseph.lee22590@xxxxxxxxx>
- To: nvda-addons@xxxxxxxxxxxxx
- Date: Thu, 23 May 2013 02:58:11 -0700
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
Other related posts: