Page tree
Skip to end of metadata
Go to start of metadata


  1. Andrew Woods
  2. Danny Bernstein
  3. David Wilcox
  4. Mike Durbin
  5. Robin Ruggaber
  6. Steve Majewski


11:00am - 11:15am

Welcome and introductions

  1. Name, institution, role on project
  2. High-level description of the pilot
11:15am - 11:35am

Project goals

  1. What is the desired end-state for the pilot?
  2. What goals do we want to achieve?
  3. Are there any concerns about these goals?
11:35am - 12:15pm

Project plan

  1. Timelines and deliverables
  2. Roles and responsibilities
  3. Requirements gathering
12:15pm - 12:25pmBreak
12:25pm - 12:45pm

Project infrastructure

  1. Communication channels and frequency
  2. Issue reporting and tracking
12:45pm - 1:00pmWrap-up and next steps



  1. Introductions & roles
    1. David Lyrasis PI 50%
    2. Robin UVA Lead for managing the UVA work and helping to document outcomes of work
    3. Steve UVA Knowledgeable of content, loading and exporting content from Fedora, testing migrations 
    4. Danny 25% Lyrasis engineer responsible for migration tooling, any needed configurations, and updates to the migration utilities
    5. Andrew 25% Lyrasis Support
    6. Mike UVA History with Fedora, knowledge of content, and author of the former migration platform on which the migration tools were built.
    7. Stan UVA Administration/Resourcing
  2. Overview of Project  & Goals
    1. Grant
      1. migrations from various version and documenting outcomes, updating tools
      2. tested migration toolkit
      3. training 
      4. migration event
    2. UVA
      1. migrating two older Fedora repositories 3.2.1 & 3.4.2 to version 6 which will lower risk and ease evaluation and updates of older content.
  3. Overview of the project plan
    1. UVA will want the infrastructure to be AWS and this seems to be of value to the community.
    2. Verification tools will be used to verify the integrity of the content.
    3. Oct UVA will set up the infrastructure and initial test migrations will inform what content is there, the further work work and documentation
    4. Performance of the migration will be documented as it could be of interest to other people with older versions of Fedora
    5. David will ask people on the tech call about