About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community:pmc_meetings:minutes20231017

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
community:pmc_meetings:minutes20231017 [2023/10/13 11:00] – [2. Goal Review] demiankatzcommunity:pmc_meetings:minutes20231017 [2023/10/31 11:28] (current) – [Action Items] demiankatz
Line 1: Line 1:
 ====== PMC Meeting: October 17, 2023 ====== ====== PMC Meeting: October 17, 2023 ======
  
-:!: This document is currently an agenda; it will be converted to minutes following the meeting.+AttendingOliver Goldschmidt, Leila Gonzales, Chris Hallberg, Demian Katz, André Lahmann, Peter Murray, Mohan Pradhan
  
-Attending:  +Apologies: Anne Christensen, Josef Moravec, Craig Murdoch (commented on agenda via email).
- +
-Apologies: +
  
 ===== 1. Review of Action Items from Previous Meeting ===== ===== 1. Review of Action Items from Previous Meeting =====
Line 38: Line 36:
  
 Discussion point: How do we define "done" for our documentation improvement project? 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 [[https://docs.google.com/document/d/1v7ygNl-Wfd8RzXazUcnZH3dgNXSY2Vxs-vwEc_VK0XI/edit|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). 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).
Line 43: Line 47:
 ===== 4. Translation Platform ===== ===== 4. Translation Platform =====
  
-Lokalise integration has been completed, and volunteer translators are beginning to use it.+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.
  
 ===== 5. Security Audit ===== ===== 5. Security Audit =====
  
 Demian opened [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1643|VUFIND-1643]] to capture the brute force password discussion. Everything else has been addressed, unless we need a ticket for the prototype pollution investigation. Demian opened [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-1643|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.
 ===== 6. Fundraising ===== ===== 6. Fundraising =====
  
 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. 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.
  
 ===== 7. EU Cyber Resilience Act ===== ===== 7. EU Cyber Resilience Act =====
 +
 +Ere mentioned that National Library of Finland is beginning to discuss this. Oliver noted that this is being discussed at TUHH as well.
  
 ===== 8. Website Improvement Project ===== ===== 8. Website Improvement Project =====
  
-With the year nearing an end, this is the only project we have not begun yet. We should begin discussing and scoping it.+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 [[https://github.com/vufind-org/vufind/pull/3137|pull request to revise our project description]].
  
 ===== 9. Possible Future Actions ===== ===== 9. Possible Future Actions =====
Line 73: Line 87:
  
 ===== Other Items ===== ===== Other Items =====
 +
 +Mohan expressed an interest in VuFind® integration with EMI systems and would like to see this on a future project goal list.
  
 ===== Action Items ===== ===== Action Items =====
 +
 +  * Craig/Demian/Mohan: make further progress on documentation updates
 +  * Chris: Complete PR incorporating feedback from [[https://docs.google.com/document/d/1qII8IRWOk0eP3er-91C5clhTfQq92yPkUbvAtq3xdNU/edit?usp=sharing|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 [[https://github.com/vufind-org/vufind/pull/3137|pull request #3137]] before Friday, October 20.
  
 ---- struct data ---- ---- struct data ----
community/pmc_meetings/minutes20231017.1697194806.txt.gz · Last modified: 2023/10/13 11:00 by demiankatz