See also: IRC log
<trackbot> Date: 12 August 2015
<scribe> scribe: fesch
js: are we set for tomorrow?
ts: we also have aria/dpub call
js: is there feedback on the prototype APA web page?
fe: where does the style come
from?
... style looks old
ts: WAI doesn't look like this
js: no control over style
fe: I think the annotation work group looks nicer
ts: agrees the WAI page looks dated
js: will forward comment on style
rs: duplicate charter link/patent
policy under join
... anything on liasons?
... task forces - I think you should mention who else is on the
task force
... need link for docs
js: under current work
... have a compliant on missing decision policy, we have a
draft decision policy,
... we have an addition to the decision policy and not close a
decision if regular contributors are on vacation...
... also may want to have longer time for feedback - usually 48
hours but can make it longer, Judy asks us to make the feedback
time to a week
rs: why do we need a week?
js: some argue that we have people all over the world... may need time...
rs: a week is too long for everything
js: I agree a week is too long for everything
rs: maybe for a formal vote - OK,
but for day-to-day that is too long, if someone finds an issue
in the minutes, then we can take it up
... don't want to do this for details...
js: we decided going forward we will log every decision
jd: recording everything may be too much, but we can record that - I already put details in an action
rs: I don't want to go through every resolution and paste that on a page
jd: I will volunteer for ARIA
rs: what about task forces?
js: we typically close by logging
a resolution
... what if someone can scrape it from the minutes
... it really helps to be systematic about the subject
... If I am consistent on CFC and the subject we can use a
scraper to pick that up
jd: if we use github to track
issues, in my commint message, then it appears in github for
you
... when do we have to state what we are going to do about
decisions?
js: can 't make a policy until we are chartered and not in August (too many folks on vacation)
jd: loves github for keeping track of stuff
js: all the time to discuss doesn't count as part of the week, the week starts after a CFC has been put out
jd: rich and my concerns are about details from a spec writer
js: we may need a yardstick for deciding, in the decision policy
jd: devils advocate - maybe we should only do things over email and no meetings
js: very few significant
decisions where there is not a CFC
... feedback for Judy? Not everyone here, we usually put a
CFC...
jd: wrt spec work, jd has some ideas on this....
js: one idea we already came up with, is what does not have to have a CFC - a yradsitck
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/deciision/decision/ Found Scribe: fesch Inferring ScribeNick: fesch Present: Tzviya_Siegman Joanmarie Fred Rich Regrets: Shane Cynthia Michael Michiel WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 12 Aug 2015 Guessing minutes URL: http://www.w3.org/2015/08/12-pf-minutes.html People with action items:[End of scribe.perl diagnostic output]