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

  1. Announcements:
    1. Fedora User Group Gathering - Open Repositories, Chicago, IL
  2. Pop-up/Other Topics:  
    1. Dependency Upate Planning
      1. Next Steps: Code Coverage Review and Updates
        1. Proposal to tackle this in sprints beginning in the first week of April
        2. Arran to handle communications and outreach for participation
    2. Slack Messages
      1. https://fedora-project.slack.com/archives/CKGK2GCR3/p1740406632769799 - removing unwanted data streams during migration
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1740423074388599 - specifying parameters in fcrepo.properties
    3. Google Tech List
      1. https://groups.google.com/g/fedora-tech/c/XwV-WRecV_0 - IAM role for S3 access instead of AWS credentials?
  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
      Refresh

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

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

    3. In Review:

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

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

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

  5. Backlog Tickets to consider working: N/A
  6. Next Meeting Chair:
    1. Chair: Ben Pennell  (swap with Demian Katz as he's likely out for his first of the month other meeting?)
    2. Note Taker: Dan Field 

See Rotating Schedule here  

Notes

  1. Announcements:
    1. Fedora User Group Gathering - Open Repositories, Chicago, IL
    2. Arran Griffith and Dan Field will be atOpen Repositories
    3. Second intro to Fedora Workshop: 130 registrations so far
  2. Pop-up/Other Topics:  
    1. Dependency Upate Planning
      1. Next Steps: Code Coverage Review and Updates
        1. Proposal to tackle this in sprints beginning in the first week of April
        2. Arran to handle communications and outreach for participation
        3. Aim: ~ 80 % code coverage
        4. Board to track work regarding dependency updates: https://github.com/orgs/fcrepo/projects/5/views/1
        5. Tech meeting will be repurposed to live working session during sprints
        6. Problably separate meetings at beginning, in the middle and at end of sprints
        7. Dedicated sprint channel in Slack
    2. Slack Messages
      1. https://fedora-project.slack.com/archives/CKGK2GCR3/p1740406632769799 - removing unwanted data streams during migration
        1. concerns Fedora 3
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1740423074388599 - specifying parameters in fcrepo.properties
        1. Wanted to know the format of the properties file: conforms to standard Java properties file
    3. Google Tech List
      1. https://groups.google.com/g/fedora-tech/c/XwV-WRecV_0 - IAM role for S3 access instead of AWS credentials?
        1. Fedora should support using IAM roles (unclear if this needs changes in Fedora source code) → we'll be implemented after dependency updates 
  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):
      1. FCREPO-3996 - Getting issue details... STATUS Deployment is currently broken, Dan Field is looking into it; unclear how much people are actually using the Javadocs.
        Won't be updated in the future, existing Javadocs will be kept online
        Dan Field will update the release documentation
      2. FCREPO-3987 - Getting issue details... STATUS We'll be tackled after release of Fedora 7
      3. FCREPO-3971 - Getting issue details... STATUS FCREPO-3970 - Getting issue details... STATUS No decision on how to tackly these, both will not be tackled before Fedora 7
      4. FCREPO-3910 - Getting issue details... STATUS No updates, can likely be closed for now
      5. FCREPO-3962 - Getting issue details... STATUS Will be tackled by dependency update sprints
    2. In Progress and older but still relevant open tickets:
      1. FCREPO-3992 - Getting issue details... STATUS
      2. FCREPO-3963 - Getting issue details... STATUS Related to dependency updates
      3. FCREPO-3931 - Getting issue details... STATUS
    3. In Review:
      1. FCREPO-3997 - Getting issue details... STATUS
      2. FCREPO-3988 - Getting issue details... STATUS
      3. FCREPO-3968 - Getting issue details... STATUS Dan Field will review it
    4. Recently closed tickets:  "closed" within "the last 2 weeks"
      1. Lot of tickets regarding dependency updates have been closed
      2. Question how to handle work, that's been tackled with Github issues instead of Jira tickets
        1. Ideas:
          1. Sync data between Jira and Github using a plugin
          2. Use a single Jira ticket and link all PR to it for
            1. Dependeny updates
            2. Code coverage
            3. Suggestion by Ben Pennell "I wonder if we could put a tag on the GitHub issues that belong to a particular jira ticket (like the epic), and then in Jira we just link to a query for all the issues with that tag"
              → Will most likeyl be chosen as solution
  5. Backlog Tickets to consider working: N/A


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.