Another reason the en.wp method is better than forcing whitespace with padding, is because using actual spaces causes the screenreader to see a word break between the element content and the content of the ::after element.

PS. i'm pretty sure the usage of border-bottom over text-decoration: underline is intentional here, but it's not documented in the CSS sourcecode.....

just noting that en.wp uses:

.hlist dd:after, .hlist li:after {
  content: " · ";
  font-weight: bold;
}

Not sure why minerva uses something else.

@Theklan that seems more in the scope of the themes T234087: Theme: Local Development and Onboarding and T234091: Theme: People and Processes. Deploying and hosting is about anything after the code (including an integration) has already been written from my point of view.

Maybe we can discuss about an incentive system to review code. I feel with the current setup of teams it is very hard to incentivize anyone to review code outside of their own responsibility. It's basically a favor that people are doing to eachother and while nice at the human level (and that will probably always be the primary motivator to use), maybe there is more we can do to encourage people to reach across team/volunteer/3rd party lines..

I'd be interested in code health and it would be lovely if we could see about getting some statistics from the past year for instance, see if we can also find some empirical evidence next to the anecdotal evidence about progress made etc.

Not to be blunt but... this mostly seems like having to attend a homework session for WMF/WMDE :)
I'm not opposed to the concept of this, as a volunteer i'd love a more predictable method for me to interact with teams as well, but..... this doesn't seem like a session i'd join at the end of a long day...

Something that I'm missing here honestly, is the dedication to educate and teach new developers/team members as a core principle, before tossing them into the deep end... This is honestly more of an internal WMF thing to decide on, but work in that area can easily benefit any contributor and I think WMF is rather bad at this area (possibly because of their history of people who 'grew up with the codebase'..

Upstream states: "I can't reproduce. Could you try Canary?" and was then merged into https://bugs.chromium.org/p/chromium/issues/detail?id=1002442 and marked as fixed.

I really like this idea. Being more flexible in experimentation and rapid deployment seems important to me.

So we would potentially discuss things like red/blue, checksumming, a better maintenance mode for upgrades, database changes rollback, the web installer and a web configurator ?

Good points being raised. Personally I see beta as actually two things.

• shadow service (use the latest software against existing data for verification), which it is not, since it uses separate data structures
• pre-production staging of significant software configuration changes and features. Which it is not, since it doesn't really reproduce production

so.. some of this theme seems rather WMF focused.. Have we considered taking lessons and input from 3rd party MediaWiki hosters within this theme ?

What is the problem that led to this session proposal ?

I'll just say: https://laravel.com/docs/6.x again ;)

The description seems clear yet when I read it, I still have no idea what we would be doing in this session.. Identify pain points ? Throw ideas at the wall and see what sticks ? These things tends to get incredibly broad and vague ('better documentation')

For newcomers getting started in a situation that is easy to setup and has proper defaults (config and extension) is most important. To me that means as much composer driven installation and config as possible (because its the php ecosystem default). Where composer is not possible (due to services in different ecosystem etc), composer should inform users what to do next.

Hi, just a quick note, that due to a very busy and long week for me where I am at an exhibit for work, I won't have time to read any of this before the 11th, when I return from this event. I'm happy to spend some time during the weekend, to still go through everything and provide commentary and you can do with it as you desire.

Note: Without contentanalyzer, we probably can also support KML uploads.

The size of the original was too large to upload to phabricator I think (just over 10MB). Saved at half size:

@matmarex i think at the very least, when we trip the limit, we would want to have that proactively logged, regardless of the solution ?

Pretty sure now this was limited to an older Testflight build I had installed.

wow. nice sleuthing !!!

so.... turns out we are missing the XMP data from a significant number of files most likely. I suspect that Photoshop actually triggers this bug, so ;)

i had the user field selected and it did not fill the fields :(

https://commons.wikimedia.org/wiki/File:Ford_Grand_Torino_(29725737128).jpg
RuntimeException: Expected <rdf:Bag> but got http://www.w3.org/1999/02/22-rdf-syntax-ns# Seq.

i guess so... ;)

One problem, the current database structure only allows one set of 2fa credentials per user.... :(

Note from webkit:

• [WebAuthn] Enable WebAuthn by default for MobileSafari and SafariViewService

I like this improvement a lot ! The messages do indeed still need some work.

works fine for me with Chrome 77.0.3865.70 (Official Build) beta (64-bit) MacOS. What exact version do you have @SerDIDG ?

@Samwilson i think that is not a bad idea...

Idea, how about exposing the data as a lua module ?
Might make using it in different visual forms easier and more flexible than a parserfunction.

No known cases remain, if you find one, simply open a new separate task, instead of reopening the tracking bug.

I advice the developers: overflow-wrap: break-word ;)

Maybe the Language-Team can assist ?

i'll rename and prefix this class soon.

@Bdijkstra i tried compressing it in Preview.app and then it turned into 64MB, Thats what made me suspicious if this really was a single page. ;)

Note to self, map_group is to implement the guidelines of Metadata working group. Their website seems to be down unfortunately, but retrieved a copy of the guidelines via Internet Archive. https://web.archive.org/web/20180919181934/http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf

This is a huge Tiff image btw. Is that supposed to be the entire book ? Because in that case, the tiff is missing important markup information that lists the various pages. That would explain why the software doesn't recognise it as paged and has trouble rendering it.

If there is a consensus of trusted developers on the Phabricator task, any of the [https://gerrit.wikimedia.org/r/#/admin/groups/1,members Gerrit administrators] can resolve the request.

In T6845#5459813, @Guy_Macon wrote:

that's why I am not asking that CAPTCHAs be disabled. Instead I am asking that the WMF

'Too many requests' just means that throttling is being applied, because the attempt to generate the thumbnail failed too often in a row. Probably the thumbnail renderer is running into memory limits.

About potential backlash on disabling CAPTCHAs: Here stewards are arguing for better CAPTCHAs because they have too many fake accounts they need to deal with.

probably the latter. Who knows, i might discover more useful missing properties ;)

For this too, we will have to force a refresh of the EXIF metadata of all jpgs..

Alternative script library that has provisions for iOS panorama's https://github.com/naver/egjs-view360

Potentially interesting software for this type of content.

This is an issue with connections using chunked encoding. The TCP connection was hung-up (basically timeout due to maximum execution length), but there is more data still to download.

Nice work @DannyS712 !

Yeah this is one of Safari's quirks. By default tab navigation only works between textfields.
https://www.weba11y.com/blog/2014/07/07/keyboard-navigation-in-mac-browsers/

Since I'm touching this library for gpano, I might take a look. @Krinkle can you get me a list of some of the filenames throwing these log lines ?

Special:TimedMedia statistics could work i guess..

For the old player this is T96504: Video subtitles delay and expected.

Another note to self: once implemented, this requires an update to the cached metadata using maintenance/refreshMetadata --force

Note to self, Apple uses EXIF CustomRendered == 6 (panorama)

i think this is a really cool idea btw.

I now have:

• changes to our xmp-reader, which read the relevant metadata (still needs test)
• changes to the thumbnail renderer, to check the metadata for panoramas and to add a data-projection-type attribute if appropriate (T151451)
• a userscript to replace images annotated with data-projection-type, with an iframed https://tools.wmflabs.org/panoviewer/ (if i disable crossorigin checks in my browser)