Page MenuHomePhabricator

Milimetric (Dan Andreescu)
User

Projects (12)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Friday

  • Clear sailing ahead.

User Details

User Since
Oct 8 2014, 5:48 PM (263 w, 11 s)
Availability
Available
LDAP User
Milimetric
MediaWiki User
Milimetric (WMF) [ Global Accounts ]

Recent Activity

Yesterday

Milimetric added a comment to T193613: Establish stable interface policy for PHP code (was: strategy for PHP interface changes).

Per the policy, public methods are considered stable (safe to call) per default. However, public constructors are not considered stable. And public methods are not automatically considered fixed (safe to override).

Tue, Oct 22, 9:33 PM · Discovery-Search, TechCom, TechCom-RFC, MediaWiki-General
Milimetric added a comment to T235143: Wikistats API for legacy pagecounts does not have mobile data before October 2014.
  • Erik compiled data from sampled logs which are no longer available
Tue, Oct 22, 9:22 PM · Product-Analytics, Analytics
Milimetric added a comment to T226071: Having trouble setting up MobileFrontend for development.

I tried to enable the vagrant role again to test and I got this error, so I figure either my vagrant is messed up or this will prevent me from having a clean test. I think if it works for other folks on a clean vagrant, it's fine, I'll try to test again when I look at the unit testing RFC next.

Tue, Oct 22, 9:19 PM · Readers-Web-Backlog, MobileFrontend
Milimetric added a comment to T234649: Wikimedia Technical Conference 2019 Session: Front-end modernization and standardization.

Something missing in the announcements about the FAWG and this task is the possibility that none of the available options are good trade-offs/long-term investments. There is a maturity of the environment required to do such a migration and I don't know if the current frontend framework landscape has reached that stage yet.
For example, it's possible that the most useful parts of these frameworks are things that should be made part of the web platform itself and that resources and efforts in terms of long-term investments would be better made in the standards space (W3C, WHATWG, etc.).
By framing the discussion on "which framework should we pick", it might lock the discussion into a close-minded view in that respect.
If there is a need so common that most websites end up using similar frameworks to achieve it, it might be something that should be part of JS/CSS. We've seen that process from beginning to end with jQuery being less and less useful as features have made their way into JS itself. Now we're still paying the price of jQuery's weight because we're locked into it, it's completely baked into all our code, even though we use very little of it.
We might be early in such a cycle with frontend frameworks. It would be unfortunate to invest a lot of resources in the jQuery-like phase when we could be helping and pushing towards the endgame. I.e. that it becomes part of the web platform and using those features becomes a non-issue. Worse, we could make a heavy frontend framework a page load requirement that will be very difficult to undo, with a potential usefulness lifespan of a few years.

Tue, Oct 22, 9:15 PM · International-Developer-Events, Wikimedia-Technical-Conference-2019
Milimetric added a comment to T131280: Make aggregate data on editors per country per wiki publicly available.

anticipating release, docs here: https://wikitech.wikimedia.org/wiki/Analytics/Data_Lake/Edits/Geoeditors/Public

Tue, Oct 22, 3:20 PM · Product-Analytics, Analytics-Kanban

Thu, Oct 17

Milimetric moved T225578: EventLogging needs to enque events to avoid draining users' battery on mobile from In Progress to In Code Review on the Analytics-Kanban board.
Thu, Oct 17, 3:56 PM · Performance-Team, Patch-For-Review, Analytics-Kanban, Analytics-EventLogging, Analytics

Tue, Oct 15

Milimetric added a comment to T233432: Figure out how to $ref common schema across schema repositories.

I wouldn't worry too much about how others are using this in their own mediawiki installs. Not that it's not important, just that we can't possibly guess as to how they might want to do that. Just having three repos with some common stuff will allow for plenty of flexibility and refactoring later on.

Tue, Oct 15, 8:39 PM · Analytics-Kanban, CPT Initiatives (Modern Event Platform (TEC2)), Services (watching), Analytics-EventLogging, Event-Platform, Analytics
Milimetric added a comment to T233432: Figure out how to $ref common schema across schema repositories.

I like a single namespace, especially because having "common" as a root would be too vague. This might be useful:

Tue, Oct 15, 3:58 PM · Analytics-Kanban, CPT Initiatives (Modern Event Platform (TEC2)), Services (watching), Analytics-EventLogging, Event-Platform, Analytics
Milimetric changed the status of T234461: Sudden drop in WikipediaPortal events from Declined to Resolved.
Tue, Oct 15, 3:37 PM · Analytics-Kanban, Analytics, Analytics-EventLogging, Wikimedia-Portals

