+1 for shelving it, but I would prefer to see it placed in the widget library rather than simply disappearing. Some widget developer in future may pick it up and do something more inspiring with it.
~Clay On Thu, Jun 28, 2012 at 11:19 AM, Anthony Whyte <[email protected]> wrote: > +1 for removal. We could disable it by default as a deprecation step but > given the reasons for removal outlined by Nico below we should take it out > now. > > Cheers, > > Anth > > > On Jun 28, 2012, at 10:36 AM, Bert Pareyn wrote: > > > +1. > It's not hard to remove from the config but if the institutions don't like > it we might as well get it out of there in 1.4.0. > > - Bert > > On 28 Jun 2012, at 15:30, Nicolaas Matthijs wrote: > > Hi everyone, > > There's been many reports of institutions not liking the carrousel > widget and people requesting to disable it. Given that the carrousel > widget as we know it will be disappearing anyway in 1.5, would it be > acceptable to remove the widget as of 1.4? There are a few widgets > specific to the carrousel that could then be removed which will speed > up QA, and eliminating the requests on the landing page will be > helpful for performance as well. > > If there are any -1s, we should probably keep it in 1.4. > > Thanks, > Nicolaas > _______________________________________________ > oae-urg mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-urg > > > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev > > > > _______________________________________________ > oae-urg mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-urg > _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
