suggestion: a workflow to auto push add ons to a compatible state if requirements are met.

[marrie]

Is your feature request related to a problem? Please describe.

I would like to see a way for add on developers to go through a workflow causing their add ons to be compatible with nvda 2024.x and beyond

Describe the solution you'd like

When an add on developer submits what ever files are needed, a workflow would run to auto deamthe add on compatable else get reouted to a human as a fallback or fault path.

Describe alternatives you've considered

We could vet all of the add ons however human time and human resources would be waisted.

Additional context

n/a.

[josephsl]

Hi,

I see. Three things:

1. If add-on development/submission flow is involved, this should be submitted to add-on datastore repository (nvaccess/addon-datastore).
2. Can you give us examples of add-ons that could benefit from the compatibility workflow?
3. Declaring add-ons compatible requires willingness by authors and the community to validate compatibility claims unless automated compatibility issue detectors ars introduced on add-on store.

Thanks.

[marrie]

One example is the "web cam helper" I'm not sure if that is now dead, however if the author wants to make it compatible and does so by what ever means they need to do so, a workflow or if not a workflow an approval process could be kicked off to do so which could go through several levels until a final manager or coder deems it compatible and pushes it to the add on store.

[ChrisDuffley]

ObjPad is another one of those where, after testing, a workflow process could have easily been used as all I needed to change at that time was the last tested version. While in this particular case I didn't mind doing it manually I still agree with a process like this, however I do realize that this can be a lot of work especially since it would probably need to compare code to conventional syntax from other generalized programs as well as NVDA's source before even considering it compatible.