13:27:52 <nickm> #startmeeting
13:27:52 <MeetBot> Meeting started Wed Mar 18 13:27:52 2015 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:27:52 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:28:02 <nickm> hello beautiful people, it's time for the weekly tor dev meeting
13:28:03 <Sebastian> nickm: weasel: armadev: Should it be time to un-recommend some old versions?
13:28:11 <Sebastian> oh, sorry.
13:28:14 <nickm> Sebastian: good question.  What's recommended now?
13:28:32 <Sebastian> RecommendedClientVersions 0.2.3.24-rc,0.2.3.25,0.2.4.17-rc,0.2.5.1-alpha,0.2.4.18-rc,0.2.4.19,0.2.4.20,0.2.5.2-alpha,0.2.4.21,0.2.5.3-alpha,0.2.5.4-alpha,0.2.4.22,0.2.5.5-alpha,0.2.4.23,0.2.5.6-alpha,0.2.5.7-rc,0.2.5.8-rc,0.2.4.24,0.2.4.25,0.2.5.9-rc,0.2.5.10,0.2.6.1-alpha,0.2.6.2-alpha,0.2.6.3-alpha,0.2.4.26,0.2.5.11,0.2.6.4-rc,0.2.6.5-rc
13:28:45 <Sebastian> RecommendedServerVersions 0.2.4.23,0.2.5.6-alpha,0.2.5.7-rc,0.2.5.8-rc,0.2.4.24,0.2.4.25,0.2.5.9-rc,0.2.5.10,0.2.6.1-alpha,0.2.6.2-alpha,0.2.6.3-alpha,0.2.4.26,0.2.5.11,0.2.6.4-rc,0.2.6.5-rc
13:28:49 <Sebastian> that
13:28:55 <nickm> hm. let's return to that during discussion time
13:29:06 <Sebastian> yup sorry i didn't meant[D to interrupt
13:29:11 <nickm> So, who's here for the meeting today? I am , and I've seen dgoulet and Yawning and Sebastian.
13:29:15 <Yawning> <-
13:29:18 <nickm> I know saint is online :)
13:29:18 <asn> my reality is here
13:29:21 <dgoulet> o/
13:29:21 <nickm> hi asn
13:29:25 <nickm> athena: are you about?
13:30:38 * isabela !
13:30:53 <nickm> let's start with quick status updates!
13:30:57 <asn> (i renamed Count unique IPs in an anonymous way
13:30:58 <skruffy> lets to discuss how to guarantee akick all my hosts
13:31:01 <asn> (oops)
13:31:24 <nickm> skruffy: everybody's welcome to particpate, but you've got to participate in a constructive way if you want to be welcome.
13:31:33 <nickm> my update:
13:31:56 <nickm> I got 0.2.4 and 0.2.5 releases out, started on an 0.2.6 one, wrote a bunch of design text for SponsorS.
13:32:08 <nickm> and started on 0.2.7 pre-triage stuff
13:32:28 <asn> good stuff!
13:33:02 <skruffy> thats why need to banme, akick especially, your community designed for such stuff
13:33:04 <Sebastian> (who goes next?)
13:33:15 <Sebastian> (or are you not done, nickm)
13:33:36 <nickm> (next I need to help triage 0.2.7 and review whatever I'm supposed to review and get all the apr-1 sponsorS stuff into a good place.)
13:33:40 <nickm> now I'm done, who'll go next?
13:33:44 <Yawning> I can go
13:34:26 <Yawning> I squashed/rebased #6411, fixed a bunch of bugs (that ExtORPort thing), and did an evaluation of LIONESS that I still need to write up and send to tor-dev@
13:34:57 <Yawning> For tor related stuff I'm supposed to review one of the large patches, help triage 0.2.7.x, and do whatever else is needed
13:35:01 <Yawning> (beyond all the pt stuff)
13:35:08 <Yawning> that's it for me
13:35:14 <skruffy> banme
13:35:15 <asn> i can go next
13:35:21 <skruffy> I want to die.
13:35:41 <nickm> asn: go for it
13:35:58 <asn> i worked a bit on #8243, and I kind of decided that it's a good idea to onlyu give the HSDir flag to Stable relays. some rationale is incldued in the ticket.
13:36:05 <asn> next step here is to write a small proposal. will try to get to it soonish.
13:36:23 <asn> i discussed a bit encrypted-services at #15271
13:36:34 <asn> one of the new insights is that it might be a good idea to have such services use more than one guard
13:36:54 <asn> so that the load is splitted to all guards. since apparently guards get quite overwhelmed by popular HSes.
13:37:20 <asn> and I also discussed hidden service scaling with DonnchaC in tor-dev. good discussions there, and DonnchaC might go ahead and implement his idea which is great.
13:37:55 <asn> and that's that i guess for little-t-tor stuff
13:37:59 <asn> who wants to go next?
13:38:03 <Sebastian> I'll go :)
13:38:20 <Sebastian> I have a spec + patch in needs-review for descriptor code generation
13:38:30 <Sebastian> erm, scratch the code
13:38:41 <Sebastian> for descriptor generation from control port
13:38:42 <saint> I am in fact here for the meeting :D
13:38:48 <nickm> Sebastian: ticket num?
13:38:52 <saint> (accounting for latency)
13:39:25 <Sebastian> I did a thing where you can disable assertions for coverage builds, which I have to test on linux and then upload
13:39:49 <Sebastian> I helped review a couple of things, worked on a stem a little wrt testing
13:40:36 <Sebastian> next I'd like to have a spec/description for the hidden service control port feature from nickm that we chatted about in valencia
13:41:05 <asn> what's this one again? too many hs control port things going on hard to keep track.9~
13:41:55 <Sebastian> nickm: hunting
13:42:17 <Sebastian> nickm: 14784
13:42:20 <Sebastian> #14784 even
13:43:16 <nickm> ack
13:43:20 <nickm> thanks
13:43:47 <dgoulet> I would also like to have an answer to asn's question :)
13:44:37 <nickm> Sebastian: Do you mean the one about doing the whole hidden service handshake step-by-step ?
13:44:41 <Sebastian> yes
13:44:57 <Sebastian> I have a hard time putting it into words
13:45:03 <Sebastian> so I'm not sure if I understood you correctly
13:45:14 <Sebastian> so if you have a few sentences written down that would help me immensely
13:45:38 <Sebastian> but I also have enough other stuff on my plate so I'm not blocking on you at all
13:45:46 <nickm> I'm actually, for sponsor S, writing up a huge list of control spec improvements that might help testing.  I'd like to get people looking at it this week if I can
13:45:53 <nickm> Shall I send to tor-dev@ when I'm finished, I guess?
13:46:08 <Sebastian> that'd be good
13:46:50 <Sebastian> ok any more questions? Otherwise I think I'm done, thanks
13:46:51 <nickm> ok
13:46:53 <nickm> anyone else?
13:47:08 <dgoulet> can go
13:47:24 <nickm> ok
13:48:43 <dgoulet> finished last week #14847 which is big and refactor part the rend client fetch descriptor code, some review here and there, next on my list is #6411 and new identity keys
13:50:11 <dgoulet> nickm: I would like to know also (after status update) how will be structured the SponsorU documentation part. I have some HS better doc. that would fit in that
13:50:43 <nickm> sounds good
13:50:44 <dgoulet> and will start 0.2.7 triage process today before the meeting tomorrow. DONE
13:50:49 <nickm> I don't think we have a solid plan for that
13:51:33 <nickm> anybody else?
13:52:02 <nickm> (if not, topics for discussion?)
13:52:28 <nickm> here's one: I have these end-of-mar deliverables:
13:52:30 <asn> topic for potential non-discussion: with the HS crowdfunding thing ocming up, it would be a good idea to split the 224 stuff to trac tickets.
13:52:49 <asn> or split the 224 stuff to individual tasks, that could later be transcribed to trac tickets.
13:53:09 <Yawning> oh, I still need to pick my ticket from the review circle
13:53:11 <asn> i can do that (for the tasks that are not already tickets), but not super soon.
13:53:22 <nickm> design writeup for chutney2;  design writeup for tor module decoupling; identify high-priority testing areas; pre-alpha chutney2.
13:53:31 <Yawning> I'll take dgoulet's followed by ed25519 id keys
13:53:35 <asn> very interesting tasks nickm
13:53:35 <nickm> the pre-alpha chutney2 may be the current chutney1.
13:53:41 <Sebastian> asn: 224 has a ton of "fill this in"-tasks
13:53:43 <nickm> anybody interested in helping with any of those?
13:53:50 <Sebastian> are these suited for crowdfunding at all?
13:53:52 <Yawning> (I shall also e-mail the circle)
13:53:56 <nickm> Yawning: what's that leave for me?
13:54:01 <nickm> Sebastian: could be
13:54:13 <Yawning> consensus diffs
13:54:28 <Yawning> athena gets primary on ed25519
13:54:29 <asn> (Sebastian: even identifying those parts would be helpful. i know some of these incomplete parts, but there are more missing.)
13:54:30 <nickm> Yawning: whoa seriously? ok.
13:54:35 <nickm> Yawning: ok, who's secondary on that one?
13:54:40 <Yawning> what, should that have been something else?
13:54:54 <Yawning> andrea since dgoulet and I both are looking at the ed stuff?
13:55:01 <Yawning> (should one of us switch?)
13:55:19 <nickm> no, all's well.
13:55:41 <nickm> I was just expecting somebody to pick for me to review their controller code. :)
13:56:06 <Yawning> eh, dgoulet and I both have been poking at the subsystem
13:56:11 <Yawning> and our patches are in related-ish areas
13:56:17 <Yawning> we might as well swap
13:56:52 * isabela has an update :)
13:57:01 <asn> i can also take one of those tickets for review. but for next week.
13:57:21 <dgoulet> isabela: go ahead
13:58:05 <isabela> I am working on mid/month check in for the roadmaps will send out EOW but HS and Core Tor (which I am more familiar with) are looking great! most things will get done looks like it
13:58:26 <isabela> !
13:58:28 <isabela> thats it
13:58:33 <nickm> cool
13:58:39 <nickm> anythingg else to chate about pre-triage?
13:58:59 <Yawning> if people haven't heard, LIONESS is sloooow ;_;
13:59:10 <Yawning> (more details to be in my writeup)
13:59:13 <asn> should we know approximate daates for 0.2.7 release cycle, or do we just triage by putting the things we like in and then figure out the times?
13:59:51 <nickm> Yawning: or in the alternative, other crypto is FAAAAST.
13:59:55 <asn> differently phrased, how do we avoid overcomitting stuff to 0.2.7? or it's too early to care about this yet9~.
14:00:07 <nickm> asn: My current plan was freeze-in-august, release-in-september.
14:00:14 <asn> useful.
14:00:20 <asn> as approximate times at least.
14:00:41 <nickm> possibly with a "slushy" phase.
14:01:01 <asn> ok
14:01:05 <asn> i'm ready for the triage
14:01:24 <dgoulet> hrm triage is scheduled for tomorrow
14:01:33 <nickm> ok. isabela, shall we begin?  (And does this end the meeting?)
14:01:42 <asn> dgoulet: also the second hour of today, *i think*.
14:01:47 <dgoulet> oh
14:02:03 <isabela> nickm: yes
14:02:12 <asn> dgoulet: or maybe i'm confused myself.
14:02:23 <Sebastian> is it now time for the recommended version question?
14:02:40 <nickm> ah, that one.
14:02:41 <Yawning> (let me know when we can have spam back in here and I'll unset "-i" >.>)
14:03:48 <nickm> Sebastian: actually, my own sense is that it's okay to leave it as-is for another week or two, and let's revisit once 0.2.6 is stable?
14:04:03 <dgoulet> asn: I don't know, I have "Thursday March 19th, 13:30UTC at #tor-dev" ... but some triage now is fine by me anyway :)
14:04:12 <Sebastian> nickm: ok
14:04:15 <Sebastian> good
14:04:17 <nickm> dgoulet, asn : The plan is triage now for a while, then take a break till tomorrow
14:04:23 <asn> dgoulet: yeah i was also confused by that.
14:04:28 <dgoulet> nickm: ack!
14:04:32 <nickm> anything else before the triage?
14:04:40 * isabela I see red rows
14:04:45 <asn> let the games begin
14:04:47 <dgoulet> asn's question about 224 ?
14:04:55 <asn> it was not really a question
14:04:59 <asn> more like a thing i have in mind these days
14:05:00 <Yawning> do I need to be logged in to edit this?
14:05:03 <asn> Yawning: no
14:05:04 <nickm> asn: IMO sure it's okay to do a break-down of it.
14:05:07 <nickm> #endmeeting