Skip to content
kstapelfeldt edited this page Oct 6, 2021 · 34 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

  • Seth Shaw, Kirsta Stapelfeldt (Notes), Drew Heles, Jared Whiklo, Jordan Dukart, Kristina Spurgin, Melissa Anez, Mark Jordan, Nat Kanthan, Rosie Le Faive, Adam V., Alex O'Neill, Brandon Weigel, Kyle Huynh, Jordan Dukart

Agenda

  1. Update on Branches/Versioning changes (https://github.com/Islandora/documentation/issues/1907)
    1. New branches cut for all github.com/Islandora code (not including islandora_ci, documentation)
    2. How to update playbook and ISLE
      1. Are all of these still in use, or do some need to be deprecated?
    3. How to version things in Islandora-Devops
  2. Issue Roundup
    1. Do we need composer.lock files in our code repos? https://github.com/Islandora/documentation/issues/1908 & https://github.com/Islandora/Crayfish/pull/129
    2. Rogue issue on islandora-sandbox: https://github.com/Islandora-Devops/islandora-sandbox/issues/3
    3. FITS Media Type RDF Mappings: https://github.com/Islandora/documentation/issues/1906 (https://github.com/Islandora/islandora_defaults/pull/55)
    4. Github config: Require checks on chullo? https://github.com/Islandora/documentation/issues/1909
  3. PR Roundup
    1. Add taxonomy manager as required module for OOTB experience: https://github.com/Islandora/islandora_defaults/pull/56
  4. Historical Issue Cleanup
  5. Islandora Awesome List

(Last 10 Minutes): Roundtable

Minutes

  1. Update on Branches/Versioning changes (https://github.com/Islandora/documentation/issues/1907) Rosie, Seth, and Bethany made a strong start to operationalize the plan for Semantic versioning, but there are a few ongoing questions. You can review the spreadsheet to see the status on this work

  2. Are all of these still in use, or do some need to be deprecated?

Possibly used in some deployments, unclear if it was a replacement for Carapace. Review who has committed to it. Danny and Don. Discussion here of how we ask questions about what we should be doing.

Also Danny and Don work.

Also Danny and Don. Alex made a commit in May, but doesn't recall. Discuss about how to handle this when it is incomplete. State of the work is unclear.

Seems to be Alex and Danny - try to have a general composer that would accept an installation profile, but relies on unsupported technologies. We should move this to deprecated for now, and then a unified composer project could be started anew later on.

This is also an installation profile, but it is not being used. Should be moved to deprecated for now (same as above).

Movement towards looking at Islandora as something that can be installed in any Drupal site without this building up of dependencies. Supporting this use case is important.

  1. How to version things in Islandora-Devops/Playbook/ISLE

We don't need to bump things to 2.0 because they are not Drupal modules. Seth assumes that we want to use the same semantic versioning approach. Alex points to the fact that some release tags already exist. Rosie points out that semantic versioning's goals may not map accurately to the goals of Islandora-Devops. For microservices, semver makes sense. How do we translate the concept of an API to this context. What is the best practice for how we go about making changes, and when that happens?

Should we tag with the same version as the 'core Islandora modules' - Islandora Playbook gets a major version when core gets updated, and that's what those pin on. Chatter in the chat: Geerlingguy roles seem to bump a major version when e.g. it adds support to another major version of the thing it is an installer for. This seems to be similar to the goals we are trying to achieve.

Jordan offers the following white paper on the subject: https://conferences.computer.org/icsme/pdfs/SCAM2020-CdP3rS7mSlqVWzF3cXW7H/924800a227/924800a227.pdf

We need pull requests to bump versions in DevOps - we are not doing branch changes, but we are doing PRs to point things to the correct new branch of the code.

Add to Agenda Next Week - **continue discussion about how to version Devops/ISLE/Playbook. For now, we are not doing branch management until this is sorted. **

  1. Issue Roundup
    1. Do we need composer.lock files in our code repos? https://github.com/Islandora/documentation/issues/1908 & https://github.com/Islandora/Crayfish/pull/129
    2. Rogue issue on islandora-sandbox: https://github.com/Islandora-Devops/islandora-sandbox/issues/3
    3. FITS Media Type RDF Mappings: https://github.com/Islandora/documentation/issues/1906 (https://github.com/Islandora/islandora_defaults/pull/55)
    4. Github config: Require checks on chullo? https://github.com/Islandora/documentation/issues/1909
  2. PR Roundup
    1. Add taxonomy manager as required module for OOTB experience: https://github.com/Islandora/islandora_defaults/pull/56
  3. Historical Issue Cleanup
  4. Islandora Awesome List

(Last 10 Minutes): Roundtable

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

⚠️ ARCHIVED Islandora Tech Calls

⚠️ ARCHIVED Islandora User Calls

Clone this wiki locally