See also: IRC log
<scribe> Scribe: EricE
<scribe> scribenick: yatil
<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_F2F_November_2016
Brent: We needed to make a
decision on weather we wanted to have a meeting coinciding with
Accessing Higher Ground in Westminster, CO, USA.
... The dates are Monday & Tuesday, 14-15 November. During
pre-conference.
... No concrete agenda yet, but we will look at the options for
the group present.
... Please visit this page and make sure your participation is
accurate.
... If you can’t go, you don’t need to do anything but if
you’re unsure please give us a percentage how likely it is to
participate.
Shawn: Wondered if we got Chris before buying airline tickets.
Chris: Yes, it is in time.
Laura: I did not get approval to go, unfortunately.
Brent: Thanks to everyone for putting information in. Any other comments?
Brent: A bit of a shift for the updates…
Brent: Send to the planning
group, I started working on my Github repository but ran into
some issues when editing the document. Do I do a fork, or do I
edit the HTML document directly. As there are some resource
managers here that need support, we will talk about this later.
I am ready to update the content, but want to do it the right
way.
... Hope to do some of the edits during next week and bring it
to this group next Friday or the Friday after.
... Questions?
<Brent> Evaluation Reports resource: https://www.w3.org/WAI/eval/template.html
Howard: I did update the planning
document template for accessibility evaluation reports.
... I uploaded it to GitHub and sent it to the planning group
last night.
... I also started editing the actual resource, same questions
as Brent. Forked the version in GitHub and first cared about
the low-hanging fruit, changing WCAG 1.0 to WCAG 2.0
references. I also wasn’t sure if I was “allowed to edit it”
before getting the OK from the planning meeting.
Brent: Previously W3C staff did a
lot of that work, but now there is more work on the resource
managers. And there are a lot of questions on how to do stuff
the right way.
... Recap for this: It did not have a requirements analysis,
and Howard created one, worked in Shadi’s feedback. As long as
that stuff is worked in, it is OK to go on with editing
this.
Shawn: Where do I find the requirements analysis?
Howard: Was attached to an email and uploaded to Github as a doc.
<Howard> https://github.com/w3c/wai-eval-report-templates
Brent: Any other questions?
<Howard> You should be able to find the requirements doc at the above url
<Brent> Referencing and Linking resource Link: https://www.w3.org/WAI/intro/linking
Laura: Sent my original comments to the planning group, got feedback from Brent, Eric set up Github repository. I’m comfortable with the HTML, as I do it every day. My questions are similar to Howard’s. Should I edit the file directly or propose a file change?
Brent: Looks like doing process overview/training seems to be good timing.
<Brent> Policies Relating to Web Accessibility (Mary Jo)
<Brent> Accessible UI Components List (Eric)
<Brent> Developing Web Accessibility Presentations and Training (Andrew)
<Brent> Easy Checks - A First Review of Web Accessibility (Caleb)
<Brent> Mobile Accessibility (Susan)
<Brent> (Draft) Tips for Getting Started with Web Accessibility (Denis)
<Brent> Web Accessibility Tutorials (Eric)
<Brent> Planning & Managing related resources (Shadi)
Brent: Next week is TPAC, I will
be back on Thursday evening and will make the EO meeting. Won’t
be at the planning meeting as I’m traveling and Shadi, Sharron
and Eric are still at TPAC. Shawn volunteered to take it up and
collect the feedback during the planning meeting time.
... So if you have anything, please feel free to bring it up
with the planning group.
Shawn: For the WAI site redesign,
it is interesting to identify the top tasks that people do on
the website. From the 2005 redesign, we have a long list of
tasks and a nice matrix. We now want to have a shorter list and
pick the top tasks.
... Going over the tasks from 2005 and identify what the top
tasks are. Anyone up to lead that project?
Joy: I can try to help.
Chris: I might be able to help if
we can split the responsibility.
... What’s the timeline?
Shawn: I think the most important thing is to go through the tasks and identify what the top tasks are. I wonder what your availability is?
Chris: I have quite limited time next week.
Shawn: It would be great to have
some top tasks next week.
... It would be great if we could bring something to the survey
next week.
Joy: Where would we find the list?
Shawn: See agenda.
Chris: I think it is feasible to identify the top lists.
Shawn: Would be good to have
double the amount we need to give people a choice.
... Thanks for taking this up, Chris & Joy.
https://www.w3.org/2002/09/wbs/35532/EO-Weekly-9-Sep-2016/results#xq2
<Brent> Eric: Survey results about scrolling behavior on Quickref shows that majority of people would like to provide two options, On and Off for scrollling
<Brent> Eric: Have implemented that in the Quickref draft on GitHub.
http://w3c.github.io/wai-wcag-quickref/?currentsidebar=%23col_customize
<Brent> Eric: Propose resolution to roll out solution of On/Off preferences for animated scrolling.
<Chris_langston> no concerns!
<James> +1
<Chris_langston> +1
<laura> +1
<Brent> +1 to On/Off
<Howard> +1
<shawn> +1
<shawn> +1 Joy
+1
RESOLUTION: Implement and publish On/Off preferences for animated scrolling in the How to Meet WCAG 2.0
Brent: So, what is the actual
workflow when you start to edit a document, like do I directly
edit the index.html document, or do I submit a pull request.
I’ll share my screen.
... Many people are not really familiar with Github.
... If you are the RM you don’t need to be the editor, but you
can manage an (or more) editors.
... Just because you’re not a technical person that doesn’t
mean that you can’t be a RM, but you can have an editor that
takes care of the technical stuff.
... This is the repository for the WCAG overview page. There is
a readme file and an index.html
... file. I don’t know what I need to do to make the
change.
... Also I have the github version of the version
rendered.
... My question was: What am I supposed to do? I know that I
can click on the index.html and edit the file but do I need to
fork it.
Shawn: Basically you edit the
HTML file. There is a couple of different ways to do it. If you
do a lot, you can use a tool like Github Desktop and do changes
locally.
... If you click on the index.html you can edit it. You can do
it directly here, but you can also use a separate editor.
... If you click on the Edit button, you can edit it. There is
a code editor, you can change the wrapping to soft wrap.
... If you are in the code area, you can search for code, for
example h1
... Using CTRL+F or CMD+F
... If you do this little one, you can make the change. On the
bottom there are two boxes where you can put a heading and then
a longer description.
Brent: Then there are two
buttons: Propose file change and Cancel.
... Clicked Propose
Shawn: Then there is another step.
Brent: This is a comparison view, on the top of the page there is a button “create a pull request”.
Shawn: The question is if you are making changes do you do it on a fork or do you submit it to the main version directly.
Brent: So am I actually editing the file directly or needs everything approved?
Eric: I think we will think about
that.
... You need to do pull request for every change.
Laura/Howard: Can you clarify?
Eric: <clarifying>
Brent: So I clicked the [Create
Pull Request] and here I can edit the title and add a longer
comment. Again clicking [Create Pull Request].
... This goes back to the pull requests on the w3c/xxx
repository. I can see that pull request, but I can’t do
anything.
... Shawn said that in that instance she would comment on the
repository.
Shawn: I added the comment, the
page refreshes automatically.
... In that case we would follow up. Most pull requests is
probably just accept, accept, accept.
... But in this case there would have been a discussion. As a
contributor you can say “see you point” and close the
issue.
... Or we discuss more and bring it to the group
eventually.
... You can then close the pull request.
... It is now a closed issue.
Eric: You can’t delete pull requests all together. But you can refer back to them in later conversations.
Howard: If you make an edit, it is automatically forked, right?
<shawn> +1 for making lots of small changes!
Eric: Right.
Laura: I wonder if it is better to make small changes or larger changes?
Shawn: Yes, smaller changes is better. And have more pull requests.
<shawn> Eric: usually short, small things. You can edit an existing pull request...
<shawn> +1 for Laura for great qustion to clarify for all !
<Zakim> shawn, you wanted to ask about rendered version of fork
Howard: Just to clarify: If I change five typos and do that in one edit, and one is not a typo, I can make changes.
Shawn: Brent had changes about how to preview a rendered fork.
Eric:
w3c.github.io/repository-name
<shawn> two ways:
<shawn> to see fork in your own account:
yourusername.github.io/repository-name
<shawn> another way to do ti: rawgit.com
<shawn> from github, index.html - copy URI - rawgit.com - past URI - then copy "URL for development"
<shawn> & paste in a browser
Brent: Where do I find my fork?
Eric: You find it from your profile or by clicking forks on the top right.
Brent: Any way to use another name than the generate ”patch-1” name?
Eric: Not that I know of.
<shawn> Eric: committing is saying these are my changes for my own repository. then pull request is saying I'm proposing this change to the w3c main repository.
<shawn> Shawn: Thank all for working with GitHub! Overall, I think helpful for EOWG working together. We'll keep learning and refining how we use it in EOWG.
Brent: Light survey this week.
Will be a question about the F2F meetings in 2017.
... Budgets are usually submitted the fall before, so we are
trying to do to lock in the meeting schedule for 2017.
... I worked on a draft survey question with possible locations
for 2017. Getting some feedback from you to determine who can
be where. We aim to have a tentative/committed schedule for
2017 instead of figuring it out on the fly during the
year.
... This might also help to get travel budgets.
... I will update the Work for this Week as well for this
question. Any questions on that topic?
(nothing)
Brent: Any other business we need to discuss?
trackbot, end meeting
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/ine/ine?/ Succeeded: s|Laura: C|Laura/Howard: C/| Succeeded: s/@@// Succeeded: s|C/an|Can| Succeeded: s/…Any other/Brent: Any other/ Succeeded: s/ (5 minutes)// Found Scribe: EricE Found ScribeNick: yatil Default Present: Shawn, Brent, Chris, Laura, Joy, Eric, Howard, James Present: Brent Chris Eric Howard Joy Laura Shawn James Regrets: Denis Shadi Andrew Susan Sharron ?Sylvie ?Kazuhito Found Date: 16 Sep 2016 Guessing minutes URL: http://www.w3.org/2016/09/16-eo-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]