[geeklog-devel] Geeklog CKEditor Integration

[Niemans]

A mixed license environment will always be a problem.
And before upgrading to GPLv3, make sure there ain't third party software involved that still is with GPLv2.
Check Pear also. Maybe switch to MariaDB also? 

My vote would be a class to embed a specific editor, not necessarily a complete plugin.
This class could be integrated by a single config parameter, as long as you have two options minimum.
A specific implementation or plugin could even use a different class, if properly configured.
Or starting with a base class that can be extended.

my 2 euro cents.

Wim





Op 29 jul. 2013, om 23:39 heeft Tom het volgende geschreven:

> We need a new editor in Geeklog since FCKeditor is not being developed any further and we are already having issues with newer browsers.
>  
> My vote would be to upgrade our license if we need to and use the CKEditor. I don’t really know the major differences between the 2 licenses beyond GPLv3 being an upgraded version of 2. As Trinity suggests we could try asking the CKEditor developers  if they can give  a special exception or licence but I don’t really have a reason to give them as why we want to stay with GPLv2.
>  
> I guess the second option would be to release the CKEditor as a plugin and bundle it as part of core to ensure that people always have it.
>  
> Tom
>  
>  
>  
> From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Yoshinori Tahara
> Sent: July-28-13 10:28 PM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] Geeklog CKEditor Integration
>  
> Now, the CKEditor has been integrated with Geeklog in my development environment. It seems to be working fine.
>  
> From http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
>  
> According to the compatibility matrix:
> column: I want to release a project under GPLv2 or later
> row: I want to copy code under GPLv3
> cell: OK: Convey project under GPLv3 [3]
>  
> 3: If you have the ability to release the project under GPLv2 or any later version, you can choose to release it under GPLv3 or any later version and once you do that, you'll be able to incorporate the code released under GPLv3.
>  
> I think, in order to distribute (convey) the Geeklog that integrates CKEditor, it is necessary to upgrade Geeklog license to GPLv3.
>  
> There would be the following three options to us.
>  
> 1. Upgrade Geeklog license to GPLv3
> 2. Switch to other editors (example: TinyMCE under LGPLv2.1)
> 3. Cancel the integration of CKEditor and release as the CKEditor plugin
>  
> What we should do?
>  
> -- 
> Yoshinori Tahara - dengen
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20130730/b9a69636/attachment.html>