Time/Place

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

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees 

• Jared Whiklo
• Jim Coble 
• Andy Wagner
• Doron Shalvi
• Yinlin Chen
• Esmé Cowles
• Kevin Ford
• Michael Durbin 
• Simeon Warner 
• Benjamin Armintor
• Andrew Woods

Agenda

1. API Specification

   1. Moving towards a shared understanding: Purpose of the API specification 

   2. Does Persistence Fixity belong in the specification?

   3. Outstanding issues

2. Implications of blank node redesign:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Suggestions from recent Fedora Leaders meetings
   1. Have an elected Fedora Committer join Fedora Leaders calls
   2. Have DuraSpace-hosted release testing infrastructure
   3. Interest in tighter alignment of effort and priorities between Islandora/Hydra/Fedora
4. Announcement: Monday - 2017-04-17 - Import - Export Planning Meeting
5. ...

6. Status of "in-flight" tickets

     Click here to expand...

Ticket Summaries

1. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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
  • no one on the call volunteered as having S3 storage
  • Esmé Cowles will contact Andrew Woods about this

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.