W3C

- DRAFT -

Web Performance Working Group Teleconference

27 Jul 2011

See also: IRC log

Attendees

Present
[Microsoft], Arvind, Jain, James, Simonsen, Nic, Jansma, Jatinder, Mann, TonyG
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Jatinder Mann

Contents


<trackbot> Date: 27 July 2011

<scribe> scribe: Jatinder Mann

Jatinder: The WG has agreed to publish Performance Timeline and User Timing specs as FPWD.
... Has everyone looked at the changes?

Tony: Changes look good.

Jatinder: Should we setup a timeline to take these specs to Last Call? I would recommend taking Performance Timeline, Resource Timing and User Timing specs into Last Call on August 8, 2011. Thoughts?

Tony: We were wondering whether we should hold to go into last call until we start looking at implementation.

Jatinder: We have started looking at implementations and haven't seen any issues yet.

Tony: What is the process for going to CR? Don't we need two implementations to enter CR?

Jatinder: Yes, I believe that is the case for entering CR. I'm not sure what state the specs would be if we go to last call without two implementations.

Arvind: The specs can go to last call. After last call, if there are not two implementations, they will go to call for implementations. Once two implementations are available, the specs will then move to candidate recommendation.

Jatinder: That makes sense. In that case, shall we go to last call?

Arvind: Yes, let's do it.

Tony: I'm not against.

Jatinder: The WG has agreed to take Performance Timeline, Resource Timing and User Timing specs into Last Call on August 8, 2011. This period will last at least until August 31, 2011. We may want to move the last call period to 6 weeks in case there are a lot of August vacations.
... Is there any other business we want to discuss?

Tony: There was one small issue. While reading the webIDL spec, I noticed that typed arrays (T[]) might be something interesting to consider for these specs. What are your thoughts?

Jatinder: I'm sorry, I haven't read that portion of the WebIDL spec yet. We should probably all read the WebIDL spec and discuss futher if we want to consider typed arrays. I will open an action item to look into to typed arrays.

Action Jatinder to look into updating the Timing specs to use typed arrays (T[]) from the Web IDL spec.

<trackbot> Created ACTION-45 - Look into updating the Timing specs to use typed arrays (T[]) from the Web IDL spec. [on Jatinder Mann - due 2011-08-03].

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2011/07/27 21:03:05 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: JatinderMann
Found Scribe: Jatinder Mann

WARNING: No "Topic:" lines found.


WARNING: Replacing list of attendees.
Old list: +1.650.253.aaaa [Microsoft] +1.650.214.aabb +1.734.332.aacc
New list: [Microsoft]

Default Present: [Microsoft]
Present: [Microsoft] Arvind Jain James Simonsen Nic Jansma Jatinder Mann TonyG

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 27 Jul 2011
Guessing minutes URL: http://www.w3.org/2011/07/27-webperf-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]