See also: IRC log
<fsasaki> scribe: dorchard
<FrederickHirsch> which bridge number should we be using? are others on yet?
<maryann> felix, what is the bridge code?
<maryann> i had included 3348 in my mail, is that the right one?
<maryann> umit sends regrets
<fsasaki> I think she has a general conflict for this slot
<prasad> I will be a couple of minutes late. Sorry
<FrederickHirsch> eclipse instructions: http://www.w3.org/2006/07/eclipse/eclipse.html
test
<FrederickHirsch> scribe: FrederickHirsch
<fsasaki> scribe: Frederick
<fsasaki> scribeNick: FrederickHirsch
maryann: need to adjust rotation, new members Frederick and Umit
David: have been doing alphabeticallly on first name
maryann: whoever is chair is scribe the following week
... Coming rotation - Prasad, Toufic, Umit, Asir,
Dave, Felix, Frederick, Maryann
... First chair, then scribe, reporter to WS-Policy on meeting they chaired
... Team report from Dave,
Maryann sent minutes out
<fsasaki> I will not be available on the 29th
No editors call next week, next call 29 November.
7 items
1. Action 59, Umit, Maryann to follow up
2 action 64, implement guidelines portion for issue 3705
Asir: why not close action 59, restates the obvious
<prasad> Editors welcome Frederic and Umit (not on the call)
<FrederickkHirsch> I'm having acl problems accessing the action item list link
<scribe> ACTION: items to http://www.w3.org/2005/06/tracker/wspolicyeds/actions/open [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action01]
<fsasaki> http://www.w3.org/Bugs/Public/show_bug.cgi?id=3705
<fsasaki> http://www.w3.org/2005/06/tracker/wspolicyeds/actions/64
i fixed my acl problem, my mistake :)
2006-10-31: 1. Separated the Guidelines Document portion of the action into a separate new action - see http://www.w3.org/2005/06/tracker/wspolicyeds/actions/64 2. Framework document - implemented resolution for issue 3705 - see http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Oct/0116.html
<asir> resolution for issue 3705 is at http://lists.w3.org/Archives/Public/public-ws-policy/notes on action 54 include 2006Oct/0093.html
maryann - will update guidelines with related text
action 77 - Part 1 (Guidelines) - Implement the resolution for issue 3792 (section 4.* Primer->Guidelines) etc.
asir - make snapshot of primer to have version to go back to, then can use resolution to implement in primer
frederick: is it possible to make snapshot of guidelines before Maryanns changes to 77
maryann: is snapshot tagging
asir: create new file with date in file name, allows diff etc
... will do for version before Maryann's edits
for both xml and html
<scribe> ACTION: Asir create snapshots of guidelines before maryann edit [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action02]
<trackbot> Created ACTION-82 - Create snapshots of guidelines before maryann edit [on Asir Vedamuthu - due 2006-11-22].
<asir> ACTION: Asir to create snap shots (xml and html) of the primer and guidelines document prior to shuffling (related to issue 3792 [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action03]
<trackbot> Created ACTION-83 - Create snap shots (xml and html) of the primer and guidelines document prior to shuffling (related to issue 3792 [on Asir Vedamuthu - due 2006-11-22].
maryann: change date for completion on action 80?
... need to have consistent dates for two related
actions,
asir: change date for action 77
maryann: will continue to apply changes from F2F for 29th, then Frederick will review and take an editorial pass on guidelines and open new action
asir: who owns 77
maryann: maryann owns it
<prasad> Is it better to split 77 also into two separate AIs?
Goal is to have plan for 29th, not revision of guidelines
<asir> +1 to splitting 77 into multiple trackable AIs
<asir> Maryann to continue to own 77
<asir> delivery by Nov 29th
maryann: Maryann owns 77, will deliver by 29th a draft of merge. Frederick to review and take another editorial pass on document.
<asir> Frederick - will have a separate action to go through a second pass on guidelines
<asir> ACTION: Everyone to Part 3 (Guidelines) - Implement the resolution for issue 3792 (section 4.* Primer->Guidelines) etc. - Frederick will take a second pass [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action04]
<trackbot> Created ACTION-84 - Part 3 (Guidelines) - Implement the resolution for issue 3792 (section 4.* Primer->Guidelines) etc. - Frederick will take a second pass [on Everyone Everyone - due 2006-11-22].
action 84 specific to guidelines
<asir> ACTION: Felix to update action 84 [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action05]
<trackbot> Created ACTION-85 - Update action 84 [on Felix Sasaki - due 2006-11-22].
Summary: Maryann to merge primer material into guidelines and reorganize by 27 November, then Frederick to review and take additional editorial pass by 2 Dec
asir: action 79 finished MTOM revision, but CVS commit not completed
... Will take action 81, to resolution
for 3966
... will take additional action to update list of editors across all specs
<asir> ACTION: Asir to update the list of editors across all the docs (framework, attachment, primer and guidelines) [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action06]
<trackbot> Created ACTION-86 - Update the list of editors across all the docs (framework, attachment, primer and guidelines) [on Asir Vedamuthu - due 2006-11-22].
prasad: what is our goal, when, Last call?
maryann: need to do working draft before Last call, for guidelines
parsad: primer we've had working draft out
maryann: need the pair both ready for working group review and comment
... treat both together, without
ambiguity and overlap
felix: no need for transitions for these documents, just update now
maryann: need to indicate to chairs that we think we are done with all issues and editorial updates for both, without overlap
asir: as part of action 77, one point of style of guidance should be like primer style, forward pointers to
question answers
... who is doing that
maryann: I am taking a first pass
I'll take a second pass
Question - how does editorial team work in this case, do we have an editorial team review before bringing to working group?
prasad: This is a major change, so may want editorial team review
maryann: agrees
+1
Everyone should read guidelines
maryann: create action for everyone to review guidelines
... review by 8th December for editorial , plan for
delivery to working group on 13th
deliver 11th of December to working group mailing list
Editors should raise issues early the week of 4th so issues can be resolved that week if possible
asir: provide window, 11th earliest, 18th latest for delivery to working group
... this is a big job
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/First/maryann: First/ Succeeded: s/Prasad/Coming rotation - Prasad/ Succeeded: s/Frederic/Frederick/ Succeeded: s/2006/notes on action 54 include 2006/ Succeeded: s/finished/action 79 finished/ Succeeded: s/11th/11th of December/ Found Scribe: dorchard Inferring ScribeNick: dorchard WARNING: No scribe lines found matching previous ScribeNick pattern: <FrederickHirsch> ... Found Scribe: FrederickHirsch Found Scribe: Frederick Found ScribeNick: FrederickHirsch Scribes: dorchard, FrederickHirsch, Frederick ScribeNicks: FrederickHirsch, dorchard Present: Asir Dave Felix Frederick Maryann Prasad Regrets: Umit Agenda: http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0058.html Got date from IRC log name: 15 Nov 2006 Guessing minutes URL: http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html WARNING: No person found for ACTION item: items to http://www.w3.org/2005/06/tracker/wspolicyeds/actions/open [recorded in http://www.w3.org/2006/11/15-ws-policy-eds-minutes.html#action01] People with action items: asir everyone felix WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]