Final report draft <- https://docs.google.com/document/d/1p3KDazY8nYb_5f-F8tHRfiKubHthXwxXa6wj2Riru0k/edit?usp=sharing
How should we let people know how to send prototypes?
Jeanne: There is a Next Steps section, I need to add text there
<scribe> scribe: jeanne
Shawn: Text to invite people, join the community group link, send the email link.
<Lauriat> Draft: Interested in helping contribute with prototyping? Join the Silver Community Group [linked] and reach out to the Silver Task Force at public-silver@w3.org!
Michael: There is a feature in Github that will be installed that will automatically flag any contribution where the creator hasn't signed off on the W3C royalty-free intellectual property agreement.
Jeanne: This helps ensure that no one comes back in a year or two and says that "I own this idea" and charge a fee. All W3C specs are royalty-free so that anyone can use them at no cost.
[minor wordsmithing of the phrasing of invitation]
<scribe> New phrase: Interested in helping contribute? Join the Silver Community Group and reach out to the Silver Task Force at public-silver@w3.org!
<kirkwood> YES
Jeanne: I will email the report
to everyone who attended the design sprint, then wait a day and
send it to the AGWG group.
... and move it to the community group and send a link.
... anyone else we invited to the Design Sprint but couldn't
make it/
Prototyping Project Plan <- https://docs.google.com/spreadsheets/d/10p-8-v-XqRllBaX_eTiXXvyyDYeft8GRiN3_11V3U0w/edit?usp=sharing
<Charles> I lost all audio
<kirkwood> lost audio
<Jan> tpac is in October this year
<Lauriat> 22-26 October 2018
Group reviews the project plan and adds items
Jeanne: Please keep in mind, that we need to start enrolling more people to participate to get all this work done. We need to change how we run this meeting, where the people on this call manage different sub projects, and this call becomes more of a reporting and assistance call for the people managing each group.
Shawn: HOw to start tackling
these things.
... who will work on each of the prototypes
... how do we manage the prototype and the work being
done
... how to do we manage the prototypes in github and the
issues
... how to manage the testing of each prototype
Jennison: DO we have a cutoff date for prototypes?
<Charles> Charles Hall has volunteered to: (1) Organize the Plain Language work; (2) Invite experts for IA work
Shawn: I think that we need to leave it open for a few months so we can continue to get ideas and refinement
Jan: Are we defining what the prototype is?
Shawn: I think it is an idea and some refinement
Jan: Are we giving them guidance?
Shawn: It's based on the research
and the Design Sprint results
... it needs to be based on "we need something that solves
[THIS]"
Jeanne: I think we need more than the Design Sprint report to communicate what we need
Shawn: We can set up different projects in Github.
<scribe> ACTION: Jeanne with Jennison to approach developers about creating accessibile interface to Github.
<trackbot> Created ACTION-169 - With jennison to approach developers about creating accessibile interface to github. [on Jeanne F Spellman - due 2018-04-24].
Jeanne: We talked about having people work on prototypes, and have the room be a drop in center for people to contribute and comment on prototypes.
<scribe> ACTION: Jeanne to contact Sharron about participating.
<trackbot> Created ACTION-170 - Contact sharron about participating. [on Jeanne F Spellman - due 2018-04-24].
see above.
Shawn: We met with Michael Cooper
at CSUN and brainstormed what should/could be in the
Requirements document
... we created this document of notes
... there are ideas to the Requirements documents, and links to
sample Requirements
Jeanne: The Requirements document
is an important part of the W3C process. When the spec goes to
Recommendation, then we have to show that we met the
Requirements document.
... Michael recommended that we write into the first draft that
we will revise the Requirements document after we finish the
prototype and after the first draft when we will get more
public comments.
Notes and thoughts about the Requirements document <- https://docs.google.com/document/d/15F4KuNXYK5q2rOgb4ktHiJQMQpAEL9EetARpMU3vD_A/edit?usp=sharing
trackbot, end meeting
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 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: Jan, Lauriat, MichaelC_, Luis_Garcia, kirkwood, JohnM, shari, Jennison, jeanne Present: Jan Lauriat MichaelC_ Luis_Garcia kirkwood JohnM shari Jennison jeanne Charles Found Scribe: jeanne Inferring ScribeNick: jeanne Found Date: 17 Apr 2018 People with action items: jeanne jennison with 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]