News for hackers. Stuff that matters.
Re:AGPL no more by protomyth on Tuesday May 29, 2012 @11:55AM (#4038061)
from the post: "The Opa compiler will remain an AGPL project."

The title on the blog post is "Opa License Change: Not just AGPL anymore"

Re:AGPL no more by kstenerud on Tuesday May 29, 2012 @12:06PM (#4038133)
From the post: "The standard library and the native backend will be licensed under the GPL license with the so-called ClassPath exception, like Java. The exception means you can link the GPL code with any code, opening the door to license your application under any license."
Re:AGPL no more by protomyth on Tuesday May 29, 2012 @12:11PM (#4038167)
Yep, multiple parts having multiple licenses. My point was the AGPL is still in the mix.

for completeness here is the list from the post:

1. The Opa compiler will remain an AGPL project.

2. The standard library and the native backend will be licensed under the GPL license with the so-called ClassPath exception, like Java. The exception means you can link the GPL code with any code, opening the door to license your application under any license.

3. The forthcoming Node.js backend will be licensed under the MIT license.