February 25, 2022

• Notes per Schedule
• Topics Roster L10 Document
• Islandora Coordinating Committee Google Drive Folder

Attending:

• Mirko (Chair), Amy, Greg, Rosie, Drew, Rebel, Isabella (notes)

Agenda

• Open Meeting review, ideas for next Open Meeting
• Continue discussion of ICC Code of Conduct and Terms of Reference discussion; Drew suggested that we also refer to the Code4Lib Code of Conduct

Interest Group Updates

• Metadata IG (Rosie)
• IR interest group (Bryan or Don)
• ISLE Interest Group (Danny or Bryan)
• Documentation Interest Group (Amy/Yamil, Melissa, or Mirko)

Islandora Events

• Next Open Meeting March 29
• How involved do you want to be in a hybrid Islandora conference in August 2022 (respond to Kirsta's email?)

Action Items

• Code of Conduct proposed revisions and comments on doc
• Amy to create a feedback form for the community to see what other topics Open Meetings should address
• March Open Meeting planning
• Zoom statistics

Notes

• February Open Meeting
  • Sandbox demo went well
  • There was too much time for open Q&A - Open Meeting should have an afternoon session to better structure conversation
• Tracking Zoom attendance - Isabella to look into this
• Future Open Meeting
  • Topics
    • More demos of sites - ex. how Carnegie Mellon made Mirador work for newspapers in Islandora 8
      • Mirko to reach out to Carnegie Mellon contacts and follow up in the coordinating committee slack
    • Github Discussions - in order to participate, you have to have a Github account and use it. This could be a barrier to entry for folks less comfortable with using Github. As a topic for the Open Meeting, this could help surface concerns people have about the discussions forum, barriers to use (e.g. how do you set up a Github account?). We want to demo how Github discussions work, what features it has, and how to use it (e.g. when does something belong in a Github discussion rather than Slack, Google Group?)
      • Mirko to send message to islandora slack asking if a Tech Call attendee can do this demo, Isabella to follow up in next week's Tech Call and meeting minutes
  • Balancing open meetings with more interpersonal as well as tech sessions
  • How do we ask the community what they want to hear about? Whiteboard tool suggested
  • Amy will draft a preliminary google form in which to gather this feedback. Could this live on the Islandora website?
• Code of Conduct discussion
  • Values-centred language: on the right track.
  • May be too focused on 'sunny situations', while a CoC is to address the most problematic situations.
  • Code4Lib model: call for volunteers to the committee, then a community vetting window where community feedback can be gathered
  • 2 scenarios outlined
    • Scenario 1 - Ultimate authority is the Board or Leadership, and the ICC is to do investigations, perhaps make recommendations, but then hand off to the Board.
    • Scenario 2 - The Board and Leadership relegate the authority to ICC, ICC thinking of further relegating it to a subcommittee composed of some ICC members and some volunteers.
• Drew to draft edits to CoC document for review among ICC