...

• 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
• 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 WoodsWoods 
• Patrick Yott

Agenda

Previous Actions

•  Offline discussion on how many Fedora 4 versions to support and back port security fixes to.
•  Andrew asks that we ask our technical people to review the approach specified in Fedora 3 to 4 wiki. Also look at the Java project and try it out.

Minutes

Actions

DuraSpace Summit Update

• Rob C. - it was a successful summit
• Susan L. - energized and interested in the PCDM
• Tom C. - F4 breakouts
  • Pilots
  • Interest in future use cases
  • Sustainability
    • Useful to elaborate on micro-pitches around feature development
• Tom C. - What would we want the summit to be next year from a Fedora perspective
  • Should this slot be used as a Fedora Leaders meeting?
• Tim S. - how many f2f meetings do we want per year?
• Glen R. - more f2f meetings are difficult considering international members
  • Susan L. - seconds idea
• Tom C. - Which dates/venues are best for international members?
  • Glen R. - Open Repositories works well
  • Susan L. - DuraSpace Summit works well
• Tim S. - Are there times of the year that work well with project schedule?
  • Andrew W. - since we work in 6-month blocks, meeting before each block could be helpful
• Declan - conflicting with PASIG was a bummer

Cross-project Leadership conversations

• Andrew W. - This came out of the summit
  • Could be useful to meet across Fedora/DSpace/VIVO at some interval
• Rob C. - need to keep conversation grounded
  • More background is needed
  • Project manager should help with a "terrain map"
• Robin R. - OR2015 could be used for cross-discussion on particular topics
• Tom C. - This is what the DuraSpace Summit should be used for
  • An agenda is needed
  • re:Installation registry?
  • Declan - suggests participants of DuraSpace Summit is too high-level
  • Tom C. - we need to define what the DuraSpace Summit should be
• Rob C. - we need to come to such a meeting with a concrete agenda
  • Choose topics that are small and meaningful with short-term deliverables
• David W. - should product managers lead the search for topics? or a survey?
  • Rob C. - chair an product managers should have initial call (6 people)
  • Action: David W. to organize initial call across DuraSpace projects to determine potential topics
  • Susan L. - seconds the idea

On-going developer participation in maintenance sprints

• David W. - We have had a challenge getting participation in maintenance sprints
  • We need 2-3 developers per sprint
  • Currently, getting developers requires continual, high-touch personal appeals
• Robin R. - maybe use trainings to advocate for developer participation
• David W. - how do we encourage a culture of institutional commitments to maintenance sprints?
• Susan L. - could part of the training curriculum require participant in sprints?
  • Tom C. - seconds the idea, has worked in Hydra
  • Robin R. - other participation is valued: documentation, testing, training, etc
  • Tim S. - cultural component, some developers do not feel up to the task
• Andrew W. - suggesting sending out tickets in categories based on skill and experience
  • Susan L., Jonathan M. - seconds the idea
• Susan L. - if people knew they had to commit to so many hours could be more palatable than 2-week long sprint commitments
  • Robin R. - possibly 80 hours over two months?
  • Tim S. - concerned about orchestration and auditing of participation

Portland Common Data Model (PCDM)

• Tom C. - this is important and leaders need to be aware of it
  • Opportunities for common model across sites
  • Hydra will start development in May
  • Declan F. - UCSD will be participating in PSU sprints
• Susan L. - likes alignment with standards
• Tom C. - have people seen it?
  • Robin R. - has seen it, supports interoperability
  • Declan F. - extremely important

Steering Elections

• Robin R.
  • 6-month offset from Leadership elections (which happens in Fall)
  • Term length? 2? 3 years?
    • Tim S. - 3 years is a long commitment
      • Susan L. - seconds idea
    • Tom C. - 3 years offers time to understand process and become more effective
  • Nominates Susan L.
  • Rob C. - seconds nomination
• Jonathan M. - important for all DuraSpace be on the same election cycle
  • Only leadership would do nominating and voting
  • Robin R. - could we do this more informally in email?
• Susan L. - need private voting mechanism
• Tim S. - how many people are on steering?
  • What characteristics are we looking for?
    • Jonathan M. - people who want to play an active role in the project
    • People who have ability to dedicate development resources
    • Robin R. - Steering is a smaller functional bodies
    • Other work is accomplished with working-groups
  • David W. - we currently have 8 (not including DuraSpace employees)
    • Robin R. - 7 or 9 steering members would be ideal in terms of ties
• Rob C. - leadership should have input into this evolving process
  • Action: Robin R. to send out proposal to leaders
  • Robin R. - to send Jonathan M. proposal for review

Actions

•  David W. to organize initial call across DuraSpace projects to determine potential topics
•  Robin R. to send out proposal to leaders

...