RHo (Rita Ho)
User

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

User Since
Mar 23 2016, 6:05 PM (147 w, 4 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
RHo (WMF) [ Global Accounts ]

Recent Activity

Fri, Jan 18

RHo updated the task description for T213992: Homepage: technical investigation.
Fri, Jan 18, 1:20 PM · Growth-Team (Current Sprint)
RHo updated the task description for T213992: Homepage: technical investigation.
Fri, Jan 18, 1:17 PM · Growth-Team (Current Sprint)
RHo updated the task description for T213992: Homepage: technical investigation.
Fri, Jan 18, 1:13 PM · Growth-Team (Current Sprint)
RHo updated the task description for T213989: Engagement emails: technical investigation.
Fri, Jan 18, 1:07 PM · Growth-Team (Current Sprint)

Thu, Jan 17

RHo added a comment to T209301: Help panel: enable searching help articles.

More comments inline....

Thu, Jan 17, 6:25 PM · MW-1.33-notes (1.33.0-wmf.14; 2019-01-22), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T209301: Help panel: enable searching help articles.

Thanks @Etonkovidova - please see responses inline.

Thu, Jan 17, 6:10 PM · MW-1.33-notes (1.33.0-wmf.14; 2019-01-22), Patch-For-Review, Growth-Team (Current Sprint)
RHo updated subscribers of T213885: Multilingual Captions: Content isn't clear:both'ed on Files with no captions yet, because it's still wrapped in a mw:mediainfoView tags.
Thu, Jan 17, 3:46 PM · Patch-For-Review, SDC Engineering, Multimedia
RHo updated subscribers of T212162: Structured data heading is level-1 instead of level-2, because it's a slot and that's how MediaWiki represents them; let's over-ride this.
Thu, Jan 17, 3:39 PM · Multimedia-Team-Working-Board, SDC Engineering, Multimedia

Wed, Jan 16

RHo renamed T213958: Welcome Survey: disable implicit escape of Variation C from Make variation C of the Welcome Survey non-escapable to Disable implicit escape of variation C of the Welcome Survey.
Wed, Jan 16, 9:53 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T213958: Welcome Survey: disable implicit escape of Variation C.

Making surveys unskippable sounds like a bad idea pretty much by principle.

Wed, Jan 16, 9:46 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T213958: Welcome Survey: disable implicit escape of Variation C from Incoming to Ready for Development on the Growth-Team (Current Sprint) board.
Wed, Jan 16, 7:41 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)
RHo created T213958: Welcome Survey: disable implicit escape of Variation C.
Wed, Jan 16, 7:41 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)

Tue, Jan 15

Trizek-WMF awarded T206715: [Design EPIC] Help desk: In-context experience a Party Time token.
Tue, Jan 15, 5:25 PM · Growth-Team (Current Sprint)

Mon, Jan 14

RHo moved T212479: UI consistency issues of Variation C from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

Thanks @Etonkovidova - I think it is acceptable to have the visible checkboxes on Chrome, and per @Volker_E 's the "selected button" using Accent10 is expected (an oversight on my part earlier). LGTM to sign-off.

Mon, Jan 14, 1:02 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), Patch-For-Review, UI-Standardization, UI-Standardization-Kanban, Growth-Team (Current Sprint)
RHo moved T212551: [minor] Help panel: the checkmark for "Your question has been posted" displayed on a new line from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM

Mon, Jan 14, 12:06 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), Patch-For-Review, Growth-Team (Current Sprint)

Sun, Jan 13

RHo added a comment to T211109: Create testable prototype for user testing the Edit action queue (add and translate title descriptions only).

Hi Robin , thanks for going through the proto again, just have a couple comments inline below.

Sun, Jan 13, 1:17 PM · Patch-For-Review, Wikidata, Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington), Android-app-feature-Description-Editing

Fri, Jan 11

RHo added a comment to T211109: Create testable prototype for user testing the Edit action queue (add and translate title descriptions only).

