W3C

ARIA Editors

22 Jul 2020

Agenda

Attendees

Present
MichaelC, Joanmarie_Diggs, Jemma, Matt, JamesN
Regrets
Chair
MichaelC
Scribe
MichaelC

Contents


<scribe> scribe: MichaelC

agenda order 1,2,3,4,6,5

Exporting definitions for aria-common

https://github.com/w3c/accname/pull/85

Respec feature to load definitions from other specs

The respec maintainers want us to use this feature

When you use a term, you can declare which spec to pull it from

Xref in respec

think you have to export terms to their shepherd database if you expect them to be reused

the pull request is against accname but may apply to aria-common

<jamesn> https://github.com/w3c/aria-common/pull/47/files

if we use the respec feature of adding the data-export attribute to terms we want reusable

then we could ignore the accname pull request

but it might link to the spec rather than pull it in

<scribe> ACTION: MC to prototype this to see what happens, and bring back to editors´ call

<trackbot> Created ACTION-2148 - Prototype this to see what happens, and bring back to editors´ call [on Michael Cooper - due 2020-07-29].

<Jemma> "Defines the terms to be exported in a variable definitions_to_export"

don´t wanna break anything though

and not sure what happens when a spec upversions

Neutral language in specs

https://lists.w3.org/Archives/Public/spec-prod/2020JulSep/0003.html

Pubrules will start warning on sensitive terms in specs

later may change to error and block publication

this is like alex js

https://alexjs.com/

<Jemma> Inclusion and Diversity Community Group

<Jemma> IDCG

also proposals to change the github ¨master¨ branch to ¨main¨

this has been encouraged but not required so far

may be non trivial in APG because of scripts built around branch names

will also need to update documentation

and may want redirects on rawgit URIs

considering our approved changes branch is ¨stable¨, maybe we want ¨unstable¨?

but most orgs seem to be going to ¨main¨

MC to implement in little-used repo first

do in accname, then discuss spreading to other repos next meeting

<scribe> ACTION: cooper to change “master” to “main” branch in accname and see what happens

<trackbot> Created ACTION-2149 - Change “master” to “main” branch in accname and see what happens [on Michael Cooper - due 2020-07-29].

New aria-at-app repo?

defer to August

1.2 CR

James still has work to do ;)

dotting i´s and crossing t´s with merges, documentation, etc.

will figure out if pending dependencies on APG

timeline pressure from management may start coming in a few weeks

Publication schedules

should do FPWD of 1.3

need a new branch of 1.2 off stable

then start using stable for 1.3

(need to work with work flow https://www.w3.org/WAI/ARIA/workflow)

let´s aim for 1.2 CR and 1.3 FPWD week of 31 Aug 2020

Next meeting

Next meeting: 5 August 2020

Summary of Action Items

[NEW] ACTION: cooper to change “master” to “main” branch in accname and see what happens
[NEW] ACTION: MC to prototype this to see what happens, and bring back to editors´ call
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/07/22 17:50:55 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Present: MichaelC Joanmarie_Diggs Jemma Matt JamesN
Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2020Jul/0001.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: cooper mc

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]