Skip to content
kstapelfeldt edited this page Dec 1, 2021 · 12 revisions

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:

Attendees

  • Alan Stanley, Don Richards, Rosie (Chair), Seth Shaw, Adam, Alexander O'Neill, Danny Lamb, Don Richards, Gavin Morris, Jared Whiklo, Jordan Dukart, Kristina Spurgin, Melissa Anez, Rosie, Sarah Goldstein, Yamil, Sujay Aryal

Agenda

  1. Issue Roundup
  2. PR Roundup
  3. Access Control Module - questions for Danny for how to package.
  4. Don Richards: Adding Statuses for things that are 'waiting for review' in Github. 1 For information: Sprint Planning Document
  5. have decided to move the issues after December 15th to minimize confusion.
  6. Can we cancel December 22nd's Open Tech Call?
  7. What is the chair roster next year? Can TAG decide this in their next meeting?
  8. Anything from Topics Backlog?

Topics Backlog

(Last 10 Minutes): Roundtable

Minutes

  • Access Control Module - questions for Danny for how to package. He says absolutely can be pulled into module. Will post snippets in
  • Don Richards: Adding Statuses for things that are 'waiting for review' in Github project for sprint - done
  • Issues will move to individual repositories after the sprint. Issues that you don't know where they go will still go into documentation.
  • We will cancel the December 22nd meeting.
  • Profile Update - from Nat - we have had conversation about install profile. We are seeking a method to facilitate testing and provide an out of the box experience. Have identified challenges: Install profile (difficult to pull upstream changes if configs have been overridden by profile). We want the default experience to reflect the latest core and supplementary modules. The install profile is a snapshot of sorts, and a little more involved when it comes to updating (if update hooks are not in modules). We want to push install profile changes to islandora core, defaults, or separate modules and there are some decisions that have to be made. For example: in the install profile, the resource type is driving behaviour but it is not required. Perhaps it can be merged with Islandora Model. Hopefully this will give us a default experience will reasonable setup that will allow us to pull the latest. We have also developed sample digital objects. Decided to merge islandora_default pull request I think?
  • Issue cleanup: https://github.com/Islandora/documentation/issues/1738 Don has a pull request for this. How do we identify Islandora sites? Can't use this PR as it will wipe out front pages. Feedback for Don that he will address. Alex says: A "welcome message" block separate form powered by Islandora might make sense "/islandora" might be a good idea. Maybe a version number, suggests Danny. Alex suggests something in footer or a separate page. Gavin: I recommend we don't use /islandora because it's reserved by a number of people. Danny suggests that "powered by islandora block may be the most innocuous"
  • Silex: https://github.com/Islandora/Crayfish/pull/133 and https://github.com/Islandora/Crayfish-Commons/pull/49 not backwards compatible. How to provide upgrade path for people? Unclear. Should be fine for Ansible and ISLE/DC. Documentation will be added to Crayfish PR to where the different configuration variables will be located moving from Silex to Symphony.

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

⚠️ ARCHIVED Islandora Tech Calls

⚠️ ARCHIVED Islandora User Calls

Clone this wiki locally