[Contrib: Evaluation System] Notice: Merging EVALSYS-861 to trunk?

Jim Eng jimeng at umich.edu
Tue Jun 22 19:41:54 PDT 2010


Based on Sean's response, I guess I don't understand what process was approved.  I am submitting this change for approval even though we agreed on it a few months ago exactly because it was not merged at that time and we now have a more formal process.  So I am saying I would like to go ahead with the proposed change unless there are objections within 48 hours.  I am publishing it to the list as a notice of the proposed change and invitation for comment.  What else do we need to do?

BTW, Matthew Jones reminded me that there is also a ddl change in this ticket.  I will provide sql for the database change.  The ticket already shows the changes in the sql for creation of the database tables. 

Jim   


On Jun 22, 2010, at 5:08 PM, Sean DeMonner wrote:

> Jim,
> 
> At the BoF in Denver last week we discussed a new process for merging changes to trunk; excerpt from notes at http://typewith.me/rN96pc2gJ3 :
> 
> --------------
> Proposal: Apache-style PMC for code changes to trunk (technical leadership). Members have veto power.
> Nominations: Jim Eng (UM), Aaron (Unicon), Rick (UMD), Lovemore (UCT).
> Output of the team: features that go in should be sent to the list as individual emails. Preferably before but definitely when the feature goes in
> -------------
> 
> So let's follow our (new) process and see what that team has to say with regard to merging these changes.
> 
> SMD.
> 
> 
> 
> On Jun 22, 2010, at 4:54 PM, Jim Eng wrote:
> 
>> We discussed this several months ago with general agreement that it would be OK to merge some work done back in February to trunk.  The work is described here:
>> 
>> http://jira.sakaiproject.org/browse/EVALSYS-861
>> 
>> I thought I had merged it, but I just discovered it has not been merged.  
>> 
>> To review, this adds a member variable named "localSelector" to the EvalEvaluation class (along with a setter and getter) and it adds a column in the database for this property in the EVAL_EVALUATION table.  This makes it possible for institutions to set this column in some way (in a provider, for example, or in import code) and then use it to select evals and other entities for export later.  The rest of the EVALSYS codebase ignores this value.  
>> 
>> Michigan has had this change in production since February with no ill effects.  The JIRA ticket indicates that Maryland would like to use this as well, and that Maryland is interested in providing a UI for setting this value when creating or modifying an evaluation, but that work has not been done and is not part of the current proposal. 
>> 
>> As I said, we had approval of this a few months ago, but since the change was not merged to trunk at that time, I thought it would be prudent to announce it again and give 48 hours for comment before merging it to trunk.  So I will merge these changes to trunk unless there are objections before 5 p.m. EDT Thursday.
>> 
>> Thanks.
>> 
>> Jim  
> 
> 
> 
> 
> ==========================================================
> Sean DeMonner, IT Senior Project Manager, CTools Implementation Group
> Digital Media Commons @ The Duderstadt Center, U-M      (734) 615-9765
> 
> 
> 
> 
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/evaluation/attachments/20100622/84ec1d96/attachment.html 


More information about the evaluation mailing list