We discussed this in a meeting yesterday, and the consensus was that setting up a second system of syncing folders would be too much work.

@elukey Yes, I'm happy to help with this! Just let me know what you'd like me to do.

@cchen @kzimmerman we should figure out how this will interact with T213467. Connie, maybe you can focus on the visual standards (and possibly R client choice), while I focus on picking the Python client? Those two seem like they can be decoupled pretty well, and of course we can work together on various parts too 😁

We've figured this out. Our overall goal is that content interactions via new form factors in emerging markets (whew) reach 12 million per month by mid 2020. If we achieve that, those content interactions will represent a 0.3% year-on-year increase in emerging market content interactions.

@cchen ran into this again trying to do the September metrics

This is now documented in the Wikimedia Product data dictionary.

I've checked through the Editing schemas on the whitelist (EditAttemptStep and VisualEditorFeatureUse) and neither uses token hashing at all, so there's nothing we need to do.

Example of an ad-hoc classification: Language's annual plan for FY2019-20 has a part of a definition of small Wikipedias: "Less than 100K Wikipedia articles. Potential to cover a large language gap compared to medium-size (100k-1.5M) and large Wikipedias (+1.5M)."

After three months, I can report that Language doesn't have any whitelisted schemas. 😂

We had a meeting about this earlier this week (notes). Generally, people felt that this wasn't urgent but would still be good to do relatively soon (perhaps Jan-Mar 2020) while we have a lot of accumulated experience with the data stream.

I don't think there's any value to this task anymore; in particular, the 2018-19 fiscal year is done so there's no big project anymore. T221566 lives on separately.

This is done! I've gotten helpful input and advice from the Trust and Safety team, documented this metric at meta:Research:Active administrators, and forwarded the correct query to @Iflorez to be included in T221566.

The 2018-19 fiscal year has added, so there's no longer value to delivering these metrics as a package. The tasks for the individual metrics will stay open on the backlog.

In T231024#5432366, @matmarex wrote:

Could these be null edits? Or are they already reported in some other way?