Page MenuHomePhabricator

RHo (Rita Ho)
User

Projects (21)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

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

Recent Activity

Fri, Jun 24

RHo added a comment to T222310: Positive reinforcement: Impact Module V2022.

@KStoller-WMF @RHo To reduce confusion in our code, public facing documentation, and i18n strings, I wonder if we could call the new version of the impact module something else, like the "Positive reinforcement module" or something like that?

Fri, Jun 24, 11:38 AM · Epic, Growth-Positive-Reinforcement, GrowthExperiments-ImpactModule, Growth Design, Growth-Team (Current Sprint)
RHo added a comment to T310962: Emails of thanks are not sent when 'enotifminoredits' is disabled.

Thanks for the bug report; the Growth team can't work on it any time soon.

... although perhaps it is in the scope of the Growth-Positive-Reinforcement project; @RHo @KStoller-WMF what do you think?

Fri, Jun 24, 10:44 AM · Growth-Team, Thanks, Notifications
RHo added a comment to T311228: Revise design of the Mentee overview filter for recent days.

@Urbanecm_WMF I'll let you decide when we get to this. Presumably it would happen after we finish the initial Vue migration.

Fri, Jun 24, 9:56 AM · Growth-Team, GrowthExperiments-MentorDashboard

Thu, Jun 23

RHo attached a referenced file: F35267800: image.png.
Thu, Jun 23, 7:26 PM · Epic, Codex, Design-Systems-Team
RHo attached a referenced file: F35268163: image.png.
Thu, Jun 23, 7:26 PM · Epic, Codex, Design-Systems-Team
RHo added a comment to T311160: Add indicator that appears when TOC has been hidden.

@ovasileva @RHo two other situations in which we could show the indicator, but i'm not sure if it's necessary:

  • someone arrives at the page with a screen 1000px wide (or less), in which case the TOC will automatically be hidden
  • someone resizes their screen to be 1000px (or less), in which case the TOC will automatically be hidden

Hi @alexhollender_WMF - I think it would be valuable to show this tooltip, esp. the first situation for long time readers/editors with narrow screens who might wonder where the ToC went.

Thu, Jun 23, 4:25 PM · Readers-Web-Backlog, Design-Systems-Team, Desktop Improvements
RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Thu, Jun 23, 3:34 PM · Epic, Codex, Design-Systems-Team
RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Thu, Jun 23, 3:33 PM · Epic, Codex, Design-Systems-Team
RHo updated the task description for T311228: Revise design of the Mentee overview filter for recent days.
Thu, Jun 23, 3:23 PM · Growth-Team, GrowthExperiments-MentorDashboard
RHo updated the task description for T303320: Design Table component.
Thu, Jun 23, 1:10 PM · Design, Codex, Design-Systems-team-20200324-20220422 (Design Systems Team FY2021-22 Kanban Board)
RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Thu, Jun 23, 1:03 PM · Epic, Codex, Design-Systems-Team
RHo created T311228: Revise design of the Mentee overview filter for recent days.
Thu, Jun 23, 12:53 PM · Growth-Team, GrowthExperiments-MentorDashboard
RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Thu, Jun 23, 12:43 PM · Epic, Codex, Design-Systems-Team
RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Thu, Jun 23, 12:42 PM · Epic, Codex, Design-Systems-Team
RHo added a comment to T277047: Epic: Do a design inventory of Wikiverse (Design Style Guide, Codex, OOUI, WVUI, MediaWiki widgets) UI components.

Addendum: wanted to confirm if part of this process of adding the Codex tickets would be de-duplicate tasks where a new Codex task has been created for an existing task - T309249 for chips, when there was already T280701, etc

Thu, Jun 23, 12:26 PM · Design-Systems-Team, Epic, UI-Standardization, Wikimedia Design Style Guide
RHo added a comment to T277047: Epic: Do a design inventory of Wikiverse (Design Style Guide, Codex, OOUI, WVUI, MediaWiki widgets) UI components.

Hi @Volker_E and @bmartinezcalvo - curious if we should either close this task or keep it updated with the main Codex components development work? Asking as I am finding new Codex tasks for components that are duplicates of tasks detailed here, for example the table component tickets T280727 and T303320.

@RHo I think we should keep Codex updated and create a column for the Codex components links in this table since now it has columns just for DSG, OOUI and WVUI but Codex is missing. We could also link the Phab tasks to each column if possible, to be able to easily find them and detect if we have duplicated tasks.

Captura de Pantalla 2022-06-23 a las 11.45.23.png (236×874 px, 78 KB)

Thu, Jun 23, 12:19 PM · Design-Systems-Team, Epic, UI-Standardization, Wikimedia Design Style Guide
RHo awarded T310833: Uploaded files via the drag-and-drop are defaulting to private-access a Love token.
Thu, Jun 23, 12:18 PM · Upstream, Phabricator (Upstream), User-brennen, Release-Engineering-Team
RHo added a comment to T310320: Account creation + Growth tools: improve UX for newcomers who create an account while mid-edit.

image.png (266×432 px, 26 KB)

@KStoller-WMF @RHo IMO we should provide a button to let the user not proceed ("Close"), "Go to my homepage" could be the progressive, blue button of course to entice the user to go there. But the user might want to admire their edit or otherwise interact with the page they're on before going on to Special:Homepage.

Yes, you're right @kostajh, that was my oversight. I've added the second close CTA to the dialog now.

image.png (354×462 px, 32 KB)

