Willy, please review and verify/correct. Especially, why do you want to know the age of closed tasks? What will you do with this information?

Out of scope:

out of scope pending clearer tooling and process guidance

• “Show all of the SRE OKRs”
  • Defined by a repeatable process
    • from authoritative source (BetterWorks)
      • defined as single root node?
      • defined as all OKRs belonging to any SRE staff?
  • Apply filtering/rollup
    • stored in Airtable
    • or a google sheet
  • provide count of filtered items
• "Show all of the KRs for quarterly tracking, grouped by Objective"
  • All in one page
  • detail view (as per existing doc detailed view)

let's resolve it. I'll follow up with the relevant users when the next person who needs this onboards.

I ran a new phlogiston process and it handled the new dump without error, and got projects data.

look good to me.

FY19 is passed and FY20 work tracking follows a different model.

It has no active users at the moment and has been broken for months. However, I would like to re-activate it for further reporting exploration and prototyping. It may now be possible to replace it with calls to the API (which didn't have all the necessary info and/or wasn't stable when the code was originally written), but that would be a significant refactor. If there's a quicker fix for the dump, it would be more helpful sooner to have the dump back.

Any suggestions on how to proceed? There is no specific deadline, but I would like to have some Phlogiston results for consideration in the next few weeks.

Wikimedia Foundation (https://wikimediafoundation.org/) → Technical Blog

title, subtitle and description

passing to Greg for step 2, configuring the blog and vanity name.

Decide on a public pretty domainname for these more public/promoteable/cacheable tech blog posts (and if it's the legacy techblog.wikimedia.org instead of a fresh name, decide how we're handling historical redirects or whatever. (who's deciding, or was it decided?))

a) didn't need Ariel; could run it myself
b) couldn't run it very easily due to officewiki config et al
c) fixed the problem manually

Withdrawn.

sounds reasonable to me. Would it have to be both sub-projected and re-named to fully prevent conflict? Something like:

video showing incorrect page up/page down behavior.

I have a video of the bug, but this Phabricator instance won't take an upload. Is this appropriate for Commons?

Works, thank you.

The new production server has been set up and is populating. The remaining server on eqiad, phlogiston-3, can be removed. All phlogiston services are running on eqiad1-r, and there is no possibility of data loss if phlogiston-3 is removed.