[11:25:37] hello! sysops here? [11:26:51] Auregann_WMDE: seems like i lost my invitation to #wikidata-admin do you know who could help? [11:41:17] youhou ? [11:41:37] hi Harmonia_Amanda [11:41:51] nikki: hello! [11:42:20] are you not able to join that channel like any other channel? or does it say you don't have access? [11:42:49] it says #wikidata-admin est sur invitation uniquement. [11:42:58] wich means "invitation only" [11:43:09] well, ok, but I should be on the list... [11:43:19] is it because i use kiwiirc ? [11:45:01] I'm not sure how to fix it :( [11:45:19] :s [11:45:53] nikki: can you please look at https://www.wikidata.org/wiki/Wikidata:Administrators%27_noticeboard then? [11:46:27] I've asked in there in case people aren't paying attention to this channel... hopefully someone else who knows what they're doing is around [11:48:22] nikki: thank you! [12:05:08] Harmonia_Amanda: sorry I have no idea [12:46:49] Both hhvm and php5.5 segfault on us in travis currenlty [12:46:50] grr [12:50:23] hhvm issue the one that has been there for few weeks or something new? [12:53:04] leszek_wmde: php5.5 is new to me [12:53:19] didn't look at anything specifically, but this is super annoying [12:53:23] hoo: yeah, I meant hhvm only. php55 is indeed new [12:53:38] often disabling gc fixes it, but that's just awful [12:53:52] hoo: this is for build or "everything" is red? [12:54:03] hm? [12:55:11] I meant in which projects on travis those segfaults happen [12:56:04] Oh, the wikibase extension build [12:56:10] I don't monitor any others [12:56:17] got it [12:56:25] (the other ones are usually managed on github, so integration there is better) [12:56:25] that's bad indeed [13:07:45] https://github.com/Wikidata-lib/PropertySuggester-Python/pull/21 Trivial change [13:08:05] aude: leszek_wmde: ^ [13:11:49] thanks leszek_wmde :) [13:12:04] hoo: such reviews I like [13:19:31] :) [13:20:07] hoo: i wonder if this code should also be moved to gerrit? [13:20:19] aude: hm [13:20:23] It could be [13:20:28] if we need it for production [13:20:42] I run it on tool labs, but it's needed for the production instance [13:20:48] yeah [13:21:25] it's annoying to have code scattered everywhere [13:21:40] but doesn't have to be done right now [13:24:43] https://phabricator.wikimedia.org/T166672 [13:25:10] hoo: readonly is now a recoverable error again in pywikibot [13:25:32] That will reduce the number of complaints [13:26:14] multichill: Ah, nice [13:26:29] I'm curios for the numbers [13:26:44] might indicate some problematic usage patterns or other issues [13:27:01] It was always something the bot would recover from, but some api messages changed breaking the whole thing [13:50:15] Hi chan, I'm a computer science student working on StrepHit project https://meta.wikimedia.org/wiki/Grants:IEG/StrepHit:_Wikidata_Statements_Validation_via_References/Renewal#Primary_Sources_Tool Is anyone available to chat on some technical stuff of Wikidata? [14:05:15] * Afnecors go home [14:32:45] Afnecors: don't ask to ask, just ask! [14:42:16] We want to move Primary sources tool (a wikidata gadget) to Wikibase or create a new MediaWiki extension, because of consistency with Wikidata code. What are ant understand the pro and cons? [15:42:35] Hjfocs: ^ [16:46:30] hello --- If I'd like to find ?items whose occupation is only author and writer (only these two occupations). How would this restriction look like? [16:49:30] SELECT ?item WHERE { {?item wdt:P106 wd:Q36180 } UNION { ?item wdt:P106 wd:Q482980 } } sky_ ? [16:53:21] Unfortunately no. This would include both instances but wouldn't exclude any other, and that is what i aim to do.. If you run the script and open the first item, you see there are many fields in the occupation area and not only the desired two [16:56:05] sky_: so you want people who have two (and only two) occupations, one of which is author, the other is writer? [16:56:21] I would like to know which items have only certain professions/occupation, such as in the example: items whose profession/occupation are only author + writer [16:56:28] exactly nikki [16:57:43] I think http://tinyurl.com/ybf6fj6n might do that [16:58:17] (the minus { } section finds people with occupations other than those two and removes them from the previous results) [17:00:19] yes awesome. Thanks nikki [17:00:28] it works [17:02:11] also thanks multichill [17:04:34] :) [19:50:22] Shouldn't it be https://www.wikidata.org/wiki/Q83364 instead of https://www.wikidata.org/wiki/Q18338317? https://www.wikidata.org/wiki/Property_talk:P1576 [19:50:58] See also the proposal... https://www.wikidata.org/wiki/Wikidata:Property_proposal/Archive/26#P1576 [19:53:27] nikki: thoughts? [19:54:43] Does anyone know where I can find project goals for the Wikidata product team? [19:55:12] hall1467: mostly on Phabricator, for example https://phabricator.wikimedia.org/T150178 [19:55:40] Okay, thank you [20:05:11] sjoerddebruin: hm... not sure whether one way is better than another, but I do think the property's description doesn't really make sense with using subclasses of people as values [20:05:42] Going to ask on project chat [20:05:46] like a vegetarian isn't a way of life [20:06:00] vegetarianism is [20:06:03] yeah, exactly [20:06:16] I just want some people saying that I'm right. :) [22:40:50] hello