September 1, 2021

Time/Place

This meeting is held virtually via Zoom, with an open channel for chatter on Slack. Anyone is welcome to join. Here is the info:

Issue Roundup
1. No new issues
PR Roundup
1. No new PRs
Leadership Group Update
Feature Parity Document - Let's do a few more rows together!
Renaming branches - https://docs.google.com/spreadsheets/d/1rC9EVXIxZQIUxGgquCytlDFUoZgCnow0uuxfBiRGC5s/edit#gid=0
Rosie's wiki project - https://docs.lefaive.ca/w/index.php/Rosie_Le_Faive%27s_Islandora_Wiki
Performance issues with islandora utils getTermWithUri
... Please feel free to add more...

(Last 10 Minutes): Roundtable

Eli ran into some issues performance issues related to Islandora modules related to database queries. He has some solutions, that he maybe able to generalize.

Updates from Islandora Leadership Group: https://groups.google.com/g/islandora/c/vYzTfZY85vQ
Islandora sprint can potentially be organized for feature parity with playbook and ISLE, feature parity with Islandora 7.x and 2.0, and to provide demo content. Currently, several organizations have committed resources for sprint. However, the exact scope is yet to be determined.
A representative from Leadership Group may need to be available for the Tech Calls to liaison between the teams.
For now, Mark will request guidance from the Leadership Group related to sprint (leadership/co-ordination to organize the tasks/followup/sprint leader, scheduling), resources, as well as scope. The Tech Call contributors would like to provide input with respect to scope for the Sprint with the aiming of stabilizing the base box experience.
Mark will edit the points shared in this meeting notes and convey them to the Leadership Group end of today! Specifically, addressing the following points:

clear direction on the sprint.
Committers want to provide suggestions about what the outcomes of the sprint are (?)
Details about resource commitments for the sprint
Clarity on who is going to set timelines and deliverables for sprint. Who is the sprint leader?

We need to clean up the branches to better support installation via composer.
Branches have several issues: inconsistent naming, stale branches
We should encourage people to fork and create PR from their own forks.
It would be helpful if people can mark the ones that can be deleted [https://docs.google.com/spreadsheets/d/1rC9EVXIxZQIUxGgquCytlDFUoZgCnow0uuxfBiRGC5s/edit#gid=0](from this list)
Drupal modules should be semantically versioned.
Ansible role repos can be tagged semantically as well.
Rosie - Is it best to cut releases for each repo? People have suggested that this may not be needed. We need to better understand what release entails.
Seth suggested that we may not need to do synchronized releases for all the modules unless there are breaking changes (i.e api changes).

This wiki aims to document what are the kids of things people doing digital asset management need, mainly focusing on Islandora.
It is an open wiki. Feedback and contributions are welcomed.

Eli is experiencing issues with islandora utils getTermWithUri, when there is a large number of taxonomies. One possible solution is to avoid using the getTermWithUri and rather use the taxonomy id.
Seth suggested that he has not seen performance issue, perhaps because they are using Memcache. Seth installation has ~400,000 nodes with 10,000s of taxonomy terms. (Update: we have 537,728 nodes and 20,934 taxonomy terms in production as of this afternoon.)
Jordan Dukart suggested the Drupal caching methods can potentially be used to addressed this. He has ingested ~250,000 objects without notable performance issues.

Having too many un addressed issues https://github.com/Islandora/documentation/issues leaves a bad impression on people evaluating the project. There are many stale issues that needs to be closed. Some issues are use cases.
Old issues review to become a standing meeting item (oldest issues).

This is an archive. For new Tech Call notes, click here