Hey @RHo, just talked to the team and @Dbrant mentioned that we’re going to use the Alpha for it. @Sharvaniharan is doing the last few tweaks and if @ABorbaWMF doesn’t have the time I’ll QA the app according to @dchen’s protocol before Monday. Does that sound fine to you?

  • Sure, I'd just request the specific Alpha version is clearly marked and uploaded for testing across all participants.
Fri, Jan 11, 9:03 PM · Patch-For-Review, Wikidata, Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington), Android-app-feature-Description-Editing
RHo added a comment to T212806: 'references' icon needs alignment.

Hey @Volker - looks like both the updated references and existing reference icons were omitted in the export. Here are the updated icons as SVGs - thanks for your vigilance :)

Fri, Jan 11, 7:41 PM · OOUI (OOUI-0.30.2), UI-Standardization-Kanban, UI-Standardization
RHo added a comment to T211166: Help panel: instrumentation for search.

The search feature is now built so we can start thinking about this.

I don't know if logging the exact search terms is going to be acceptable.

As a first step we could log a search action with how many results are returned as well as a link-click with something like "search-result-2" (referring to the second result on the list). These don't seem too controversial and would already tell us if the feature is being used at all.

Fri, Jan 11, 6:52 PM · Growth-Team (Current Sprint)
RHo updated subscribers of T211109: Create testable prototype for user testing the Edit action queue (add and translate title descriptions only).

hi @Dbrant - can the updated APK for testing be linked to this ticket when ready so that @dchen and @schoenbaechler can continue pilot and test planning? Thanks!

Fri, Jan 11, 1:33 PM · Patch-For-Review, Wikidata, Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington), Android-app-feature-Description-Editing
RHo renamed T211109: Create testable prototype for user testing the Edit action queue (add and translate title descriptions only) from Create testable prototype for user testing to Create testable prototype for user testing the Edit action queue (add and translate title descriptions only).
Fri, Jan 11, 1:31 PM · Patch-For-Review, Wikidata, Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington), Android-app-feature-Description-Editing

Thu, Jan 10

RHo moved T213486: Comparative review of engagement emails from Incoming to Needs Design/Design Doing on the Growth-Team (Current Sprint) board.
Thu, Jan 10, 9:06 PM · Growth-Team (Current Sprint)
RHo created T213486: Comparative review of engagement emails.
Thu, Jan 10, 9:06 PM · Growth-Team (Current Sprint)
RHo moved T212905: Help panel: Mobile version should show help contents on a scrollable layer behind the "post a question" form from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM as well (tested on Chrome mobile browser on Pixel, Android OS 9)

(open full screen to see animated gif)

Thu, Jan 10, 8:30 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212890: Help panel: design - CTA on mobile view should be circular from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM too!

(Nexus 5)

Thu, Jan 10, 7:47 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T212551: [minor] Help panel: the checkmark for "Your question has been posted" displayed on a new line .

Is this wrapping acceptable?

  • Yes, that's fine. The main thing is that the message is intended to start on the same line as the icon. The message wrapping to a second line is bound to occur in some language translations and smaller device widths anyway.
Thu, Jan 10, 7:45 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T213458: Analyse Android notifications release.

thanks @Charlotte - nothing in terms of targeting, but it would be good to see if there are patterns in usage of Notifications itself (event logging from T201943). That is:

  • How many people turned on polling out of all those who saw Notifications?
  • Interactions with different notification types - how many Milestone, Welcome and Thank notifications were sent vs viewed?
  • Was there a particular notification type that shifted contribution/edit rate more than others?
Thu, Jan 10, 5:49 PM · Product-Analytics

Tue, Jan 8

RHo added a comment to T210847: Resize the OOUI 'x` close icon?.

I think we don't need to mention this one exception case

Tue, Jan 8, 5:00 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), OOUI (OOUI-0.30.1)
RHo added a comment to T212905: Help panel: Mobile version should show help contents on a scrollable layer behind the "post a question" form.

The "post a question" form is sticky to the bottom of the mobile screen and exists on a separate layer from the other help panel contents

@RHo should this be the case for step two of the post question process? This is how it currently looks on an iPhone 5/SE:

Tue, Jan 8, 1:23 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212902: Help panel: Use ButtonWidget normal style for mobile confirmation screen from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM too

