I've updated the task description to deal with the people who have never fiddled with their prefs.

In T270119#6730234, @ppelberg wrote:

NEXT STEP

• @Whatamidoing-WMF: can you please review the task description's "Setting defaults" section within the ===Requirements heading?

...this section describes an initial approach for how people at ar, cs and hu will experience the New Discussion Tool by default and I'd like to know whether anything about what's described is concerning to you.

The task description mentions radio buttons. I think a checkbox would be more normal.

For anyone who's interested, the all-time total is about 3,500 accounts right now. Many of these were new editors who have only used it once. (The overall attrition rate for new accounts is very high.)

The 2017WTE is not a Beta Feature on office.wiki. It's 'deployed' as a regular preference. The result is this:

More generally, T67191: BetaFeatures: Add a Notification for "A Beta Feature you have enabled has been updated" would solve this problem.

I think this is done.

I've posted the updated schedule at all of these wikis.

@ppelberg, I think this is {{done}}.

Is this vote easy enough to figure out?

If editors aren't asking for this right now, then I'd make the tag hidden. It can always be changed later if someone wants it.

This edit was made in the VisualEditor-MediaWiki-Mobile

There have been some changes, but the problem still exists.

• Partner wikis for the Reply tool: nlwiki, frwiki, arwiki, huwiki

For clarity: If the Reply tool is already available at your non-Wikipedia wiki (i.e., Meta-Wiki, MediaWiki.org, English Wikiversity), then it should continue to be available there.

Some related discussions:

"Outdent" doesn't do anything to the structure. It just draws a line, and the editor changes the structure manually (i.e., by not typing any colons).

They are indeed very similar. Perhaps this task should be marked resolved?

Another request for this, from the Polish Wikipedia.

I think that if you had CSS code that added a visual-but-not-real blank space in the editing boxes and/or on the page, that it would probably be popular with editors at many wikis.

This was suggested again at https://www.mediawiki.org/wiki/Topic:Vgnhu5y3r8yxipqr by @Arthur_Crbz

@ppelberg: Please let @matmarex know whether we can put English Wikiversity in this group as well. I'd rather have it go up as a Beta Feature than as a sitewide script.

Peter, I missed Santali earlier. I've just added it to the task description.

I have put this in User-notice (because it affects multiple wikis) and asked Dyolf to post to arwiki separately.

Will this solve the problem that User:Refiona describes at https://www.mediawiki.org/wiki/Topic:Vtf86rvpkhgl0jo0 ? First, only one category was visible; then, after putting all the categories in the correct order, none of them were visible in visual mode. That means that none of them could be removed from the visual editor.

I think that's everything, @patilise.

Grants for software projects are available from the Wikimedia Foundation. See https://meta.wikimedia.org/wiki/Grants:Project However, the process is not quick, and software grants often have other requirements that would make it even slower.

Update: Probably Tuesday, 22 September 2020. But that's "probably", not "definitely".

@Dyolf77_WMF, @Urbanecm_WMF, @Samat, @Tacsipacsi: Peter and I just talked about this, and we think that this might happen on Tuesday, 22 September 2020. This is our current best guess; we may be wrong.

Update: I asked @AntiCompositeNumber to extend the timeframe in https://signatures.toolforge.org/reports/en.wikipedia.org We're working with a rolling period of 90 days, which meant 1,618 editors with plain-fancy-sig late last week. I've sent directions to all of those people. We're hoping to find out what kind of response rate we get from MassMessages before trying to replicate that process at other wikis.