**Session Date/Time:** 05 Dec 2023 15:00

# [IVY](../wg/ivy.html)

## Summary

The IVY working group met to address immediate operational items. Key discussions focused on resolving issues with meeting invitations, successfully migrating the `network-inventory-yang` GitHub repository to the IVY working group organization, and transferring all relevant open issues. The meeting also confirmed plans for the upcoming `00` draft submission and refined the process for future meeting invitations.

## Key Discussion Points

*   **Meeting Invitation Challenges:** Several participants, including a co-chair, experienced issues with calendar invitations not updating automatically or integrating correctly, leading to low attendance at the start of the meeting.
*   **GitHub Repository Migration:** The `network-inventory-yang` GitHub repository, previously hosted under Sergio's account and the C-CAMP organization, was successfully transferred to the `IVY` working group's GitHub organization. This involved granting appropriate ownership and membership roles (Italo, Oscar) to facilitate the transfer process.
*   **Issue Transfer and Consolidation:** All 30 open issues pertaining to the base model from the previous context (SEC draft) were successfully transferred and are now tracked within the newly migrated `IVY` `network-inventory-yang` repository. The old, duplicate repository was subsequently removed.
*   **Repository Naming Convention:** The repository name was adjusted to align with IETF guidelines, removing "draft-ietf-ivy" as implicit when hosted within the `IVY` working group's GitHub organization.
*   **Improved Invitation Process:** A more reliable method for distributing calendar invitations via the IVY working group page on the IETF website was demonstrated and verified, which correctly adds the event to participants' existing calendars rather than creating new ones. Sergio sent a test invitation to the mailing list, which several participants confirmed appeared correctly.
*   **Meeting Schedule Clarification:** Confusion regarding multiple invitations for January 10th (a weekly call versus the interim meeting) was discussed. Italo confirmed he would cancel the conflicting design team call.

## Decisions and Action Items

*   **Decision:** The `network-inventory-yang` GitHub repository was successfully migrated to the `IVY` working group's GitHub organization.
*   **Decision:** All 30 open issues applicable to the base model were transferred to the new `IVY` `network-inventory-yang` repository.
*   **Decision:** The old, duplicate GitHub repository for `network-inventory-yang` was removed.
*   **Decision:** The `network-inventory-yang` GitHub repository name was adjusted to conform to IETF naming conventions.
*   **Action Item:** Italo to submit the `00` version of the `IVY` draft (target: tonight/tomorrow morning).
*   **Action Item:** Chairs/Secretariat to utilize the verified method for sending calendar invitations for future IVY meetings to improve attendee calendar integration.
*   **Action Item:** Italo to cancel the conflicting design team call scheduled for January 10th.

## Next Steps

*   Submission of the `00` version of the `IVY` draft to the IETF Datatracker.
*   Ongoing development and issue tracking for the `network-inventory-yang` model within the newly migrated `IVY` GitHub repository.
*   Continued effort to improve meeting invitation dissemination for future IVY sessions.