Meeting Time and Conference information
Meeting Time: 3rd Monday of each month at 1pm EST as needed (if Wednesday at 8am PT on a bi-weekly basis, i.e. alternating with the TSC Meeting. If there are no agenda items, the meeting is will be cancelled)
EdgeX Working Group 2 is inviting you to a scheduled Zoom meeting.
Time: Jan 18, 2023 08:00 AM Pacific Time (US and Canada)
Every 2 weeks on Wed, until Dec 4, 2024, 50 occurrence(s)
Please download and import the following iCalendar (.ics) files to your calendar system.
https://zoom.us/meeting/vpEufuytpzstxwJXp3nHvYoHt7mRqmscaw/ics?icsToken=98tyKuqtrTIvH92Vt1_Hd7MvA5X5buHylmlZgJtNzxHNFRlcShehO9BTP6F8Ec-B
Join Zoom Meeting
Zoom Link: https://zoom.us/j/353955907?pwd=MEhSQmlxQ1lLcCtsQ1lrSFh6cE0yQT09
Meeting ID: 353 955 907
Passcode: 150365
One tap mobile
+16699006833,,353955907# US (San Jose)
+1646558865612532158782,,353955907# US (New YorkTacoma)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656253 215 8782 US (New YorkTacoma)
877 369 0926 US Toll-free 855 880 1246
US Toll-free +1 647 558 0588
Canada 855 703 8985
Canada Toll-free Meeting ID: 353 955 907
Find your local number: https://zoom.us/u/abscayLpz ( https://www.google.com/url?q=https://zoom.us/u/abscayLpz&sa=D&ust=1570487240002000&usg=AOvVaw3baS0YLvMOVQhRUsVMH2C0 )ajhw77vTU
Meeting Agenda/Minutes
...
Mar 16, 2020: special edition of the monthly architect's meeting to test holding Hanoi planning via conference call. Meeting will be from 10am to 1pm EDT
Agenda
/Recordings
Currently running bi-weekly:
- August 1st, 2023: Meeting Recording
- Discussed potential integration with Project Alvarium (Trevor Conn in attendance)
- July meetings were cancelled due to no active topics
- June 21st, 2023: Meeting Slides; Meeting Recording
- May 10th, 2023: Meeting Slides; Meeting Recording
- Slides presented by EMQ relating to their proposal of NanoMQ for EdgeX: NanoMQ For LF Edge.pptx
- April 26th, 2023: Meeting cancelled this week
- April 12th, 2023: Meeting Slides; Meeting Recording
- March 15th, 2023: Meeting Recording
- March 1st, 2023: Meeting cancelled this week
- Feb 15th, 2023: Meeting Recording
- Feb 1st, 2023: Meeting Recording
- Jan 18, 2023: Meeting Recording
Previously run monthly:
- Nov 28, 2022: Meeting Recording
- Sep 26, 2022: Meeting Slides; Meeting Recording
- Aug 15, 2022: Meeting Cancelled due to summer holidays
- July 25, 2022: Reviewed: EdgeX 3.0 Candidates List, Meeting Recording
- June 27, 2022: Meeting Minutes; Meeting Recording
- May - no meeting due to planning meeting
- April - no meeting due to release work
- March 28, 2022: Meeting Notes; Meeting Recording
- Feb 28, 2022: Meeting Notes; Meeting Recording
- Jan 24, 2022: Meeting Minutes; Meeting Recording
- Dec 13, 2021: Meeting Minutes; Meeting Recording
- Nov 15, 2021: Meeting cancelled
- Oct 18, 2021: Meeting Minutes; Meeting Recording
- Sept 20, 2021: Meeting Minutes; Meeting Recording
- May 17, 2021: Meeting Minutes; Meeting Recording
- Apr 19, 2021: Meeting Minutes; Meeting Recording
- Mar 15, 2021: Meeting Minutes; Meeting Recording
- Feb 16, 2021: Meeting Minutes; Meeting Recording
- Architects Meeting - EdgeX Microservice Authentication.pptx.pdf (Bryon's presentation)
- Jan 26, 2021: Meeting Minutes; Meeting Recording
- Nov 30, 2020: Meeting Minutes; Meeting Recording
- Sept 21, 2020: Meeting Minutes; Meeting Recording; Adopter Series Requirements Summary
- Aug 20, 2020: Meeting Minutes; Meeting Recording
- July 20, 2020: Meeting Minutes; Meeting Recording
- June 30, 2020 (extra meeting to address growing number of issues): Meeting Minutes; Meeting Recording
- Jun 15, 2020: Meeting Minutes; Meeting Recording
- May 18, 2020: Meeting Minutes; Meeting Recording (Password: 1k&I$62S)
- April 20, 2020: Meeting Minutes; Meeting Recording (Password: 5W?vM=#X)
- Mar 16, 2020 (special long session): Meeting Minutes; Trevor Conn's V2 API issue notes; Meeting Recording
- V2 API redo – continuation of ongoing conversation led by Trevor Conn
- Review of current decisions (see https://wiki.edgexfoundry.org/display/FA/Monthly+Architects%27+Meeting?preview=/37912817/43581510/API%20V2%20Follow-up%20Meeting%20Notes.pdf)
- Device Service / App Functions committing to their own OpenAPI docs using the principles from the V2 ADR
- Depth of "common implementation" across sub domain applications. Does this end at the bootstrapping or are there additional layers to align? How do we know when it's enough?
- For Core/Support services, do we split V1 and V2 persistence?
- Start to think about which use cases we think would benefit from the addition of pub/sub
- Do we consider Support services optional? Should we approach Core-Data as Support-Data for V2?
- Additional open architect topics (time permitting)
- Blacklisting of devices and how/when to remove. Tony to argue on how blacklist APIs and delete APIs can be called by some system ; Trevor to argue how this needs to be automated. Implementation of any automation (whether all in metadata, via message bus to rules engine/app services, etc.) - all dependent on the first decision about whether to automate.
- Finalization of config-seed removal ADR (#0005)
- Revisiting holding and when work needs to enter holding (and what it takes to get out)
- Acceptance of DS and testing needs - how to bring a new device service from holding to the EdgeX repos (presented by DS WG – Iain, Tony)
- Bound checking issue (presented by Tony)
- Apache 2 licensing requirements (per Tony E message and Brett P (LF) and Ducan (IOTech) responses.Whether it was necessary and wise to move code from EdgeX org to holding only to go back to EdgeX org again (vs just make a new repo directly in EdgeX) - initially covered in Jan 15, 2020 TSC
- Address policy on patch/minor release based on discovery of CVE or other security issue (high/critical) - would we force dot release of all services, just affected ones, ??? For Consul and Mongo, we just minor rev'ed those services and containers. What if issue was in one of the go services? Would we have to minor release all (example go from 1.2.0 to 1.2.1) on all services even if only one was affected?
- Last 20-30 minutes of the session, reflect on good/bad/ugly of the meeting. Does this format fit for Hanoi planning? If so, how/when should we hold Hanoi sessions.
- Mar 3, 2020: Meeting Minutes; Meeting Recording (API V2 special session)
- Feb 18, 2020: Meeting Minutes; Meeting Recording
- Jan 27, 2020: Meeting Minutes; Meeting Recording
- Dec 16, 2019: Meeting Minutes; Meeting Recording
- Dec 4, 2019: Meeting Minutes; Meeting Recording
- Nov 18, 2019: Meeting Minutes; Meeting Recording
Open Topics
- Review hybrid app-device service UCR (and any subsequent ADR) with the community
- What to do about the future of system management
On Hold Topics or Pending Research
- None at this time
- Revisiting holding and when work needs to enter holding (and what it takes to get out)
- Acceptance of DS and testing needs - how to bring a new device service from holding to the EdgeX repos (presented by DS WG – Iain, Tony)
- Bound checking issue (presented by Tony)
- Apache 2 licensing requirements (per Tony E message and Brett P (LF) and Ducan (IOTech) responses.Whether it was necessary and wise to move code from EdgeX org to holding only to go back to EdgeX org again (vs just make a new repo directly in EdgeX) - initially covered in Jan 15, 2020 TSC
- Address policy on patch/minor release based on discoveryof CVE or other security issue (high/critical) - would we force dot release of all services, just affected ones, ??? For Consul and Mongo, we just minor rev'ed those services and containers. What if issue was in one of the go services? Would we have to minor release all (example go from 1.2.0 to 1.2.1) on all services even if only one was affected?