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

Time/Place

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

Attendees

Agenda

  1. 4.7.5 release testing
  2. Moving into alignment with the spec
    1. Sprint date options
  3. Pairtree/Appletree options
  4. ...

Ticket Summaries

  1. Please squash a bug!

     Click here to expand...

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

  2. Tickets resolved this week:

     Click here to expand...

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

  3. Tickets created this week:

     Click here to expand...

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

Minutes

  1. Who is going to Open Repositories? Esme, Josh, Doron, Bethany, Ben, Mike (on the fence), David. No specified interest group session, but still supposed to identify. Maybe get together for some sort of Fedora dinner and discussion.
  2. Same for Code4Lib - Yinlin, Josh, Esme, Ben, Peter attending. Josh to coordinate a Fedora event.
  3. 4.7.5 Testing
    1. Esme is handling Samvera testing
    2. Jared to test with CLAW and API-X
    3. Anyone has a Windows machine for testing. Have to wait for Aaron.
    4. CVE warnings...is everyone seeing those? Peter and Josh are seeing them. http://www.victi.ms/ is throwing 503 Service Available
    5. Database testing. Josh to try both databases on OSX, Jared to try both databases on Linux.
    6. Backup/restore both release backup to release restore and previous backup to release restore.
    7. Targeting February for release.
    8. Carrick from North Western has offered to do some fuller integration testing. Andrew will reach out to see what can be done.
  4. API alignment sprint
    1. Please fill out your availability for the dates provided.
    2. The spreadsheet has many tests to tell where we are in alignment.
    3. Also good to try out the test compatibility suite.
    4. For something like messaging there are some things Fedora does with regard to referential integrity (which is fine), but it also emits messages for hash uris. That is notable, but not necessarily in conflict with the spec. Should these types of differing or additional functionality be noted somewhere?
  5. Pairtree / Appletree
    1. Which way do we want to configure it?
    2. What about implement pairtrees as in Modeshape, but in the API the pairtrees are not resolvable instead return a 404. Possibly allow you to PUT an intermediary resource later.
    3. Some performance testing would be helpful.



  • No labels