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

Agenda

  1. Announcements:
    1. Release Candidate Announcement
  2. Pop-up/Other Topics:
    1. OAI-PMH work
      1. Looking to begin scoping this work out
    2. Future of Fedora Technology Info Gathering Sessions
      1. Proposed Dates:

        1. New Users/Fedora 3 or earlier users):

          North American Time Zones

          Wed. April 12 @ 1pm Eastern

          Wed. May 17th @ 1pm Eastern

          EU/UK Time Zones

          Fri. April 21 @ 9am Eastern

          Fri. May 19 @ 9am Eastern

        2. F6 Users

          North American Time Zones

          Mon. June 5th @ 12pm Eastern

          EU/UK Time Zones

          Mon. June 12 @ 9am Eastern


    3. Google Groups Message - https://groups.google.com/g/fedora-community/c/z8RN9JyvzDI
  3. Migration Updates:

  4. Updates on:

    1. Open Tickets (but assigned in some cases):
      1. FCREPO-3878 - Getting issue details... STATUS
      2. FCREPO-3875 - Getting issue details... STATUS
      3. FCREPO-3870 - Getting issue details... STATUS
      4. FCREPO-3866 - Getting issue details... STATUS
      5. FCREPO-3865 - Getting issue details... STATUS
      6. FCREPO-3864 - Getting issue details... STATUS
      7. FCREPO-3855 - Getting issue details... STATUS
      8. FCREPO-3850 - Getting issue details... STATUS
      9. FCREPO-3849 - Getting issue details... STATUS
      10. There are a pile of older open tickets that may need to just be closed (ie. 3854, 3851, 3852, 3853)
    2.  In Progress and older but still relevant open tickets:
      1. FCREPO-3876 - Getting issue details... STATUS
      2. FCREPO-3874 - Getting issue details... STATUS
      3. FCREPO-3873 - Getting issue details... STATUS
      4. FCREPO-3871 - Getting issue details... STATUS
      5. FCREPO-3868 - Getting issue details... STATUS
    3. In Review:
      1. FCREPO-3867 - Getting issue details... STATUS
      2. FCREPO-3841 - Getting issue details... STATUS
      3. FCREPO-3839 - Getting issue details... STATUS
      4. FCREPO-3834 - Getting issue details... STATUS
      5. FCREPO-3830 - Getting issue details... STATUS

  5. New tickets:

      1. None

  6. Backlog Tickets to consider working:
  7. Next Meeting Chair:
    1. Chair: Ben Pennell
    2. Note Taker: Jared Whiklo
    3. See Rotating Schedule here 

