CVS or Mercurial? (was RE: Draft spec editorship)

>>> The most urgent need right now seems to be to collect
>>> use-cases/scenarios and requirements in a document. Would you be willing
>>> to edit such a document?
>>
>> Would love to.
>Excellent!
>
>Could you start a document at http://dev.w3.org/2011/webrtc/editor/ ?
>That is where the very first draft is stored as well. Cvs is used for
>revision control.

I can certainly do that. I've actually started work on a document on the Mercurial server [1] on the W3C, since:
1.  Mercurial seems to be the version control system that new specs at the W3C are being authored in (see Indexed DB [2] (in WebApps WG), User Timing [3] (in Perf WG), and Contacts API [4] (DAP, recently migrated).
2.  It was _much_ less work to get started in that system than legacy CVS (since I only have a user/password combo and not a public/private key pair--yet).

I'm not certain if there are other pros/cons for/against using Mercurial as I'm fairly new to it...

If you don't mind having the doc on Mercurial, that's easier for me. I've set up a folder at:
https://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/ 

However, I'm just as happy to work with good-old CVS also :)

Let me know if you'd still like to move forward with the CVS location.
-Travis

[1] http://dvcs.w3.org/hg/
[2] http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html
[3] https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.html
[4] https://dvcs.w3.org/hg/dap/raw-file/ce922ee80ed2/contacts/Overview.html

Received on Friday, 2 December 2011 17:56:22 UTC