...
When:
Tuesday, October 4, 2022
9am to 10am PDT/12:00PM-1PM EST
ZOOM Please Register in advance for this meeting:
https://zoom.us/meeting/register/tJwpcO2spjkpE9a1HXBeyBxz7TM_Dvo8Ne8j
Attendees:
- Nathan Southern (openIDL)
- Sean Bohan (openIDL)
- James Madison (Hartford)Ken Sayers (AAIS)
- Faheem Z (Hanover)
- SuryaL (Chainyard)
- AdnanC (Chainyard)
- Peter Antley (AAIS)
- Allen Thompson (Hanover)
- Tsvetan Georgiev (Senofi)
- Yanko Zhelyazkov (Senofi)
Agenda Items:
- Antitrust Policy
- Welcome to our Co-Chairs Yanko Zhelyazkov and Aashish Shrestha
- Status Updates
- North Dakota Uninsured Motorist POC (Chainyard/AAIS)
- openIDL Testnet (Senofi)
- Auto Stat Reporting POC on Testnet (PeterA)
- Demo script shared
- RRDMWG Update
- Catastrophe discussion, mobile home owners and dwelling.
- Open Source Software Project Management (JeffB)
- Next Actions
- Co-Chair planning
Minutes:
- ReadTheDocs - easier to navigate as a document'
- Use GitHub as documentation resource, feeds to ReadTheDocs (documentation in repos)
- RTD has to be overhauled extensively, close to up to date with chainyard, needs to be revisted
- Also creating issues in GitHub - best way to document what has changed - CY, Senofi who have changed branches - make issues with what was the problem, what was changed, start there
- Ken - issues are repo specific - issues on repo where changes are made, sometimes across repos? Release-train where mult repos are dependent for a release
- Topic - how we org different modules - ETL should not have Infras as COde in diff repo for what is creating network - issue found everything is in one place in GitHUb, gitops branch should only start the network - talking ETL should live in ETL repo
- Historically, IBM had diff project for every folder, really difficult to manage change - diff repo for each one - we need to collectively decide - for this group to determine
- first thing - org of the code with the IAC and documentation - how does that fall out?
- what repos? how connected? release chains?
- Configs need to stay private per member (node) - specific implementation/deployment for a member, settings need to be in priv repo - can share, but held private
- Surya - thought of sep fork for each particular node off main, and how the sensitive info stored as the environ var in the pipeline of github actions, there were some actions written to deploy sep nodes using sep forks, also use sep branches in same repo to deploy diff nodes in diff environs, tried to avoid pushing any sensitive info (aws secrets, etc.) via github repos, right now input keys as secrets as opposed to config files in repos
- FOrking - concerning, forking to run locally, can start doing local changes,
- may have in repos test configs, easier for who is using it to set up own config/template - sample network/project
- related - when operator does work with UI, own priv server or resource? or translated into files pop in github?
- priv store for operator? console for dedicated local storage (ui)
- container deployed next to console - just works
| View file | ||||
|---|---|---|---|---|
|
Action items:
- Sean to set up call with Aashish and Yanko to set agenda
- Review Repos in GitHub per team - what is specific or generic to implementation,