Time/Place

Time: 12:00pm Eastern Daylight Time US (UTC-4)

URL: https://duraspace.zoom.us/my/fedora

Or iPhone one-tap :

Or Telephone:

Meeting ID: 812 835 3771
International numbers available: https://duraspace.zoom.us/zoomconference?m=dLuIIwXLUv5-UK4kIXYkkH9mryRETY08

Attendees

Topic	Lead
Update on API alignment sprint	Andrew
Fedora Vision and Strategy Update and feedback on the process so far Is the current process addressing the needs of this group? Ongoing spreadsheet review Are columns A and B correct and complete? What about column H?
Project priorities for the coming year Fedora API Specification Aligning Fedora Modeshape implementation with the specification Fedora API Specification test suite Increased preservation sensibilities: Oxford Common Filesystem Layout? Design recommendations/tools for migration? Adopters guide (https://github.com/fcrepo/fcrepo-adopters-guide) Next Leaders/Committers meeting on March 19
Fedora Code of Conduct Reporting Guidelines Leaders review and ratify Post to website Circulate to relevant lists (Fedora, Islandora, Samvera)	Rosalyn
Updated DuraSpace membership model New lower levels for less well-resourced institutions Normalized across Fedora, DSpace, and VIVO Revised election structure Bronze: 1 Leader for every 8 member institutions Silver: 1 Leader for every 5 member institutions Gold: 1 Leader for every 2 member institutions	David
Archiving Fedora Slack history Currently on the free plan, only last 10,000 archived messages are available (nearing the limit - 8,680) Is there interest in paying for access to the complete archive?	Andrew
LAKEsuperior release	Stefano

Roundtable	All

All: Explore how to bring better cross-effort alignment between Fedora and other repository efforts.
All: contribute to generating content for, and formatting Fedora annual report.
DuraSpace staff/All: Generate and share articulation of benefits of moving to Fedora 5.

API alignment sprint

Fedora Vision and Strategy

Document at: https://docs.google.com/spreadsheets/d/1YH3uNxFXPgrRlOv3Nh8z6I3bWCVyC2k6jY21DFjzLvI/edit#gid=0
brain storming on a separate platform, add ideas, review process. get in touch with Maurice York if you're interested in it. the group may make it broadly available to the rest of the leaders.
they are moving through the document and doing well with it. feedback is welcome.

Project Priorities 2018

These are solidified
- Fedora API Specification
- Aligning Fedora Modeshape implementation with the specification
- Fedora API Specification test suite
These are not, but are leaders interested in supporting it?
- Increased preservation sensibilities: Oxford Common Filesystem Layout?
  - OCFL https://docs.google.com/document/d/13gFfSu1fePKx0eQYk458zE6OZwCW5JH_hTIG58f3S8c/edit.
  - this isn't fully fleshed out yet
  - but being a part of it may mean that whatever is developed may work with Fedora
  - watching these things are important if we want to align whenever / where ever possible
  - partnering with outside groups like OCFL can be useful
  - some of the things that were available in fedora 3 are coming out in OCFL. the persistence layer is important
  - what are the benefits of OCFL? how might it affect Fedora?
- Design recommendations/tools for migration?

Fedora Code of Conduct Reporting Guidelines

Updated Duraspace membership model

the new models bring all the durasace projects into alignment for community membership models;
lower levels are being added to help make it easier for institutions are less resourced
support for the updated models; really helps with getting more people on board to the project; fundraising; getting smaller institutions to the table
we need feedback from leaders on this; we should put this to a vote

Fedora Slack

budget implications: do we want to pay for slack
do we want to allocate budget for this? we need more information about the implications of the decision

David Wilcox / Andrew Woods: add an OCFL agenda item to the leaders/committers meeting; add a design recommendations/tools for migration agenda item to leaders/committers meeting
Rosalyn Metz: send the code of conduct out to leaders for ratifying
David Wilcox: will send out a fuller explanation about the membership model and ask for a vote
Andrew Woods / David Wilcox: send budget information for slack