Time/Place

• Time: 11:30am Eastern Standard Time US (UTC-5)
• Call-in: DuraSpace conference line
  • 209-647-1600,   117433#

Attendees

• Julie Allinson
• Andrew Ashton
• Chris Awre
• Robert Cartolano
• Stefano Cossu
• Tom Cramer
• Steve DiDomenico
• Jon Dunn
• Euwe Ermita
• Declan Fleming
• Michael Friscia
• Michael J. Giarlo
• Ladd Hanson
• Wolfram Horstmann
• Neil Jefferies
• Philip Konomos
• Susan Lafferty
• Mark Leggott
• Jonathan Markow 
• Tom Murphy
• Matthias Razum
• Glen Robson
• Robin Lindley Ruggaber
• Dan Santamaria
• Tim Shearer
• Kirsta Stapelfeldt
• Thorny Staples
• Jim Tuttle
• David Wilcox
• Andrew Woods
• Patrick Yott

Agenda

Minutes

Welcome, new leaders!

DuraSpace Summit Fedora Topics

• Three 45-minute sessions.  Maybe one would be with new CEO(?)
• Support for new Fedora Repository use cases in next 3 years
• Sustainability could include a number of things:  developer resources, memberships, funding alternatives, migrations(?)
• How Fedora relates to other enterprise systems
• Poster session could be helpful letting people know how people are using Fedora

Migration Pilots

• We call it an "Upgration"!
• It is hoped that pilots will represent multiple community segments (e.g., Hydra, Islandora, roll-your-own), features, and use cases.  Anyone with a Fedora 3.0
• Five pilots would be a good minimum - We need commitments for pilots as early as possible!
• UNSW in Australia and York in Canada have already made commitments
• Duke and U Mich considering this now. 
• UNC will put up a Curator's Workbench on Fedora 4 near-term (new app)

Migration Working Group interest:  

• Declan, Susan, Glen
• Susan 
• Glen

Fedora 4.1 Feature Priorities

• Asynchronous Storage - Indiana will be helping with this as part of their HydraDAM2 requirements
• Audit service is high priority for 4.x
• LDP paging is candidate
• Web Access Control is W3C spec for web authorization
• API Partitioning moves Fedora away from custom code and towards robust standard API
• We want to get consensus on first features to work on and then recruit for sprints
• We can use resources for maintenance sprints (bug squashing), feature sprints (working on new priority features), migration pilots and tooling.  All hands are welcome!
• Please comment on features and priorities:  Leadership mailing list is a good place for discussion

OR 2015 Proposals

• David proposing some panel discussions for Fedora
• Susan:  UNSW staff proposing a poster on research data storage work
• Andrew:  Will be a Fedora Technical Session
• Jim:  Considering poster for Hydra-Fedora3 presentation, but would like to talk about Fedora 1 migration - Migration panel could be a good idea
• Mike:  Proposing on Hydra work, upgrade plans, Fedora-Sakai LTI integration
• Jon: HydramDAM2 proposal will highlight Fedora 4

Fedora4 / VIVO integration project

• Has come up several times in past
• Integration work would involve linked data
• Seems like low-hanging fruit
• Columbia exploring this but not ready for commitment yet
• Let David know if you are interested in joining any of this work or starting your own project

Actions

• Send out message to Leaders re: Migration Working Group (David Wilcox)
• Send out message to Leaders re: feature priorities with Jan. 30 deadline for feedback (David Wilcox)