January 17, 2018

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join. Here is the info:

• Time: 1:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (641) 715-3570
  • Participant Code: 304589#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  • Join the #islandora chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #islandora on irc.freenode.net

Attendees

• Seth Shaw
• Bryan Brown
• Yamil Suarez
• Jonathan Green
• Jared Whiklo
• Marcus Barnes
• Natkeeran
• Rosie LeFaive 🌟

Agenda

1. Github permissions: In order to assign labels or move issues around in a project, you must have write permissions!
2. Need another tester: https://github.com/Islandora-CLAW/islandora/pull/71
3. https://github.com/Islandora-CLAW/islandora/pull/70 closed in favor of https://github.com/Islandora-CLAW/islandora/pull/72
4. https://github.com/Islandora-Devops/claw-playbook/pull/43 has been merged. Existing claw-playbook PRs targeting these roles need to be made against their new repos.
5. ... (feel free to add agenda items)

Minutes

1. Seems that to do basic stuff, you need pretty high permissions! Unless you're a committer, you can't assign labels or move issues. This isn't ideal. However, the CLAW repo is no longer used for code anymore (except Chullo). Decision: We're going to switch the default permission to 'write' for people within the Islandora Claw organization. So: just because you now can merge code, you're not allowed to by our policy unless you're a big-C Committer.
2. Don't be scared of this PR, we need another tester on pull/71!
3. If we get pull/72 (follow-up to 71), we'll pretty much have a full-on REST API.
4. Now that this has merged, roles are external and are pulled from Galaxy. If you have a claw-playbook PR, and it hits "roles", you'll have to close it and make a new one. However there are still overlapping variable definitions that need to be separated . In fcrepo syn we use the tomcat variable, but there's not one for that, so we should define one and synchronize it in the playbook to whatever it should be set to...

Non-Agenda-based discussion:

Discussion of setting up a multi-server setup that Nat is working on. We want to have standard roles (with enough flexibility that you can use your own), e.g. for installing tomcat. So we don't want to make "our" roles mandatory.

Sprint soon! Danny will put feelers out for what needs to be done. Suggestions:

• documentation.
• Content models.
• metadata transforms

Fedora community is talking about how Blazegraph is being sold to Amazon (rumour?) and how the OS version of Blazegraph is stagnating (according to Cavendish which is an implementation of the Fedora4 API on BG). Should we consider Fuseki despite current performance being poorer? Whikloj sees no reason to change for now, but be aware (and maybe consider building an Ansible Role that instals Fuseki?)