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

[Neal Caidin]

Sounds like the license issue was cleared up, but did this proposal every pass the PMC?

Thanks,
Neal



Neal Caidin
Sakai Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Nov 15, 2013, at 10:01 AM, Mark Breuker <mbreuker at loi.nl> wrote:

> Hi all,
> 
> I checked with Jaeques from Edia and they have no objections to modify the licensing for the Skin Manager. So this objection can be scrapped from the list.
> 
> Cheers,
> 
> Mark
> Mark Breuker
> Product Owner
> Tel.: +31 71 5451 203
> Leidse Onderwijsinstellingen bv
> Leidsedreef 2
> 2352 BA Leiderdorp
> www.loi.nl
> ________________________________________
> Van: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] namens Charles Severance [csev at umich.edu]
> Verzonden: vrijdag 15 november 2013 15:52
> Aan: Sakai-Dev
> Onderwerp: Re: [Building Sakai] Edia skin manager for Sakai 10 (license incompatibility)
> 
> I would also add one comment about the particular conditions where this tool might and might not work.  Since this is an *admin-only* tool, to me, saying "it does not work in some particular case" or "with this particular configuration, an extra step is required", is not an automatic blocker as it would probably be for an end-user tool.
> 
> I think we can assume that admins know what they are doing and perhaps with some documentation or even messaging in the UI, we can move forward.  Admins can choose not to use a tool if they are informed when not to use the tool.  And it is likely the case that if the tool works for simple setups and has limitations for super-complex setups - then the admins of those complex setups likely already know what is going on.
> 
> (I am making these numbers up) If this adds functionality that admins at 90% of the sites would find extremely useful and somehow might not work for admins at 10% of the sites that have some special advanced clever configuration - then to me that is OK as long as we make sure not to trip up or mislead the 10% folks.
> 
> /Chuck
> 
> On Nov 15, 2013, at 8:38 AM, Seth Theriault <slt at columbia.edu> wrote:
> 
>> On Thu, Nov 14, 2013 at 9:22 PM, Seth Theriault <slt at columbia.edu> wrote:
>> 
>>> The Skin Manager essentially assumes that your /library is being
>>> served by Tomcat. If you use Apache to serve /library from static
>>> files, the upload capabilities of the Skin Manager either won't work
>>> or require specific changes to system directories.
>> 
>> Partial correction here after looking at the code: the Skin Manager
>> can be configured to write to an external directory (such as one with
>> static files served by Apache). However, whether or not this is
>> actually allowed is still a possible obstacle based on local security
>> policies..
>> 
>> 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"
> 
> _______________________________________________
> 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"
> _______________________________________________
> 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-pmc/attachments/20131213/10e9f564/attachment.html