@Chaotic_Enby There is now some documentation about the general 'Best Practice' advice for writing a textmatch, which uses the specific example from here, at https://www.mediawiki.org/wiki/Edit_check/TextMatch#Regex_queries:~:text=When%20using -- I.e. order the alternatives from longest to shortest, and thus rewriting "enhanc(e|ed|es|ing)" into "enhanc(ed|es|e|ing)".

An Admin/IntAdmin from Italian Wikipedia has also requested user sandbox pages (plus Draft namespace), at https://www.mediawiki.org/wiki/Talk:VisualEditor/Suggestion_Mode#namespaces_configuration
I noted there, that user sandboxes are complicated because AFAIK there isn't much consistency between wikis (or even within wikis) regarding categories/templates used to mark "article sandboxes" as distinct from "random notes page as a user-subpage" where we probably don't want to display suggestions - e.g. Only 21 wikis currently seem to have a dedicated templates for Template:Draft article (Q19723431) - but perhaps that would be sufficient as a start?
@Wellverywell is there a standard template/category used in Ruwiki for article drafts within the User: namespace?

Is this a duplicate of T416430: Suggestions: Define the meaning and label for the Dismiss/Skip button?

Hmm, I was surprised by seeing this task title, as in the 2010 editor I'm accustomed to seeing these aspects formatted in a way that matches how they are rendered, e.g. [screenshot below]

@Michael Thanks for the catch,
Re: Who to ping - generally Sandister is the lead-editor these days, but there are a few backups people, so just mentioning Tech News within a comment (in a task tagged with user-notice) is usually sufficient/preferred.
Re: Timing - it's unfortunate that this is going to be announced the week after it launches, I.e. Gentle reminder to all, to consider the comms early on in the process. [Some people even recommend starting a project entirely, by writing the intended announcement text, and then working outwards from that!]
Re: current Draft - I recommend adding a link to the text (for the project page, which hopefully has a screenshot(s)), plus a short (phrase or sentence) addition to the first sentence to explain why this change is happening.

There's also a good idea from Femke at https://www.mediawiki.org/wiki/Talk:VisualEditor/Suggestion_Mode#Prompt_text_for_Add_a_reference -- Copying/Rephrasing slightly:

Often, when an editor finds a source for an uncited paragraph, it does not fully support the text. New editors often do not change the text to align with the citation they found.
Could the prompt that editors get in the Suggestion, include something like this?

• "Do not forget to update the text based on your new source"

I agree it would be very helpful to add this detail, as we really don't want newcomers to add references that aren't perfectly suitable. Alternative rephrasing ideas:
"[Please/Also] update the text based on the source you use."
"Make sure the article text is aligned with the source you add."

Related discussion/bug-report at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Watchlist_category_changes_not_being_shown

Posted announcement: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Discussion_Tools_usability_improvements_becoming_default

@LEvalyn Thank you! Yes, this is a very complicated piece of wording to get 'right' (in particular for the default version that goes to translatewiki), and we're planning (T429656) on asking a number of communities for feedback on ways to improve those strings of text before we finalize them, probably over the course of the next 2 weeks. Your feedback here (with the precise alternative-wording suggestions) is exactly the kind of thing we're hoping other editors will respond with.

@Chaotic_Enby Please do file a separate task, with some examples to describe the use-case(s) you are envisioning for this idea. Thanks!

@simon04 Just to check (I assume "yes"!), will these patches also work for
(A) Users (or wikis) with non-English language settings -- IIUC, this is already handled automagically.
(B) All other skins? -- I.e. Minerva, Monobook, Timeless, Vector (legacy); but also generic 3rd-party skins?
It might be good to add screenshots for those examples, to prove that the changes are suitable & tested for all easily-predictable situations.
P.s. Thank you immensely for working on this bug!

In T424606#11864899, @Esanders wrote:

This also gets into sentence splitting, as there could be a complete sentence before the one ending in a colon that requires a citation, e.g.

FedEx Corporation describes the sub-divisions of its business as "operating units" [citation needed]. The main operating units are:

Looks good to me.

Is this a duplicate of T428665: Broken section-anchors to TextMatch entries in Special:EditChecks?

In T422190#11998439, @Wellverywell wrote:

BTW, could we also add a check if a page has a "true" self-link, not fragment self-link -- like the ones that don't work and show in bold (except from those in navigation templates)? Should I file a separate task?

I think this is also semi-related to T95702: Be able to use the auto-cite tool to insert a citation template outside of a reference

@Aklapper Re: 1a.: Sounds reasonable, although I believe LibUp-bot is the only bot that ever creates tasks that show-up in this weekly summary. But I defer to your guidance.
Re: 1b. & 1c.: The 3 other tags you suggested would also be reasonable/helpful, yes please. But nothing beyond that. Context: We're just trying to auto-filter-out the regular things that we currently often have to manually filter-out (i.e. personal phab-board creations, gitlab account approvals). I checked the 3-month history of the 3 tags you suggested (e.g. LDAP-Access-Requests) and I do see a couple of tasks filed by volunteers-and-resolved-by-staff that it would've been helpful to auto-remove, but those are rare. -- We know that a manual review is always going to be needed; these requests are just to make it a bit quicker each week.
Re: 2. & 3. & 4.: Sounds good.
Re: us writing gerrit patches: Heck no! Especially for (4.), that's all well beyond my/Sandister's code-familiarity, and would take an impractically long time! [I learned how many years ago, and have forgotten everything since then.] Please could you/someone else help with this?

