Joseph:
We now have addon template and addon wizard. What should be done with the
wizard to make it easier to use if some want it?
On Tue, Mar 28, 2017 at 5:21 AM, Noelia <nrm1977@xxxxxxxxx> wrote:
Hi, the todo repo, which includes the add-ons guidelines, is available at
https://github.com/nvdaaddons/todo
Thanks.
2017-03-28 7:45 GMT+02:00, Noelia <nrm1977@xxxxxxxxx>:
Hi, for consistency, to use just GitHub when possible, I can move also----------------------------------------------------------------
the add-on guidelines.
I will do this later or tomorrow if none do it before.
Cheers.
El 28/03/2017 a las 4:49, Joseph Lee escribió:
Hi everyone,
To allow better visibility and unify our development process with NV
Access, the community add-ons template repo address has changed. The new
address is:
https://github.com/nvdaaddons/addontemplate
The former repo at Bitbucket will be maintained (no more new commits)
until later in 2017. I will give you sixty days notice before taking
Bitbucket version offline.
Also, a gentle reminder: the NVDA Add-ons organization at GitHub is
staffed by leaders of the add-ons community and is intended to serve as
a collection of repos used by majority of add-ons, such as add-on
template, development documentation, add-on wizard and what not. Thus,
please don’t use the organization as a venue for hosting your own
add-ons - these should live in your repositories, not with the
organization. Speaking of development docs, the Bitbucket version of the
devDocs repo will be moving to the GitHub organization before end of
spring (end of May at the latest), and I will update the add-on dev
guide to reflect features added and changed in recent NVDA releases.
Thank you.
Cheers,
Joseph
NVDA add-ons: A list to discuss add-on code enhancements and for reporting
bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
To change your list settings/unsubscribe: //www.freelists.org/list/
nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
