While evaluating the decision brief, it was pointed out that we should default to non-consent and allow capturing of consent from users prior to avoid the act of revoking consent identifying a user against their wishes as a donor. This is slightly different from what was proposed in the decision brief but more conscious and equally powerful as it will allow us to capture potential donors.

@AKanji-WMF please link out to your results here when you have them!

There is still room for improvement with the subheadings
e.g. http://localhost:8888/w/index.php?title=List_of_Hollyoaks_characters_introduced_in_2018&useparsoid=1#Storylines / https://d026251709.catalyst.wmcloud.org/w/index.php?title=List_of_Hollyoaks_characters_introduced_in_2018#Storylines )

@AnneT suggested making it clear it is an override would be sensible and @matmarex pointed out if we want to rename we should do it now. Would darkmode-override make sense? Any other options?

I might be wrong but I'm not sure if it's currently possible to deploy Reference Previews without the standard page previews and associated preferences... but please prove me wrong :-)

Interesting. I'm not sure when that was enabled but that didn't used to be the case. The summary endpoint was built specifically for projects that follow Wikipedia's structure (e.g. headings, image and paragraphs of text) so I have no idea how it ended up enabled on non-Wikipedias. It was added to WIkivoyage without objections since its format is consistent with Wikipedia.

The patch seems to resolve the issue for all skins except Minerva (see T417372#11616493), so I want to say that this is a Minerva bug at this point.

Please don't reopen tickets that were declined 7 years ago. It is very confusing. If you have a new request please open a new ticket and reference this ticket.

It can be fixed on wiki too by modifying https://en.wikipedia.org/wiki/Template:abbrlink using the guidelines in https://www.mediawiki.org/wiki/Extension:Popups#Why_is_content_removed_from_the_summary?

This is a bug in the summary endpoint for Page Content Service .

FYI @egardner this has no impact on MobileFrontend or Page previews, it just cleans out some code that wasn't doing anything so I went ahead and merged it without Reader Growth involvement.

The Popups API currently doesn't support non-Wikipedias as far as I'm aware so this is not possible. We do not support the use of Extension:TextExtracts for page previews in production.

This banner is provided by the English Wikipedia community. @spatton could you please help me route this issue to the correct volunteer?

Vector 2010 is not a responsive skin so it's not expected to work well at these kind of resolutions without gadgets. Development of legacy Vector is frozen (we are in maintenance only mode).

@cscott will provide us a function that checks if a page has unbalanced template as part of T417334: Parsoid should provide an easy way for hooks to check if parser content is unbalanced (discussed this with him today in our 1 on 1)

I talked to @cscott today about this and it seems like we have a potential solution here. In the case of the Main page raw HTML (h1 tag) is being used so we should be able to detect this and avoid outputting the HTML here. I'll check in with @cscott in a few weeks time.

@STei-WMF Yep no need to mention baby globe. This is just about Site notices now displaying on mobile site.

In T393819#11611413, @Bewfip wrote:

There is a report on zhwiki (link) that the search suggestion feature is broken recently. I suspect gerrit #1217251 causes this regression.

I am able to reproduce that issue with Vector 2022 and Minerva on desktop Windows 10. It happens when typing a few alphabets into the search box first, then switch to an IME to input Chinese characters. Those /w/rest.php/v1/search/title?q=%s requests only contain the candidate Chinese characters when the IME is active (the alphabets before are not included). The full input box content is sent only after pressing backspace.

I assume we'd also move the logging code to WikimediaEvents for consistency with other events so tagging WikimediaEvents.

There should be no skins in group 2 that are not in group 1 or 0. I'm fairly confident you should be fine tomorrow. Thanks @Tgr for taking care of the Nostalgia issue.

cc @jgleeson @Ejegg and @Lars - feel free to ask questions here if you need to dig into details beforehand about how we will handle the transfer from CiviCRM to this environment (for example if you want to get guidance on encryption options).

@CDanis says that we might be able to use one of the Ceph clusters we have in production now as we have a few existing data streams that get picked up by puppetservers that way.