Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20221206
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
community_call:minutes20221206 [2022/11/16 18:30] – created demiankatz | community_call:minutes20221206 [2022/12/06 14:34] (current) – [Next Call] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VuFind® Community Call Minutes: December 6, 2022 ====== | ====== VuFind® Community Call Minutes: December 6, 2022 ====== | ||
- | Attending: | + | Attending: |
===== Agenda ===== | ===== Agenda ===== | ||
Line 13: | Line 13: | ||
=== Pull Request Review (9.0 milestone) === | === Pull Request Review (9.0 milestone) === | ||
- | * ... | + | * [[https:// |
+ | * Next step: final test/review - DK | ||
+ | * [[https:// | ||
+ | * Next step: resolve conflicts; finish testing and fixing outstanding issues - CH / DK | ||
+ | * [[https:// | ||
+ | * Next step: final test/review - DK | ||
+ | * [[https:// | ||
+ | * Next step: decide when to add buttons and when to use MenuButton controls from [[https:// | ||
+ | * [[https:// | ||
+ | * Next steps: finish discussion, ensure full test coverage - CH / DK | ||
+ | * [[https:// | ||
+ | * Next step: decide whether Solr 9 belongs in release 9.0 or 10.0 of VuFind® -- no strong opinions on call; DK will talk EM | ||
+ | * [[https:// | ||
+ | * Next step: Discuss / finish TODO list - CH | ||
+ | * [[https:// | ||
+ | * Next step: continue test/review process - CH / DK | ||
=== JIRA Ticket Review (9.0 release, without an existing pull request above) === | === JIRA Ticket Review (9.0 release, without an existing pull request above) === | ||
- | |||
- | == In Progress == | ||
- | * ... | ||
== Not Started - No Blockers == | == Not Started - No Blockers == | ||
- | * ... | + | * [[https:// |
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
== Not Started - With Prerequisites == | == Not Started - With Prerequisites == | ||
Line 31: | Line 49: | ||
* Prerequisite: | * Prerequisite: | ||
- | ==== 2. Technology Demo ==== | + | ==== 2. Technology Demo: Theme Configuration Helper |
+ | Chris highlighted the [[https:// | ||
+ | |||
+ | Chris demonstrated some possible applications of this feature -- for example, adjusting the order of elements in the theme' | ||
+ | |||
+ | The proposal was well-received. | ||
==== 3. Community Call Survey Outcomes ==== | ==== 3. Community Call Survey Outcomes ==== | ||
+ | The Community Call survey received 17 complete responses. No one expressed a desire to change the current time or schedule. | ||
+ | |||
+ | The majority of participants (16) said that development updates are useful. A significant number (11) also highlighted the value of being able to ask questions of the community, and 9 highlighted tutorial videos. Only 3 noted community planning exercises as a positive feature. | ||
+ | |||
+ | Other suggestions included: | ||
+ | |||
+ | * More frequent JIRA/PR status check-ins (which we're already planning to do!) | ||
+ | * Including lightning talks on related topics (PHP news, Laminas news, etc.) if people are willing to share | ||
+ | * More discussion of authority data | ||
+ | * More time for beginners to ask questions | ||
==== 4. Other Topics? ==== | ==== 4. Other Topics? ==== | ||
+ | Chris is interested in offering more user-initiated theme options (e.g. light/dark theme, including detection of device light/dark mode). How should we manage all this complexity without creating very messy code? CSS variables can help with this... but what if we also have LESS/SCSS variables? How do we reconcile all this? e.g. if we need light versions of all variables and dark versions of all variables, that's already doubled the number of variables... and then how do we make sure these are all accounted for properly? If you have any ideas/best practices, please share them with him. | ||
+ | |||
+ | One possible proposal: use CSS variables for " | ||
+ | |||
+ | Possible next step: Chris can create a PR to better formalize the problem for deeper discussion. | ||
+ | |||
+ | It was proposed that we should postpone the next Community Call due to the regularly scheduled date falling very close to a holiday. There were no objections, so we will next meet on January 10 instead of January 3. | ||
===== Next Call ===== | ===== Next Call ===== | ||
- | The next call will be Tuesday, January | + | The next call will be Tuesday, January |
+ | |||
+ | :!: Note that this was rescheduled based on discussion above. | ||
---- struct data ---- | ---- struct data ---- |
community_call/minutes20221206.1668623431.txt.gz · Last modified: 2022/11/16 18:30 by demiankatz