Time/Place

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

Attendees 

**Each week a meeting chair will be assigned based on a rotating schedule.**

(star) - denotes note taker

🪑 - denotes chair

Agenda 

Agenda

  1. Announcements:
    1. Reminder - no meeting next week (Juneteenth)
  2. Pop-up/Other Topics:
    1. Slack Issues
      1. https://fedora-project.slack.com/archives/C8B5TSR4J/p1749563324719629 - large transaction commit times
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1749648887446299 - replicating S3 buckets
      3. https://fedora-project.slack.com/archives/CKGK2GCR3/p1747998810223739 - auto versioning and time stamps for multiple versions in less than 1 second
      4. https://fedora-project.slack.com/archives/CKGK2GCR3/p1749687904683919 - migration from Fedora 4.7.x to 6.x issues with export?
    2. ldptestsuite - should we drop it, update it, or replace it with more ITs?
      1. Archived since early 2024, "use at own risk", 5 security vulnerabilities, and is forcing us to pull in outdated dependencies
      2. Has it ever caught any bugs?
  3. Migration Updates:
  4. Updates on:
    REMINDER: Need to put tickets in meeting notes to ensure we don't lose information from dynamic filters.
    1. Open Tickets (but assigned in some cases):

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh


    1. In Progress and older but still relevant open tickets:

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

    2. In Review:

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh


    3. Recently closed tickets:  "closed" within "the last 2 weeks"


T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

  1. Dependency Upgrade Project Updates
    1. Consideration for next steps - Community testing process? Does this need to be reviewed?
  2. Backlog Tickets to consider working: N/A
  3. Next Meeting Chair:
    1. Chair: Arran Griffith
    2. Note Taker: Jared Whiklo

See Rotating Schedule here  

Notes

  1. Announcements:
    1. no meeting next week (Juneteenth)
  2. Pop-up/Other Topics:
    1. Slack Issues
      1. https://fedora-project.slack.com/archives/C8B5TSR4J/p1749563324719629 - large transaction commit times
        1. connect to Jira ticket regarding long running transactions by docuteam
        2. might be related to
          1. use of S3 storage
          2. database transaction timing out ( FCREPO-3970 - Getting issue details... STATUS and/or FCREPO-3971 - Getting issue details... STATUS )
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1749648887446299 - replicating S3 buckets
        1. Dan Field does not expect issues
        2. Nobody in today's call seems to have experience with it
      3. https://fedora-project.slack.com/archives/CKGK2GCR3/p1747998810223739 - auto versioning and time stamps for multiple versions in less than 1 second
        1. FCREPO-3864 - Getting issue details... STATUS
        2. Has bee
        3. n discussed already
        4. Limited by Memento spec
        5. Would be possible to change the way Fedora display/names versions
      4. https://fedora-project.slack.com/archives/CKGK2GCR3/p1749687904683919 - migration from Fedora 4.7.x to 6.x issues with export?
        1. Could be related to OCFL needing more storage than Modeshape (used in Fedora 4)
        2. Dan Field will get back to them and try to link with others having similar problems
    2. ldptestsuite - should we drop it, update it, or replace it with more ITs?
      1. Archived since early 2024, "use at own risk", 5 security vulnerabilities, and is forcing us to pull in outdated dependencies
      2. Has it ever caught any bugs?
      3. Shortterm decision: remove test suite
      4. Mid- to longterm options:
        1. completely remove ldp functionality and rely on Fedora API spec only (would allow to drop some code need to support that)
        2. add tests to verify conformance with LDP spec
  3. Migration Updates: no updates
  4. Updates on:
    1. Open Tickets (but assigned in some cases):
      1. No updates on:
        1. FCREPO-4023 - Getting issue details... STATUS
        2. FCREPO-4022 - Getting issue details... STATUS
        3. FCREPO-4021 - Getting issue details... STATUS
        4. FCREPO-4020 - Getting issue details... STATUS
        5. FCREPO-4019 - Getting issue details... STATUS
        6. FCREPO-4007 - Getting issue details... STATUS
      2. FCREPO-4017 - Getting issue details... STATUS not related to upgrade work, can be taken care of after dependency upgrades is finished
    2. In Progress and older but still relevant open tickets:
      1. Open PRs:
        1. https://github.com/fcrepo/fcrepo/pull/2235 reviewed by Jared Whiklo
        2. https://github.com/fcrepo/fcrepo/pull/2225 mariadb integration test failing
        3. https://github.com/fcrepo/fcrepo/pull/2224 seems ok to merbe
        4. https://github.com/fcrepo/fcrepo/pull/2184 tests fail
      2. Open issues: no specific issues discussed
    3. In Review: not discussed
    4. Recently closed tickets:  "closed" within "the last 2 weeks:
  5. Dependency Upgrade Project Updates
    1. Consideration for next steps - Community testing process? Does this need to be reviewed?
  6. Backlog Tickets to consider working: N/A
  • No labels