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 

• Longshou Situ 
• A. Soroka
• Unknown User (acoburn)
• Esmé Cowles
• Yinlin Chen 
• David Wilcox
• Nick Ruest 
• Benjamin Armintor
• Bethany Seeger
• James R. Griffin III
• Aaron Birkland
• Jared Whiklo 
• Jack Hill
• Michael Durbin
• Andy Wagner

Agenda

1. Weak/Strong ETags for Containers and the If-Match header
   1. Conversation moved to LDP-Next mailing list
2. High priority issues that need development volunteers
   1. Versioning 
      1. 
      2. 
   2. Many members
      1. 
      2. 
      3. 
3. Still time to participate in the Fedora Value Proposition brainstorming
4. ...

5. Status of "in-flight" tickets

Ticket Summaries

1. Please squash a bug!

2. Tickets resolved this week:

3. Tickets created this week:

Minutes

1. E-Tags
   1. tamsin johnson moved the discussion up to the LDP Next community on the mailing list. Benjamin Armintor replied, but nothing further.
   2. A. Soroka : I've been told that this is not surprising, and we may not get a response. This was a blocker for an earlier release candidate, but due to the spec conflict is this really a blocker?
   3. Esmé Cowles : we should go ahead with the release, and inform clients that they should not use the If-Match Header for the time being and to use the If-Unmodified-Since.
   4.  : Actually the headers are evaluated correctly, but LDP and HTTP specs contradict each other. 
      1. Consensus around Close Won't Fix and open a new ticket () to track the issue.
2. High Priority tickets
   1. A. Soroka :  is not necessary a bug, but a documentation issue.
   2.  : this is not necessarily a problem in versioning, but a triple being added to the RDF. More discussion on the ticket. Possibly the outcome of FCREPO-2118 could influence the work of this ticket.
   3.  : Different options for dealing with this, some inside Fedora and some dealing in the client-side. Benjamin Armintor as a PR for id translation refactoring and a very experimental branch for refactoring container membership triple generation. 
3. Fedora Value Propositioning
   1. Go to the link and vote. It is an exercise to see what Fedora stakeholders think are the most important aspects are. Comments go under "Pros & Cons", but the heading is less important and will be reviewed individually.
4. Tickets...
   1. No one has any concerns or needs for the in-flight tickets.