April 6, 2016

Time/Place

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

• Time: 1:00pm 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

• Ben Rosner
• Ed Fugikawa
• Melissa Anez
• Nick Ruest
• Diego Pino
• Jared Whiklo ⭐

Agenda

1. "Squash your commits"

• Shall we create a squash policy?

2. CollectionService should allow you to get a collection
3. PHP7, HHVM, high performance PHP.
4. Sprint debrief
5. April sprint planning
6. What's in a name? CLAW vs. 7.x-2.x for documentation
7. ... (feel free to add agenda items)

Minutes

irclogs

1. Squash your commits

   New feature allows you to squash your commits. Do we want to make a policy of doing this?

   Consensus it to leave it up to the committer and PR author to discuss and decide when it is appropriate.

2. What do we want when we GET a collection?

   A collection service should tell you everything that is a child of that collection. That would be the pcdm:hasMember links.

   Current RDF does a shallow traversal of children. ldp:contains is restricted to the first 100 children.

   When we issue a GET request we will get the Fedora path instead of the UUID, so we would need to convert them back.

   Do a single SPARQL query for the collection path all the pcdm:hasMember UUIDs at once.

   Consider a mapping service to turn Fedora 4 RDF into Islandora CLAW RDF.

   Open an issue for the mapping service. Overwrite $app->idToUri() function for the CollectionService to instead of returning the single path from a UUID. It would return a list of UUIDS for the collection and all pcdm:hasMember children

   Tickets:

   • https://github.com/Islandora-CLAW/CLAW/issues/168
   • https://github.com/Islandora-CLAW/CLAW/issues/169

3. PHP 7 & HHVM

   Diego has been testing, trying to improve Islandora 7.x-1.x performance. Experimenting with the PHP 7 and suggests that for the Silex framework at least be written with PHP 7.

   Drupal 7 has not been fully tested, but moving forward Drupal 8 will support PHP 7.

   Will people have to run 2 versions of PHP? Do we keep compatibility with PHP 5? Keep the Travis tests for PHP 5. Do we support Drupal 7 with PHP 7, or do we program with a plan for Drupal 8 now.

   Roadmap is waiting on our prospectus, so we need to continue with Drupal 7 for now.

   Drupal 7 and Drupal 8 are very different when it comes to the use of entities to build a node. We will have to build content-models for both versions. Which is a lot of work twice.

   Dropping Drupal 7 is probably not going to happen any time soon so we will be building for both Drupal 7 & 8 anyways. Could work as a good learning experience/sprint task to convert a content-type from Drupal 7 -> 8 or vice versa.

   Tickets:

   • https://github.com/Islandora-CLAW/CLAW/issues/180
   • https://github.com/Islandora-CLAW/CLAW/issues/181

4. Islandora 7.x-2.x vs CLAW

   Making sure that CLAW is just a working name and not integrated in the project. This will be the Islandora project eventually. Drupal does not allow for semantic versioning (in Drupal 7, it does in Drupal 8).

   Our first version will be 7.x-2.0 or 8.x-0.1 depending on the Drupal version we move towards.

   Aside: We have everything in one repository and soon we will need to yank stuff out. Collection gateway needs to go on Sonatype and when we need to cut releases. We were going to set each part up as separate repositories and reference them as sub-modules for the core CLAW repository. It can work as an incremental change as PRs are placed against the individual repositories and then it can be included into the main repository.

   What do others think about Islandora and CLAW?

   Ed doesn't really have a preference.

   Ben thinks that CLAW is a development name and will eventually become Islandora.

   In Fedora 4 individual modules that are not part of core have their own version numbers and there is a compatibility matrix to show what software works with what.

   What happens if 7.x-1.x releases for Drupal 8, what would their version be?

   We can think of it like Apple's naming structure for OS X updates, with a version number and a code-name.

   A deeper question is what is Islandora in the CLAW project? Is it the core Drupal module?

   We keep using the code name "CLAW" but always refer to this version in documentation and publication as Islandora CLAW and make sure not to tie CLAW into the code (ie. not in ontologies, module names, etc.)

   Tickets:

   • https://github.com/Islandora-CLAW/CLAW/issues/182

5. Sprint debrief

   Tabled to next meeting.

6. Next sprint planning - tentatively April 18 - 29th

   Tabled to next meeting.