Tue, Jan 8, 12:25 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212893: Help panel: incorrect content section heading text color on mobile from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM too

Tue, Jan 8, 12:24 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212894: Help panel: Incorrect top articles link list styling on mobile from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM too

Tue, Jan 8, 12:22 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212897: Help panel: Design enhancement - increase help panel width on Desktop when the browser window is *wider* than 1366px from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

The Help panel will be correctly resized if the browser viewport >1366:
betalabs - the browser viewport 1699 - the Help panel is 500x335


testwiki (without the patch) - the browser viewport 1648 - the Help panel is 300x411

Note:
Once the larger Help panel was opened, resizing the browser window will not resize the Help panel back to 300x411. The resized page needs to be reloaded to make Help panel smaller.

LGTM, and not resizing to the standard view after opening when the window was >1366px is fine.

Tue, Jan 8, 12:21 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212901: Help panel: add space between paragraphs on confirmation screen in mobile view from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM

Desktop
Mobile
Tue, Jan 8, 12:15 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T212887: Help panel: Missing animation transitions from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

Hiya - animations LGTM for desktop and mobile:
(open fullscreen to view animated gifs)

Desktop
Mobile
Tue, Jan 8, 11:55 AM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, MediaWiki-extensions-GrowthExperiments, Growth-Team (Current Sprint)

Mon, Jan 7

RHo added a comment to T188333: [UX-Debt] Allow users to search for articles across all reading lists.

Relevant to this are some old designs for the same issue on iOS:
T141874

Mon, Jan 7, 4:51 PM · Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington), Android-app-feature-UX-Debt
RHo moved T206716: Help panel: business rules on displaying the feature from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.
Mon, Jan 7, 3:39 PM · MW-1.33-notes (1.33.0-wmf.9; 2018-12-18), Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T209318: Help panel: allow users to "Ask a question" to help desk from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

hi @MMiller_WMF @Etonkovidova - this LGTM, the close icon is using the standard positioning from OOUI.

Mon, Jan 7, 3:35 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T204081: Color of visited links is difficult to distinguish from plain black text in MinervaNeue skin.

@Nirzar thanks for taking a look. I too think purple 1 is a good choice.

General note: Nirzar pointed out that using the WCAG AA rating was not a good method for evaluating these options (measuring the legibility of foreground colors on a given background is different than measuring the difference between two adjacent colors). I've therefore updated the ratings in the table above to use the Delta E measurements. You can read more about that at the bottom of this comment: T204081#4831911.

Mon, Jan 7, 12:14 PM · Readers-Web-Backlog (Readers-Web-Kanbanana-Board-2018-19-Q3), MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), Patch-For-Review, MinervaNeue, Accessibility, UI-Standardization, UI-Standardization-Kanban

Fri, Jan 4

RHo triaged T212890: Help panel: design - CTA on mobile view should be circular as High priority.
Fri, Jan 4, 6:27 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)
RHo triaged T212893: Help panel: incorrect content section heading text color on mobile as Normal priority.
Fri, Jan 4, 6:27 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo triaged T212894: Help panel: Incorrect top articles link list styling on mobile as Low priority.
Fri, Jan 4, 6:26 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo triaged T212897: Help panel: Design enhancement - increase help panel width on Desktop when the browser window is *wider* than 1366px as Lowest priority.
Fri, Jan 4, 6:26 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo triaged T212901: Help panel: add space between paragraphs on confirmation screen in mobile view as Normal priority.
Fri, Jan 4, 6:26 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo triaged T212905: Help panel: Mobile version should show help contents on a scrollable layer behind the "post a question" form as Low priority.
Fri, Jan 4, 6:26 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo triaged T212903: Help panel: text on mobile is behaving like a link as Lowest priority.
Fri, Jan 4, 6:24 PM · MW-1.33-notes (1.33.0-wmf.14; 2019-01-22), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T212905: Help panel: Mobile version should show help contents on a scrollable layer behind the "post a question" form.

@RHo is this a new requirement or did I miss that in the original specs? Does it need to be done before the initial launch?

Fri, Jan 4, 5:48 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T206716: Help panel: business rules on displaying the feature.

