Time/Place

  • Time: 12:00pm Eastern Daylight Time US (UTC-4)
  • Call-in: DuraSpace conference line
    • 641-715-3650 209-647-1600,   117433#

Attendees

Agenda

  1. Introductions
  2. Comments, questions, and feedback from Leadership Group
  3. Fedora governance model review and feedback
  4. Fedora 4 community update
    1. Summary of events and community engagement
      1. DC Area Fedora User Group Meeting
      2. DuraSpace Sponsor Summit
      3. Fedora BoF at 3rd RDA Plenary
    2. Call for acceptance testers and beta pilots
  5. Fedora 4 technical update
    1. Sprint progress
    2. Upcoming beta release
  6. Upcoming conferences and face-to-face opportunities
    1. Open Repositories, June 9-13
    2. PASIG Meeting, September 16-18
    3. 4th RDA Plenary, September 22-24
    4. Hydra Connect, September 30 - October 3
    5. DLF, October 27-29
    6. eResearch Australasia, October  27-31
    7. CNI, December 8-9

Minutes

Opening Questions/Comments from Group

  • Mike F.: Want to do upcoming active digital curation work in Fedora 4, perhaps look for grant; will do digitization (and some elimination) of materials as well as preserve born-digital content; is looking for collaborators.

New Fedora Governance Model

  • David summarized the governance policies just formulated by the steering group
  • Tim McGeary:  As a bronze member but an in-kind contributor, wants to be eligible to be nominated and elected to the Steering Group as well as serving on Leadership; we will follow up with steering to clarify this policy
  • Glen:  Could Leadership become too large?  Jonathan:  Don't forsee it being a problem.  Steering needs to be nimble.
  • We need to add .5 FTE to governance benefits table
  • Term limits for steering and elected leadership positions need to be discussed.  Maybe at CNI
  • Should members be able to nominate people outside their group
  • Mike:  can we coordinate elections with institutional fiscal year
  • We should make travel and time expectations clear for these different roles
  • We will continue this discussion on list

Community Update

  • Steering has attended productive DC user group mtg; 
  • BOF session at RDA Plenary in Dublin–good communications, interest in F4 for research
  • Call for beta testers and pilots;  use cases are being validated;  we can always use more participation!
  • No committed beta pilots yet; UCSD is considering this; so is UNC; same for Indiana
  • We will be looking for beta testers at Open Repositories

Technology Update

  • Read the Sprint updates on the wiki–they are very detailed–for starters
  • Beta will be available at the end of the current sprint!
  • Included features are documented in above link; use cases are covered very well
  • Proposal from IU and WGBH using F4
  • Interest from Northwestern in IIIF over F4
  • Interest from MIT in ResourceSync over F4
  • Art Institute of Chicago - progress on F4 prototype
  • Development team is thinning out a bit - we need to fill it out;  our hope is to get to production this year, but it is contingent on developer availability
  • UCLA is now contributing
  • UCSD has added new developer
  • UC-Berkeley will be adding developer
  • Hackfest last week very successful; focus on performance testing, CRUD operations, versioning, number of objects supported; 16 million files supported, especially when hierarchically structured
  • Push for supporting complex authorization use cases; XACML work progressing nicely–we hope to get it into the beta; it will be able to support a broader base of use cases
  • Call for action:  Beta testers, raise your hand
  • Message for OR:  Beta serves new Fedora implementations; upgrade path to be addressed in next production iteration; please join us in testing
  • Hydra work with F4 is continuing; Mike G:  Hydra application on F4 will be available at OR if all goes as expected; Yale will kick the tires; by August will hope to pilot F4 with Hydra
  • Mike F: Can development work be done on a ticket outside of the sprint schedule? Andrew:  Would like to see evolving development model where people are engaged long-term outside of sprints too, participation on committer calls.  Mike F. thinks this would be feasible for his team.  We will carry on this conversation on list
  • Tim:  UNC sprints are synched to Fedora sprints to maximize possible participation

Actions

 

 

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