-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potentially support a more permissive license #2
Comments
@tswicegood - Unfortunately, we are locked down by a GPL because of some third party GPL2 code that is in the ice core. My idea is to identify the GPL2 parts and rewrite them, as it would be beneficial to switch ice to a GPL/MIT. I'll keep this open and try to scope out the work, find some help, and adjust priority. I would like to talk about possible integration with @armstrong in the future. |
Awesome. Please let me know if you need any help and I'll help out as I can. |
same here |
enables default backspace and delete key when ICE is not tracking
@delambo, it looks like this issue has arisen it's head a few times here, and more times for LITE base on ICE (https://github.com/loopindex/ckeditor-track-changes). I don't think anyone else has raised this, but there's also a compounding issues for both these projects in that the stated license for a while was MIT....so authors contributing during this time were putting their changes under MIT, not GPL....and that remains the case (unless there wan a contributor agreement allowing a license change). Anyways, myself and my team might be able to help solve this by helping to re-write the third-party parts that were GPL (and trying to get buy-in from other authors to switch licenses). Is there many of them? Do you remember where they are? |
The WP and TinyMCE plugs definitely need to be to GPL to be compatible with the respective software, as does all of the other code used, but have you considered releasing everything else with a GPL/MIT similar to that used by jQuery? I would love to look at possible integration with the @armstrong project, but a straight GPL license means we can't use this directly in Armstrong out-of-the-box.
The text was updated successfully, but these errors were encountered: