You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

Attendees

  1. Danny Bernstein   
  2. Andrew Woods

Agenda

  1. Announcements
  2. Fedora 5.1.0  Release 
  3. Update on Fedora 6 Pilots (NLM, Docuteam, UWM)
    1. migration-utils work
      1. Configure "fedora4Client" to new implementation of the Fedora4Client.java interface
      2. Writing to OCFL instead of Fedora4/5/6 API
  4. Sprint Planning
    1. 6.0 Architecture Review
    2. Problems requiring design
      1. Transaction and Lock Management
        1. Transactions scope:  what do we need to support?
          1. Individual Resources
          2. Groups of resources
          3. Containment hierarchies 
        2. Globally accessible state (for horizontal scalability)
      2. Caching/indexing strategy 
        1. What caches and indexes do we need(ie in what layer(s)?)
          1. OCFL client 
          2. Persistence Implementation (OCFL) 
          3. Kernel Implementation
        2. Physical location of the cache (assuming we want to plan for horizontal scalability support)
          1. Cache per instance? 
            1. synchronizing changes across instance
          2. 1 Global cache/index?  
  5. Your topic here...

Tickets

  1. In Review

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

  1.  Folks are largely out today :  just a skeleton crew.
  2. Is it worth exposing an HTTP interface to the OCFL Go client? 
    1. Advantage:  decoupled service that can be used for a variety of purposes, not just Fedora
    2. Disadvantage:  performance could suffer, especially when thinking about supporting S3 (client → http → fedora → http → ocfl → http → S3  =  lots of hops)
  3. migration-utils (f3 → ocfl)  work is moving forward:  Andrew is looking for internally consistent Fedora 3 data sets for testing :  will push something up once he's able to run a successful test.
  4. There is agreement on the team to merge Danny's fcrepo4  PR  that removes modeshape.

Actions


  • No labels