ICC: October 21, 2022

• Notes per Schedule
• Topics List
• Islandora Coordinating Committee Google Drive Folder
• Islandora Code of Conduct

Attending:

• Amy Blau (chair)
• Rosie Le Faive (notes)
• Alistair Morrison
• Sarah Goldstein
• Brandon Weigel
• Bridget Whittle
• Kirsta Stapelfeldt

Agenda

• Islandora Events - Kirsta
  • Camp in March and Con in August as a benefit for membership, revenue stream (Kirsta and Isabella are organizing)
  • Proposed long-term event calendar
• Interest Group Updates
• Update from TAG meeting: discussion of TAG terms of reference; Carapace deprecation; how to list (or not) code maintainers; committers review yearly
• Update from LG meeting: committers as a group, work with Drupal; new Islandora Intern recruitment in November
• Code of Conduct Committee training update
• Open Meeting planning for Nov 29

Interest Group Updates

• Metadata IG (Rosie)
• IR interest group (Don)
• Documentation Interest Group (Yamil or Mirko)

Islandora Events

Action Items

• Notes for next meeting:

Notes

Events and scheduling (with Kirsta)

• What work (organization, planning, recruiting) is in the ICC's purview, what's not?
  • we're still redefining everything. ideally the calendar would set the events out, but would not necessarily do all the organizing. The intern could help. There could be a "conference committee" (made of some ICC and some external members) that would do the organizing, that would report at ICC meetings and get feedback from them
  • The community is different but the world is different too! What are expectations around events now we've learned from the pandemic? Events used to be very frequent (a couple a year) and were a good onboarding tool - new users could go to camps.
  • Proposal: 2-day virtual only camp in March, and an in-person con in August at UTSC.
  • Who would organize the camp?
  • Vision: a camp is short and focuses on instruction (mostly a plug-and-play intro for users, intro for programmers) and community events.
  • What's the accountability? the conference committed would do what we can.
  • would it be useful to talk about how the Chair of the conference committee has more responsibility/accountability for making everything happen?
  • there is usually a need for a team "on the ground" (i.e. at the host institution) to set up logistics. We could provide
  • the poll is currently leaning towards late july, go vote
  • the decision (to have a con or not have a con) is... do we get consulted on that decision making process? we are getting mixed signals. Response: the ICC is really slow and we don't have the workflows to make these proposals/decisions yet. because we haven't developed, we've proposed a specific event to cover the short term. ultimately the ICC would have the responsibility...
  • has there been a decision made? Response: everything's changeable.
  • last time we discussed this, there was an idea (proposal/consensus?) that we could have a joint camp/con.
  • Kirsta had to leave early for a meeting.
  • ICC will create a response document regarding the proposal regarding 2023's camp/con, for us to hash out clarity regarding roles
• Amy worked with Isabella to lay out "when things can happen" in islandora (including Canadian, US, and religious holidays)

Group updates:

• DIG: Mirko is onboarding a colleague! Congrats!

• MIG (Rosie): is meeting Monday (last meeting was cancelled) to discuss Linked Agent field.

• IR (Amy): IR has a need for a temporary-sandboxy-thing to hack around in. Intend to create a "cookbook" for ways of doing things. They might end up with multiple different "ways" of doing these things. Hoping to get a spot in an open meeting with IR implementers.

  • is this "have a structured conversation around IR with a panel of implenters who are using 2.0, with feedback from the community?" "was thinking, more of what are the pathways/tools that let you do IR things, getting documented what the current tools and things are, e.g. for citations and embargoes?" getting to a little more "cookbook structured" rather than "show and tell"
  • Side note (Alistair) We could think about being vocal in DLF. Many other solutions are immature (too)
  • Side note (Amy) Commercial solutions are taking jabs at OS projects.

• TAG Update - in the agenda

• LG Update - in the agenda

• CoC Updates: about 5 people have responded they want to get training. Since Isabella is leaving we will probably get our new intern to participate in the January training, offering an alternate time for folks who can't make the november one. IF has proposed the idea of "passing on" the training but Drew asserted that it does not work that way. We don't have enough $$ to train everyone who wants it though that would be ideal. Maybe try to have a certain number of trained members in every event's CoC response committee.

Open meeting planning

• Open Meeting Planning: as part of the IG updates, we

  • will have a Modularization Project update by Rosie (with DGI participating/listening) in November
  • will likely have a IR panel/cookbook discussion in January.

• Open meetings in general

  • Who will run the "welcome" on the 25th? Sarah volunteered! (possibly with Isabella if she's available)
    • need to prepare a slide deck
    • need someone to act as "host" so it's not awkward
  • Alexander volunteered to be the developer present at the Q&A. This will be the first time we've had an official "techy person" who has agreed to be there (since we used to have Danny for this all the time). For following Tuesdays we would like to get other people - not the same people all the time, and not necessarily Committers.

Priorities for next meeting:

• Draft of doc regarding camps/con
• Get a handle on whats going on with the Terms of Reference