Fri, Oct 11

Milimetric moved T131280: Make aggregate data on editors per country per wiki publicly available from In Progress to In Code Review on the Analytics-Kanban board.
Fri, Oct 11, 3:10 AM · Product-Analytics, Analytics-Kanban

Thu, Oct 10

Milimetric added a comment to T234188: Taxonomy of new user reading patterns.

I looked at this and it's a clever way to get some rough information to answer the main question. But I just wanted to point out: it's not by accident that this kind of correlation is hard to do. We made a conscious decision a while back that we should not optimize accessing reading patterns of specific users. Being able to get this data is problematic for privacy reasons, and more so if we can get this data quickly. So, nice work, but I would hesitate before optimizing it too much more.

Thu, Oct 10, 5:17 PM · Analytics, Research
Milimetric closed T235143: Wikistats API for legacy pagecounts does not have mobile data before October 2014 as Resolved.
Thu, Oct 10, 5:08 PM · Product-Analytics, Analytics
Milimetric added a comment to T235143: Wikistats API for legacy pagecounts does not have mobile data before October 2014.

Yes, unfortunately we don't have mobile data going back before that. Before 2014, we had:

Thu, Oct 10, 5:08 PM · Product-Analytics, Analytics
Milimetric updated the task description for T235189: Prototype client to log errors in vagrant.
Thu, Oct 10, 4:43 PM · Product-Infrastructure-Team-Backlog (Kanban), Performance-Team (Radar), Better Use Of Data, Epic, Analytics
Milimetric created T235189: Prototype client to log errors in vagrant.
Thu, Oct 10, 3:40 PM · Product-Infrastructure-Team-Backlog (Kanban), Performance-Team (Radar), Better Use Of Data, Epic, Analytics

Wed, Oct 9

Milimetric added a comment to T233504: add whether an edit happened on cloud VPS to geoeditors-daily dataset .

ok, I restarted the monthly job and this column will be populated going forward. The first time it will be inserted is November 1st, 2019, when it runs the month of October.

Wed, Oct 9, 9:56 PM · Patch-For-Review, Analytics-Kanban, Analytics, Cloud-Services, Developer-Advocacy (Jul-Sep 2019)
Milimetric moved T233504: add whether an edit happened on cloud VPS to geoeditors-daily dataset from Ready to Deploy to Done on the Analytics-Kanban board.
Wed, Oct 9, 9:52 PM · Patch-For-Review, Analytics-Kanban, Analytics, Cloud-Services, Developer-Advocacy (Jul-Sep 2019)
Milimetric added a comment to T193613: Establish stable interface policy for PHP code (was: strategy for PHP interface changes).

I'm thinking about the generated documentation that may now be confusing to newcomers / people who haven't read this policy yet. For example, if you have two public methods, and one of them is annotated with @stable while the other is not. I would read the documentation and use any public method and expect it to be stable unless something jumped out at me telling me not to make this assumption. So, ideally, docs would color/explain both annotated methods and public methods that are not annotated.

Wed, Oct 9, 9:48 PM · Discovery-Search, TechCom, TechCom-RFC, MediaWiki-General
Milimetric added a comment to T233504: add whether an edit happened on cloud VPS to geoeditors-daily dataset .

The column has been added and I'm restarting the job so it will be filled going forward. Should we backfill this data as far back as we have the raw source (90 days)?

Wed, Oct 9, 6:40 PM · Patch-For-Review, Analytics-Kanban, Analytics, Cloud-Services, Developer-Advocacy (Jul-Sep 2019)
Milimetric moved T233504: add whether an edit happened on cloud VPS to geoeditors-daily dataset from In Code Review to Ready to Deploy on the Analytics-Kanban board.
Wed, Oct 9, 6:37 PM · Patch-For-Review, Analytics-Kanban, Analytics, Cloud-Services, Developer-Advocacy (Jul-Sep 2019)
Milimetric added a comment to T226663: Develop a tool or integrate feature in existing one to visualize WMCS edits data.

@Milimetric I don't quite understand what happened here, so I'm reverting the ownership change.

Wed, Oct 9, 6:27 PM · Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric added a comment to T131280: Make aggregate data on editors per country per wiki publicly available.

