Proposed revisions to add-on store user guide subchapter#14966
Merged
Conversation
added 18 commits
June 5, 2023 21:55
… noted view changing via arrow keys.
…e first one to "Filtering for enabled or disabled add-ons".
…uctory section, explaining enabled/disabled states.
…. Moved explanations before usage instructions.
…uctions on how to reach the search field.
…isplay name, publisher and description.", because there are no instructions.
…", because that has been used to describe NV Access accepting add-ons into the store, by some members in the community, and I wanted to make clear that they are not "vetted" in any way.
…ince the cases are specific.
…able all add-ons.
seanbudd
reviewed
Jun 6, 2023
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
…red by display name, publisher and description.", because there are no instructions.' This reverts commit a53058b.
… and wording of gesture assignment suggestion.
seanbudd
reviewed
Jun 6, 2023
Co-authored-by: Sean Budd <seanbudd123@gmail.com>
…y display name, publisher and description.", per review.
seanbudd
approved these changes
Jun 6, 2023
Contributor
|
@seanbudd, by instance the Vocalizer driver add-ons are free. Tiflotecnia, Lda. |
Member
|
@ruifontes - yes. In that case, the add-on is free, but you are paying for a separate component. |
Collaborator
Author
|
@seanbudd wrote:
@ruifontes - yes. In that case, the add-on is free, but you are paying for a separate component.
NV Access just has no plans to support payments on the add-on store platform at this stage.
That confusion and situation, was exactly why I wrote the original version in
the way that I did, that you thought was too complex.
Not saying I disagree with the changes that we made, just that Rui's situation
was what I had in mind when saying that the vast majority were free.
Is an add-on really free, if you can download and install it, but it doesn't do
anything unless you pay for the commercial portion with which it interfaces? I
don't know the "user level" answer to that, though obviously the exact
technical answer is "yes".
|
Member
|
@XLTechie maybe an added sentence could help. "Some free add-ons require a purchase of external software to work, such as commercial synthesizers." |
Contributor
Collaborator
Author
|
@seanbudd wrote:
@XLTechie maybe an added sentence could help.
"Some free add-ons require a purchase of external software to work, such as commercial synthesizers."
I like that.
Can we have a policy requirement in the add-on store docs, that if that is the
case it will be clearly stated in the description?
E.g. "If your add-on requires a purchase of commercial components (such as
drivers) in order to function, this must be clearly stated in the manifest
description."
|
Member
|
Could you raise that suggestion as a separate issue? I think it's worth discussing further |
seanbudd
pushed a commit
that referenced
this pull request
Jun 9, 2023
…of free add-ons with paid components (#14982) Consideration of the language to use in the User Guide, when describing all add-ons as free in the store, while certain add-ons require the purchase of components or licenses in order to do anything. Description of user facing changes Revised language. Description of development approach Edited the language to be more in line with the comments in #14966. It may still not be as desired, but this provides a context to revise it in.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: this was originally presented in PR #14961
Link to issue number:
Part of #13985
Summary of the issue:
After reading the proposed add-on store user guide sections, I thought they could be more user friendly. The current form appeared to assume more knowledge than the user may have.
Description of user facing changes
The following summarizes the changes I made to each section.
Add-on Store:
Browsing add-ons:
Add-on list views:
Include incompatible add-ons:
This heading was duplicated.
Changed the first one to "Filtering for enabled or disabled add-ons".
Filtering for enabled or disabled add-ons:
Wrote a substantive introductory section, explaining enabled/disabled states.
Include incompatible add-ons:
Minor grammar.
Filter add-ons by channel:
Search add-ons:
Add-ons can be filtered by display name, publisher and description.", because there are no instructions on how to do that. Expect to add back in later, after that part can be more easily explained.Add-on actions:
Made the instructions more complete.
Installing add-ons:
Removing Add-ons:
Minor word change to avoid proximate word repetition.
Disabling and Enabling Add-ons:
Changed "a status" to "the status", since the cases are specific.
Incompatible Add-ons:
Description of development approach
Tried to read as a less technical user.
Testing strategy:
Preferred review from @Qchristensen
Known issues with pull request:
Change log entries:
Code Review Checklist: