[Contrib: Evaluation System] Evaluations Preview Changes -- process for merging to trunk?

[Beth Kirschner]

Great!

On Nov 29, 2010, at 12:19 PM, Stephen Marquard wrote:

> The most recent discussion of process was at the Denver BOF:
> 
> http://confluence.sakaiproject.org/display/EVALSYS/06_17_2010+Denver+Sakai+Conference+BoF
> 
> but sadly the typewith.me notes seem to have disappeared though there
> are some references here:
> 
> http://collab.sakaiproject.org/pipermail/evaluation/2010-June/000463.html
> 
> none of which conflict with what you suggest.
> 
> Regards
> Stephen
> 
> 
> -- 
> Stephen Marquard, Learning Technologies Co-ordinator
> Centre for Educational Technology, University of Cape Town
> http://www.cet.uct.ac.za
> Email / IM (Jabber/XMPP): stephen.marquard at uct.ac.za
> Phone: +27-21-650-5037 Cell: +27-83-500-5290 
> 
> 
>>>> Beth Kirschner <bkirschn at umich.edu> 11/29/2010 5:02 PM >>> 
> Hi all,
> 
>   As many of you know, Michigan has a set of enhancements to the
> Evaluations tool that we would like to contribute back to the Sakai
> community. As a relative newbie to the Evaluations group, I'm a bit
> unclear on what the process is for merging enhancements to trunk. There
> seems to be a fair amount of similarity between this group and the OSP
> group (broad base of institutions with broad range of evaluation use
> cases), so I wonder if we should leverage their general process if one
> doesn't already exist?
> 
>   Generally, that process involves:
> 	1) Discuss enhancement with community (i.e. is this a reasonable
> addition? does this meet multiple institutions' needs? should this be an
> optional feature?). JIRA should include enough information to describe
> change, including mockups if appropriate.
> 	2) Minor enhancements can be made directly to trunk, while
> moderate or significant changes should first be developed in a branch.
> This is a subjective assessment that should be determined as part of the
> discussion in step #1.
> 	3) If development was done in a branch, the community will be
> notified when the change is complete and ready for review. After a
> period of review (with any changes/bugs either logged in JIRA or
> resolved as part of the original JIRA), the changes can be merged to
> trunk.
> 
>   Michigan would like to try out this process with
> http://jira.sakaiproject.org/browse/EVALSYS-792, which has been
> discussed at least in JIRA (possibly on the list as well). There seems
> to be interest beyond Michigan on this change, but we'll still make this
> an "optional" new feature, so that the default behavior is not changed.
> Thoughts?
> 
> - Beth
> _______________________________________________
> evaluation mailing list
> evaluation at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/evaluation
> 
> TO UNSUBSCRIBE: send email to
> evaluation-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> 
> 
> 
> 
> 
> ###
> UNIVERSITY OF CAPE TOWN 
> 
> This e-mail is subject to the UCT ICT policies and e-mail disclaimer
> published on our website at
> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from
> +27 21 650 9111. This e-mail is intended only for the person(s) to whom
> it is addressed. If the e-mail has reached you in error, please notify
> the author. If you are not the intended recipient of the e-mail you may
> not use, disclose, copy, redirect or print the content. If this e-mail
> is not related to the business of UCT it is sent by the sender in the
> sender's individual capacity.
> 
> ###
> 
> 
>