Skip to content

September 28, 2016

Jump to bottom Edit New page
Jared Whiklo edited this page Sep 28, 2016 · 7 revisions

Time/Place

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

Attendees

  • Nick Ruest
  • Melissa Anez
  • Jared Whiklo 🚬
  • Danny Lamb
  • Ed Fugikawa
  • Mark Cooper
  • Marcus Barnes
  • Kim Pham
  • Natkeeran Ledchumykanthan
  • Audrey Templeton
  • Bryan Brown

Agenda

  1. Fedora Import/Export
  1. Determine where json-ld repository should go?
  • Move to Islandora-CLAW as a stand alone repo?
  • Move to Islandora-CLAW/islandora as a sub-module?
  • Something else?
  1. Documentation
  1. PCDM Community Call; October 6th
  2. ... (feel free to add agenda items)

Minutes

  1. Fedora Import/Export

    Nick: Penn State Concentrate report that went out.

    Phase 1 is complete, import and export is working... except a small bug with importing pair-tree nodes. Esme Cowles will be working on that soon.

    Phase 2 planning started at Penn State. Sketched what the BagIt bags would look like for Meta-archive and AP Trust.

    Adam Wead wrote a background job to start an export job from inside Creation Concerns (Hydra). This is something we could do later in Drupal, calling an asynchronous service (ie. Camel) and call the Export job.

    Sprint for Phase 2 (December 5 - 16th)

  2. JSON-LD

    Had a previous discussion (Sept. 7, 2016) but no decision. Talk it out, because Diego is away

    Diego has created a standalone JSON-LD module and an Islandora module.

    One thing Nick would like is to not have a tonne of separate modules in Drupal.org.

    So should we make the JSON-LD a sub-module of the Islandora module or should it be a stand alone module?

    Nick thinks it should be a sub-module for now. Bryan agrees.

    Nat thinks json-ld is generic and useful to other projects. Jared agrees.

    Actionable things are...it is not fully Islandora specific but also not fully generic.

    Jared: If it starts out as a sub-module then it will more than likely stay as a sub-module. Perhaps we could have someone go through the module and look for better ways to generalize its use.

    Nick: Project Director tuque applied, move it over. Fearful that someone looking at this module is a waste of time.

    Danny: Tech lead hat, we have better uses of what very limited resources we have. If I need someone to do a little, then I need to do a lot beforehand. I would bring it over on its own, as its own module which forces us to think about it correctly as a separate module.

    Drupal.org Sandbox : https://www.drupal.org/sandbox/islandora/1791628

    Consensus to move the JSON-LD module to the Islandora-CLAW repo as a separate module and cross the Drupal.org bridge when we get there.

  3. Documentation

    Nick has some thoughts about this and Robin Dean chimed in on the ticket. Kim has done a lot of work.

    Do we need to have a full set of documentation for each release?

    Danny: We need one for each release, if it is every 6 months or so. If its many small releases, then no. IMHO, it seems wasteful at a certain point to keep replicating the documentation.

    Nick: If we're doing developer docs, those are released for each version. But user documentation, could be a single copy.

    The reason it is in the repositories now is to force us to keep it up-to date.

    Melissa: The 1.x documentation gets used by release version. So we might get some push-back from the community.

    Danny: It seems easier for us and easier for users to cut a full version.

    Readthedocs.org seems good, but might be a hosted service and we might need a separate repo. Need a Readthedocs account and it builds a site from there, and it is hosted on Readthedocs. It is free. You can tag different versions of your documentation.

    Nick: "Read the Docs is funded by readers like you. Help keep the site alive and well by supporting us with a Gold Subscription. You can also make one-time donations on our sustainability page."

    https://readthedocs.org/projects/islandora/

    Melissa: if we end up using it, we could probably arrange a one-time donation as a show of thanks

    Set-up a new repo to reduce the number of existing versions having documentation created.

    Should we go through the documentation and remove all the 7.x-2.x references? Consensus: yes.

    Should we keep up future.islandora.ca?

    Danny/Nick: Ideally we should bring it down, but optically how are we looking?

    Melissa: We haven't really promoted it, so it shouldn't be to big of a loss.

    Any objections? Consensus: burn it with fire

    Nick to create a ticket for somebody to go through the current CLAW documentation and remove anything 7.x-2.x related.

    Danny: Pretty soon, once we have a versioned documentation process decided on. We should go through the release process and sort out the documentation process ahead of a full release.

    Nick: We have very early (0.0.x) versions of some of the microservices and Alpaca is in Maven Central.

  4. Second PCDM call will be happening on October 6

  5. Anything else

    Danny: I've add some things to the MVP document recently, I'm having some second thoughts about some parts of the document. Would be good to get some review on it. Then he will get it ready for the general public.

    Use this as a jump off point toward much more focused sprints.

    Appreciate all the review and comments.

    Come along way but still a ways to go with Drupal 8, but there are still gaps in the workflow that need to be filled.

    Doodle poll for sprint debrief call. http://doodle.com/poll/pdxskugrevz8x8qn

You may be looking for the islandora-community wiki · new to islandora? · community calendar · interest groups · roadmap

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

⚠️ ARCHIVED Islandora Tech Calls

⚠️ ARCHIVED Islandora User Calls

Clone this wiki locally