Add-on dev and review processes: now public, edits in progress
As I promised a few days ago, the add-on dev and review processes document is now available for public consumption:
Also, the document has been linked to from the community add-ons index page.
Please provide suggestions and edits for the processes document to make it friendly toward beginners.
Hi, but this has been always for public consumption. The onlytoggle quoted messageShow quoted text
meningful change that I see in the provided link is that the recently
published code of conduct is mentioned.
I think this process should be clarified or followed more exhaustively, since:
1. Addons following continuous releases may not be reviewed properly
if code is too large.
2. New versions posted on the website may or not be reviewed.
I think this kind of issues may be caused sfor some factors, for example:
a. We don't use a checklist for review on GitHub or other platform
where results are registered and available for public consumption as
done in pull request. This is a super hight traffic list and it's not
easy to search results or see them.
b. Just three persons, one active (Joseph) can now post add-ons on the website.
c. Addons review is a superhard work that requires lot of time and
there are not many reviewers.
For these reasons I hope that NV Access, as promised, can work on the
add-on store or, if not possible, another option is that all us can
post add-ons in a store, like done in other projects that don't
Personally, I would prefer that my addons could be accepted, or some
of them, after a review process to ensure more quality. But I think
that if the process has important lacks like the mentioned ones, it
may not be so fair for everybody.
Fopr example, I'm thinking on an addon posted while some people noted
that a command was in conflict (Zoom add-on), to explain my opinion
with a real example. I think that a checklist on GitHub could help in
2020-10-18 0:06 GMT+02:00, Joseph Lee <firstname.lastname@example.org>:
Coming back to this...
Some of you may have noticed that the processes document has been rewritten. Please provide feedback.
I've been interested in this document before.
The current version of the document fairly clear and detailed describes the process of community approval of add-ons.
I'm very grateful to you and the community for publishing it on the official website.
Good luck to all!