- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Sat, 17 May 2014 08:32:07 -0400
- To: Rick Byers <rbyers@google.com>, Doug Schepers <schepers@w3.org>
- CC: "public-touchevents@w3.org" <public-touchevents@w3.org>
On 5/15/14 10:47 AM, Rick Byers wrote: > I can also make proposed edits via GitHub if that's better... I think the PrincipleOfLeastSurprise suggests people would expect to find the latest ED of the spec where the Web Events WG last worked on it i.e. <https://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html>. Would you please clone that repo, try to push an update and let us know the results? We could also use GH i.e. <https://github.com/W3C/touch-events> and if we want to go that route then Doug or I can make sure that directory gets created. At this point, it seems like the most important thing to do is to create an updated spec (and the location of the spec is secondary). -Thanks, ArtB > > Rick > > > On Mon, May 12, 2014 at 12:53 PM, Arthur Barstow > <art.barstow@gmail.com <mailto:art.barstow@gmail.com>> wrote: > > On 5/9/14 11:48 AM, Rick Byers wrote: > > So should I just propose the exact text of the change here in > e-mail and leave the doc work to you Doug (which the community > could then review)? Or is there some system for me to > directly do the doc work, even though it'll be published by > W3C staff? > > > I don't have a strong preference for you sending proposal(s) to > the list vs. you updating the ED (although it seems like a > changeset/diff would be easier for reviewers, especially if the > proposal affects more than one part of the spec). > > Doug? > > -AB > >
Received on Saturday, 17 May 2014 12:32:33 UTC