About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20220405

VuFind® Community Call Minutes: April 5, 2022

Attending: Oliver Goldschmidt, Chris Hallberg, Demian Katz, Claas Kazzer, André Lahmann, Ere Maijala, Aleksi Peebles, Mario Trojan

Agenda

1. Development Planning

Newsletter Highlights

The March, 2022 Newsletter was discussed.

Future of JIRA

Demian is working with Peter Murray from the OLF on this process.

Possible Laminas Deprecations

We will discuss Laminas migration during future sprint planning.

Citation Style Language

No news this month.

IxTheo Feature Sharing

We plan to talk about authority data features in more detail on next month's call; that would be a good time to cover this topic as well.

2. Theme Community Sprint Planning

Chris proposed breaking down templates into smaller parts for clarity, reusability and easier customization.

The goal is to refactor current themes as a first step, then use the resulting granular parts to build the next-generation, improved theme.

He opened pull request #2378 as an example of how this could work. Everyone is encouraged to review/comment on this.

Next step: Identify areas where components need to be developed/built.

There was discussion of the ongoing conversation on pull request #1962, including the problem of underlined spaces in links containing icons. Should we reduce the amount of underlining?

Aleksi shared his thoughts/experience from working on component templates for the Finna project. He has a pull request on the Finna side containing the latest iteration of icon/button/link templates, which may be useful for reference.

There was discussion of naming/organization of components (in particular, where Javascript/CSS related to components is placed). Ere suggested that a view helper might be a good fit here, since we may change some decisions, but the helper would abstract that away and make it easier to change underlying mechanisms without touching all the templates. Aleksi expressed some possible concerns with this approach.

Tooling conversation: Aleksi suggested using modern CSS instead of LESS/SASS, and using PostCSS to convert it to legacy CSS for backward compatibility. Possibly a more future-proof option. (Chris likes this suggestion; PostCSS is a strong contender, since it gets “thinner” over time – as browsers support more features natively, it does less work).

Also discussion about where to continue these types of conversations. Demian encouraged creating JIRA tickets for concrete actions that require further conversation. He discouraged using Slack for decision making because it does not keep a permanent record (it's fine to have conversations there, but copy and paste them to somewhere more permanent if valuable outcomes are reached).

Mario suggested starting to identify the smallest atoms such as hyperlinks, forms, form components etc. and see how many we get.

Ere noted that this all is quite overwhelming. We need to make sure we don't paint ourselves in a corner so that we're able to do the work in iterations.

3. Other Topics?

None this month.

Next Call

The next call will be Tuesday, May 3, 2022 at 9am Eastern Daylight Time (13:00 GMT).

community_call/minutes20220405.txt · Last modified: 2022/04/05 14:49 by demiankatz