RE: Even for Note-track? Re: CFC - Standing permission to publish Working Drafts of COGA Gap Analysis

I think it would help the document editor(s) to make discrete changes and then commit each change to the GitHub branch with a suitable commit message. The change log can then be constructed from the "git log" commit history.

This requires discipline, but it's easier than finding and summarizing changes after the fact.

> -----Original Message-----
> From: Michael Cooper [mailto:cooper@w3.org]
> Sent: Friday, February 2, 2018 11:28 AM
> To: tink@tink.uk; Andrew Kirkpatrick <akirkpat@adobe.com>; WCAG <w3c-wai-
> gl@w3.org>
> Subject: Re: Even for Note-track? Re: CFC - Standing permission to publish
> Working Drafts of COGA Gap Analysis
>
> My personal view is that a link to github commit history is sufficient to meet the
> spirit of the Process document advice James referenced. For Rec-track stuff I
> support going further with practices that have emerged. That said, if it's the will
> of the WG to require an actively managed change log in order to feel
> comfortable giving standing publication consent, then that's the WG decision. I
> manage the change log for WCAG 2.1, and it's a lot more work than it seems, so
> I am *not* prepared to take that on for the COGA gap analysis. We will need to
> ensure that the document editors accept this responsibility. Once we sort that
> out hopefully we can move forward with a decision. Michael
>
>
> On 02/02/2018 6:54 AM, Léonie Watson wrote:
> >
> > On 01/02/2018 22:43, Michael Cooper wrote:
> >> I need to point out that the COGA Roadmap and Gap Analysis is not a
> >> spec - it's a Note-track document. Therefore I don't think it should
> >> be held to the practices of specs. Change logs are great in specs,
> >> and in ARIA we use them even without standing consent to publish on
> >> the books. But Note-track documents are often edited in less discrete
> >> chunks than specs, making it hard to make a meaningful change log. To
> >> ensure there is WG review, we explicitly plan for review opportunity
> >> and explicit WG consensus before transition to Note status, so I
> >> don't think things will sneak past the WG long-term. It is certainly
> >> possible to put a link to the github commit  history in the document,
> >> which people who really want to track its evolution can use. But if
> >> the WG doesn't support a standing consent to publish over this issue,
> >> the TF will have to ask for WG approval every time it wants to
> >> publish a draft, which will be more burden on all of us and more
> >> bureaucracy than I feel is needed for a Note-track document.
> >
> > Without a changelog you're expecting WG members to be able to identify
> > what's changed between one WD and the next. If, as you say, the
> > changes in this case are in "less than discrete chunks", that means
> > it'll be even harder to quickly review what's changed.
> >
> > The changelog doesn't need to be complicated. It just needs to be a
> > list of high level changes, plus links to the relevant Github commits.
> > For example:
> >
> > "Section X updated to include Y + [link to Github commit]".
> >
> > That way someone can review the changelog and decide whether they want
> > to review the change in detail (using the commit log), or not.
> >
> >
> > Léonie.
> >
> >>
> >> Given all that, is it really needed to have a change log in this
> >> Note-track document to get consent for standing Working Draft
> >> publication authority?
> >>
> >> Michael
> >>
> >>
> >> On 01/02/2018 1:12 PM, Léonie Watson wrote:
> >>> -1
> >>>
> >>> In the absence of a CFC that summarises the changes between updates,
> >>> there needs to be a changelog in the spec that makes it easy for WG
> >>> members to ascertain what's changed for themselves. Currently the
> >>> spec doesn't have such a thing.
> >>>
> >>>
> >>> On 01/02/2018 17:15, Andrew Kirkpatrick wrote:
> >>>> Call For Consensus — ends Monday February 5th at 12:30pm Boston time.
> >>>>
> >>>> The AGWG discussed a decision to grant standing permission for the
> >>>> COGA Task Force to publish updated working drafts of their Gap
> >>>> Analysis.
> >>>>
> >>>> The First Public Working Draft (FPWD) of their Gap Analysis is
> >>>> available here:
> >>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

> >>>> w.w3.org%2FTR%2F2017%2FWD-coga-gap-analysis-
> 20171207%2F&data=02%7C0
> >>>>
> 1%7Cjjwhite%40ets.org%7Ce8ae1ab0cacf486a218c08d56a5a0abe%7C0ba6e9b
> 7
> >>>>
> 60b34fae92f37e6ddd9e9b65%7C0%7C0%7C636531857316045835&sdata=WJa1
> zUQ
> >>>> NmGScXUIhyURJ5H5KkxsMV4Sko98HzDgynpQ%3D&reserved=0
> >>>>
> >>>> Please note there is a concurrent CfC on this same question in the
> >>>> Accessible Platform Architectures Working Group (APA WG). Members
> >>>> of both groups are asked to respond on both CfCs.
> >>>>
> >>>> Call minutes:
> >>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

> >>>> w.w3.org%2F2018%2F02%2F01-ag-
> minutes.html%23item01&data=02%7C01%7Cj
> >>>>
> jwhite%40ets.org%7Ce8ae1ab0cacf486a218c08d56a5a0abe%7C0ba6e9b760b3
> 4
> >>>>
> fae92f37e6ddd9e9b65%7C0%7C0%7C636531857316045835&sdata=ei%2FX2RJ
> D%2
> >>>> FNev10v7jVW5rCElgH9jfaaLZk6ScsFMy8k%3D&reserved=0
> >>>>
> >>>> If you have concerns about this proposed consensus position that
> >>>> have not been discussed already and feel that those concerns result
> >>>> in you “not being able to live with” this decision, please let the
> >>>> group know before the CfC deadline.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> AWK
> >>>>
> >>>> Andrew Kirkpatrick
> >>>>
> >>>> Group Product Manager, Accessibility
> >>>>
> >>>> Adobe
> >>>>
> >>>> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
> >>>>
> >>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwi

> >>>>
> tter.com%2Fawkawk&data=02%7C01%7Cjjwhite%40ets.org%7Ce8ae1ab0cacf4
> 8
> >>>>
> 6a218c08d56a5a0abe%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7
> C636
> >>>>
> 531857316045835&sdata=nBBaCl55UcqSLOUM4poNqs6UpXxmyF8EGiCniSKyigI
> %3
> >>>> D&reserved=0
> >>>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftw

> >>>>
> itter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd
> 66c
> >>>>
> 05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786
> 436&
> >>>>
> sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=
> 0
> >>>> >
> >>>>
> >>>
> >>
> >
>


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Friday, 2 February 2018 16:35:01 UTC