It looks like the example article's timeline has re-appeared since this June 4 edit. I don't know if that's a helpful clue or not. (I'd guess the original problem is something more back-end, than that.)

@STei-WMF LGTM.

@Mitte27 Ah, that makes sense, but... it also needs to work on Mobile sized screens, where there's a different layout.

TechNews Timing-wise: Is this the kind of change where either:

1. admins/editors will want to know ahead of time? (I.e. Is there any slim expectation of pushback, or further changes being needed?) -- I.e. Announce it in June 8th edition
2. or would it be better to wait until after the train so that when folks learn about it they can immediately start implementing it? (I.e. I assume the new version won't work until after next-Thursday, and therefore informing everyone on next-Monday might reduce the chances that anyone does anything 3 days later..). -- I.e. Announce it in June 15th edition.

[UPDATE: I misunderstood -- Ignore this comment! See the Wellverywell's reply.]

Thinking aloud... I believe I understand that the goal of the longer-wording that Russian Wikipedia wants to use here, is to inform any curious/confused people a little bit more about what exactly the "View suggestions" in this button is referring to.

1. One alternative: We could expand the default En.json wording from "View suggestions" to "View suggested edits". -- Perhaps that makes it sufficiently clearer?
2. Another alternative: We could add a "ⓘ" icon into the <editcheck-dialog-scroll-into-view> button, with a tooltip-message that contains some extended text to explain the feature a bit more (and/or a link to mw:Help:Suggestion_mode).

Noting: I see there's a recent edit to temporarily fix the localized string, which helps to explain the desired outcome:
https://translatewiki.net/wiki/Special:Translations?message=Editcheck-dialog-scroll-into-view&namespace=8 -- I.e.

• Desired string (machine transl.): View recommendations for improving the article
• Temp-fix string (machine transl.): View recommendations
• En.json version: View suggestions

I like the idea of making this message-area significantly modifiable in length like this,
but also recommend tweaking the qqq (https://translatewiki.net/wiki/MediaWiki:Editcheck-dialog-scroll-into-view/qqq) to include something about a limited-length (i.e. guidance for display & UX aspects).

Once this is ready for announcement in Tech News (after a few more followup actions to be completed, possibly for the upcoming edition), DTorsani will comment here. The draft for Tech News is:
[in "Updates for editors"]

• The user interface icon library will be updated later this week. Most of the ~300 icons have been slightly refined and ~30 new icons have been added. These changes improve the icons to make them more consistent and comprehensible, and provide more visual balance when they are used in groups. [ 1 ]

I wonder if this is similar/related to the old problems we had c.2013–2017? Cf. This and subtasks T58414: Get mail relay out of Yahoo! blacklist: apply to Yahoo for whitelisting bulk mail

Another related bug-report about this at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Bug_when_copying_code_from_another_wiki -- Copying for ease of access, + linebreaks + formatting for clearer distinction of the details:

The problem affects copying images between Wikipedias in Visual Editor.
It copies fine in VE initially (i.e. it renders normally after CTRL+C CTRL+V), but after save becomes corrupted.
Here is a diff for copying an image from pl wiki to en wiki, with error after save, and manual fix needed
(the software does not substitute File for local translations, does not recognize term File in other languages, and also adds an unnecessary link= parameter).

FTR, related comment and example:

• feedback-comment: https://www.mediawiki.org/wiki/Talk:VisualEditor/Suggestion_Mode/Feedback#addReference_on_MEMRI_at_enwiki
• Two examples in this section: https://en.wikipedia.org/wiki/MEMRI#Positive_reception -- (permalink)
• [added] feedback-comment: https://www.mediawiki.org/wiki/Talk:VisualEditor/Suggestion_Mode/Feedback#addReference_on_Cossack_raids_at_enwiki

@Escargot_rouge There's a related task for investigating if it's feasible to re-use the existing listings of AWB fixes (rather than duplicating them into TextMatch) at T423650: [Suggestion] Detect typo from existing lists. As DLynch notes in the comments there, yes, it does need to be checked on the performance/scaling issues regarding adding thousands of entries.

Agreed, fixed.

In T421189#11872580, @Esanders wrote:

Editing Engineering: create JSON pages basic json pages at zh.wiki and ko.wiki

Is this necessary? A null config should be valid (i.e. use all defaults), and I'm seeing suggestions on kowki if enabled by querystring. cc @Quiddity

@bd808 This might be relevant to your ideas.

Hi, you probably saw it already, but just in case: You might find this page and associated tool to be useful (for ideas, if not more!):

• https://www.mediawiki.org/wiki/Phabricator/Help/Task_Creation_URL
• https://phabulous.toolforge.org/

In T371425#11859374, @Tacsipacsi wrote:

In T371425#11859075, @Quiddity wrote:

E.g. Perhaps it could offer me a button to wrap a section in the appropriate <div ... if it sees my wplanguage user-preference is set to something different from the wiki default? [Assuming that is the desired practice!?!]

I’m not sure if it’s a good idea. Just the fact that my interface language is the same as the site language, doesn’t mean that I always write on that language. [...]

I think I'd also find something like this occasionally useful.