Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [iot-wg] Next IoT WG Meeting - the Future of Paho - Tuesday 11th Feb
Hi everyone!

Just a reminder not to miss our IoT working group meeting tomorrow, February 11, 2020 @ 8am Pacific / 11am Eastern / 5pm Central Europe. Learn all about the future of Eclipse Paho!


*** Adding the invite to your calendar ***

1. GSuite (Google applications) users 
  • In Google Calendar, Locate the "Other calendars" header and click on the "+" button.

    image.png
  • In the contextual menu, select the "Subscribe to calendar" option. This will open a new screen.
    image.png

  • In the new screen, paste this value: u5j68s710reqmr37vd78jdlbm4@xxxxxxxxxxxxxxxxxxxxxxxxx
  • Press Enter. This will display the settings for the calendar, which will have been added to the "Other Calendars" section of Google Calendar.

2. Apple Calendar, Microsoft Outlook, Mozilla Thunderbird+Lightning users

Best Regards,

Frédéric Desbiens

Program Manager, IoT and Edge Computing | Eclipse Foundation, Inc.

Eclipse Foundation: The Platform for Open Innovation and Collaboration





On Fri, 7 Feb 2020 at 07:20, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello All,

the next Eclipse IoT WG meeting will be held on Tuesday February 11 @ 11am EDT.

To join the Zoom meeting from PC, Mac, Linux, iOS or Android: https://eclipse.zoom.us/j/646159255

We will be discussing the Eclipse Paho (https://eclipse.org/paho) project, and its future. 

Nearly all of the people are now working on the project in their own time rather than as part of their paid employment.  Now this isn't perhaps that unusual for Open Source projects in general, but it is a change from the start of the project, when several people working at IBM formed the initial committers.

The remit of the project was to help create a community around MQTT, and I think that it has generally succeeded in doing that over the last 7 years.  Paho consists of a number of components for the MQTT and MQTT-SN protocols, principally client libraries in various languages.  Each of the components has a committer responsible for it, some more involved than others. 

Some components do not have much active involvement, and one of the questions is how to treat those.  Should we deprecate in some cases?  From time to time, some people do want to get involved, but becoming an Eclipse committer is perhaps more onerous than they would like to take on.  Is there any feasible way of making temporary contributions easier?

I have recently been sponsored by HiveMQ (thanks to them) for some of my work on Paho, and Github sponsors is a new program which we may be able to take advantage of.  However given that I think that there are companies who rely on the Paho components, contributions in terms of time and effort are the most valuable.

If anyone would like to add their thoughts to the discussion, as a contributor or as a consumer of the project, please feel free to join in.  Thanks!

This is the first of a series of proposed project level discussions at the regular IoT workgroup meeting, alternating with general IoT WG business.

Ian Craggs

_______________________________________________
iot-wg mailing list
iot-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/iot-wg

Back to the top