Jump to: navigation, search

Difference between revisions of "IoT/M2MIWG/Weekly call minutes"

< IoT
(Agenda)
 
(139 intermediate revisions by 10 users not shown)
Line 1: Line 1:
The Machine-to-Machine Industry Working Group is holding weekly calls on Tuesday at 9amET.<br>Participation to these calls is restricted to members of the IWG, but the minutes are public.  
+
{| align="right"
 +
| <googlecalendar title="IoT WG Meeting" mode="AGENDA" height="300" width="100%">u5j68s710reqmr37vd78jdlbm4%40group.calendar.google.com</googlecalendar>
 +
|}
 +
The Internet of Things Industry Working Group is holding bi-weekly calls on Wednesdays, at 12pm ET.<br>
 +
Participation to these calls is restricted to members of the IWG, but the minutes are public. We alternate between marketing-focused calls (upcoming events coordination, community outreach, etc.), and technical calls mostly targeting project leads, to synchronize cross-project activities.
  
The meetings are held via teleconference. The regular call-in numbers are as follows (if possible, please used caller paid numbers)  
+
The meetings are held via teleconference. The regular call-in numbers are shown below (if possible, please used caller paid numbers). There are a few local / toll-free dial in numbers, but you may want to setup a [https://wiki.eclipse.org/Asterisk#SIP SIP client] on your computer if possible.
  
*Ottawa (local call in Ottawa) 1-613-454-1403
+
* North America 1-866-569-4992
*North America (toll free) 1-877-369-7806
+
* Germany 49-692-2224-6059
*Germany (local call anywhere in Germany) 49-692-2224-6059  
+
* France 33-(0)-17-070-8535
*France (local call anywhere in France) 33-17-070-8535  
+
* UK 0800-033-7806
*UK (toll free) 0800-033-7806
+
* Switzerland 41-44-580-2115
 +
* Sweden 46-85-063-8386
 +
* Italy 003-902-3604-8268
  
Participant conference extension: 427, then enter pin 1156
+
Participant conference extension: 713, then enter pin 68764
  
*SIP clients can call 427@asterisk.eclipse.org, then enter pin 1156.
+
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
  
= Apr 2, 2013 (proposed agenda)=
+
----------------------------------------
* EclipseCon feedback (M2M sessions, F2F meeting)
+
* M3DA/MQTT convergence
+
* EclipseCon France
+
  
 +
= Feb 1, 2017 (WG Call)=
  
<br>
+
== Participants ==
= Feb 19, 2013 (proposed agenda)=
+
* Starting API Work.
+
* MqGnatt contribution
+
  
<br>
+
*Dan Gross, Samsung
<br>
+
*James Sutton, IBM
= Feb 12, 2013=
+
*David Bericat, Red Hat
* There is general consensus that the Continua sequence diagrams can serve as starting point for REST mapping and API work. We will look for means to get that work going in one or more of the projects, on the next call.  Axeda's work on the scenarios will factor into this as well.
+
*Laurent Lagosanto, MicroEJ
* Arlen is still intending to contribute McGnatt. It could  as a "best practices implementation" in combination with some new documentation.
+
*Roxanne Joncas, Eclipse Foundation
* Possible Webinars
+
*Benjamin Cabé, Eclipse Foundation
** It was proposed that a whitepaper and/or webinar on Device Management/Provisioning with respect to the Eclipse work, would be of value.  Mats will look further into this.
+
*Brad Micklea, Codenvy
** A security webinar to outline and discuss security solutions in end-to-end M2M application development
+
* An introduction to the Lua MQTT client, and the platforms and applications it is being used on.   
+
<br>
+
<br>
+
  
= Feb 5, 2013=
+
== Agenda ==
== Attendees  ==
+
=== Eclipse IoT Testbeds: review strategy and next steps. ===
*Mats Samuelsson, Axeda
+
Work on a set of industry oriented (vertical solutions) to showcase a technical solution and showcase the Eclipse projects and vendor ecosystem.
*Patrick Dempsey, Band XI
+
Eclipse IoT Members working together to set-up the testbed and create a demo that runs 24/7 on the Eclipse servers
*Hilary Tomasson, Eurotech
+
More details: https://docs.google.com/presentation/d/1nmdi-cmw_O-7W2qZKRHMN-3gw0WHxE75llcV0nMhS-U/edit?usp=sharing
*Scott de Deugd, IBM
+
Proposed Testbed scenario around Asset Tracking Management: https://docs.google.com/presentation/d/1KF7yxv5Dnk6b2a574HPtU5pHR5q7wvsT4skKjGDz1Q4/edit?usp=sharing
==Continuation: discussion of MQTT related topics raised by Axeda==
+
There are many options for collaboration
* Scott gave update on OASIS TC. Last date to join the TC is March 18th.  
+
* There was some feedback from review of Continua Sequence Diagrams that it looks like useful input to the API work. No next steps were agreed to but we will revisit this again after Phil and Mats have the opportunity to update the Scenarios and Problems.
+
* Discussion of MQTT related topics raised by Axeda but not covered last week.
+
**Lua: Axeda would like to contribute to Lua Client. Scott suggested their project lead call into the bi-weekly Paho calls for an introduction to Andy Gelme.
+
**Best Practices: There still are no volunteers for such a document but Mats said Axeda is interested in taking a lead to get this moving. There was some discussion of integration this with the pending MqGnatt contribution from Cirrus Link so we will discuss again when Arlen can make the cal.
+
* Ian pointed out a potential new contributions from m2m.io (https://twitter.com/kylemroche/status/297462594699157505). It looks that discussion has moved to the MQTT Google Group.
+
<br>
+
  
= Jan 29, 2013 =
+
*Dan Gross: Samsung interested in participating - Kura gateway using ARTIK.
== Attendees  ==
+
*Laurent Lagosanto: Potential use case for Eclipse Edje.  
*Mats Samuelsson, Axeda
+
*David Bericat: Excited and look forward to working with everyone.
*Phil Lombardi, Axeda
+
*Joe Biron, Axeda
+
*Patrick Dempsey, Band XI
+
*Arlen Nipper, Paho
+
*Benjamin Cabé, Sierra Wireless
+
*Scott de Deugd, IBM
+
==Discussion of MQTT related topics raised by Axeda==
+
*''High level positioning of the MQTT protocol'' (e.g. "long haul" networks). Scott and Arlen gave a brief overview of the discussion the OASIS C charter which led to describing a number of characteristics of MQTT and network topographies it is designed for. While it is well suited for wireless/constrained networks between an M2M gateway/edge and an enterprise type server, we probably want to avoid precluding its uses there, or in other network topologies. The IWG should pursue this as the topic of a white paper and it will be discussed again around MQTT-s (see note below)
+
*''Client ID:  
+
**The behavior to disconnect existing clients if a client connects to the broker with the same client ID is not ideal. It would be nice if the protocol specified that the broker should auto-assign an unused client ID. Perhaps this could be an option sent in one of the header fields?
+
**It would be great if the client ID could hold at a minimum a UUID length of characters.''
+
**It was not clear that this needs to be part of the MQTT protocol Axeda will work this into a requirement set so that the IWG can understand the problem and work on a recommend solution in the Eclipse projects. Phil will take a look at the existing M2M use cases in the form of [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_Scenarios Scenarios and Problems], to see if they can be modified to include the situations Axeda anticipates.  
+
*''MQTT-S: The community needs a public reference implementation of MQTT-S. When we performed our research on MQTT around October of 2012 we were unable to find any public implementations of MQTT-S. I remember seeing that the reason for this is that there are legal issues surrounding the MQTT-S spec somewhere on the MQTT Google Group.''
+
**Scott gave an overview of the OASIS Standardization effort and how it is positioned with Paho. Community feedback so far is that MQTT-S is important, yet out of scope of the OASIS Technical Committee. It is withing the scope of Paho and agreed to take this discussion outside the IWG calls to develop a recommendation.
+
*The remaining topics brought up were deferred to a future call.
+
<br>
+
----------------------------------------
+
  
= Archives =
+
'''Next Steps''': Stay tuned, we will be updating the group at large and scheduling individual meetings.
== 2012 ==
+
  
[[Machine-to-Machine/M2MIWG/Weekly call minutes/2012 Archives]]
+
=== 2. MQTT 5: Update from Ian Craggs / James Sutton on what’s in MQTT 5 and the expected impact on Eclipse Paho / Mosquitto and downstream adopters. ===
 +
'''Big set of changes:'''
 +
*Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
 +
*A messaging transport that is agnostic to the content of the payload.
 +
*Three qualities of service for message delivery:
 +
**At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
 +
**At least once", where messages are assured to arrive but duplicates can occur.
 +
**"Exactly once", where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
 +
*A small transport overhead and protocol exchanges minimized to reduce network traffic.
 +
*A mechanism to notify interested parties when an abnormal disconnection occurs.
 +
 +
'''Notes from the meeting:'''
 +
*Any request sent (and reply received) can have embedded metadata. This will be used for e.g letting a publisher know about *what* happened to the packet in addition to just acknowledging it
 +
**The CONNECT packet can contain information regarding what QoS are supported by the server
 +
**Supporting QoS 2 on the server is not mandatory anymore
 +
**Scalability
 +
*It will affect the Paho client and so a new Paho client will be created.
 +
**Improve API
 +
**Feedback from community
 +
**Work nicely with the new MQTT 5 features
 +
*The complete move will take a while, MQTT 3 will not go away anytime soon. It will be a parallel process. The previous versions of the client will be maintained. Some users might choose to use MQTT 3 since it’s more lightweight.
  
== 2011 ==
+
'''IMPORTANT:''' Get your feedback in as soon as possible, because in a few months it will be finalized, so review the specifications. View working draft 10 dated January 4: https://www.oasis-open.org/committees/documents.php?num_per_wg=10&wg_abbrev=mqtt
 +
 
 +
=== 3. PMC topics: project documentation, build machines, Docker, … ===
 +
Skipped this item - not enough PMC members on the call
 +
 
 +
=== 4. Misc. updates ===
 +
*WG Meeting at the Eclipse IoT Day San Jose Add your project for project update or intro: https://wiki.eclipse.org/EclipseIoT_SanJose2017
 +
*IoT Developer Survey Test it and give us feedback! It will go live next week. https://www.surveymonkey.net/r/Preview/?sm=PpPJLkX2kyFIkd4FpbfnijKgtSau8CTbzClUcIqMOv8UHpkGU6kxWrpBNJfYHpzC
 +
*Member companies are encouraged to ask for a special link that they can use to promote the survey to their communities, and have access to answers based on this segment.
 +
Open IoT Challenge: we will schedule a live hangout for project leads to answer any technical questions the participant may have. https://iot.eclipse.org/open-iot-challenge/
 +
 
 +
= Feb 15, 2017 (WG Call) =
 +
 
 +
== Participants ==
 +
*Kai Kreuzer, Deutsche Telekom
 +
*Jens Reimann, Red Hat
 +
*Dejan Bosanac, Red Hat
 +
*Gerald Glocker, Bosch SI
 +
*Shuai li, CEA-LIST
 +
*Roxanne Joncas, Eclipse Foundation
 +
*Ian Skerrett, Eclipse Foundation
 +
*Benjamin Cabé, Eclipse Foundation
 +
*Dave Woodard, Eurotech
 +
*Ian Craggs, IBM
 +
*Kilton Hopkins, IOTRACKS
 +
 
 +
== Agenda ==
 +
===Presentation new project proposal: Eclipse Ditto (Digital Twins) ===
 +
'''Presenter: Gerald Glocker, Bosch SI'''
 +
 
 +
Bosch will be proposing a new project called “Eclipse Ditto” soon for managing state of Digital Twins. Hopefully the proposal will be made next week.
 +
The Ditto Project will be a mediator between IoT Devices and the state of their Digital Twins. 
 +
Digital Twin is not really a fixed term. Bosch views Digital Twin as is a holistic view of all capabilities and aspects of a device/product asset including its digital representation.
 +
Ultimate goal is to use the digital twin as a service. There would be a higher level API to work with individual devices and you wouldn’t have to know what is happening in the background. The plan is to integrate with Eclipse Vorto and Eclipse Kapua.
 +
 
 +
Read the one-page: https://wiki.eclipse.org/File:Ditto_Project.png
 +
 
 +
*Questions:
 +
Can changes to the state be made on the device of the twin, or is it only one way? The state of the device could be in both directions. Changes to the state on the device or the digital twin would change the state of the other one.
 +
A twin is not necessarily 1:1 device, a twin can represent many things (device + JVM + …)
 +
 
 +
Project Proposal: https://projects.eclipse.org/proposals/eclipse-ditto
 +
 
 +
=== Presentation by CEA-List on Model Design Environment for IoT ===
 +
'''Presenter: Shuai li CEA-List'''
 +
 
 +
*Slides: https://wiki.eclipse.org/File:S3P-IoTModelingExecution_CEA_Primstech_MicroEJ-final.pdf
 +
*Video: https://www.youtube.com/watch?v=7JqAPRH0bfU
 +
*For more details, contact Shuai li from CEA-List.
 +
 
 +
=== Update on Testbeds ===
 +
'''Presenter Benjamin Cabé'''
 +
 
 +
Testbeds aim to showcase the software stack available from our open source projects, as well as the various offers that the WG members provide on top if it (cloud solutions, analytics platforms, hardware, integration services, …).
 +
 
 +
The first testbed will be a solution for Asset Tracking Management, more specifically tracking the delivery of valuable parcels. The end-to-end solution will comprise embedded sensors that can be attached to the parcels to monitor e.g temperature or vibration, IoT gateways in order to collect the sensor data (for example inside the delivery truck), process it, and report it to a cloud backend where it can be further analyzed, or made available to 3rd party apps. Members currently participating: Red Hat + Eurotech
 +
 
 +
A wiki page describes the solution https://wiki.eclipse.org/IoT/Testbeds/Asset_Tracking_Management and will be completed as other members jump on the train to extend the code scenario with their respective solutions.
 +
The code to replicate and demonstrate the testbed will be shared through https://github.com/eclipselabs/eclipseiot-testbed-assettracking.
 +
 
 +
Participation to the testbeds is open to any member of the IoT WG, and more details on the overall strategy are available at https://goo.gl/UeDekI.
 +
 
 +
=== Eclipse IoT Day in San Jose and Unconference ===
 +
'''Presenter: Ian Skerrett'''
 +
 
 +
We’re looking for use-case type speakers to present how their company uses Eclipse IoT projects. Last year at ECE 2016 we had a speaker from the Deutsche Bahn train system explain how Eclipse Paho and MQTT are used in their train systems.
 +
 
 +
Ideally the speaker would be from the Bay area since this is short notice. Please let us know if you know anyone that could be a good candidate.
 +
 
 +
=== Eclipse Leshan Press Release ===
 +
'''Presenter: Ian Skerrett'''
 +
 
 +
Today, February 15, we issued a press release about Eclipse Leshan and Eclipse Waakama “Eclipse IoT Announces Support for OMA LightweightM2M 1.0 Device Management Standard” Read it here: http://www.eclipse.org/org/press-release/20170215_lwm2m.php
 +
 
 +
=== IoT World plans ===
 +
'''Presenter: Ian Skerrett'''
 +
 
 +
Eclipse IoT will have a booth at IoT World and would like to coordinate with other members. We won’t be doing the pavilion since not enough members wanted to participate, but we will get in touch soon to partner with interested members, such as IOTRACKS, that showed interest in participating.
 +
 
 +
=== IoT Developer Survey ===
 +
'''Presenter: Roxanne Joncas'''
 +
 
 +
On February 7, we launched the third annual IoT Developer Survey. Please take the time to complete the survey and to share it with your coworkers and community.
 +
*Link to promote/share: https://www.surveymonkey.com/r/iotsurvey2017eclipseiot
 +
*Graphic for promotion: https://wiki.eclipse.org/File:Iotsurveypartners.png
 +
 
 +
----------------------------------------
 +
 
 +
= Archives =
  
[[Machine-to-Machine/M2MIWG/Weekly call minutes/2011 Archives]]
+
* [[IoT/M2MIWG/Weekly call minutes/2016 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2015 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2014 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2013 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2012 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2011 Archives]]

Latest revision as of 09:11, 20 February 2017

The Internet of Things Industry Working Group is holding bi-weekly calls on Wednesdays, at 12pm ET.
Participation to these calls is restricted to members of the IWG, but the minutes are public. We alternate between marketing-focused calls (upcoming events coordination, community outreach, etc.), and technical calls mostly targeting project leads, to synchronize cross-project activities.

The meetings are held via teleconference. The regular call-in numbers are shown below (if possible, please used caller paid numbers). There are a few local / toll-free dial in numbers, but you may want to setup a SIP client on your computer if possible.

  • North America 1-866-569-4992
  • Germany 49-692-2224-6059
  • France 33-(0)-17-070-8535
  • UK 0800-033-7806
  • Switzerland 41-44-580-2115
  • Sweden 46-85-063-8386
  • Italy 003-902-3604-8268

Participant conference extension: 713, then enter pin 68764

SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.


Feb 1, 2017 (WG Call)

Participants

  • Dan Gross, Samsung
  • James Sutton, IBM
  • David Bericat, Red Hat
  • Laurent Lagosanto, MicroEJ
  • Roxanne Joncas, Eclipse Foundation
  • Benjamin Cabé, Eclipse Foundation
  • Brad Micklea, Codenvy

Agenda

Eclipse IoT Testbeds: review strategy and next steps.

Work on a set of industry oriented (vertical solutions) to showcase a technical solution and showcase the Eclipse projects and vendor ecosystem. Eclipse IoT Members working together to set-up the testbed and create a demo that runs 24/7 on the Eclipse servers More details: https://docs.google.com/presentation/d/1nmdi-cmw_O-7W2qZKRHMN-3gw0WHxE75llcV0nMhS-U/edit?usp=sharing Proposed Testbed scenario around Asset Tracking Management: https://docs.google.com/presentation/d/1KF7yxv5Dnk6b2a574HPtU5pHR5q7wvsT4skKjGDz1Q4/edit?usp=sharing There are many options for collaboration

  • Dan Gross: Samsung interested in participating - Kura gateway using ARTIK.
  • Laurent Lagosanto: Potential use case for Eclipse Edje.
  • David Bericat: Excited and look forward to working with everyone.

Next Steps: Stay tuned, we will be updating the group at large and scheduling individual meetings.

2. MQTT 5: Update from Ian Craggs / James Sutton on what’s in MQTT 5 and the expected impact on Eclipse Paho / Mosquitto and downstream adopters.

Big set of changes:

  • Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
  • A messaging transport that is agnostic to the content of the payload.
  • Three qualities of service for message delivery:
    • At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
    • At least once", where messages are assured to arrive but duplicates can occur.
    • "Exactly once", where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
  • A small transport overhead and protocol exchanges minimized to reduce network traffic.
  • A mechanism to notify interested parties when an abnormal disconnection occurs.

Notes from the meeting:

  • Any request sent (and reply received) can have embedded metadata. This will be used for e.g letting a publisher know about *what* happened to the packet in addition to just acknowledging it
    • The CONNECT packet can contain information regarding what QoS are supported by the server
    • Supporting QoS 2 on the server is not mandatory anymore
    • Scalability
  • It will affect the Paho client and so a new Paho client will be created.
    • Improve API
    • Feedback from community
    • Work nicely with the new MQTT 5 features
  • The complete move will take a while, MQTT 3 will not go away anytime soon. It will be a parallel process. The previous versions of the client will be maintained. Some users might choose to use MQTT 3 since it’s more lightweight.

IMPORTANT: Get your feedback in as soon as possible, because in a few months it will be finalized, so review the specifications. View working draft 10 dated January 4: https://www.oasis-open.org/committees/documents.php?num_per_wg=10&wg_abbrev=mqtt

3. PMC topics: project documentation, build machines, Docker, …

Skipped this item - not enough PMC members on the call

4. Misc. updates

Open IoT Challenge: we will schedule a live hangout for project leads to answer any technical questions the participant may have. https://iot.eclipse.org/open-iot-challenge/

Feb 15, 2017 (WG Call)

Participants

  • Kai Kreuzer, Deutsche Telekom
  • Jens Reimann, Red Hat
  • Dejan Bosanac, Red Hat
  • Gerald Glocker, Bosch SI
  • Shuai li, CEA-LIST
  • Roxanne Joncas, Eclipse Foundation
  • Ian Skerrett, Eclipse Foundation
  • Benjamin Cabé, Eclipse Foundation
  • Dave Woodard, Eurotech
  • Ian Craggs, IBM
  • Kilton Hopkins, IOTRACKS

Agenda

Presentation new project proposal: Eclipse Ditto (Digital Twins)

Presenter: Gerald Glocker, Bosch SI

Bosch will be proposing a new project called “Eclipse Ditto” soon for managing state of Digital Twins. Hopefully the proposal will be made next week. The Ditto Project will be a mediator between IoT Devices and the state of their Digital Twins. Digital Twin is not really a fixed term. Bosch views Digital Twin as is a holistic view of all capabilities and aspects of a device/product asset including its digital representation. Ultimate goal is to use the digital twin as a service. There would be a higher level API to work with individual devices and you wouldn’t have to know what is happening in the background. The plan is to integrate with Eclipse Vorto and Eclipse Kapua.

Read the one-page: https://wiki.eclipse.org/File:Ditto_Project.png

  • Questions:

Can changes to the state be made on the device of the twin, or is it only one way? The state of the device could be in both directions. Changes to the state on the device or the digital twin would change the state of the other one. A twin is not necessarily 1:1 device, a twin can represent many things (device + JVM + …)

Project Proposal: https://projects.eclipse.org/proposals/eclipse-ditto

Presentation by CEA-List on Model Design Environment for IoT

Presenter: Shuai li CEA-List

Update on Testbeds

Presenter Benjamin Cabé

Testbeds aim to showcase the software stack available from our open source projects, as well as the various offers that the WG members provide on top if it (cloud solutions, analytics platforms, hardware, integration services, …).

The first testbed will be a solution for Asset Tracking Management, more specifically tracking the delivery of valuable parcels. The end-to-end solution will comprise embedded sensors that can be attached to the parcels to monitor e.g temperature or vibration, IoT gateways in order to collect the sensor data (for example inside the delivery truck), process it, and report it to a cloud backend where it can be further analyzed, or made available to 3rd party apps. Members currently participating: Red Hat + Eurotech

A wiki page describes the solution https://wiki.eclipse.org/IoT/Testbeds/Asset_Tracking_Management and will be completed as other members jump on the train to extend the code scenario with their respective solutions. The code to replicate and demonstrate the testbed will be shared through https://github.com/eclipselabs/eclipseiot-testbed-assettracking.

Participation to the testbeds is open to any member of the IoT WG, and more details on the overall strategy are available at https://goo.gl/UeDekI.

Eclipse IoT Day in San Jose and Unconference

Presenter: Ian Skerrett

We’re looking for use-case type speakers to present how their company uses Eclipse IoT projects. Last year at ECE 2016 we had a speaker from the Deutsche Bahn train system explain how Eclipse Paho and MQTT are used in their train systems.

Ideally the speaker would be from the Bay area since this is short notice. Please let us know if you know anyone that could be a good candidate.

Eclipse Leshan Press Release

Presenter: Ian Skerrett

Today, February 15, we issued a press release about Eclipse Leshan and Eclipse Waakama “Eclipse IoT Announces Support for OMA LightweightM2M 1.0 Device Management Standard” Read it here: http://www.eclipse.org/org/press-release/20170215_lwm2m.php

IoT World plans

Presenter: Ian Skerrett

Eclipse IoT will have a booth at IoT World and would like to coordinate with other members. We won’t be doing the pavilion since not enough members wanted to participate, but we will get in touch soon to partner with interested members, such as IOTRACKS, that showed interest in participating.

IoT Developer Survey

Presenter: Roxanne Joncas

On February 7, we launched the third annual IoT Developer Survey. Please take the time to complete the survey and to share it with your coworkers and community.


Archives