Time/Place

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

Attendees 

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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Many members
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  3. Still time to participate in the Fedora Value Proposition brainstorming
  4. ...

  5. Status of "in-flight" tickets

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

  1. Please squash a bug!

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  : 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 ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. ) to track the issue.
  2. High Priority tickets
    1. A. Soroka : Unable to locate Jira server for this macro. It may be due to Application Link configuration.  is not necessary a bug, but a documentation issue.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  : 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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  : 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.

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.