...
- Melissa Anez
- Chris Awre
- Thomas Bernhart
Danny Bernstein- Robert Cartolano
- Stefano Cossu
- Dan Coughlin
- Jon Dunn
- Dan Field
- Raman Ganguly
Jennifer GilbertMark JordanDanny Lamb- Rosalyn Metz
- Este Pope
- Scott Prater
- Robin Ruggaber
- Tim Shearer
- Andrew Woods
- Dustin Slater
- Jennifer Vinopal
- David Wilcox
- Arran Griffith
- Maurice York
- Laurie Arp
Robert Miller- Ben Wallberg
Agenda
Advanced Tables - Table Plus | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Previous Action Items
Notes
Financial Update
Quarterly Financial
membership is a little lower, budgeted 15% but are at 22%
Grant started in Sept 1, and that makes up a bit for the lower membership
This isn't unexpected, we are planning to be spending a bit more than taking in throughout the year
There are less than 10K of outstanding membership fees that we are awaiting, a vast majority have come in already
Budgeting Forecasting for Next Year 2021-22
...
Started planning for this prior to COVID because there were concerns on the existing membership model for the last 12-18 months
We are working with universities on timing, if that is helpful to send it early or late in the year
Discussions has begun on what do we need to do to absorb anticipated losses
as a leadership group only dipped into a portion of the reserves, in the hope of getting the grant that would cover up for losses as well.
...
Broad view of Membership
...
Started planning for this prior to COVID because there were concerns on the existing membership model for the last 12-18 months
Broad view of Membership
Membership breakdown
Most folks that cancelled did so because of budget issues related to COVID, there are some technical issues, but the vast majority are budget cuts related to COVID.
Fedora 6
Continuing to make progress towards Fedora 6
first alpha release is out, not feature complete, but very close
any features missing are likely not used features
please pull it down and test
next version of alpha will be out next week
what is the criteria for putting out beta release
proposed
feature complete
migration tooling (3, 4, 5 -> 6)
validation tool
initially this will only exist for Fedora 3 and development will begin next week
If we need further validation tooling, we can create it, but based on surveys this didn't seem to be necessary (migration tooling for Fedora 4, 5)
documented expectations performance/scale criteria
rates for migration (size of content should migrate in ___ time)
collections of ____ size should get a response time of _____
need collaboration to get people to run these tests and create the expectations for these tests
documentation complete
Jira items
All priority flagged red are prioritized for beta,
All priority flagged blue are prioritized for production
what is the criteria for putting out 6.0 production release
proposed
Stakeholder sign-off
Migration tooling - stakeholder sign-off
Validation tool stakeholder sign-off
Validation of integration -
samvera
islandora
F6 documentation complete
Performance/Scale results documented
Discussion on configuration of F6
new version created with any change to the file, version is created automatically
new version created only when it's told to create a new version by the application sitting on top of it
If this is the configuration there is an outstanding pull request to define this extended functionality within the context of OCFL
We could use a review and feedback on this pull request, please encourage team to look at this.
Not positive on the level of desire of this feature and what makes the most sense. We need feedback on this to understand the level of interest to the priority.
We need comments and feedback on the extension and pull requests and a particular focus on the technical details on this PR
Four Actions coming out of this:
Review and provide feedback and signing off on criteria for the beta release
Review and provide feedback and signing off on criteria for the production release
Look at google doc linked in the agenda and put in expectations for performance and scale
Existing performance tests and results: https://wiki.lyrasis.org/display/FF/Fedora+6+Test+Results
Providing feedback on the mutable head pull request: https://github.com/OCFL/extensions/pull/17
IMLS Fedora migration grant
...
- David: good progress. Starting migration tooling next week with sample data. Full production set up next year. Noting dependency on Fedora 6 development - delays in Fedora 6 might affect meeting grant deadline. We can continue working on other grant-related things while we wait for Fedora 6 dev to advance.
Membership Model Proposal
- summary "With the current state of membership renewals, it has been proposed that changes need to be made to the current membership model to ensure recurring income. Through extensive discussion, 3 proposals were generated to assist with short, medium, and long-term actions. We will break into smaller groups to discuss the recommendations with the goal of approving short-term actions and refining the proposed medium-term actions."
- Rosy: motivated by concerns about reduction in members and member $$.
- Revenue ops: looking at value-added initiatives, membership levels, services related to migration. What do our users need and want?
- if you need receipt language changed to say something to meet your orgs needs, let us know
- medium-term: looking to understand fedora installations and what data we have and could
...
- collect. Who is using fedora? Where are they? Can we collect this data in a more automated way? This data will help us better understand what users need/want and what we might charge for.
- Data will be handed off to Governance group - please join us in that group to help with this work. Rosy will send an email reminder.
- Emily will join the governance group
- Small group discussions about what data we want to collect about installations, to help us better understand our membership - report outs:
- group 1 (forthcoming from David)
Transparency
Need to know the data Fedora is sending
Maybe a reward for sending the data
Needs to be opt-in, maybe at the point of installation
Here is the data we want to collect, select which data you want to send
- group 1 (forthcoming from David)
...
Might need a form to collect data - what can be collected auto vs. manual
Real-time data - can we collect automated stats?
Technical data - software version information
Only collect what we need - don’t need to profile the entire system
Front-end - Islandora/Samvera, etc.
This is a shared problem - maybe the communities can coordinate
Are there other examples of server-side OSS that does this?
Drupal may do some of this reporting
GraphDB triplestore product does this as part of the registration process
How to incentivize
Get on a list for security fixes
Might be a good way to get contact information
Dashboard with statistics
- group 2 - is a way to communicate to the community, update them about updates/bugs. Need to make it opt-out, have it be part of installer process. Need to explain to the community this change ahead of time. SHould be an ongoing process (not just at installation) - could continue to collect ongoing info about their installations.
- Rob: institutions should not be allowed to opt out of sharing this info (even though we need to allow individuals to opt out).
- Types of data to potentially collect
- Nature of installation - test, production
- Fedora version
- Geo location
- Fedora and system config
- Institution name
- Contact info
- URL
- Frontend application
- On-going reporting
- Repository size over time
- Potentially tie-in with Islandora and Samvera
- Automated? or opt-in? - interest in "opt-in"
- Hit a button to submit, or not
- Ability to include user-input data, details that can not be auto-collected
- Application download stats
- Also can build from source
- Skepticism about how it may work and how it may be received
- Although, not an uncommon pattern
- Need to provide transparency on when info is being sent
- Enables support for upgrade and security patch messaging
- Need clear community messaging
- group 3 (more forthcoming from Rosy) - mandatory: institution name and institutional email address; Opt-in: financial and technical contact. Need language to say why we're collecting this info. Also should collect ongoing data, including number of objects in the repo when updates are applied. Not sure how this would be received by the community and also discussion about technical feasibility. Big discussion about GDPR and how we would remove personal contact info when needed.
- This would require development by the team.
- Is ArchiveSpace a model for us: low-cost way to become member ($300?). Could be a good way to expand the membership base, total number of participants. Should link with releast of Fedora 6 (a kick-the-tires membership approach).
Last topic, Reports, ran out of time - David will follow up via email
Action Items
- All - OCFL versioning - please review and provide feedback on the following pull request: https://github.com/OCFL/extensions/pull/17
All - Review and provide feedback and signing off on criteria for the beta release
All - Review and provide feedback and signing off on criteria for the production release
All - Look at google doc linked in the agenda and put in expectations for performance and scale
Existing performance tests and results: https://wiki.lyrasis.org/display/FF/Fedora+6+Test+Results
Providing feedback on the mutable head pull request: https://github.com/OCFL/extensions/pull/17