See also: IRC log
<scribe> Scribe: Sarah
<jeanne> [Sarah reviews the methods she added to the Process Options doc]
<jeanne> https://docs.google.com/document/d/1irMybNoo-yUaUlEoo4beqIkTX7MUmyBX4b2eqZNjfR8/edit?usp=sharing
Shawn: Expand on Production and Evolution
Jeanne: Hiring an editor for the
spec, was successful in HTML 5
... Find way to broadly crowdsource creation of spec, look at
HTML 5 model
... Hold workshop for people to work in small groups to craft
spec
... W3C face-to-face meeting, take chunks of spec, write it,
and present to group
... Given individuals in working group responsibility for
sections of spec, manage them, hold to writing section on
timeline
... First step is take results of experimentation and turn into
requirements doc
Shawn: One goal of experimentation must be requirements
Jeanne: Requirements must include structure and basic outline of Silver
Shawn: Experimentation helps us
determine what structure should look like
... Structure and Scope
Jeanne: Requirements document is what we're commiting to doing
Shawn: Interpretation phase, clarifying objectives, turn data into actionable insights
Jeanne: Considerations and recommendations that we can use for the ideation phase
Shawn: Adding to objectives, looking at structure and substance of Silver
Sarah: Choose a subset of viable options for prototyping
Shawn: We can have implementation
plan generally defined from start
... At TPAC we can have high-level implementation plan included
in proposals
... We should look at HTML5 in the discovery phase, secondary
research
... Method for Production and Evolution, break down
milestones
... Let's go through matrix and rate other methods, process
options
Sarah: Need to have grouping activity after inventory
Will do, thanks!
[Sarah and Shawn rank methods]
https://docs.google.com/spreadsheets/d/1C4Wqf-g-0X_HqbJ-4euFS_U0xEISnURnilV6TJk7FQs/edit?usp=sharing
Sarah: Having an editor for spec is high across the board
<jeanne> Jeanne: We will have to have an editor, but the options become how much time that editor can devote to the spec. If that editor is fulltime devoted to the spec and authorized by the WG to write sections of the spec following the requirements, that has a very high cost.
Sarah: Faster progress approach also requires building consensus, what activities work best for building consensus?
Jeanne: What about having a track at a11y camps/conferences for the ideation activities?
Sarah: What are ways to choose options?
Jeanne: Subgroup selects based on report in interpretation phase
Sarah: Quick and dirty feedback (desirability testing — positive, neutral, negative)
Jeanne: This method can be good for gathering feedback and making progress
Shawn: With choosing, need option for voting that will make for faster progress: added subgroup's choice
Jeanne: Add "forming official
taskforce" to production because then companies can assign
people, would have structure of other taskforces
... Can ask companies to donate people as fellows
... Helps to get companies to give more time
... Writing workshop can be good, people are face to face,
people aren't distracted, meet deadlines
<scribe> ACTION: Jeanne to create wiki page structure for process options [recorded in http://www.w3.org/2016/08/26-silver-minutes.html#action01]
Shawn: At TPAC, present series of process options with rationale, have structured conversation about options, will need half day
Jeanne: For presenting option, explain phases, methods
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/codt/cost/ No ScribeNick specified. Guessing ScribeNick: SarahHorton Found Scribe: Sarah Present: jeanne sarah shawn Got date from IRC log name: 26 Aug 2016 Guessing minutes URL: http://www.w3.org/2016/08/26-silver-minutes.html People with action items: jeanne WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]