[Building Sakai] [DG: Teaching & Learning] Lazy Consensus: OSP disposition in Sakai 10

[Adam Marshall]

I'm so lazy I cant even be bothered to reply with a +1.

Adam


From: pedagogy-bounces at collab.sakaiproject.org [mailto:pedagogy-bounces at collab.sakaiproject.org] On Behalf Of Berg, Alan
Sent: 14 February 2014 14:09
To: Neal Caidin
Cc: sakai-user at collab.sakaiproject.org; sakai-dev; portfolio at collab.sakaiproject.org; pedagogy at collab.sakaiproject.org
Subject: Re: [DG: Teaching & Learning] Lazy Consensus: OSP disposition in Sakai 10


+1
On 14 Feb 2014 14:52, Neal Caidin <neal.caidin at apereo.org<mailto:neal.caidin at apereo.org>> wrote:
[sakai-dev, portfolio, pedagogy, sakai-users]

Hey all,

I apologize in advance if this proposal already was passed, but it is
not clear to me, so for the record, I thought I would send out a quick
proposal under the lazy consensus process so we can wrap this up.

OSP in Sakai 10 Proposal: The Sakai release team will disable the
Portfolio site type. Existing portfolio sites still will be able to add
OSP tools, but users will not be able to create new portfolio sites in
the default Sakai distribution. Re-enabling the creation of portfolio
sites will require a configuration change and re-deploy. Alternately, an
admin user could change the site type in the Sites tool to convert newly
created sites to portfolio sites. [1]

Rationale: The OSP portfolio tool plays an important role at a number of
institutions. However resources for developing, maintaining and QA
testing of the OSP tool set have become scarce as the community starts
to focus on other, more up-to-date open source options, especially
Project Karuta [2], an LTI tool. Therefore, we probably do not want
institutions new to Sakai adopting OSP, when the support for this tool
is not strong. It is likely that OSP will not be a part of Sakai 11 and
for this reason, should not be promoted as a preferred tool in Sakai
10.  It should stay fully in Sakai 10 core in order to provide time for
institutions to plan their next stage in managing their portfolio
functionality.

Lazy consensus:
Everyone is welcome and encouraged to comment.  +1 indicates approval
and silence indicates consent. Only a member of the PMC (Project
Management Committee) can block the proposal. All comments must be
submitted by close of business (your time zone) on Tuesday, February 18,
2014.

[1] Jira to track the work to disable the Portfolio site type -
https://jira.sakaiproject.org/browse/SAK-25587
[2] Project Karuta -
https://confluence.sakaiproject.org/display/OSP/Portfolios+for+the+Future+of+Sakai


Cheers,
Neal


--
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org<mailto:neal.caidin at apereo.org>
Skype me! (but let me know in advance for the first interaction) - nealkdin

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

TO UNSUBSCRIBE: send email to pedagogy-unsubscribe at collab.sakaiproject.org<mailto:pedagogy-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/20140214/b4a7cd1d/attachment.html