[Contrib: Evaluation System] EVALSYS Merge Process & Plan
Aaron Zeckoski
aaronz at vt.edu
Tue Sep 1 07:05:21 PDT 2009
> 2. The ability to import/export institutional specific scales/items/etc
> (i.e. customizing the preload) I believe there is a JIRA suggesting an xml
> format. I’ve started working on one and I think U-M has as well. Is it worth
> to standardize this?
Yes please. Great suggestion.
-AZ
On Tue, Sep 1, 2009 at 2:40 PM, Richard C. Moyer II<rmoyer at umd.edu> wrote:
> I’d like to suggest a few other agenda items for this chat or future ones
>
>
>
> 1. There’s been recent mention of tagging eval-1.2.2. What should be
> included, timelines, etc….
>
>
>
> 2. The ability to import/export institutional specific scales/items/etc
> (i.e. customizing the preload) I believe there is a JIRA suggesting an xml
> format. I’ve started working on one and I think U-M has as well. Is it worth
> to standardize this?
>
>
>
> Rick.
>
>
>
>
>
>
>
> From: evaluation-bounces at collab.sakaiproject.org
> [mailto:evaluation-bounces at collab.sakaiproject.org] On Behalf Of Sean
> DeMonner
> Sent: Tuesday, September 01, 2009 8:54 AM
> To: evaluation at collab.sakaiproject.org; Jim Eng; Aaron Zeckoski; Ellen Yu
> Borkowski; Richard Ellis; John Leasia; Stephen Marquard
> Subject: Re: [Contrib: Evaluation System] EVALSYS Merge Process & Plan
>
>
>
> Oops, it was pointed out to me that there may be a conflict with the Sakai
> 001 room on the teleconference so I'm moving this meeting to Sakai 002:
>
>
>
> Name: Sakai002 - Ad-hoc
> Telephone: +1-812-856-7060
> Internet:156.56.240.9
> Conference Code: 350#
> PIN: 72524#
>
>
>
> Sorry for the confusion.
>
>
>
> SMD.
>
>
>
>
>
>
>
> On Aug 31, 2009, at 4:36 PM, Sean DeMonner wrote:
>
> All,
>
>
>
> it looks like the earliest time when most of the folks can meet on this
> topic is Thurs 9/3 at 11 am EDT (there was no time when everyone was
> available so I grabbed the best, earliest spot). I've reserved the Sakai
> conference bridge for this meeting.
>
>
>
> Name: Sakai001_Scheduled
> Telephone: +1-812-856-7060
> Internet:156.56.240.9
> Conference Code: 348#
> PIN: 72524#
>
>
>
> See below for draft agenda.
>
>
>
> SMD.
>
>
>
>
>
>
>
>
>
>
>
> On Aug 28, 2009, at 2:19 PM, Sean DeMonner wrote:
>
> Sakai EVALSYS Users,
>
>
>
> This week there has been some off-list discussion about efforts to merge
> changes from a local branch (specifically the U-M branch) back to the 2.6
> EVALSYS trunk and how that work should be orchestrated with the rest of the
> community. Branch management was a topic at the Boston conference BoF where
> we agreed that regular meetings (monthly?) would be desirable in order to
> coordinate the work occurring at the disparate institutions. This email is
> an attempt to schedule the first of those technical meetings.
>
>
>
> Please indicate at the following Doodle poll your availability to attend a
> conference call:
>
>
>
> http://doodle.com/ckzgz3rhwshafhxq
>
>
>
> I will send out a meeting confirmation next week once we have a critical
> mass that can settle on a time. There is some urgency around this effort for
> all of us (not just U-M), so please plan to attend if possible.
>
>
>
>
>
> ---------------------
>
> Proposed Agenda:
>
>
>
> 0. Context and Boston follow-up
>
> http://confluence.sakaiproject.org/x/3ADNAw
>
>
>
> 1. Review of proposed U-M merges (see excerpt of earlier message from Jim
> Eng below; please *preview* the proposed changes before the meeting)
>
> - http://tinyurl.com/nv62l2 (screencast of U-M changes for
> context)
>
>
>
> 2. Pending merges from other institutions
>
>
>
> 3. Next steps:
>
> - next technical/merge coordination meeting
>
> - progress on product/project management coordination effort?
>
> ---------------------
>
>
>
>
>
> Thanks.
>
>
>
> SMD.
>
>
>
>
>
>
>
>
>
> On Aug 27, 2009, at 3:34 PM, Jim Eng wrote:
>
> Sorry. I wasn't at the meeting in Boston because I had to leave the
> conference early. I understood from Aaron that we were to merge to trunk.
> I have been creating branches to work on particular features. Once all the
> details have been worked out, I have been merging from there to trunk. I
> have done this with four features so far. In each case, there is a setting
> to enable/disable the feature or capability and the default setting makes no
> change in any behaviors or user-facing components. Here are the tickets
> that have been merged to eval trunk:
>
>
>
> http://jira.sakaiproject.org/browse/EVALSYS-769
>
> http://jira.sakaiproject.org/browse/EVALSYS-767
>
> http://jira.sakaiproject.org/browse/EVALSYS-788
>
> http://jira.sakaiproject.org/browse/EVALSYS-787
>
>
>
> I will be glad to participate in the meeting. If need-be I could back out
> these changes in trunk, but I would prefer not to. It's very easy for a
> branch to become stale so it's very hard to merge back to trunk. We believe
> these are features or capabilities other people will want, so I would prefer
> to continue getting them into trunk when we are ready to merge them, unless
> that creates a problem for anybody.
>
>
>
> Jim
>
>
>
>
>
> ==========================================================
>
> Sean DeMonner, IT Senior Project Manager, CTools Implementation Group
>
> Digital Media Commons @ The Duderstadt Center, U-M (734) 615-9765
>
> Pub Key 24DD6B09
>
>
>
>
>
>
>
>
>
>
>
>
>
> SMD.
>
>
>
>
>
> ==========================================================
>
> Sean DeMonner, IT Senior Project Manager, CTools Implementation Group
>
> Digital Media Commons @ The Duderstadt Center, U-M (734) 615-9765
>
> Pub Key 24DD6B09
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> SMD.
>
>
>
>
>
> ==========================================================
>
> Sean DeMonner, IT Senior Project Manager, CTools Implementation Group
>
> Digital Media Commons @ The Duderstadt Center, U-M (734) 615-9765
>
> Pub Key 24DD6B09
>
>
>
>
>
--
Aaron Zeckoski (azeckoski (at) vt.edu)
Senior Research Engineer - CARET - University of Cambridge
https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski
http://aaronz-sakai.blogspot.com/ - http://tinyurl.com/azprofile
More information about the evaluation
mailing list