Follow up on Action Items from Last Meeting

• Most AA items were preliminary testing that was completed by 5pm. All but one of the fixes were included.

• (Megan) Follow up on inclusion of

  SAK-9718 - Getting issue details... STATUS
  in next tag

• (Hannah) look into getting the test data required for testing

  SAK-9721 - Getting issue details... STATUS

Action Items from Today's Meeting

Agenda

1. Review of Action items from last weeks meeting
2. Status updates from those in attendance
3. Updates on all open Blockers

• Must be resolved prior to .014 tag

  • SAK-8447 - Getting issue details... STATUS
    Syllabus/ conversion

  • SAK-9106 - Getting issue details... STATUS
    MySQL Conversion

  • SAK-9328 - Getting issue details... STATUS
    Polls / Conversion

  • SAK-9506 - Getting issue details... STATUS
    Announcements / Automaticall create trigger for ScheduledInvocationRunner on init

  • SAK-9668 - Getting issue details... STATUS
    Samigo properties changes to kernel

• Assignments & Site Info:

  • Assignments linked to GB entres created prior to 2.4 need conversion

  • Assignment resubmission does not update after instructor Saves without Returning

  • Site Info / cannot edit roles for provided data

  • Resubmission count updated in odd manner

  • Grades entered in Assignments tool not always transfered to GB}

  • Changes in GB/Assignment association do not always transfer grades to the appropriate GB assignment

4. Updates on resolved Blockers (dynamic list below):

5. Other Updates

• JIRA ??: worksite setup: The new worksite setup stuff has a place where anyone can put in anyone else's account name and see the list of classes that person is teaching. I guess this was put in for assistants to create classes for their instructors, but we don't want that for a number of reasons, until we can control it better as to who sees it for which set of instructors. So, Zhen is going to be putting in a sakai.property to optionally omit that piece from the UI (similar to how the import from file doesn't show up in the site info toolbar based on a sakai.property).

6. Call for inclusions not listed below

7. Focus for next week - GB, Resources, ensure attachment widget works

8. Documentation Update

• 14th for having everything ready for review.

9. When to expect next tag

Release Status Dashboard View

Meeting Notes

Pre-Meeting Camaraderie

Megan: Does anyone want to add anything to the agenda?
Deadair

It's real quiet on the line.

Meeting

Action items from last week

9718: WebDAV, calculating quoting. Disagreement as to whether fix from Ian should be included. It's a temporary fix. No consensus from technical leadership. We should create a patch and put it in the release notes.
Jim: Wants to check with Glenn one more time as a temporary fix, still wants to go in the release. I am happy with Ian's answer. Haven't heard from Glenn yet on the issues he raised.
John: We would have to set our quota to zero.
Jim: Need to check with Linda and Glenn. Can we wait a few hours.
Megan: Unsure of Tagging time. Will coord with Lance, Glenn,...
???: Are the issues in the ticket? We want to make sure everything is documented.
Lance: All discussion is in the ticket and list.
Jim: Temp fix using some caching but is not clustered. Clustering is the issue.
Lance: Based on Ian's comments there don't seem to be any 'serious' clustering issues. Can be worked around with the Event Bus.
Jim: The clustering issue is that sometimes we allow uploads that violoate the quota. Some concern from Glenn about this Hash table potentially getting very big, if not cleaned regularly. Ian thinks this may be resolved. Glenn unsure still.
Those are the big concerns.
Megan: Ok. further questions?
Linda: If this bug effecting the clustering component and we are now exploring a presence problem in our compacity. At the end of the term the clustering mechanism is hurting the app server because of presence. If this is a complication of that, there should be some concern.
Lance: Not related to presence.
Linda: We'll be testing.
Megan: We haven't decided for sure if this is going in. Will be working to see this afternoon if folks are comfortable.

Status from Everyone:

Update from John Leasia: Assignments. Several issues and are concerned and because Zhen (lead dev) is out of town. Hopeful that she can fix these. With respect to the issues, the resubmit checkbox. Feature request to allow students to resubmit after it has been returned to them. <<details>>. Students can keep resubmitting as many times as they want until the end date or it's been graded. We are in a situation with a lot of bugs surrounding this. We need to eliminate for 2.4 the ability to multiple re-submit. A number of bugs rurround it still. In 2.5 this can be fixed with multiple controls. Suggesting approaching this by scaling back this functionality from 2.4.
>>Lance: Looking at the calendar we have 1 QA tag today, and one more opportunity to get stuff in after that. Tag today, and one from the week from today. Need to think about a contingency plan.
>>Megan: Spoke earlier with Chuck and John about who can fix these, if Zhen can't get out of the massive firewall.
>>John: If we completely remove that control takes off the functionality. It could be a contingency.
>>Megan: During testing some inconsistency found. Instructor had to check it once before the student could do multiple resubmissions.
>>John: The bug we are worried about with multiple submit. Student submits, instructors saved, student than can keep resubmitting. There is no indication that the instructor does not see the resubmitting context.
>>Seth: <<Talks really fast: Discussing at what points the resubmitting ability starts and stops>> What are we proposing.
>>John: 1. Resubmit 2. Multiple Revisions Suggesting we eliminate number 2.
>>Seth: Is 1 already existing?
>>John: We want 1 to be globally available not just on a per student page. It might be possible to control this with a simple change with a choice of 1. Set it to zero to dismiss everything.
>>Megan: The documentation was not clear that those submission features were different in the way they function.
>>John: Yeah, wasn't clear at first that the pieces of functionality were different. A late breaking function maxed out the Widget Control.
>>Lance: This is the biggest problem with assignments firhg tnow? Related to any Gradebook Jira?
>>John: I don't believe so.
>>Lance: Last week, the top three items were related to grading activities. Grades are very concerning.
>>Megan Summarizing: