[cle-release-team] Proposal: Replace Roster with Roster 2, fully retire Profile 1

[Steve Swinsburg]

Roster1 and Profile1 have now been fully removed from the trunk build.
Please let me know if you have any issues.

regards,
Steve


On Tue, Dec 17, 2013 at 12:01 AM, Neal Caidin <neal.caidin at apereo.org>wrote:

> Congratulations!
>
> — Neal
>
>
>
> Neal Caidin
> Sakai Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
>
>
>
>
>
>
>
>
>
> On Dec 13, 2013, at 4:08 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
>
> Following up on this proposal. No binding -1 votes were received so this
> proposal has passed and work will be undertaken to fully remove Roster1 and
> Profile1 from core. Roster2 has been added to the build already and this
> work will be finalised soon.
>
> Thanks,
> Steve
>
>
> On 15 Nov 2013, at 1:38 pm, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
>
> *Proposal*
>
> 1. Remove Roster 1.
>
> 2. Add Roster 2.
>
> 3. Fully remove Profile 1. The tool has been deprecated and removed for
> some time, the API is the only part remaining.
>
>
> *Rationale*
>
> Roster 1 has been without proper community support for some time. When
> Profile2 was developed (2008, released 2009), both Profile2 and Profile1
> ran side by side. The Profile1 tool was eventually deprecated and removed
> from the release in 2.8. However, due to architectural requirements, the
> Profile2-Roster1 integration depended on the Profile1 API and this is still
> deployed in the release.
>
> Roster2 was subsequently developed (2010) with the same UI and base
> feature set as Roster1, but in a newer UI technology and more
> functionality. The Roster2-Profile2 integration uses EntityBroker and thus
> there is no direct API dependency between the two.
>
> Due to the evolution of Profile2 and the number of image, privacy and
> preference combinations available, the Profile2-Roster 1 doesn't work
> fully, and no more work will be spent in this area.
>
> The Roster2-Profile2 link is a complete integration and respects all
> privacy and preference configurations. With this tool in place, the
> Profile1 API can be fully retired.
>
> Roster2 is a contrib tool, currently in use at a number of sites including
> Lancaster University and New York University [1].
>
> Roster2 is currently deployed on the nightly+experimental server [2].
>
> Roster2 is currently maintained by Adrian Fish and Steve Swinsburg.
>
> *Where to from here*
>
>  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 Friday
> 22nd November 2013 (two weeks from now).
>
> *Links*
>
> 1. https://confluence.sakaiproject.org/display/RSTR/Roster2
> 2. http://nightly2.sakaiproject.org:8085/portal
>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131217/d128157d/attachment.html