[sakai2-tcc] [Building Sakai] Assignments Shows Wrong Submission For Student

[Beth Kirschner]

On Mar 5, 2013, at 2:13 PM, Matthew Jones <matthew at longsight.com> wrote:

> 
> Some questions I guess.
> 	• Is Michigan still providing support for A1 or is it (like nearly every other tool) being dropped onto the CLE Team? The default assignee is "Umich Developers" and many are assigned as such but some tickets are being reassigned to CLE Team or others. (This doesn't matter to me either way, just if Michigan isn't exclusively supporting this as in the past it makes more of a case for replacement)
Michigan hasn't dropped support for 'nearly every other tool', though perhaps what you really meant to say is that nearly every other tool is now supported by the CLE team, which has been discussed as the preferred direction (from my recollection), and that developers shouldn't consider themselves "silo'd" in their support of a single tool.

Michigan continues to be listed as the default JIRA assignee for a few tools (e.g. Assignments, Site-Manage), and I've been taking the effort to triage new tickets assigned to Michigan and if it's not critical and/or not something we can work on in the near-term, I've been re-assigning them to the CLE team. This doesn't mean we're not supporting these tools, but instead we're broadening the scope of our Sakai support. We have several new features in development or already checked in for the site-manage tool (e.g. SAK-22450 and SAK-16600), as well as active support in the Kernel, Announcements and Basic LTI, Portal, user-preferences, and contrib tools. 

We could remove Michigan as the default assignee for any Sakai tools, but I feel there is benefit to the community to triage these tickets. What other institutions are doing this? Neal has been quietly asking some TCC members to review outstanding JIRA tickets (including myself), and perhaps we should change the expectation of the default JIRA assignee to be the person/group who triages the tickets rather than the one who is silo'd in support of only that tool? This might be a path to getting more tickets reviewed and re-assigned to people or institutions who have can more quickly work on them?

There's also benefit in an honest assessment of how much Michigan can actually do, and if there's room for the community to step in, I think it's helpful to be clear as to where that help can/should be focused.

> 	• Is IU or anyone else other than Longsight still interested in working on getting A2 into core? Either technical (development/UI work) or non-technical (gap analysis/filing issues) help would be useful.
> There were nearly 25 people in the session at the last conference, and I was reluctant to hold another similar one because of the lack of progress or anything new to report.
> 
I think the last conference showed there was significant interest in having just one Assignments tool, but no-one seemed able to contribute the resources to close the gap between the two tools (everyone seemed to walk away from that BOF thinking 'the other guy' was going to work on it). Frustrating for all, and perhaps worth another BOF to re-frame the question of not who would like to see this happen but who has resources they can commit to a cross-institutional team that would work on this. Would Longsight be willing to coordinate this effort?

- Beth

> 
> 
> On Tue, Mar 5, 2013 at 1:46 PM, Charles Severance <csev at umich.edu> wrote:
> 
> On Mar 5, 2013, at 11:52 AM, Matthew Jones wrote:
> 
>> I reported this ticket a few days ago, sounds similar:
>> https://jira.sakaiproject.org/browse/SAK-23247 (When grading students, if you press the back button, some of the form is incorrect)
>> 
>> I spent about an hour looking at the code and couldn't see where this was happening. We were just going to add a lock on the back button to avoid it being used as that was the only way I could reproduce this. It's got to be something with the state and context not being in sync.
> 
> Is it time to bite the bullet and take this stuff out of state in Assignments???
> 
> /Chuck
> 
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc