This is an old revision of the document!
Table of Contents
VuFind® Community Call Minutes: March 7, 2023
Attending:
Agenda
1. Development Planning
Newsletter Highlights
The February, 2023 Newsletter was discussed.
Pull Request Review (9.0 milestone)
- #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
-
- Next step: finish review/testing - CK / CH / DK
- #2699 - Remove unused folder_id field from search table
- Next step: finish review - CH
- #2741 - Improve button styling in critical fix page
- Next step: finish review - CH
JIRA Ticket Review (9.0 release, without an existing pull request above)
Not Started - No Blockers
- VUFIND-1566 - Clean up/standardize Javascript lib directory [assigned to CH]
- Next step: DK has proposed next steps; CH will implement soon.
- VUFIND-1567 - Update language translation files for release 9.0
- Next step: DK will start later today.
PHP Version 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?
Release Date Discussion
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.
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?
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?
3. Open Q&A / Other Topics?
Next Call
The next call will be Tuesday, April 4, 2023 at 9am Eastern Standard Time (14:00 GMT).