Page Comparison

Date

15 Dec 2022

...

1. Call to Order (KenS)
2. Anti-Trust, Review of TSC Meeting format and Participation by TSC Chair
3. Introductions
4. TSC Activity Desk (TSC - Activity Tracking)
   1. Architecture Working Group (KenS)
      1. https://lucid.app/lucidchart/ac20d4e1-50ad-4367-b5cf-247ed9bad667/edit?invitationId=inv_de1a5e61-8edc-488a-90ee-8312f8c69cd4&page=cy0StEuclJcD#
      2. Call for Co-Chairs for the AWG (Sean and Ken)
   2. ND Uninsured Motorist POC (KenS)
   3. openIDL Testnet update (JeffB)
   4. RRDMWG Update (PeterA))
   5. AAIS Stat Reporting using openIDL internal Project (PeterA) 
5. Infrastructure WG Update/Documentation (Sean)POC Scope Redux. TSC - POC 1 Scope 
6. AOB

FOLLOW UP:

Recording/Meeting Minutes

...

SB: Read LF Antitrust Policy

KS: Called everyone to order - a quorum was present. 

II. Agenda

A. AWG Update

1. KS: Most of activity involves Peter's progress
2. KS: Considerable activity synchronizing Chainyard and Senofi
3. SB: noted that we have lost Satish and now need co-chairs and greater member input into calls. People from individual organizations can propose via email individuals from their companies to co-chair these discussion
4. KS: ND - 60 day reprieve to carriers who wanted more time to do more due diligence. First call will be in February in lieu of Dec

B. TestNet update

1. SB: Up and running. Main priorities for Dec are to work on a discovery process around HL Fabric Operator - will make fabric deployment more efficient. Two members of IBM team leading in HL. Senofi team working on discovery to gauge if we want to incorporate this into openIDL. Second priority: supporting Peter Antley and the demo he's doing.
2. SB: CA hasn't been finished because we've prioritized Peter's work and operator discovery - CA is 3rd priority.

C. RRDMWG Update

1. Prototype for coverage report - almost there. Most of biz questions answered but implementation work still needs to be done
2. Moving forward with homeowners. Both of these tables loaded up. Mason producing homeowners report - and making excellent time. 
3. Hoping we can do a demo for auto and homeowners
4. Working with Senofi extensively - stood up testnet PA has access to test net account and openIDL application. Working on polishing a demo where we show creation of report
5. PA's next to do is working on the report generator - has two separate PDCs and working on aggregation of two.

D. Infrastructure Working Group

1. Two ad hoc calls - first btwn CY and Senofi. Second focused on changes that have happened
2. Goal of this group: coordination between the infrastructure partners. Over time will focus on network implementation planning
3. Public meeting - anyone who wants to join can
4. We're seeking TSC input. Senofi & Chainyard will lead these discussions
5. TSC will bring all related issues (bug reports, pull requests, etc.) to the BOG. Maintainer process needs to be defined. A bigger function or working change - esp. consequential - TSC would need to approve this. Meeting will be used as starting point to organize w/infrastructure partners. Right people brought in to make final decisions.
6. Three main deliverables for this group
   1. Defining the code merge btwn ND and Testnet 
   2. Implement code merge btwn to code bases
   3. Define maintainer policy
7. Group will self-organize and create within the codebase side of idl the maintainer corps. 
8. SB will be identifying main reps from Senofi & Chainyard to be running these calls.
9. As idl we need to define how discussions will occur so that it isn't always ad hoc. 

III. Logistical decision - TSC over the holidays - meeting on Dec. 28th? No. Agreement to meet in 2nd week of January.

IV. Questions from group

1. Hanover - clarification of when their node will be up and running and mapped to HDS - JB: clarified first quarter of 2023. AT: wants to make sure he has the right people present for discussions in Q1 2023 - JB agreed to confer with AT before year's end to make this happen.
2. Questions about when data is anonymized - Hanover. JB confirmed that the only data that leaves their nodes is data that has been aggregated and anonymized to their satisfaction. Completely under control and nothing leaves without their consent. 

Discussion Items:

...