Thu, Jun 23, 12:10 PM · Growth-Team (Current Sprint)

Wed, Jun 22

RHo added a comment to T310833: Uploaded files via the drag-and-drop are defaulting to private-access.

+1 it would be super appreciated if this can be resolved soon. It is causing more work and lost time for design team folks who tend to upload a fair amount of images on tasks. Besides the added steps needed right now, the fact that a person uploading or copy+pasting can see the image makes it easy to forget to even take those extra steps to change view permissions/attach the file.

Wed, Jun 22, 7:01 PM · Upstream, Phabricator (Upstream), User-brennen, Release-Engineering-Team
RHo awarded T310833: Uploaded files via the drag-and-drop are defaulting to private-access a Burninate token.
Wed, Jun 22, 6:46 PM · Upstream, Phabricator (Upstream), User-brennen, Release-Engineering-Team
RHo added a comment to T303522: Decide on CSS breakpoints for the design system.

Thanks @bmartinezcalvo, this latest proposal with four breakpoints looks good to me!
Though I think there is a typo on breakpoint-M - I assume the range should be 1120px to 1679px (not 1799px as it is currently in the mock and figma)... is that right?

Wed, Jun 22, 1:47 PM · Design, Design-Systems-Team (Design-Systems-Sprint), Codex

Tue, Jun 21

RHo attached a referenced file: F35259826: image.png.
Tue, Jun 21, 11:33 PM · Epic, Codex, Design-Systems-Team
RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Tue, Jun 21, 12:13 PM · Epic, Codex, Design-Systems-Team
RHo updated subscribers of T280677: Revise and extend the info / help tooltip pop-up in our design component library.

adding @Prtksxna and @bmartinezcalvo as this is being worked on (?) for IP info.

Tue, Jun 21, 11:49 AM · OOUI, Wikimedia Design Style Guide
RHo updated subscribers of T277047: Epic: Do a design inventory of Wikiverse (Design Style Guide, Codex, OOUI, WVUI, MediaWiki widgets) UI components.

Hi @Volker_E and @bmartinezcalvo - curious if we should either close this task or keep it updated with the main Codex components development work? Asking as I am finding new Codex tasks for components that are duplicates of tasks detailed here, for example the table component tickets T280727 and T303320.

Tue, Jun 21, 11:31 AM · Design-Systems-Team, Epic, UI-Standardization, Wikimedia Design Style Guide
RHo updated subscribers of T303320: Design Table component.

hi @bmartinezcalvo and @Volker_E - should this task be merged with T280727?

Tue, Jun 21, 11:27 AM · Design, Codex, Design-Systems-team-20200324-20220422 (Design Systems Team FY2021-22 Kanban Board)

Thu, Jun 16

RHo changed the visibility for F35247609: image.png.
Thu, Jun 16, 8:24 PM
RHo changed the visibility for F35247609: image.png.
Thu, Jun 16, 8:24 PM
RHo changed the visibility for F35247609: image.png.
Thu, Jun 16, 8:20 PM
RHo changed the visibility for F35247609: image.png.
Thu, Jun 16, 8:18 PM
RHo changed the visibility for F35247609: image.png.
Thu, Jun 16, 8:17 PM
RHo changed the visibility for F35236001: image.png.
Thu, Jun 16, 7:35 PM
RHo changed the visibility for F35239729: image.png.
Thu, Jun 16, 7:35 PM
RHo changed the visibility for F35240562: image.png.
Thu, Jun 16, 7:35 PM
RHo changed the visibility for F35247457: image.png.
Thu, Jun 16, 7:23 PM
RHo added a comment to T310320: Account creation + Growth tools: improve UX for newcomers who create an account while mid-edit.

After discussion with @KStoller-WMF, what I suggested above is amended slightly so that the dialog after a new account creates an edit will only have the single CTA to go to the homepage. To recap, the following is proposal for this task:

Thu, Jun 16, 12:18 PM · Growth-Team (Current Sprint)

Tue, Jun 14

RHo updated the task description for T306025: [EPIC] Add ButtonGroup component to Codex.
Tue, Jun 14, 4:24 PM · Epic, Codex, Design-Systems-Team
RHo added a comment to T303522: Decide on CSS breakpoints for the design system.

Hi @bmartinezcalvo, thanks for the ping for feedback. I mostly agree with this proposal and it fits in with the 3 layouts we use on the Growth Desktop version of the homepage (see this task T258005 for reference to the responsive breakpoints we have set, and demo the page live at testwiki at Special:Homepage).

Tue, Jun 14, 1:15 PM · Design, Design-Systems-Team (Design-Systems-Sprint), Codex

Mon, Jun 13

RHo added a comment to T310320: Account creation + Growth tools: improve UX for newcomers who create an account while mid-edit.

@kostajh my understanding is that this task is separate from T267273 , but certainly could be done in tandem if you think that makes sense.

It is separate, but T267273 touches the same areas of code, so if the specification is finalized I could incorporate the changes now. But on second thought, I'll just finish up with T267273 and keep in mind that we may make updates to it soon. :)

This isn't urgent, but something I think we should pull in soon based on results from @nettrom_WMF 's NEWTEA Revisted data analysis. I wanted to be sure to discuss it with you and @RHo first, since I don't know enough about the account creation flow to know if it's even possible to just wait until after an edit to present the welcome survey and "get started here"

Maybe we could do a custom version of the post-edit dialog for these users. The dialog would invite them to visit Special:Homepage or to take the welcome survey.

