The main examples of relation:site are: dispersed power plants, parking sites, heritage sites, historic sites, and French survey point sites.
https://wiki.openstreetmap.org/wiki/Relation:site#Examples

In T92432#10056770, @Novem_Linguae wrote:

@Mathglot, should you instead make your edit as a new comment, instead of editing Jdforrester's post?

See also T5241: Transclusion should produce tree-like results in "What links here"

@Mathglot, should you instead make your edit as a new comment, instead of editing Jdforrester's post?

We've been trying to determine what "Wikimedia has switched from osm2pgsql to imposm3, support for more relation types can be configured, now type=waterway is supported in addition to previous three types. It should be further reviewed which other relation types can be and should be supported." actually means.

There are no longer any plans to upgrade Vega. The Graph extension will be succeeded by Charts, a new extension being built this year as part of a dedicated WMF initiative. Apache eCharts has been selected as the framework to power these charts, but using Vega has not been ruled out entirely for future use (see T368336#9971574 for more context).

Test wiki on Patch demo by Jdlrobson using patch(es) linked to this task was deleted:

Addiung Community-Tech as the 2022 survey is past and open tasks must have at least one active project tag.

See also: T14019: ifexist function uses pagelinks table in lieu of better options

One way I was thinking about this would require the page to be in at least one category, but then would suggest other categories based on the category membership of other pages in that category. They could be listed in order of page count, perhaps. For example: File:Unknown_artist_-_Fish_Bowl_-_1917.54_-_Cleveland_Museum_of_Art.jpg is in Category:Jade_bowls, as is File:Jade_bowl_national_museum_india.JPG. The latter is also in Category:Mughal_jade and so that could be suggested for the first file. (I'm not saying that'd be a good suggestion, just trying to explain the mechanism!)

(awaiting T360188 for the correct #community-wishlist-survey-2021 tag)

Also related: T268526#9594281 which proposes to decouple/restructure how dependency tracking is done. In theory if LinksUpdate wasn't using ParserOutput::addTemplate() we could have a bit more freedom in restructuring how that dependency tracking is done. Right now Parsoid isn't used in any LinksUpdate jobs (except for the "prewarm cache jobs" maybe?) so this would be blocked on T310512: Parsoid and the legacy parser should emit exactly the same ParserOutput metadata.

Change 904755 abandoned by Kosta Harlan:

[mediawiki/extensions/Echo@master] EchoWatchlistNotifications: Don't create events if edit-user-page or edit-user-talk are enabled

Reason:

https://gerrit.wikimedia.org/r/904755

Change 835079 abandoned by Samwilson:

[mediawiki/extensions/PageImages@master] Add new {{#pageimage:}} parser function

Reason:

https://gerrit.wikimedia.org/r/835079

Update: I was able to fix the watchstar sort of, but that code still needs to be cleaned up.

In T265716#9404693, @Stevietheman wrote:

Will the changes cover calls by apps like AutoWikiBrowser, like when I set it to "Use MW preferences" for determining if a page I change is watched?

Will the changes cover calls by apps like AutoWikiBrowser, like when I set it to "Use MW preferences" for determining if a page I change is watched?

Outstanding issues as of the time of writing:

From the sound of it, none of us here seem to have strong feelings, so I hope it's alright to stick to essentially:

nb. this missing feature was again brought up on wiktionary recently :-)

Sorry, I missed this at the time, can you advice someone on the team how to do it, as you are busy.

Related: T14396