ICC: December 16, 2022

Attending:

[please add attendees] [indicate Chair, notes]

Agenda

Interest Group and Code of Conduct Committee Updates
Tech call discussions of LSAP and committers procedures - Kirsta would like ICC feedback on these documents and the planned process
Event planning document -- finalize ICC role recommendations?
SOAR analysis? Might need to be held for first January meeting.

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

Interest Group and Code of Conduct Committee Updates
- Early 2023 to convene the IG
  - Hear from the IG folks on what’s on their radar and what’s helpful to them
  - Inre: March Camp, perhaps some time set aside for IG session, that ICC could participate in?
  - First day is instruction, so possibly second day
Other IG Updates?
- IR: Jessica Colati (DGI) at last meeting, FLVC, service providers doing some IR work
- CoC:
  - Communications pathways and email addresses: Kirsta will connect the right people (Mark Jordan) and make sure the form setup is correct/access is correct
  - Drew will make sure the Samvera community is ok with us cribbing from their amazing documentation; waiting to hear back from them.
- There was discussion and agreement that the revised “How to Make an IG” doc is now ready to be posted to the wiki.
Tech call discussions of LSAP and committers procedures
- Kirsta would like ICC feedback on these documents and the planned process
- Context: need to update the LSAP docs as things have changed, as well as responsibilities for the ICC that are no longer relevant. The ICC still votes/approves, so want to make sure it’s clear what is required for software. These new versions should make everything clearer and can continue to be improved.
- Role of the ICC?
  - Want to make sure TAG is ok with this? Yes!
  - Can approve code. In some ways to rubber stamp really obvious things. Is also a place for other users of Islandora (non-developer) to offer feedback, opinion about usefulness.
  - In the past the CLA was an issue, and maybe it should be something that is checked right away and doesn’t hold up things? We may be moving away from it in the future (Fedora did this).
  - Example of existing Islandora code is slightly refactored and submitted as a separate thing, normally a PR but bc it is a new module it has to go through LSAP. Is there a way to think about this? Perhaps bounce to TAG to consider how to better/more efficiently manage?
  - Modularization events go to TAG and this avoids LSAP.
- Related discussion about Committers
  - When you give the module over, you can discuss maintenance (who/what group does this). And reverse is true: for stuff that is in core, before modularization is complete, if there’s a major feature change, it should get the same level of oversight. There are discussions that happen now, but definitely this is important.
- Add info in LSAP doc to specify that it doesn’t pertain to PR against existing repositories and agreed modularizations of existing code (or something similar, Kirsta can wordsmith); help to clarify.
- Suggestions for LSAP:
  - Add a license file to the flowchart, to ensure those are there. If the ICC will be voting, we should have a shared understanding of what licenses are acceptable.
  - Clarify how designates work. Voting procedure that ICC uses: can this document just say that the ICC will vote? ICC already has a process for voting.
  - What is the process for the wider community to comment or be consulted? This is part of the ICC role, so should this document express this? Step one includes a public email blast, but we don’t have anything in the doc about how we manage feedback. A reasonable period of time is given for community feedback to be given.
- Committers:
  - Empowering non-developers to contribute. This wider group will have access to Foundation keys that aren’t code.
  - Ambassadors becomes an event-specific term to encourage newer members to connect with. They may also have keys.
  - Add some more context to the doc to lay this out?
  - General members: get unlimited write action to wikis and docs
- Do we have enough committers to split the groups? There should be some kind of stepped approach, but maybe just they are all the same group. Rosie will take this to TAG to see if this is acceptable. Trainings to the community so folks feel confident, etc.
- The doc will be more widely shared in January for more feedback.
Event planning document -- finalize ICC role recommendations?
- Tabled until the new year.
SOAR analysis? Might need to be held for first January meeting.