[sakai-pmc] Re-proposing - Edia skin manager for Sakai 10

Berg, Alan A.M.Berg at uva.nl
Sun Dec 15 04:21:15 PST 2013 

Its great to see this proposal emerge.  Sakai 10 is really making compelling strides.
Anthony, is this proposal tabled so that we can vote on it?


Regards,
           Alan


Alan Berg

Innovation working group
On the use of ICT in Education & Research
University of Amsterdam
________________________________
From: sakai-pmc-bounces at collab.sakaiproject.org [sakai-pmc-bounces at collab.sakaiproject.org] on behalf of Neal Caidin [neal.caidin at apereo.org]
Sent: 14 December 2013 02:22
To: sakai-pmc at collab.sakaiproject.org; Sakai-Dev
Cc: Jaeques Koeman; Mark Breuker; roland at edia.nl Groen
Subject: [sakai-pmc] Re-proposing - Edia skin manager for Sakai 10

Building on Mark Breuker’s proposal (aka stealing), and tying up some loose ends:

Proposal: Include the Edia Skin Manager tool in the main distribution. [1] Edia has agreed to convert the licensing to ECL V2 (Educational Community License version 2). Edia also has offered to help maintain the Skin Manager in the main distribution. Also Mark Breuker has offered to put effort into making it compatible with Sakai 10.

Implications: The Skin Manager has been around for quite some time and makes it much easier to deploy new skins into a running Sakai instance.

[1] https://confluence.sakaiproject.org/display/SM/Home


Cheers,

Neal


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









On Dec 13, 2013, at 10:41 AM, Mark Breuker <mbreuker at loi.nl<mailto:mbreuker at loi.nl>> wrote:

Would it be an option to move the code from contrib (the rsmart branch) to the main Sakai repo and then make the necessary changes there?

Regards,

Mark
________________________________
Van: sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org> [sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org>] namens Matthew Jones [matthew at longsight.com<mailto:matthew at longsight.com>]
Verzonden: vrijdag 13 december 2013 16:28
Aan: Neal Caidin
CC: Jaeques Koeman; sakai-pmc at collab.sakaiproject.org<mailto:sakai-pmc at collab.sakaiproject.org>; Sakai-Dev
Onderwerp: Re: [Building Sakai] [sakai-pmc] Edia skin manager for Sakai 10 (license incompatibility)

I'd want the license updated and the changes John Bush described that were made to his branch to make the tool cluster safe incorporated. (Or maybe just that branch used)
http://collab.sakaiproject.org/pipermail/sakai-dev/2013-November/025242.html

Then I'd be okay with this tool.




Mark Breuker
Functioneel Consultant
Tel.: +31 71 5451 203

Leidse Onderwijsinstellingen bv
Leidsedreef 2
2352 BA Leiderdorp
www.loi.nl<http://www.loi.nl>

________________________________

<nwss_loi34eaab.gif>

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, Dec 13, 2013 at 9:06 AM, Neal Caidin <neal.caidin at apereo.org<mailto:neal.caidin at apereo.org>> wrote:
So if there was a proposal made (by today) that included the plan to update the license, it sounds like that would have a chance of at least being considered?

Thanks,
Neal



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









On Dec 13, 2013, at 7:51 AM, Anthony Whyte <arwhyte at umich.edu<mailto:arwhyte at umich.edu>> wrote:

Skin manager trunk code is still licensed LGPL, so a change in the license has yet to be made.

anthony whyte | its and mlibrary | university of michigan | arwhyte at umich.edu<mailto:arwhyte at umich.edu> | 517-980-0228<tel:517-980-0228>


On Dec 13, 2013, at 7:43 AM, Neal Caidin wrote:

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<mailto:neal.caidin at apereo.org>
Skype: nealkdin
Twitter: ncaidin









On Nov 15, 2013, at 10:01 AM, Mark Breuker <mbreuker at loi.nl<mailto: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<tel:%2B31%2071%205451%20203>
Leidse Onderwijsinstellingen bv
Leidsedreef 2
2352 BA Leiderdorp
www.loi.nl<http://www.loi.nl/>
________________________________________
Van: sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org> [sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org>] namens Charles Severance [csev at umich.edu<mailto: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<mailto:slt at columbia.edu>> wrote:

On Thu, Nov 14, 2013 at 9:22 PM, Seth Theriault <slt at columbia.edu<mailto: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<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

_______________________________________________
sakai-pmc mailing list
sakai-pmc at collab.sakaiproject.org<mailto:sakai-pmc at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc



_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto: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/20131215/15a00131/attachment.html

More information about the sakai-pmc mailing list