Attendees

1. Bridget Almas 
2. Jon Dunn 
3. Jennifer Gilbert 
4. Arran Griffith 
5. Scott Prater 
6. Robin Lindley Ruggaber 
7. Oliver Schöner 
8. Timothy Shearer  
9. Terry Reese 
10. Kate Dohe 
11. Rosalyn Metz 
12. Maria Esteva
13. Alexander Berg-Weiß - Parental Leave
14. James Alexander 
15.  Nicole Scalessa 
16. Dan Field
17. Tom Wrobel
18. Heather Greer Klein 

() Indicates Note Taker

Agenda

Notes:

Fedora Registry Reminder

• With launch of the website, the new registry is moving to the new site (this will be the current data long-term)
• Website Registry Working Group is reaching out in order to clean old data and get data moved to the new site. 

2024 Fedora Showcase

• Call proposal is out and open till the 30^th.

Privacy Policy Update:

• Found that the current privacy policy on Lyrasis did cover CTS programs or wasn’t gdpr compliant.
• Been working with legal to update the policy – so as of today, the policy now includes all cts programs , and is gdpr compliant. 

Paid Slack Upgrade:

• Slack has made a change so that free slack plans would lose all there chat history if not changed to a pro account by Aug. 26th
• To protect the historical slack documentation for Fedora workspace, we worked with Lyrasis to shift this plan.
• This year, Lyrasis will sponsor this license at 50%.
• This means will be able to retain the historical content allow us to retain information that can be useful for document and support.

AI Survey:

• Bridget is participating in a working group at Lyrasis discussing AI regarding AI needs within members.
• They are developing a survey, and can include questions for partner sites – so asking if we’d like to have any questions asked specifically for the Fedora community (or related to how the community may be interested in utilizing Fedora in relationship to AI processing)
• Bridget has invited members of the governance team to reach out if you have any questions or looking for clarification (bridget.almas@lyrasis.org)

Note –

• • It was noted that one question that is coming up in the community is how to feed fedora content for use in gen-ai tools.
  • Noted that OCFL format should make it easier to crawl data
    • https://docs.google.com/document/d/17FnViabg6j3p0eVjLvE20ath4vbvbOP6dbURxtYsIpw/edit?usp=drivesdk
  • Nicole notes that DLF will be having a hackathon where one area will focus on the legal and ethical considerations for born digital access. Contact DLF – info@diglib.org 
    • Occurring Aug. 6, 2-3.
  • Noted a generalized need related to using AI to support some of the larger accessibility issues found within digital content.
  • Question about blocking ai bots
    • AWS’s Firewall has an option to block bots. Looks like they also keep a list that may be available.
  • Noted in potential AI bot harvesting and changes to accessibility rules, there are emerging challenges that could make it more difficult to continue to keep repositories open as risk models change.
  • AI4LAM community – there is a new speech to text working group
    • Looking specifically at ways AI could be leveraged to aid challenges around accessibility
    • https://docs.google.com/document/d/1Z65tdXmazxn5KAFHj_mf8TEcXaGpAOh7kNvmt8QKeaE/edit?usp=sharing 

Financial Update:

• Reviewed the Year-end financial update report

Governance Elections:

• There will be:
  • Copper Level: 1
  • Bronze Level: 1
  • Silver Level: 2
  • Gold Level: 3
  • Community Member Seats: 1

• https://wiki.lyrasis.org/display/FF/2024+-+2026+Term+-++Call+for+Nominees

Brainstorming Pt. 2 – building new Contributor Opportunities

• https://docs.google.com/document/d/1SG_885VQ8SM7L4twgwxJwbH_MfnPyMPCLeEgTubd7yQ/edit?usp=sharing

Last session, we did a brainstorming session to find new ways to help folks find ways to contribute to the community (beyond just contributing code).  This is a discussion of the top topics.

Couple questions and notes:

• One area was reaching out to service providers to have some discussions around contributions and things that they see as needs.
• Question: Do institutions find value in being granted a membership level?
  • Feedback seems to be that the membership level seems to be less important for institutions. Rather, contributions are made because of the value the tool has to the environment.

• As part of this, there is an in-kind contribution policy. Noted this needs to be reviewed.
• Google Analytics will be on the new website – so we have now have a way to see how traffic is being driven to the website and what is being primarily accessed.
• Question: Regular tech team calls oriented to developer-curious Fedora users
  • This had been done in the past, but keeping momentum has historically been an issue.
  • Pointed at Islandora Community which seems to be doing this very well.
• Attempt to create a more attractive user interface
  • The interface was initially developed for Fedora 4 and never was developed for use. There was a discussion/desire to look at refreshing this interface.
    • This is where we’d need to look at front-end developers (these are not on our committers group currently)
    • This could potentially be a good opportunity to bring in new contributors to aid in the front-end and accessibility review/remediation on this front.

Also noted – specific interest in mini-camps/hack-a-thons, etc. are of interest.  There will be some ongoing discussion about how we might bring some additional collaborative contributor events. 

Pop-up Topics

From Tim:

• From his campus, he’s hearing from his Security Team a concern related to on-off academic software that can increase the security exposure/risk to campus.
• Led to a discussion thinking about continuity and how our community can position Fedora to design security directly into the application development. And how the community addresses identified security concerns quickly.   [This feels like a larger topic that might make for a good strategic planning discussion]