This task involves the work of learning what experienced volunteers (patrollers/reviewers, specifically) think of the end-to-end experience (read: in-edit UX/UI, post-edit tagging, community configuration, etc.) the Editing Team is proposing for Paste Check.
More at mw:Edit check/Paste Check.
Learning objectives
Patrollers/Reviewers
- In-edit guidance: what do you think of the language and link we are thinking to include within the user experience? Might there be adjustments that you think could help better align the edits newcomers make with WP:COPYVIO (and related policies)?
- Community configuration: what do you think about how the team is proposing for Paste Check to be configured by default? Might you think different defaults ought to be set at your wiki? Might there be additional aspects of the experience that you think would be valuable for volunteers to be able to configure?
- Tagging: to start, edits in which ≥1 Paste Check is shown will be tagged with editcheck-paste-shown.
Newcomers
@bmartinezcalvo is leading the work of learning how newcomers experience the proposed UI/UX in T400622.
References
This section contains the information I think Product Ambassadors will need to facilitate converersations with patrollers/reviewers about the questions listed in hte === Learning objectives section above.//
In-edit guidance
Volunteers can review the proposed user experience in two says:
- Viewing this diagram of the proposed experience:
- Trying the proposed experience for themselves by:
- Visiting: https://en.wikipedia.beta.wmcloud.org/w/index.php?title=Cats&veaction=edit&ecenable=2
- Pasting ≥50 characters of text from an external source (e.g. a news site)
Community configuration
To start, the team is proposing (T399973) that Paste Check be configured and configurable in the following ways:
| Name | Description | Default |
|---|---|---|
| Account | Specify which account state Paste Check should apply to. Valid values are "loggedin", "loggedout", false. The default false results in the edit check applying to all users. | false |
| Edit Count | Specify a threshold for the number of changes at which Paste Check is activated. The default 100 means that Paste Check will only be shown to users with 100 edits or fewer. If this value is not defined, the default value is used. The number of edits is based on user edit count, edits from all namespaces are taken into account. | 100 |
| ignoreSections | An array of section titles, which will be compared case-insensitively to headings. If a heading matches an item in this array, all content within that section will be ignored for Paste Check. Each section title has to be between ", separated by a ,: ["External links", "Unsupported claims", "Discussion"]. | [] |
| Lead section | A boolean. If true, the content of the lead section will be ignored for Paste Check. A lead section is defined as content in an article with at least one heading that precedes the first heading. | false |
| Namespace | Specify what namespace(s) Paste Check has the potential to be activated within | TBD |
| Paste sources | Specify what sources will NOT cause Paste Check to active. E.g. Google Docs, Microsoft Office, other visual editor edit sessions, LibreOffice, etc. | TBD |
Tagging
To start, edits in which ≥1 Paste Check is shown will be tagged with editcheck-paste-shown.
The team, in partnership with volunteers, is thinking of expanding the set of tags available related to pasted content. E.g. T402465: Enable volunteers to identify published edits that might include pasted content.//
Wikis
To start, we're going to start by seeking feedback from volunteers that align with the communities Product Ambassadors are most knowledgable about/experienced with:
- Arabic
- English
Spanish- French
Done
- Feedback is documented
- A summary of the feedback is published on mediawiki.org