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:
  2. Pop-up/Other Topics:
    1. ISLE/Fedora user question about Solr: https://groups.google.com/g/islandora/c/omyfFQlnF40/m/Kg-lSYKLBAAJ
    2. Committer Code Signing Key Process
    3. Fedora Technology Survey deadline has been extended to 1/31; keep reminding people to participate!
    4. Fedora on Tomcat 10
  3. Migration Updates:
  4. Updates on:

    1. Open Tickets (but assigned in some cases): 
      1. FCREPO-3918 - Getting issue details... STATUS
      2. FCREPO-3917 - Getting issue details... STATUS
      3. FCREPO-3912 - Getting issue details... STATUS
      4. FCREPO-3910 - Getting issue details... STATUS
      5. FCREPO-3906 - Getting issue details... STATUS
    2.  In Progress and older but still relevant open tickets:
      1. FCREPO-3919 - Getting issue details... STATUS
    3. In Review:
      1. FCREPO-3907 - Getting issue details... STATUS
  5. New tickets:

    1. FCREPO-3920 - Getting issue details... STATUS  
  6. Backlog Tickets to consider working:
  7. Next Meeting Chair:
    1. Chair: Ben Pennell
    2. Note Taker: Doron Shalvi

See Rotating Schedule here  

Notes

Announcements:

  • Lyrasis Member's Summit - taking place Feb 22
    • Let Arran know if your institution didn't receive their initiates, but should have.
  • Program team met with AWS team handing a Fedora 6 + Islandora 2.0 installation yesterday to discuss the implementation and future of the effort
    • AWS will open source the solution once they are confident in it's reproducibility and it has been through their internal vetting processes
    • Hope is to provide pathways to doing this for other institutions who are interested in an entirely AWS infrastructure

Pop Up Topics

  • ISLE question from Slack follow up
    • Jared will send follow up for more info
  • Committer Code Signing Key Process/Release Process Review
    • Mostly a note for Mike to remind himself to complete his
  • Tomcat 10 conversation from Slack
    • Should start to consider how this is incorporated in to something like Fedora 7
    • This might signify enough "work" and enough changes to consider a point release
    • could include work to make the java/jakarta change

Tickets

3918 - Thomas has it (Thomas’ notebook of improvements for the process)

  • Unassign it from Thomas once he’s input all the detail he wants to include

3917 - Thomas has plans to do it soon as it’s related to 3912

  • Remove the “latest” tag, should note this in the README
  • Should also outline what “main” is doing or what it is

3912 - Thomas started working on it

  • Should we keep “latest” for now and give people a heads up that newer version
  • Add a note to README and include it with release notes
    • Thomas would like to see as pre-note in advance just to make sure people will know
  • Thomas proposal to delete “latest” tag once we make the switch so people don’t get old versions by default
    • With no “latest” tag, Docker will require a tag in place
  • Thomas will raise his questions with the PR’s

3910 - Still hanging around - DocuTeam just needs to supply more info, and will look at it when they’re able too

3906 - 


3919 - Assigned to Dan - will get an update next week


3907 - Mike had a question about this

  • Reindexing could be added to performance testing work
  • Mike will test once more then merge


3920 - out of date documentation

  • Will need to fix this before next release
  • Related where we write data by default
    • Probably writing it to tomcat directory
  • No labels