TAG October 25

https://zoom.us/j/968367412

Attending

• Danny Lamb
• Jared Whiklo
• Jonathan Green
• Bethany Seeger (notes)

Agenda

Old Business

https://github.com/Islandora/islandora/wiki/TAG-September-27

• More frequent release schedule

New Business

• Fedora decision over OCFL: https://docs.google.com/document/d/1RE8M7882JSSCvL5H9QKo5eWGrHWFtZ1uHkkHenTX5mU
• Policy on updates between versions?
  • Fedora 5 now uses a relational db for backend instead of a file db.
  • Installer now targets Ubuntu 18.04.
• Dockerizing Islandora 8
  • Policy for maintaining an environment?

Notes

• Fedora FYI - Decision of using OCFL with a mutable head, which is not quite in the specification (yet).
• Policy on updates between versions:
  • How do we define this as it's complicated. For example going from Fedora 5 to 6, where the data model changes and something has to be done to the data. But Islandora 8 itself hasn't changed, so how do we make sure that this issue is addressed.
  • There are things the users are going to have to do that are outside of Islandora 8's concern.
  • Ubuntu 16.04 - 18.04 - ISLE (Dockerization) might be able to help with this part.
  • configuration changes might fall in this category, too.
  • This might all be best solved in documentation that describes upgrades in detail.
  • Should try an upgrade from 1 - 1.1 to see what it looks like. Perhaps add this as a test case for each new release: having someone walk through an upgrade from the previous release and document what's involved for each component.
  • Should the playbook be versioned differently from Islandora?
  • What is a version in Islandora 8 when it pulls in so many other components? Want to avoid versioning everything every time a release happens, esp. if they didn't change. Version things separately and create a compatibility matrix?
  • Having something like ISLE will help, where things are separated and in containers and versions specified.
  • Some folks don't want scripts like Ansible provisioning a machine for them for security reasons/concerns.
  • Need to be clear about expectations here, both in what we're going to do and what users can expect.
  • What is the expectation of support for Islandora 8 in this context? What are the requirements for upgrades/support? As it can be complicated to support these systems where it brings many separate and non Islandora related tools together.
• Preservation - and paths for preservation. Can offer up tools and options for preservation.
  • bagIt is mostly used for data transitions.
  • Create recommendations about tools you can use to do this stuff and what they do. Detail the best practices - and create them, as a community, as we go forward. Best practices will emerge as the software gets used more and more.