W3C

Accessible Rich Internet Applications Working Group Teleconference

03 Feb 2016

Agenda

See also: IRC log

Attendees

Present
Joanmarie_Diggs, MichaelC, Tzviya, Shane, Michiel, Matt, fesch, Joseph_Scheuhammer, JamesN
Regrets
Chair
MichaelC
Scribe
MichaelC

Contents


<scribe> scribe: MichaelC

<scribe> meeting: ARIA Editors

agendum 3 = Glossary stuff https://github.com/w3c/aria/issues/106 and https://github.com/w3c/aria/issues/76

Publication timeline check

last: https://www.w3.org/2016/01/20-aria-editors-minutes#item02

same as last time

but also add ARIA practices

some issues in AccName might not be done, but still ok to publish

Restructuring repository repeat (see https://www.w3.org/2015/12/16-pf-editors-minutes.html#item01)

<ShaneM> Needs a quiet time...

MichaelC forgot to do this in Dec

could do 12 Feb

or 19 Feb

or with next publication cycle if we´re all hands off

make sure to send the hands off mail to people individually

let´s do at time of next heartbeat publication

<Zakim> clown, you wanted to ask how this affects urls that currently reference the things to be moved?

what about impact on rawgit URIs

also might cause us to look at github.io URIs

<scribe> ACTION: cooper to see if it´s possible to set up redirects when github resources change location [recorded in http://www.w3.org/2016/02/03-aria-editors-minutes.html#action01]

<trackbot> Created ACTION-2010 - See if it´s possible to set up redirects when github resources change location [on Michael Cooper - due 2016-02-10].

Glossary stuff https://github.com/w3c/aria/issues/106 and https://github.com/w3c/aria/issues/76

we have common terms from which we include

it´s winnowed to only include terms used in that doc

a bug is that if I ref term A, and it refs term B but nothing else does, term B doesn´t get included though it needs to be

I have a fix, but don´t want to perturb anything

there´s enough lead time to next pub cycle that we could play with it now

<joanie> https://github.com/w3c/aria/pull/112 ?

SM will put in fix

can review rawgit of branch? yes

Pull request vs branch

<MichielBijl> +1 to branches in main repo

<MichielBijl> Makes rebases easier too

Joanie suggest editing in branch in main repo, rather than in branch of private repo followed by pull request

people can review in the branch

easy to merge into master

find it easier than dealing with pull requests

it is possible to comment on lines in a pull request

but that may be possible on individual commits anyways

general consensus we prefer to use branches instead of pull requests

allow pulll requests for outside contributors

Horizontal rules between sections https://github.com/w3c/aria/issues/228

In the ARIA spec there are <hr> between each section

suggests a thematic change, but <section> elements do that intrinsically

<Zakim> ShaneM, you wanted to discuss the new stylesheet

we may have had a reason before, but not clear we need it

the new TR CSS does this stuff for us

we shouldn´t add the styling

general consensus we can remove those

editors, please do for your own specs

AOB

MB has done some indent fixing in APG

question about line wraps

https://www.w3.org/2016/01/06-aria-editors-minutes.html#item05

some of us prefer one line per para, easier to edit text

others like shorter lines

this may be very much the preference of specific editors, so perhaps shouldn´t impose a repo-wide rule, leave it to each spec

<MichielBijl> https://github.com/w3c/aria/blob/master/practices/aria-practices.html

<MichielBijl> Sorry: https://github.com/w3c/aria/blob/master/practices/aria-practices.html#L185

shorter lines make diffs easier to use

<jamesn> +1 to that too - I like short lines too.

a middle approach is one *sentence* per line

<tzviya> +1 I like short lines, but i use a tool that allows me to adjust the settings as I prefer

<ShaneM> I checked in a branch shane-glossary with the fixed resolveReferences method.

for now, no repository wide rules

do what you want for your spec, coordinate with other editors if needed

will bring up again when we do a version update

Next meeting

Next meeting is Feb 17 2016 at 1:00 pm Boston

<scribe> meeting: ARIA Editors

<scribe> Meeting: ARIA Editors

trackbot, end meeting

Summary of Action Items

[NEW] ACTION: cooper to see if it´s possible to set up redirects when github resources change location [recorded in http://www.w3.org/2016/02/03-aria-editors-minutes.html#action01]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/02/03 18:36:07 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Default Present: Joanmarie_Diggs, MichaelC, Tzviya, Shane, Michiel, Matt, fesch, Joseph_Scheuhammer, JamesN
Present: Joanmarie_Diggs MichaelC Tzviya Shane Michiel Matt fesch Joseph_Scheuhammer JamesN
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2016Feb/0000.html
Found Date: 03 Feb 2016
Guessing minutes URL: http://www.w3.org/2016/02/03-aria-editors-minutes.html
People with action items: cooper

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]