@RHo any thoughts on presenting the Welcome Survey later from the Special:Homepage? Or could/should we consider skipping the welcome survey in this case (as we already have a clear indication as to why they are creating their account).

In previous iterations of the homepage, we had a "Start" module that prompted the user to confirm their email, create a user page, and read a tutorial. We could probably bring back something like that again, and have it include a step for filling out the survey.

Mon, Jun 13, 4:30 PM · Growth-Team (Current Sprint)
RHo added a comment to T301537: Reduce size of intro-heart-article.svg.

Kosta mentioned this task in chat, so I figured I'd take a look.

Thank you @Krinkle!

According to Codesearch, this cool artwork is used on Special:Impact via this stylesheet:

		&-image {
			width: 160px;
			height: 130px;
			background: url( ../../images/intro-heart-article.svg ) no-repeat center;

Assuming we optimise for 144 dpi (aka 2 dppx, or "Retina"), this means we need to render 320x260px under the hood.

When I take a simple screenshot of https://en.wikipedia.org/w/extensions/GrowthExperiments/images/intro-heart-article.svg rendered at 260px height, I get a PNG that after losless optimisation is 56KB, a 50% reduction.

capture-320px-opt.png (260×320 px, 55 KB)

If we convert that to a high 90%-quality JPEG and run it through again, we get a 19KB file, a 90% reduction compared to the SVG.

capture-320px-opt.jpg (260×320 px, 18 KB)

Also consider https://squoosh.app/ for a visual picking what works best for a given image.

@RHo @KStoller-WMF does the JPEG file look OK for you to use in place of the SVG? 110KB to 19KB is a fairly significant reduction, and translates to less bandwidth used and a faster loading experience for our users.

Mon, Jun 13, 2:26 PM · Growth-Team (Current Sprint), Growth-Scaling, Performance Issue, Growth Design, GrowthExperiments
RHo added a comment to T310443: make the spelling of "copy editing" consistent.

No strong opinion but changes seems fine to me.

Mon, Jun 13, 2:21 PM · Growth-Team (Current Sprint), Patch-For-Review, MediaWiki-extensions-GettingStarted, GrowthExperiments
RHo added a comment to T307488: Have a way for mentors to opt-out from a mentee.

I agree with @Urbanecm_WMF that the most apt course of action for this (hopefully very edge) case is to disable the men tor module for the newcomer. However, we should provide some message that says something along the lines of "Your mentor has opted out of mentoring you. No other mentors are available right now, but you can get more help on editing via the <link to Help desk/Help articles>." That way the mentee knows what has happened and can still get help via other channels. And perhaps still then they still have the option to request another mentor when someone new is available in future if they so choose (since we may get new mentors at some point that may have better luck with this person).
I do think that to some extent the newcomer probably wouldn't be that shocked by the mentor opting out since in this case they have had some negative interaction with that mentor in the first place to cause the mentor to want to remove them without being able to/wanting to find a suitable replacement mentor.

Mon, Jun 13, 10:47 AM · GrowthExperiments-Mentorship, Growth-Team

Wed, Jun 8

RHo updated subscribers of T220139: Homepage Impact: Filter/Sort options to customize the top edited articles of the impact module.

@RHo I see this feature request is also reflected in the positive reinforcement figma designs. Is this change something we would like to ship before the rest of impact module changes or are we planning to deliver it as part of the rest of imapct module changes?

Wed, Jun 8, 6:48 PM · Growth-Positive-Reinforcement, Growth-Team-Filtering, Wikimania-Hackathon-2019, Wikimedia-Hackathon-2019, GrowthExperiments
RHo added a comment to T277189: Consider applying 960px max-width to Newcomer Homepage.

Thanks for proposing this @alexhollender. I agree that the desktop newcomer homepage layout is already pretty optimised to work well in that 960 max width. One caveat may be changing the order and layout of the "secondary" modules on the RHS since this would mean that the mentor module is always below the impact module, whereas currently there is a wider view on desktop which would show the mentor module 'above the fold' as a third column:

image.png (1×3 px, 557 KB)

@RHo any new thoughts here? I'm certainly biased...still prefer the limited width : ) Maybe even having the three columns side-by-side (shown in your screenshot above) could be overwhelming?

Wed, Jun 8, 6:44 PM · Wikimedia-Site-requests, Readers-Web-Backlog (Tracking), Growth-Team-Filtering, Growth-Team, Desktop Improvements
RHo updated subscribers of T275783: Revisit styling of "Create account" link in X months.

@RHo several months have passed. What do we want to do about this ticket?

Wed, Jun 8, 5:21 PM · Growth-Team-Filtering, Growth-Team, Desktop Improvements

Mon, Jun 6

RHo added a comment to T286466: Persistent contribution entry point on the mobile navigation menu.

I agree this is a desirable new entry point to Growth's suggested edits as well, but have some comments and questions:

Thanks for the input @RHo, all good points. I'll add some details and context below.
The current desktop version was created as part of Content Translation initial release with the intention to provide an entry point to translation but avoiding it to be another one-off solution and start to test the idea of. have a more general contribution entry point. Building such general entry point fully was out of the scope, so a couple of easy-to-add options were considered to avoid "translation" to be the only one. This allowed to try the idea that we are refining on mobile, even if it was using a sub-optimal architecture (e.g., disabling Content Translaiton removes all options to contribute, not just translation).

  • Desktop vs Mobile - I'm a little unsure about the scope of this task. Is the intention to apply this tabbed separation only to Minerva? If so, curious why we would not consider the benefits of consistency in having this separated in Desktop as two tabs as well.

This task is focused on mobile, as a first step. This time the intention is to have a more clean architecture where different projects can add to the list of entry points. Exposing this new approach on desktop makes sense as a next step. We need to define the details about how the entry point will be presented on desktop to replace the current solution (old approach).

Gotcha, thanks that makes sense.

Mon, Jun 6, 3:40 PM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), MediaWiki-Core-Skin-Architecture (Menus 2.0), Language-Team (Language-2022-April-June), Campaign-Registration, Inuka-Team, Campaign-Tools, Readers-Web-Backlog, MobileFrontend, SectionTranslation
RHo closed T275485: Positive reinforcement: Design brief as Resolved.
Mon, Jun 6, 1:15 PM · GrowthExperiments-NewcomerTasks, Growth-Team (Current Sprint)
RHo closed T275485: Positive reinforcement: Design brief, a subtask of T248330: [EPIC] Growth: Positive reinforcement, as Resolved.
Mon, Jun 6, 1:15 PM · Growth-Positive-Reinforcement, Growth-Team, Epic
RHo closed T307992: Positive reinforcement: Create target-language mocks for user study , a subtask of T307950: Positive reinforcement: User research to understand positive feedback and incentives to newcomer contribution, as Resolved.
Mon, Jun 6, 1:13 PM · GrowthExperiments-NewcomerTasks, Growth-Team (Current Sprint)
RHo closed T307992: Positive reinforcement: Create target-language mocks for user study as Resolved.
Mon, Jun 6, 1:13 PM · GrowthExperiments-NewcomerTasks, Growth-Team (Current Sprint)
RHo updated the task description for T307992: Positive reinforcement: Create target-language mocks for user study .
Mon, Jun 6, 1:13 PM · GrowthExperiments-NewcomerTasks, Growth-Team (Current Sprint)

