You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if you'd be willing to release haxe-continuation under the more lenient MIT license, instead of BSD.
The issue with the BSD license is that it requires a copy of the license to be bundled with binary code, which can be problematic for distribution. In the most extreme case, it makes it useless for the Flash target, since SWF files are embedded as stand-alone, and not bundled into a package which can contain text files. Even on other targets, bundling the license text file with the executable can be problematic.
For these reasons, Haxe's standard library was released under the MIT license since Haxe 3. You can read about it here: http://haxe.org/doc/license
While I don't think every library should have a permissive non-attribution license, this library really adds core-functionality, from which it is more likely to create a program's core than some optional/added feature. So I think that functionality-wise it is in line with Haxe's standard library, and would benefit from having a similar license.
The text was updated successfully, but these errors were encountered:
I guess there are some “about” or “credits” pages in your production to declare licenses and copyrights, and SWF's XMP metadata can also contain these informations.
Thanks for your appreciation. But, unfortunately, I am not working for Haxe Foundation, and these guys do not maintain haxe-continuation.
I'm wondering if you'd be willing to release haxe-continuation under the more lenient MIT license, instead of BSD.
The issue with the BSD license is that it requires a copy of the license to be bundled with binary code, which can be problematic for distribution. In the most extreme case, it makes it useless for the Flash target, since SWF files are embedded as stand-alone, and not bundled into a package which can contain text files. Even on other targets, bundling the license text file with the executable can be problematic.
For these reasons, Haxe's standard library was released under the MIT license since Haxe 3. You can read about it here: http://haxe.org/doc/license
While I don't think every library should have a permissive non-attribution license, this library really adds core-functionality, from which it is more likely to create a program's core than some optional/added feature. So I think that functionality-wise it is in line with Haxe's standard library, and would benefit from having a similar license.
The text was updated successfully, but these errors were encountered: