Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda

  1. Hash fragments: review description

  2. ...

...

  1. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  2. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  3. Tickets created this week:

    Expand
    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

  1. Hash URIs

    1. Comments seem to indicate a little bit of a consensus on proposed behaviour
    2. No expressed opinions/preferences/concerns/comments regarding implementation approach
      1. No clear understanding right now of tradeoffs of approaches, or cost of implementing
    3. Is anybody committed to actually implementing the fix? 
      1. Not sure if Esmé Cowles is planning on implementing, or is just facilitating the discussion and doing some exploration
      2. Aaron Birkland indicated a future business need for this functionality, though a ways off into 2016.  Will likely need to produce a fix if one isn't already in place by then.  No resources right now, though
    4. Is this a critical bug?  What are the consequences of limping along?
      1. Consequence is left-over resources that cannot be removed
      2. It is unclear if anybody is actually using it right now in a manner that presents a problem to them
    5. Hydra's PCDM ordering seems to be the biggest concrete use case right now
      1. Still, it seems a rather odd use case to drive Fedora's functionality and APIs