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_call:minutes20221101

VuFind® Community Call Minutes: November 1, 2022

Attending: Chris Hallberg, Demian Katz, Claas Kazzer, Ere Maijala, Peter Murray, Susan Turkel

Agenda

1. Development Planning

Newsletter Highlights

The October, 2022 Newsletter was discussed.

Pull Request Review (9.0 milestone)

  • #2378 - Make MenuButton component [under discussion]
    • Next step: reply to outstanding review comment (should we tolerate missing menuItems values?) - CH
  • #2400 / VUFIND-1533 - Wrapped link elements should not have space between the lines [in progress]
    • Next step: finish testing and fixing outstanding style issues - CH / DK
  • #2447 - AJAX status standardization/modernization [in progress]
    • Next step: test/review/reply to review comments - DK / JL / Overdrive user(s) / CH
  • #2492 - Add refresh buttons to jump menu controls [waiting on #2378]
    • Next step: decide when to add buttons and when to use MenuButton controls from #2378
  • #2543 - ThemeInfo: Fix getMergedConfig [in progress]
    • Next steps: finish discussion, ensure full test coverage - CH / DK
  • #2513 - Remove password check in PAIA patronLogin() if client_credentials is used as grant_type [in progress]
    • Next step: awaiting review - OG
  • #2580 / VUFIND-1573 - Upgrade Solr for release 9.0 [Solr 8 minor upgrade completed; Solr 9 major upgrade in progress]
    • Next step: decide whether Solr 9 belongs in release 9.0 or 10.0 of VuFind®
  • #2596 / VUFIND-1556 - Handle relator URIs during indexing [in progress]
    • Next step: approved by EM, awaiting possible secondary review - AL / MT
  • #2600 / VUFIND-1474 - Remove deprecations from 8.x [in progress]
    • Next step: finish code and review - SK / DK
  • vufind-browse-handler#39 / VUFIND-1525 - Update browse handler to use call number normalizers from org.marc4j.callnum package [in progress]
    • Next step: awaiting review - TO

JIRA Ticket Review (9.0 release, without an existing pull request above)

In Progress
  • VUFIND-1514 - Modernize front end build environment [assigned to CH]
    • Next step: give tech demos - CH ; discuss - Community
Not Started - No Blockers
  • VUFIND-1563 - Blowfish encryption fails under Ubuntu 22 and Fedora 36 [assigned to CH]
  • VUFIND-1568 - Make Solr port configurable during installation [assigned to DK]
  • VUFIND-1396 - Investigate possibility to deprecate the Context view helper [assigned to EM]
  • VUFIND-1529 - Configurable sort tie-breaker field [assigned to SK]
  • VUFIND-1538 - Add retraction watch support to DOI lookup functionality [assigned to DK]
  • VUFIND-1541 - Add Mink test coverage for Markdown rendering [assigned to CH]
  • VUFIND-1547 - Normalize search event namespace [unassigned]
  • VUFIND-1535 - Make search history labeling more consistent [assigned to DK]
  • VUFIND-1566 - Clean up/standardize Javascript lib directory [assigned to CH]
Not Started - With Prerequisites
  • VUFIND-1570 - Update browse handler in release 9
    • Prerequisites: complete all Solr and browse handler updates first.
  • VUFIND-1567 - Update language translation files for release 9.0
    • Prerequisite: complete all changes that impact language files.

2. Technology Demo for Javascript Tooling Planning

Chris proposed using package.json scripts instead of using Grunt (which is no longer widely used and is somewhat hard to understand). Some tasks will “just work” (like eslint, which is a simple command that loads a default configuration file), but other tasks may require custom scripts (like less/sass, which needs to account for our theme inheritance, etc.). Chris proposes adding a “scripts” directory to hold these scripts.

Chris also raised the issue of Javascript modernization – should we use React, Vue.js, Typescript, etc. Possible compromise that could improve code quality without increasing complexity of deployment/development: annotate files using jsdoc for types, then use Typescript's tsc to validate the files. Offers a possible “best of both worlds” solution.

Next steps: Chris will set up a PR to begin the grunt –> npm conversion, starting with SCSS compilation (which Claas will help test).

3. Other Topics?

Reminder: next month, Daylight Saving adjustments will be complete worldwide, and this meeting will take place in Eastern Standard instead of Eastern Daylight; please adjust your local calendar if necessary.

Next Call

The next call will be Tuesday, December 6, 2022 at 9am Eastern Standard Time (14:00 GMT).

community_call/minutes20221101.txt · Last modified: 2022/11/01 13:40 by demiankatz