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

Matthew Jones matthew at longsight.com
Thu Nov 14 17:50:48 PST 2013


I was going to send out an email after Mark's question on that thread "what
are the criteria for inclusion?". I couldn't find any defined/documented
criteria other than really old stuff from 2005/2006.

The only tool addition we've had to Sakai since 2.7 (when the Product
Council added a number of tools [1]) was Lessons in 2.9. This was basically
a unanimous inclusion with strong support, running everywhere and no
disagreement. There were no new tools in 2.8. From the 2.7 tool review the
comment there was

*"I'm also uneasy that we have relatively little in the way of objective
criteria for the PC just yet, and we have not extended our review very *
*far in directions in which we've been weak in the past (e.g.
accessibility). " - Clay Fenlason*

A few weeks ago I'd mentioned considering parts of the Apereo incubation
process for new tool inclusion but Steve didn't agree with that.

*"We don't need incubation for tool promotions unless we as the PMC
recommend it - ie the project was very new or we saw issues with it that
needed to be worked through, or if the developer wanted it themselves. But
of course that will slow things down." - Steve Swinsburg*

While I don't think we need to go consider all parts of this incubation,
reviewing things like this (licensing), i18n (at least that the tool
supports language bundles), that the tool is running in production in X
institutions and that it will be supported by someone at least up to the
release I'd consider minimal criteria. Accessibility and UI consistency [2]
would also be nice to consider if the tool is going to be used by
non-admins, as this is something we hear pretty often and difficult to fix
later.

Once a tool gets in, it seems very unlikely to get out, and it often
requires long term maintenance from the community. New tools that provide
useful functionality or those that replace unsupported legacy tools which
will bring new adopters or increase the value to existing institutions are
great for core Sakai.

[1]
http://sakai-project-mail-list-archives.1343168.n2.nabble.com/Product-Council-2-7-Tools-Capabilities-Brief-td4046887.html
[2]
http://collab.sakaiproject.org/pipermail/sakai-user/2013-July/003530.html



On Thu, Nov 14, 2013 at 8:29 PM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Edia's skin manager has been suggested for inclusion in Sakai 10.  The
> code is licensed GPL and as such cannot be included in a Sakai distribution
> due to it's strong copy-left provisions.  However excellent the tool may
> be, the suggestion of inclusion is a non-starter given its current license.
>
> Cheers,
>
> Anthony
>
>
>
> https://source.sakaiproject.org/contrib/edia/skin-manager/trunk/api/src/java/nl/edia/sakai/tool/skinmanager/SkinService.java
>
> /*
>  * Edia Project edia-sakai-skin-manager
>  * Copyright (C) 2007 Roland, Edia Educatie Technologie
>  *
>  * This library is free software; you can redistribute it and/or
>  * modify it under the terms of the GNU Lesser General Public
>  * License as published by the Free Software Foundation; either
>  * version 2.1 of the License, or (at your option) any later version.
>  *
>  * This library is distributed in the hope that it will be useful,
>  * but WITHOUT ANY WARRANTY; without even the implied warranty of
>  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>  * Lesser General Public License for more details.
>  *
>  * You should have received a copy of the GNU Lesser General Public
>  * License along with this library; if not, write to the Free Software
>  * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
>  */
>
>
> Begin forwarded message:
>
> *From: *Steve Swinsburg <steve.swinsburg at gmail.com>
> *Date: *November 14, 2013 5:38:36 PM EST
> *To: *Mark Breuker <mbreuker at loi.nl>
> *Cc: *sakai-pmc at collab.sakaiproject.org, Sakai QA <
> sakai-qa at collab.sakaiproject.org>, Anthony Whyte <arwhyte at umich.edu>,
> Adrian Fish <adrian.r.fish at gmail.com>, "
> cle-release-team at collab.sakaiproject.org" <
> cle-release-team at collab.sakaiproject.org>, Developers Sakai-Dev <
> sakai-dev at collab.sakaiproject.org>
> *Subject: **Re: [Building Sakai] [WG: Sakai QA] [cle-release-team]
> Proposal: towards a releasable trunk for Sakai 10 (and beyond)*
>
> Mark can you work that up into a proposal for inclusion and send it out?
> Include some background and maybe ask around the lists for some people that
> are running it in production. Then we can discuss it in a thread of its own
> and get it voted on.
>
> Cheers
> Steve
>
>
> Begin forwarded message:
>
> *From: *"Berg, Alan" <A.M.Berg at uva.nl>
> *Date: *November 14, 2013 4:03:20 PM EST
> *To: *Mark Breuker <mbreuker at loi.nl>
> *Cc: *Anthony Whyte <arwhyte at umich.edu>, Adrian Fish <
> adrian.r.fish at gmail.com>, Sakai QA <sakai-qa at collab.sakaiproject.org>, "
> sakai-pmc at collab.sakaiproject.org" <sakai-pmc at collab.sakaiproject.org>,
> Developers Sakai-Dev <sakai-dev at collab.sakaiproject.org>, "
> cle-release-team at collab.sakaiproject.org" <
> cle-release-team at collab.sakaiproject.org>
> *Subject: **Re: [sakai-pmc] [Building Sakai] [WG: Sakai QA]
> [cle-release-team] Proposal: towards a releasable trunk for Sakai 10 (and
> beyond)*
>
> Another excellent EDIA tool, used by many institutions.
> Don't mind QAing if it gets included
>
>
> Begin forwarded message:
>
> *From: *Mark Breuker <mbreuker at loi.nl>
> *Date: *November 14, 2013 3:43:29 PM EST
> *To: *'Anthony Whyte' <arwhyte at umich.edu>, Adrian Fish <
> adrian.r.fish at gmail.com>
> *Cc: *Sakai QA <sakai-qa at collab.sakaiproject.org>, "
> sakai-pmc at collab.sakaiproject.org" <sakai-pmc at collab.sakaiproject.org>,
> Developers Sakai-Dev <sakai-dev at collab.sakaiproject.org>, "
> cle-release-team at collab.sakaiproject.org" <
> cle-release-team at collab.sakaiproject.org>
> *Subject: **RE: [Building Sakai] [WG: Sakai QA] [cle-release-team]
> Proposal: towards a releasable trunk for Sakai 10 (and beyond)*
>
> Hi all,
>
> May I suggest to include the Skin Manager tool in the main distribution?
> It has been around for quite some time and makes it much easier to deploy
> new skins into a running Sakai instance.
>
> https://confluence.sakaiproject.org/display/SM/Home
>
> Also I think there are quite some institutions running this tool although
> I don't have any hard evidence. Perhaps people using it can reply to this
> message ("Say aaai!" :).
>
> The latest version is compatible with Sakai 2.9.x I would be willing to
> put some effort in making it compatible with Sakai 10.
>
> BTW: what are the criteria for inclusion?
>
> Cheers,
>
> Mark
>
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu | 517-980-0228
>
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131114/89e1898b/attachment-0001.html 


More information about the sakai-pmc mailing list