Differences

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

--- community:pmc_meetings:minutes20230815 [2023/08/15 14:18] – [8. Governance Document Review] demiankatz
+++ community:pmc_meetings:minutes20230815 [2023/08/18 16:24] (current) – [Action Items] demiankatz
@@ Line 1: / Line 1: @@
 ====== PMC Meeting: August 15, 2023 ======
-Attending:
+Attending: Anne Christensen, Oliver Goldschmidt, Leila Gonzales, Chris Hallberg, Demian Katz, André Lahmann, Ere Maijala, Josef Moravec, Mohan Pradhan
-Apologies:
+Apologies: David Maus, Craig Murdoch
 ===== 1. Review of Action Items from Previous Meeting =====
@@ Line 47: / Line 47: @@
 André has received a first draft of the audit, which contains some suggestions but no huge surprises.
+Initial results were discussed. André will take some follow-up questions back to the vendor.
 One of our new members suggested finding a way to issue cybersecurity alerts for VuFind® that can make it into global CVE databases.
@@ Line 55: / Line 57: @@
 Demian proposes setting up a vufind.org/donate URL that will make it convenient to donate. This probably needs multiple links -- i.e. to the credit card form, the "request an invoice" form, and the RSP form. Maybe we can make big buttons to make this friendlier.
+We have received a few donations so far, as well as a new RSP application. Demian is currently waiting for financial processing on these. He plans to start a spreadsheet in the project's Google Drive to centrally track everything, as it is beginning to get complicated.
 ===== 8. Governance Document Review =====
 Demian's notes:
-  * Should we mention other communication methods like Slack somewhere? Might be best not to name a specific technology, but maybe somewhere under "Contributors" we should add a link to the community support page. The Tech list is the primary method listed throughout the document, but in practice, Slack seems to be more popular.
+  * Should we mention other communication methods like Slack somewhere? Might be best not to name a specific technology, but maybe somewhere under "Contributors" we should add a link to the community support page. The Tech list is the primary method listed throughout the document, but in practice, Slack seems to be more popular. Consensus agrees that adding link to more options is desired.
-  * I've been publishing committer vote results in the newsletter, which in turn gets announced on the Tech list. This follows the letter of the document but maybe isn't exactly what we originally intended. Is adjustment needed/worthwhile?
+  * I've been publishing committer vote results in the newsletter, which in turn gets announced on the Tech list. This follows the letter of the document but maybe isn't exactly what we originally intended. Is adjustment needed/worthwhile? Maybe just mention newsletter instead of explicitly referencing Tech list. DK will adjust.
-  * The sentence "The Treasurer is not required to be a member of the PMC, but the Secretary should be a member of PMC." is somewhat ambiguous -- it seems to be saying both positions are PMC-optional, but maybe saying that more strongly for the Secretary. Should we change the Secretary requirement to "must" to make things more clear?
+  * The sentence "The Treasurer is not required to be a member of the PMC, but the Secretary should be a member of PMC." is somewhat ambiguous -- it seems to be saying both positions are PMC-optional, but maybe saying that more strongly for the Secretary. Should we change the Secretary requirement to "must" or "is required" to make things more clear? No objections to changing this.
-  * We say that "Any committer can merge a trivial contribution, even if it is their own." I think we should remove "even if it is their own" since GitHub rules currently prevent this.
+  * We say that "Any committer can merge a trivial contribution, even if it is their own." I think we should remove "even if it is their own" since GitHub rules currently prevent this. Rephrase to make these exempt from 72-hour waiting period, but remove "even if it is their own" language. No objections to this.
+Ere noted that we're still using https://vufind.org/jira as our JIRA link, even though it has moved. This is intentional in case of future moves/changes, to keep the URL under our control.
 ===== 9. Possible Future Actions =====
@@ Line 78: / Line 84: @@
 ===== Other Items =====
+  * Moravian Library is willing to contribute in creating new theme. [[https://github.com/sipek-mzk|Robert Šípek]] could work on it. Demian will devote some time to this on the next Community Call.
 ===== Action Items =====
+  * Craig/Demian/André: continue updating older wiki pages as time permits.
+  * Demian/Mohan: make further progress on updating/testing Koha installation and Open Data Sources wiki pages.
+  * André: move security audit process forward (get final draft from vendor, get answers to questions, find out about CVE process if possible).
+  * Demian/André: continue work on Lokalise integration.
+  * Chris: Open PR incorporating feedback from [[https://docs.google.com/document/d/1qII8IRWOk0eP3er-91C5clhTfQq92yPkUbvAtq3xdNU/edit?usp=sharing|Josef's accessibility review]].
+  * Demian: Create https://vufind.org/donate URL that redirects to membership page; incorporate new credit card form when ready.
+  * Demian: Start spreadsheet to track memberships/donations.
+  * Demian: Open PR(s) addressing proposed governance document changes.
+  * Josef: Connect Robert Šípek with Chris and the next Community Call for discussion of theme contributions.
 ---- struct data ----
 properties.Page Owner :
 ----