[Contrib: Evaluation System] Additional topics for 06_17_2010 Denver Sakai Conference BoF

[Richard C. Moyer II]

All,

            I would like to discuss the policy for merging local changes into trunk. I believe that some local changes should never be merged back.

            Recently, several additions have been made to trunk based upon local jira tickets - this does not allow for comments from the general community since one cannot view or comment on the ticket.  It's too late to make suggestions once they are in trunk.

            Also, any proposed database modifications should be discussed at the list level.  This will help flush out functionality as well as maintain naming conventions.

            Depending on the size and impact of your changes, a  list discussion should be held.  Who knows, you might get some help or suggestions.  However, current functionally should not be changed without agreement from this list.

            When coding changes, you must remember that there are 3 ways which groups and users are processed by course evaluation and code for all of them.  They are:

Internal sakai sites
Evaluation ad-hoc
Evaluation external providers

            Please remember that at UMD, we are entering our 4th year of production  with this mission critical application.  I find it very frustrating that we must find the new options, retest,  and fix the code at every merge.

Thanks,
Rick Moyer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/evaluation/attachments/20100616/8a765f8f/attachment.html