agenda order 3, 1, 6, 7
https://github.com/w3c/accname/issues/41
appears to have been sorted out in the issue
but we want consistency among the specs
support for that, but suggest doing it via include file
Respec has default RFC stuff
https://github.com/w3c/respec/wiki/conformance
but MC elected to not use at some point for some reason
<joanie> https://github.com/w3c/aria-common/issues/24
agree to harmonize the language, via a common include, circle back here when a proposal ready
CSUN is March 11 - 15
spec has new stuff by then
APG has templates to support new ARIA feature
needs time to write new practices content for things that land
anyways need practices stuff for stuff to land in stable, and therefore WD
MC still to split acknowledements
1 ack file for entire WG
in each spec, put in an acknowledgements section manually
inside it it load the WG ack file if desired for a sub-section
load any other common subsections we set up
do private subsections as standard HTML subsections
for APG, want a subsection for active contributors to that version
oh, and the enabling funders one is needed in all specs as well
https://www.w3.org/2019/01/02-aria-editors-minutes.html#item03
also a list of TF participants
MC to maintain files of WG / TF participants based on DBWG
https://github.com/w3c/aria-common/issues
we need someone to take over maintenance of the scripts
issues are stacking up, taking the current editors more time than desired to address
also could benefit from unit tests and regression tests
<joanie> https://github.com/w3c/aria-common/pull/23
<joanie> https://github.com/w3c/aria-common/tree/master/script
diffs with each commit to see the full impact would be helpful
also the support scripts arenĀ“t documented
JD could do some refactoring of the scripts
not sure how to integrate support for unit tests though
might be able to find someone to help port stuff from the APG regression tests to the common framework
JD and MC to investigate script refactoring
if we can find a javascript jock to come in and take over maintainer role for the aria-common scripts that would be great
otherwise, refactoring will make it more maintainable
we also want to consider the bus factor, others should be able to come in and be able to continue ARIA spec development
so documentation and tests will help
plan to publish 22 Jan
need the acknowledgements sorted!
CfC is out now
<Jemma> Michael will add the dates for former editors of ARIA APG.
<none>
Next meeting: 6 February 2019
3 weeks from today
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/contributors/participants/ Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Present: Jemma Joanmarie_Diggs MichaelC Matt Regrets: JamesN No ScribeNick specified. Guessing ScribeNick: MichaelC Inferring Scribes: MichaelC Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2019Jan/0002.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.)[End of scribe.perl diagnostic output]