November 3, 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:

Time: 1:00pm Eastern Time US (UTC-5)
Zoom link: https://zoom.us/j/97345581392
Join us on the Slack Islandora 8 Channel https://islandora.slack.com/archives/CM5PPAV28
- Chair rota
  - Mark
  - Melissa
  - Danny 🪑
  - Rosie
  - Seth
  - Eli

Attendees

Willow's last day! (sniff), Kirsta, Alan Stanley, Mark Jordan, Alex O'Neill, Mark Jordan, Adam Vessey, Brandon Weigel, Don Richards, Drew Heles, Eli Zoller, Jared Whiklo, Jordan Dukart, Kristina Spurgin, Kyle Huynh, Melissa Anez, Nat Kanthan, Seth Shaw, Yamil, Noah Smith

Agenda

Issue Roundup

PR Roundup

Islandora Governance Proposal for Feedback
Sprint Signup Sheet - Sprint issues voting progress
Deployment Survey results - should Kirsta post to website? Any movement here?
Protecting default/main branches
- Github's docs

Topics Roster (Backlog of issues to discuss)

Who are current maintainers
Fix Chair Rota?
What are workflows around releases that ensure testing, RCs, documentation, etc.
Drupal.org - when and how?
From Adam - Automatically create box? https://stackoverflow.com/questions/66261101/using-vagrant-on-github-actions-ideally-incl-virtualbox/66261102#66261102
Review DevOps Repo descriptions/dependencies Rosie made this sheet to sort out DevOps
Islandora Labs needs cleaning
Purpose and future of Islandora_Defaults - what is its role in the Islandora 2.0 ecosystem (managing updates)
Deployment Survey results - should Kirsta post to website? Any movement here?

Minutes

Issue Roundup

https://github.com/Islandora/documentation/issues/1977 - will deal with during PRs
https://github.com/Islandora-Labs/islandora_vagrant/issues/167 - Against Fedora 3. MJ will respond. Admin client hasn't worked in a year.

PR Roundup

3 & 206 can go together. Ready for testing but another profile is coming.

Jordan: If our goal is to define a base profile, what is the intent? Alex: This is like the Drupal restaurant demo - pre-configured behaviours to copy. We don't want to say that you have to take all of this as official Islandora, but it's demo. Nat will test. Alex says that we could suggest Islandora Lite as one of these as well.

https://github.com/Islandora/islandora_defaults/pull/58

Seth: Anything on Islandora/Islandora needs update hooks. If it's on defaults, it doesn't, because we presume you use defaults and then keep moving. Only new installations will get this and anybody else will need to do their own if they want.

Jordan: Suggest we document this in case people think they will get this automatically. 2.0 would be the next release.

Mark: Do people have an understanding of how defaults work? In case they don't, this is a good suggestion.

Seth: General note on Readme that says "we don't do updates for fields"? Jordan: Yes, and then if we do a 2.0 it will show up as a note for the release. Jordan will put in a little PR for that.

Adam: Does semantic versioning really belong there then?

Seth: How does Solr search API defaults (they have a default config that you then own and don't do default hooks.)

Alex: If you install Islandora defaults does it do the same thing? Are there hooks in there that we should be aware of and move into Islandora?

Seth: We were trying to move in that direction but there was never a full audit on that.

Nat: Are we expected to keep Islandora Defaults up to date, or is it ours to maintain?

Seth: Danny has been saying this for a long time.

Nat: The challenge with this approach. If we add new display stuff, how does the user get that feature? There have been some recent changes recently to taxonomy, for example.

Alex: Aquia lightning tried this for a while - their approach was to have a secondary update task where you would do DB updates and then run update:lightning and then it would go through and ask the user "would you like to update this display" etc. but they have abandoned because of diminishing returns. Hard and too easy to damage existing data.

Seth: Tried something similar using features, but it didn't scale. Became a mess really quickly so we walked back.

Kristina: Remembers this discussion with metadata and recalls that we need clear documentation that a metadata person can understand and pull in if you want or need htem.

Noah: Islandora 7 had the required objects page - would a dashboard like this work for this?

Kristina: that sounds like more than what we need. Sounds like what Acquia found untenable.

Adam suggests: https://www.drupal.org/project/config_update

Moved to Issues backlog for further discussion. May deserve further meeting.

https://github.com/Islandora-Devops/isle-dc/pull/193 Question from Mark: Should we include? Seth: Doesn't hurt. Minor savings. Noah: Could be changed in "secrets" Don: Simple change and he can make it.

Islandora Governance Proposal for Feedback

Kirsta will make change re: committers to preserve committers as currently defined and widen the definition to include any tech call contributor as possible TAG members. This will come back to this group next week for any additional feedback.