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.0 release candidate - testing and migration
  2. https://github.com/w3c/ldp-testsuite/issues/229#issuecomment-250448306
  3. HydraConnect attendance/meet-up
  4. Document compatibility of external components relative to Fedora releases
    1. In READMEs, or
    2. Component Compatibility Matrix
  5. Prioritization of ticket review
  6. API Spec inter-dependencies
    1. Resource CRUD
      1. Resource Versioning
        1. Fixity Checking
        2. Atomic Batch Operations?
      2. Authorization
    2. Messaging SPI
  7. Pruning documentation: Authorization Delegates
  8. ...
  9. Status of "in-flight" tickets

     Click here to expand...

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

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. Now that the release candidate is out,  let's focus on testing. 
    1. Yin will try vagrant today and verify whether or not it is broken.
      1. try "vagrant box update"
    2. Possible to tie vagrant to a specific version of the base box?  Since base boxes can shift under a fedora version and cause confusion...
    3.  Who will help with testing? 
      1. Danny
      2. Nick
      3. Aaron Birkland
    4. Some focus should be brought to migration of existing repositories
      1. Who might be willing to attempt such a migration test?
    5. Jared:  Please test something
  2. LDP Test Suite:  We need to maintain this thing - at least insofar as the tool should still run:
    1. We should come to an agreement with Rob and others about the terms of maintenance.
    2. Do we fork this project ?
    3.  Project still runs, but will break.  Maintainers are not responding.
    4. Chris Beer has identified a problem with the Test Suite and has a pull request in.
  3. HydraConnect:
    1. Anyone up for a meetup?  
    2. Who will be there: 
      1. Esme, Kate, Yinlin,  Ben, Andrew Woods, Bethany
    3. Any ideas of how to use this opportunity?
      1. Containerizing in Production Deployment
      2. Import/Export unconference session?  Yes - there is  interest there
    4. Informal get together?  Yes there is interest.
      1. Lunch Wednesday or Thursday?
  4. It is not always clear which versions of which pluggable components are compatible with which version of fcrepo4.
    1. Andrew Woods surfaced the need to maintain a compatibility matrix or at least capture this information somewhere in the documentation.
      1. Proposal:  When a component is released,  document which fcrepo4 version it will work against,  whether in a compatibility matrix or in the readme.
      2. General agreement: any release notes  should note which fcrepo4  the component was tested against.
      • Andrew Woods : Add a note to EXTS policy docs indicating that people must document which version of fedora was used with integration tests (where applicable)
  5. Next week Andrew Woods will be gone:  Any high priority work / blockers that should be raised?  No.
  6. Comments on the API dependencies: 
    1. Who will tackle each component: 
      1. Resource CRUD:  
        • A. Soroka will reach out to Ben,  Tom Johnson, Danny Lamb

 

  • No labels