Sorry about the delay in responding.

The current expectation is that after the Ecma General Assembly meeting, Dec 
10, that anyone will be able to make code contributions to test262 by filling 
out (only once, not once er contributed test) the Ecma software contribution 
form http://www.ecma-international.org/memento/TC39%20exhibit%20B.pdf 

This requires that the code be contributed using a BSD license.  The 
contributor retains ownership of the copyright and the ability to license it 
using other licenses.

I'll provide an update after the meeting.

Allen





On Nov 23, 2013, at 10:45 AM, Domenic Denicola wrote:

> [+test262-discuss]
> 
> From: es-discuss [mailto:[email protected]] On Behalf Of Mark 
> Miller
> 
>> Adding a test262 test would be awesome! But I am no longer sure of the weird 
>> ECMA procedure needed to do so while avoiding IPR issues. Can someone else 
>> advise? Thanks.
> 
> My stance on this, not really informed by anyone but myself, is that you 
> should write test-262 tests, then release them under a liberal license, and 
> ask your favorite Ecma member to copy them into test-262.
> 
> If anyone thinks this won't work, I'd love to hear back before I start 
> converting a lot of promise tests to test-262 form :)
> _______________________________________________
> es-discuss mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/es-discuss
> 

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to