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

Time/Place

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

Attendees

Agenda

  1.  Fedora 5.0.0 Preparation Tasks

    1. Work completed in the last week

      1. Jiras:
        1. FCREPO-2798 - Getting issue details... STATUS
        2. FCREPO-2822 - Getting issue details... STATUS
        3. FCREPO-2771 - Getting issue details... STATUS
        4. FCREPO-2840 - Getting issue details... STATUS
        5. FCREPO-2826 - Getting issue details... STATUS
        6. FCREPO-2752 - Getting issue details... STATUS
        7. FCREPO-2742 - Getting issue details... STATUS
      2. CTS: 
        1. 9 Tests Added
        2. 4 Tests Fixed 
      3. Documentation
    2. Assigned and/or In Progress:
      1. FCREPO-2717 - Getting issue details... STATUS
      2. FCREPO-2801 - Getting issue details... STATUS
    3. In Review: 
      1. FCREPO-2821 - Getting issue details... STATUS
    4. Status of key Jiras:  
    5.  Ideas for this week

      1. Low hanging fruit (once 2742 is merged)
        1. FCREPO-2718 - Getting issue details... STATUS
        2. FCREPO-2824 - Getting issue details... STATUS
        3. FCREPO-2825 - Getting issue details... STATUS
        4. Do a code review 
        5. Join the CTS Challenge:  Write two tests before the next meeting:
          1. Look at how easy it is to add tests: https://github.com/fcrepo/Fedora-API-Test-Suite/commit/18a58618a856c6796fed69765d796985048f345b
      2. A little higher in the tree:
        1. FCREPO-2743 - Getting issue details... STATUS
        2. FCREPO-2698 - Getting issue details... STATUS
  2. All API Alignment Issues

     Click here to expand...

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

  3. 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

  • Danny to explore inserting a macro into documentation for Fedora version.
  • Send email to community seeing who is interested in reviving OAI

Notes

  • This week 9 new tests were added to the test suite
  • No documentation movement this week
  • ACL tickets entering the low hanging phase, so they should be good candidates
  • Discussing whether to do 405 or 404 or 400 for ticket Fcrepo-2821 with PR https://github.com/fcrepo4/fcrepo4/pull/1375
    • For PUT/POST/PATCH, if requesting a resource that doesn't exist, 405 since this is a path where this kind of request is disallowed.
    • For GET, if requesting resource that doesn't exist, then 404. If the URL is invalid (memento id is not a 14 digit number), then a 400 should be returned.
      • May need a constraint document if that is the case explaining why the structure was wrong.
      • Update the regular expression to specify the number length, should be 14 digits.
  • Work this coming week
    • Peter, may have time to work fcrepo-2717
    • Danny is in a duracloud related sprint, may try to do one of the tickets in the low hanging section
    • Ben will probably work fcrepo-2797 once other external content tickets are merged, particular 2821. Possibly some of the external content documentation tickets but may not have time.
    • Jared does not have much availability this week. May be able to review, but not familiar with WebAC code.
    • lsitu - 2718, is that overlapping with 2717?
      • Peter says one is about RDF sources and the other is about Non-RDF Sources.
      • Peter was considering doing 2718 after 2718, or doing them both at once depending on how things are structured.
      • Danny - 2824, 2825 may be good candidates for lsitu to knock out. If WebAC is null, then return the root AC document. These are low hanging
        • If you have sufficient privileges you should be able to PUT to override the default WebACL for the root node. If you were to PUT to the root ACL, here is no modeshape node behind that path, so need a bit of logic to deal with that case to get back the root ACL.
      • Do we need to add TTL of the root ACL to modeshape? Do we just retrieve the file for the user? If no ACLs in repository, then retrieve from file system (under the resources folder, is there a default file?) and generate response from that.
    • Other more complicated WebAC tickets, like implementing control and default. They are available but may not get to this week
  • Compatability Test Suite


  • No labels