2011-08-10 Meeting Notes

Owned by Former user (Deleted)
Last updated: Aug 11, 2011Version comment
3 min read

Samigo Working Group Meeting Notes

Date: Wednesday, August 10, 2011
Time:  1-2 pm Eastern Daylight Time (12noon-1pm CDT, 11am-noon MDT, 10am-11am PDT, 6PM BST)
Phone number: (317) 278-7008  Access Code: 850075#
Meeting Prep Documents

Agenda

  • Introductions
  • Logistics: frequency and meeting day/time for future meetings  (Lynn)
  • 2.9 timetable and open questions and tasks (Jackie)
  • Collaborative process for reviewing, vetting, and merging bug fixes for 2.9 (Megan)
  • Collaborative process for proposing, reviewing, and vetting future enhancements (Lynn)
  • Other issues?

Attendance:

  • Lynn Ward, Indiana University
  • Ying Wang, Indiana University
  • Roger Henry, Indiana University
  • Bryan Holladay, Longsight
  • Sam Ottenhoff, Longsight
  • Megan May, Indiana University 
  • Narasi Ramachandran Univ of Florida
  • Jim Mezzanotte, rSmart
  • Trish Harris, rSmart
  • Nathan Finley, University of the Pacific
  • Jackie Krueger, Stanford University
  • Lydia Li, Stanford University
  • Christine Doherty, Stanford University
  • Keli Amann, Stanford University
  • Ken Romeo, Stanford University
  • Karen Tsao, Stanford University
  • Makoto, Stanford University 
  • David Goodrum, Indiana Univeristy 


Meeting Notes:
kick off with introductions

Process for reviewing, vetting, and merging bug fixes

  • IU has a number of bug fixes
  • How to make this a community process
  • For message center, the fix just goes in and left there unless it causes a problem
  • Folks on call should list their fixes on a confluence page
  • Can we arrange for new Jiras not to go to SAK project in Jira.
  • How do we get things in in the long term
  • ACTION ITEM:  IU will collect and post list of samigo bugs listed. 
  • Currently, anyone with a fix attached a patch to JIra and Stanford then does the merge work.  Can we move to a model where other members of the community can merge their own fixes.
  • SAM-1256: remove all references to metadata (Item that Sam is 

Collaborative process for proposing, reviewing, and vetting future enhancements 

  • Stanford is still interested in reviewing everything, but we could look for volunteers to review things.
  • Sign up list for things that need to be reviewed.
  • to do for stanford: add 2.10 page on confluence
  • Lynn mentioned using the minispec from OAE project - would be good for things already done or things that people are thinking about working on
  • SAK-1256:  Remove references to metadata, background colors 
  • There is a ton of code here.  Hard to maintain . ..this is a way to cut down the code and the tool isn't making use of it
  • There is a school that is making use of metadata - hooked it up to a database
  • Lynn suggested making this a r
  • Roger will post use case to item 


Action Items

  • Standford will continue discussion of email options 
  • IU will post list of fixes they have locally that might be candidates for merging into general code base. 
  • Roger will add a use case to SAM-1256
  • Stanford: add 2.10 page on confluence
  • Review 2.9 feature/fix list (all)
  • Sam O.  will create patch for  JQuery work


Future topics:

  • Do we want to continue to align with the Sakai release schedule?
  • Having a testing strategy for 2.9, who can coordinate, who's can be involved?
  • Questions/clarifcations on the 2.9 release