@MMiller_WMF

@kostajh -- I just re-read this. @Etonkovidova is pointing out that people who do not have a confirmed email will still receive echo notifications on wiki (not email notifications), and that therefore the text might be misleading because it could make it seem like the only way to find out about the response is through email. I think that the language is okay, because we believe that users are much more likely to notice notifications via email than through echo alerts on wiki. I'm afraid to clutter and confuse by adding additional caveats to the sentence. Is this what you were getting at @Etonkovidova?

Right, but reading thinking more about it and reading the text "If you add an email address to your account, you'll receive an email confirmation link so that you can be notified of responses." - it sounds ok. It'd be nice to introduce to a user echo notifications, but the Help panel has its obvious space limitations.

Fri, Jan 4, 12:03 PM · MW-1.33-notes (1.33.0-wmf.9; 2018-12-18), Patch-For-Review, Growth-Team (Current Sprint)

Thu, Jan 3

RHo added a comment to T211633: Help panel: design tweaks.

Thanks @RHo, @MMiller_WMF can we close this one?

Thu, Jan 3, 9:56 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212905: Help panel: Mobile version should show help contents on a scrollable layer behind the "post a question" form.
Thu, Jan 3, 9:53 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo updated the task description for T212505: Help Panel: Disable zoom on form elements in iOS.
Thu, Jan 3, 9:27 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint), MediaWiki-extensions-GrowthExperiments
RHo created T212903: Help panel: text on mobile is behaving like a link.
Thu, Jan 3, 9:27 PM · MW-1.33-notes (1.33.0-wmf.14; 2019-01-22), Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212902: Help panel: Use ButtonWidget normal style for mobile confirmation screen.
Thu, Jan 3, 9:25 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212901: Help panel: add space between paragraphs on confirmation screen in mobile view.
Thu, Jan 3, 9:24 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T211633: Help panel: design tweaks.

Thanks, @kostajh. I just did some testing, and I have a couple other "design tweak" issues. I'm putting them in this comment. But I agree that these will be easier to manage in separate tasks. @RHo -- what do you think about going through everything in this task's description and comments tomorrow, making new tasks for anything outstanding, and putting them in priority order in the "Ready for Development" column?


  • In my testing, I noticed the width of the help panel being awkwardly narrow, especially when there is a lot of text. I know this is already listed here, but I just wanted to vote for it. Here is the screenshot that was bugging me:

Since the intention of the narrower design of the help panel is to not cover too much of the editing UI, I've created an "enhancement" task T212897 to only expand the width when the browser window on Desktop is wider than 1366px

Thu, Jan 3, 9:19 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo renamed T212505: Help Panel: Disable zoom on form elements in iOS from Help Panel: Disable zoom on form elements in iOS to Help Panel: Mobile display UI fixes.
Thu, Jan 3, 9:19 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint), MediaWiki-extensions-GrowthExperiments
RHo created T212897: Help panel: Design enhancement - increase help panel width on Desktop when the browser window is *wider* than 1366px.
Thu, Jan 3, 8:38 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T211633: Help panel: design tweaks.

@RHo @MMiller_WMF I updated the status for each item. Please have a look and let me know what you think. Looking at it all together, the main item I see that's not done is the animation. If possible I'd like to close this task and open up individual tasks for follow-up items (the animation, or anything else) for better efficiency.

Thu, Jan 3, 8:28 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo updated the task description for T211633: Help panel: design tweaks.
Thu, Jan 3, 8:27 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a project to T212894: Help panel: Incorrect top articles link list styling on mobile: Growth-Team (Current Sprint).
Thu, Jan 3, 8:23 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212894: Help panel: Incorrect top articles link list styling on mobile.
Thu, Jan 3, 8:23 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212893: Help panel: incorrect content section heading text color on mobile.
Thu, Jan 3, 8:18 PM · Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212890: Help panel: design - CTA on mobile view should be circular.
Thu, Jan 3, 8:06 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), MediaWiki-extensions-GrowthExperiments, Patch-For-Review, Growth-Team (Current Sprint)
RHo created T212887: Help panel: Missing animation transitions.
Thu, Jan 3, 7:58 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, MediaWiki-extensions-GrowthExperiments, Growth-Team (Current Sprint)
RHo moved T211113: Help panel: allow users to supply an email address from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.
Thu, Jan 3, 7:41 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T211113: Help panel: allow users to supply an email address.

