Page History

Versions Compared

Key

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

...

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

Aug 20, 2020: Next meeting

July 20, 2020: Meeting Minutes; Meeting Recording

...

Nov 18: Meeting Minutes; Meeting Recording

Open Topics

...

Next meeting: Jim White to use the evaluation list provided by Tony/James to review the 30+ library/module imports of edgex-go that are dynamically versioned (have no version number tag - example is bitbucket.org/bertimus9/systemstat v0.0.0-
20180207000608-0eeff89b0690)
With the revised criteria list and module/library report, re-evaluate the draft vetting policy.
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.
Mike, Lisa and Tony to provide improved template around conventional commits and any recommended policy for TSC approval.
How should we deal with example code? Example code for app services lives in holding. Example code for Device Services lives in the device service SDK (although to some extent, device random and virtual are examples). Security is about to create some example code for SSH tunneling
.
Should all this be collected somewhere? Should it live in Github or in the docs (or on the Wiki or other location)? Should it be consolidated? Is it managed code or is it "buyer beware" code?
With TSC approval, Jim presenting proposal for new repo soon

Backward compatibility and what to do about Mongo, Logging and Support Rules Engine for Hanoi?
Some think exemption to remove these under minor version for Hanoi may have been too hasty
Should we reverse course? Are we too far down to reverse course?
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?
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)
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, …)
How do address module and component version release needs for examples (per Slack exchange with Luis Obando). go.mod in the examples helps - or at least some documentation on dependencies.
How do we review/remove artifact removal (docker images in Docker Hub, snaps, etc.)?
Is order of event/readings being sent by a single device service important? Are there async operations in any service that could change the order of events as they are sent from a DS to core to application services (with REST, 0MQ or MQTT infrastructure)? What do customers desire here? Is maintained order important? What is the current state of the system and can we diagram/document that? Jim to do some research first.
...