<scribe> scribe: MichaelC

Zakim, start meeting

https://www.w3.org/2001/12/zakim-irc-bot.html#startmeeting

replaces trackbot, start meeting command

Automatic review assignments

https://lists.w3.org/Archives/Public/public-aria-editors/2019Dec/0007.html

consider using automatic review assignments

to spread the load and make sure we get sufficient review of PRs

look for 3 approves before merge

would we want round robin or load balance?

would need to decide who would be in the reviewer group

look at reviewers in past month?

let´s set up for ARIA repo

Systematizing versioned cross references

want to think about a script to make sure the specs reference the same versions as each other

e.g., make sure ARIA 1.2 uses [[WAI-ARIA-PRACTICES-1.2]]

Automatic TR publication

Can automatically publish to TR upon commit to a given branch

e.g., stable

(for Working Drafts)

<Jemma> I think it is like having the stage server.

<Jemma> branch - stable - master

let´s set up for aria and core-aam repos for now

Status of moving APG off TR

<Jemma> https://www.w3.org/2019/12/18-waicc-minutes.html

need first to get aria-at project hosted

<Jemma> "Matt_King: 6 different screenreader and browser combinations. Currently you go the example itself; the documentation; a table for roles; states properties, etc; the source code for the example.

<Jemma> ... what we will be a adding is a table that will include support information. Not sure exactly what that will look like but it will get aggregated into a single number or 2-3 numbers.

<Jemma> ... The main question is could we solve high level problems and support upcoming integrations by hosting the authoring practices within the website as a section of the website with its own navigation and architecture? I don't want to make content changes.

<Jemma> <jamesn> +1 to all of this

<Jemma> I think this will open the door to serve multiple audiences and needs. Start consolidating some of the accessibility resources. Just being able to authoring practices that is user friendly and solves versioning problems."

MCK to work with MC on setting up hosting in W3C

drop item 6

Stumbling on old versions

if people search for APG, they get sent to 1.1 version

whereas there is 1.2 version out there

note that versionless URI takes latest version

in CR or higher

Removing old editors drafts

<jamesn> https://www.w3.org/WAI/PF/aria/states_and_properties#aria-selected

we could set up redirects of old editors´ drafts to current editors´ draft URI

Adding "outdated" note to ARIA 1.0 Recommendation?

<jamesn> https://www.w3.org/TR/wai-aria-1.0/

Want to mark ARIA 1.0 as superseded

and UAIG

and APG 1.0

(which is retired or something)

Next meeting

Next meeting: 5 February 2020

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)

Succeeded: s/haveing/having/
Succeeded: s/agendum 5. "Status of moving APG off TR" taken up [from MichaelC]//
Default Present: MichaelC
Present: MichaelC Jemma Joanmarie_Diggs Matt
Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2020Jan/0006.html

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.)