@Etonkovidova -- the testing was done on testwiki but the screenshots are from beta? Something I noticed is that the message for "no email" is incorrect. It is supposed to start with "If you add an email address to your account..." not "You'll receive..."

Thu, Jan 3, 7:41 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T210865: Improve the language icon.

Agree with @Pginer-WMF and @Amire80's point that there is unlikelt to be some universally accepted language icon we could be using instead of the current one. I'd also advocate for appending with more signifiers that this is a change-able language settings by adding the language code and/or a dropdown arrow after the icon, rather than trying to amend/change it to some other icon.

Thu, Jan 3, 11:27 AM · Wikimedia-Interwiki-links, Readers-Web-Backlog (Design), MobileFrontend

Wed, Jan 2

RHo added a comment to T212505: Help Panel: Disable zoom on form elements in iOS.

In the design the link appears as a new paragraph as the first of 2 links

I thought we're just doing a single link, and "More about this feature" is going to live under the settings cog?

  • @MMiller_WMF can weigh in but I think it would be good to more explicitly provide information to users about this experimental feature here as well.
Wed, Jan 2, 7:52 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint), MediaWiki-extensions-GrowthExperiments
RHo added a comment to T207528: To what extent do newly registered users search for how-to information?.

We may also want to consider looking at search queries from the Help panel, assuming T209301 is implemented.

Wed, Jan 2, 6:04 PM · Growth-Team, Product-Analytics
RHo added a comment to T212505: Help Panel: Disable zoom on form elements in iOS.

A couple things from light testing:

  • I think "View your question on the Help Desk" should have greater affordance. It's currently a blue link in the same font as the paragraph above it, and it isn't spaced away from that paragraph. I'm imagining it being larger, bolder, and distinct from the black text above it. Good question for @RHo.
Wed, Jan 2, 6:00 PM · MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint), MediaWiki-extensions-GrowthExperiments
RHo added a comment to T212479: UI consistency issues of Variation C.

hi @Volker - re: the last item you added about the different transition in the task description after @SBisson's patch - we can use the standard transition

Wed, Jan 2, 5:28 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), Patch-For-Review, UI-Standardization, UI-Standardization-Kanban, Growth-Team (Current Sprint)
RHo added a project to T212684: App crashes when logging in on Meizu Pro 6 with Flymeos 7.8.5.22 beta and Android 7.1.1: Android-app-Bugs.
Wed, Jan 2, 1:18 PM · Android-app-Bugs, Wikipedia-Android-App-Backlog
RHo renamed T212683: BUG: Copy paste icon not visible in latest Beta on Android 4.1.2. from Copy paste not visible in latest Beta on Android 4.1.2. to BUG: Copy paste icon not visible in latest Beta on Android 4.1.2..
Wed, Jan 2, 1:14 PM · Android-app-Bugs, Wikipedia-Android-App-Backlog
RHo added a comment to T210847: Resize the OOUI 'x` close icon?.

@RHo Any feelings about this? I've just looked at the Personalized First Day implementation again and had the same reaction about 20x20px being too large that made me file this.

Wed, Jan 2, 1:08 PM · MW-1.33-notes (1.33.0-wmf.13; 2019-01-15), OOUI (OOUI-0.30.1)

Dec 20 2018

RHo added a comment to T211633: Help panel: design tweaks.

A. Missing animation to transition help panel CTA onto the editor screen

This is doable but I don't know if we'll be able to get the right timing. The loading sequence of the various editors on the different platforms (desktop vs mobile) is already quite busy, especially with VE. I don't know if adding another moving part is really helping. What would be the ideal timing for the animation (when should it start)?

Thanks @SBisson - can we ideally time it to come in after the editor has finished loading?

E. Help panel dialog header icons color and placement
K. Confirmation icon color

