17:00:23 #startmeeting 17:00:23 Meeting started Mon Aug 7 17:00:23 2017 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:50 https://pad.riseup.net/p/CSo6JXbG9H0W -- the pad for today 17:00:53 how's everybody doing? 17:01:31 hellooo 17:01:40 pretty good :) 17:02:01 a lot of folks are away this week 17:02:24 Dreary day outside, but I'm here like usual :) 17:03:14 I am not so good. my back got way worse yesterday. I can't really sit or get out of bed. I will be dropping off this meeting soon 17:03:21 argh 17:03:26 sorry to hear that, mikeperry 17:03:26 :( 17:03:34 take it easy 17:04:41 looks like folks are still updating 17:04:49 isis around this week? 17:05:46 mikeperry: take it easy mike 17:08:06 catalyst: did you see https://pad.riseup.net/p/tor-client-progress btw? 17:10:13 komlo: have you had any more thoughts on getting rust experience for more folks? 17:10:21 nickm: looking 17:10:37 ahf, dgoulet: I'm guessing you're busy with conference stuff right now. Enjoy! 17:11:15 nickm: yes, i am planning on having a small rust kata for the montreal rust hackday 17:11:20 nickm: yeah i've seen that before but hadn't pondered it long enough to come up with a plan of action (because diagnosing failures to the extent that would best help Tor Launcher is hard) 17:11:23 pastly, dgoulet: do you think I should be skimming the kist stuff too, or should I wait till this round of review's done? 17:11:45 catalyst: yeah. It's easy to see what's working, but hard to see why something's failed, especially when proxies are involved 17:13:13 also isis, komlo: do you think I should be skimming the protover stuff too, or should I wait till this round of review's done? 17:13:26 The more eyes the better of course. I wouldn't look too hard though ;) Leave some work for dgoulet 17:13:40 nickm: isis is going to do an initial review of my protover implementation in rust this week 17:13:45 pastly: ok. I'll skim for general structure 17:14:13 I'll make sure you are aware that I've made it needs_review 17:14:13 komlo: Understood. Should I skim too, or wait till this is done? Please let me know which you'd prefer. 17:14:13 nickm: after isis's review, it would be great to have you take a look 17:14:18 ok; will wait 17:14:52 isis: i did followup investigation on how `make check` output gets consolidated and it seems ok (see my update) 17:15:29 nickm: for montreal, we can come up with a schedule for the rust hackday, and get feedback on whether this is enough to get more people going on rust 17:16:01 cool 17:17:06 Does everybody feel like they have enough stuff to make good progress & stay appropriately busy coding and reviewing and etc over the next 2 weeks? I'm out next week... 17:17:15 ...so feel free to ping me any time so we can plan ahead 17:17:29 I'll have email, and read personal email, though I'll mostly ignore lists. 17:18:32 im def filled up with prop224 stuff 17:18:45 so ill be good :) 17:18:48 catalyst: would you like to plan a time some time this week to try to turn the tor-client-progress wishlist into something implementable? 17:19:02 asn: after today's branch, do you think there will be more for me to look at this week? 17:19:27 i will have more #20657 updates for you, based on your latest feedback 17:19:39 updates will arrive tomorrow 17:19:40 cool; I meant after that? 17:19:42 no 17:19:44 ok 17:19:50 i dont expect there will be another branch after #20657 for this week 17:20:01 but we hope to have something for you for after you get back 17:20:03 I might be able to spend a few hours reviewing next week if I get bored, so don't be afraid to show me code... 17:20:05 (the client-side) 17:20:08 ack 17:20:09 the worst I can say is "later" 17:20:13 (that goes for everybody) 17:20:53 so, only a few discussion topics left that I'm aware of 17:21:17 main one is: should I try to put out an -rc towards the end of this week, or wait longer to see if more bugs will be found in 0.3.1.5-alpha ? 17:22:11 it looks like the next firefox isn't till end-of-september, so we'll not be rushing to meet a TB deadline... 17:22:16 afaik... 17:22:30 but we would still like to release in early september if we can, and the code _is_ seeming pretty stable. 17:23:08 perhaps we can do an rc in mid-aug when you come back, and a release in early sept as well? 17:23:16 ok 17:23:35 then let's all remember to look at and fix 0.3.1.x bugs over the next 2 weeks :) 17:24:46 any other topics, or shall we call our meeting finished? 17:25:07 nickm: we can chat about tor-client-progress Wednesday or Thursday possibly 17:25:21 catalyst: let's aim for thursday? it'll give us more time to think. When's good for you? 17:25:34 I can do any time except 1130 to 1300 eastern. 17:26:42 nickm: let's try 14:00 eastern? 17:26:48 works for me 17:27:04 are central or mountain time? 17:27:17 i'm in central time 17:27:27 ok, so not too far off. groovy 17:27:49 1400 eastern on Thurs. Let's see what we can figure out between now and then 17:27:51 oh right i should revise my "what hours are good meeting hours" now 17:28:06 anything else for today? 17:28:11 * nickm waits 60 sec to hear... 17:29:16 okay. thanks, everybody! 17:29:20 thanks :) 17:29:23 thanks! :) 17:29:34 I'll be seeing everybody online; feel free to say hi any time 17:29:40 #endmeeting