Sam, was the exclusion of is_bot intentional?

Just checked, these are safe to delete.

Option 1: "Inline after the lead section" has some advantages.

1. It resembles the previous state and allows the menu to go back to its previous narrower form (now that it doesn't have to match widths with the ToC which needs to be wider). This will probably leave people that like narrow windows largely unaffected.
2. Yes, in that case, there's no floating ToC any more, but then if the window is that narrow, there's no room for one anyway.

I've given the above-mentioned e-mail address access to the two English
Wikipedia domains (en.wikipedia.org and en.m.wikpedia.org).

@jcrespo I've been involved in this discussion so I know what's going on here. I've updated the ticket to reflect what they need. I can take care of providing access; how do I put an entry in the maint-announce calendar to revoke access on the expiry date?

That's _very_ interesting. Thanks for doing this! Would it make sense to just test this theory a bit more?

Works as expected, thank you.

Update: @AndyRussG already has access to Bing, as of yesterday. I'm working on a process to follow if/when more people request access.

Apologies, this fell through the cracks somewhat. I'll reply conclusively
before the end of this week.

@JMeybohm Given that we didn't actually add each language domain one by one, there should be, a "wikipedia.org" entry listed as a "Domain Property" along with all of the per-language Wikipedias on Search Console. When you select that one and add me as an "Owner" that should do it. There isn't an actual "Administrator" ACL level as far as I can tell - it's just "Owner", "Restricted", or "Full".

It got a bit trickier.

I confirm that Bing.com verification has worked properly. However, for Yandex it seems they need the TXT entry to be under www.wikipedia.org and not wikipedia.org. Sent out patch https://gerrit.wikimedia.org/r/c/operations/dns/+/768664 to that effect.

Just had a discussion with @jcrespo. To understand what each of these webmaster consoles provides and what ACLs and such they support (so that we can have a process around giving access to it), we want to first add a few domains to each and learn more about the platforms. Stand by for a DNS patch.

You're absolutely right to be concerned about traffic from search engines. That said, I'm familiar enough with how this works to be comfortable owning it, and my PM counterpart and I (and a half dozen or so other people at the Foundation including @AndyRussG) gaze at this data often enough that we'd know if something were amiss, and we'll obviously be watchful if we decide make any changes at all.

Just filed https://phabricator.wikimedia.org/T302617 to start discussing domain ownership verification on various consoles with SRE. I'll be unavailable for a few days starting now, but I've already had a discussion with @AndyRussG about this.

In case someone's wondering, DuckDuckGo doesn't actually have a webmaster console. Strange.

I'm working on this, please stay tuned on this ticket; ETA tomorrow.

Just did. All good, thank you and sorry for the trouble!

My new public key is here:

Apologies for the inconvenience. Bad key management on my part, thanks for
letting me know.

Manager approves.

Thank you Jesse. This will be sufficient for now; I'll come back if I need more sites.

@dr0ptp4kt is aware of the request; he's just somewhat swamped for now.
FWIW, I'm not in any sort of hurry. :-)

Additional note: if we determine that this data is useful enough for us to import into our own data stores, the same service account can be used just as well to run periodic imports of the data. I'm asking around in the Analytics channel and will follow up as required.

Manager approves.

Indeed, I did mean wikimedia.org and not mediawiki.org. Thank you.

We'll take care of this.

It has nothing to do with ULS. I can reproduce the same behaviour just clicking on the Alerts and then clicking on the user menu. There's some event that's being blocked or not sent by clicking on Alerts and Notices that the User Menu and ULS rely on to hide themselves.

Having reproduced and tested this somewhat, it looks like clicking on the Alerts or Notices buttons does not hide the ULS menu but clicking on the User Menu does.

Adding direct manager for approval.

Yes, I did attend one session where I got walked through a deployment. It
was very informative. I still have to actually deploy once myself though.

Approved by manager.

Confirmation: As it stands now, I only need access to superset.

If it's relevant, please note my shell account username is different. It's "saisuman".

Thank you, everyone. I've asked for request to ldap/nda as per your advice (I've already filed a request for ldap/wmf for gerrit).

Purpose: Apparently I also need this for access to the Alertmanager dashboard.