@cooltey Can you check if this meets your expectations? If so, feel free to resolve 👍

Approved on my side too.

@pmiazga I'm not sure who will be working on it on the team so I'd suggest adding all the engineers, except for James who is working on multimedia right now: @bearND @Mholloway @MSantos @Tgr

Sorry I didn't see the comments before. I agree with you @Elitre, we're going to decline for now, since we are not going to be working on this (we're busy doing the critical maintenance tasks) and there is no maps team.

I was just re-reading the task and I find these comments funny 😃:

I'm going to be bold and resolve it. If any of the subscribers or else finds some improvements we can make a new task or reopen it. Thank you everyone!

Just FYI, there is some ongoing conversation in an email thread with the engineers about the specifics of this part 👍

Cool! I missed it somehow. Thanks.

I'll try to provide some information as a summary, let me know if it helps:

This work is specifically about the skin Minerva, and its frontend, and splitting mobilefrontend and minerva sensibly.

@MSantos can you resolve this task if it is done, or list what is remaining if it isn't?

A couple of things come to mind:

I think we should check what content.parsoid.less does to the content on minerva, and if it is acceptable (the file is quite small) then including that file/module to it would be a good idea, making mobile web content styles work with parsoid HTML for the future parser migration.

I'll leave it to @Tgr to decide, whatever you both think works.

Do we want to keep this one open to wait for the stretch migration and checking on the eventbus load, or should we spin up new tasks?

I'm the Reading infrastructure engineer manager, looks good 👍

1. Action items generated from the transcription

1. Literal transcription from the posters of the session

We have transcribed everything to the google doc, will be publishing here soon and summarizing to answer the questions

Sounds good from my end too 👍

@Tgr I think the task is mostly final with the session structure in case you want to have a look.

I think the description got messed up, as there is only 1 of the two options written and I'm not sure if it is actually what was meant to be written, or if it is a pro. Can you please review the description @bearND ?

Ill be discussing this with Nirzar to pick his brain and see if he thinks we should reach out to the designers to find some sort of common ground for all platforms.

After consulting, the teams won't be able to work on this on the near term, but will get to it on the future, so we shouldn't rush to implement the API when it is not going to be used.

Related to T202997: Maps using GeoShapes via Wikidata queries do not handle wiki links properly, seems like the same problem showing up in two different places.

@Gehel checked and it seems low frequency: https://logstash.wikimedia.org/goto/908d53aae57f35808ab0c12b6e79764f

@MSantos will look at this and the frequency of the errors.

Seems like it is fixed, thanks for the report!

Nice, added that task as a subtasks (blocks this one). When it is done, we can resolve this one. Moving to the blocked column.

So let's make it work like the apps need, and we can rise the issues with Design if it is not appropriate in the future.

For sure, in the case of skins.minerva.tablet.styles, the behaviour of the UI when going to tablet mode is to float the infobox to the right.

Thanks for the input @Kaartic, very useful.

Oh right, dumb me 😅

Ye @Krinkle just documenting next steps for me or the team to look into. Thanks for the report. Thanks @Umherirrender for the example.

👍 Sounds good. Should we do the JS too in parallel?

I'm not sure if it is needed to be written down explicitly but one thing that product engineers will do when adding instrumentation (obviously) is test and QA event logging, validation, sampling, etc. locally in their mediawiki and mediawiki-vagrant installs. Also QA/analysts/engineers sometimes perform these tests also in either beta cluster or some cloud labs instance that the teams have set up.

There is some info here, not very friendly tho: https://wikitech.wikimedia.org/wiki/Grafana.wikimedia.org

Thanks @MSantos, can you follow up on the talk page with the discussion about what we've done here and ask them to create a new ticket for the issue they are having? This task as presented should be done so it should be resolved.

I visited the two links in the description and I'm still seeing the images with the same size on my low dpi monitor. Is that how we can check if it is fixed?

Thanks @Mholloway

@MSantos Can you have a look into the parent security tasks that are in TODO in the kanban board and verify if we need to do anything else for them? Thanks!

Once in place it would be great to have some dashboards to look at and an experience report with how useful it was. I think it is a case of lack of resources (human and hardware both) and no one is opposed to it in principle, so with time we should get there.

Another issue I've found with /page/summary: https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_summary_title

Nice. I've been talking to Gergo and I've put the sentry topic and client side error logging into the platform evolution feedback we are giving, so hopefully we can raise global awareness and resourcing to finally get proper infrastructure for client side error monitoring in the future. It is still ways off, so I think this would be a great stopgap measure specially now that you are refactoring different pieces.

Should we connect the test servers to a dashboard like the production one where we could see stats for tile generation rates, etc? (excuse me if it is already somewhere, couldn't find it). Seems like it could be a good idea to check on the servers before rolling to production when we make changes.

Cool, thanks for checking!

Do the apps bundle that module @bearND?

FTR all the reading lists post parameters that have "in": "body" have a name, the only one that doesn't is the /transform/section-changes/to/wikitext/{title}/{revision} one.

I'll keep it as stalled while we discuss, declined may have been to strong.

Hi @Kelson, I'm using priorities as stated on mediawiki. Low is not a bad thing, it means:

Maybe it makes sense for this to be in pagelib CSS instead of the base endpoint.