[02:04:16] <Amir1>	 ebernhardson: *waves* feel free to ping in IRC to discuss details of the gui work
[06:32:35] <dcausse>	 errand (first day of middle school for the young one), will be back between 10 and 11am CEST
[07:23:10] <zpapierski>	 errand
[09:33:33] <gehel>	 zpapierski, dcausse: any chance we could do our hiring debrief now?
[09:33:47] <dcausse>	 gehel: in 10 min?
[09:34:01] <gehel>	 works for me, let's see if Zbyszko is back
[09:34:10] <gehel>	 otherwise, let's keep this afternoon meeting
[09:42:24] <gehel>	 let's keep this afternoon
[09:42:27] <gehel>	 coffee time
[09:46:28] <zpapierski>	 I' m back
[09:46:47] <zpapierski>	 I see 4 min too late
[10:16:48] <dcausse>	 lunch
[10:36:40] <zpapierski>	 gehel: turned out newer version of spotbugs has exactly the same issue with try-with-resources, I just haven't reached that module before :( 
[10:37:24] <zpapierski>	 on top of dozens issues with the EI_EXPOSE_REP, e.g. when returning Instant (class that is immutable)
[10:37:46] <zpapierski>	 I'm not going to update that version, I'll ignore the original issue and report upstream issue with EI_EXPOSE_REP
[12:15:23] <zpapierski>	 ok, no need to - https://github.com/spotbugs/spotbugs/issues/1601
[12:23:21] <gehel>	 ryankemper: I've moved our pairing session a bit later. I need some time to get something to eat
[12:49:14] <gehel>	 @team: I just canceled retro in favor of the staff meeting
[12:49:37] <gehel>	 zpapierski: we never finished that conversation about SOLID :)
[12:52:20] <zpapierski>	 I believe it was about Open/Closed principle, not SOLID per se
[12:52:24] <zpapierski>	 but yeah
[12:56:06] <gehel>	 we can continue that discussion in the open hangout in 5'
[12:56:17] * gehel is movign this offer forward first
[12:56:48] <zpapierski>	 need to eat and relocate - and staff meeting is unfortately afterwords (and then weighted tags retro)
[13:01:48] <zpapierski>	 meal break and relocating
[13:05:24] <gehel>	 open hangout is now open! https://meet.google.com/ugw-nsih-qyw
[13:41:50] <gehel>	 addshore: we're doing some phab cleanup. Is T241314 still relevant? Do you need a fix? Or should we close it as won't fix?
[13:41:51] <stashbot>	 T241314: Why does the WDQS updater seemingly poll sometimes when given a list of --ids to update - https://phabricator.wikimedia.org/T241314
[13:43:53] <addshore>	 closed
[13:44:37] <gehel>	 thanks!
[14:59:06] <ryankemper>	 gehel: ack
[15:21:53] <ebernhardson>	 lol, someone invoked nazi's in a ML post with mike godwin
[15:22:12] <ebernhardson>	 if not familiar: https://en.wikipedia.org/wiki/Godwin%27s_law
[15:32:29] <gehel>	 ebernhardson: weighted tag retro: https://meet.google.com/ssj-hybs-eqc
[15:32:30] <dcausse>	 ebernhardson: meeting?
[15:32:34] <ebernhardson>	 oh, sec
[16:18:17] <dcausse>	 dinner
[17:40:48] * ebernhardson realizes reading through streaming-updater codebase that it's code:comment ratio is 20:1, while my recent projects are more like 4:1.  Perhaps our difference on ideas on documentation is I put all my documentation in the code where i expect to see it
[17:42:30] <ebernhardson>	 heh, cirrus is 3:2 in code:comment
[17:43:34] <ebernhardson>	 (to be fair though a significant amount of cirrus comments are probably boilerplate parameter annotations)
[22:27:45] <ebernhardson>	 randomly wondering, do we alloy https://commons-query.wikimedia.org to start serving web requests whenever the appropriate patches are merged, or do we throw up some non-response until we merge a specific go-live patch
[22:27:49] <ebernhardson>	 s/alloy/allow/