Fri, Jun 3

RHo closed T203941: Allow watchlist notifications to be delivered as web notification (through Echo), a subtask of T125653: Create new types of notifications, as Resolved.
Fri, Jun 3, 10:41 AM · Growth-Team-Filtering, Growth-Team, Tracking-Neverending, Notifications
RHo closed T203941: Allow watchlist notifications to be delivered as web notification (through Echo) as Resolved.

Thanks @Etonkovidova for the notes and thanks @kostajh for the update to the first note about prepending Talk: when it's in that namespace. It looks like the second issue with topic subscriptions is covered in T299874 already, so will resolve this task. Awesome update!

Fri, Jun 3, 10:41 AM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), MW-1.38-notes (1.38.0-wmf.16; 2022-01-03), Growth community maintenance, Growth-Team (Current Sprint), Patch-For-Review, MW-1.35-notes (1.35.0-wmf.11; 2019-12-17), Google-Code-in-2019, WMSE-Bug-Reporting-and-Translation-2018, MediaWiki-Watchlist, Notifications
RHo moved T304099: Structured tasks: temporary free text for "other" rejection reason from Needs Design/Design Doing to Ready for Development on the Growth-Team (Current Sprint) board.

@RHo , should we remove this task from the current sprint board? Are you planning to work on this any time soon?

Fri, Jun 3, 10:33 AM · MW-1.39-notes (1.39.0-wmf.18; 2022-06-27), Patch-For-Review, Growth-Team (Current Sprint), Add-Link, Growth-Structured-Tasks

Wed, Jun 1

RHo updated the task description for T220141: Homepage Impact: "sparkline" style graph that shows pageviews over time.
Wed, Jun 1, 9:26 PM · Growth-Team-Filtering, Wikimania-Hackathon-2019, Wikimedia-Hackathon-2019, Growth-Team, GrowthExperiments
RHo updated the task description for T220141: Homepage Impact: "sparkline" style graph that shows pageviews over time.
Wed, Jun 1, 8:57 PM · Growth-Team-Filtering, Wikimania-Hackathon-2019, Wikimedia-Hackathon-2019, Growth-Team, GrowthExperiments
RHo renamed T220139: Homepage Impact: Filter/Sort options to customize the top edited articles of the impact module from Homepage Impact: Dropdowns or controls to customize the content of the impact module to Homepage Impact: Filter/Sort options to customize the top edited articles of the impact module.
Wed, Jun 1, 8:37 PM · Growth-Positive-Reinforcement, Growth-Team-Filtering, Wikimania-Hackathon-2019, Wikimedia-Hackathon-2019, GrowthExperiments
RHo updated the task description for T248636: Newcomer tasks: update time period used in page views count on newcomer homepage from 60 days to 30 days.
Wed, Jun 1, 8:28 PM · Growth-Team-Filtering, Growth-Team, GrowthExperiments
RHo renamed T220143: Homepage Impact: Provide an option to show pageviews earlier than the 60-day limit from the PageViewInfo extension from Homepage Impact: show pageviews earlier than the 60-day limit from the PageViewInfo extension to Homepage Impact: Provide an option to show pageviews earlier than the 60-day limit from the PageViewInfo extension.
Wed, Jun 1, 8:27 PM · Growth-Team-Filtering, Wikimania-Hackathon-2019, Wikimedia-Hackathon-2019, GrowthExperiments, Growth-Team

Tue, May 31

