[Building Sakai] Edia skin manager for Sakai 10 (license incompatibility)

[Steve Swinsburg]

Thanks Mark.

The other issue I've experienced is redeploys wiping out skins that have been uploaded. Is there a strategy to mitigate that?

Cheers,
Steve

Sent from my iPad

> On 15 Nov 2013, at 19:22, Mark Breuker <mbreuker at loi.nl> wrote:
> 
> Hi all,
> 
> Thanks for the feedback.
> 
> I will check with Edia regarding the license. 
> 
> Regarding the cluster aware issue: indeed, in the current version you do need to upload the skin on each node but in my opinion that is still far better than being depended on a system admin for uploading new skins. I think moving the files into the database can have a disadvantage performance wise over serving the files from the file system. But maybe this can be overcome with some caching mechanism?
> 
> Regards,
> 
> Mark
> Van: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] namens Steve Swinsburg [steve.swinsburg at gmail.com]
> Verzonden: vrijdag 15 november 2013 4:17
> Aan: Charles Severance
> CC: Sakai-Dev Developers
> Onderwerp: Re: [Building Sakai] Edia skin manager for Sakai 10 (license incompatibility)
> 
> Edia need to be approached regarding the license. If they want it in the release they will change the license to be compatible, as an LGPL license for source code is incompatible with our current practice.
> 
> cheers,
> Steve
> 
> 
> 
> 
> Mark Breuker
> Product Owner
> Tel.: +31 71 5451 203
> 
> Leidse Onderwijsinstellingen bv
> Leidsedreef 2
> 2352 BA Leiderdorp
> www.loi.nl
> 
> 
> <nwss_loi647cc6>
> 
> De informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) toestemming hebben dit bericht te lezen. Gebruik door anderen dan geadresseerde(n) is verboden. De informatie in dit e-mailbericht (en de bijlagen) kan vertrouwelijk van aard zijn en kan binnen het bereik vallen van een wettelijke geheimhoudingsplicht. Indien u deze e-mail ten onrechte ontvangen hebt, wordt u verzocht ons daarvan zo spoedig mogelijk per e-mail of telefonisch op de hoogte te stellen, en het ontvangen bericht (en de bijlagen) te wissen zonder deze te lezen, te kopiëren of aan derden bekend te stellen.
> 
> P  Denk aan het milieu voordat u dit bericht print
> 
> 
>> On Fri, Nov 15, 2013 at 2:08 PM, Charles Severance <csev at umich.edu> wrote:
>> Seth is right - LGPL is OK for jar files - not for source code.
>> 
>> /Chuck
>> 
>>> On Nov 14, 2013, at 9:38 PM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>>> 
>>> I think Seth is right about this. As I understand it, we can only
>>> include LGPL as long as we don't modify it. Not being able to modify a
>>> tool is not really a situation we want to get into for core code.
>>> -AZ
>>> 
>>> 
>>>> On Thu, Nov 14, 2013 at 9:17 PM, Seth Theriault <slt at columbia.edu> wrote:
>>>> On Thu, Nov 14, 2013 at 8:49 PM, Mark J. Norton
>>>> <markjnorton at earthlink.net> wrote:
>>>>> Actually, it's LGPL, which isn't nearly as restrictive as the GPL.  I
>>>>> believe Sakai is using some packages that are LGPL.
>>>> 
>>>> Sakai has only ever included unmodified 3rd-party libraries that use
>>>> the LGPL pursuant to:
>>>> 
>>>> https://confluence.sakaiproject.org/display/LIC/LGPL2.1
>>>> 
>>>> The Skin Manager is not a 3rd-party library or the like. so my opinion
>>>> is that the LGPL is a problem.
>>>> 
>>>> Seth
>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131115/b88ffc64/attachment.html