Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://lyrasis.zoom.us/j/88068382811
- Meeting ID: 880 6838 2811
- Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia
Join fedora-project.slack.com on the "tech" channel
- Self-register at: http://slack.fcrepo.org/
Attendees
- Danny Bernstein
- Arran Griffith
- Jared Whiklo
- Peter Winckles
- Ben Pennell
- Calvin Xu
- Michael Ritter
- Demian Katz
- Thomas Bernhart
- Robin Lindley Ruggaber
- Jennifer Gilbert
- Timothy Shearer
Agenda
- Announcements
- Leaders and Committers On How to Encourage Fedora Users to Register
- Why the registry is important
- The state of the registry now
- What can we do?
- In the UI
- on the Command line
- On our ecosystem projects (camel toolbox, migration utils, etc)
- Islandora
- Samvera
- NLM Migration Update
- New Tickets
- FCREPO-3811 - Getting issue details... STATUS
- FCREPO-3812 - Getting issue details... STATUS
- New Tickets
- 6.2.0 Release
- PRs that need to be resolved
- Jira, Slack, Github integrations
Notes:
- All of Leaders and Steering was invited.
- Governance wants to take action on enhancing our registry.
- We can't legally reach out to registered users due to GDPR concerns.
- We need a better understanding of our installed base.
Without an accurate registry we can't make the case for Fedora:
- we can say who is using it
- we can't say how many people are using
- we can say where in the world it is deployed
- we're missing use cases
- we're missing diverse voices
- which is to say we're missing the critical feedback loop to grow the community
At stake in how we can connect users to the registry:
- theres's law
- privacy issues
- there's community perception
How would we get information about Fedora's that are part of a prefab tech stack?
- Samvera
- Islandora
To bring the tech team to this problem is vital.
We have an existential threat to our project because we don't know have data: we are not creating spyware, we are trying to help our community.
From Jakov:
OJS has a beacon feature which we might consider replicating in Fedora
- Has an opt out - perhaps we should consider opt in
- generate unique id
- send information to Fedora
- What information:
- Fedora Version
- IP
- Institution
- Country
- Contact Email
- Periodically send stats (object count, byte count)
- What information:
Provide ability to offer different levels of information
Possibly remind folks when they upgrade the software?
What data does not present risk?
Scott's Notes:
Many Fedora 3's have been inherited from the original implementers by IT groups, digital archivists and collections managers who may not be plugged into the community via email lists, etc.
- So I'd recommend an outreach effort that focused on publicizing Fedora 6 and migration help outside the usual channels
- posting to forums like code4lib, the dspace forum (many institutions that run DSpace also run Fedora), NDSA lists, PASIG lists, Samvera, Islandora, etc
- Digital curation listserv as well