16:28:08 <RRSAgent> RRSAgent has joined #tagmem
16:28:08 <RRSAgent> logging to http://www.w3.org/2013/07/18-tagmem-irc
16:29:57 <ht> ht has changed the topic to: Agenda: http://www.w3.org/wiki/TAG/Planning/2013-07-18-TC
16:43:13 <annevk> annevk has joined #tagmem
16:44:12 <annevk> I've got a problem. I'm in SF and there's been a power outage. So the internet at the office is down. And now I'm in a Starbucks and the wireless is crappy and the music is loud, and crappy too.
16:49:52 <dka> dka has joined #tagmem
16:52:10 <JeniT> JeniT has joined #tagmem
16:54:12 <annevk> I think I'll be able to attend over IRC though.
16:56:31 <dka> zakim, call me or something
16:56:31 <Zakim> I don't understand 'call me or something', dka
16:56:52 <twirl> twirl has joined #tagmem
16:57:16 <dka> rrsagent, start meeting
16:57:16 <RRSAgent> I'm logging. I don't understand 'start meeting', dka.  Try /msg RRSAgent help
16:57:23 <Zakim> TAG_Weekly()1:00PM has now started
16:57:31 <Zakim> + +44.771.520.aaaa
16:57:46 <dka> zakim, who's here?
16:57:46 <Zakim> On the phone I see +44.771.520.aaaa
16:57:47 <Zakim> On IRC I see twirl, JeniT, dka, annevk, RRSAgent, Zakim, marcosc, timbl, ht, Yves, trackbot, slightlyoff, wycats_, bkardell, plinss
16:58:12 <dka> zakim, aaaa is me
16:58:12 <Zakim> +dka; got it
16:58:14 <Zakim> +??P3
16:59:22 <ht> trackbot, start telcon
16:59:25 <trackbot> RRSAgent, make logs public
16:59:27 <trackbot> Zakim, this will be TAG
16:59:27 <Zakim> ok, trackbot, I see TAG_Weekly()1:00PM already started
16:59:28 <trackbot> Meeting: Technical Architecture Group Teleconference
16:59:28 <trackbot> Date: 18 July 2013
16:59:33 <dka> zakim, ??p3 is Sergey
16:59:33 <Zakim> +Sergey; got it
16:59:40 <ht> scribenick: ht
16:59:45 <ht> scribe: Henry S. Thompson
16:59:55 <ht> chair: Dan Appelquist
17:00:54 <dka> Zakim, Sergey is twirl
17:00:54 <Zakim> +twirl; got it
17:01:00 <dka> zakim, who is here?
17:01:00 <Zakim> On the phone I see dka, twirl
17:01:01 <Zakim> On IRC I see twirl, JeniT, dka, annevk, RRSAgent, Zakim, marcosc, timbl, ht, Yves, trackbot, slightlyoff, wycats_, bkardell, plinss
17:01:01 <Zakim> +[IPcaller]
17:01:17 <dka> zakim, [ipcaller] is marcos
17:01:17 <Zakim> +marcos; got it
17:01:19 <Zakim> +plinss
17:02:47 <Zakim> +??P5
17:03:24 <ht> zakim, disconnect me
17:03:24 <Zakim> ht is being disconnected
17:03:26 <Zakim> -ht
17:03:52 <Zakim> +Noah_Mendelsohn
17:04:07 <Zakim> +??P10
17:04:43 <annevk> Zakim, passcode?
17:04:43 <Zakim> the conference code is 0824 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), annevk
17:04:54 <Zakim> +[IPcaller]
17:04:58 <annevk> Zakim, [IP is me
17:04:58 <Zakim> +annevk; got it
17:05:49 <annevk> welcome twirl!
17:06:06 <slightlyoff> Yep
17:06:18 <annevk> ht: https://twitter.com/briankardell
17:06:25 <Yves_> Yves_ has joined #tagmem
17:06:27 <ht> zakim, who is on the call
17:06:27 <Zakim> I don't understand 'who is on the call', ht
17:06:31 <ht> zakim, who is on the call?
17:06:31 <Zakim> On the phone I see dka, twirl, marcos, plinss, Noah_Mendelsohn, ht, annevk
17:06:43 <Zakim> +Yves
17:06:52 <Noah> Noah has joined #tagmem
17:07:07 <slightlyoff> P
17:07:13 <ht> Topic: Admin
17:07:15 <slightlyoff> Yep
17:07:32 <ht> Welcome to new member Sergei Konstantinov (Yandex)
17:07:42 <ht> s/Welcome/DKA: Welcome/
17:07:43 <twirl> Hi, everyone :)
17:08:06 <ht> Topic: TC39 / TPAC Update and Next Steps
17:08:22 <ht> DKA: Update from Philippe le Hegaret on this
17:08:42 <Zakim> + +1.415.997.aabb
17:09:47 <slightlyoff> no discussion in tc39 that I'm aware of
17:10:37 <ht> DKA: So the question is how we move the discussion from a private conversation to engage all of TC39
17:10:54 <ht> ... to make good on our promise of making TPAC a welcoming place for TC39
17:11:31 <ht> AR: I'll bring this up in person at the TC39 meeting next week
17:11:41 <ht> DKA: Before our next call?
17:11:43 <ht> AR: Yes
17:12:18 <ht> Topic: Review current work including new work items and spec reviews
17:12:28 <ht> DKA: Round robin?
17:12:46 <dka> zakim, who is here?
17:12:46 <Zakim> On the phone I see dka, twirl, marcos, plinss, Noah_Mendelsohn, ht, annevk, Yves, +1.415.997.aabb
17:12:48 <Zakim> On IRC I see Noah, Yves_, twirl, JeniT, dka, annevk, RRSAgent, Zakim, marcosc, timbl, ht, Yves, trackbot, slightlyoff, wycats_, bkardell, plinss
17:12:52 <ht> HST: +1 to round robin
17:13:13 <ht> DKA: MC, anything happening?
17:13:29 <ht> MC: Not sure, given uncertainty about how my participation will go forward
17:13:34 <Zakim> -twirl
17:13:59 <ht> PL: I have been working on github mirroring and so on
17:14:06 <twirl> I'm cut off somehow
17:14:17 <slightlyoff> plinss: exciting!
17:14:23 <ht> ... I'll give more info when I'm ready to go public
17:14:33 <ht> DKA: Progress on website redesign?
17:14:45 <ht> PL: No, will set up a repo and get that out
17:14:59 <Zakim> +??P3
17:15:14 <twirl> I redialed
17:15:26 <ht> NM: I mentioned the HTTP2.0 which you might want to look at at some point
17:16:06 <dka> HT: I've spent the last week or so collecting statistics about http usage in conjunction with http 1.1 review.
17:16:15 <dka> … About to do a TAG blog post with some numbers.
17:16:30 <dka> … highlight is - http bis needs to look very carefully at what it has to say about con neg.
17:16:53 <dka> … I've looked at 100m http requests and only a couple of hundred 300 responses - responses supposed to be given in con neg.
17:18:06 <slightlyoff> ht: can you charachterize the services that the requests are from in the post?
17:18:14 <annevk> (300 is a kind of a useless response code. Nothing happens.)
17:18:28 <ht> AR: That's harder, privacy issues
17:18:37 <ht> s/ht:/ht,/
17:18:42 <ht> s/AR:/AR,/
17:18:46 <slightlyoff> ht: are they from many services? a few?
17:18:51 <slightlyoff> ht: that sort of thing
17:19:33 <annevk> I don't have anything. I'm been traveling and otherwise occupied.
17:19:45 <ht> s/ht:/ht,/
17:19:48 <ht> s/ht:/ht,/
17:20:03 <masinter> masinter has joined #tagmem
17:20:17 <dka> zakim, aabb is slightlyoff
17:20:17 <Zakim> +slightlyoff; got it
17:20:37 <ht> AR: I spoke with Chris Wilson about Web Audio, which I've made an initial stab at writing up
17:20:52 <ht> ... Plan to work on that with YK and also do a draft review
17:21:11 <ht> DKA: I reviewed your Web Audio doc't, I think it looks good
17:21:55 <ht> AR: There's an important arch. issue which isn't addressed in my doc't yet: shared mutable data which is viewable from multiple concurrent javascript thread
17:21:55 <Zakim> -annevk
17:22:06 <ht> ... That breaks a core invariant of the JS processing model
17:22:43 <ht> ... I have a proposal on how to avoid this, but I'm not quite ready to propose it until I research things more
17:23:21 <ht> AR: I hope they can sidestep the problem via my approach, but it's going to be trickhy
17:23:26 <ht> s/trickhy/tricky/
17:23:31 <ht> DKA: Timeline?
17:24:19 <ht> AR: I'm ready for feedback ASAP on the doc't as it stands, wrt both content and format/style -- is this the kind of way we should be feeding into WGs?
17:24:39 <ht> DKA: The variation between formal and informal in the doc't did strike me
17:24:55 <ht> AR: Put in an issue or pull requests for some changes
17:25:08 <ht> DKA: Style isn't the main point
17:25:50 <ht> DKA: What else do we have in github in the spec review area. . .
17:25:58 <ht> ... Any other issues?
17:26:13 <ht> DKA: I added the Push API to the spec review list
17:26:34 <slightlyoff> have the chairs thought about a plan for how to work through the backlog in a structured way?
17:26:46 <ht> ... I reached out to Charles and Art of Web Apps to try to begin coordination between us and Web Apps
17:26:59 <ht> ... Certainly we should plan for joint meeting at TPAC
17:27:13 <ht> ... We may ask Art to join us in Cambridge at the Sept. F2F
17:27:54 <ht> DKA: But we need to move sooner on key topics -- Charles is keen to see the Promises discussion moving soon
17:28:36 <ht> AR: Wrt the Status pages [ref?] which the W3C maintains, is there a process we have / should have to monitor that?
17:28:58 <slightlyoff> right, makes sense
17:29:07 <ht> ... I'm happy to work on a "put out fires" informal way, but do we need more?
17:29:33 <ht> DKA: I was expecting to use the spec review list for this
17:29:36 <Yves_> Some groups have a dashboard, like webapps. Otherwise the WG page and their publication list.
17:30:04 <ht> AR: That's fine, but how do we keep confident that we keep up to date on what's new and might need to go on there
17:30:19 <Zakim> -twirl
17:30:27 <ht> MC: I agree, is _ad hoc_ monitoring sufficient?
17:30:52 <Zakim> +??P1
17:30:59 <ht> MC: So, recently, a [???] spec came up, do we need to put it on the list -- i.e., do we treat all new specs equally
17:31:39 <ht> DKA: We could have a semi-automatic process, where we periodically go through new specs and vote them in or out
17:31:58 <ht> AR: Maybe just auto-generate a bug on the spec review list for new pubs
17:32:09 <ht> DKA: Sure -- propose something?
17:32:12 <ht> AR: Will do
17:32:22 <ht> s/?/ by email?/
17:32:30 <slightlyoff> oh, right
17:32:36 <slightlyoff> totally forgot about that...sorry Yves_
17:32:49 <ht> PL: YL did take an action to try to automate this, at the F2F
17:33:13 <ht> DKA: But YL is currently blocked on that with hardware pblms
17:34:18 <slightlyoff> I thought the proposa was to _leave it open_
17:34:22 <ht> DKA: Ashok Malhotra has sent email about a draft candidate for a TAG blog post about the [legal xx stuff] -- once we have a look at it, I expect we will say yes
17:34:26 <slightlyoff> not to commit to a longer meeting every 2 weeks
17:34:52 <ht> PL: We still have a decision to make on whether we have a 90-minute meeting on a regular basis. . .
17:35:23 <Noah> I think you should send a signal as to when TAG members should try to hold > 30 mins free, and when not.
17:35:32 <Noah> My concern is that when you do want a longer call, you'll find conflicts
17:35:35 <slightlyoff> +1 to what DKA jsut said
17:35:49 <ht> DKA: I thought the plan was a) have a 30-minute standup every week, _and_ to have the possibility of deciding to extend some calls for technical discussion if we have something queued up
17:36:01 <twirl> +1
17:36:08 <slightlyoff> agree with that
17:36:11 <Yves_> Note that inviting spec editors and not only chairs might be intetesting
17:36:23 <ht> PL: Note the YK has a conflict post 30-mins every other week, so we need to be aware of that
17:36:53 <dka> Proposed RESOLUTION: have a 30-minute standup every week, _and_ to have the possibility of deciding to extend some calls for technical discussion if we have something queued up, taking into account members' scheduling issues and providing the group adequate notice.
17:37:38 <slightlyoff> +1
17:37:51 <Yves_> +1
17:38:00 <ht> DKA: Notice would normally be given by the Monday before
17:38:10 <dka> RESOLUTION: have a 30-minute standup every week, _and_ to have the possibility of deciding to extend some calls for technical discussion if we have something queued up, taking into account members' scheduling issues and providing the group adequate notice (ideally by the Monday of that week EOD).
17:38:19 <ht> PL: Maybe we end each standup with a call for tech. topic for the next week
17:38:53 <ht> HST gives regrets for next 6 weeks :-(
17:39:09 <slightlyoff> ht can't make next week = (
17:39:18 <slightlyoff> +1
17:39:36 <ht> DKA: What about discussing http2.0 next week?
17:39:52 <ht> DKA: But HST won't be here -- take it to email?
17:40:06 <ht> HST: You can talk about it w/o me, but sure, let's start by email
17:40:22 <ht> DKA: Adjourned
17:40:24 <slightlyoff> late all
17:40:27 <slightlyoff> later, even
17:40:28 <Zakim> -dka
17:40:29 <Zakim> -marcos
17:40:30 <Yves_> Bye
17:40:33 <Zakim> -slightlyoff
17:40:34 <Zakim> -Yves
17:40:36 <Zakim> -twirl
17:40:37 <Zakim> -Noah_Mendelsohn
17:40:37 <Zakim> -plinss
17:40:40 <ht> RRSAgent, bye
17:40:40 <RRSAgent> I see no action items