Differences

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

--- community_call:minutes20230418 [2023/04/11 13:22] – created demiankatz
+++ community_call:minutes20230418 [2023/06/07 04:30] (current) – [VuFind® Community Call Minutes: April 18, 2023] typo in attendee name corrected ubilmenau
@@ Line 1: / Line 1: @@
 ====== VuFind® Community Call Minutes: April 18, 2023 ======
-Attending:
+Attending: Dana Geier, Chris Hallberg, Ursula Kampling, Demian Katz, Rodolfo Marraffa, Ere Maijala, Andrea Buntz Neiman, Mario Trojan, Susan Turkel
 ===== Agenda =====
@@ Line 13: / Line 13: @@
 === Pull Request Review (9.0 milestone) ===
-  * ...
+  * Two scheduled pull requests proved to be more complex than anticipated and will need to be rescheduled for a future release (9.1 or 10.0). These are accessibility enhancements, but the release will not be broken without them.
+    * [[https://github.com/vufind-org/vufind/pull/2723|#2723]] - Component: confirmation menu
+      * Status: significant work still needed (existing functionality needs to be fully ported)
+    * [[https://github.com/vufind-org/vufind/pull/2814|#2814]] - Replace jumpMenu controls with menu-button components
+      * Status: basic functionality complete, but styling and accessibility polishing are needed
+  * All other work is complete (including several recent contributions that were not originally planned for, but which were appropriate for inclusion in the release -- e.g. recent autocomplete attribute additions).
 === JIRA Ticket Review (9.0 release, without an existing pull request above) ===
@@ Line 20: / Line 25: @@
     * Next step: DK will close this when the release is packaged up, and will post a comment with the current translation percentages.
-=== PHP Version Discussion ===
-Discussion: release 9.0 is currently slated to release with support for PHP 7.4. Should we drop this and move to 8.0 since 7.4 is now at end of life? Or should we consider releasing as-is (to avoid unexpected last-minute dependency problems) but raising the version requirement in release 9.1?
+=== Next Meeting Plans ===
-No objections to sticking with 7.4 for 9.0 and bumping to PHP 8.0 for 9.1. Should put a warning on 9.0 release warning of this plan.
+We should review unscheduled open pull requests and determine which should be scheduled for 9.1 and which for 10.0.
-=== Release Date Discussion ===
+==== 2. VuFind® 9.0: What's New / What's Changed ====
-Demian proposed releasing version 9.0 in April, as it seems that work is nearly complete, and we just need to allow time for outstanding translation work to be completed.
+Demian presented on the changes in the upcoming 9.0 release; a recording will be posted soon.
-April 24th was agreed upon as a good date to allow ample time for translation in light of holidays, etc.
+==== 3. Open Q&A / Other Topics? ====
-==== 2. Technology Discussion: Documentation ====
-One of the areas of potential improvement identified by the recent documentation survey is the approach to PHPDoc comments. Our basic approach hasn't changed much since 2007, but the PEAR standards are now very old, and language features like improved type support render some aspects of the comments redundant. Is there an opportunity to do things in a more modern way without losing the benefits of our current approach?
+On the next call, the plan is to talk about the lokalise translation platform with André Lahmann and work out a plan for streamlining the i18n process in time for the next release.
-Possible actions/things to investigate:
-  * Can we replace some/all of our PEAR style rules with PSR-12?
-  * Desirable: raise line length from 80 characters to 120 characters (This proposal was received positively).
-  * Can we reduce redundancy in comments without losing the ability to enforce full/consistent documentation?
-==== 3. Next Call Date ====
-Demian will be out of office on the next scheduled call date (April 4) and others will be away the following week (April 11), so it was agreed to push the date back to April 18.
-==== 4. Open Q&A / Other Topics? ====
-Mario followed up on the Google Scholar issue discussed in a previous call. The http-equiv meta header is causing problems. Mario found a workaround that seems to help. Demian proposed opening a PR so we can discuss whether core changes are needed, and re-evaluate why we're using http-equiv and whether we should do things differently.
-Mario also mentioned ongoing discussion about visualizations of author/subject data to present information in different ways to assist researchers. Mario is interested in feedback on tools, technologies and approaches. Stephanie shared [[https://linkedjazz.org/52ndStreet/|linkedjazz.org]] as an inspirational example. Demian mentioned [[https://openlibraryfoundation.atlassian.net/browse/VUFIND-825|VUFIND-825]] as an early effort at building something like this.
-Stephanie offered to help with Bootstrap 5 upgrading and/or other theme-related refactoring. Demian described the current plan (refactoring to components, and using the abstraction of components to make code more feature-agnostic). Stephanie is willing to help with this as needed if time permits.
-Mario asked about the status of deduplication. Demian explained the relationship between deduplication and RecordManager, and talked about the advantages of using RecordManager as a complement to and/or replacement for SolrMarc. Demian was not sure whether you could harvest records into RecordManager, generate deduplication IDs, and then export MARC with those IDs injected, but suspects that such a feature might be possible even if it does not already exist; he will check with Ere.
 ===== Next Call =====
-The next call will be Tuesday, April 18, 2023 at 9am Eastern Standard Time (14:00 GMT).
+The next call will be Tuesday, May 2, 2023 at 9am Eastern Daylight Time (13:00 GMT).
 ---- struct data ----