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

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

Compare with Current View Page History

« Previous Version 4 Next »


Time: 11:00am Eastern Time (US)

Please see calendar invite for Zoom link.


  1. Andrew Woods
  2. Danny Bernstein
  3. Rosalyn Metz
  4. Ben Pennell
  5. Jennifer Gilbert
  6. Jared Whiklo
  7. Dan Field
  8. Dan Coughlin
  9. Oliver Schöner
  10. Peter Winckles
  11. Scott Prater
  12. David Wilcox
  13. Mark Jordan
  14. Kathryn Michaelis
  15. Arran Griffith
  16. Melissa Anez
  17. Dustin Slater
  18. Aaron Birkland


  1. Ensure alignment between Committer and Leadership teams on technical priorities/direction
  2. Establish final plans for initial F6 Alpha/(Beta?) release



  1. Leadership/Governance updates?
  2. Technical updates since previous meeting
  3. Final plans for Alpha (Beta?) release
    1. Criteria (see below)
    2. Timing 

Alpha Criteria

  1. (tick) Almost or mostly feature complete
  2. (tick) Migration tooling for F3, F4 and F5 → F6
  3. Documentation
    1. Documented API compliance of Alpha
    2. Documented missing features of Alpha
    3. Documented breaking changes of Alpha
    4. Documented upgrade process of Alpha

Beta Criteria

  1. Feature complete
    1. API test suite fails (Indirect Containers, State tokens, etc)
    2. Minimal Search Service UI
    3. Performant rebuild
    4. Side-loading / targeted rebuild
    5. Performant S3 integration (question)
  2. Performance criteria (question)
    1. Scale
    2. Response times underload
    3. Migration rates
  3. Documentation
    1. Documented API compliance of Beta
    2. Documented missing features of Beta
    3. Documented breaking changes of Beta
    4. Documented upgrade process for Beta



  • Folks introduced themselves
  • Purpose of meeting is to keep governance to keep governance and technical groups in sync


  • Tech team has been working on performance, metrics.  The dashboard has been a valuable tool
  • Updates to the user interface and API
  • Integration from S3 has been brought in
  • Work on tweaking mementos
  • Work around migration tooling has been an a highlight
    • tooling for migrating from 3,4,5 has been a prerequisite for alpha, all are usable now.
  • Docker containers and automation
  • Work making Fedora cross-database compliant (postgres, mariadb, mysql)
    • Travis runs suite of integration tests across all DBs
    • Putting energy into postgres
    • Postgres is usually the best/fastest/most reliable choice
    • Should we focus intense optimizations to other DBs?
    • Islandora folks might use mariadb more often "by default"
    • Samvera is likely to go postgres
    • --- pause for zoom technical difficulties ---

    • Should there be a recommendation/warning for islandora folks who would tend to use mysql based on Drupal?
      • Difference is not large/horrible; postgres is just slightly faster in general 
  • Validation tool designed, scheduled for January 
    • Bidirectional verification:  Is there anything in fcrepo3 that hasn't been migrated; is there anything in fcrepo6 that didn't come from fcrepo3

Alpha and Beta releases

Conversation focus: What are the blockers and timing?

  • We are extremely close to an alpha
    • Migration tooling is "alpha" ready, a couple outstanding PRs remain
    • Fcrepo6 is mostly feature complete (beta will be fully feature complete)
  • Given the fact that we are mostly feature complete, have migration, and have documentation; are there any barriers to an alpha?
    • What are the criteria from alpha->beta→6.0?  
      • We assume there will be people testing alpha and filing bug reports, providing feedback.  Is this true?  Does this help when we determine from alpha to beta?

      • Andrew:  Think of alpha→beta as a matter of feature completeness.  Beta will be feature complete, and ready to test in institutional environments.  Not sure how much we can rely on early feedback in the alpha phase.
        • Thinking the transition from alpha to beta will be quick; beta to 6.0 is more rigorous.
    • Do we agree with the "Beta Criteria" listed on this wiki?
      • Add Object locking:  two people on the same object.  Right now, second person editing a contended object gets rejected.  Want to fix that
      • Validation tool in some state of beta
      • Feasible to test integration with Samvera or Islandora?  
        • Samvera is diverse.   Hyrax, Avalon, and Hyku have their own needs.  Not so simple to say "hey, can you see it it works?".  However, there is an initial proposal for a hyrax grant submitted which might have some fedora 6 migration work included in it.  
        • Islandora could do sanity check, but probably not scale check
          • Dustin Slater interested in helping with such a check
        • We want to make sure that nothing is broken as far as APIs staying substantially the same
  • It would be desirable to get a beta out this calendar year.  Feasible to get alpha after next week's sprint.  If we're just talking about feature completeness, a November beta might be possible.  Given validation and integration testing, that might make 2020 harder to hit.  Is that a concern?
    • Scott:  comfortable with alpha now,  Time lag between alpha and beta is not a bad thing, 1Q 2021 is reasonable.
    • David W:  Concern from grant perspective.  It's OK to start at alpha state, but we do need to move these pilots into production.  Planned for beta in 2020, full release early 2021.   There is risk of delaying too long.  Not sure we agree on what Beta is
    • Andrew: Could do DSpace approach of Beta1, Beta2, Beta3, etc... 
  • Anything concerns/interest in S3 integration?
    • Fcrepo5 used S3 as binary store (only).  F6 uses it for everything (objects, binaries, manifests, etc).  Need to characterize what that means in real life.

Action Items 

  • Type your task here, using "@" to assign to a user and "//" to select a due date
  • No labels