2010 July Call

Owned by Jeremy Jeremy
Last updated: Jul 27, 2010 by Dave SteinerVersion comment
2 min read

Logistics

This is a monthly update call open to everyone to discuss the progress being made on OpenRegistry

Time: July 27th, 2010, 1:30pm Eastern
Conference Bridge: (712)432-1600, access code: 548898#

Attendees

Omer, Dave, Mohammed Siddique, Nancy LaParo, Benn Oshrin, Jonathan, Jeremy, Melissa Luck, Ray Davison, Robert Urquhart

Agenda

  1. Update from Rutgers
    • Recent Progress
    • Task Management
  2. Update from SFU
    • Product Backlog
    • Sprint planning
  3. Release Planning

Notes

Rutgers is working on:

  • loading from student SoR
  • initial load of users from the legacy registry (PDB)
  • Bringing new team members up to speed (Mohammed, Nancy)

SFU is working on:

  • Product Backlog is ready
  • Establishing value and effort priorities
  • Within the next couple of weeks tasks will be identified
  • SFU will create Jira Issues for tasks they are working on

Release Planning:

  • tasks should be added to Jira as an accepted standard
  • releases should be identified as describing functionality not necessarily dates
  • 0.x releases are important to keep momentum and signal to the community that development is happening

Benn meets with Penn State and eats ice cream:

  • Benn visited Penn State to discuss IDM
  • Benn ate very good ice cream but not enough of it
  • Penn State is working on a major IDM initiative
  • OR is a good fit for Penn State
  • Topics of interest included:
    • Penn State specific data model requirements
    • Localized reconciliation requirements, OR should have a stock configurable solution with a hook for full customization to hook into legacy systems
    • LOA identity assurance profiles
    • Privacy elements
    • Suggested that validation happen after standardization in the workflow to help validate addresses (Robert from SFU suggests that validation should happen before AND after)
    • Support for non Java languages
    • time based calculations of attributes
    • questions around sustainability of the project, should be answered by Rutgers' new FTEs and SFU's increasing involvement
    • OpenRegistry needs a better name
    • List of features on the side of the box

Discussion of sponsor data model

  • suggestion to roll back the change that moved sponsor information out of the role table
  • the larger issue is the question of who is a sponsor?
  • departments, people or roles can be sponsors
  • discussion about how data model stability relates to releases

Action Items

  • Data model needs to be updated and displayed in somekind of editable format (Jeremy will look at options, open to suggestions)
  • Rutgers to update their release descriptions to accurately reflect the the functionality they will be delivering in December
    • Any functionality or data model changes beyond that will go into a later release/branch
  • Jonathan is going to make sure that there are teleconferencing tools available at the unconference to bring Rutgers in
  • Jeremy to organize an OR meetup on the Wednesday morning/lunch during Educause
  • Jeremy to contact John Fink at RPI and Jens to discuss the ORAC again