Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Time: 11:30am Eastern Daylight Time US (UTC-4)
  • Dial-in Number: (712) 775-7035

Attendees

  • Chris Awre 
  • Doug Blair
  • Ginny Boyer
  • Robert Cartolano
  • Aaron Choate
  • Sayeed Choudhury
  • Stefano Cossu (star)
  • Tom Cramer
  • Joanna DiPasquale 
  • Jon Dunn
  • Karen Estlund
  • Declan Fleming
  • Maude Francis
  • Mike Giarlo (regrets, will be boarding a flight)
  • Neil Jefferies
  • Debra Kurtz
  • Susan Lafferty 
  • Steve Marks
  • Rosalyn Metz (star)
  • Tom Murphy
  • Este Pope
  • Nick Ruest
  • Robin Ruggaber
  • Tim Shearer
  • Jon Stroop
  • Jennifer Vinopal
  • Evviva Weinraub
  • Jared Whiklo
  • David Wilcox
  • Andrew Woods
  • Maurice York
  • Jim Tuttle

Agenda

Advanced Tables - Table Plus
autoNumbertrue


Topic

Lead

CNI Fall Meeting proposals

  • Due October 11
  • What Fedora-related topics make sense in terms of proposals?
  • e.g. Fedor and digital preservation, API spec, related grant work

CNI Fedora Leaders Meeting Agenda

Establishing a review process for governance documentation


The 2.5% Commitment

Brief Update on API Specification Sprint


Oxford Common Filesystem Layout
RoundtableAll


Previous Actions

 

Minutes

Andrew

Aaron

Debra

Stefano

Karen

Carolyn

Tom

Rosalyn

Este

Evviva

Robin

Andrew

Debra

...

  1. CNI proposal
    1. Due October Brainstorming about related topics11
    2. Possible topics:
      1. Fedora specs and API changes
      2. File system specs
      3. Integration with different ecosystems 
      4. Preservation and Import//Export
      5. Grant proposals
    3. Will a session proposal have greater success chance than a panel?
    4. Integration examples:
      1. Hyku
      2. UMichigan / ICPSR
      3. LAKE
    5. Follow up with further discussion separately
  2. CNI Fedora Leaders meeting
    1. Add topics in Wiki page
      1. Mission/vision
      2. Budget 
        1. Reliance on contractors vs. community for development
        2. This comes post-retreat and post-budget definition so we will have good numbers to work on
      3. Membership: report on current membership drive & EU vs. US strategies
        1. Put some emphasis of Erin Tripp's effort toward this goal
      4. Business opportunities / service providers
    2. State of the technology / API specs
      1. More tactical and less technical discussion
      2. We don't want to get caught in the weeds but also find possible challenges or aspects that Leaders can help with
    3. Mission/vision should be the agenda centerpiece and we should have a very open and honest discussion about it
    4. Where Fedora fits and should fit / Declan's thread
    5. We should discuss how to tie tech advancement with strategy; there cannot be a vision discussion without including technology
  3. Anual Review—need David's feedback
  4. 2.5% contribution
    1. If 2.5% of revenues from collection budgets and fundraising are dedicated to infrastructure and development to support open scholarly
    2. We need to be careful with increasing contribution dramatically
    3. How do we get credit for my contribution?
    4. This is not a Duraspace- or Fedora-only membership drive; it is at a higher level where funds are put aside for this kind of projects in general
    5. A brief write-up would be helpful to bring to Sr. management
    6. It is a complex topic, and not new; it is very challenging to meet this goal
    7. First discussion about this was about collections; now it seems to be expanding into technical infrastructure. There is staff time to consider
    8. Accreditation needs to be validated
    9. Talk to Cliff Lynch about a special session in CNI? 
  5. API specs update
    1. First alignment with API specs sprint is concluding today
    2. Aaron B. took on interim lead role in the last 2 weeks
    3. A more complete update will be available soon as the sprint concludes
  6. Oxford filesystem specs
    1. This is directly tied to preservation concerns raised by community members
    2. This is two things: an API to talk to storage and serialize contents
    3. Andrew is involved in the filesystem layout and Neil in the serialization aspect





Actions