13:29:45 <nickm> #startmeeting
13:29:45 <MeetBot> Meeting started Wed Apr 22 13:29:45 2015 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:29:45 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:30:47 <nickm> hi all!
13:30:50 <nickm> looks like it's meeting time!
13:30:53 <Yawning> hi
13:30:58 <nickm> I see helix and isabela and dgoulet and Yawning
13:31:06 <teor> and /me
13:31:13 <nickm> and teor !
13:31:20 <dgoulet> o/
13:31:27 <athena> hi meeting
13:31:34 <Yawning> (http://copyright.gov/comp3/docs/compendium.pdf)
13:31:40 <teor> and athena!
13:31:55 <nickm> Hi, everybody!
13:32:06 <nickm> Let's start with statuses
13:32:41 <nickm> I've been mainly swamped on ED-transition tasks, but I managed to get a sponsorS thing written for isabela.  I hear I need to write more in order to help prep a report.
13:32:59 <nickm> I also wrote an implementation of that PCSA algorithm I've been going on about
13:34:19 <nickm> and hm. Main priorities for this coming week are mainly keep people from freaking out, get enough sleep, help with everything I'm needed on, and learn more about bank accounts really work than I ever knew before
13:34:26 <nickm> oh, and merge patches
13:34:37 <nickm> that's always important.
13:34:41 <nickm> Who's next?
13:34:46 <Yawning> I can go
13:34:53 <Yawning> Fixed up #6411, needs review again
13:35:09 <Yawning> fixed up #15652 needs review again
13:35:21 <Yawning> probably can just take #15759
13:35:41 <Yawning> apart from that got stuck doing pt reporting and sent isabella a gigantic wall of text
13:35:46 <Yawning> need to write more apparently
13:36:00 <Yawning> so more pt stuff in the future in addition to core tor
13:36:19 <Yawning> also I'm mentoring one of the two TSPO students that will require core-tor changes I think
13:36:22 <Yawning> so yay
13:36:25 <PI_> Question?
13:36:33 <nickm> isabela: should we schedule a few minutes to talk about this stuff before the phone call, after the meeting, or do it during the discussion period here?
13:36:36 <nickm> PI_: go for it
13:36:51 <athena> i did #14840 and have #15358 and that long code review pending, and hopefully apartment-hunting won't explode out from under me again
13:36:54 <PI_> I have a raspberri Pi
13:37:04 <PI_> I cannot get tor up on it
13:37:10 <Yawning> #tor
13:37:13 <PI_> More tbb
13:37:23 <Yawning> ah ha there
13:37:24 <nickm> PI_: head over to #tor for that; this channel is about making the software. :)
13:37:45 <PI_> Not the software to load it then?
13:38:00 <PI_> Ok off to #tor
13:38:09 <nickm> athena: did you find having stuff to hack on make the code review less overwhelming?
13:38:16 <Yawning> In the US skruffy's patches are public domain
13:38:33 <isabela> nickm: leave as the last discussion topic
13:38:45 <nickm> ok
13:38:49 <Yawning> (306 The Human Authorship Requirement)
13:39:22 <GeKo> thanks
13:39:42 <Yawning> nb: INAL
13:39:45 * dgoulet can go
13:39:51 <nickm> athena: go for it
13:40:10 <nickm> err, dgoulet
13:40:13 <dgoulet> :)
13:40:16 <dgoulet> Work on last week SponsorR, fixup #14847, did code also on #15745. I'm
13:40:17 <dgoulet> continuing on R for this week that doesn't involve little-t tor code.
13:40:21 <athena> nickm: yeah, it flows along smoothera bit now
13:40:43 <dgoulet> basically it as for little-t tor is concern
13:40:50 <nickm> athena: cool. in that case maybe remember to pick a couple more tickets.  Ideally high-priority ones for 0.2.7 :)
13:41:33 <athena> ok
13:41:58 <Yawning> (oh, my next thing to do for core tor is prolly the curve25519 stuff and the high priority pt stuff)
13:42:22 <Yawning> (unless my patches need further revision.  I might rage implment a better guess the IP address routine for the BSDs)
13:42:55 <Yawning> isabela: was my wall of text comprehensible?
13:44:04 <isabela> Yawning: yes - I havent gone over the evaluations docs yet tho
13:44:19 <isabela> Yawning: and thank you so much for it!
13:44:28 <nickm> dgoulet: anything the rest of us can be doing on R?
13:44:34 <Yawning> isabela: np
13:44:44 <Yawning> Jcam wanted an FTE eval so I'll do that when I have a moment
13:44:56 <isabela> ok
13:45:25 <isabela> i saw the emails
13:46:50 <Yawning> (I probably have random other patches outstanding and in needs_review that I'm forgetting about, and I know I have a bunch of spec stuff in needs_revision that I need to finish)
13:47:17 <dgoulet> nickm: for now we seem all set, SMC is in research mode, we have bunch of tickets to work on, so your help would be simply to review little-t tor patches I guess (which is underway :)
13:47:33 <nickm> please don't forget to keep bugging me about those
13:47:54 <dgoulet> ok I shall :)
13:48:05 <nickm> I am reaching the limits of my time management skills and I am worried that I might just give my time to whatever is loudest, not to whatever is most important.
13:48:11 <Yawning> dgoulet: torrrrrrr sockssssssss
13:48:16 <isabela> hehe
13:48:34 <dgoulet> Yawning: so good news, I've planned this afternoon for that! I know it's needed and more than needed :)
13:48:40 <Yawning> 9\o/
13:48:46 <Yawning> let me know if you have questions
13:48:55 <dgoulet> nickm: yes I understand your time constraint thus trying to offload you as much as I can so for now, everything is well in R world :)
13:49:00 <Yawning> feel free to carve up my patches, I don't care, they're public domain >.>
13:49:31 * isabela has an update :)
13:50:00 <dgoulet> nickm: (technically speaking)
13:50:05 <dgoulet> isabela: I guess go for it ? :)
13:50:38 <isabela> I migrated the spreadsheet to Trac so that info is no on our tickets. I still want to organize it more.
13:50:49 <Yawning> yay
13:50:52 <dgoulet> o/
13:51:16 <isabela> I've been working on a new version of 'how tor uses trac' doc where I want to add custom fields to our tickets for instance one just for us to put sponsor info
13:51:26 <isabela> so we dont have 20 thousand keywords going on
13:51:35 <dgoulet> isabela: fantastic idea
13:52:06 <isabela> I am writing this to share with you all and also qbi (sysadmin of trac / I found out :D) so ppl are cool with it before  implementation
13:52:25 <dgoulet> isabela: would that include the results of your survey?
13:52:32 <isabela> I will change things a little bit but should be for good of all hehe
13:52:33 <dgoulet> isabela: (small/medium/large)
13:52:55 <Yawning> isabela: I replied to your survey on IRC using amount of alcohol to characterize how I felt about small/medium/large, was that sufficient?
13:53:06 <isabela> dgoulet: yes! I will use that info from you to propose a definition of small/medium/large and them reflect that on the tickets / and hopefully others can adopt that as well
13:53:18 <isabela> Yawning: fantastic!
13:53:25 <Yawning> >.>
13:53:30 <isabela> I think that's it
13:53:31 <isabela> <done>
13:53:41 <dgoulet> awesome
13:53:45 <nickm> My own sense here is that nobody is in love with our current keyword plan
13:53:48 <nickm> err,
13:53:51 <nickm> current keyword usage
13:54:15 <isabela> cool
13:54:16 <nickm> Having per-release milestones has worked out better than trying to have per-sponser-month *AND* per-release deliverables used to do
13:54:24 <nickm> but there might well be an even better way
13:54:36 <nickm> I don't think you'll get much arguments from us about any sane system :)
13:54:44 <isabela> hehehe
13:56:11 <nickm> anybody else with a status thing or should we move on to discussions?
13:56:15 <Yawning> so we should map our sponsors, deliverables and milestones onto zodiac symbols, and the Tree of Life from the Kabbalah, and just tag the symbols right?
13:56:35 <nickm> This is turning into a console RPG
13:56:46 <dgoulet> Yawning: clearly we should add a random component :)
13:56:50 <isabela> ahahahaha
13:56:54 <isabela> I want that :)
13:57:04 <Yawning> (tagging our sponsors after Pokemon also acceptable)
13:57:15 <isabela> yes sir!
13:57:30 <Yawning> anyway, do we have discussion?
13:57:49 <nickm> There's the report(s) that isabela is up to; that was for last.
13:58:09 <Yawning> oh well, mine was like a gigantic amount of PT stuff
13:58:16 <Yawning> so not really tor core
13:58:24 <nickm> I wanted to talk RSN about dividing tasks for 0.2.7 and trying to get 0.2.7 done on schedule... and not miss any deliverables
13:58:39 <Yawning> mmk
13:58:40 <nickm> Anyone else have a discussion topic?
13:58:49 <Yawning> pls review my codez?
13:58:56 <nickm> ack
13:59:03 <nickm> I will try to review some codez on the bus today
13:59:15 <armadevich> btw, i am here, but mostly planning to spend my morning catching up on things and preparing for the sponsorO/S phone call later today.
13:59:28 <Yawning> I *think* I got the control port stuff into something mergable
13:59:41 <Yawning> the base64 and unit test changes are also trivial
13:59:54 <Yawning> well, apart from "the base64 change has a new encoder"
14:01:06 <nickm> yeah...  I am trying to go through all the needs_review stuff in 0.2.7 periodically
14:01:10 <Yawning> nickm: before I spend cycles on it, you haven't looked at the curve25519 stuff right?
14:01:16 <nickm> not for a long time
14:01:19 <Yawning> ok
14:01:20 <teor> There was discussion on tor-dev about fallback directories, but I think there is a serious bug in the code
14:01:33 <nickm> I did write code for some of it long ago but I'm not sure that I believe it is any good
14:01:40 <nickm> Yawning: might be worth salvaging.
14:01:50 <Yawning> (also, do you think it will be worth looking into specing ntor with goldilocks?)
14:01:55 <nickm> teor: Is there a ticket for the bug?
14:02:09 <Yawning> (the library is supposedly going to be ready real soon now)
14:02:15 <nickm> Yawning: I'm not really sure.  Not for 0.2.7 I hope.
14:02:22 <Yawning> oh good heavens no
14:02:23 <teor> Yes, #15642 has the bug and also a summary of my additional questions
14:02:32 <Yawning> was looking at it for obfs5 related stuff
14:02:47 <teor> In short, we still use the fallback directories even in test networks. Which is bad.
14:03:00 <Yawning> since there's elligator code for it
14:03:26 <teor> nickm: and also, people want a signed file of fallback directories, which is unsupported by the current code
14:03:43 <nickm> I am not sure why a signed file makes sense, personally.
14:03:58 <nickm> But fixing the test network issue seems important
14:03:58 <Yawning> oh, armadevich if you're here, did anything come out of that HS IP related thing?
14:04:11 <Yawning> the one that affects loadbalancing and other cleverness
14:04:12 <teor> It seems like a lot of effort for not much gain
14:04:39 <teor> I mean, we don't even sign the hard-coded list of authorities
14:06:03 <nickm> yup.  I think the request for making it signed doesn't actually have a solid threat model.
14:06:42 <teor> The threat model was: "well-meaning maintainer adds own directory"
14:07:02 <Yawning> "don't do that"
14:07:07 <nickm> well-meaning maintainer can also remove the signature check
14:07:26 <teor> Yes. Or substitute their own authorities, for that matter.
14:08:52 <nickm> teor: for #15642 , I'm trying to understand the current status.  There's a patch but because of lack of test coverage you don't trust it?
14:09:23 <teor> Ah, sorry, I confused the two issues.
14:10:03 <teor> There is a patch, and I am fine with it. I know that code well from #13163
14:10:32 <teor> What I disliked were the complications of importing a signed file. That code doesn't exist and hasn't been tested.
14:10:37 <Yawning> that bug seems familiar
14:10:38 <nickm> yeah.  Let's not do that.
14:10:53 <teor> I also included unit tests for the changes I made.
14:11:13 <nickm> so maybe put that ticket back in needs_Review?
14:11:26 <teor> Yes, I will can the speculation.
14:11:29 <nickm> woot
14:11:34 <nickm> or move it to a new ticket :)
14:11:41 <nickm> ok, next topic... dividing up 0.2.7 stuff
14:11:54 <nickm> we can continue to go for a "do whatever is most important-looking" approach
14:12:00 <nickm> but that isn't really a plan
14:12:01 <Yawning> "pick stuff that we want, ideally in priority?"
14:12:03 <teor> Do you want #15642 in 0.2.7?
14:12:04 <nickm> isabela: any ideas?
14:12:11 <nickm> teor: sure I think
14:12:27 <Yawning> I should ask this
14:12:34 <Yawning> before I minor/lorax #15760
14:12:42 <Yawning> do people think it's important?
14:12:54 <Yawning> (there have been 0 1.1.0 releases)
14:13:12 <Yawning> and it's the cipher list code breaking into tons of little peices
14:13:13 <isabela> nickm: for today I would say to go with that / due to ED transition stuff and EOQ reports I could not make a custom query for us to use at this meeting
14:13:24 <nickm> isabela: ok
14:13:25 <isabela> nickm: will work on that for next week hopefully
14:13:30 <nickm> great
14:13:51 <nickm> how hard is the fix for #15760 ?  How close is this version of openssl to release?
14:14:09 <Yawning> I'd need to look at what's changed, probably not, just timeconsuming and annoying
14:14:14 <Yawning> and not at all
14:14:36 <Yawning> I can poke at it if it's important, or we can leave it till it matters and spend an afternoon on it
14:14:37 <nickm> My guess is that there's some structure whose contents they no longer export
14:14:40 <Yawning> (small, few beers)
14:14:47 <nickm> I say minor but not lorax
14:14:50 <Yawning> ok
14:16:06 <Yawning> done
14:16:19 <nickm> next topic ...  Are we up to the EOQ report topic?
14:16:28 <nickm> shall we do this after the meeting so people not interested can do other stuff?
14:16:34 <nickm> Yawning: thanks
14:16:48 <Yawning> (does this include my pt stuff, or can I go kitty/videogame?)
14:16:52 <dgoulet> which sponsor is this EOQ report?
14:17:22 <isabela> S
14:17:31 <isabela> and yes EOQ report
14:17:44 <nickm> #endmeeting