[Building Sakai] [sakai-pmc] Proposal: Add Delegated Access as a Sakai core tool

[Bryan Holladay]

Thanks Anthony for taking the lead on this!  Also thank you to Caret and
Aaron Z!


On Fri, Jan 24, 2014 at 4:15 PM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Update.  I have secured permission from CARET to both update the hierarchy
> license to ECL 2.0 and donate the code to the Apereo Foundation.
>
> I'll patch the code during Apereo Camp.
>
> Cheers,
>
> Anth
>
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu | 517-980-0228
>
>
> Begin forwarded message:
>
> *From: *Anthony Whyte <arwhyte at umich.edu>
> *Date: *January 23, 2014 2:46:39 PM EST
> *To: *Bryan Holladay <holladay at longsight.com>, Aaron Zeckoski <
> azeckoski at unicon.net>, Theriault Seth <slt at columbia.edu>
> *Cc: *"Sakai Development (sakai-dev at collab.sakaiproject.org)" <
> sakai-dev at collab.sakaiproject.org>, sakai-pmc at collab.sakaiproject.org, "
> cle-release-team at collab.sakaiproject.org" <
> cle-release-team at collab.sakaiproject.org>
> *Subject: **Re: [sakai-pmc] Proposal: Add Delegated Access as a Sakai
> core tool*
>
> Swinging back to have a look at this proposal from a license perspective.
>  Delegated Access is ECL 2.0, copyright Columbia University. [1]  As was
> noted earlier, Delegated Access is dependent on the contrib hierarchy
> module, originally developed by CARET, University of Cambridge [1].  A good
> bit of the code is licensed ECL 1.0, copyright CARET; at least two files
> are licensed Apache 2, copyright Aaron Zeckoski. [2]
>
> At a minimum Hierarchy's ECL 1.0 license needs to be updated to 2.0 before
> it can be considered for core.  It would be preferable if the project code
> for both modules were donated to the Apereo Foundation.
>
> Anth
>
> [1]
> https://source.sakaiproject.org/contrib/delegatedaccess/trunk/NOTICE.txt
>
> [2] ECL 1.0, copyright CARET (example)
>
> https://source.sakaiproject.org/contrib/caret/hierarchy/trunk/api/src/java/org/sakaiproject/hierarchy/HierarchyNodeReader.java
>
> At least 2 files are licensed Apache 2, copyright Aaron Zeckoski
>
> https://source.sakaiproject.org/contrib/caret/hierarchy/trunk/api/src/java/org/sakaiproject/hierarchy/HierarchyPermissions.java
>
> https://source.sakaiproject.org/contrib/caret/hierarchy/trunk/api/src/java/org/sakaiproject/hierarchy/dao/model/HierarchyNodePermission.java
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu | 517-980-0228
>
>
> On Dec 10, 2013, at 3:30 PM, Bryan Holladay wrote:
>
> *Proposal*
>
> Add Delegated Access as a Sakai core tool
>
>
> *Rationale*
>
> Sakai doesn't have a verbose administration feature set and requires
> institutions to grant too much or too little access for users who shouldn't
> have full administrative privileges.  Delegated Access allows
> administrative users to choose who can access which sites and which
> permissions they have and tools they can view.  Site access through
> Delegated Access doesn't effect Sakai performance and doesn't show up in
> the site's membership list.  Only step required for an institution to start
> using Delegate Access is to add site properties (or leverage existing site
> properties) to describe the hierarchy.
>
> Delegated Access is a contrib tool, currently in use at a number of
> institutions including Columbia (2 years in production) (I wish I had a
> list of all production instances!  I know of at least 10 others, but I
> don't want to post them w/o permission).  This tool has been proven to
> handle scalability as well as functionality.  It is built off of wicket and
> the hierarchy tool and is running in both Oracle and MySql production
> instances.  It is highly customizable with several sakai.properties to
> taylor the tool to your specific use case. [1]
>
> Delegated Access is currently deployed on the nightly+experimental server
> [2].
>
> Delegated Access is currently maintained by Bryan Holladay and supported
> by Longsight. Longsight will continue to support this application and hope
> the community will adopt it as a standard for delegating access to
> departmental administrators.
>
>
> *Vote*
>
> Read the rationale above. A material objection (indicated by a -1 and
> accompany reasoning) raised by a Sakai PMC member will block this proposal.
>  Other opinions are welcome, indeed encouraged. Silence equals consent.
> Discussion should be on the sakai-dev list unless of a private nature in
> which case I am happy to correspond off list. Objections must be received
> before Tuesday 17th December 2013 (one week from now).
>
>
> *Links*
>
>
> 1. https://confluence.sakaiproject.org/display/DAC/Delegated+Access+Tool
>
> 2. http://nightly2.sakaiproject.org:8085/portal
> _______________________________________________
> 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-dev/attachments/20140124/5dd920fe/attachment.html