Skip to content

October 25

Jump to bottom Edit New page
aaronchoate edited this page Oct 25, 2019 · 14 revisions
  • Chair: Don Richards
  • Notes: Aaron Choate

Per: Schedule

Attendees:

  • Aaron Choate
  • Don Richards
  • Jeffrey Rubin
  • Janice Banser
  • Gabriela
  • Brandon Weigel
  • Rosie Le Faive
  • Jonathan Green
  • Melissa Anez
  • Martha Tenney
  • Daniel
  • Weixuan

Agenda

Old Business

New Business

Interest Group Updates

  • Metadata IG (Rosie)
  • IR interest group (Bryan)
  • ISLE Interest Group (Martha or Gavin)
  • Multi-tenancy Interest Group (Brandon)

Islandora 8

Islandora Camps

  • Islandoracon takeaways

Round Table

Next meeting November 8

  • Chair: Donald Moses
  • Notes: Danny Lamb

Minutes

New Security Workflow from the TAG (Danny)

  • Revised workflow for critical vulnerabilities (taken over from security interest group which is on hiatus)
  • added the fact that it should be advertised when updates get made
  • why patches only on Wednesdays? (and not Monday and Tuesday) - no change - makes it so people know when to expect it
  • suggestion for creating a specific list where people who are wanting to be alerted first - added to workflow
  • PR version on the Islandora page so it is easy to see that we "have" a security update policy
  • vote to approve in chat - 9 yes - 3 abstain

Islandora 8 Committers Workflow (also from the TAG) (Danny)

  • Release workflow - while releasing - we're free to pull from the release branch in dev so no need to do multiple pull requests
  • Query about the use of tags? - we do use tags to tag master and only resort to branches if you have to backport a fix
  • useful to mention when a pull request goes stale? - it is mentioned re: languishing in the text - also it has been modified to allow closing pulls for users that have ghosted -- should we have a way to allow a submitter to adopt a ghosted pull request - that gets handled by the new submitter to create a replacement pull request that supersedes the original orphaned request
  • should there be a way to officially dismiss pull requests that are not in line with the will of the community? - partially addressed in the social dynamics sections, but admittedly it is a challenge to deal with - in favor of keeping it light - trying to address with policy tends to back people into corners. (agreed) - add the code of conduct as a link
  • once approved - we need to also make sure this shows up
  • vote to approve in chat - 10 yes - 1 abstain

Officially retiring irc in favor of Slack (Melissa)

  • Seems like Slack has pulled in the majority of the community and IRC has waned. It has broadened the community significantly: (adding an auto-invite)
  • Propose that we vote to deprecate IRC where possible
  • vote to approve in chat - 9 yes - 2 abstain

LSAP: Islandora Cookbook (Melissa)

  • Has been working on it in personal Github and would like to move it to Labs ( will never get into release so makes sense for it to live in labs)
  • Where do we draw the line? - if something becomes core inslandora we will "graduate" it to release - okay to let it be "fuzzy" with the understanding that we can move things back and forth when it makes sense.
  • the goal is to make it more discoverable
  • vote to approve in chat - 9 yes - 0 abstain

Fedora OCFL decision coming up. (Melissa and Danny)

  • Fedora leadership feels that OCFL needs to be core to Fedora -
  • But... OCFL is intended to be immutable - that is in opposition to some Fedora installs where things are versioned does it work "on" an OCFL file system or does it "create" one?
  • what does that do re: bloat? several options have been explored
  • currently liaising with OCFL to explore versioning/mutable head options
  • would it be better to build a versioning side process?
  • not a final decision point at this moment - but important to be aware and prepped to provide input

Metadata IG (Rosie)

IR interest group (Bryan)

  • Call yesterday - pushed to next month

ISLE Interest Group (Martha or Gavin)

Multi-tenancy Interest Group (Brandon)

  • A lot of progress has been made at IslandoraCon
  • looking for a meeting to talk about the progress that shows in the github issue

Islandora 8

Islandoracon takeaways

  • Sent out survey midweek this week (and advertise the Arizona Cmap) - wants to hold till next meeting

  • early feedback:

  • everybody really loved the food...

  • most people would like it to next go to East US/Canada

  • liked the format - with slight mods to some of the timing and insert some breaks/transfer time

  • code of conduct progress is on the survey - initial takeaway is to it needs to be emphasized before the workshops

  • accessibilty - push in chairs

  • "agressive aiding" - how to provide guidance from an authoritative source?

  • appreciation for the quiet room

  • appreciation of the pronoun and flair stickers

  • how to emphasize inclusion and accessibility in location selection

  • USEathon extremely successful

  • need to be more careful on the dates

##Round Table

Rosie - Still working on RDM work and looking for directions to uploading large files (Tusk?)

Don - two open positions https://www.lib.utk.edu/employment/position/it-analyst-ii-software-developer/ trying to work through on testing migrations

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

⚠️ This wiki is an archive for past meeting notes. For current minutes as well as onboarding materials, click here.

Clone this wiki locally