Notes


  1. Announcements:
    1. Release has been announced
      1. James reports the new release builds fine
  2. Pop-up/Other Topics:
    1. OAI-PMH work
      1. Some community members report interest
      2. Baked-in to Fedora or extension?
      3. Next step?  Perhaps hold a design meeting to scope.  Arran will coordinate.
        1. For example, what is a set?  Depends on end user.  Configure?
      4. What is the use case?  May make more sense to be in the system in front of Fedora, instead of Fedora itself.
        1. NLWR has a need for this within Fedora
        2. NLM would like as a nice to have, doesn't matter where in the stack
        3. Villaonva uses VueFind in front of Fedora, that has OAI-PMH built in
        4. UNC has OAI-MPH at app level, not in Fedora
        5. European customers often interested
    2. Future of Fedora Technology Info Gathering Sessions
      1. Governance seeking to look back into community to get people to Fedora 6 to gather feedback on what's working, what's not working.
      2. What pain points exist currently?  What do people like and dislike about Fedora? 
      3. Use for future tech roadmapping. 
      4. Looking for committer / tech representation in meetings, in addition to governance, to listen to conversations
    3. Tombstone version info
      1. John G. reports a versioning issue with ArchivalGroups, will write a ticket. Could be a new feature request. 
      2. Can you get to a version of an object that's been deleted?  How to get past the tombstone?  
      3. Access timemap to provide info on old version?  The info should still be there in OCFL
    4. RO filesystem issue reported on Google groups
      1. https://groups.google.com/g/fedora-community/c/z8RN9JyvzDI
      2. Fedora 6.3 with Tomcat 9 - RO filesystem errors - permissions problem?
      3. Could be SE Linux permissions
      4. Recommend to open permissions temporarily (777) and test
      5. Dan will follow up with user
  3. Migration Updates:
    1. NLM - starting testing migration again, Fedora 3 to 6
      1. Using migration tool 6.3.1 and validation tool 1.3.0
      2. Trying out in on-prem Linux VM and also probably AWS
    2. NLW - fixing metadata issues pre-migration, scripting to fix 

  4. Updates on:

    1. Open Tickets (but assigned in some cases)
      1. FCREPO-3878 - Getting issue details... STATUS - Dan started looking at.  Is this a use case we want to pursue?  Perhaps wrap in flag because not everyone has DC or will want to migrate it
      2. FCREPO-3875 - Getting issue details... STATUS - we have to do it.  Put, delete, purge, put again.  Causes issue with ArchiveGroups.  
      3. FCREPO-3870 - Getting issue details... STATUS - BagIt Java still maintained?  Still in git but no commits for a few years.  Was set as trivial.
      4. FCREPO-3866 - Getting issue details... STATUS
      5. FCREPO-3865 - Getting issue details... STATUS - Dan's request.  More complicated than initially thought, may not be high priority compared to other tickets.
      6. FCREPO-3864 - Getting issue details... STATUS - Should we version sequentially instead of by second?  Seems useful, but need someone to have time to work on it.  Either current impl or proposed new impl could confuse people.  Ask people to vote on tickets so we can understand which tickets have more popular support.
      7. FCREPO-3855 - Getting issue details... STATUS - Dan notes there is a workaround for now
      8. FCREPO-3850 - Getting issue details... STATUS - docker, wait for Thomas to analyze
      9. FCREPO-3849 - Getting issue details... STATUS - docker, wait for Thomas to analyze
      10. There are a pile of older open tickets that may need to just be closed (ie. 3854, 3851, 3852, 3853)
        1. 3851 - docker related?  tomcat cleanup when stopping docker.  Minor issue.  dupe, retest?  Jared will take
        2. 3852 - needs followup to see if it is really fixed?  Can be closed, seems fixed.  Needs to be retested.  Jared will close.
        3. 3853 - another docker compose problem.  Intermittent, Mike couldn't replicate.
        4. 3854 - release migration validator, nothing in ticket but title.  Mike closed.
    2.  In Progress and older but still relevant open tickets:
      1. FCREPO-3876 - Getting issue details... STATUS - 
      2. FCREPO-3874 - Getting issue details... STATUS - Jared still has to do
      3. FCREPO-3873 - Getting issue details... STATUS - Mike has an integration test
      4. FCREPO-3871 - Getting issue details... STATUS - Dan - leave so we can document as we find
      5. FCREPO-3868 - Getting issue details... STATUS - Dan hasn't had chance to test yet
    3. In Review:
      1. FCREPO-3867 - Getting issue details... STATUS  
      2. FCREPO-3841 - Getting issue details... STATUS - probably don't want this for all requests.  See comment below for 3839.
      3. FCREPO-3839 - Getting issue details... STATUS - Jared looked at banner tickets - who should do?  Need governance opinion on what pages should receive text header.  Seems OK to keep on HTML UI but don't want to bombard everyone on all requests.
      4. FCREPO-3834 - Getting issue details... STATUS - Jared will look at
      5. FCREPO-3830 - Getting issue details... STATUS - Jared hasn't looked at root ACL override, but doesn't seem work for this tx stuff.  Have PR for Java 17?  Not closed yet, in review.


  • No labels

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