@Ijon I'm working on a blacklist, and wanted to check with you to see how it would impact the usefulness of the dataset. I'll write more details but basically on the advice of folks more familiar with censorship of Wikipedia I'm using scores from Reporters Without Borders [1] and Freedom on the Net [2]. It makes more sense to blacklist the top wikis used in each of these countries, but that is often English Wikipedia and things get confusing. So sticking with the simpler approach of just blacklisting the countries, here's a list of the worst offenders according to those two sources:

Wed, Oct 9, 2:02 AM · Product-Analytics, Analytics-Kanban

Mon, Oct 7

Milimetric moved T234461: Sudden drop in WikipediaPortal events from Next Up to In Progress on the Analytics-Kanban board.
Mon, Oct 7, 4:37 PM · Analytics-Kanban, Analytics, Analytics-EventLogging, Wikimedia-Portals
Milimetric assigned T234461: Sudden drop in WikipediaPortal events to Nuria.

ok, we found the problem - we deployed a filter to exclude requests from domains we don't have on a whitelist (like the many Wikipedia mirrors that randomly run our JS code and send bad data). Since this instrumentation comes from wikipedia.org, we were excluding it. We'll put that on the whitelist and rerun refine for this time period.

Mon, Oct 7, 4:36 PM · Analytics-Kanban, Analytics, Analytics-EventLogging, Wikimedia-Portals
Milimetric triaged T233716: Create mediarequests top files AQS endpoint as High priority.
Mon, Oct 7, 4:09 PM · Patch-For-Review, Analytics-Kanban, Services (watching), Analytics
Milimetric triaged T233057: Clean up descriptions of fields in included common schemas in mediawiki/event-schemas repository as High priority.
Mon, Oct 7, 4:09 PM · Analytics-Kanban, Event-Platform, Analytics
Milimetric triaged T231677: Superset + Turnilo access for Verena Lindner + Raja Gumienny (WMDE) as High priority.
Mon, Oct 7, 4:09 PM · Analytics
Milimetric claimed T231861: Check home leftovers of smalyshev.
Mon, Oct 7, 4:08 PM · Analytics-Kanban, Analytics
Milimetric triaged T231861: Check home leftovers of smalyshev as High priority.
Mon, Oct 7, 4:08 PM · Analytics-Kanban, Analytics
Milimetric triaged T231858: Archive data on eventlogging MySQL to analytics replica before decomisioning as High priority.
Mon, Oct 7, 4:08 PM · Analytics-Kanban, Analytics, Analytics-EventLogging
Milimetric triaged T232349: Disable production EventLogging analytics MySQL consumers as High priority.
Mon, Oct 7, 4:08 PM · Analytics, Analytics-EventLogging
Milimetric moved T234281: Explore importing geoeditors_daily data (aggregated edits per namespace per country per wiki) into druid from Next Up to Paused on the Analytics-Kanban board.
Mon, Oct 7, 4:07 PM · Analytics-Kanban, Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric moved T234281: Explore importing geoeditors_daily data (aggregated edits per namespace per country per wiki) into druid from Incoming to Smart Tools for Better Data on the Analytics board.
Mon, Oct 7, 4:07 PM · Analytics-Kanban, Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric moved T234629: Move the Analytics infrastructure to Debian Buster from Next Up to Parent Tasks on the Analytics-Kanban board.
Mon, Oct 7, 4:07 PM · Analytics-Kanban, Analytics
Milimetric added a project to T234629: Move the Analytics infrastructure to Debian Buster: Analytics-Kanban.
Mon, Oct 7, 4:07 PM · Analytics-Kanban, Analytics
Milimetric moved T234629: Move the Analytics infrastructure to Debian Buster from Incoming to Operational Excellence on the Analytics board.
Mon, Oct 7, 4:06 PM · Analytics-Kanban, Analytics
Milimetric raised the priority of T234808: Upgrade python-kafka to 1.4.7 from Normal to High.
Mon, Oct 7, 4:06 PM · Performance-Team (Radar), Analytics-Kanban, Analytics
Milimetric moved T234808: Upgrade python-kafka to 1.4.7 from Incoming to Operational Excellence on the Analytics board.
Mon, Oct 7, 4:05 PM · Performance-Team (Radar), Analytics-Kanban, Analytics
Milimetric moved T234344: MinervaClientError sends malformed events from Incoming to Radar on the Analytics board.
Mon, Oct 7, 4:05 PM · Performance-Team (Radar), Readers-Web-Backlog (Kanbanana-2019-20-Q2), Analytics, MinervaNeue
Milimetric triaged T234281: Explore importing geoeditors_daily data (aggregated edits per namespace per country per wiki) into druid as Low priority.

