RE: W3C Testing How To slides

I believe it's a lot of extra work without a lot of benefit.
* Set up new accounts and commit privileges (additional ongoing cost)
* Setup scripts to mirror all the content and php files so that it replicates to w3c-test.org
* This won't work for all the various WGs so the reality is that everyone will  end up doing some work in Hg and Github and the W3C will have to spend time/$$ supporting both.

I'd rather see people focus their energy writing test cases than move to another source control system.
The content today is read-only (for HTML) and like Hg a 'pull' can be done without any type of permissions.

-Kris

-----Original Message-----
From: Odin Hørthe Omdal [mailto:odinho@opera.com] 
Sent: Wednesday, September 19, 2012 2:54 AM
To: public-test-infra@w3.org
Subject: Re: W3C Testing How To slides

On Wed, 19 Sep 2012 11:48:46 +0200, Tobie Langel <tobie@fb.com> wrote:
>> Oh *that* readonly. Yes indeed. I would recommend we simply stop 
>> using hg and move everything to GH, but maybe that's just me.
>
> I would vote in favor of that too. We could however still use hg to 
> mirror our github repositories.

I would too.

It'll be a lower barrier for doing pull requests etc.

--
Odin Hørthe Omdal (Velmont/odinho) · Core, Opera Software, http://opera.com

Received on Wednesday, 19 September 2012 16:28:35 UTC