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


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


  1. Danny Bernstein  
  2. Daniel Lamb 
  3. David Wilcox
  4. Jared Whiklo
  5. Ben Pennell (star)
  6. Yinlin Chen
  7. Peter Eichman
  8. Bethany Seeger 
  9. Joshua Westgard


  1. Announcements
  2. Fedora 5.1.0  Release
    1. RC 3?
  3. Import Export
    1. 2 PRs need some attention:
  4. Drastic Test Suite Results
  5. Fcrepo4-docker:
    1. PR need review: 
  6. Fedora 6.0.0 Sprint Planning Page
    1. The plan for the master branch 
    2. Pre-Sprint Tasks:   
      1. Update on Remove all JCR dependent code
      2. Defining fcrepo-persistence-api
      3. 6.0 Architecture Review


  1. In Review

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due

  2. Please squash a bug!

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  3. Tickets resolved this week:

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  4. Tickets created this week:

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution


Fedora 5.1.0 release

  1. The Windows issue has been resolved, the commit that resolved the issue was made to 5.0.2 but needed to be ported to master
  2. Danny is going to put out release candidate 3, we will then run through a manual test on linux
    1. Danny Lamb will test in islandora, Esme will (hopefully) test with valkyrie.
    2. What is the minimum amount of time for a release candidate?
      1. Jared will send out an announcement today indicating that unless any new issues are found, it will be released on the following Friday (July 26)


  1. Roundtripping implemented, PRs need to be reviewed
    1. Ben will look at PRs
  2. Will then need to do community testing
    1. Would anyone be interested in a 4 to 5 migration test?
      1. Josh Westgard is interested in this. Actual production migration they would likely wait for 6, but they are willing to test this.
      2. Danny and Josh will be in contact about testing things

Drastic Test Results

  1. Greg set up instance of DRASTIC, Andrew ran the test suite against it. 45% of MUSTs passed
    1. Should we attempt to do anything about this?
      1. Josh - It should continue to be a goal to push towards having a second implementation. They had a grant to explore the Fedora API on top of DRASTIC.
      2. Peter - there are a lot of MUST failures around digest processing. Is this a limitation of the cassandra backend?
      3. Jared - there are 28 WebAC failures, so that is probably the largest section
    2. Reach out to Greg to see if there is any intention of pursuing these. Try to determine if any of these are resolvable or if they are architectural mismatches.
    3. Josh - check with DRASTIC and Trellis people to see their opinions on the failures
    4. Danny will reach out to Greg


  1. Yinlin needs someone to review a PR, it adds in camel tools
  2. Danny will take a look, Josh will also try running the docker script, Aaron can also try today or tomorrow

Fedora 6 Sprint planning

Plan for master branch

  1. Discussed creating a fedora 6 overhaul branch, keep master in working state until build and test pass
    1. Decided to go with master as the main line of development branch, even though it won't build
    2. Email the tech list about this decision for informational purposes

Pre-sprint tasks

  1. Danny has started on the demolition, about halfway there.
    1. Removed the modeshape kernel module from the project pom
    2. Been moving Exception classes out to the API module where appropriate
    3. Hasn't revolutionized his understanding of what changes we'll need to make to the codebase for 6.0 yet.
    4. Once this is done, it will be merged into master. Should be next week.
  2. fcrepo-persistence-api is awaiting someone to come along and try to figure out what the API is for a persistence layer
  3. Most likely others will need to wait until after the demolition to start collaborating.
  4. Architectural diagrams, very tentative, how should we proceed with these?
    1. Current plan is to use Aaron's OCFL client as a placeholder, possibly for the final project depending on how well it works.
    2. Aaron take people through the client in the committer's call.
    3. This page can be a good place to use as a white board for gathering ideas
    4. Aaron - Once we start creating the APIs it should be easier to start commenting on it and the bigger picture.


  • No labels