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 )
Meeting Agenda/Minutes
Meeting Agenda/Minutes/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
- 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
- Explore process and procedures for vetting 3rd party packages. This initially came out of the security working group as a need to vet 3rd party packages for security issues (see #1947). The community now has a larger interest in exploring it from a license perspective, size/performance impact, better alternative, as well as a security vetting. James Gregg has done research to explore options. James will lead the initial discussion (see https://github.com/jamesrgregg/1947-explore).
- Listen to Security WG recording (Password: 6U#=Q%?^) for context and more information.
- Currently being worked by James Gregg - next step is to find too to do PR review of any additions to go.mod file (see May 18 meeting notes)
- 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
- Does EdgeX work with IPv6? If not, what work needs to be accomplished and what are the impacts to the code base?
- Add a service dot setting to set up the adapter for listen on web services (Lenny to provide more details)
- EdgeX UI - it is for dev/test right now. Would we ever want to have a UI for production? Under what constraints?
- Explore how we can inform people of architectural decisions (especially the small ones vs ones done via ADR). Can we tag items in the project boards? If so, which ones and how? (comes from the Hanoi planning meetings)
- First topic to be explored on Jun 15th meeting
- How should we apply semantic versioning to modules? When do we update the minor and major versions of modules? (comes from the Hanoi planning meetings)
- PR Template for conventional commits is now in place for all repositories for all PRs but without TSC approval. It doesn’t appear to be affecting any problem. We need to finalize the shape of this and officially approve the template by the TSC.
- Extract of Device Service requirements to ADR legacy - what are all the pieces that need to be moved there?
- Per the Hanoi planning conference - we need to better define "bound checking" so that a design (and eventual implementation) can be brought forth to meet the requirements
- Currently considering limiting the number of operations that can be performed on a service (like a device service) over a period of time or setting the max request size (that lends to DoS attacks)
- Can the solution be more globally applied?
- Design metadata about the “gateway” or host platform (identity, location, …)