13:32:09 <nickm> #startmeeting
13:32:09 <MeetBot> Meeting started Wed Apr 15 13:32:09 2015 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:32:09 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:32:15 <nickm> welcome to the weekly tor dev meeting
13:32:21 <nickm> who's here?  I see isabela ...
13:32:28 <nickm> and I saw Yawning a little while ago...
13:32:30 <isabela> :)
13:32:35 <Yawning> hi
13:33:21 <nickm> dgoulet is off doing SponsorR meeting stuff, perhaps?
13:33:23 <qwerty1> hi
13:33:42 <nickm> hi qwerty1
13:34:00 <athena> hi meeting
13:34:01 <nickm> I guess we can start with status things
13:34:02 <nickm> hi athena !
13:34:54 <nickm> so my status is that I did nearly no programming this last week; I've been hoping to get more done, but other tasks are eating my time
13:35:02 <dgoulet> nickm: I'm in and out so don,t count on me :S
13:35:13 <nickm> I got the results of the triage spreadsheet mostly applied
13:35:27 <nickm> and I'm hoping to spend some real time programming really soon
13:35:32 <nickm> so much darned stuff
13:35:51 <nickm> but I expect I'm going to be more distracted than usual with stuff for a bit :)
13:35:55 <nickm> who's next?
13:36:25 <Yawning> I wrote some patches, but not as many as I'd like
13:36:34 <Yawning> (business as usual basically)
13:36:47 <Yawning> I talked about the bits I wrote at the patch thing yesterday
13:37:26 <Yawning> I'm also still half asleep
13:37:29 <Yawning> :/
13:37:34 <nickm> ow
13:38:40 <nickm> any pans for the coming week?
13:38:45 <Yawning> pt stuff
13:38:57 <Yawning> finish cleaning up the pt spec, do the revisions for 6411
13:39:19 <Yawning> try to fix my sleep schedule to be not inverted from the rest of the people in my time zone
13:40:49 <Yawning> (should I be more verbose?)
13:41:16 <nickm> i think that's fine
13:41:33 <nickm> I also hope that really soon we'll be prioritizing the stuff already allocated to 0.2.7, fwiw
13:41:44 <isabela> Yawning: lets coordinate via email a summary of sponsorT stuff
13:41:49 <Yawning> isabela: yeah
13:41:58 <isabela> cool
13:42:12 <nickm> athena / dgoulet : One of you want to go next?
13:43:07 <isabela> Yawning: I sent you something yesterday
13:43:19 <isabela> Yawning: but we can do this via email
13:44:41 <athena> been doing #14840 and #15358 to get a break from the long horrible code review; patches forthcoming
13:44:57 <nickm> eta on those?
13:46:51 <athena> probably tomorrow-ish
13:46:54 <dgoulet> nickm: afk here, sorry :S, bbl
13:46:55 <nickm> sounds good
13:47:11 <nickm> dgoulet: np; fill us on on what you're up to later, and catch up on backlog?
13:47:24 <nickm> so I think that's all the updates unless somebody else has one?
13:47:41 <nickm> what's there to talk about today?  I have a couple of things, and others may too.
13:47:58 <nickm> I'd like to figure out how we deal with all the tickets in 0.2.7.x and divvy them up, including stuff that sponsors want.
13:49:16 <nickm> And I'd like to ask who other than me might be interested in comentoring for TSoP; there are some applications I was supposed to look at on Monday, but Stuff came up, so I'll be looking today.
13:49:23 <nickm> any  other topics?
13:49:49 <isabela> nickm: I have a question
13:49:53 <nickm> go for it!
13:50:42 <isabela> nickm: so this the query 0.2.7 triage on trac reflects our spreadsheet?
13:50:47 <nickm> mostly!
13:50:48 <isabela> https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&milestone=Tor%3A+0.2.7.x-final&group=status&col=id&col=summary&col=milestone&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=priority&report=56
13:50:53 <isabela> sorry
13:50:55 <isabela> long url
13:51:02 <nickm> don't worry, we're used to those :)
13:51:05 <nickm> So, here's what I did.
13:51:15 <isabela> ok cool
13:51:22 <nickm> I applied 027-triaged-1-{in,out,deferrable} for everything we had triaged.
13:51:49 <isabela> ok
13:51:58 <nickm> Then I moved all the 027-triaged-1-out ones away (and maybe the deferrable too) for every status besides needs_review and needs_revision, on the theory that  if there's code we might want to have another look.
13:52:07 <nickm> So right now, in the 0.2.7 milestone, there are:
13:52:17 <nickm> things we decided to do.  They have the status 027-triaged-1-in
13:52:28 <nickm> things with code that we should have a look at before finally deferring
13:52:38 <nickm> things that were added after we started doing triage
13:52:43 <nickm> does that make sense?
13:53:01 <isabela> yes
13:53:04 <nickm> great
13:53:49 <nickm> isabela: any thoughts on how we should divide these up and make sure they get done in a timely way?
13:53:54 <isabela> I will review it and then we should 'close it' and if things needs to be added should have a good reason
13:55:01 <isabela> nickm: this meeting should be where people pick up work... I think we need to organize that query in a way the most important stuff shows at the top (has major priority) and at this meeting we review backlog and ppl pick up tasks from there
13:55:04 <nickm> hm, okay.  How do we decide who does what when?
13:55:19 <isabela> when is the month the release becomes a candidate?
13:55:27 <isabela> when we should freeze it
13:55:46 <nickm> I think we're aiming for feature-freeze in August.  We also need to be aware of external deliverables in sep and oct, I think
13:56:44 <isabela> yes, I will help organize that and keep at the top the important things.. I want to avoid 'me assigning things to ppl' ppl should pick up the tasks they want to work on from a pre-organized list (does that makes sense?)
13:57:08 <isabela> normally we should always only care about the top of the backlog... and I can help maintain it and keep the important stuff at the top
13:57:15 <nickm> seems okay to me, but we need to be aware of stuff that nobody wants to do, and negotiate to make sure it gets done soon.
13:57:24 <isabela> yes
13:57:27 <nickm> (I did not apply sponsor tags to the tickets , and I did not change priorities)
13:57:39 <isabela> i will do that dont worry
13:57:43 * isabela back in the game
13:58:06 <nickm> great
13:58:39 <nickm> so whenever we get something done, we should grab something for ourselves, based on priorities, from the triaged-into-0.2.7 items, and assign it to ourselves?
14:00:02 <isabela> we dont have formal sprints or anything yet, but if we had one. and this was a sprint meeting we would go down the backlog, picking up tasks till we get to the limit of things we can do for the sprint (a sprint normally is one or two weeks)
14:00:45 <isabela> my function is to keep the backlog organized so you just need to look at what is at the top
14:00:50 <isabela> and work down the list
14:01:51 <isabela> let me know if you have any concerns or questions
14:03:20 <nickm> sounds good.  So for this week, we wing it and do whatever we think will be smartest, and expect to be a little more organized at the next meeting? :)
14:03:49 <isabela> yes sir!
14:04:00 <nickm> sounds good to me
14:04:15 * nickm looks again at our backlog above to see what more topics we had.
14:04:38 <nickm> oh yeah, who is interested in tsop mentoring anything on little-t tor?
14:04:45 <nickm> (and do we have more things to talk about this week?)
14:05:21 <Yawning> nickm: depending on what it is, I could be convinced to mentor
14:05:36 <nickm> okay.  I'll forward stuff to you if I think you might be interested
14:05:47 <Yawning> I commented on 1 I think
14:05:52 <Yawning> on the list
14:05:55 <nickm> great
14:06:32 <nickm> anything else for this week?
14:08:46 <nickm> ok, sounds fine then. That was a fast one! :)
14:08:47 <nickm> #endmeeting