<scribe> scribe: Sukriti
sh: should we meet Jan 6 or also sometime in the next 2 weeks
sc: Jan 6 with asynchronous tasks for the meantime
todd: will be gone from Dec 28 to
5
... 5 Jan
sh: let's do next meeting Jan 6
and async work in the meantime
... I will still work tomorrow and available on the chat
sh: formal structured scope statement
<sarahhorton> https://www.w3.org/WAI/GL/task-forces/silver/wiki/Error_Handling#Project_Definition
<sarahhorton> Link to the scope statement work description: https://public.3.basecamp.com/p/z24UZtTAFrMqUxgm2To27NsW
sh: any questions on the scope or
charter?
... deadline is Jan 8 for presenting
sc: Is it going to deviate from the initial plan?
st: concern was that the scope
was too broad
... because our scope included preventing errors
... sarah and charles pointed out that we are focused on
preventing errors so we don't just focus on when you've made
the error
sh: lots of different ways to
manage errors
... would rather start with a broader scope and narrrow it
down
... would need something succint
st: I could write a first draft
RESOLUTION: Suzanne to write first draft, share on basecamp and present on Jan 8
sh: continue to use the error flow inventory as inspiration for the guidelines document
sh: adding screenshots of error flows in the screenshot document
<sarahhorton> Error User Needs Worksheet: https://docs.google.com/spreadsheets/d/1BEzSKUsoMQZAwLY5uM5T4Jk7vqKruQT8EaheijQJ7nk/edit#gid=0
sh: notion of an action, outcome, which functional needs and which accessibility needs apply
<sarahhorton> Errors User Needs Summary: https://docs.google.com/document/d/1mTrr0hSsQrApmC4N0tF4fQOF-PiLsK-FNZproi7WQcA/edit#
this document takes the flows and surfaces user needs and unique needs
sh: within an action, there might be multiple outcomes
st: do we have new error flows, should we be filling them out in the inventory document or in the sheet?
sh: at some point we will become
more targeted but still good practice to add in the inventory
document
... maybe not is too much detail but just so we have them
accounted for
st: how will this inventory document translate to the sheet?
sh: rich source of content in the inventory document when it comes time to write the guidelines
st: add different user needs if we come across new ones in a more distinctive ways
sh: add screenshots and small notes on error flows we come across in the wild
sc: next action item?
sh: action-outcome and grouping
them with the system action
... walking through an example of how to map them
... will finish error messages
someone could take input labels and instructions
sh: I will make the sheets with 2
examples each
... we can each then take a sheet
sh: how about the end of Jan to have the summary ready to share with the task force - Part 1. Define user need
st: is it supposed to be in a
publishable format or a working document
... longer approach or the more aggressive schedule?
... March?
... right now it's brainstorming, but we'll have more
debate
sh: our task is to get it to the
first public draft so we can collect those opinions
... end of june for everything?
... of error related guidelines
... June it is!
<SuzanneTaylor> rssagent, make minutes
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) Default Present: sarahhorton, Sukriti, ToddLibby, SuzanneTaylor Present: sarahhorton Sukriti ToddLibby SuzanneTaylor Found Scribe: Sukriti Inferring ScribeNick: Sukriti 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.)[End of scribe.perl diagnostic output]