Re: W3C reftest submissions and imports

On 09/27/2011 06:28 AM, Gervase Markham wrote:
> On 23/09/11 01:24, fantasai wrote:
>> The dual-license that applies to the W3C tests:
>>    http://www.w3.org/Consortium/Legal/2008/04-testsuite-copyright
>>
>> The license grant that W3C requests of contributors to the test suite:
>>
>>    The Contributor hereby grants to the W3C, a perpetual, non-exclusive,
>>    royalty-free, world-wide right and license under any Contributor
>>    copyrights in this contribution to copy, publish, use, and modify the
>>    contribution and to distribute the contribution under a BSD License or
>
> The fact that this final word is an "or" and not an "and optionally" is
> rather worrying.

Good point, I'll ask Rigo about it. On the plus side, it's a non-exclusive
license, not a copyright grant. So if the author chooses independently to
also license it under BSD, it's under BSD regardless.

> But we do have a general principle that we contribute stuff upstream
> under the licence used upstream. So that part is OK. We just need to
> make sure that people who check in to this directory know what they are
> doing. Given that in practice, I expect that you will be involved in all
> checkins, I'm sure you can make sure that people are aware :-)

Actually, my intention is to *avoid* being involved in most of these
checkins. :)

>> What I'd like to do is to create
>>
>> other-licenses/
>>    |-w3c-css/
>>        |-submitted/      # tests we are submitting to W3C, our copy is master
>>        |-received/       # tests we are receiving from W3C, their copy is master
>>
>> What is the process for setting this up?
>
> Straw man:
>
> Just create it, and add a README to the "submitted" directory saying
> "Files and modifications in this directory must be submitted under the
> following licence grant:" and then a copy of what you quoted.

Sounds reasonable to me. :) I think we should toss in a LICENSE with the
appropriate BSD 3-clause into w3c-css/ as well.

> But I would file a bug to get legal sign-off on this plan.

Under which component would I file this bug?
   https://bugzilla.mozilla.org/enter_bug.cgi?full=1
I've been staring at this list for awhile now, and can't find where it
should go...

~fantasai