<scribe> scribe: Francis_Storr

Update on publishing

c: update in publishing. responses to deadlines sent out on Monday. Chairs will process responses next Monday.

rm: when we get back after the holidays, there will be a survey coming out. Keep an eye out for that.

Continue decision policy

js: continued to work on updated policy this week. really close to approving it and would like to get it finished.
... have drafted an updated to address all of Wilco's points, he reviewed and approved them all.

<Chuck> proposal part 1: For decisions being considered in task force meetings, objections should be raised immediately by participants in that meeting when there is a call for objections. Participants who miss meetings are expected to read the resolutions and raise objections to any decisions made within a week of the meeting. It is a best practice of the group to include a list of resolutions in the email of the

<Chuck> proposal part 2: minutes of the meeting. If participants will be out for more than a week, let the facilitators know so they can take this into account when considering objections. Facilitators can extend the timeline at their discretion.

<sajkaj> +1

<KimD> +1

<Rachael> +1

jsa: suggests a clause at the end to reference standard holiday periods.

<Chuck> part 2: minutes of the meeting. If participants will be out for more than a week, let the facilitators know so they can take this into account when considering objections. Facilitators can extend the timeline at their discretion, and will take into account holidays and W3C schedules..

<Chuck> ...and will always take into account holidays and W3C schedules.

<Chuck> ...and will always take into account holidays and W3C moratoria.

<Chuck> and will always take into account worldwide public holidays and W3C moratoria.

<Chuck> and will always take into account factors such as public holidays and W3C moratoria.

<KimD> +1 to and will always take into account factors such as public holidays and W3C moratoria.

<sajkaj> +1

<Chuck> +1

+1

<Rachael> 0 A bit concerned about the "always"

<sarahhorton> 0 Liked the "worldwide"

<sajkaj> W3C calendar interruptions: https://www.w3.org/wiki/Holidays

<Chuck> and will take into account factors such as worldwide public holidays and W3C moratoria.

<sarahhorton> +1

<sajkaj> +1

<KimD> +1 (I like taking "always" out too)

<Rachael> +1

<Chuck> For decisions being considered in task force meetings, objections should be raised immediately by participants in that meeting when there is a call for objections. Participants who miss meetings are expected to read the resolutions and raise objections to any decisions made within a week of the meeting. It is a best practice of the group to include a list of resolutions in the email of the

RESOLUTION: Amend the Silver decision policy first bullet to read as follows...

<Chuck> For decisions being considered in task force meetings, objections should be raised immediately by participants in that meeting when there is a call for objections. Participants who miss meetings are expected to read the resolutions and raise objections to any decisions made within a week of the meeting. It is a best practice of the group to include a list of resolutions in the email of the

<Chuck> minutes of the meeting. If participants will be out for more than a week, let the facilitators know so they can take this into account when considering objections. Facilitators can extend the timeline at their discretion, and will take into account factors such as worldwide public holidays and W3C moratoria.

early draft of training for writing content

<jeanne> https://docs.google.com/presentation/d/1-V6svcPVxBve3_5lBeDvks7xOMJCFSNcuSUpnmBTzws/

js: this is the start of a training class for people who want to write guidelines. What we expect is that this part will take an hour and the second part will be people writing guidelines and asking questions.
... we have guidelines, a how-to, guidelines with multiple outlines, and scoring detail.

<Rachael> The image address for what we used is https://w3c.github.io/silver/guidelines/img/structure-scoring.svg

<Rachael> There are a few subtle differences and I think its worth using hte one in the document to reduce confusion

js: want to look at the WCAG 3 writing process. Have a new drawing for that.
... updates on work on the scope
... if there are updates or comments, please comment on the slides

rm: incorporating an example all the way through would be useful.

welcome Jen :)

ca (and others): happy holidays!

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: jeanne Chuck Francis_Storr Rachael sajkaj KimD SuzanneTaylor sarahhorton shari
Regrets: David Charles Todd Wilco\ Peter_Korn
Found Scribe: Francis_Storr
Inferring ScribeNick: Francis_Storr

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)