[08:16:33] o/ [10:01:25] 10Scoring-platform-team (Current), 10Discovery, 10ORES, 10Wikidata, and 3 others: Measure maturity/quality of Wikidata items in a way it can be queried - https://phabricator.wikimedia.org/T166427 (10Ladsgroup) We can pick this up now I think. It might need some extension work but I think it's possible. [10:05:30] 10Scoring-platform-team, 10Community-Tech, 10MediaWiki-extensions-ORES, 10MediaWiki-extensions-PageAssessments: Implement ORES wp10 predictions in PageAssessments tool - https://phabricator.wikimedia.org/T156820 (10Ladsgroup) The data is now stored in ores_classification table. Whether it should be used in... [10:46:18] 10Scoring-platform-team, 10Edit-Review-Improvements-RC-Page, 10Growth-Team, 10MediaWiki-extensions-ORES, and 3 others: Index on oresc_probability, temporarily or permanently - https://phabricator.wikimedia.org/T175778 (10Ladsgroup) a:03Ladsgroup I'm officially picking this up but first, I need a maintena... [10:49:14] 10Scoring-platform-team (Current), 10MediaWiki-extensions-ORES, 10User-Ladsgroup: Rework PurgeScoreCache.php - https://phabricator.wikimedia.org/T200680 (10Ladsgroup) p:05Triage>03High [12:31:50] afk for lunch [12:32:21] 10Scoring-platform-team, 10ORES, 10Wikibase-Quality-Constraints, 10Wikidata: quick overview of the quality of an item - https://phabricator.wikimedia.org/T195703 (10Jan_Dittrich) Could I get a screenshot of the gadget/script UI, so we could have a look (I could not get it running myself right now) [12:40:40] Amir1: there are a bunch of 'Use of undefined constant NS_JADE_TALK' errors in the logs, is awight aware of that? [12:42:09] on second look, probably just deploy byproducts [13:36:46] * halfak catches up on email. [13:57:04] halfak: I won’t be able to join this morning’s meeting due to a schedule conflict [13:57:53] OK anything we should consider or review in your absence? E.g. a progress update or something you have in the Review column? [13:58:56] Not particularly. I did talk over an idea Adam had about creating a central wiki for judgments and I expressed my concerns. [14:00:04] Ahh yes. That seems like it would be an i18nightmare. [14:00:16] Among other issues. [14:00:20] It would be multiple types of nightmares :) [14:11:53] I updated etherpads. [14:12:39] thanks harej :) [14:18:50] 10Scoring-platform-team (Current), 10Discovery, 10ORES, 10Wikidata, and 3 others: Measure maturity/quality of Wikidata items in a way it can be queried - https://phabricator.wikimedia.org/T166427 (10Halfak) It looks like the item quality model isn't loaded yet. See https://quarry.wmflabs.org/query/28639... [14:27:22] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10mark) I am a bit confused by this RFC/proposal as it stands now, as I feel it doesn't really reflect the discussion... [14:28:24] halfak: I have several things waiting for review in the review column [14:30:37] Hey Amir1! Still working through email. I'll check the review column as soon as I'm done with the wave :) [14:31:10] cool [15:02:22] 10Scoring-platform-team (Current), 10MediaWiki-extensions-ORES, 10User-Ladsgroup: Run PurgeScoreCache.php on all wikis that have ORES enabled - https://phabricator.wikimedia.org/T200680 (10Ladsgroup) [15:11:24] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10Harej) Thank you for the summary, @mark. I am interested in this perspective that we can get the same user experien... [15:15:18] harej, EC! [15:15:21] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10Halfak) @mark, I think you have raise some good points here. I think there is a point of confusion around the "hop... [15:23:32] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10Halfak) I'm OK with the move to wikimedia github, but gerrit would be really difficult for our more scholarly collaborat... [15:32:23] 10Scoring-platform-team, 10ORES, 10Wikibase-Quality-Constraints, 10Wikidata: quick overview of the quality of an item - https://phabricator.wikimedia.org/T195703 (10Halfak) {F24333890} Note the prediction right underneath the title. [15:35:53] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10Marostegui) >>! In T200297#4461793, @Halfak wrote: > > Past evidence (e.g. see Flow) suggests that it is not reali... [15:39:27] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10Ladsgroup) >>! In T194212#4461836, @Halfak wrote: > It seems like that was the driving need behind this move, right?... [16:09:47] 10Scoring-platform-team (Current), 10Wikidata, 10User-Ladsgroup: Run analysis of revert time and number changes over time for wikidata - https://phabricator.wikimedia.org/T189962 (10Halfak) Make a report! Start from https://meta.wikimedia.org/wiki/Research:New_project :) [16:59:09] o/ FajneFarita :) [16:59:24] * halfak waits for notconfusing(Max) to join in [16:59:30] \o/everybody [17:03:16] question about Microsoft buying Github: is the allotted space our main concern? or we also have a problem with being at mercy of a corporation, etc.? [17:07:27] halfak: Do you think it's okay if I pick up https://phabricator.wikimedia.org/T160692 ? given the recent incident we had [17:07:52] +1 Amir1. I don't know why we dropped it earlier. [17:11:43] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10awight) Hi, it's great to see the activity on this RFC, thank you all for the input. To expand on our answer about... [17:12:12] FajneFarita: Good question. What we were discussing today was just the storage allotment and pricing, but we’ve all expressed discomfort about the corporate takeover as well. [17:12:45] awight: got it, thanks for the answer [17:12:55] Honestly, I think the risk has been there all along, and it might be better now that VC money has been replaced by corporate money. [17:13:29] i.e. Microsoft can’t just close GH now cos there will be enormous PR backlash. [17:18:14] ^ good point [17:18:17] * halfak --> lunch! [17:18:21] awight: oh no, they won't close it. they'll try pt profit on it) and will reluctantly support free accounts. But I do think the Wikipedia can be an exception. My concern was that users can migrate from Github somewhere else in the near future. Like they did from Skype. [17:18:36] good call. [17:19:45] And M$ does decide to squeeze everyone else for pennies, we would have to move in order to withdraw our support, regardless of getting a “free tier” deal. [17:21:03] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10awight) @Marostegui, I'd like to explore how we might be able to use x1 for storage. We aren't currently consideri... [17:25:23] although the "new" [17:25:36] MS is pretty open source friendly from what I've read [17:26:24] halfak, awight: i would like to participate in the new wikilabels campaign (and refresh in my memory what vandalism is). could you direct me to the right page? [17:26:53] FajneFarita: which language? http://labels.wmflabs.org [17:27:03] English, russian [17:27:28] http://labels.wmflabs.org/stats/enwiki/ [17:27:35] http://labels.wmflabs.org/stats/ruwiki/ [17:27:42] (no campaigns) [17:28:09] saurabhbatra: I haven’t read much about it, do you know what their motivation is behind the purchase? [17:28:50] FajneFarita: http://labels.wmflabs.org/ui/enwiki/ [17:29:37] nope, i've just read that Satya has a pro-open source stance [17:30:09] with them supporting linux and making a lot of their offerings like Powershell open-source [17:30:20] Makes sense, FLOSS has proven to be a great thing for bottom lines almost everywhere. [17:30:39] as opposed to Balmer who thought FOSS was a joke... [17:30:46] Also a good way to deal with aging cruft maintenance :-) [17:31:03] awight: thanks. what Labeling Unsourced Statements is for? sounds research-promising.. [17:31:04] huh, good to know that bit of history! [17:31:29] FajneFarita: :-). I’m not sure whose project that is, let me find more about it. Could be the Research dept... [17:31:52] btw i completed the feature engineering for our model *yay* [17:32:12] just waiting for casey to up the sklearn on the server so i can get some plots [17:32:35] That’s awesome, can’t wait to see! [17:33:17] FajneFarita: This is the high-level task about the project, https://phabricator.wikimedia.org/T171230 [17:34:40] Adam, thank you [17:35:09] FajneFarita: here it is, https://meta.wikimedia.org/wiki/Research:Identification_of_Unsourced_Statements [17:35:29] Just let us know if you want help connecting with anyone working on that. [17:36:27] FajneFarita: Ah, @miriam is IRC for the PI [17:37:44] Miriam is in UTC+1 [17:38:03] ok. great. will ping you later. --->away [17:38:28] o/ [17:44:28] 10Scoring-platform-team, 10Community-Tech, 10MediaWiki-extensions-ORES, 10MediaWiki-extensions-PageAssessments: Implement ORES wp10 predictions in PageAssessments tool - https://phabricator.wikimedia.org/T156820 (10Niharika) We'll be happy to provide guidance and review code if someone wants to volunteer t... [17:46:18] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10Ladsgroup) @greg Hey, in our meeting @Halfak pointed out that we are storing large repos that is way beyond size limit o... [17:50:16] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10greg) >>! In T194212#4462232, @Ladsgroup wrote: > @greg Hey, in our meeting @Halfak pointed out that we are storing larg... [18:02:05] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10awight) There's another interesting point here, from @mark, > According to T196547 there seems to be the expectatio... [18:05:09] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10awight) I want to explicitly ask something that has come up among our team: Can we agree on guidelines for new cont... [18:06:37] * awight mops brow [18:15:06] gotta run for a long lunch o/ [18:52:00] 10Scoring-platform-team (Current), 10Discovery, 10ORES, 10Wikidata, and 3 others: Measure maturity/quality of Wikidata items in a way it can be queried - https://phabricator.wikimedia.org/T166427 (10Smalyshev) @Halfak the most preferred way would be to get it into page_properties. But if it's in a DB acces... [18:59:54] 10Scoring-platform-team (Current), 10Discovery, 10ORES, 10Wikidata, and 2 others: Include ORES predictions in RDF export - https://phabricator.wikimedia.org/T200716 (10Halfak) p:05Triage>03Normal [19:00:41] 10Scoring-platform-team (Current), 10Discovery, 10ORES, 10Wikidata, and 3 others: Measure maturity/quality of Wikidata items in a way it can be queried - https://phabricator.wikimedia.org/T166427 (10Halfak) Great! I created T200716 to track that work. :) [19:07:21] 10Scoring-platform-team (Current), 10Wikidata, 10User-Ladsgroup: Run analysis of revert time and number changes over time for wikidata - https://phabricator.wikimedia.org/T189962 (10Ladsgroup) Started this: https://meta.wikimedia.org/wiki/Research:Revert_time_analysis Will work on it more in the next couple... [19:21:29] (03PS1) 10Sbisson: [POC] Introducing a hook to decide what to score [extensions/ORES] - 10https://gerrit.wikimedia.org/r/449274 (https://phabricator.wikimedia.org/T199357) [19:25:58] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10jcrespo) > Can we agree on guidelines for new content extensions, so that nobody needs to go through this discussio... [19:26:51] Amir1 (for when you're back online) I've been trying different ways to score 'draftquality' for revs of pages in PR queue. Moving the PT hooks to ORES introduces disturbing coupling, maybe too much duplication, and a race condition that is hard to get around. [19:27:24] * halfak sneaks back in after lunch + big meeting block [19:27:39] awight, might know something about stephanebisson's question [19:27:46] Amir1: I've documented a proof of concept with a hook: https://gerrit.wikimedia.org/r/#/c/449274/ and https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/PageTriage/+/449275/ [19:28:15] Amir1: It's not production ready but the idea should be clear. Let me know what you think. Thanks. [19:28:22] stephanebisson: I'm around [19:28:58] * halfak works on Amir1's totally unrelated PRs :) [19:30:05] stephanebisson: I like the concept of introducing hooks in ores extension, basically it's very much following DIP. We have done it in Wikibase before (now WikibaseLexeme extension uses hooks that Wikibase extension defined) [19:30:54] and it's better that PageTraige extension depend on ORES extension and not the other way around but at the same triggering jobs on behalf of ORES extension in PageTriage extension is problematic in the future [19:31:14] overall hooks should be avoided but I think this is a great compromise [19:31:58] stephanebisson: Does this answer your questions? [19:32:29] Amir1: Yes, I'm glad you're onboard. [19:32:51] Amir1: Do you have preferences about hook name, params, position? [19:34:11] stephanebisson: I haven't looked at the patch but make sure to hook into the cleanParent part, otherwise it might make the table unnecessary big, if it's not possible, it's not a big deal either IMO [19:34:37] stephanebisson: right now, I'm deleting the old scores from ores_classification table everywhere, FYI [19:34:58] Amir1: what do you mean by 'old'? [19:35:34] the ones that are attributed to revisions that are not in recentchanges anymore [19:37:32] Amir1: re cleanParent: Do you think it should be a separate hook or a single hook that receives and modifies both $models and $parentsToClean (with some refactor of the code to make that possible)? [19:37:53] stephanebisson: one hook is better IMO [19:39:23] Yeah, I think so too. [19:39:36] Thank you! [19:40:55] Amir1: Looking at the config now... what if we configure 'draftquality' with cleanParent => true ? For most pages it would not do anything since only the first rev is scored. For articles in PT queue it would clean things up and keep only latest rev. [19:41:29] stephanebisson: hmm, that would work [19:45:03] Amir1: It sounds like we have a plan. I'll rework the hook patches so they can be reviewed and submit a config patch to enable cleanParent for 'draftquality' on enwiki. Do you have any concerns that we haven't discussed? [19:48:02] stephanebisson: nothing so far :) It looks great to me [19:48:12] Amir1: thanks [20:01:17] Amir1 or awight, did we ever get a review of the JADE extension? [20:01:58] IDK, I know about a security and that's all [20:02:08] OK gotcha. [20:02:29] I'm struggling to understand what jynus seems to expect WRT to DBA review. [20:02:41] Schema changes make sense to me 100% [20:03:10] But new namespaces -- that's a new one to me. [20:03:19] I'm looking for any process that might have caught this. [20:03:31] I thought there was an extension review process of some sort. [20:04:23] It's weird to get yelled at for violating a policy when I can't even identify what policy is being discussed. :| [20:05:27] 10Scoring-platform-team (Current), 10MediaWiki-extensions-ORES, 10User-Ladsgroup: Run PurgeScoreCache.php on all wikis that have ORES enabled - https://phabricator.wikimedia.org/T200680 (10Ladsgroup) I ran it everywhere but it failed on wikidata, each query to delete 1000 rows takes around 10 minutes :/ Will... [20:17:52] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10Halfak) @Jcrespo, I can't find the policy you are referencing. Can you link to the specific lines that apply here?... [20:18:06] * halfak braces for impact [20:23:41] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10Ladsgroup) I know, we were thinking of the middle step (moving from wiki-ai organization to wikimedia origination in git... [20:26:10] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10Halfak) FWIW, getting LFS in gerrit/phab was critical for our deployment processes and regardless of where development i... [20:27:34] (03PS2) 10Sbisson: Introducing ORESCheckModels hook [extensions/ORES] - 10https://gerrit.wikimedia.org/r/449274 (https://phabricator.wikimedia.org/T199357) [20:30:48] (03CR) 10jerkins-bot: [V: 04-1] Introducing ORESCheckModels hook [extensions/ORES] - 10https://gerrit.wikimedia.org/r/449274 (https://phabricator.wikimedia.org/T199357) (owner: 10Sbisson) [20:31:41] (03PS3) 10Sbisson: Introducing ORESCheckModels hook [extensions/ORES] - 10https://gerrit.wikimedia.org/r/449274 (https://phabricator.wikimedia.org/T199357) [20:56:02] Amir1, I got it! https://github.com/mediawiki-utilities/python-mwbase/pull/3 [20:56:15] I was doing something stupid for a good long time :) [20:57:24] 10Scoring-platform-team (Current), 10revscoring, 10User-Ladsgroup, 10artificial-intelligence: Rewrite scoring libraries to replace pywikibase with mwbase - https://phabricator.wikimedia.org/T194758 (10Halfak) I got the damn python 3.4 problem fixed! https://github.com/mediawiki-utilities/python-mwbase/pull/3 [21:24:45] 10Scoring-platform-team (Current), 10Discovery, 10ORES, 10Wikidata, and 2 others: Include ORES predictions in RDF export - https://phabricator.wikimedia.org/T200716 (10Smalyshev) There is another option - make an API like https://www.wikidata.org/wiki/Q2?action=constraintsrdf which would export the data in... [21:38:27] stephanebisson: Amir1: I like the new hook, fwiw... [21:39:15] halfak: Yes, we’ve gotten official review: https://phabricator.wikimedia.org/T188307 [21:39:42] Design review was discussed and waived cos we have no new UI: https://phabricator.wikimedia.org/T190690 [21:40:00] DBA review… didn’t happen because there is no schema! [21:40:16] Right. [21:40:38] I did apologize for surprising them with this, but yeah nobody has spelled out what the “policy violation” is. [21:40:44] unless something happened during my lunch. [21:40:54] * awight continues backscrolling [21:40:58] I explicitly asked for the lines this time. [21:41:01] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10greg) >>! In T194212#4462790, @Halfak wrote: > FWIW, getting LFS in gerrit/phab was critical for our deployment processe... [21:41:29] 10Scoring-platform-team, 10Release-Engineering-Team (Watching / External): Another round of discussion about wiki-ai's GitHub->gerrit mirroring - https://phabricator.wikimedia.org/T194212 (10greg) (for the record, that's how git-annex works, which is my mental model for how all these things should work ;) ) [21:45:17] halfak: FYI here’s the checklist I was working from, https://www.mediawiki.org/wiki/Review_queue [21:45:39] Finally, it was “Preparing for deployment” section 3 [21:49:49] Looks pretty clear to me. [21:49:58] It's not like we've danced around some clear sign post. [21:51:41] This is all very regrettable. I think the "policy violation" discussion is a dead end. Ultimately, I think this comes down to the conversations about content growth rates in JADE and what our infra can handle. [21:52:48] If our infra can handle JADE, it should be OK. I see assessments of what kind of patrolling activity we expect to see recorded in JADE, but I don't see discussions of the limits of our infra. [21:53:00] I like your question about what kind of growth rates would be acceptable [21:53:02] awight, ^ [21:56:06] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10awight) @jcrespo Thanks for the good tips, I agree with most of what you say. FWIW, I was working off of the exten... [21:56:35] I don’t see it as a dead-end, unless I’m misunderstanding. [21:57:17] I’m mostly just following through on your comment in this morning’s meeting, that the guidelines are incredibly fuzzy... [21:57:49] Currently, it reads “it you have reasons to think that a database review is needed”, without giving any examples or criteria... [21:57:52] crazy stuff [21:58:12] So IMO clarifying the guidelines is a good way to help future us [21:58:43] I’m thinking it might not be a dead-end for us, because we can step back, refine the guidelines without the emotional coupling caused by a concrete project waiting for deployment. [21:58:53] Then we can come back and apply those guidelines, I would hope. [21:58:56] halfak: ^ [21:59:50] I guess I think it's a dead end because it's emotions, more than the needs of the current situation, that are driving the accusations about policy. [21:59:58] +1 [22:01:33] Unfortunately, I don’t think this crew is okay with having a side discussion about the bigger picture, I get the feeling that they see me as side-stepping or something. [22:01:39] Which I am ;-) [22:01:43] but that’s how it’s done. [22:12:48] Right. This side-stepping narrative needs to be address regardless of policy. It's a separate problem to be accused of being a bad actor (violating policy). [22:15:19] OK I think there's no more to do right now. I'm going to go do some gardening :) Have a good one, folks. [22:16:59] That’s a difficult call. I’ve been addressing the policy thing directly so that it can be fixed, but what I meant above was actually about jynus’s comments in https://phabricator.wikimedia.org/T200297#4455344 [22:17:31] This was insisting that we roll the discussion back to a previous point where I was on the ropes, it seems. [22:19:09] But what concerns me is that I might get the same pushback for trying to address the policy-level problems. [22:19:19] like “why aren’t you sticking to the subject” [22:20:07] In my mind, a healthy discussion is evolving the subject matter collaboratively, but the perspective that seems to be in use is “stick to one point so that I can finish demolishing it" [22:20:14] I can see where that comes from... [22:20:49] I’m open to advice about how to resolve, maybe if we “finish” a topic before starting others… so inefficient, though... [22:58:20] Does anyone know off-hand what version of Postgres Wikilabels is running? 9.5 or 9.6 probably? [23:20:37] oof, I would log in for that. Or check the backups... [23:20:43] Let me see if I have permission. [23:22:41] thanks, its just not in the documentation, and that's a gotcha that i know from experience [23:23:00] im going to try and create a new view for it that's on the session level [23:23:45] debian 8.1 [23:24:00] I missed what happened at postgres 9.6 [23:24:24] You should get access to the wikilabels group on wikitech horizon [23:24:38] *Cloud VPS [23:25:01] Do you have an account yet? [23:27:35] awight: in the new wikilabels campaign, are intentionally including edits from the talk namespace to label? [23:27:45] like this one https://en.wikipedia.org/w/index.php?diff=699726235 [23:29:14] notconfusing: psql (9.4.15) [23:29:29] awight: thank you so much, that's really helpful [23:29:51] awight: i have a horizon account [23:30:08] FajneFarita: Which campaign, editquality? [23:30:25] If so, then yes I think it makes sense that we sample from every namespace including Talk. [23:31:09] notconfusing: wikitech u/n is notconfusing and login name should be notconfusing? [23:33:08] awight: i log into horizon as my wikitech legacy name "Maximilianklein" [23:35:23] FajneFarita: fwiw I cannot find the query that was used to generate the enwiki 2016 editquality sample, yet. Can you paste me an URL showing which campaigns you’re talking about, and I’ll get you the query... [23:35:31] notconfusing: Oops, sorry to out you :-) [23:36:25] I'm not embarrassed, sometimes we're clark kent as well (or something) :P [23:36:31] awight: Edit quality (20k 2016 sample). [23:37:23] notconfusing: I should have added you, but not seeing feedback in the web console yet. Can you log into wikilabels-01.wikilabels.eqiad.wmflabs ? (Do you have the labs ssh config?) [23:37:41] I do, I'll try logging in [23:39:54] awight: so you're saying talk namespace signal can benefit the classifier? I just feel it may confuse it because what people are allowed to write in the talk is so different from what is appropriate in the main nm. I hope, there will be a way tell apart talk and main namespace edits later when they are all labeled and aggregated into train sets... [23:40:11] it asked me to accept the fingerprint, but then `Connection closed by UNKNOWN port 65535` [23:40:12] halfak: Did you document the sample for https://phabricator.wikimedia.org/T163464 ? [23:40:29] I was hoping to find it in the editquality/config/wikis/enwiki.yaml [23:40:44] notconfusing: ooh, can you ssh -vv [23:40:54] just let me know if it’s rejecting your user [23:41:00] or log into another labs project [23:41:05] bastions changed, that might be the issue. [23:41:12] please confirm your labs ssh config [23:41:15] in other words [23:41:20] [23:42:20] yeah i'll look trhough that. I am able to `ssh wigi.eqiad.wmflabs` (my own project) so this is curious [23:42:45] let me keep adding you. [23:43:59] notconfusing: Can you confirm your username? “Maximilianklein” [23:45:46] I think so. This works for me: `$ ssh maximilianklein@wigi.eqiad.wmflabs` and logged into Horizon I see my username as "Maximilianklein" (with capital M) [23:46:35] Thanks [23:49:19] notconfusing: k you are added for real now. [23:52:09] yes, i can confirm i am. thanks! [23:52:39] alright time to make a delve and make a pull request. this might be useful because I see a few forms on wikilabels that aren't on github [23:53:51] gtg, but this is good, one environmental set-up barrier down [23:59:07] 10Scoring-platform-team, 10DBA, 10JADE, 10Operations, 10TechCom-RFC: Introduce a new namespace for collaborative judgments about wiki entities - https://phabricator.wikimedia.org/T200297 (10awight) @mark I think you're right that our future potential use cases involving bulk bots should be dropped and re... [23:59:15] halfak: ^ fyi [23:59:19] I think that will help.