RHo updated the task description for T309614: Newcomer tasks: add intermediate loading state.
Tue, May 31, 7:02 PM · Growth-Team-Filtering, GrowthExperiments-NewcomerTasks, Growth-Team
RHo updated the task description for T278311: [EPIC] Add Card component to Codex.
Tue, May 31, 3:02 PM · Epic, Design-Systems-Team, Codex, Design, Wikimedia Design Style Guide
RHo added a comment to T309247: Add BouncingDots component to Codex.

Note this is a type of progress indicator that is captured in T266028

Tue, May 31, 2:41 PM · Epic, Codex, Design-Systems-Team
RHo added a comment to T266028: Add “Progress indicators” to DSG.

Note that there is a separate task for 3-dots progress indicator here: T309247: Add BouncingDots component to Codex

Tue, May 31, 2:40 PM · MW-1.37-notes (1.37.0-wmf.3; 2021-04-27), Wikimedia Design Style Guide
RHo added a comment to T242414: Consider adding suggestion widget to OOUI.

Maybe this is something that will happen when we migrate to Vue.

Tue, May 31, 2:24 PM · Growth-Team-Filtering, Structured-Data-Backlog, MachineVision, OOUI, Growth-Team, GrowthExperiments
RHo added a comment to T256036: Add Card component to Codex.

Exploration starting now, toward end of the current sprint. We will be discussing the Card component further this week with the Readers Web Team

Tue, May 31, 10:31 AM · Design-Systems-Team, Design, Codex

Mon, May 30

RHo added a comment to T308008: Number of "found articles" is not matching the real number of articles.

As discussed during reviews ( gerrit 793035 ) and meetings the filtering of protected pages would benefit from having T259346: Add page protection filter to CirrusSearch in place and improving the protection filter to make just one single query per-taskset as opposed of per-task, see T309535: ProtectionFilter::filter should make a single query per task set.

The changes in gerrit 793511 are:

  • Show the "next button" in an ellipsis state while a request to fetch more tasks is being made, preventing the "End of queue" state to show in between task feed navigation.
BeforeWith patch
Screenshot 2022-05-30 at 15.42.33.png (1×1 px, 125 KB)
Screenshot 2022-05-30 at 15.19.11.png (1×1 px, 195 KB)
icon color is black and it is clickableicon color is grey and not clickable
  • In the pager widget copy text n of M suggestions, update the M with the (real) number of tasks fetched, on the last chunk of tasks fetched. This prevents the "End of queue" state to show at an "unexpected" end of the queue.
BeforeWith patch
... 10 of 17 suggestions, click next, 11 of 17 suggestions, click next, 12 of 17 suggestions, click next, End of 17 suggestions...10 of 17 suggestions, click next, 11 of 12 suggestions, click next, 12 of 12 suggestions, click next, End of 12 suggestions
  • On mobile, when the user navigates to the "End of the queue" and then navigates to the hompeage using the back button (Top corner arrow) the "Suggested edits" module shows the last day edits counter widget. IMO this is miss-leading since there are still tasks in the queue. This patch will force the last task in the queue to render in such scenario. @RHo could you confirm this behavior improves the status quo or which would be the desired outcome? Ty.
Mon, May 30, 2:12 PM · Patch-For-Review, Growth-Team (Current Sprint), GrowthExperiments-NewcomerTasks, GrowthExperiments-Homepage
RHo updated subscribers of T309403: Improved Watchlist and revision UI prototype with Codex.

Thanks for sharing @Tgr - this is a good exploration for when we want to revise the page to use Codex. cc @Volker_E and @bmartinezcalvo

Mon, May 30, 11:12 AM · Growth-Team, Design, MediaWiki-Watchlist
RHo renamed T309403: Improved Watchlist and revision UI prototype with Codex from Improved Watchlist and revision UI prototype to Improved Watchlist and revision UI prototype with Codex.
Mon, May 30, 11:08 AM · Growth-Team, Design, MediaWiki-Watchlist

May 27 2022

RHo added a comment to T292627: Mentorship: Provide more information about the public nature of the mentors and talk pages in the Mentor module.

@Urbanecm_WMF - I checked on cswiki wmf.13 - some text is not present; is it still a work-in-progress task?

Desktop cswiki wmf.13Mobile cswiki wmf.13
Screen Shot 2022-05-26 at 1.04.43 PM.png (852×650 px, 99 KB)
Screen Shot 2022-05-26 at 11.49.53 AM.png (880×1 px, 194 KB)
Screenshot_20220526-122700_Chrome.jpg (2×1 px, 306 KB)
Screenshot_20220526-122711_Chrome.jpg (2×1 px, 337 KB)
Screenshot_20220526-122723_Chrome.jpg (2×1 px, 448 KB)

@RHo The line space looks a little bit tight.

Screen Shot 2022-05-26 at 11.49.53 AM.png (880×1 px, 194 KB)

Agree. @MUrbanec - could this please use the same line-height as paragraph text (line-height:1.6)? Thank you!

May 27 2022, 12:02 PM · MW-1.39-notes (1.39.0-wmf.18; 2022-06-27), User-Urbanecm_WMF (Engineering), Growth-Team (Current Sprint), GrowthExperiments-Mentorship
RHo added a comment to T284088: Merge preference "Enable the editor help panel" with "Display the newcomer homepage" together.

Currently, the Help (or the guidance panel) will be always present for SE tasks (structured or non-structured).

Checked in betalabs on desktop and mobile when

  • a user has opted out from mentorship
  • a user has global settings for Homepage and Help panel with local exclusions
  • a user disables Homepage but enabled Help panel

The task's Acceptance criteria were updated.

