Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3FA8BA70.4070500@outerthought.org>
Date: Wed, 05 Nov 2003 09:53:04 +0100
From: Steven Noels <stevenn@outerthought.org>
Organization: Outerthought
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
 rv:1.5) Gecko/20031013 Thunderbird/0.3
MIME-Version: 1.0
To: dev@cocoon.apache.org
CC: pmc@cocoon.apache.org
Subject: current status of rhino+cont issue
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

I just wanted to quickly brief you about my talks with some board peeps 
so far on this matter + my personal thoughts. Some of this can be 
followed on the licensing list for those whose subscription is moderated 
through.

Looking at the situation, I think the impasse is much bigger than it 
seems at first sight. While Chris' fork is perfectly legal, integrating 
the source into Cocoon CVS is a different thing:

- it is not in the interest of the Cocoon TLP to host a Javascript 
engine implementation - and I think the ASF board has a perfectly good 
point there
- we can not simply relicense Chris' fork without a proper donation and 
transfer from the Mozilla peeps (which might or might not work out)
- Roy & Brian insist on exploring all possible options to remerge the 
changes into the proper Rhino codebase
- if we succeed at this, we could explore the possibility of moving 
rhino++ (with our continuations stuff added to the 'real' codebase) from 
mozilla.org to ASF (but not to Cocoon) - which might attract a community 
and could be a good thing for rhino itself

I'm busy ATM, but will report back if I have more news.

Cheers,

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source Java & XML            An Orixo Member
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org