Attending: Oliver Goldschmidt, Leila Gonzales, Chris Hallberg, Demian Katz, André Lahmann, Peter Murray, Mohan Pradhan

Apologies: Anne Christensen, Josef Moravec, Craig Murdoch (commented on agenda via email).

• Craig/Demian/André: continue updating older wiki pages as time permits. ONGOING
• Demian/Mohan: make further progress on updating/testing Koha installation and Open Data Sources wiki pages. ONGOING
• Demian/André: continue work on Lokalise integration. DONE
• Chris: Complete PR incorporating feedback from Josef's accessibility review. ONGOING
• Josef: Connect Robert Šípek with Chris for discussion of theme contributions. ONGOING
• Demian: Set 9.1 release date to October 30. DONE
• Demian: Request translations for 9.1 before September 30. DONE
• Demian: Open JIRA ticket(s) for outstanding security audit issue(s); bring ambiguous items back to this group for further discussion. DONE
• Chris: Research Javascript prototype pollution. ONGOING
• Peter: Raise issue of EU Cyber Resilience Act at next OLF Projects Roundtable meeting. DONE
• ALL: For discussion next time, consider whether to include a fundraising banner on website in conjunction with release 9.1. DONE

2023 Goals:

• Release versions 9.0 (DONE!) and 9.1 (Coming October 30)
• Hold a VuFind® Summit in Summer, 2023 linked with WOLFcon in some way (DONE!)
• Run fundraising campaign in parallel with summer conference season (DONE!)
• Complete a documentation improvement project
• Complete a website improvement project (marketing-oriented)
• Finish implementation of standard translation platform (DONE!)
• Investigate possible training partnerships and fundraising around training materials

Koha wiki page development/testing is still ongoing.

Discussion point: How do we define “done” for our documentation improvement project?

Craig's input: I feel like done is always tricky for large items, and especially for documentation which is always changing. Are there specific tasks for this particular project we can set criteria for and then evaluate as done? Maybe more important is some process for continuous review of documentation. That obviously places additional workload on people. Can it be automated (at least the notification that it’s time for review)? Can we assign a PMC member the task to check and follow up?

There are still quite a few pages flagged with issues in Susan's Google doc summary. Demian has cleaned out resolved comments and done a bit more work, but there's still quite a bit to do. Can we come up with a plan to at least look at all of the impacted pages by end of year?

Mohan volunteered to help finish reviewing outstanding pages. Demian will share the list of remaining pages with Mohan.

Work is still pending on MeSH, DoAJ, PubMed Central and NepJol “open data sources” pages. Mohan also plans to contribute documentation related to integrating SubjectsPlus (which recently had example XSLT import configs added to the project) and Moodle (which is still being researched).

Lokalise integration has been completed, and volunteer translators are beginning to use it. So far, it is working very well. Thanks again to André for significant contributions to this success.

Demian opened VUFIND-1643 to capture the brute force password discussion. Everything else has been addressed, unless we need a ticket for the prototype pollution investigation.

André suggested publishing the security report as a link from his Summit presentation. He will email a copy to Demian to ensure the correct revision is posted.

If we are going to put up a fundraising banner in conjunction with the 9.1 release, we should write and design it in time for the October 30 release.

Craig has a team member who might be able to help with this if provided with specifications/general ideas.

Leila suggested that we could start small with a donate menu item, or have a small banner right below the top menu (using the existing conference banner mechanism). Chris and Demian were in favor of the “starting small” approach. Mohan emphasized the importance of highlighting what the funds will do for the project.

Possible approach: single line of text, linking to existing donation page.

Ere mentioned that National Library of Finland is beginning to discuss this. Oliver noted that this is being discussed at TUHH as well.

With the year nearing an end, this is the only project we have not begun yet. We should begin discussing and scoping it. Demian has started the ball rolling with a pull request to revise our project description.

Some other possible items for the future:

• Develop a documentation maintenance plan
• “Good first issue” highlighting
• Investigate getting a VPAT
• Outreach to forks for new feature contributions
• Marketing project (better VuFind® definition, website improvements, etc.)
• Publication / presentation efforts related to PMC and sustainability
• Look at It Take a Village Toolkit Governance Activities.
• Look at It Take a Village Toolkit Technology Activities.
• Investigate possible uses of AI for documentation, etc.

Mohan expressed an interest in VuFind® integration with EMI systems and would like to see this on a future project goal list.

• Craig/Demian/Mohan: make further progress on documentation updates
• Chris: Complete PR incorporating feedback from Josef's accessibility review.
• Josef: Connect Robert Šípek with Chris for discussion of theme contributions.
• Chris: Research Javascript prototype pollution.
• Demian: Publish security audit report.
• Demian: Reach out to Craig about fundraising banner.
• ALL: Review and comment on website changes in pull request #3137 before Friday, October 20.