low priority until someone asks for this in Druid - and let's be careful how we expose the IP/UA/user id column.

Mon, Oct 7, 4:04 PM · Analytics-Kanban, Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric assigned T234333: Import siteinfo dumps onto HDFS to JAllemandou.
Mon, Oct 7, 3:58 PM · Analytics-Kanban, Analytics
Milimetric moved T234333: Import siteinfo dumps onto HDFS from Incoming to Data Quality on the Analytics board.
Mon, Oct 7, 3:58 PM · Analytics-Kanban, Analytics
Milimetric moved T234461: Sudden drop in WikipediaPortal events from Incoming to Radar on the Analytics board.
Mon, Oct 7, 3:57 PM · Analytics-Kanban, Analytics, Analytics-EventLogging, Wikimedia-Portals
Milimetric added a comment to T234461: Sudden drop in WikipediaPortal events.

The fact that there are some events means the data is flowing through. First guess is take a look at the eventerror table for your schema, see if there's a spike of errors and if so, what they are. If there's a corresponding rise there, it means your events are not matching the schema. If not, let us know and we can help look further. This also looks ok, events flowing in seem relatively consistent (no 100x drops): https://grafana.wikimedia.org/d/000000018/eventlogging-schema?orgId=1&var-schema=WikipediaPortal&from=now-90d&to=now

Mon, Oct 7, 3:57 PM · Analytics-Kanban, Analytics, Analytics-EventLogging, Wikimedia-Portals
Milimetric added a project to T234484: Add data quality metric: traffic variations per country: Analytics-Kanban.
Mon, Oct 7, 3:50 PM · Research, Analytics-Kanban, Analytics
Milimetric triaged T234484: Add data quality metric: traffic variations per country as High priority.
Mon, Oct 7, 3:50 PM · Research, Analytics-Kanban, Analytics
Milimetric moved T234484: Add data quality metric: traffic variations per country from Incoming to Data Quality on the Analytics board.
Mon, Oct 7, 3:50 PM · Research, Analytics-Kanban, Analytics
Milimetric closed T234493: Druid monthly indexing of eventlogging segments as Declined.

data's only in Druid for these datasources for 3 months, we decided we don't need to reindex monthly

Mon, Oct 7, 3:50 PM · Analytics
Milimetric closed T234494: Eventlogging to druid daily timers not executing? , a subtask of T234471: superset not showing data after 09/16 for some datasources , as Invalid.
Mon, Oct 7, 3:46 PM · Analytics-Kanban, Analytics
Milimetric closed T234494: Eventlogging to druid daily timers not executing? as Invalid.

nothing to do, maybe monitor and see if this causes other performance problems?

