<shadi> scribe: Brian
<shadi> scribenick: Brian_Bors
Wilco, explains to me how to scribe
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/515
<Wilco_> https://www.w3.org/TR/act-rules-format/#background
Wilco, the new format demands more than just links, it needs an explanation to why the link is relevant, we currently don't do that.
<jon_avila> what is the WebEx password?
Wilco, a solution to this would be to add a little explainer before the links
<jon_avila> thanks
Anne, asks about other things than links to WCAG techniques, should we have a section for that too?
Wilco, suggests a miscellaneous section
Wilco, and Brian will work on a proposal for the explainer texts
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/467
Audrey, explains the issue and the suggestion. The suggestion is to only write in a positive form to reduce ambiguity.
<Wilco_> https://act-rules.github.io/rules/2779a5
<Wilco_> https://act-rules.github.io/rules/2779a5#expectation-2
Anne, also notes that the human brian has problems with picking up the word "not"
Audrey, and Jey will work together on working on rewording the rules
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/476
Wilco, asks the group what the highest priorities are on the TODO list
Anne, mentions that getting the website accessible should probably be a priority
Shadi, Currently we are mainly concentrating on the information architecture instead of the visual design
Jey, will got to the list next week and will prioritise accessibility issues and some other things
Wilco, the aim is to get this done by the end of the month
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/472
<Wilco_> https://github.com/act-rules/act-rules.github.io/pull/488
Wilco, FYI: there is an open pull request to get the rules up to speed with the new format
Anne, Kaspar has promised to write some guidelines to write PR comments so those can be scraped to generate a changelog. That has not been done yet, but we should also write code to scrape that and that will be more work. Wilco and Kaspar will communicate about this next week.
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/546
<Wilco_> https://act-rules.github.io/rules/5b7ae0
<Wilco_> https://act-rules.github.io/rules/5b7ae0#inapplicable-example-3
Wilco, correct implementations of the rules requires that test cases produce the same results which would be hard to do because some of the test cases don't comply to WCAG. We have passing or inapplicable test cases that don't sattisfy the SC they are testing.
Wilco, the proposal is to write passing and inapplicable test cases that pass the SC and to write failed test cases that only fail the test they are depicting, not a second one.
<jon_avila> I agree with Wilco's comments on fails/passing aligning and failure test cases should be clear on failure
Shadi, and Brian don't completly agree with Wilco and made some arguments
Anne, and Jon Avila agree with Wilco and make some arguments for it
How do I stop this scribing process?
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: Wilco_ Audrey Brian Jey John Shadi Found Scribe: Brian Found ScribeNick: Brian_Bors 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]