W3C

ARIA Editors

07 Dec 2016

Agenda

See also: IRC log

Attendees

Present
Joanmarie_Diggs, tzviya, scribe, Matt, Joseph_Scheuhammer
Regrets
Chair
MichaelC
Scribe
MichaelC

Contents


<scribe> scribe: MichaelC

Timeline check http://www.w3.org/WAI/ARIA/project

DPub CR now planned for 15 Dec

MC to send transition request today

AAMs for Jan still lookng possible

just need a bit more of the input to roll in

Seems ok according to https://www.w3.org/WAI/ARIA/project for now

Upcoming holidays, work plan

last two weeks of Dec tend to be dead

any coordination needed?

<silence>

Update on common resources

MC asked for github specialist

no luck yet on getting submodules to show in rawgit

but pointer on how to build static snapshot using the submodule resource

what if we do that, so editors drafts work, but rawgit URIs don´t come up formatted?

MCK: there are many people who need to be able to review branches

without special setup

so this would be a big barrier

Practice is working, but because we forked the common files

how often do we update common?

MC: semi regular, for MC and Shane

MCK: but just a couple people

could be simple to push changes to the forks

JD: is issue something which cannot be done, or something we simply don't yet know how to do?

<jamesn> https://github.com/rgrove/rawgit/issues/28

MC: seems not possible ATM

JD: could it be implmemented?

MC: appears to have been raised 2 years ago, maintainer agreed, but needs GH feature that seems not to have been taken up

MCK: we just need to know not to edit our common forks / reject pull requests against those in the repos

put in readme that edits have to be done in the common repo

MC: seems like this unsticks us on the repo split

JS: we could put our scripts in the W3C scripts location

MC: yes, for mapping-tables.js; the others are too specific to our docs IMO

Branch protection

MC: learned of GH feature to protect key branches

allowing us to give more people access to create branches

interested?

in practice, same effect as pull request from a fork

MC: forks can be hard to keep up to date

or have pull request from wrong branch

MCK: doesn´t effect editors :)

JS: Just ability to make branches is needed

MC: includes master unless we invoke branch protection

JS: then trust people to do the right thing :)

MCK: advantage would be other people could pile in on the proposal branch

MC: let´s handle repo by repo after split, can invoke branch protection or just give people access

core editor of each repo should have decision; have been conservative in big repo because so many affected

Testing update

test files in ARIA repo from a year ago at least

that is now OBE

AOB

none

Next Meeting

Next meeting is 4 January 2017

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/12/07 18:38:41 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
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
Present: Joanmarie_Diggs tzviya scribe Matt Joseph_Scheuhammer
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2016Dec/0000.html
Got date from IRC log name: 07 Dec 2016
Guessing minutes URL: http://www.w3.org/2016/12/07-aria-editors-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]