Time/Place

• Time: 11:30am Eastern Standard Time US (UTC-5)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information

Attendees

• Chris Awre 
• Robert Cartolano
• Aaron Choate
• Sayeed Choudhury
• Stefano Cossu
  
• Tom Cramer
• Joanna DiPasquale 
• Jon Dunn
• Karen Estlund
• Declan Fleming
• Maude Francis
• Mike Giarlo
• Neil Jefferies
• Debra Kurtz
• Susan Lafferty 
• Steve Marks
• Rosalyn Metz
• Tom Murphy
• Este Pope 
• Nick Ruest
• Robin Ruggaber
• Tim Shearer
• Jon Stroop
• Jennifer Vinopal
• Evviva Weinraub (and Carolyn Caizzi, as Evviva's alternate)
• Jared Whiklo
• David Wilcox
• Andrew Woods
• Maurice York

Agenda

Previous Actions

Minutes

1. Fedora and Samvera Dinner Notes
   1. Dinner during Samvera Connect - several conversations - captured in notes

   2. See: Fedora and Samvera Dinner Notes  Graph — Notes

   3. Connection issues - will table discussion for later 

   4. Venn diagram - display of objects is key thing we need for users and is missing

   5. Stefano would like to make an editable version of the Venn Diagram
   6. Features ideas discussed - interface to show where object is (example), (Rosie, Declan, Eviva) will look into preparing document with some ideas to share with the group
   7. Concern about Fedora not getting in the way (and it will be good to elaborate on this)
   8. Fragmentation of the Fedora communities - something to tackle (between Samvera, Islandora, other clients)
   9. What was the tenor of the discussion? A desire for working together, not fragmentation - how to continue working together - would be beneficial to have conversation at Open Repositories about this
   10. Topics in notes - some aspirational, some are current, in Fedora/Samvera
   11. Leadership discussion topic - noting various lines of potential fragmentation, directions of various related communities and position (if anything) of messaging to the community
   12. Driving principles/ideas - zoomed out from Venn diagram. One: what is something to work around, and what is essential in a robust digital repository. Something we need to discuss at CNI - not clarity on all the services Fedora provides - clarification will help in larger library community.
   13. Can we zoom out and include other clients/communities in the Venn diagram? Can we improve our net investment to get a better view of the broad needs of the various stakeholders for Fedora. Many Islandora members still using Fedora 3 - having a tool in front of them is most critical (putting resources to CLAW, for example). Islandora folks aren't really using Fedora 4 so aren't speaking to what ideas/concerns are, whereas Samvera community actively using Fedora 4 has much more to say.
   14. Takeaway: have this as an agenda item on the Fedora Leaders meeting at CNI in December. Share completed documentation before the December meeting.
   15. Action item for Stefano: transfer Venn diagram to Google Drawing.
2. CNI Fedora Leaders Meeting Agenda
   1. Agenda - any additions/changes?
   2. State of the technology - can this go beyond a state, to what are the important questions we need to answer - using time to work together rather than just reporting.
   3. Possibility of adjusting order of Agenda - where to place Mission/Vision conversation for most impact, especially for  new people
   4. Onboarding process/how new leaders can get up to speed to be prepared for participation - would be interested in feedback from new leaders
   5. How to ensure we have enough time to talk about Mission/Vision - we need to avoid letting other agenda items prevent finishing this conversation. Better to front-load the vision conversation first as it will impact further agenda items (Budget, Membership, etc.)
   6. Action item: fleshing out Agenda Item 1 - Mission/Vision/Staffing in advance of meeting - Mission/Vision group do before CNI (group meets twice before CNI)
   7. Action item: Agenda Items 2-6 - report out in advance of meeting, come prepared with feedback, to allow for more focus on Agenda Item 1
      1. Include concrete questions for the group (in addition to updates)
   8. Phone call pre-meeting for new members to help get up to speed (Thanks Karen)
3. DuraSpace Cross-rganizational Changes
   1. Projects across DuraSpace can be more disjointed than would be preferable
      1. Technical folks - thinking of this as a team
      2. Community/project management - another team
      3. These two teams working together more and considering DuraSpace projects more broadly
   2. Committers - "Holiday Gathering" - how to coaelesce around priorities in 2018 (today)
      1. Define and increase community engagement
      2. Have rotating roles such as annual Fedora Tech lead coming from committers group 
      3. Have conversation about how to implement such a shift
      4. How would technical team at DuraSpace support a Technical lead from committers group - identifying expectations
      5. Will document internally and communicate to board (Debra will work on this)
      6. Practical benefit for widening circle of technical participation, and a good idea to have a technical lead amongst committers.
4. Open Repositories
   1. Think about ideas and how to focus Fedora-related presentations and will discuss further at a future meeting.

Actions

• Stefano Cossu: transfer Venn diagram to Google Drawing.
• Vision & Strategy group: Fleshing out Agenda Item 1 - Mission/Vision/Staffing in advance of meeting - Mission/Vision group do before CNI (group meets twice before CNI)
• All: Agenda Items 2-6 - report out in advance of meeting, come prepared with feedback, to allow for more focus on Agenda Item 1