Time/Place

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

• Time: 11:00am Eastern Standard Time US (UTC-5)
• U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
• International toll free:  http://www.readytalk.com/intl 
  
  • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
  • Once on the call, enter participant code 2257295
• IRC:
  
  • Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #duraspace-ff on irc.freenode.net

Attendees 

• Nick Ruest
• Aaron Coburn
• Osman Din

• Esme Cowles

• Michael Durbin
• Kevin S. Clarke
• Yinlin Chen
• Andrew Woods
• Jared Whiklo
• David Wilcox
• Benjamin Armintor
• A. Soroka

Agenda

1. Release of 4.1.1?
   1. We will not met the goal of having the release done by the end of this week
   2. Goal (blocker) to have the blank node work in 4.1.1
      1. Michael Durbin will take the lead on getting the release out next week while Andrew Woods is at LDCX
2. Release of 3.8.1?
   1. 3.8.1 branch pull requests need to be merged 
   2. Testing needs to be done before the release
      1. Testing must be done by the community so we can actually release it.
      2. OR2015 is the agreed upon the deadline for testing.
   3. All pull requests will be merged into the 3.8.1-SNAPSHOT branch
   4. Release candidate and release candidate artifacts will be built from the 3.8.1-SNAPSHOT branch
3. migration-utils
   1. Nick Ruest proposed a prioritization of migration functionality
      1. Traverse fcrepo file system (current primary focus)
      2. Migrate export context
      3. Archive export context
   2. Nick Ruest volunteered to create test fixtures migration-utils vm (fcrepo 3.x content and fcrepo4)
   3. Michael Durbin should have a preliminary solution in about a week, and Nick Ruest will be a guinea pig
   4. Goal of having a "solid" release of this for OR2015 (Nick, Danny, Jared willing to do whatever we can to make this happen!)
4. Audit Service implementation options
   1. Audit Service call at 3pm EST today
   2. Focused on external triple-store
   3. Read: servicing queries
   4. Write: audit events (internal & external)
   5. Requirement: exposing external SPARQL endpoint
   6. Incorporate fcrepo-camel component
      1. Discussion around event ordering and who/what sends the message
         1. Combination of timestamps and users would alleviate this
         2. Old pivitol ticket about jcr namespaces being leaked that wasn't transferred over
         • Unknown User (acoburn) to port old Pivitol ticket to JIRA (jcr namespaces being leaked). Done:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   7. Requirements can be met without a lot of core fcrepo code updates
   8. Guiding principles
      1. Any Fedora4 feature should be available through an API which is an implementation of LDP or an optional extension (ideally an existing standard)
      2. Fedora4 features should favor existing tools over custom code
      3. Fedora4 features should establish integration patterns where an implementation is not a part of the core code
5. Further discussion on "pure" LDPRs : Design
   1. Discussion centralized on the wiki page
      1.  Need to break proposals down, and not approve them all together
      2. Things that are less contentious
         1. server managed properties
      3. Things that are contentious
         1. non-container resources
         2. arbitrary RDF
         3. rdf interaction model and non-rdf interaction model
6. LDP and /fcr:versions
   1. We need to tighten up and clary (obscurities) where Fedora can do a better job with LDP
7. New JIRA tickets

   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