Time/Place
Time: 10:00am Eastern Time (US)
URL: https://lyrasis.zoom.us/my/fedora
Meeting ID: 812 835 3771
Dial by your location:
888 475 4499 US Toll-free
877 853 5257 US Toll-free
855 703 8985 Canada Toll-free
0 800 031 5717 United Kingdom Toll-free
Find your local number: https://zoom.us/u/ad6Xb7q3ia
Attendees
Tammy Allgood Wolf- Melissa Anez
- Chris Awre
- Thomas Bernhart
- Danny Bernstein
- Robert Cartolano
- Aaron Choate
- Sayeed Choudhury
- Stefano Cossu
- Jon Dunn
- Karen Estlund
- Dan Field
- Raman Ganguly
- Jennifer Gilbert
- Babak Hamidzadeh
- Neil Jefferies
- Mark Jordan
- Danny Lamb
- Rosalyn Metz
- Este Pope
- Scott Prater
- Robin Ruggaber
- Tim Shearer
Erin Tripp- Andrew Woods
- Dustin Slater
- Jennifer Vinopal
- Evviva Weinraub
- Jared Whiklo
- David Wilcox
- Wei Xuan
- Maurice York
- Laurie Arp
- Robert Miller
Agenda
Topic Financial Update Fedora 6 design decisionLead Laurie David
Previous Action Items
- Governance Group - Review subgroups and organization before end of June. Jennifer Vinopal Rosalyn Metz
- Maurice York and Robin Lindley Ruggaber to ask their teams how things are currently structured on disk to compare against the OCFL spec.
- Robin - the structure on disc is the way the Samvera stack structures them (for Fedora 4). Did not receive a satisfactory answer for Fedora 3. Not sure if we will move that forward. But we expect to be able to migrate.
Notes
Budget Overview and Quarterly Report:
(document was attached to email sent to group by David Wilcox)
Previous years not available due to differences in fiscal year accounting between Duraspace and Lyrasis. The complexity is too great. Robert's key number is the Net Assets. That keys him in on what resources he has to accomplish objectives.
Lyrasis views a positive revenue as a strength. Building up a reserve provides stability and flexibility and is a symbol of health.
Q: Since membership dues aren't a steady income, how are they handled?
A: Invoices go out at the beginning of the year. Institutions generally pay promptly. Lyrasis recognizes the income at 1/12th of the total per month.
Q: How do you managed delayed payments? Or Institutions that don't renew?
A: We initially expect the revenue to come in, as it is understood that it sometimes get delayed. However we quickly follow up with organizations. If people indicate they are not going to renew there is CEO/leadership engagement. We call the institution to understand the impetus for not renewing. We use this information to try to identify trends across the the 10 community supported organizations under the Lyrasis banner. This allows us to get ahead of the trend for other related products.
Q: When we look at this sheet how should we consider the total assets?
A: It follows accounting practices, so it includes reserves.
Fedora 6 Design Decision
Core issues and implementation options
David introduced the topic, which was a summary of the document linked immediately above.
Q: (MY) Why not just create a default "Version 0" for everything on the backend?
A: (DW) If we did this .... we still need to figure out what to do with that with the content later. Creating a version signals intent. But generally users just put content in Fedora and don't think about versioning.
A: (RM) OCFL assumes you are being intentional. Fedora does not assume the user is being intentional. It allows for a broader use case of individuals not thinking about what happens when they update content.
Q: Does the Fedora tech team have a preference from their technical point of view?
A: (DW)They do, but we're hesitant to introduce that this early in the discussion. We will share that later in the discussion, but we want to prejudice the discussion.
Comment
Repository owners will have 2 main concerns:
1) Can I rebuild my repository from disk?
2) Is my content versioned or not?
If technical details can be overcome, there is no reason not to version.
(RM) My concern about auto versioning is that it will create a lot of storage. This will become a point that the community will have concerns about.
(TS) Cloud costs for storage could be prohibitive with auto versioning.
(AW) Every time you create a new version, you get a new manifest. So there is a text file that gets larger with each version. On the extreme end, we have seen spreadsheets with 35,000 versions.
(EP) What are the objects that most often get large number of versions?
(AW) The above scenario was that there was a parent container that got version every time a child was modified or added. The act of creating a version in OCFL is the act of preservation. Indicating that it is ready for preservation. In Fedora the act of creating a version has been more about wanting to not lose a previous version.
Action Items
