[00:03:40] harej: I'm realizing that T212178 might be our biggest risk/blocker at the moment. [00:03:40] T212178: Rename the "Judgment" namespace to [new label] - https://phabricator.wikimedia.org/T212178 [00:04:16] Tricky of course, because we have to push it forward but in an inclusive way. [00:04:25] That's another thing I want to work on this week after I'm done with the cloud services report [00:05:10] my plan is to create a spreadsheet with all the options (one doesn't exist yet, right?) and compare them and then discuss a potential answer with you all and then post to the ticket with our team's intentions [00:06:09] harej: Thanks! I wonder if Keegan might be interested in the community side of this, too... [00:06:19] harej: I haven't made that spreadsheet, no. [00:07:05] awight: do you know more about releng blocking us and if it would interfere with launching a new kowiki model? [00:07:20] harej: ah--I was able to work around today! [00:08:25] https://ores.wikimedia.org/v3/scores/dewiki/172144111 [00:08:35] https://office.wikimedia.org/wiki/Topic:Urj9pea6tjwcrd1l [00:10:21] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10awight) [00:10:23] halfak: ^ [00:10:53] 8D [00:11:58] harej: Would you prefer that I explain the unblocking there, or maybe just edit yr post? [00:12:15] please post [00:19:14] harej: Were you around when Keegan was helping us btw? I suggest because of that history, and because it might be nice to have a community-headed colleague to bounce ideas off. [00:19:38] I don't specifically remember a consultation with Keegan [00:22:41] * awight scratches head--I feel like Trizek also helped our team within the last year [00:23:36] https://phabricator.wikimedia.org/search/query/ggndbVdnecOo/#R [00:24:56] Keegan notable for having worked on Jade specifically, though this was pre- significant changes of course, so could use a refresher I'm sure. [00:26:25] If this was before July 2018 I have no memory of it :) [00:40:07] 10Scoring-platform-team, 10Gerrit, 10GitHub-Mirrors, 10Release-Engineering-Team: articlequality repo mirroring is broken - https://phabricator.wikimedia.org/T212962 (10awight) 05Open→03Resolved a:03awight I was able to work around by pushing directly to gerrit. If it happens again, I'll reuse this t... [00:40:26] Also, do we have this model development/deployment procedure documented somewhere? I felt silly for not being able to adequately answer MMiller's questions on demand regarding a workflow our team has done many times already. [00:45:01] harej: https://www.mediawiki.org/wiki/ORES/New_model_checklist [00:45:59] Thank you! [00:46:06] I love that doc and am happy to add any suggestions you come up with. [00:46:16] https://wikitech.wikimedia.org/wiki/ORES [00:47:04] harej: You should do the next new model request... [03:47:26] 10ORES, 10Scoring-platform-team (Current), 10Analytics, 10Patch-For-Review: Wire ORES scoring events into Hadoop - https://phabricator.wikimedia.org/T209732 (10awight) This is the idea, https://gerrit.wikimedia.org/r/#/c/analytics/refinery/+/481025/ Should I avoid creating a view, though? I don't see any... [04:22:10] 10ORES, 10Scoring-platform-team (Current), 10Analytics, 10Patch-For-Review: Wire ORES scoring events into Hadoop - https://phabricator.wikimedia.org/T209732 (10awight) >>! In T209732#4861475, @awight wrote: > Should I avoid creating a view, though? I don't see any precedent for it, although the access pat... [13:51:22] 10ORES, 10Scoring-platform-team (Current), 10Patch-For-Review: Support CIDR range whitelist for ORES throttling - https://phabricator.wikimedia.org/T210103 (10akosiaris) Change has been deployed and all uwsgi/celery processes restarted to pick up the change [14:43:02] 10Jade, 10Scoring-platform-team (Current), 10DBA, 10Operations, and 2 others: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10daniel) Moving this to "backlog" for now. This should have happened right after last week's TechCom meeting,... [15:11:24] * halfak looks into translatewiki API issue. [15:33:50] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10Halfak) Based on how the API performance I noted during feature extraction, I didn't expect an issue. Maybe someone from translatewiki can comment about what kind of API... [15:42:26] akosiaris, it looks like we can't access translatewiki's API from ORES nodes. [15:42:37] I just realized we might be blocking that because it's outside of prod. [15:46:15] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10Halfak) After some more testing, I think it's likely that we're blocking ourselves. Translatewiki.net is outside of prod. It is the only API ORES has ever tried to acces... [15:46:47] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10Halfak) @JBennett may have some thoughts on this from security's point of view. [15:53:42] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10Nikerabbit) I can confirm translatewiki.net does not currently block any WMF ips. [15:54:25] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10awight) >>! In T213131#4862799, @Halfak wrote: > After some more testing, I think it's likely that we're blocking ourselves. Translatewiki.net is outside of prod. I thin... [16:01:18] 10Jade, 10Scoring-platform-team (Current), 10DBA, 10Operations, and 2 others: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10Halfak) The meeting happened. @Krinkle confirmed that his questions had been answered. I imagined that he'... [17:36:08] 10ORES, 10Scoring-platform-team, 10Operations, 10Release Pipeline (Blubber): Build blubber file for ORES - https://phabricator.wikimedia.org/T210268 (10thcipriani) [17:37:54] 10ORES, 10Scoring-platform-team, 10Operations, 10Release Pipeline (Blubber): Build blubber file for ORES - https://phabricator.wikimedia.org/T210268 (10thcipriani) [17:37:57] 10ORES, 10Scoring-platform-team, 10Operations: [Epic] Deploy ORES in kubernetes cluster - https://phabricator.wikimedia.org/T182331 (10thcipriani) [17:38:02] 10ORES, 10Scoring-platform-team, 10Operations, 10Release Pipeline (Blubber), 10Release-Engineering-Team (Backlog): The continuous release pipeline should support more than one service per repo - https://phabricator.wikimedia.org/T210267 (10thcipriani) [18:00:54] Finished management meeting. Getting lunch [18:28:15] 10ORES, 10Scoring-platform-team, 10translatewiki.net: Are we breaking translatewiki's API? - https://phabricator.wikimedia.org/T213131 (10Bawolff) >>! In T213131#4862801, @Halfak wrote: > @JBennett may have some thoughts on this from security's point of view. You should make ores use http://url-downloader... [18:31:25] 10ORES, 10Scoring-platform-team, 10translatewiki.net: ORES should be configurable to access some APIs through a proxy - https://phabricator.wikimedia.org/T213203 (10awight) [18:57:02] 10ORES, 10Scoring-platform-team (Current), 10Analytics, 10Patch-For-Review: Wire ORES scoring events into Hadoop - https://phabricator.wikimedia.org/T209732 (10awight) [19:47:42] I have a person on Telegram who is interested in working on AI applications for Wikidata and Commons [19:47:47] I don't want to make this person use IRC... [19:59:26] email / phabricator maybe? [20:00:59] Do we have any other good options for an open channel we could offer to people? [20:01:30] Slack is walled off. Could we create a telegram room? [20:01:35] *group [20:01:41] I'd be fine with a Telegram group [20:01:41] harej: Any interest in heading to https://en.wikipedia.org/wiki/Wikipedia:Meetup/San_Francisco/Stanford_Wikipedia_Day_2019 next Tuesday? [20:04:13] halfak: I just created a "Wikimedia AI" group in Telegram and added you [21:09:54] PROBLEM - ORES worker labs on ores.wmflabs.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 INTERNAL SERVER ERROR - 5687 bytes in 5.057 second response time [21:09:56] PROBLEM - ORES web node labs ores-web-01 on ores.wmflabs.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 INTERNAL SERVER ERROR - 5687 bytes in 5.070 second response time [21:11:06] RECOVERY - ORES web node labs ores-web-01 on ores.wmflabs.org is OK: HTTP OK: HTTP/1.1 200 OK - 540 bytes in 1.443 second response time [21:13:26] RECOVERY - ORES worker labs on ores.wmflabs.org is OK: HTTP OK: HTTP/1.1 200 OK - 540 bytes in 0.150 second response time [22:42:02] (03CR) 10jenkins-bot: Localisation updates from https://translatewiki.net. [extensions/JADE] - 10https://gerrit.wikimedia.org/r/482952 (owner: 10L10n-bot) [22:56:08] (03CR) 10jenkins-bot: Localisation updates from https://translatewiki.net. [extensions/ORES] - 10https://gerrit.wikimedia.org/r/482963 (owner: 10L10n-bot) [23:12:46] 10ORES, 10Scoring-platform-team, 10Documentation: Peer review ORES Feature Injection doc page - https://phabricator.wikimedia.org/T213207 (10Aklapper) Assuming this is about #ORES? [23:30:22] Finally sat down with google draw. https://docs.google.com/drawings/d/13oPP12vLcER-1aC69Qrj4bP6TSVkh7_RSG1QaZcO5lw/edit [23:31:02] harej, ^ Still missing a lot of stuff, but I have a few basic bits in place. I want to make a few versions with this much detail. [23:37:08] * harej takes a break from calculating Chi Squared statistics [23:41:40] O_O [23:43:54] halfak: Looks like a good start. I'm concerned about the schema menu at the top; how many different annotation schemata are you expecting in the long haul? [23:48:49] That's a good question and I think it is a limitation of this strategy. [23:49:06] This strategy is inspired by Special:Preferences. [23:49:45] On the bright side, it solves for a lot of other issues. [23:50:29] Anyway, it's time to push the pedals. I'll have a little writeup for each of these versions to help explain the benefits and drawbacks I see. We can extend that through discussion. [23:51:02] I'm not sure Special:Preferences is a great example of a design pattern [23:51:16] And, it is appreciated, thank you