@MMiller_WMF, @RHo - when the Help panel is disabled, and, since SE tasks are still displaying it, there is a link on the panel referring to the Help panel documentation (https://www.mediawiki.org/wiki/Help:Growth/Tools/Help_panel).

Screen Shot 2022-05-25 at 5.36.16 PM.png (1×798 px, 114 KB)

Questions:

  • is it ok to refer to the Help panel even though a user intentionally disabled it?

Yes, since the distinction from the design/user perspective is that the panel that opens in Suggested edits is meant to be a specific "Guidance panel for fo suggested edits". It just so happens that a user can access help panel content additionally if they wish. The confusion IMO is caused from calling it by the same name because it was implemented as an extension of the help panel.

Perhaps updating the documentation to make the distinction above of Guidance vs Help panel would make it more clear? Not sure.

May 27 2022, 10:57 AM · MW-1.39-notes (1.39.0-wmf.14; 2022-05-30), MW-1.38-notes (1.38.0-wmf.5; 2021-10-19), Growth-Team (Current Sprint), Add-Link, Growth-Structured-Tasks
RHo added a comment to T305659: Account creation: Thank You Page landing pages.

@Etonkovidova if it helps, I was able to replicate the issue described:

  • Open Chrome incognito browser from your desktop computer
  • Navigate to: en.m.wikipedia.org/wiki/Special:CreateAccount
  • Create an account
  • After the account is created, I land on https://en.wikipedia.org/wiki/Special:CentralLogin/complete (no longer on the mobile version) and I see that "No active login attempt is in progress for your session" error.

But my understanding is that this issue is probably a result of testing a use case that is unlikely to happen outside of testing (testing a mobile URL from desktop). Does that seem accurate?

There was some prior discussion (task?) about this but I can't find it. IMO we should just add configurable help text to the username field. That would look something like this:

Screenshot Capture - 2022-05-20 - 00-06-59.png (750×913 px, 163 KB)

@Tgr I agree, that looks better. Should I create a separate task for this? (Would that actually be a Growth task?)

Should we consider this task done or is there unmet acceptance criteria?

May 27 2022, 5:28 AM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), Patch-For-Review, Growth-Team (Current Sprint)

May 25 2022

RHo added a comment to T309149: Mobile Create Account page does not immediately validate username.

LGTM

Screen Shot 2022-05-25 at 12.03.03 PM.png (1×1 px, 157 KB)

Screen Shot 2022-05-25 at 12.07.48 PM.png (1×1 px, 179 KB)

Thanks for the screenshots. IMHO it would be an improvement to add this, if design adjustments are desired it could be done in a follow-up. (The patch just enables the existing form validation code used on desktop for mobile.) @RHo or @KStoller-WMF, do you have an opinion on this?

May 25 2022, 8:15 PM · Growth-Team (Current Sprint), MinervaNeue, MediaWiki-User-login-and-signup

May 23 2022

RHo added a comment to T295670: Allow for retrying timed out requests in GrowthTasksApi.

@RHo we're using MediaWiki's API helper class, which sets a default value of 30 seconds for the XMLHttpRequest timeout value. We could lower or raise that number. Maybe something like 10 seconds is closer to the upper limit of what users would tolerate, so if the request hasn't finished by then, we should offer that they can manually retry it.

Yes, maybe 15seconds (to split the difference) before there is a dialog or message with an action to retry?

That sounds good to me; I think the next step would be to think about what the UX would look like (a popup dialog with a button to retry, like VisualEditor has?), and what the wording should be. And it should probably be instrumented as well.

How about something like this:

image.png (368×670 px, 35 KB)

It uses the OOUI name | Message dialog (2 actions)]] and I was thinking the following message copy:
Heading: Request timed out
Text: The request took too long to respond. Would you like to retry?
Primary (progressive) CTA button label: Try again

That looks good to me, though I'd suggest a minor change on the wording to: The request took too long to complete. Would you like to retry?

May 23 2022, 11:22 AM · Growth-Team (Current Sprint), JavaScript, GrowthExperiments-Homepage, Wikimedia-production-error

May 20 2022

RHo added a comment to T295670: Allow for retrying timed out requests in GrowthTasksApi.

@RHo we're using MediaWiki's API helper class, which sets a default value of 30 seconds for the XMLHttpRequest timeout value. We could lower or raise that number. Maybe something like 10 seconds is closer to the upper limit of what users would tolerate, so if the request hasn't finished by then, we should offer that they can manually retry it.

Yes, maybe 15seconds (to split the difference) before there is a dialog or message with an action to retry?

That sounds good to me; I think the next step would be to think about what the UX would look like (a popup dialog with a button to retry, like VisualEditor has?), and what the wording should be. And it should probably be instrumented as well.

How about something like this:

image.png (368×670 px, 35 KB)

It uses the OOUI name | Message dialog (2 actions)]] and I was thinking the following message copy:
Heading: Request timed out
Text: The request took too long to respond. Would you like to retry?
Primary (progressive) CTA button label: Try again

May 20 2022, 11:41 AM · Growth-Team (Current Sprint), JavaScript, GrowthExperiments-Homepage, Wikimedia-production-error
RHo closed T308241: [Visual design] Newcomer tasks: Suggested edits mobile preview when there are zero tasks - fix visual regression/discrepancies as Resolved.

Moving for @RHo to take a quick look - seems all fine to me. There seems to be a small issue (unrelated to this task) for RTL where the text "edits in the last days" is place a little too tight to the image

IMG_0944.PNG (1×640 px, 175 KB)
.

