Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 Linkhttps://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

ajhw77vTU

Meeting Agenda/Minutes/Recordings

Currently running bi-weekly:

Previously run monthly:

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
  • Apache 2 licensing requirements (per Tony E message and Brett P (LF) and Ducan (IOTech) responses.
  • 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?