<scribe> scribe: MichaelC
Repos have been split
https://www.w3.org/WAI/ARIA/contribute
lists them
common files in separate repo
not yet automated pushing to repos
don´t edit common files within each repo! do in aria-common repo
aria repo reorganized to reflect just one spec
the repos have Repo Manager and PR-Preview tools installed
https://labs.w3.org/hatchery/repo-manager/
also automated editors´ draft now happens with commits to master
may want to set up protected branches
in aria repo there are lots of stale branches, should remove
please check your branches if still needed
https://github.com/w3c/aria/branches
If you needed other branches besides master put into the split repos, let MichaelC know
Joanie will do the messy stuff
will be helpful for everyone to look through branches with their name on them and delete if no longer needed, so Joanie doesn´t need to guess
suggest setting up master and gh-pages as protected branches
so only editors can commit
other WG participants could work in other branches and request merge
which editor does when approved
also need to protect stable branch
documents inadvertently published under software and document license since June 2017
due to Respec unannounced change
now made config change to switch back to proper license
published documents should be edited in place
increasing frequency of changes to respec that break something about our workflow
we talked about snapshotting respec so we´d know what the features of that snapshot are; do we want to come back to that?
maybe ask respec to switch to a stable / unstable work mode so the stable one has less of the surprises and more vetting of what´s in there
alternatives? mainly Bikeshed https://tabatkins.github.io/bikeshed/
otherwise, custom tool, no tool just manually it all, create a new general-purpose tool
fork or snapshot respec
probably living with it, forking / snapshotting, or switching to bikeshed are the main viable options
submitting pull requests to enhance respec also an option, if we have people with the skillset
master is the ¨unstable¨ branch
but content in it is supported by WG consensus
and editors´ draft snapshots come from that
content isn´t stable until there are tests, mappings, etc.
at which point it moves to ¨stable¨ branch
from which WDs published
other branches are working branches, from which content merged into master upon approval
version number branches contain the content that is finalized as Rec for that version number
only set up upon finalization
which we could set up as a ¨release¨ annotation
Next meeting: 7 February 2018 (3 weeks)
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 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/me/MichaelC/ Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Present: JamesN MattK Joanmarie_Diggs MichaelC Found Scribe: MichaelC Inferring ScribeNick: MichaelC Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2018Jan/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]