2012 November Call

Owned by Omer Almatary
Last updated: Nov 28, 2012
2 min read

Logistics

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

Time: 1:30 EST every last Tuesday of every month

If you don't have an invitation you can find a call in number at:

http://apps.calliflower.com/conf/show/163033

And use Quick Pin: 28804

Attendees

  • (Omer, Dave, Sherry, Muhammad ) Rutgers
  • Bill Thompson, Unicon
  • John Finke,  RPI

  • Agenda

  1. JIRA  Issue 
    1. https://issues.jasig.org/browse/OR?selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel
    2. Issues 
      1. Versions
        1. Released 
        2. Archived 
      2. Components
      3. Change Log
        1. Released versions
    3. Reporters (active/inactive)
    4. Assigned to (active/inactive)
    5. Can we group the open items in the archved version into new version? for example create a new release for UI (1.0 UI)?
    6. New release for Incubation Exit?
  2. OpenRegistry Planning Group Meeting

 

Discussion: 

  • The Goal of the JIRA cleanup effort is to reflect the current state of the projects.  
  • In reviewing some of the unresolved JIRA  items , it was noticed that many of these tickets did not have enough details , some are obsolete as the solutions have been already provided and others are documentations related     
  • It was also noticed that some of these issues were reported by  or/and assigned to people   who are no longer active on the project
  • In the Past, The new  Rutgers team archived all of these issues and started  new versioning sequence . In these new version (un archived)  most of the issues are current and majority were resolved and released
  • In cleaning up the unresolved item from the archived versions, we agreed that  we can close all the tickets that are no longer relevant, and move the relevant ones to the next version to resolve them in the possible efficient way 
  • Rutgers will take the lead to do the cleanup since its team is more familiar with most of these items 
  • The next target version of the OpenRegistry is 1.0 . We discussed  if this version #  has any dependency on 1)  Incubation Exit effort 2) Adding the UI competent . The team agree that the most important thing is to get to the most stable version ,that can encourage adapters to start using the product , and it does not have to necessarily tie to exit  incubation or  to complete the UI
  • The team feels strongly  that the product is stable enough to move soon to the next version. Since  August 2012 , the product is  in Rutgers production environment and has been working flawless so far. The Core API , the data model and most of the Rest APi are stable enough to be used in production environments 
  • There is a UI genral code in the Open Source repository , but Rutgers has also shared with Universality of Utah it's overlayed version hoping to have help to get the UI  download able for other adapters 
  • Due to the Rutgers/UMDNJ merger effort , which is pretty aggressive in timeline , the Rutgers IDM team has some challenges in freeing resources to contribute some of the examples including the UI, such as the Camel routing and Batch
  •  The two items that we need to focus on are 1) The Adoption of release Strategy 2) The Quick start 
  • We can  follow other Jasig successful projects (CAS, uPortal)  steps in coming up with the release strategy . Unicon (Bill Thompson) can also volunteer to help with the Quick start 

Notes:

 

 

 

 

 

Â