15:57:56 <RRSAgent> RRSAgent has joined #webevents
15:57:56 <RRSAgent> logging to http://www.w3.org/2011/02/15-webevents-irc
15:58:00 <timeless> Scribe: timeless
15:58:04 <ArtB> RRSAgent, make log public
15:58:20 <Zakim> +Art_Barstow
15:58:21 <ArtB> ScribeNick: ArtB
15:58:21 <ArtB> Scribe: Art
15:58:21 <ArtB> Agenda: http://lists.w3.org/Archives/Public/public-webevents/2011JanMar/0048.html
15:58:21 <ArtB> Date: 15 February 2011
15:58:21 <ArtB> Chair: Art
15:58:22 <ArtB> Meeting: Web Events WG Voice Conference
15:58:45 <ArtB> Scribe: Josh
15:58:54 <ArtB> ScribeNick: timeless
16:00:23 <Zakim> +[IPcaller]
16:00:43 <ArtB> zakim, IPcaller is Sangwhan_Moon
16:00:43 <Zakim> +Sangwhan_Moon; got it
16:00:51 <smaug_> Zakim,  [IPcaller] is Olli_Pettay
16:00:51 <Zakim> sorry, smaug_, I do not recognize a party named '[IPcaller]'
16:01:18 <Zakim> +Shepazu
16:01:25 <Zakim> +Matt_Brubeck
16:01:41 <ArtB> Present: Art_Barstow, Matt_Brubeck, Doug_Schepers, Olli_Pettay
16:02:41 <smaug_> Zakim,  Sangwhan_Moon is Olli_Pettay
16:02:41 <Zakim> sorry, smaug_, I do not recognize a party named 'Sangwhan_Moon'
16:03:05 <ArtB> Present+ Josh_Soref
16:04:12 <timeless> Topic: 1. Brainstorm for agenda topics ...
16:04:14 <Dzung_Tran> Dzung_Tran has joined #webevents
16:04:27 <Dzung_Tran> Present+ Dzung_Tran
16:04:58 <timeless> MB: We want to talk about Mercurial workflow
16:05:04 <timeless> DS: yep
16:05:12 <Cathy> Cathy has joined #webevents
16:05:34 <timeless> DS: We had talked about talking about tracker
16:05:37 <timeless> s/tracker/Tracker/
16:05:48 <mbrubeck> In the last telcon, we also talked about test suite code hosting and public forking/contributions.
16:06:01 <timeless> Topic: Mercurial workflow
16:06:25 <timeless> MB: Quick summary ...
16:06:26 <Dzung_Tran> I have a conflict, so I was just going to follow on IRC
16:06:48 <timeless> ... for SW, DS, myself -- editors, we need to decide how we are going to merge eachother's changes
16:06:54 <timeless> ... there are many things we could do
16:07:01 <timeless> ... two of the simple ones are ...
16:07:12 <Zakim> + +1.781.266.aaaa
16:07:15 <timeless> ... using the CVS model where we each push/pull from a single centralized repo
16:07:35 <Cathy> zakim, aaaa is me
16:07:35 <Zakim> +Cathy; got it
16:07:36 <timeless> ... or we could each have our own repos, push our changes to our individual clones
16:07:46 <timeless> ... and once changes have been discussed, we could push to the official repo
16:07:47 <timeless> q+
16:07:50 <ArtB> Present+ Cathy_Chan
16:07:58 <timeless> DS: What are the advantages of each approach?
16:08:11 <timeless> MB: The centralized approach is easier for people to follow
16:08:36 <timeless> ... The advantage of people publishing changes before they're integrated is that it provides a way for people to review proposals before they're made
16:08:49 <timeless> DS: So this touches on Review then Commit or Commit then Review model
16:09:01 <timeless> ... traditionally @W3C we follow a Review then Commit
16:09:11 <timeless> ... At HTML/SVG
16:09:36 <timeless> ... WebApps, CSS(?), all use Commit then Review
16:10:27 <timeless> ... In the newer browser centric groups, we typically do Commit then Review
16:10:41 <timeless> ... it tends to be faster and provides context for review
16:10:57 <timeless> MB: In distributed you can do Commit, then Review, then Merge (=Accept)
16:11:09 <timeless> DS: I think that's OK
16:11:16 <timeless> MB: We could do any of these
16:11:28 <timeless> ... If the editors want to use a central repo
16:11:43 <timeless> ... And other people especially people without write access could use clones
16:12:07 <timeless> DS: I tend to favor for non controversial changes, in order to make it easy for people to understand what's going on with the group
16:12:21 <timeless> ... using the central repository for the three editors
16:12:33 <timeless> ... But if we have controversial things, we could do something else
16:12:45 <timeless> MB: I think that's OK, since there aren't many editors
16:13:06 <timeless> DS: I'm very intrigued by the prospect of having distributed changeset.
16:13:14 <timeless> ... people sending in patches on a mailing list
16:13:23 <timeless> ... I like the idea of multiple editors getting their ideas out there
16:13:29 <timeless> ... and letting people decide which works best
16:13:35 <timeless> MB: And we'll probably see some of that
16:13:42 <timeless> ... we've already seen some of that w/ SW
16:13:58 <timeless> DS: And i'll see some of that with Hg
16:14:23 <timeless> MB: Using central you'll have simple pull merge cycle
16:14:32 <timeless> ... but it won't feel much different from CVS
16:14:36 <timeless> ack me
16:15:05 <timeless> JS: Another way to do things is to use Branches
16:15:21 <timeless> ... but I'm not at all in favor of it. Merely noting it's possible
16:15:30 <timeless> AB: So it sounds like we're in favor of using a central repo
16:15:38 <timeless> ... does that seem like a fair characterization?
16:15:48 <timeless> ... Anyone else have feedback/input?
16:15:57 <timeless> RESOLUTION: Stick with central repo
16:16:20 <RRSAgent> I have made the request to generate http://www.w3.org/2011/02/15-webevents-minutes.html timeless
16:17:03 <timeless> DS: So, we covered what + how
16:17:09 <timeless> ... but we haven't talked about The Who
16:18:05 <timeless> DS: Do we want to have MB/SW make some changes?
16:18:12 <timeless> MB: I think I can do some simple changes
16:18:31 <timeless> DS: You can make some changes and cause me to need to do a merge.
16:18:40 <timeless> ... It will be good practice for you (editing) and for me (merging)
16:18:57 <timeless> ... MB: have you ever been an editor before?
16:18:59 <timeless> MB: no
16:19:12 <timeless> AB: So we also agreed to a Commit then Review model
16:19:39 <timeless> RESOLUTION: We will follow the Commit then Review model
16:19:52 <timeless> AB: ... this will align us with the other groups DS mentioned
16:20:09 <timeless> DS: I'd also like to use this group to do some experimenting
16:20:16 <timeless> ... but for starters, I think this is fine
16:20:37 <timeless> DS: so MB, for next week, you'll make some small changes?
16:20:57 <timeless> MB: Yes, I'll look through the issues on the mailinglist and see which ones I can address
16:21:13 <timeless> DS: I think that leads us to our next topic
16:21:29 <timeless> Topic: Tracker
16:21:51 <timeless> DS: So, Tracker is our issue tracker
16:22:04 <ArtB> tracker: http://www.w3.org/2010/webevents/track/
16:22:17 <timeless> DS: Let's walk through creating an issue and creating an action
16:22:24 <timeless> ... MB: have you used Tracker before?
16:22:27 <timeless> MB: No, I haven't
16:22:34 <timeless> DS: It's rather simple
16:23:29 <shepazu> action: matt to update touch events spec for next week
16:23:29 <trackbot> Created ACTION-11 - Update touch events spec for next week [on Matt Brubeck - due 2011-02-22].
16:23:35 <ArtB> Scribe+ Art
16:23:40 <ArtB> ScribeNick: ArtB
16:24:02 <mbrubeck> and then I can see http://www.w3.org/2010/webevents/track/actions/11
16:24:05 <ArtB> DS: can create Actions via IRC interface
16:24:14 <ArtB> ... and can create Issues via IRC as well
16:24:20 <shepazu> issue: resolve touch area re. radius and angle
16:24:20 <trackbot> Created ISSUE-1 - Resolve touch area re. radius and angle ; please complete additional details at http://www.w3.org/2010/webevents/track/issues/1/edit .
16:24:28 <ArtB> ... (provided trackbot is running ...)
16:24:35 <shepazu> issue-1?
16:24:35 <trackbot> ISSUE-1 -- Resolve touch area re. radius and angle -- raised
16:24:35 <trackbot> http://www.w3.org/2010/webevents/track/issues/1
16:24:53 <ArtB> DS: then in IRC, can say "ISSSUE-n?" where n is an issue number
16:25:01 <ArtB> ... and trackbot will dump out the issue
16:25:10 <ArtB> ... same thing works with "ACTION-n?"
16:25:18 <ArtB> ... don't forget the "?" at the end
16:25:29 <ArtB> ... Raised state means raised
16:25:29 <Zakim> -Olli_Pettay
16:25:37 <ArtB> ... Open means WG agreees it is an issue
16:25:48 <ArtB> ... Pending state means we are awaiting feedback
16:26:13 <Zakim> +??P0
16:26:17 <ArtB> ... Postponed state means the Issue will not be released in the current spec (postponed to v2)
16:26:22 <smaug_> Zakim, ??P0 is Olli_Pettay
16:26:22 <Zakim> +Olli_Pettay; got it
16:26:30 <ArtB> ... Can also select the issue/action's "product"
16:26:42 <ArtB> ... currently we just have the one Touch Event product
16:27:08 <shepazu> http://www.w3.org/mid/4D470F74.9020208@canonical.com
16:27:41 <ArtB> DS: after an Issue is created, an email will be sent to public-webevents
16:28:28 <ArtB> ... if an email includes a {ACTION,ISSUE}-n tag, that email's archive link will be added to the issue or action
16:28:44 <shepazu> issue-1?
16:28:44 <trackbot> ISSUE-1 -- Resolve touch area re. radius and angle -- raised
16:28:44 <trackbot> http://www.w3.org/2010/webevents/track/issues/1
16:29:07 <ArtB> ... f.ex. if you look at the issue I just raised: http://www.w3.org/2010/webevents/track/issues/1
16:29:16 <ArtB> ... you will see the email trail
16:29:29 <ArtB> ... can also define a "short name" for Issues
16:29:47 <ArtB> ... which can be convenient way to identify an Issue
16:30:05 <shepazu> action-1?
16:30:05 <trackbot> ACTION-1 -- Arthur Barstow to work with Doug on a voice conference time of day that works for most people -- due 2010-12-15 -- CLOSED
16:30:05 <trackbot> http://www.w3.org/2010/webevents/track/actions/1
16:30:21 <shepazu> action-11?
16:30:21 <trackbot> ACTION-11 -- Matt Brubeck to update touch events spec for next week -- due 2011-02-22 -- OPEN
16:30:21 <trackbot> http://www.w3.org/2010/webevents/track/actions/11
16:30:44 <ArtB> ... Issues and Actions created in IRC are "bare bones"
16:31:04 <ArtB> ... Need to use Tracker's Web interface for more advanced management tasks
16:31:35 <ArtB> ... f.ex. can change due date (which defaults to 7 days from creation date)
16:33:01 <ArtB> DS: tracker scans all emails on public-webevents
16:33:18 <ArtB> ... for {Action,Issue}-n tags
16:33:35 <ArtB> ... and adds a link to the emails archive to the Action or Issue
16:33:48 <ArtB> MB: does Tracker track mercurial changes?
16:33:53 <ArtB> DS: no, I don't think so
16:34:04 <ArtB> ... but we may be able to make something like that work
16:34:29 <ArtB> ... there is an option to do that for CVS
16:34:35 <ArtB> ... but sure about Mercurial
16:34:48 <ArtB> ... I'll need to talk to sysadmin team at W3C
16:35:00 <ArtB> ... we may also be able to connect commits to twitter
16:36:00 <ArtB> AB: I've been using Tracker for years
16:36:09 <ArtB> ... it's easy to use and that's good
16:36:19 <ArtB> ... may be missing some features Bugzilla has
16:36:25 <ArtB> ... but overall, it's a good tool
16:37:07 <ArtB> DS: a disadvantage to Bugzilla is all of the comment treads are kept in Bugzilla, whereas with Tracker, email is used for comment threads
16:37:45 <ArtB> AB: anything else on Tracker for today?
16:38:20 <ArtB> DS: I just logged one issue based on comments from two different people
16:38:45 <mbrubeck> action: Matt Brubeck to raise issues on Tracker for previous mailing list discussions.
16:38:45 <trackbot> Created ACTION-12 - Brubeck to raise issues on Tracker for previous mailing list discussions. [on Matt Brubeck - due 2011-02-22].
16:38:46 <ArtB> ... it may be good for Matt (and others) to create Issues based on comment from the list
16:39:45 <ArtB> JS: how does one get support for Tracker?
16:39:59 <ArtB> DS: everything is handled by W3C sysadmin team
16:40:07 <ArtB> ... and I can be your conduit to that team
16:40:33 <ArtB> AB: yes, please notify Doug and I if you have any Tracker issues and we will follow up
16:41:11 <ArtB> DS: I would like to walk thru a merge
16:41:17 <ArtB> MB: let's do that after the call
16:41:19 <ArtB> DS: OK
16:41:40 <ArtB> Topic: Technical Discussion
16:42:06 <ArtB> AB: I have some open action; I'll get to them RSN
16:42:25 <ArtB> DS: we didn't get much response about UCs and Reqs
16:42:38 <ArtB> ... but could defer them until next week
16:43:07 <ArtB> DS: re Andrew Grieve's email ...
16:43:24 <ArtB> ... we may want to create some issues
16:43:37 <shepazu> http://lists.w3.org/Archives/Public/public-webevents/2011JanMar/0043.html
16:44:14 <ArtB> DS: re what should happen if touch is dragged off the screen ....
16:44:26 <ArtB> ... I think that is already addressed in the spec -> touch cancel
16:44:40 <ArtB> DS: I significantly changed touch cancel
16:45:22 <ArtB> DS: oh, Matt, we should talk about "ReSpec" which is used by the Touch Events spec
16:45:49 <mbrubeck> issue-2?
16:45:49 <trackbot> ISSUE-2 -- What should happen when a touch is dragged off the screen -- raised
16:45:49 <trackbot> http://www.w3.org/2010/webevents/track/issues/2
16:46:17 <ArtB> AB: I don't think anyone has responded to the email
16:46:28 <ArtB> DS: I will respond to Andrew's email
16:46:49 <ArtB> ... will need to tighten up the spec re what happens when touch is moved offscreen
16:46:56 <ArtB> ... Matt, can you look at that?
16:46:58 <ArtB> MB: yes
16:47:57 <ArtB> DS: re 2nd issue ...
16:48:22 <ArtB> OP: I think this is closer to a mouse use case
16:48:35 <mbrubeck> re issue-2, different hardware devices may or may not be able to detect whether a touch was dragged off the screen or released normally.
16:48:37 <ArtB> ... need to check this on an Android or iPhone
16:48:48 <ArtB> DS: I could test this
16:48:55 <mbrubeck> issue-3?
16:48:56 <trackbot> ISSUE-3 -- Click event target after DOM mutation during touchstart -- raised
16:48:56 <trackbot> http://www.w3.org/2010/webevents/track/issues/3
16:48:57 <ArtB> ... would be good if someone would write a test though
16:49:04 <ArtB> ... any volunteers for that?
16:49:07 <ArtB> [Silence]
16:49:12 <ArtB> DS: ok, I'll write it
16:50:14 <mbrubeck> issue-4?
16:50:14 <trackbot> ISSUE-4 -- Does preventDefault on touchmove cause a dragging motion to fire a click event? -- raised
16:50:14 <trackbot> http://www.w3.org/2010/webevents/track/issues/4
16:51:14 <ArtB> ACTION: doug create a test for ISSUE-4
16:51:14 <trackbot> Created ACTION-13 - Create a test for ISSUE-4 [on Doug Schepers - due 2011-02-22].
16:51:21 <Zakim> -Josh_Soref
16:51:44 <ArtB> OP: remember to test mouse up and mouse down
16:52:04 <ArtB> MB: iPhone synthesize mouse up/down
16:52:13 <ArtB> ... mouse up, mouse move, click
16:52:43 <ArtB> ... needed for compatibility of apps that know about mouse events but not touch
16:53:39 <ArtB> DS: what are we doing about preventDefualt in general?
16:53:44 <ArtB> MB: will be impl-specific
16:54:02 <ArtB> ... e.g. safari pans with touch move
16:54:47 <ArtB> DS: we don't define all default actions the UA can take
16:55:03 <ArtB> ... but we can define what preventDefault does
16:55:22 <ArtB> ... There could be some issues around timing
16:55:28 <ArtB> ... that we may need to define
16:55:30 <mbrubeck> MB: In mobile Firefox, for performance reasons, we also might want preventDefault on touchstart to affect which other touch events are fired.  For example, if you don't preventDefault on touchstart, then no touchmove/touchend events will be dispatched.
16:55:34 <ArtB> ... other than "don't do that"
16:56:52 <ArtB> DS: that's good info
16:56:58 <ArtB> ... perhaps you should put that in the spec
16:57:07 <ArtB> MB: let me bring it up on the list first
16:57:14 <ArtB> DS: sounds good
16:58:39 <ArtB> Topic: AOB
16:58:51 <ArtB> AB: let's continue discussion on the lsit
16:58:57 <Zakim> -Olli_Pettay
16:58:58 <Zakim> -Cathy
16:59:03 <ArtB> ... and meet again next week
16:59:10 <mbrubeck> shepazu: Want to try a merge?
16:59:11 <Zakim> -Matt_Brubeck
16:59:13 <Zakim> -Art_Barstow
16:59:16 <Zakim> -Shepazu
16:59:17 <Zakim> RWC_()11:00AM has ended
16:59:18 <ArtB> ... Meeting adjourned
16:59:19 <Zakim> Attendees were Josh_Soref, Art_Barstow, Shepazu, Matt_Brubeck, Olli_Pettay, +1.781.266.aaaa, Cathy
16:59:21 <mbrubeck> We can remove the "test" and "test2" files
16:59:24 <ArtB> RRSAgent, make minutes
16:59:24 <RRSAgent> I have made the request to generate http://www.w3.org/2011/02/15-webevents-minutes.html ArtB
16:59:24 <shepazu> mbrubeck: yes, give me 15 minutes
16:59:30 <mbrubeck> ok
17:00:39 <ArtB> Regrets: Sangwhan_Moon
17:00:44 <ArtB> RRSAgent, make minutes
17:00:44 <RRSAgent> I have made the request to generate http://www.w3.org/2011/02/15-webevents-minutes.html ArtB
17:31:32 <shepazu> mbrubeck: sorry, had another call
17:31:43 <mbrubeck> np
17:31:43 <shepazu> ready now if you are
17:32:09 <mbrubeck> shepazu: Okay to start: how about if I push a commit that removes "test"
17:32:18 <mbrubeck> and without pulling, you push a commit that removes "test2"
17:32:23 <mbrubeck> then you can pull and merge my commit
17:32:59 <mbrubeck> pushed
17:33:13 <shepazu> hmmm
17:33:26 <shepazu> I'm going to try this with command line, rather than Murky
17:34:13 <shepazu> mbrubeck: could you walk me though it?
17:34:17 <mbrubeck> sure
17:34:34 <mbrubeck> I'll just type out some commands, let me know if any of them give you issues
17:34:37 <mbrubeck> hg rm test2
17:34:38 <shepazu> k
17:34:48 <mbrubeck> hg com -m "Remove old dummy file."
17:35:03 <mbrubeck> hg push #this should give you an error, which lets you know your tree is not up to date
17:35:39 <shepazu> abort: repository default-push not found!
17:35:46 <shepazu> hmmm
17:35:53 <shepazu> not the error I was expecting
17:36:19 <mbrubeck> shepazu: You can try |hg push https://dvcs.w3.org/hg/webevents|
17:36:44 <mbrubeck> or edit your .hg/hgrc to read:
17:36:44 <mbrubeck> [paths]
17:36:44 <mbrubeck> default = https://dvcs.w3.org/hg/webevents
17:36:46 <shepazu> searching for changes
17:36:46 <shepazu> abort: push creates new remote heads!
17:36:47 <shepazu> (did you forget to merge? use push -f to force)
17:36:54 <mbrubeck> shepazu: Great, that's the expected error
17:37:00 <mbrubeck> shepazu: Now try |hg pull|
17:37:29 <shepazu> min, gonna change my path
17:38:49 <shepazu> mbrubeck: I don't see an hgrc file, should I just create it?
17:38:53 <mbrubeck> yes
17:39:15 <mbrubeck> normally that would be set up automatically by your initial |hg clone|
17:40:04 <shepazu> well, I used a GUI, Murky
17:40:15 <shepazu> pulling from https://dvcs.w3.org/hg/webevents
17:40:15 <shepazu> searching for changes
17:40:16 <shepazu> adding changesets
17:40:16 <shepazu> adding manifests
17:40:16 <shepazu> adding file changes
17:40:16 <shepazu> added 1 changesets with 0 changes to 0 files (+1 heads)
17:40:19 <shepazu> (run 'hg heads' to see heads, 'hg merge' to merge)
17:40:34 <mbrubeck> okay, now would be a good time to open Murky and look at the graphical log
17:40:52 <mbrubeck> you'll see what it means by the two "heads" in your repo
17:41:45 <mbrubeck> you should see your last commit and my last commit, both branching off from the same parent
17:42:08 <mbrubeck> when you've seen that, run |hg merge|
17:42:57 <shepazu> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
17:42:57 <shepazu> (branch merge, don't forget to commit)
17:43:07 <mbrubeck> hg commit -m "Merge"
17:43:12 <mbrubeck> and then take a look at Murky again
17:43:35 <mbrubeck> this was an easy merge since there were no conflicts.  If we both edited the same lines, then you'd have to resolve conflicts.
17:43:43 <shepazu> right
17:43:55 <mbrubeck> Just like Subversion, Mercurial will place conflict markers into your files by default, or run a merge tool that you specify in your hgrc
17:44:01 <shepazu> ok, seems straightforward, if a little verbose
17:44:14 <mbrubeck> now you can |hg push| again and it should succeed
17:44:34 <shepazu> pushing to https://dvcs.w3.org/hg/webevents
17:44:34 <shepazu> searching for changes
17:44:34 <shepazu> http authorization required
17:44:34 <shepazu> realm: W3C Mercurial Repository
17:45:56 <shepazu> maybe I can add that to my hgrc?
17:46:11 <mbrubeck> I'm not sure whether it can save passwords
17:46:27 <mbrubeck> A common option is to provide an ssh:// URL and use public key authentication
17:46:52 <mbrubeck> did it prompt for your username/password?
17:47:19 <mbrubeck> You might be able to use https://username:password@dvcs.wc.org/... format
17:48:07 <shepazu> it didn't prompt
17:48:22 <mbrubeck> hmm
17:48:27 <mbrubeck> what version of hg do you have, by the way?
17:48:52 <shepazu> sorry, it did prompt
17:48:58 <mbrubeck> the current is 1.7.x.  If you have 1.5.x or older, you should definitely update.
17:49:11 <shepazu> Mercurial Distributed SCM (version 1.3.1)
17:50:05 <shepazu> best way to update?
17:50:28 <shepazu> ugh, I sure don't want to have to auth every time I push :(
17:51:08 <mbrubeck> shepazu: Are you using MacPorts or something?  I don't have a Mac, but however you installed hg should be able to update it.
17:51:36 <mbrubeck> setting the path to https://username:password@dvcs.wc.org/hg/webevents seems to work (but I haven't tried pushing)
17:51:36 <shepazu> I think I'm just using the version that came on my mac
17:51:54 <shepazu> I don't even know what MacPorts is :)
17:52:35 <mbrubeck> http://mercurial.selenic.com/wiki/Download#Mac_OS_X has some options
17:52:46 <mbrubeck> fink and macports are package managers for Unix-style packages on OS X
17:53:12 <shepazu> ah
17:54:05 <mbrubeck> older versions had some bugs especially around moving/renaming files.  We probably won't run into that any time soon...
17:55:09 <mbrubeck> What we did above is everything you need to push/pull changes in a shared repository.  There are a bunch of extra optional things that you can do, but don't have to.
17:55:58 <mbrubeck> Mozilla folks like to use the mq extension or http://mercurial.selenic.com/wiki/RebaseExtension which lets you replay your local changes on top of the remote ones, instead of a creating a new "merge" commit.  This is basically what "svn up" does, and it gives you a more linear history.
17:57:01 <mbrubeck> It's basically an aesthetic decision; it makes the changelog more readable, but it doesn't play well if you have already published your changes in a different public repo.
17:58:06 <shepazu> Mercurial Distributed SCM (version 1.7.5+20110209)
17:58:18 <mbrubeck> yay
17:59:39 <mbrubeck> http://twitter.com/#!/w3cwebevents/status/37568328994136064
18:01:59 <shepazu> mbrubeck: well, it would be nice to have a clear changelog
18:03:31 <mbrubeck> shepazu: Try enabling the Rebase extension (see instructions in link above), then instead of "hg pull; hg merge" you can just do "hg pull --rebase" and it will be basically the same as "svn up"
18:03:52 <shepazu> ok
18:03:53 <mbrubeck> (except unlike svn, you commit before pulling)
18:04:33 <mbrubeck> shepazu: You can enable that extension in ~/.hgrc instead of webevents/.hg/hgrc, so it will apply globally.
18:56:05 <Zakim> Zakim has left #webevents
18:58:49 <ArtB> rrsagent, bye
18:58:49 <RRSAgent> I see 3 open action items saved in http://www.w3.org/2011/02/15-webevents-actions.rdf :
18:58:49 <RRSAgent> ACTION: matt to update touch events spec for next week [1]
18:58:49 <RRSAgent>   recorded in http://www.w3.org/2011/02/15-webevents-irc#T16-23-29
18:58:49 <RRSAgent> ACTION: Matt Brubeck to raise issues on Tracker for previous mailing list discussions. [2]
18:58:49 <RRSAgent>   recorded in http://www.w3.org/2011/02/15-webevents-irc#T16-38-45
18:58:49 <RRSAgent> ACTION: doug create a test for ISSUE-4 [3]
18:58:49 <RRSAgent>   recorded in http://www.w3.org/2011/02/15-webevents-irc#T16-51-14