Mon, Oct 7, 3:46 PM · Analytics-Kanban, Analytics
Milimetric triaged T234494: Eventlogging to druid daily timers not executing? as High priority.
Mon, Oct 7, 3:44 PM · Analytics-Kanban, Analytics
Milimetric moved T234494: Eventlogging to druid daily timers not executing? from Incoming to Operational Excellence on the Analytics board.
Mon, Oct 7, 3:44 PM · Analytics-Kanban, Analytics
Milimetric triaged T234588: Add data quality metric: distribution of eventlogging user agents as High priority.
Mon, Oct 7, 3:44 PM · Analytics-Kanban, Analytics
Milimetric moved T234588: Add data quality metric: distribution of eventlogging user agents from Incoming to Data Quality on the Analytics board.
Mon, Oct 7, 3:44 PM · Analytics-Kanban, Analytics
Milimetric moved T234590: Add ability to the pageview tool in labs to get mediarequests per file similar to existing functionality to get pageviews per page title from Incoming to Radar on the Analytics board.
Mon, Oct 7, 3:44 PM · Multimedia, Analytics, Tool-Pageviews
Milimetric triaged T234589: Add mediarequests metrics to wikistats UI as High priority.
Mon, Oct 7, 3:43 PM · Multimedia, Analytics, Tool-Pageviews
Milimetric moved T234589: Add mediarequests metrics to wikistats UI from Incoming to Wikistats Production on the Analytics board.
Mon, Oct 7, 3:43 PM · Multimedia, Analytics, Tool-Pageviews
Milimetric triaged T234591: Backfill data from mediacounts into mediarequests tables in cassandra so as to have historical mediarequest data as High priority.
Mon, Oct 7, 3:43 PM · Analytics-Kanban, Multimedia, Analytics, Tool-Pageviews
Milimetric moved T234591: Backfill data from mediacounts into mediarequests tables in cassandra so as to have historical mediarequest data from Incoming to Analytics Query Service on the Analytics board.
Mon, Oct 7, 3:43 PM · Analytics-Kanban, Multimedia, Analytics, Tool-Pageviews
Milimetric triaged T234594: Eventlogging Client Side can use the stream config module to dynamically adjust sampling rates as High priority.
Mon, Oct 7, 3:33 PM · Better Use Of Data, CPT Initiatives (Modern Event Platform (TEC2)), Services (watching), Analytics-EventLogging, Event-Platform, Analytics
Milimetric moved T234594: Eventlogging Client Side can use the stream config module to dynamically adjust sampling rates from Incoming to Modern Event Platform on the Analytics board.
Mon, Oct 7, 3:33 PM · Better Use Of Data, CPT Initiatives (Modern Event Platform (TEC2)), Services (watching), Analytics-EventLogging, Event-Platform, Analytics
Milimetric reassigned T234684: Superset not able to load a reading dashboard from Milimetric to Nuria.
Mon, Oct 7, 3:29 PM · Analytics-Kanban, Analytics
Milimetric triaged T234607: Upgrade matomo to its latest upstream version as High priority.
Mon, Oct 7, 3:29 PM · Analytics-Kanban, Analytics
Milimetric moved T234607: Upgrade matomo to its latest upstream version from Incoming to Operational Excellence on the Analytics board.
Mon, Oct 7, 3:29 PM · Analytics-Kanban, Analytics
Milimetric claimed T234684: Superset not able to load a reading dashboard .
Mon, Oct 7, 3:28 PM · Analytics-Kanban, Analytics
Milimetric moved T234684: Superset not able to load a reading dashboard from Incoming to Ops Week on the Analytics board.
Mon, Oct 7, 3:27 PM · Analytics-Kanban, Analytics
Milimetric lowered the priority of T234826: Repurpose db1108 as generic Analytics db replica from High to Normal.
Mon, Oct 7, 3:27 PM · DBA, Analytics
Milimetric triaged T234826: Repurpose db1108 as generic Analytics db replica as High priority.
Mon, Oct 7, 3:27 PM · DBA, Analytics
Milimetric moved T234826: Repurpose db1108 as generic Analytics db replica from Incoming to Operational Excellence on the Analytics board.
Mon, Oct 7, 3:27 PM · DBA, Analytics

Fri, Oct 4

Milimetric added a comment to T234649: Wikimedia Technical Conference 2019 Session: Front-end modernization and standardization.

Can't wait to help as much as I can with this effort. I think it's going to be a big challenge with an even bigger payoff. I didn't get to be part of the FAWG but I've used several mainstream and several weird frameworks in my career and have hopefully useful opinions about how to understand pros and cons and decide on this specific kind of technology. Looking forward to help in any way I can.

Fri, Oct 4, 7:53 PM · International-Developer-Events, Wikimedia-Technical-Conference-2019
Milimetric awarded T234090: Theme: Standardization Decisions a Love token.
Fri, Oct 4, 7:50 PM · International-Developer-Events, Wikimedia-Technical-Conference-2019
Milimetric added a comment to T18691: RFC: Section header "share" link.

Ok, so, good progress here. The technical committee would like to see concerns from the March 2015 version reviewed, to ensure we don't repeat any of those problems. As stated in the description, the issues were raised in and around comments T18691#1051560 and T18691#1098570, and include:

Fri, Oct 4, 7:48 PM · Core Platform Team Workboards (Clinic Duty Team), Readers-Web-Backlog, Patch-For-Review, TechCom-RFC, Design, MediaWiki-Interface

Tue, Oct 1

Milimetric added a comment to T228795: Investigate API and client architecture requirements for edit history, diffs and related user actions.

All the data requested here is available in the mediawiki history dataset. We have not had any requests to query this data from our user-facing interface. It's certainly possible, but not trivial: it's just too much data to allow arbitrary querying without putting it on a *monster* cluster. But, for example, if we just had to answer the questions listed here, we could probably do it much more efficiently. We just need someone to stand up and say "this is important". Also, right now this data is computed monthly. If we need more frequent updates, the same principle applies. It's very hard to update everything incrementally, but for a limited set of questions and queries, we could update near real-time.

