Re: Errata for Touch Events?

On 10/6/14 12:53 PM, Patrick H. Lauke wrote:
> As Matt pointed out that this is the place to discuss this, more 
> focussed question to the CG: how do we work on this? Do we discuss 
> things on the list first, or is there a bugzilla instance we use, or...?

The Web Events WG (WEWG) used Tracker for Touch Events Issues/Bugs (not 
Bugzilla). That Tracker instance (as well as the WEWG's wiki) were set 
to read-only mode when WEWG closed. I don't recall this CG agreeing on 
an issue/bug tracking mechanism per se, thus the default to this list 
and the touch-events hg repo.

With respect to working on both errata for the v1 REC and TE extensions, 
there is a branch for each:

[1] v1 REC errata 
<https://dvcs.w3.org/hg/webevents/raw-file/v1-errata/touchevents.html>.

[2] Extensions 
<https://dvcs.w3.org/hg/webevents/raw-file/default/touchevents.html>.

[ProcDoc] defines REC errata `management` and it assumes errata are 
managed by a chartered WG. Given this CG has already identified errata 
for the TE v1 REC, based on my understanding of [ProcDoc], it appears 
the errata should have already published errata in the errata document 
included in the REC:

[3] 
<http://www.w3.org/TR/2013/REC-touch-events-20131010/REC-touch-events-20131010-errata.html>

Perhaps as a starting point, it would be useful for someone to go 
through [1]'s  changelog and create a Draft of the data that should be 
added to [3]. Doing this is important because for *each* change, we must 
decide if the change is substantive enough ("class" 3 or 4 in [ProcDoc]) 
to require the spec to be published as an "Edited Recommendation" and 
let's just say things get "a little complicated".

FYI, some sample errata for which I have been involved:

<http://dev.w3.org/2006/waf/widgets/errata.html>

-AB

[wiki] https://www.w3.org/wiki/TouchEvents/
[ProcDoc] http://www.w3.org/2005/10/Process-20051014/tr.html#rec-modify

Received on Tuesday, 7 October 2014 12:48:06 UTC