Closed (fixed)
Project:
KCFinder integration
Version:
7.x-1.82
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 May 2011 at 19:24 UTC
Updated:
4 Jan 2014 at 00:53 UTC
Jump to comment: Most recent
Comments
Comment #1
Niremizov commentedThe reason is that we are sharing session data of drupal with KCFinder, for that we made some correction of core/autoload.php. So if all KCFinder files are placed inside module it is much easyer to install it...
Comment #2
danyalejandro commentedAs Niremizov said,
Initially, we tried to not include the kcfinder's library, but ended up doing it because it needs some lines of it's code to be altered to work with Drupal (to include the Drupal session). To this date, we haven't been able to setup the module in a way that doesn't require code alteration.
Besides, the library's development has been suspended, so making a "fork" isn't out of planning in our future versions. We even got the author's permission and everything (he didn't get the drama of the situation though, no need to ask for it).
KCFinder library:
I think we would be candidates for an exception.
Comment #3
pwolanin commentedLarry or Gerhard should weigh in here, but sounds like a reasonable case for an exception.
The code must be licensed GPL v2+ to be on d.o, so you should add an additional line to that effect in each of the source files that has a copyright and license statement.
This diagram suggests the LGPL2 can legally be converted to GPL v2+
http://www.dwheeler.com/essays/floss-license-slide.html
If it was GPL v2 (only) you could not add it to d.o without permission of all existing copyright holders to re-license it.
Comment #4
danyalejandro commentedNow the KCFinder library is a separate download! No more legal issues I guess...