Re: Should touchmove really always be synchronous and cancellable?

Ok, I'll start looking into how to make an update with hg (I'll start with
the simpler change in the other thread - fractional touch co-ordinates).
 Jacob if you've got any notes/advice to get me started that would be great!


On Tue, May 20, 2014 at 7:27 PM, Jacob Rossi <Jacob.Rossi@microsoft.com>
wrote:

>  In addition to Art’s point about the Principle of Least Surprise….
>
>
>
> While I prefer git to hg, my preference here is to keep it in hg so you
> can still diff against arbitrary editions past or present.  We could also
> create an errata branch to separate things.
>
>
>
> A W3C account is all that you need (technically, not procedurally) to
> start publishing. Rick, if you’re volunteering to do the editing then I can
> help you get the environment set up.
>
>
>
> -Jacob
>
>
>
> *From:* Sangwhan Moon [mailto:smoon@opera.com]
> *Sent:* Tuesday, May 20, 2014 5:16 AM
> *To:* Arthur Barstow
> *Cc:* Rick Byers; Doug Schepers; public-touchevents@w3.org
> *Subject:* Re: Should touchmove really always be synchronous and
> cancellable?
>
>
>
> On Sat, May 17, 2014 at 9:32 PM, Arthur Barstow <art.barstow@gmail.com>
> wrote:
>
>  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?
>
>
>
> If we are to do this, then I think the respec meta data should probably be
> rolled back so it doesn't show the document status as rec to avoid
> confusion.
>
> (This mixed top and bottom posting is hard to follow...)
>
>
>
>  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
>
>
>
>
>
>
> --
> Sangwhan Moon [Opera Software ASA]
> Software Engineer | Tokyo, Japan
>