17:00:32 #startmeeting weekly network team thingy! 17:00:32 Meeting started Mon Aug 22 17:00:32 2016 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:44 greetz 17:00:50 athena: dgoulet: asn: isis: isabela: teor: etc: hi! 17:00:57 hey hey 17:01:26 o/ 17:02:16 i can start 17:02:17 here you go: 17:02:20 Hello last week I did plenty of things. Mainly focused on reviewing hidden 17:02:20 service code, but also wrote some code and sent some emails. I reviewed #17238 17:02:20 and I'm now doing some improvements to the branch (eta wednesday). I also 17:02:22 reviewed #17178. I wrote more code for #19043. I wrote a short blog post on 17:02:25 onionbalance that is currently being reviewed by donncha. I also sent some 17:02:28 emails to tor-dev: 17:02:30 https://lists.torproject.org/pipermail/tor-dev/2016-August/011308.html 17:02:33 https://lists.torproject.org/pipermail/tor-dev/2016-August/011311.html 17:04:22 anything you need help with? Any other plans for this week? 17:04:55 i plan to contiue reviewing/improving #17238 so that we can set it to official needs_review asap 17:05:03 also looking forwrd to see progress with the guard project 17:05:23 nothing in particular i need help with right now 17:05:37 thx :) 17:06:03 ok. I'll go next. :) 17:06:56 I've been on vacation with my family. While gone I hacked on a tool to generate a large number of sample paths, but didn't we have one already? I also hacked on an implementation of prop#264, since I really want one of those as a prerequisite for many of the new things we are adding 17:07:23 I merged some reviewed branches when I got back home on Friday, and reviewed a little code. 17:07:58 I hope to put out a new 0287 release in the next couple of days if possible. I was planning on today, but it might make sense to wait for the bridge auth IP change. 17:08:34 how come you hacked on the tool to gen a large number of sample paths? 17:08:41 and what's the tool we already have? 17:08:55 I was thinking about ways to integration- test our path selection algorithms. 17:09:13 I don't know what the tool we already had is; I think maybe karsten worked on it? 17:09:20 e.g. catching bugs like the recent teor one 17:09:23 yeah 17:09:38 yes i was also thinking of how to catch such bugs 17:09:45 i dont know if karsten has a tool that can do that 17:10:04 branch is sample_paths in my public repo 17:10:15 err, 17:10:17 sample_path 17:10:20 I have no idea if it works 17:10:23 :) 17:10:38 ack 17:10:57 This week I'm planning to review, do a release, and I hope to get all/most of 15055 done 17:11:05 #15055 17:11:06 this will require me to spend time not glued to IRC :) 17:11:09 aha 17:11:14 And that's it for me 17:11:16 next update? 17:11:21 (brbb reloc) 17:11:33 i can go next 17:11:52 i put the guard tickets back on 029 17:12:02 can we make it official that mid oct is freeze day? 17:12:29 I am fine with that 17:12:31 (it will be good to have it after dev meeting because folks will be able to do work f2f there and that can help get s**t done for 029) 17:12:38 i'm not 100% sure we can fit all the guard work by mid oct 17:12:52 i am mostly working on new grants and reports of current grants 17:13:07 lots of deadlines 17:13:16 but i agree we should aim for 029 17:14:13 i might ping the list on proposals we are writing for this week but that doc is looking good 17:14:54 nickm: maybe you can help a little bit with the pad - i asked folks to expand a little on those ideas for proposals just add some why and how to help me understand them 17:15:13 timeframe? 17:15:14 hi meeting 17:15:21 isabela: send link again? 17:15:24 athena: hi athena 17:15:29 nickm: will do one sec 17:15:32 * isabela done 17:16:33 got a revised #18640 in for you; next week i'm going to tie off the WIP i have for #19552 and then hopefully get started on that series of guard tickets 17:17:05 ok. Are you thinking you'll want to be doing all those guard tickets yourself (i hope not) or are there some you want and some you don't? 17:17:17 I'd especially like to help with the early API design phasts 17:17:20 *phases 17:17:27 to make sure we get something we both consider clean and easy to work with 17:20:31 i'll go next, i guess 17:20:34 In the last week, I worked with weasel to migrate the sandstorm server to TPO 17:20:35 infrastructure (#19255), and spent most of the remainder of my time on the 17:20:35 bridge authority transition. I reviewed one minor tor ticket (#19875). Other 17:20:35 than that, I didn't really manage to get very much of the work I'm supposed to 17:20:36 be doing on BridgeDB done, due to needing to do some other tasks. 17:20:48 nickm: yeah, i'll loop you in on them when i'm ready to jump in 17:21:15 cool, thanks 17:21:29 oops, sorry athena, didn't realise you were still going 17:21:37 isis: anything the rest of us can do to help out? 17:22:25 more time to transition the server would be nice, if possible? 17:22:32 HI! (woa made it!!) 17:22:49 isis: armadev is the best person to try for that, I'm afraid. 17:22:58 and I put our odds at so-so 17:24:57 dgoulet: o/ 17:25:12 hi dgoulet 17:25:34 hmm. ok, doing everything i can to get the machine up asap. 17:25:46 so simple for me, #17238 was my big thing last week... got great reviews round with asn on this, it's now in his hands to fix some stuff. 17:25:57 I've also reviewed couple of tickets in review-group-7 17:27:01 my goal this week is to fix prop224 spec with some changes that happened during the implementation, review more ticket and if possible help asn with the prop224 cell work 17:27:23 asn: also what's the state of your sign + prefix patch? (can't remember the number :S) 17:27:57 and finally, we've been adding relays to our test net! I'll send an email to network-team today about it 17:27:58 -- 17:30:45 anyone else to check in? 17:30:50 FYI, I am still working on the CopperheadOS + Tor prototype. I think I figured out my major snag. I'm hoping that I'm within striking distance of getting something working well enough for an announcement. after that, I'll turn my attention to #16861, #17592, and #17604 17:31:34 I think #17591 should come out of 029, btw. and #8453 probably should 17:32:04 mikeperry: please let me know if my monotonic time, timer, and handle features are not clear; I think they would all help with #16861 17:32:23 mikeperry: If you think so, please defer them to a later milestone? 17:32:49 the handle stuff seemed fine. I need to look at the monotonic time and timer stuff again 17:33:25 it should let you throw out a lot of kludge 17:34:29 mikeperry: there is a 0.3.0 one 17:34:45 mikeperry: or 0.2.???? which is where i put the ones i removed from 029 17:35:14 isabela: ok, done. 17:35:35 cool 17:36:09 nickm: yeah, I just need to spend the time to think through all the timey-wimey stuff again. I remember not being satisfied with the places and types of monotonic time that were used in the first version of it 17:36:47 I ripped out the old monotonic time code and wrote new stuff; it shares nothing with the old stuff 17:37:17 the netflow code had special checks that prevented padding from being disabled for more than 60s regardless of clock jump direction. the monotnic time would remove that ability.. at least the version I looked at months ago. 17:37:21 ah ok 17:39:43 so, any discussion topics for today? else let's call the meeting, and all poke isabela's pad. 17:41:24 i dont have anything, just wanted that final check of moving the freeze date to mid oct 17:41:29 will email the list about it too 17:41:39 ah but! 17:41:54 we all should think of topics for dev meeting :) and add them to the agenda wiki 17:41:59 and think of what to hack during hacking days 17:42:17 ok 17:42:20 asn: are the thoughtworks ppl who helped with guard stuff going to be at the dev meeting? 17:46:40 nickm: you can stop the bot btw :) 17:47:40 ok 17:47:41 #endmeeting