[WG: Sakai QA] [cle-release-team] Additional Sakai 10 property questions

[Matthew Jones]

I missed the call because of local issues but here are my thoughts

1) This was recommended back on
https://jira.sakaiproject.org/browse/SAK-18799.

I noted 5 jiras that are limitations with this functionality that would
either be fixed or should be mentioned to the user as limitations so there
isn't and confusion when it didn't work correctly. 2 of those issues have
been closed since as "Won't Fix", 3 of them are still open. The last one is
the only one I can see as a potentially easy fix.

- The calendar import will skip the import of any individual full day
events, re-occurring events, events without an end time and events in
shared calendars provided without full details (free/busy style in Google
calendars)
- It was recommended also on that ticket that this feature could also
introduce a potential performance issue, though a lot of events imported
into a schedule would probably have the same effect right now.

2) This option has historically been a performance problem in the past,
sometime contributing up to 15-20% additional database load since the
presence information is updated and queried on the database rather than via
something like JMS. There are ways to adjust this, and I think it should be
mentioned, but I'd probably also be concerned about performance, especially
in large classes. We could mention it in the documentation though.

3) This was turned off in the past because it queried the events tables
directly, which resulted in poor performance, and many institutions
warehouse that data so it was limited. There also wasn't support for
Oracle. Steve added this support for 10 (
https://jira.sakaiproject.org/browse/STAT-299 /
https://jira.sakaiproject.org/browse/STAT-330) so is something that I would
be okay with re-enabling and testing, though previous semesters data would
still be missing for schools that clean up their events table.


On Fri, Jan 10, 2014 at 10:17 AM, Neal Caidin <neal.caidin at apereo.org>wrote:

> Hi All,
>
> By default, we are now turning on features by default [a]. However, in
> QA testing we ran into a few properties that are not turned on by
> default and prevented us from verifying some Jiras.
>
> 1) Proposal: Turn on ical.experimental to true by default, and change
> the name to calendar.ical.enabled ?  This seemed to be the sense of
> folks attending the Sakai release team meeting. It appears to have been
> in experimental status for about 5 years [b]
>
> 2) Keep enableSitePresences at org.sakaiproject.sitestats.api.StatsManager
> off by default? Turning it on would also require
> display.users.present=true [c].  There were mixed comments about whether
> to turn this on by default. The concern raised is that this has
> potential performance and security issues, which based on our criteria
> would mean that this should stay off by default.
>
> 3) serverWideStatsEnabled at org.sakaiproject.sitestats.api.StatsManager
> keep default off?   Couldn't find much documentation on this one [d]
>
>
>
> [a] Decision for Properties : "We plan on turning on all new features
> for Sakai 10 in source code, by default, except for features with
> performance or security concerns, or settings which are too ambiguous to
> guess at a standard need across institutions."
>
> [b] ical.experimental -
> https://confluence.sakaiproject.org/display/SCHED/Home?src=search
>
> [c] enableSitePresences at org.sakaiproject.sitestats.api.StatsManager -
>
> https://confluence.sakaiproject.org/display/STAT/Configuration+Options?src=search
>
> [d] serverWideStatsEnabled at org.sakaiproject.sitestats.api.StatsManager
> - https://jira.sakaiproject.org/browse/STAT-61  and a comment on
>
> https://confluence.sakaiproject.org/display/STAT/Configuration+Options?focusedCommentId=68162034#comment-68162034&src=search
>
>
> Thanks,
> Neal
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
> _______________________________________________
> 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/sakai-qa/attachments/20140110/4474ed31/attachment.html