Thanks @Etonkovidova - agree this is a different RTL issue which I've filed as T308846. I have a funny feeling this may be regression as I swear we fixed this before.

May 20 2022, 11:23 AM · MW-1.39-notes (1.39.0-wmf.12; 2022-05-16), Regression, Growth-Team (Current Sprint)
RHo triaged T308846: [Minor] Mobile newcomer homepage on RTL - zero tasks Suggested edits preview illustration is not aligned to the Start (left) of the preview. as Medium priority.
May 20 2022, 11:22 AM · Growth-Team
RHo created T308846: [Minor] Mobile newcomer homepage on RTL - zero tasks Suggested edits preview illustration is not aligned to the Start (left) of the preview. .
May 20 2022, 11:22 AM · Growth-Team
RHo closed T302335: Suggested edits: show the full task feed on post-edit dialog as Resolved.

LGTM, thank you!

May 20 2022, 11:12 AM · MW-1.39-notes (1.39.0-wmf.12; 2022-05-16), Growth-Team (Current Sprint)
RHo closed T302335: Suggested edits: show the full task feed on post-edit dialog, a subtask of T300851: [EPIC] Growth: "add a link" structured task 2.0, as Resolved.
May 20 2022, 11:12 AM · Growth-Team (Current Sprint), Add-Link, Epic
RHo renamed T308787: [minor] Help panel menu button illustrations are not vertically aligned to bottom from [minor] "mw-ge-help-panel-home-button-image" placement in Help panel to [minor] Help panel menu button illustrations are not vertically aligned to bottom.
May 20 2022, 11:08 AM · MW-1.39-notes (1.39.0-wmf.14; 2022-05-30), Growth-Team (Current Sprint), GrowthExperiments-Help panel

May 19 2022

RHo added a comment to T305659: Account creation: Thank You Page landing pages.

hi all, thanks for the work on these so far! I was looking through the Prod URLs and noticed/wondered two things related to the "Consider using a username other than your real name, as usernames are public and cannot be made private later." text:

  • It's only present on the English pages. should it be present, translated, on es and pt pages?

Hi @HNordeenWMF - this text was added by an enwiki admin on their own steam, so no, it doesn't need to be added to other language wikis.

May 19 2022, 9:40 PM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), Patch-For-Review, Growth-Team (Current Sprint)

May 18 2022

RHo added a comment to T295670: Allow for retrying timed out requests in GrowthTasksApi.

I'm not sure that there is anything to do here? Sometimes requests time out. I suppose we could present a message to the user that this is happening with a prompt to retry the request (the request is to fetch suggested edits tasks, usually) and not log the error? @RHo what do you think?

I might need a little more context but I'm firstly curious if we know on average how long before it times out? If it was 20-30sec then an error message and retry action definitely makes sense, but would not want it to be much longer than that. If it was 2min then pretty sure that person already closed the window and perhaps we could look at introducing some other indicator like progress or messaging to let the person know that something is still being fetched until it fails.

@RHo we're using MediaWiki's API helper class, which sets a default value of 30 seconds for the XMLHttpRequest timeout value. We could lower or raise that number. Maybe something like 10 seconds is closer to the upper limit of what users would tolerate, so if the request hasn't finished by then, we should offer that they can manually retry it.

Yes, maybe 15seconds (to split the difference) before there is a dialog or message with an action to retry?

May 18 2022, 4:59 PM · Growth-Team (Current Sprint), JavaScript, GrowthExperiments-Homepage, Wikimedia-production-error
RHo renamed T294835: Add an image: Revise skeleton state and behaviour of the Post-edit dialog from Add an image: Create a skeleton state of the Post-edit dialog to Add an image: Revise skeleton state and behaviour of the Post-edit dialog.
May 18 2022, 4:00 PM · Growth-Structured-Tasks, Growth-Team, Image-Suggestions
RHo updated the task description for T294835: Add an image: Revise skeleton state and behaviour of the Post-edit dialog.
May 18 2022, 3:57 PM · Growth-Structured-Tasks, Growth-Team, Image-Suggestions
RHo added a comment to T307752: [wmf.10] Homepage - Mentorship module: on hover mentor username displays cross line.

Screen Shot 2022-05-17 at 9.50.34 AM.png (186×386 px, 14 KB)

Not in the scope of this task but some how related, maybe @Urbanecm_WMF can help to clarify:

Is the text-decoration under the Mentor name when hovering the icon a desired feature?

Screenshot 2022-05-18 at 10.19.56.png (570×830 px, 55 KB)

Also I see the link has a yellow/orange color when in the "active" state. Is this meeting design requirements?

Screenshot 2022-05-18 at 10.22.36.png (570×830 px, 51 KB)

The color does not follow WCAG standards. Is this a known issue?

Screenshot 2022-05-18 at 10.25.33.png (1×3 px, 524 KB)

That's not good. We are using the existing styles from OOUI and Vector/Minerva though as it is expected to be conformant, and I see this is an issue with links on many content pages not just the homepage. For example here's the active state on the Special:Preferences screen:

image.png (1×2 px, 388 KB)

