@Isaac All looks good. Merged and deployed.

I did a shallow clone of mediawiki/extensions and mediawiki/skins to look for references to Design Style Guide. I could recursively init submodules of the latter but not of the former due to bad refs.

Thanks!

Does it make sense to keep other meta files besides README? e.g: AUTHORS and LICENSE.

@Bethany On Timeline each year generally have a one line introduction to that year research focuses. Will we add one for 2024?

As the Gerrit repo was out of sync with the GitHub repo the Gitlab repo was missing a dozen commits. So I rebased gitlab/master on top of github/master.

I wonder why it uses so much memory. Locally the image uses less than 200MiB.

I deployed last changes.

{F41726514}

@leila like this?

Just deployed changes.

@Isaac The replacement makes sense. Currently it's impractical to use Twitter/X without being logged in. But if it's desired to keep both we can replace the text links with icon links.

And the design team deployers (@Volker_E and @DDeSouza?) should be onboarded to the new deployment workflow.

It isn't a mockup but a copy of the page from previous editions (2016 to 2023). The images are screenshots of the 2024 page running locally in a simulated 1080p screen. Mobile users are as important than desktop users. I didn't bother with adding images of mobile viewports because there were no significant changes to the layout of the page besides a minor margin fix of the footer element.

Changes done but not yet deployed. I hid/commented the sections without content.

Would this look okay if the pink section links on the left are black? They are still a bit hard to read.

I'm pausing on the hot pink, but sounds good. ;) for accessibility purposes if it's hot pink, consider choosing something from https://meta.wikimedia.org/wiki/Brand/colours

Also found (and fixed) two paragraphs that were missing in the published report:

@leila I tagged you in the merge request to implement the print button. Not sure you're receiving notifications from the Gitlab.

@leila I used the previous report as a template. This block is an artifact from it that I left by mistake and missed on later edits. I did double-check the report for errors but didn't compare the page with the docs side-by-side – a step where I would likely have caught the oversight. Gonna remove it.

@leila Change was made. I will close the task as soon as the change goes live.

Report was published.

@leila
CC: @GEscalante-WMF

@YLiou_WMF Yes. Scheduled for today at 9pm UTC.

1. Undeployment status

@YLiou_WMF Scheduled for tomorrow (Dec 12) at 2pm UTC.

@Jdrewniak I estimate 1-2 weeks at max as that is the typical duration of a QS survey. We adjusted the coverage rate for wikis that were lagging behind on responses.

Will you be able to deploy the content on the website on December 19th?

@YLiou_WMF Yes.

On the QuickSurvey box, can we change "See our privacy policy here" to "Read our privacy statement" and link to https://foundation.wikimedia.org/wiki/Legal:Community_Feedback_Survey_on_Annual_Plan_FY_23-24_Core_Metrics_Reports_Privacy_Statement there?

@CMyrick-WMF It is.

@YLiou_WMF ok

I don't have familiarity with the repo before the migration but it looks like the test actions are working as expected. Current practices are a bit different but upgrading wouldn't be trivial.

This is how the survey looks:

Gonna deploy a survey with zero coverage today to test messages and speed up deployment later.

It wasn't on your end, it was my fault -- I had the link set up in the wrong place when we were thinking about doing a subsample. Resolved! (Nice to note that QuickSurvey also won't show up if a link doesn't exist)

For arwiki:

Instead of reader-demographics-2-survey-description can we use Reader-segmentation-1-description? This is a blank mediawiki page from the previous survey.

Most of the external links result in 404.

frwiki is missing reader-demographics-2-survey-description message that is why it doesn't show.

I made a typo in arwiki reader-demographics-2-survey-question. reader-demographics-2-survey-description is missing. Everything else looks good.

• arwiki: configuration typo (patch in progress)
• cswiki: missing translation for ext-quicksurveys-survey-confirm-msg
• dewiki
• elwiki: missing translation for ext-quicksurveys-survey-confirm-msg
• enwiki
• eswiki
• [fawiki](https://fa.wikipedia.org/wiki/بنیاد ویکی مدیا?quicksurvey=reader-demographics-2-fa)
• frwiki: something is wrong
• hewiki
• [hiwiki](https://hi.wikipedia.org/wiki/विकिमीडिया फ़ाउंडेशन?quicksurvey=reader-demographics-2-hi)
• idwiki: missing translation for ext-quicksurveys-survey-confirm-msg
• itwiki: missing translation for ext-quicksurveys-survey-confirm-msg
• jawiki
• kowiki: missing translation for ext-quicksurveys-survey-confirm-msg
• nlwiki: missing translation for ext-quicksurveys-survey-confirm-msg
• plwiki
• ptwiki
• rowiki: missing translation for ext-quicksurveys-survey-confirm-msg
• ruwiki
• trwiki
• ukwiki
• viwiki
• zhwiki

@Pablo Should it be added to the "Recent updates" section? If so what's the desired description?

Sorry @leila. I missed that.

As far as I know no survey has been deployed on metawiki so far but QuickSurveys were enabled by c46dd9b3a4.

@diego Done. I made slight changes in the citation style. Please let me know if it needs changes.

@leila done.

Ignore my request. Resolved.

Thank y'all!

In T219903#9250036, @leila wrote:

Hi @DDeSouza. This is a timely ask and I ask it outside of the process. Please remove the "We're hiring!" button from the pages and restore the usual text which links to the X account. Thank you!

@dchen Please let me know if you want changes. I didn't know where to put "online social behavior".