Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20230502
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
community_call:minutes20230502 [2023/05/01 12:55] – [1. Development Planning] demiankatz | community_call:minutes20230502 [2023/05/02 13:58] (current) – [3. Open Q&A / Other Topics?] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VuFind® Community Call Minutes: May 2, 2023 ====== | ====== VuFind® Community Call Minutes: May 2, 2023 ====== | ||
- | Attending: | + | Attending: |
===== Agenda ===== | ===== Agenda ===== | ||
Line 23: | Line 23: | ||
* [[https:// | * [[https:// | ||
* Next step: backport functionality from KohaRest (if appropriate) or close (if no longer needed). | * Next step: backport functionality from KohaRest (if appropriate) or close (if no longer needed). | ||
+ | * Decision: close PR -- KohaRest meets the need | ||
* [[https:// | * [[https:// | ||
* Next step: finish implementation | * Next step: finish implementation | ||
Line 29: | Line 30: | ||
* [[https:// | * [[https:// | ||
* Next steps: resolve conflicts; fix lightbox problems which currently prevent this from working consistently. | * Next steps: resolve conflicts; fix lightbox problems which currently prevent this from working consistently. | ||
+ | * Decision: milestone 10.0 (requires lightbox refactoring and/or improvements to login system -- i.e. intermediate "login success" | ||
* [[https:// | * [[https:// | ||
* Next steps: decide whether this adds significant value beyond what phpstan already offers; work through outstanding problems if worth keeping. | * Next steps: decide whether this adds significant value beyond what phpstan already offers; work through outstanding problems if worth keeping. | ||
+ | * Discussion: could be complementary (Ere uses both for RecordManager), | ||
* [[https:// | * [[https:// | ||
* Next steps: resolve conflicts; finish review process | * Next steps: resolve conflicts; finish review process | ||
+ | * Discussion: Aleksi has been very busy, but it could be useful; Ere will follow up | ||
+ | * [[https:// | ||
+ | * Next steps: discuss whether this is needed/ | ||
+ | * [[https:// | ||
+ | * Next steps: determine what work is still required | ||
+ | * Discussion: Demian will review status and set an appropriate milestone | ||
+ | * [[https:// | ||
+ | * Next steps: discuss and determine whether this is a good approach moving forward | ||
+ | * [[https:// | ||
+ | * Next steps: determine whether this work should be completed; complete it, if so | ||
+ | * [[https:// | ||
+ | * Next steps: resolve conflicts; complete review process | ||
+ | * Discussion: André will follow up and check the status of this one | ||
+ | * [[https:// | ||
+ | * Next steps: finish review process; determine appropriateness for inclusion | ||
+ | * [[https:// | ||
+ | * Next steps: complete (long) TODO checklist | ||
+ | * Discussion: Ere pointed out that some versions of UDC are incompatible with each other (e.g. religions getting mixed up). If we add support, we should version it for clarity. | ||
+ | * [[https:// | ||
+ | * Next steps: complete implementation (large amount of work still to be done) | ||
+ | * Discussion: André' | ||
+ | * Decision: 10.0 milestone | ||
+ | * [[https:// | ||
+ | * Next steps: resolve conflicts; work through TODO list (which includes some design discussion needs) | ||
+ | * Decision: 10.0 milestone | ||
+ | * [[https:// | ||
+ | * Next step: complete review process | ||
+ | * Decision: 9.1 milestone | ||
+ | * [[https:// | ||
+ | * Next step: resolve conflicts and complete review process | ||
+ | * Decision: 9.1 milestone | ||
+ | * [[https:// | ||
+ | * Next step: complete review process (address attribution issues and installation process) | ||
+ | * Discussion: Ere proposed an alternative to accessible-slick which he found to be more accessible -- Splide. | ||
+ | * Decision: 9.1 milestone | ||
+ | * [[https:// | ||
+ | * Next step: complete review process | ||
+ | * Decision: 9.1 milestone | ||
+ | * [[https:// | ||
+ | * Next step: complete review process | ||
+ | * Decision: 9.1 milestone | ||
+ | * [[https:// | ||
+ | * Next step: complete review process | ||
+ | * Decision: 9.1 milestone | ||
+ | * [[https:// | ||
+ | * Next step: complete review process | ||
+ | * Discussion: large but backward-compatible change; Ere is flexible about 9.1 or 10.0. We'll decide on a milestone after further review | ||
+ | * [[https:// | ||
+ | * Next step: complete review process | ||
+ | * Decision: 9.1 milestone | ||
=== Next Meeting Plans === | === Next Meeting Plans === | ||
Line 40: | Line 93: | ||
==== 2. Technical Discussion: Internationalization with localise ==== | ==== 2. Technical Discussion: Internationalization with localise ==== | ||
+ | André has been exploring the lokalise.com platform, which the Open Library Foundation uses for some of its projects. It imports languages from GitHub, makes it possible for users to collaboratively improve/ | ||
+ | |||
+ | The interface displays percentage done, number of words in need of translation, | ||
+ | |||
+ | The system also has project management features built in, so you can assign work, create tasks, etc. | ||
+ | |||
+ | Some quirks may confuse the project (e.g. @parent_ini directives, use of language codes that don't exactly match lokalise' | ||
+ | |||
+ | During import, lokalise is currently set up to ignore native.ini -- this is a special file and would not benefit from management through the platform. | ||
+ | |||
+ | Text domains are imported using filename patterns, which enables us to keep domain-specific strings appropriately separated. | ||
+ | |||
+ | When translating, | ||
+ | |||
+ | André opened a German-specific example pull request as a proof of concept. This reveals some problems we need to overcome: | ||
+ | |||
+ | * Some files are renamed (e.g. en.ini --> en_GB.ini) | ||
+ | * Some formatting is changed (e.g. strings with special characters are enclosed in single quotes; double quotes are removed) | ||
+ | * All comments are removed | ||
+ | * Numeric keys are dropped (a problem for the Dewey Decimal text domains) | ||
+ | |||
+ | Possible solution: Custom processor -- the ability to create a REST endpoint for pre- or post-processing of translations. Well documented with examples provided. One question: can the custom post-processor be combined with the "post PR to GitHub" | ||
+ | |||
+ | We confirmed that our current lokalise account seems to support the custom processor. | ||
+ | |||
+ | There was some discussion about how/where to implement and host the processor: one option would be to create a repository that exposes a Laminas module containing the processing functionality, | ||
+ | |||
+ | Also discussion about where to get comments from: one option would be to have the API just pull the latest .ini files from GitHub using URL patterns (raw download). | ||
+ | |||
+ | Volunteers to work on the project: Demian will set up a vufind-org GitHub repo to build the module and will help with deployment to vufind.org. André will help with development of the code. | ||
+ | |||
+ | André will inquire about the " | ||
==== 3. Open Q&A / Other Topics? ==== | ==== 3. Open Q&A / Other Topics? ==== | ||
+ | None this month. | ||
===== Next Call ===== | ===== Next Call ===== | ||
community_call/minutes20230502.1682945757.txt.gz · Last modified: 2023/05/01 12:55 by demiankatz