May 18 2022, 3:55 PM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), Browser-Support-Firefox, Growth-Team (Current Sprint), GrowthExperiments-Homepage
RHo changed the status of T253778: Newcomer tasks: post-edit dialog animations, a subtask of T245790: Newcomer tasks: post-edit dialog, from Resolved to Invalid.
May 18 2022, 3:00 PM · MW-1.35-notes (1.35.0-wmf.36; 2020-06-09), NewcomerTasks 1.2, Growth-Team (Current Sprint)
RHo changed the status of T253778: Newcomer tasks: post-edit dialog animations from Resolved to Invalid.
May 18 2022, 3:00 PM · Growth-Team-Filtering, Growth-Team, NewcomerTasks 1.2
RHo closed T253778: Newcomer tasks: post-edit dialog animations, a subtask of T245790: Newcomer tasks: post-edit dialog, as Resolved.
May 18 2022, 3:00 PM · MW-1.35-notes (1.35.0-wmf.36; 2020-06-09), NewcomerTasks 1.2, Growth-Team (Current Sprint)
RHo closed T253778: Newcomer tasks: post-edit dialog animations as Resolved.

Closing this as this has been superseded by changes implemented in T301603: Newcomer tasks: increased flexibility at post-edit dialog

May 18 2022, 3:00 PM · Growth-Team-Filtering, Growth-Team, NewcomerTasks 1.2
RHo moved T308669: Add image: Add "Suggestion reason:" label before the suggestion reason in the image inspector from Inbox to Triaged on the Growth-Team board.
May 18 2022, 1:31 PM · NewcomerTasks Future Release , Image-Suggestions, Growth-Team
RHo triaged T308669: Add image: Add "Suggestion reason:" label before the suggestion reason in the image inspector as Medium priority.
May 18 2022, 1:31 PM · NewcomerTasks Future Release , Image-Suggestions, Growth-Team
RHo created T308669: Add image: Add "Suggestion reason:" label before the suggestion reason in the image inspector.
May 18 2022, 1:31 PM · NewcomerTasks Future Release , Image-Suggestions, Growth-Team
RHo moved T287915: Mentorship: allow newcomers to opt-in and opt-out of mentorship from Design Review to In Progress on the Growth-Team (Current Sprint) board.

Hi @Urbanecm_WMF - thanks for your work so far. As @Etonkovidova picked up in QA, there are some differences in the mocks that I wanted to get fixed.

May 18 2022, 12:40 PM · MW-1.39-notes (1.39.0-wmf.16; 2022-06-13), User-notice, MW-1.38-notes (1.38.0-wmf.22; 2022-02-14), Patch-For-Review, User-Urbanecm_WMF (Engineering), Growth-Team (Current Sprint), GrowthExperiments-Mentorship

May 17 2022

RHo added a comment to T286466: Persistent contribution entry point on the mobile navigation menu.

I agree this is a desirable new entry point to Growth's suggested edits as well, but have some comments and questions:

May 17 2022, 1:04 PM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), MediaWiki-Core-Skin-Architecture (Menus 2.0), Language-Team (Language-2022-April-June), Campaign-Registration, Inuka-Team, Campaign-Tools, Readers-Web-Backlog, MobileFrontend, SectionTranslation

May 16 2022

RHo added a comment to T295670: Allow for retrying timed out requests in GrowthTasksApi.

I'm not sure that there is anything to do here? Sometimes requests time out. I suppose we could present a message to the user that this is happening with a prompt to retry the request (the request is to fetch suggested edits tasks, usually) and not log the error? @RHo what do you think?

May 16 2022, 4:10 PM · Growth-Team (Current Sprint), JavaScript, GrowthExperiments-Homepage, Wikimedia-production-error

May 12 2022

RHo triaged T308241: [Visual design] Newcomer tasks: Suggested edits mobile preview when there are zero tasks - fix visual regression/discrepancies as Low priority.
May 12 2022, 1:04 PM · MW-1.39-notes (1.39.0-wmf.12; 2022-05-16), Regression, Growth-Team (Current Sprint)
RHo created T308241: [Visual design] Newcomer tasks: Suggested edits mobile preview when there are zero tasks - fix visual regression/discrepancies.
May 12 2022, 1:04 PM · MW-1.39-notes (1.39.0-wmf.12; 2022-05-16), Regression, Growth-Team (Current Sprint)
RHo closed T307637: Long article names break small card title as Resolved.

Checked in betalabs - the UI matches the screenshots in @Sgs the comment above.

  • Mobile

Adding the screenshots for Mobile SE preview:

no description
Screenshot_20220511-133257_Chrome.jpg (2×1 px, 308 KB)
with description
Screenshot_20220511-130600_Chrome.jpg (2×1 px, 340 KB)

@RHo - there is also the case when a user selects filters that return zero results - looks ok?

Screenshot_20220511-131239_Chrome.jpg (2×1 px, 283 KB)

May 12 2022, 12:58 PM · MW-1.39-notes (1.39.0-wmf.12; 2022-05-16), GrowthExperiments-Homepage, Growth-Team (Current Sprint)

May 11 2022

RHo updated the task description for T244930: Newcomer tasks: post-edit nurture for non-suggested edits.
May 11 2022, 3:42 PM · Growth-Team-Filtering, Growth-Team, NewcomerTasks 1.2
RHo updated the task description for T203941: Allow watchlist notifications to be delivered as web notification (through Echo).
May 11 2022, 11:53 AM · MW-1.39-notes (1.39.0-wmf.13; 2022-05-23), MW-1.38-notes (1.38.0-wmf.16; 2022-01-03), Growth community maintenance, Growth-Team (Current Sprint), Patch-For-Review, MW-1.35-notes (1.35.0-wmf.11; 2019-12-17), Google-Code-in-2019, WMSE-Bug-Reporting-and-Translation-2018, MediaWiki-Watchlist, Notifications