Tue, Oct 1, 3:01 PM · iOS-app-v6.5-Squid-On-A-Tandem-Bike, Spike, Wikipedia-iOS-App-Backlog
Milimetric added a comment to T226663: Develop a tool or integrate feature in existing one to visualize WMCS edits data.

@srishakatux / @bd808: what would you like to see in your dashboard? Off the top of my head I can see how the following things might be useful:

Tue, Oct 1, 2:24 PM · Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services

Mon, Sep 30

Milimetric added a comment to T201063: Modern Event Platform: Schema Registry.

While I would love to argue for a .NET deployment, so me and everyone I love can enjoy programming again, what do we need from schemastore? I didn't think we needed any fancy features outside of Stream Config

Mon, Sep 30, 9:43 PM · Analytics, Core Platform Team Legacy (Watching / External), Services (watching), Analytics-EventLogging, Event-Platform
Milimetric claimed T234229: Shorten the time it takes to move files from hadoop to dump hosts by Kerberizing/hadooping the dump hosts .
Mon, Sep 30, 4:32 PM · Patch-For-Review, User-Elukey, Analytics-Kanban, Analytics
Milimetric moved T225578: EventLogging needs to enque events to avoid draining users' battery on mobile from Paused to In Progress on the Analytics-Kanban board.
Mon, Sep 30, 4:32 PM · Performance-Team, Patch-For-Review, Analytics-Kanban, Analytics-EventLogging, Analytics
Milimetric moved T233636: Banner History and page view data access for fundraising analysts - Jerrie and Erin from Incoming to Radar on the Analytics board.
Mon, Sep 30, 4:31 PM · Analytics, Operations, SRE-Access-Requests, Fundraising-Backlog
Milimetric moved T233824: [SPIKE 8hrs] How will the changes to eventlogging affect desktop improvements from Incoming to Radar on the Analytics board.
Mon, Sep 30, 4:31 PM · Readers-Web-Backlog (Kanbanana-2019-20-Q2), Analytics, Event-Platform, Desktop Improvements
Milimetric reassigned T233329: Review draft Modern Event Platform schema guidelines from Neil_P._Quinn_WMF to Ottomata.
Mon, Sep 30, 4:31 PM · Event-Platform, Analytics, Product-Analytics
Milimetric moved T233329: Review draft Modern Event Platform schema guidelines from Incoming to Modern Event Platform on the Analytics board.
Mon, Sep 30, 4:31 PM · Event-Platform, Analytics, Product-Analytics
Milimetric raised the priority of T233661: Publish tls related info to webrequest via varnish from Normal to High.
Mon, Sep 30, 4:29 PM · Analytics-Kanban, observability, Operations, Analytics, Traffic
Milimetric moved T233661: Publish tls related info to webrequest via varnish from Incoming to Smart Tools for Better Data on the Analytics board.
Mon, Sep 30, 4:29 PM · Analytics-Kanban, observability, Operations, Analytics, Traffic
Milimetric raised the priority of T226663: Develop a tool or integrate feature in existing one to visualize WMCS edits data from Normal to High.
Mon, Sep 30, 4:22 PM · Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric reassigned T226663: Develop a tool or integrate feature in existing one to visualize WMCS edits data from srishakatux to JAllemandou.
Mon, Sep 30, 4:22 PM · Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric moved T226663: Develop a tool or integrate feature in existing one to visualize WMCS edits data from Incoming to Smart Tools for Better Data on the Analytics board.
Mon, Sep 30, 4:22 PM · Analytics, Developer-Advocacy (Oct-Dec 2019), Cloud-Services
Milimetric added a project to T234238: Enable geoeditors_daily deletion : Analytics-Kanban.
Mon, Sep 30, 4:17 PM · Analytics-Kanban, Analytics
Milimetric triaged T234238: Enable geoeditors_daily deletion as High priority.
Mon, Sep 30, 4:16 PM · Analytics-Kanban, Analytics
Milimetric moved T234238: Enable geoeditors_daily deletion from Incoming to Operational Excellence on the Analytics board.
Mon, Sep 30, 4:16 PM · Analytics-Kanban, Analytics
Milimetric added a comment to T217848: Sqoop: remove cuc_comment and join to comment table.

