21:01:20 RRSAgent has joined #audio 21:01:20 logging to http://www.w3.org/2011/12/12-audio-irc 21:01:22 RRSAgent, make logs world 21:01:24 Zakim, this will be 28346 21:01:24 ok, trackbot; I see RWC_Audio()4:00PM scheduled to start now 21:01:25 Meeting: Audio Working Group Teleconference 21:01:25 Date: 12 December 2011 21:01:33 zakim, agenda? 21:01:33 I see 5 items remaining on the agenda: 21:01:34 1. Review of action items and resolutions from last week [from olivier] 21:01:36 2. Splitting work on use cases and requirements [from olivier] 21:01:37 3. Intro to Tracker [from olivier] 21:01:38 4. f2f logistics [from olivier] 21:01:39 5. Any other business [from olivier] 21:02:16 zakim, who is here? 21:02:16 I notice RWC_Audio()4:00PM has restarted 21:02:18 On the phone I see chrislo, kinetik, olivier, Michelle_Park, Doug_Schepers 21:02:19 On IRC I see RRSAgent, chris, Zakim, chrislo, MikeSmith, colinbdclark, kinetik, foolip, trackbot, olivier, shepazu, paul_irish 21:02:50 shepazu has changed the topic to: Telcon code 28346 ("AUDIO") 21:03:13 Last minutes -> http://lists.w3.org/Archives/Public/public-audio/2011OctDec/0132.html 21:04:02 scribeNick: chrislo 21:04:15 zakim, take up agendum 1 21:04:15 agendum 1. "Review of action items and resolutions from last week" taken up [from olivier] 21:04:51 Al sends his regrets. 21:05:00 Action 1 from previous meeting is done. 21:05:01 Sorry, couldn't find user - 1 21:05:19 shepazu: Action 2 is in progress 21:05:43 olivier: has integrated WebRTC use cases into our doc. (Action 3) 21:05:51 http://www.w3.org/2011/audio/wiki/Use-Cases#Requirements_from_the_Real-Time_Communications_Working_Group 21:06:31 olivier: the WebRTC have more requirements than use cases, so we'll need to find common terminology. 21:06:40 trackbot, close action-5 21:06:41 ACTION-5 Integrate WebRTC use cases into our doc closed 21:06:47 but this looks good enough for the time being. So closing. 21:08:37 chris: is a bit concerned about changing the name since the API has wide coverage so far. Doesn't want to cause confusion by changing the name at this point. 21:09:15 olivier: the reason this was proposed was to keep the next steps as neutral as possible at this stage. Hence wanting to switch away from the generic name. 21:09:32 olivier: remembers Roq saying he could live with keeping the names as currently. 21:09:42 s/Roq/ROC/ 21:09:54 chris: suggests that the umbrella name is "Audio processing API" and keep the names as current. 21:10:05 olivier: looking for consensus. 21:10:47 Resolution: The three documents will be Audio Processing API for the umbrella, and Web Audio API / Media Streaming API for the two proposals respectively. 21:10:50 zakim, take up agenda 4 21:10:50 agendum 4. "f2f logistics" taken up [from olivier] 21:12:15 chris: can make enquires about whether Google could host the meeting. 21:12:27 chris: he can ask his manager. 21:12:56 olivier: do you think f2f could be held in Southern California / Mountain View. 21:13:17 chris: if we're choosing NAMM event it would be better if it was close to the event itself. 21:13:35 chris: I'll have to look into it a bit more. 21:13:51 chris: asks if Tom Wight had suggestions for a venue. 21:14:35 shepazu: looks it up, they don't have the space for 1-2 days. 21:15:16 shepazu: we should ask if the NAMM members have space for 10 people for 1-2 days 21:15:27 chris: could look into whether Google could finance that. 21:15:42 shepazu: will take it off list, keep olivier and chris in the loop. 21:17:10 olivier: for chrislo and I approval to attend is granted already, we're ok if logistics can be secured. 21:17:26 olivier: what is the deadline for people to confirm, round the table? 21:17:56 chris: pretty easy for me. Would be good to attend NAMM as well. 21:19:21 shepazu: that's the link for anyone interested in attending. 21:20:05 shepazu: I got an invitation a couple of days ago. The deadline is today for signing up for invites. 21:20:22 olivier: the invitation, as I understand it, does not have strings attached. 21:20:29 shepazu: agrees. 21:21:14 zakim, take up agendum 2 21:21:14 agendum 2. "Splitting work on use cases and requirements" taken up [from olivier] 21:22:20 olivier: could we already get a rough idea of who is planning to work on which areas of the use case and requirements docs. 21:22:45 agenda+ publication of fpwd 21:22:54 http://www.w3.org/2011/audio/wiki/Use-Cases 21:23:04 olivier: that's the use cases document 21:23:13 olivier: we have 8 classes at the moment in this document. 21:23:29 http://www.w3.org/TR/widgets-reqs/#requirements 21:23:53 olivier: I think we should try, for each class, to make sure the requirements are in line with the template shepazu just posted. 21:26:13 chris and chrislo mention that the XG group didn't spend too long on the pre-exisiting use case documents. 21:26:43 olivier: we need to spend a bit of time on this for the WG because it will help us to objectively rationalize/refine the two proposals. 21:26:48 shepazu: agrees. 21:27:30 shepazu: we need both use cases and requirements. They're good for communicating with the community and other groups. 21:27:50 shepazu: make sure there's no surprises and get early involvment from other groups. 21:28:04 shepazu: and we can advertise what we're working on, to get other people excited. 21:28:37 shepazu: it also helps if we want to move to candidate recommendation status. It helps to show that the work satisfies widely held needs. 21:28:49 shepazu: it's good to have a checklist for our own book keeping purposes. 21:29:22 olivier: asks shepazu to take us through the document. 21:29:22 http://www.w3.org/TR/widgets-reqs/#requirements 21:29:33 s/the/this 21:30:49 shepazu: rationale are known issues 21:31:25 shepazu: this is a pretty rigorous format. 21:31:40 shepazu: if we split use cases away from the requirements we can link between them. 21:32:11 shepazu: it will be useful when we have people actively reviewing the document. 21:32:45 shepazu: need identifier/name, motivation, rationale and a link to the use cases. 21:34:27 ACTION: doug to show example of how to derive requirement from our use cases on the mailing-list 21:34:28 Created ACTION-6 - Show example of how to derive requirement from our use cases on the mailing-list [on Doug Schepers - due 2011-12-19]. 21:34:51 shepazu: also the two specs have requirements already, so it's fine to "back port" them to this document. 21:35:13 shepazu: doing this will help us tease out the differences between the two documents. 21:35:39 q+ 21:36:25 chris: will be able to take a look at back porting the requirements. 21:36:42 shepazu: doesn't want to cut into chris's time as editor and implementor 21:36:47 olivier: concurs 21:36:57 ACTION: Chris_Rogers to start back porting requirements from his proposed spec into use cases/reqs doc 21:36:57 Sorry, couldn't find user - Chris_Rogers 21:37:46 shepazu: suggests we start on the wiki, he can convert later to another format. 21:37:47 ACTION: Chris Rogers to start back porting requirements from his proposed spec into use cases/reqs doc 21:37:47 Sorry, amibiguous username (more than one match) - Chris 21:37:47 Try using a different identifier, such as family name or username (eg. clowis, crogers) 21:37:51 shepazu: will create a page. 21:38:03 ACTION: CRogers to start back porting requirements from his proposed spec into use cases/reqs doc 21:38:03 Created ACTION-7 - Start back porting requirements from his proposed spec into use cases/reqs doc [on Chris Rogers - due 2011-12-19]. 21:38:53 zakim, take up agendum 6 21:38:53 agendum 6. "publication of fpwd" taken up [from olivier] 21:39:19 fpwd = first public working draft 21:39:37 olivier: asks shepazu to explain the importance of this 21:40:15 shepazu: people are often asking what is happening with the audio working group, they are not sure of our progress 21:40:24 shepazu: so publishing frequently is important. 21:40:49 shepazu: w3c has a policy that we need to publish every 3 months (heartbeat requirement) 21:41:17 shepazu: many groups are quite lax about this, but it would be good for us in particular to show that we are actively moving forward. 21:41:51 chris: asks what the process is when publication happens - are they snapshots of a more rapidly changing document? 21:42:03 chris: should I commit to a repo on a day-to-day basis 21:42:31 shepazu: we decided to publish three documents as separate documents that are updated on their own time. 21:42:49 shepazu: the editors draft should always be the most up to date version of the document. 21:43:19 shepazu: you (chris) should always publish to mercurial repo, when we decide to publish shepazu or Thierry will take a snapshot and publish to TR-space 21:43:26 TR = technical report. 21:43:57 chris: I need to get changes back to the trunk repo when changes are made to publication. 21:44:53 shepazu: changes made in the publication fork should be merged back in. shepazu will work with chris to do this. 21:45:54 chris: I have some changes to make so should I put them directly in the mercurial repo? 21:45:57 shepazu: yes. 21:46:12 shepazu: and let me know, so I can keep the publication up to date. 21:54:28 shepazu: gives a brief update on recruiting members for the group 21:54:30 zakim, take up agenda 3 21:54:30 agendum 3. "Intro to Tracker" taken up [from olivier] 21:54:43 shepazu: hardware people as well as implementors are welcome. 21:54:47 http://www.w3.org/2011/audio/track/ 21:55:11 ^^ this is the tracking tool for our working group 21:55:23 olivier: it will help us track action items, issues in the spec etc. 21:55:55 olivier: go and have a look, try it out. We'll be using this a lot. 21:56:03 shepazu: I'll be setting a test! 21:56:20 zakim, take up agenda 5 21:56:20 agendum 5. "Any other business" taken up [from olivier] 21:56:22 olivier: Any other business? 21:57:10 olivier: volunteer scribe for next week? 21:57:37 Matthew volunteers to scribe next time. 21:58:02 shepazu: would like us to focus on technical stuff going forward as much as possible. 21:58:18 olivier: agrees, it will happen now we're up and running. 21:58:32 olivier: adjorns, with thanks. 21:58:37 -olivier 21:58:38 -Michelle_Park 21:58:38 -Doug_Schepers 21:58:40 -kinetik 21:58:44 -chrislo 21:58:45 RWC_Audio()4:00PM has ended 21:58:47 Attendees were chrislo, kinetik, olivier, Michelle_Park, Doug_Schepers 21:58:50 rrsagent, draft minutes 21:58:50 I have made the request to generate http://www.w3.org/2011/12/12-audio-minutes.html olivier 21:58:52 trackbot, end telcon 21:58:52 Zakim, list attendees 21:58:52 sorry, trackbot, I don't know what conference this is 21:58:53 RRSAgent, please draft minutes 21:58:53 I have made the request to generate http://www.w3.org/2011/12/12-audio-minutes.html trackbot 21:58:54 RRSAgent, bye 21:58:54 I see 4 open action items saved in http://www.w3.org/2011/12/12-audio-actions.rdf : 21:58:54 ACTION: doug to show example of how to derive requirement from our use cases on the mailing-list [1] 21:58:54 recorded in http://www.w3.org/2011/12/12-audio-irc#T21-34-27 21:58:54 ACTION: Chris_Rogers to start back porting requirements from his proposed spec into use cases/reqs doc [2] 21:58:54 recorded in http://www.w3.org/2011/12/12-audio-irc#T21-36-57 21:58:54 ACTION: Chris Rogers to start back porting requirements from his proposed spec into use cases/reqs doc [3] 21:58:54 recorded in http://www.w3.org/2011/12/12-audio-irc#T21-37-47 21:58:54 ACTION: CRogers to start back porting requirements from his proposed spec into use cases/reqs doc [4] 21:58:54 recorded in http://www.w3.org/2011/12/12-audio-irc#T21-38-03 21:59:11 olivier: there was a RESOLUTION at the top, not sure I captured it correctly.