Page tree
Skip to end of metadata
Go to start of metadata


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


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



Fedora Steering Group election resultsRobin

Maintenance sprint schedule


Next round of Fedora 4 implementation projects

  • Focus on currently scheduled implementation projects
  • Flexible timelines - aim to complete in early 2016
  • Need clear milestones and deliverables
  • Looking for 3-5 institutions

Hydra/Islandora interoperability

  • Value proposition
  • Agenda for Fall events

Fedora Hack Camp

  • Classroom styled event for 30-40 participants
  • Focus on building Java/Fedora 4 skills
  • Goal of increasing developer engagement with Fedora 4

Previous Actions

  • Declan Fleming and David Wilcox will compile a list of vendors and information to support outreach
  • Michael J. Giarlo will look into F4 performance issues and, if appropriate, engage Hydra and Fedora communities about corroborating/troubleshooting/resolving them
  • Lets pilot a Hackathon for Fedora Developers in late 2015 or early 2016

  • David Wilcox to begin capturing, curating content for an "ambassadors" list of F4 implementations. Start a list / table in Confluence with updated case studies
  • David Wilcox & Stefano Cossu to form an elite subcommittee to refresh content on the Website over next 6 months
  • Patrick Yott to confirm participation on elite subcommittee by end of this week
  • All: send any additional comments on website content in to Leaders or the Elite Subcommittee
  • All: Steering election is still open; voting for 3 new Steering members; each institution only gives one vote. Votes open another 1-2 weeks. 
  • Jonathan MarkowDavid WilcoxAndrew Woods to discuss the F3 -> F4 mental mapping / upgration support issues raised by Glen in email to leaders, reflect back to Leaders


  1. Introductions
    1. Susan Lafferty’s last Leadership Group Meeting representing UNSW; moving to Australian Catholic University, not currently using DuraSpace product
  2. Fedora Steering Group election results (Jonathan)
    1. Susan Lafferty, Stefano Cossi, Declan Fleming elected as new members
    2. New members started July 15, 2015 and will continue for three year term to mid-July 2018
  3. Maintenance sprint schedule (Andrew)
    1. Following on from discussions at OR15 about maintenance sprints and needing more lead time for signups in order to facilitate local resource planning, calendar now contains dates through end of 2016
    2. Have had good success with feature sprints (audit, Web Access Control); maintenance sprints have fallen off peoples’ priority lists; need to get people to sign up – not yet clear how much this will help with fundamental problem.
    3. Susan: Just entering planning cycle for 2016. Haven’t yet added commitments to schedule.
  4. Next round of Fedora 4 implementation projects (Andrew)
    1. Focus on currently scheduled implementation projects
      1. Formerly known as “upgration pilots” – following on from success of first round
      2. Goal to work closely with handful of institutions already planning move from F3->F4
      3. Could be Hydra context, Islandora context, or neither
      4. Goals: work out kinks in process; identify and fix bugs in the software; scale testing
      5. Exercising not just Fedora 4, but other tools such as migration tools from UVA, fedora-migrate Hydra gem from Penn State, etc.
    2. Flexible timelines - aim to complete in early 2016
    3. Need clear milestones and deliverables
    4. Looking for 3-5 institutions
      1. Putting request out to Leaders first, then will expand to broader community
      2. Tom Murphy: Are we interested in new implementation projects as well? Andrew: Yes, interested, but goal of these pilots is F3->F4. Trying to address uncertainties amongst F3 users about what is needed to make the move.
      3. Stefano Cossi: Art Institute of Chicago launching its new F4 repo in 1Q16
      4. Rob Cartolano: Planning to upgrade Columbia’s Academic Commons from F3 to F4 by Summer 2016. Does this fit timeframe? Andrew: Makes sense to talk more offline.
      5. Mike Friscia: Yale on similar timeframe: migrating Hydra stack to F4 over next year; most content in by January 16 but will wait to release. Focus on ingest performance; bringing in close to 3 million objects from F3->F4. Andrew: Sounds like ideal implementation pilot. Mike will have Eric (sp?) contact Andrew. Will try to work in maintenance sprints to project timeline as well.
      6. Jim Tuttle: Duke has begun planning; goal to work on in September-December. About 16,000 objects to migrate across two repositories. Want to migrate to PCDM.
      7. Tim Shearer: UNC plans to choose corpus of materials that will push on various areas (storage, authn/authz, etc.). Complete pilot by December to inform full upgration. Interested in committing to maintenance sprints as issues uncovered.
      8. Jon Dunn: possible IU interest, but not sure of timing yet; may know more in next month. Jon will check with HydraDAM2 team and get back to Andrew about readiness to work on HSM storage integration
    5. Don’t want to impose too much additional overhead, but want enough structure to provide outcomes that flow into the community. Communication via wiki pages and email summaries.
      1. Discussion: Would be useful to have standard template for communication; document challenges and benefits of upgration, lessons learned; demographic data about collections
  5. Hydra/Islandora interoperability (Andrew)
    1. Value proposition – see Google Doc
      1. Discussion out of OR15 about benefit of having some level of interoperability between Hydra and Islandora implementations of Fedora 4
    2. Agenda for Fall events
      1. Proposed sessions at Hydra Connect in Minneapolis (September 21-24) and Islandora Camp Connecticut (October 20-23)
    3. Looking for feedback
      1. Stefano: Would be very useful but would be a lot of work (incl. ongoing maintenance) to do on both Hydra/Islandora and Fedora sides. Andrew: Need to clearly define line of division of responsibility between Fedora and application communities; would imply ongoing commitments; hope would get more devs from app communities involved in Fedora.
      2. Stefano: Would it be dependent on the F4 API extension effort? Andrew: Needs more investigation/definition.
    4. Do we think this effort is worthwhile?
      1. Several expressions of support from participants on the call
  6. Fedora Hack Camp (Andrew) - will continue as agenda item for next call
    1. Classroom styled event for 30-40 participants
    2. Focus on building Java/Fedora 4 skills
    3. Goal of increasing developer engagement with Fedora 4