I fixed a broken link, the task we need to follow is now T233004, and it looks like work is going forward. So we'll need a patch here. I'm happy to take this but will wait for grooming to jump back in the dance.

Mon, Sep 30, 2:35 PM · Analytics
Milimetric added a comment to T232531: Refactor Comment fields for CheckUser Component.

@Anomie: thanks. Importantly, I tagged T233004 with Analytics as well, because we need to be in this loop. Closing this task had taken us out of the loop again.

Mon, Sep 30, 2:31 PM · Analytics, Core Platform Team, CheckUser
Milimetric added a project to T233004: Schema changes for `cu_changes` and `cu_log` table: Analytics.
Mon, Sep 30, 2:29 PM · Analytics, Core Platform Team Workboards (Clinic Duty Team), Patch-For-Review, Schema-change, DBA, CheckUser
Milimetric added a comment to T211881: graphoid: Code stewardship request.

@dr0ptp4kt and how will this work? The graphs will start out as some placeholder image as the vega module is brought in async?

Mon, Sep 30, 2:07 PM · Release-Engineering-Team-TODO (201908), Release-Engineering-Team (Code Health), Core Platform Team Legacy (Watching / External), Services (watching), Operations, Code-Stewardship-Reviews, Graphoid
Milimetric added a comment to T226631: Write user documentation for Matrix trial.

Oh, glad to hear, @revi, I'm happy to help edit the docs (I just got back from paternity leave), I'll look for updates here

Mon, Sep 30, 1:48 PM · User-revi, Documentation, Matrix

Thu, Sep 26

Milimetric added a comment to T212521: RFC: Reconsider how we run QUnit unit tests.

I'm back and getting up to speed. I'd need to hear what the unresolved issues are, so we can collaborate on a way forward. The patch that Jon proposed for core seemed like an improvement to me, for example. And it wouldn't affect how other extensions use qunit tests, but it seems to improve testing in general. So yeah, let's brainstorm together.

Thu, Sep 26, 9:05 PM · TechCom-RFC, Patch-For-Review, User-Jdlrobson
Milimetric added a comment to T233432: Figure out how to $ref common schema across schema repositories.

I agree the npm and submodule ideas are the best two. I prefer the submodule idea, after working through what I think are likely scenarios

Thu, Sep 26, 4:35 PM · Analytics-Kanban, CPT Initiatives (Modern Event Platform (TEC2)), Services (watching), Analytics-EventLogging, Event-Platform, Analytics

Aug 23 2019

Qgil awarded T129: Phabricator boards should live update a Love token.
Aug 23 2019, 1:54 PM · Phabricator (2019-08-22), Upstream, Wikimedia Phabricator RfC

Aug 19 2019

Milimetric added a comment to T131280: Make aggregate data on editors per country per wiki publicly available.

My latest patchset on that change above is just a draft implementing some of the thoughts so far. It implements the following so that we have a place to start from when we finalize our thoughts on privacy here:

Aug 19 2019, 8:52 PM · Product-Analytics, Analytics-Kanban
Milimetric added a comment to T131280: Make aggregate data on editors per country per wiki publicly available.

I could use a collaboration on the list of countries to blacklist. The paper that Nuria mentions includes: China, Cuba, Egypt, Indonesia, Iran, Kazakhstan, Pakistan, Russia, Saudi Arabia, South Korea, Syria, Thailand, Turkey, Uzbekistan, Vietnam. But the reason for censorship is pretty different in each country, and they don't all seem like they need a blacklist. I tried to guess at a first draft of the blacklist but honestly I'm not sure. The governments in not just those countries but those regions seem pretty troubling to me. And I don't have enough knowledge to know when something goes from troubling to dangerous.

Aug 19 2019, 1:34 PM · Product-Analytics, Analytics-Kanban
Milimetric added a comment to T131280: Make aggregate data on editors per country per wiki publicly available.

@Yair_rand, that's what we're trying to prevent, yes. The value of the data is great, and the risk will be minimized as much as possible. As Asaf points out above, we have had this conversation for a very long time. Our legal and security teams have thought about the potential danger of this dataset and signed off on us publishing it. Nevertheless, I personally would like to protect this dataset as much as possible and that's why I'm looking into how to make it harder to determine the country of specific editors. Does that make sense? Do you have additional concerns?

Aug 19 2019, 12:59 PM · Product-Analytics, Analytics-Kanban