...
Removal of one-click option. Designed for testing, not for production.
Relies older version of Jetty; relies on older version of Java. People now use docker. Currently broken; nobody in community seems to miss it.
3. Membership funding campaign
Goal: get it out in advance of membership renewals
Ties to budget proposal -- raise at least $25,000
Arran has messaging created, asks community/governance help getting the word out.
Buys us a year to continue to work on a long-term sustainable financial model.
$500 more from each member would meet our goal.
Membership level increases: higher levels bring more benefits, some new Lyrasis benefits may be introduced
Messaging calls out concrete technical deliverables funds will cover
Arran showed her draft poster. Arran will take feedback on it. Scott and Arran working on more formal targeted message for executive decision-makers.
Is it a one-time ask, or an indefinite increase? Whatever we can get.
4. Tech Survey results
Posted on Lyrasis now blog.
Goal: priorities for next 18 to 24 months
After months of internal work and discussion, determined these projects in priority order:
1. Performance improvements
2. Fedora Technical Documentation Upgrades
3. Migration support
4. Network of shared implementations
5. HTML UI Facelift
Resources for Fedora support is challenging; most cannot contribute to code, but may be able to tackle concrete tasks (testing, documentation, etc.)
Much of the work is already in progress; no surprises about priorities
expressed by community.
Plan: use this prioritized list of projects to create and publish a community roadmap, tied to messaging and funding
Q: Can community roadmap be published in time for funding campaign? A: Arran is planning on it, yes.
5. Website working group
Contracted outside designer to help design it. New site slated to be released
in June.
Website working group activity: challenging to organize info across
Duraspace, Lyrasis, wiki, Google docs, and Github. Staging work with website
first, then wiki.
Thinking about information architecture, different user audiences, user
experience (DRY, etc.), and accessibility (part of what contractor is
delivering).
Where we are: info architecture, audiences, design pretty strong, in QA stage.
Arran will release website for governance review soon.
After website, working group will turn towards redoing the wiki, probably from scratch.
Goal: come up with same terms, images, etc -- brand identity kit -- for everyone to use when talking about Fedora.
6. Community Participation update
Islandora update: scramble to upgrade to Drupal 10. Now in testing phase. Unexpected update was a big hit to budget.
Area for improvement: make community projects that rely on Fedora more aware of what Fedora is, its value. Perhaps a presentation to Islandora community? Next Islandora GLAMmeeting will focus on infrastructures.
Hyrax Fedora 6 Working Group: following on work with Sirenia (Hyrax 5, Valkyrie, and Fedora 6), uncovered some bugs (one Fedora-related, now squashed). Reissued scope and deliverables, to investigate path to fully-functional Sirenia, and performance testing of it. Due to Hyrax data modelling, approach to migrate is to export Fedora data, then reimport into Sirenia test stack.
7. Future discussion topic: in-kind contributions. Path to Fedora governance, and how it translates to membership level? Currently offered on ad hoc basis.
Next activity: membership funding campaign. Volunteers welcome