Attending:

The February, 2023 Newsletter was discussed.

• #2447 - AJAX status standardization/modernization
  • Next step: finish testing and fixing outstanding issues - CH / DK
• #2492 - Add refresh buttons to jump menu controls
  • Next step: revise to use MenuButton controls from #2378
• #2624 / VUFIND-1514 - Modernize front end build environment, replace Grunt with NPM scripts
  • Next step: Discuss / finish TODO list - CH
• #2669 / #2723 - Correct non-validating cart dropdown menus
  • Next step: finish review/testing - CK / CH / DK
• #2685 - FOLIO: support proxy user requests
  • Next step: merge if no one objects - DK
• #2729 / VUFIND-1595 - Finalize dependencies for 9.0 release
  • Next steps: review/merge php-cs-fixer updates; update Solr; update swagger-ui. - DK / EM

• VUFIND-1566 - Clean up/standardize Javascript lib directory [assigned to CH]
• VUFIND-1593 - Ensure JSON encoding of strings embedded in HTML is properly escaped [unassigned]

• VUFIND-1567 - Update language translation files for release 9.0
  • Prerequisite: DK can start work after #2685 is merged.

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?

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.
• Can we reduce redundancy in comments without losing the ability to enforce full/consistent documentation?

The next call will be Tuesday, April 4, 2023 at 9am Eastern Standard Time (14:00 GMT).