I don't think we can change the icons colors. They can be black, blue, or red. Lighter grey is used to represent disabled state and is implemented by lowering the opacity.

Hmm can we make the icons black at opacity .56 so make it as close as possible to the desired Gray?

A green checkmark would have to be a custom icon.

Nevermind, we can live with a blue checkmark.

Dec 20 2018, 12:12 AM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)

Dec 17 2018

RHo added a comment to T209539: On boarding screens for the App Editor task list.

@cmadeo I just wanted to run the disabled looks by you since we decided to have an alpha instead of different colors..
We decided 0.62 looks like this :

I just felt 0.82 looked better so here is a screenshot of that as well

Please let me know which one looks good, and if you don't feel like they are good enough i will be happy to just code freshly to the completely different disabled colors from zeplin..

Dec 17 2018, 10:24 PM · Patch-For-Review, Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington)

Dec 12 2018

RHo moved T210112: Help panel: conduct user testing of initial help pane design from Needs Design/Design Doing to Needs PM Review on the Growth-Team (Current Sprint) board.

Findings summary presentation is complete, with most of the minor recommendations from the testing incorporated into the V1 design.

Dec 12 2018, 9:56 PM · Growth-Team (Current Sprint)
RHo updated the task description for T210112: Help panel: conduct user testing of initial help pane design.
Dec 12 2018, 9:55 PM · Growth-Team (Current Sprint)
RHo added a comment to T164606: As a user who enjoys adding descriptions, I can easily find other suitable articles to add descriptions to.

Thanks for bringing this up @cooltey. I'm actually a bit stuck about what the answer should be and would love input from @schoenbaechler and @Charlotte.

On one end, it seems like it would be a good idea to reduce the number of interfaces to maintain, but on the other the user has more context when they are editing from the article (therefore the UI could be a little more paired down). I can definitely see some benefits to including more context (eg. the new design) in the normal description editing though, so my vote would be to update both editors to be the same (the new version). I am not sure that we really need to review in the article view though as the user will see the article immediately after submitting and can take action to change it if they made a mistake.

Dec 12 2018, 4:26 PM · Patch-For-Review, Wikipedia-Android-App-Backlog (Android-app-release-v2.7.27x-L-Lamington), Wikidata, Android-app-feature-Description-Editing
RHo added a comment to T207717: Personalized first day: build Variation C.

[...]
FWIW, it is the same radio button control as var A, it has just been styled differently – so in var A as well if someone had selected an option by accident they would not have been able to deselect all either.

Var A is using dropdowns instead of radio groups for the first 2 questions and they include a placeholder value ("Please select...") that the user can go back to.

Dec 12 2018, 1:48 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T211633: Help panel: design tweaks.

@RHo will prioritize the different issues in this task to help the team work through them.

Updated on each line item in the Task description.

Dec 12 2018, 1:21 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo updated the task description for T211633: Help panel: design tweaks.
Dec 12 2018, 1:21 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T207717: Personalized first day: build Variation C.

@SBisson @RHo @Etonkovidova -- thank you for making this turn out great!

I have a few questions and issues from trying this on mobile in Safari on my iPhone:

  • I noticed that the email address question and the mentorship question are on the same page on both mobile and desktop. Is that deliberate? Do we prefer it that way instead of separated?
  • hi Marshall, these have always been on the same step in the design since they are somewhat related. The other more pertinent reason is that for users who provided their email during account sign-up don't see the email field, only the mentor checkbox question. Having them on same step means not having to have a conditionally shown extra 5th step.
  • @RHo -- why do we want it so that users can't unselect a radio button? To encourage them to submit their response?

Not so much that, but more so that is the way single-selection response type questions are by design. I.e., the group of radio buttons offers the gamut of all responses possible, for which users choose 1 response. So if someone has made a selection by accident on option A, they should still be able to select whatever the pertinent answer for them in that list.
FWIW, it is the same radio button control as var A, it has just been styled differently – so in var A as well if someone had selected an option by accident they would not have been able to deselect all either.

Dec 12 2018, 12:19 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)

Dec 11 2018

