Sprint 5 of FY2024-25 Q1
Details
Wed, Nov 6
Change #1065288 abandoned by Jdlrobson:
[mediawiki/extensions/MobileFrontend@master] Adds event attributes
Reason:
I'm abandoning this since https://phabricator.wikimedia.org/T372780 is resolved.
Sep 30 2024
Sep 27 2024
Thank you! I'll talk with @ovasileva about prioritizing these
Thanks @SToyofuku-WMF, I just filed this T375901: User links: Appearance icon shouldn't come between text links and another followup task T375903: User links: Show Donate link in overflow menu on small screens.
Sep 26 2024
- Test Result - PROD
Sep 25 2024
- Test Result - PROD
Sep 23 2024
@Pcoombe that would be great! We'll have to prioritize it and figure out with the team where to put user page links in general vs the appearance menu, but having that tracked would help (thank you!)
Change #1066947 abandoned by Jdlrobson:
[mediawiki/skins/Vector@master] Adds data-event-names to search input and button
Reason:
(Shouldn't be needed any more)
Sep 20 2024
Hi, thanks for working on this! I noticed that at smaller breakpoints this appears between the Search and Appearance icon, and it might be better if it was with the other text links. Not a blocker, just a potential improvement. Should I create a new task for this?
Sep 19 2024
Sep 18 2024
Sep 17 2024
I suggested this as Wikivoyage is the only project where RelatedArticles is enabled on desktop and I felt this data point might be useful given our experiments are on desktop and this analysis on Wikipedia's is mobile only.
Sep 16 2024
@Jdlrobson - also curious why we looked at wikivoyage specifically - is this related to our upcoming experiment in any way?
Thanks for those notes @ovasileva !
Signing this off since I believe there are proper tickets for everything.
Leaving notes here as well for anyone following along:
- I love the visual styling of the machine-generated content. I think it's really good at giving that machine-generated visual cue for those that are not reading the disclaimers
- I think the accordion and the location fit the feature really well
- I like the verified/unverified tags. I wonder if the copy here is correct (I think it also depends on our level of trust in the model itself versus trust in the overall content - see comment below on Simple English)
- I like the level of detail on how the summary was generated and the copy in general
- I would like to push back on using data from simple English alongside this feature (more info on that below)
- I wonder if we can look for other locations for presentation on Minerva. Potentially after the first paragraph/after the infobox
Thank you @jwang! @Jdlrobson, @jwang - curious about how we're measuring impressions here. Which of the following is an impression in this context:
- All pageviews
- All times when related pages is shown (measured by whether someone scrolls to the bottom of the page?)
- Something else?
Sep 13 2024
Read through the backscroll and I understand the issue now - created T374753 and signing this one off!
Sounds good!
❓ The search functionality works as expected and the temporary flash of the recommender is no longer there. This is an odd edge case that you may want to look into If you type a query in the search box, and either press Enter, click Search, or select a search suggestion, then click back on the browser, clear the search field, click out and back into it, there are no recommended articles.
I'll let you sign this off given it concerns the work we'll be doing next sprint!
I've created T374743 to disable the surveys! Nice job all!
Should be testable on beta cluster shortly.
Change #1072793 merged by jenkins-bot:
[mediawiki/extensions/WikimediaMessages@master] Remove donate link in sidebar when it's been moved
Sounds good! I will read the above and create a new ticket, then sign this one off with a link to the new one
Just to summarize the progress here. We've currently deployed the more prominent donate link to the beta cluster for anonymous users, so I'm signing off this ticket based on that criteria.
Worth a follow up tickeT?
For Olga: status of this one is that we had to do a little scramble this week because we figured out the hook we were using had a bug in it (more accurately, we introduced a bug by using it). The correct hook is now in code review, and will hopefully wrap up this ticket