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. Outstanding issues on Fedora API Specification

  2. The following ticket should be squash/merged by another committer if approved:  FCREPO-2402 - Getting issue details... STATUS

  3. The following ticket should be squash/merged by another committer if approved... once Danny Bernstein merges code-review PR FCREPO-2105 - Getting issue details... STATUS
  4. ...
  5. Status of "in-flight" tickets

      Click here to expand...

Ticket Summaries

  1. Please squash a bug!

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

  2. Tickets resolved this week:

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

  3. Tickets created this week:

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

Minutes

API Spec Outstanding Issues

  • #82 about ordering issues, which was largely not an API issue
  • #81, a little bit of langage in the spec should clear up confusion here
    • change a "may" to a "must" if a preference is applied, the fedora implementation should say so
  • #80, there's some disagreement about whether fedora should redirect or proxy to external content, and once a clear consensus is achieved, the spec should reflect it
    • Benjamin Armintor is the only one who has articulated a need for proxying, while presumably other stakeholders are content with redirects
      • Feedback at LDCX suggested that other stakeholders minimally preferred proxied content, and in some cases required it.
    • A new issue was opened for this Proxy vs. Redirect requirement in the spec.

Committer's needed to close PRs

  • S3 Configuration ticket needs to be merged, but someone with S3 storage should test them

A PR from Danny Bernstein to address performance of items with lots of properties

  • This is almost done, but maybe a test failure is holding it back

In-Flight tickets (none?) and Bugs

  • no questions or comments about current outstanding bugs.
  • No labels