RHo updated the task description for T209301: Help panel: enable searching help articles.
Dec 11 2018, 7:15 PM · MW-1.33-notes (1.33.0-wmf.14; 2019-01-22), Patch-For-Review, Growth-Team (Current Sprint)
RHo moved T207717: Personalized first day: build Variation C from Design Review to Needs PM Review on the Growth-Team (Current Sprint) board.

LGTM on Desktop and Mobile

Dec 11 2018, 6:34 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T207717: Personalized first day: build Variation C.

When I was testing it I was gonna ask Marshall "wait, the questions are mandatory?", and I realized he told me before that they're optional several seconds after, so I proposed the button can say Skip in this case instead.
If this confused me for a while (as I consider myself as someone who knows a little how this should work), it can confuse a newbie too. The comparation of risk of having a newbie answering all questions because they think they are mandatory and a risk of having a newbie confused about the difference of Skip question and Skip survey is up to you of course, I'm just sharing my thoughts.
We can minimalize the second kind of risk by having the button say "Skip this question" instead. Of course, that can make significant differences in length of that button. To solve this, we can have the button say only Skip this question and show next question when user pickes a response.

I think the risk of confusion by renaming the first button "Skip this question" along with “Skip this survey” outweighs the minor risk of people thinking that the survey questions are mandatory (since we do say they are optional in the intro text on that same first question). Secondly it will substantial effort for the change to auto-advance to the next question when the user picks an answer, not to mention the need for an additional “next” button if the user picks “Other” as the response.
My recommendation is we go with the survey as it is now and monitor response rate. If we see a great decline in completion by people exiting at this first step then we can re-evaluate.

Dec 11 2018, 11:47 AM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T211206: Help Panel: Enable on beta labs.

the asterisk is not present until 'Review and submit' is clicked - should we communicate earlier that the input is required?

IIRC this is by design (@RHo please correct me if I'm wrong, because at a quick glance I didn't find the relevant notes in T209318). The idea is that you can click the button on the first step without having entered any text, and you're only required to fill in text on step two. I can easily change it to add the required indicator on step 1 @RHo so just let me know.

  • hi @kostajh - yes, let's make it mandatory on both steps 1 and 2 please.
Dec 11 2018, 10:22 AM · MW-1.33-notes (1.33.0-wmf.9; 2018-12-18), Patch-For-Review, MediaWiki-extensions-GrowthExperiments, Growth-Team (Current Sprint)
RHo added a comment to T211513: Help panel: show search link content and help link content inside help panel.

+1 to this proposal, including for showing the "top 5 editing links" inside the help panel as well rather than opening in a new tab.

Dec 11 2018, 10:20 AM · Growth-Team

Dec 10 2018

RHo created T211633: Help panel: design tweaks.
Dec 10 2018, 9:25 PM · MediaWiki-extensions-GrowthExperiments, MW-1.33-notes (1.33.0-wmf.12; 2019-01-08), Patch-For-Review, Growth-Team (Current Sprint)

Dec 7 2018

RHo added a comment to T211206: Help Panel: Enable on beta labs.

(2) the lost part of the message does not appear even when the box is increased:

That's the placeholder text. I agree it looks awkward but not sure what can be done with that, other than changing the placeholder text. FWIW, I think the "I need help with editing" is probably redundant or maybe just too vague; would the help desk mentors want to see questions that start with "I need help with editing"?

  • This is actually the updated placeholder copy after feedback from a number of people about wanting it to be clearer that people should be asking for help about editing by hinting at this using the first sentence, rather than expecting users to re-type in "I need help with editing". Suggest we keep this as is for now and see what help questions look like before further changes.
Dec 7 2018, 7:41 PM · MW-1.33-notes (1.33.0-wmf.9; 2018-12-18), Patch-For-Review, MediaWiki-extensions-GrowthExperiments, Growth-Team (Current Sprint)
RHo added a comment to T211113: Help panel: allow users to supply an email address.

Here's what this looks like:

I'm wondering what you think about moving the "Confirm email" note and step to the last panel. My reasoning is:

  1. Suppose the user clicks "Confirm email"
  2. Special:ConfirmEmail will open for them in a new tab or window. Best case scenario, they'll click the "mail link", go to their inbox, click the link, and be back on Special:ConfirmEmail with a notice that their email was confirmed.
  3. Then, they'll have to find their other tab/window with the help panel. Once there, they'll still see "Confirm your email". We could make "Confirm your email" disabled as soon as the user clicks it, but then it's still potentially confusing to the user as to whether they succeeded in confirming or not.

    If we move the "confirm your email" flow to the last step of the panel, there's less chance of the user getting confused about what's going on, IMO.
Dec 7 2018, 3:53 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T207717: Personalized first day: build Variation C.

hi @SBisson - one more thing I noticed in the mobile test is that when tapping "Next", it proceeds to the next question without returning the user to the top of the screen. For example if I've scrolled to enter my own interest topics on Q3 and tap "Next", I do not see the "Enter an email" field because the viewport is on the lower part of the dialog. See vid showing the behavior here: https://youtu.be/RF9meXc7K0A?t=21 (start ~21sec mark)

Dec 7 2018, 1:30 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T207717: Personalized first day: build Variation C.

This would mean "back" and "next" shifting under the user's cursor. I'll do it if you really insist but I see absolutely nothing wrong with navigation buttons being stable and enable/disable as relevant.

Dec 7 2018, 1:24 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T207717: Personalized first day: build Variation C.

@RHo I've made all the visual changes suggested above (patch coming up) but I'm not sure about "C. Placement of Next and Finish CTAs".

Putting "Finish" where "Next" is means that clicking "next" repeatedly has a high chance of the user hitting "Finish" by accident.

Dec 7 2018, 1:22 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)

Dec 6 2018

RHo added a comment to T211113: Help panel: allow users to supply an email address.

@RHo what should the "Confirm your email" button do? In preferences, it takes you to /wiki/Special:ConfirmEmail. Would the button in the help panel do the same thing or do you want that button to trigger sending the confirmation email, then disable the "Confirm your email" button and add text explaining to the user that they should check their inbox and click the link to confirm their email?

Dec 6 2018, 7:24 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T209318: Help panel: allow users to "Ask a question" to help desk.

@RHo @MMiller_WMF:

We will prevent duplicate headers by numbering them sequentially.

Do we need to append a number to the end? On Beta labs the numbering on the index seems sufficient. Do you want to see (2) and (3) appended to items 11 and 12 in the screenshot below?

Dec 6 2018, 7:18 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T211113: Help panel: allow users to supply an email address.

I think the best would be to provide a link to wiki/Special:ConfirmEmail, where the user can follow the instructions to mail themselves a new verification code.

Dec 6 2018, 7:15 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T207717: Personalized first day: build Variation C.

When @Urbanecm was testing out Variation C in beta this morning, he brought up two questions for @RHo:

  • On the very first screen (the question about why they made their account), there is a grayed-out back button. Since there are no circumstances in which that back button would not be grayed out, should we just not have a back button th
  • Yes agree, can we hide "Back" on the first step @SBisson ?
  • If a respondent is looking at a question and pushes "Next" without answering it, that is effectively them saying "Skip". Should the button literally say "Skip" until they give a response, at which point it becomes "Next"?
  • Let's keep it as "Next" since it is confusing to have two actions that say Skip ("Skip this survey" and "Skip" to the next question)
Dec 6 2018, 6:31 PM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T206716: Help panel: business rules on displaying the feature.

Can the link to disable the panel work directly, without forcing people to go to the preferences?
For now, it is not possible to link th a precise message and highlight it (I've documented that need T211204), which can confuse people.

Dec 6 2018, 3:08 PM · MW-1.33-notes (1.33.0-wmf.9; 2018-12-18), Patch-For-Review, Growth-Team (Current Sprint)
RHo added a comment to T206716: Help panel: business rules on displaying the feature.

Here's a simpler version for settings, with a tooltip to inform the user about what's going on. Doesn't solve the problem for mobile, but for desktop at least the user has some idea of what's going on.

Dec 6 2018, 2:07 PM · MW-1.33-notes (1.33.0-wmf.9; 2018-12-18), Patch-For-Review, Growth-Team (Current Sprint)