13:29:43 #startmeeting 13:29:43 Meeting started Wed Oct 7 13:29:43 2015 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:29:43 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:30:05 Hello all! I see Yawning and asn and Sebastian ! and I saw dgoulet a little while ago! 13:30:12 hello! 13:30:22 hi 13:30:23 time to try to get back into the rhythm of tor development! 13:30:33 who's got a status report first? 13:30:44 suuure 13:30:57 went to the dev meeting, got back, still jetlagged (woke up at 4pm yay) 13:31:23 goals for the next week are uh, write pt docs, catch up on administrative paperwork, start writing code again 13:31:28 (and fixing my sleep schedule) 13:31:33 hello. just doing some shared randomness coding currently. 13:31:34 next >.> 13:31:49 * dgoulet can go 13:32:02 Yawning: is there anything that others can do to help out with the pt docs? I know you're not thrilled to be doing them. Is the answer to stick them on an etherpad maybe and have everybody poke them at once? 13:32:06 dgoulet: go for it 13:32:27 I have to go run to a bus, sorry I'm not really here for the start of the meeting. 13:32:31 there is one more doc to write that I need to do 13:32:32 since I got back, I did some housekeeping on all R tickets and tor-hs tickets, now it's much more clean and in a workable state. I opened bunch of 224 tickets (see #12424 child tickets) 13:32:32 have a good meeting 13:32:41 I hope to catch up in a bit 13:32:46 so light at the end of the tunnel 13:33:07 and I've worked on dirauth configuration management process also yesterday and would *love* feedback on my last comment of #16558 13:33:35 finally, dev meeting was amazingly useful! did lots of work with asn on SR among other things, so going forward big time! :) done 13:34:26 peace Sebastian 13:35:51 dgoulet: I think I agree with your comment. I wonder if something related to prop#177 might help a little with that. 13:36:08 but it doesn't seem like a must-do-in-028 in any case to me, unless I am missing something important 13:36:33 nickm: we are having a *HARD* time now getting majority of dirauth rejecting malicious HSDirs we are finding 13:37:03 nickm: thus the interest in getting less dirauth voting invalid... but.... yeah... 13:37:26 fix human problem by technology, what can go wrong :D 13:38:16 I think the idea of prop#177 was to get it more okay for a dirauth to help reject malicious nodes without forcing them to commit henceforth to rejecting *all* malicious nodes. 13:38:28 IIUC 13:38:30 it's been ages 13:38:35 nickm: thanks for the pointer, I'll read that! 13:38:44 and see if it can be useful in anyways with the current statre 13:38:57 (isn't that what Tor is? Just teach the spooks not to spy instead of doing all this development...) 13:39:16 Yawning: ahahah! it's a big part , needed though if you want users :) 13:39:50 anybody else? asn? 13:41:39 ok I'll go for now 13:41:52 I've got back from the dev meeting and accumulated huge amounts of sleep 13:41:59 top priorities for this month are: 13:42:06 * PETS reviews due in 2 days 13:42:17 * Getting out another 0.2.7 rc if needed; fixing all 0.2.7 bugs. 13:42:28 * Finishing every single sponsor U item (help would be nice) 13:42:39 * Getting 0.2.8 triage finished 13:42:53 And if I can really get those all done, I can think about other priorities but cmon seriously 13:43:00 oh also 13:43:16 * Reviewing every needs_review ticket in 0.2.8. 13:43:23 (help would be nice there too) 13:43:27 and that's about it for me 13:43:34 anyone else here for the meeting? 13:43:39 shall we move on to discussion? 13:43:51 we can 13:43:58 is there stuff to talk about that wasn't covered at the dev meeting? 13:44:31 probably a lot; we never really did the 028 triage together or did much together discussion of the roadmap 13:44:38 anything else in mind? 13:44:39 curious about the what's left to do for "Getting 0.2.8 triage finished", like go over all Tor tickets and make sure they have a milestone if none? 13:44:49 ah 13:45:22 dgoulet: having everything get a milestone would be good. 13:45:38 having all deliverables on the roadmap get a ticket would be good 13:46:07 and finally, we need to prioritize. There are more things in 0.2.8, and more in 028-triaged, than we can realistically do before freeze, if the past is a guide 13:48:55 I see 7 tickets without a milestone for component Tor 13:49:02 that's an improvement from last week 13:50:17 ah one of them is "we block the google cloud" !! ahah... I was working on that yesterday of coming up with processes of removing entries in the conf 13:50:22 #14044 13:51:18 just forwarded everybody my notes from the roadmap meeting 13:51:29 if anybody woudl like to take responsibility for getting that onto the wiki that would be great 13:51:37 also great would be making sure there is a ticket for every item 13:51:50 any volunteers? :) 13:52:16 nickm: I can probably help you out a bit there but probably not the entirety :S ... (opening the .ods....) 13:53:08 if it would help to throw it onto storm, please do so. :) 13:53:38 nickm: I'll put them on the wiki for starter 13:53:55 that would rock. eta on that? 13:54:04 5-10 min? 13:54:07 yaaay 13:54:15 formatting issue here :P 13:54:26 other discussion topics? I'm hoping I can get volunteers to help with some of the end-of-month sponsor U stuff 13:54:33 or I will be too busy to help anybody else with anything 13:56:02 hrm I'm good on discussion 13:57:00 could everybody take a look at the "october" part of that spreadsheet I just sent you? 13:57:14 I'm hoping somebody will say "hey that looks fun/easy/whatever" for one or more of the items 13:57:21 or alternatively, "nick how can we possibly do that" 13:57:48 How can we possibly do that!? ;) 13:58:33 I was hoping for a more specific "that" :) 13:58:36 "Implement an improved guard design prototype", just this, seems that Berlin session on that didn't reach a clear decision :S 13:58:55 are the notes for it in a good online format, or do they need fixup? 13:58:57 DoS whitepaper... ouff... 13:59:14 My thought for a prototype is basically "do something fast in python so we can simulate different problematic situations and confirm it works" 13:59:19 nickm: oh my, maybe mikeperry has some or asn some pictures of the notes but quite unsure 13:59:46 (wait, after I'm done with pt docs, am I going to be writing DoS docs? >.>) 14:00:06 Yawning: you told me SOOOO many times that you enjoy writing doc 14:00:10 :P :P 14:00:42 nickm: do you have a doc or git or of "Overview of structure of tor codebase" and "Quick-start guide for new developers" 14:02:04 Yawning: you can if you want to. my plan was to make a whitepaper into an outline, write the paper, call it done 14:02:19 dgoulet: see tor-guts for that overview (work in progress) 14:02:22 ah I see 14:02:45 nickm: ack 14:02:46 Yawning: if you want to help, I'd appreciate any degree of collaboration from anybody on any of this, even if it's just rubber-duck level :) 14:02:54 quack 14:03:01 :) 14:04:29 back shortly, I'm at ~1k Cal of food for the day, which is insufficient >.> 14:06:10 sounds good 14:06:21 shall we close the meeting and go on with triage and planning? 14:06:25 or is there more to do at the meeting? 14:06:31 * nickm waits 60 sec and sips tea 14:06:34 good here 14:07:37 #endmeeting