Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20230418
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
community_call:minutes20230418 [2023/04/11 13:23] – demiankatz | community_call:minutes20230418 [2023/04/11 13:24] – demiankatz | ||
---|---|---|---|
Line 20: | Line 20: | ||
* Next step: DK will close this when the release is packaged up, and will post a comment with the current translation percentages. | * 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 | + | ==== 2. VuFind® 9.0: What's New / What's Changed ==== |
- | Discussion: release | + | Demian presented on the changes in the upcoming |
- | 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. | + | ==== 3. Open Q&A / Other Topics? ==== |
- | === 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. | ||
- | |||
- | April 24th was agreed upon as a good date to allow ample time for translation in light of holidays, etc. | ||
- | ==== 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/ | ||
- | |||
- | * 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/ | ||
- | |||
- | ==== 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/ | ||
- | |||
- | 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, | ||
===== Next Call ===== | ===== Next Call ===== | ||
community_call/minutes20230418.txt · Last modified: 2023/06/07 04:30 by ubilmenau