Page MenuHomePhabricator

Make partner wikis aware of `dtvisual=1` and v2.0 sequence and timing
Closed, ResolvedPublic

Description

This task is about making our partner wikis aware of the Reply tool's new visual mode which they can experiment with by appending the following text to any URL where the Reply tool is already available: dtvisual=1.

Announcement components

What the new features are

  • Writing and styling comments in a new visual mode
  • Send notifications to other editors; a username suggestion list will appear by typing @
  • Switch back and forth between source and visual editing modes

How people can try the new features
Append the following text to any URL where the Reply tool is already available: dtvisual=1.

What we are asking people to do
Try out the feature, report issues and ideas for improvement. We are specifically curious to hear what peoples' experiences are doing the following:

  • Ping another user using the tool's visual mode
  • Style the text they are writing (bold, italicize, computer code, etc.) using the tool's visual mode
  • Switching between the tool's visual and source modes and sharing any unexpected behavior
  • Making sure the diffs of comments posted with the tool's visual mode look as expected

What our plan is to make these features more readily available
Provided no issues come up during this initial testing period, add this new functionality to the existing Beta Feature in 1-2 weeks.

Announcements

Done

  • Links to the announcements made on each of our partner wikis are added to the "Announcement link" column in the table in the "Announcements" section above.

Details

Due Date
May 14 2020, 7:00 AM

Event Timeline

ppelberg set Due Date to May 14 2020, 7:00 AM.
ppelberg moved this task from Backlog to Community Engagement on the Editing-team (Tracking) board.
ppelberg renamed this task from Make partner wikis aware of `dtvisual=1` to Make partner wikis aware of `dtvisual=1` and v2.0 sequence and timing.May 9 2020, 2:26 AM
ppelberg added a subscriber: Whatamidoing-WMF.

Do you plan to share a template for the announcement?

Do you plan to share a template for the announcement?

@Lofhi good question – I defer to @Whatamidoing-WMF who is thinking about this communication.

Note: I've updated the task description to add details about which particular features we would value people trying out and sharing their experiences with.

Update
1.35.0-wmf.32 has landed on "Group 2" [1] meaning the visual mode is now available for testing at our partner wikis by adding ?dtvisual=1 to the URL of any page where the Reply tool is already available.

I've confirmed this in T251963#6166693.


  1. https://versions.toolforge.org/

I will announce the version 2.0 of the Reply tool since... it's version 2.0! It's already complicated enough for editors to explain to them that the Reply tool is a tool of the DiscussionTools beta feature and that there will be other tools. Do you think we need to wait Thursday for the last fixes?

I will announce the version 2.0 of the Reply tool since... it's version 2.0!

You announcing this as being "Version 2.0" of the reply tool sounds great – thank you, @Lofhi.

The information we think is important for people to know is listed in the "Announcement components" section of the task description – does what's included there look okay to you?

Do you think we need to wait Thursday for the last fixes?

What are the fixes you have in mind?

...I see you filed a few tickets recently (thank you!) [i] and I'm wanting to be sure I know which ones you are referring to.


i. T253660, T253667, T253482

@ppelberg T253664 and T252460. One editor I tried the visual editor with already complained about the absence of the @, so I might as well wait for it to be added?

@ppelberg T253664 and T252460. One editor I tried the visual editor with already complained about the absence of the @, so I might as well wait for it to be added?

Thank you for the links to these tasks, @Lofhi.

It looks like fixes for these issues are scheduled to land at fr.wiki tomorrow [i]. With this in mind, let's do as you suggested:

  1. Tomorrow (28-May): confirm T253664 and T252460 have been fixed at fr.wiki (assuming they will in fact land there then)
  2. Once we confirm both issues have been fixed (ideally, tomorrow), you announce that v2.0 is available for testing.

If, for some reason, fixes for the two issues do not land tomorrow (28-May), I would suggest we do the following, although I default to doing what you think is best.

  1. Amend the announcement you had planned to post to include a section for known issues which would include T253664 and T252460
  2. Announce that v2.0 is available for testing with the "known issues" amendment included

i. @matmarex: please comment if fixes for T253664 and T252460 will not land tomorrow (28-May) on fr.wiki.

  1. Tomorrow (28-May): confirm T253664 and T252460 have been fixed at fr.wiki (assuming they will in fact land there then)

@Lofhi, it looks like fixes for both of these issues have landed on fr.wiki. See this edit where @ was automatically prefixed: https://w.wiki/S8f

Updating task description to include the posts made to Dutch and French Wikipedias...@Whatamidoing-WMF, do you know if anything has been posted to hu.wiki yet? I know we talked about pinging Samat, tho I haven't seen anything posted to the local discussion page [1] which led me here to ask.


  1. https://hu.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Konzult%C3%A1ci%C3%B3_a_vitalapokr%C3%B3l_%C3%A9s_a_k%C3%B6z%C3%B6ss%C3%A9gi_kommunik%C3%A1ci%C3%B3r%C3%B3l&action=history

@Lofhi, it looks like fixes for both of these issues have landed on fr.wiki. See this edit where @ was automatically prefixed: https://w.wiki/S8f

All right, I'll write something on Le Bistro for tomorrow.

@Lofhi, it looks like fixes for both of these issues have landed on fr.wiki. See this edit where @ was automatically prefixed: https://w.wiki/S8f

All right, I'll write something on Le Bistro for tomorrow.

Excellent. Thank you.