Talk:Requests for comment/Inline diffs

Jump to navigation Jump to search

About this board

Next steps from RFC review meeting

6
Sharihareswara (WMF) (talkcontribs)

Per the meeting on March 5th, MaxSem is going to add mode switching UI details to the RFC, and Dan Garry is going to look into whether we want to make this a beta feature, a preference, an option on the diff page, or something else.

Deskana (WMF) (talkcontribs)

I think this would be a good candidate to be a Beta Feature. This is because we believe the average user of a Beta Feature is a relatively experienced Wikipedia editor and the target audience for a feature such as this one is experienced users. This helps you be sure that the feedback you get about the Beta Feature is actually from the intended audience, which is really important when deciding whether to graduate the feature to default across all wikis.

To be a Beta Feature, this will need someone acting as product manager. I can't volunteer for that as I'm spread a little thin already. The person needn't be a product manager by title, just someone who's willing to take point and drive the development of the product forward and bear the users of the product in mind.

I'm more than happy to offer further advice if it's needed.

Thanks!

This post was posted by Deskana (WMF), but signed as DGarry (WMF).

MaxSem (talkcontribs)

Even if a beta feature, we still need a selector because nobody's intending to replace the current diff, only to add an optional alternative to it.

Sharihareswara (WMF) (talkcontribs)

Max, have you been able to add those mode switching UI details?

Reply to "Next steps from RFC review meeting"
Quiddity (WMF) (talkcontribs)

As long as we stick to the mockup, or improve upon it, specifically the inclusion of a high-visiblity Toggle, to switch between the 2 views, and also not making it the default anywhere, to start with, then I think it should be very easy to get this done.

Docs must have side-by-side screenshots of:

  • 2 Instances where Inline Diff is clearer (than the default)
  • 2 Instances where it is not

(to demonstrate that we understand its limitations, and to showcase its benefits.)

Docs must have solid citations for the accessibility of the colour-palette. (To prevent endless discussion). I assume these are available from whoever validated the colors in Mobile, but I don't know where to find them.

InlineDiff could have options for colour-palette. Eg. the colour-palette and strikethrough used in Navpopups: File:Navpopups_diff_screenshot.png (I grok that some devs are reluctant to add preferences, but users love having options. At the very simplest, we should provide user.css snippets for easy copy&pasting, so that anyone can test/use 1 or 2 alternative colour-palettes.)

That's all the blockers/suggestions I can think of.

Reply to "To do list"
There are no older topics