Roadmap for this repo

[hannestschofenig]

I noticed that PRs for LwM2M v1.1 are available for a while already but none of them have been merged (for an unknown reason).

Can I have a roadmap for continuing the work on wakaama?

[sbernard31]

Hi @hannestschofenig,

A lot of PRs was provided by contributors but without any answer from actual development team. :worried: After a while contributors asked Eclipse foundation to find a solution. Eclipse foundation tried to contact current development team and in particular current project lead @dnav, but after several mails and time waiting without any answer ... The Eclipse foundation recently decides to create a new team for this project.

Too bad that so many time was lost just because previous team abandoned the project without any news... :disappointed:

Anyway, there are currently at least 2 active contributors which should revive the project soon. Stay tuned :wink:

[dnav]

To say I am surprised by this announcement is an understatement. I have not received any communication from the Eclipse Foundation in the last six months.

The last communication we had was in February with Frédéric. I had the impression that there was an understanding of the status of Wakaama. Wakaama is a LwM2M 1.0 reference implementation. It is a foundational baseline and was never intended to be a complete product. To quote my discourse from that discussion:

The consensus among users of Wakaama is that the project is complete. I had discussions with various industry people, and they are all satisfied with the current feature set. Of course, most have implemented additional features, but few want to contribute their features to Wakaama. This part should illustrate why new contributions did not get meaningful feedback: people are happy with the status quo and are reluctant to see new features coming to Wakaama. Yes, even LwM2M 1.1. They see that as a disruption of their current deployed setup.

Some additional points we should consider about the Wakaama project:

1. This is an open-source project. The license is permissive. If you are not satisfied with the direction, or the content of this project, fork it, as Scott did. Authorization is not required.

2. This project is free (as in beer). No one owes anything to anyone. As previously mentioned, many large corporations have benefitted from this Wakaama, and added needed functionality in their self-interest without contributing in any way, shape, or form, and that is okay. People contributing are either doing it in their free time or to answer their own business needs. If you need something missing from it, and if your employer is okay for you to spend time and money working on this, do it. Otherwise, get something with additional features, complete documentation, and a full-time team supporting it like https://github.com/IOTEROP/IOWA.

To all the users of Wakaama during these years, thank you for your interest. Just remember that software, like any other work, has value.

Sincerely, dnav

[boaks]

@dnav

AFAIK, Jens Reimann (@ctron) from the IoT-PMC tried to reach you multiple times, the last time via e-mail on 25.03.2020. Maybe, his e-mails didn't reach you, or your answers didn't reach him.

For myself, I have to say, that I spent my time into Californium, because it's too hard for me to switch to frequently between C and Java. It was also much too work in the Californium project.

[sbernard31]

Hi @dnav,

I didn't follow precisely what happened with wakaama last month, but I can maybe give some hints about the current situation.

About communication issue :

I have not received any communication from the Eclipse Foundation in the last six months.

Email was sent as you can see : https://www.eclipse.org/lists/iot-pmc/msg06997.html (your were in copy, your ioterop.com address was used) Maybe an issue with your email provider ?

About scope of the project :

Wakaama is a LwM2M 1.0 reference implementation.

It seems this was not clear for the community and we can not blame it as there is nothing about this in documentation(readme or websites). And by the past you let understand that wakaama will support LWM2M 1.1 : https://www.eclipse.org/lists/wakaama-dev/msg00506.html

So not really surprising that people expect LWM2M 1.1 support.

About community expectation :

The consensus among users of Wakaama is that the project is complete people are happy with the status quo and are reluctant to see new features coming to Wakaama.

This sounds clearly not the case when you see all the open PRs and issues.

Yes, even LwM2M 1.1. They see that as a disruption of their current deployed setup.

I do not understand, generally this problem is solved using semantic versioning (or something like this).

• one stable branch (1.x or 1.0.x) with bug fixes and not so much changes.
• another one (2.x) for new feature with big API changes.

Of course people who are happy with the current version is not forced to upgrade.

The license is permissive. If you are not satisfied with the direction, or the content of this project, fork it, as Scott did. Authorization is not required. No one owes anything to anyone.

Maybe, I'm wrong and @fdesbiens will correct me, but I think this is not so true for eclipse project. An eclipse project is more than that. Committers are responsible to make the project "alive" at least by answering to community. They should also facilitate contribution and integration of new committers etc etc .. (see https://www.eclipse.org/projects/dev_process/#2_1_Open_Source_Rules_of_Engagement) If there are no time or willingness to continue to make the project alive, committers should at least help to pass the torch.(I'm not sure this expression is really used in English :sweat_smile:) If nobody is interested by the project anymore it should be archived.

If you need something missing from it, and if your employer is okay for you to spend time and money working on this, do it

Community try to do it but nobody integrate the changes :confused:

Otherwise, get something with additional features, complete documentation, and a full-time team supporting it like https://github.com/IOTEROP/IOWA.

Maybe, I didn't get you but you seem a bit disappointed that there is not enough contribution to Wakaama project but at same time you encourage people to use your new closed-source solution. It sounds confusing to me.

But to be honest, I still don't get what is your position about Wakaama project. Do you still feel as project lead ? or are you considering that the project is "finished" and should be archived ? I don't get it ?

[fdesbiens]

Hi @dnav.

I am glad to see you are still around.

I am surprised you think we had reached an understanding. In my last private to reply to you, sent on January 20, I wrote this:

I understand that a large part of the user base is happy with the code and not looking for new features. However, at least a few members of your community seem to have a different opinion.

Obviously, it is up to the project team to decide where Wakaama will be headed. That being said, I would strongly recommend to explore ways to accommodate people like Scott. A possible way, for example, would be to declare the current 1.0 release train as a long term support (LTS) branch that would live in parallel to a 2.x branch implementing new features. There are many other ways to achieve the same result. What do you think?

You never replied to me. This led me to bring the matter to the PMC.

Jens sent several emails to the PMC list and to the same ioterop.com address my email had been sent to. You never replied to any of them.

In the last one, he wrote this.

Shouldn't I hear back from you in the next week (which should make this a period of 4 weeks), my recommendation to EMO would be, to declare the project dysfunctional, so that we can elect new project leads and/or committers.

We are well past that date.

Since April, I worked hard to find people willing to continue working on the project. We now have four potential committers willing to jump in.

If you consider Wakaama is complete, what you have is not a project but just a dead repository. Projects have roadmaps, respond to issues and have commits. Dead repositories do not have a community around them and certainly do not contribute to the improvement of the Eclipse ecosystem. Moreover, as @sbernard31 mentioned, projects and committers have obligations to the community. I am sure @waynebeaton can provide more details.

The simple fact this GitHub issue exists shows there are people who wish to push Wakaama forward.

So, David, the choice is yours.

If all you care about is a reference implementation set in stone, then you can create your own static fork of the current repository and live happily ever after.

If you still wish to be part of the team, then I am sure the new committers will welcome your leadership and contributions. However, this means you will have to agree with them on a new course and scope for the project in an open and democratic fashion.

Since you saw the previous messages in this thread, I expect you will read this one very soon. Please let us know as soon as possible if you wish to be part of the project's future.

[waynebeaton]

I am not aware of any reason why this project should be prevented from moving forward. Hypothetically, there may be some limitations on what can be claimed with regard to a specification, but I am not aware of any such limitations. Without having specific knowledge of the governance of the specification process to which Eclipse Wakaama contributes a reference implementation, I have to assume that as long as the 1.0 version remains tagged, it may continue to be the reference implementation while the project progresses.

Independent of any claims regarding specifications, the project is open source and the Eclipse Foundation's definition of open source requires that a project be both open and transparent. Note that our particular definition of open means "open to input from others" (we often refer to this as a "level playing field").

With respect, "you can fork it and do what you want" does not conform to the Eclipse Foundation's definition of open source.

Having said all that, a Eclipse open source project is required to operate within its defined scope. If the contributions are within scope of the Eclipse Wakaama project, then the contributions need to be given fair consideration for merging. It is completely reasonable, however, for a project team to reject contributions that fall outside of the project scope. It is not reasonable for a project team to completely ignore contributions (FWIW, there are a lot of open source projects that would love to have twenty pull requests).

By my observation, the project is no longer active. According to our process, in the absence of a compelling reason to do otherwise, the project should be terminated and archived. Alternatively, the project leadership chain (which includes the PMC and EMO) may declare the project dysfunctional and replace the development team. How shall we proceed?

[ctron]

Thanks for everyone, summing up what already has happened in the last months. So I don't need to do it :)

To say I am surprised by this announcement is an understatement. I have not received any communication from the Eclipse Foundation in the last six months.

As people already mentioned, that is not true. And I do think that this is indeed a big problem. If the people leading the project cannot be contacted.

By my observation, the project is no longer active. According to our process, in the absence of a compelling reason to do otherwise, the project should be terminated and archived. Alternatively, the project leadership chain (which includes the PMC and EMO) may declare the project dysfunctional and replace the development team. How shall we proceed?

I think the PMC already came to the same conclusion a while back. We already asked EMO to declare the project dysfunctional a while back. And we also took quite some extra time to discuss options, alternatives, …

To me, this issues doesn't change the current situation of the project, and I would propose to continue with the plan do declare the project dysfunctional.

As @waynebeaton already mentioned, curating a specific version/tag/state of the repository is no problem at all. But development should be allowed to progress. The project still continues to be an Eclipse project, and thus allows current and new committers to work in the defined project scope. Existing committers can still work on the project, as they can now, if they wish to do so.

@waynebeaton if you need any additional +1 from the PMC, please let me know and I will start another e-mail thread.

[dnav]

OK. It seems I need to remind people of a fundamental fact:

I am not an employee of the Eclipse Foundation.

So please, do not blame me for not doing the things you want to be done. I explained my position in February. It seems you found people willing to take care of this repo. There are other committers. Why the drama ?

[waynebeaton]

I am not an employee of the Eclipse Foundation.

I don't think that anybody has made any consideration of your employment status. To be clear, while we do need certain paperwork from committers to ensure that they have their employer's approval to contribute to open source projects, employment status is otherwise irrelevant. In case there is any confusion, with a very small number of exceptions (mostly the Eclipse Dash and Eclipse CBI projects), the Eclipse Foundation does not employ any project leads or committers.

There appears to be some confusion regarding the project lead and committer roles, so I'd like to spend a minute to discuss what we're doing here in the larger sense.

The Eclipse Foundation Development Process (EDP), which all committers and project leads agree to implement, is all about building a community and ecosystem around open source technology. This means that committers and project leads agree to build up and, at least in part, serve a community around their technology. At least in part, that means that committers and project leads sign up to court contributor participation and help them with the contribution process. To do this successfully requires giving up any idea of absolute control and allowing others to participate on a level playing field (with in the scope of the project). Our most successful open source projects have committers representing a wide diversity of interests, employers, and backgrounds.

I don't see any drama here. Only a community trying to participate in and grow the project.

[waynebeaton]

@waynebeaton if you need any additional +1 from the PMC, please let me know and I will start another e-mail thread.

The project has zero active committers and so I agree with the PMC's assertion that we are in an exceptional situation.

So now what?

My strong preference is that the existing project team return to an active state and that they start an election to bring aboard new committers to increase their diversity. Are any of the committers on this thread prepared to do that? FWIW, the project has three committers: all of them will need to vote in order for a committer election to conclude successfully.

That failing, as is outlined in the EDP, the project leadership chain (the project lead, PMC, and EMO) has responsibility to adjust the composition of the project team to get the project back into an active state. Who should be removed and who should be added?

My recommendation is that we (the PMC or EMO) take this to the wakaama-dev list.

[hannestschofenig]

It is good to hear that you guys are looking into the project management. I am looking forward to hear how the work on Wakaama will go forward.

[hannestschofenig]

FWIW I am interested to see whether this LwM2M v1.1 branch (see https://github.com/sbertin-telular/wakaama/tree/lwm2m_1.1) will get advanced because we are in the process of releasing LwM2M v1.2 and it would be unfortunate if the implementation work falls too far behind the specification development.

I am also interested to hear whether there is interest in integrating Mbed TLS into Wakaama.

[boaks]

@dnav

let me first say thank you for all the work you spend into LwM2M and this open-source offering. I'm not sure, if I understand, how you want to continue. I don't want to force something nor someone nor offend someone. As many others feel, that it's better to have "fresh committers", I would go to start such an committer-election, as @ctron has requested in an e-mail.

@dnav @sbernard31 @jvermillard

I would do so on Thursday, 01. October, Evening, if no-one objects that. So, is that OK for all?

[sbernard31]

@hannestschofenig,

it would be unfortunate if the implementation work falls too far behind the specification development.

At least for Leshan we have difficulty to follow you (OMA). Maybe a little part of explanation could be that sometime this is hard to get answer from OMA on not so clear parts of the specification or blind spots. I think investing more time on OMA github issues could help a bit.

In a perfect world, we(implementer and specifier) should be synchronized (we should start to implement version which is currently writing, not an already released one) This way we could report you issue that could be fixed before you release the version. Currently, we are de-synchronized and when we find issue sometime this is too late to fix in the specification. Sometime this issue generates more effort for implementer and can slow us a bit more.

@boaks, I have no objection (but as I'm not committer on Wakaama not sure my word is useful :slightly_smiling_face: ) Hoping the project will be on track quickly :crossed_fingers:

[boaks]

@sbernard31

My bad! I always thought, you're a committer here as well. But sure it's, David, Julien, and me.

[jvermillard]

@hannestschofenig

I am also interested to hear whether there is interest in integrating Mbed TLS into Wakaama.

This something Sierra Wireless is interested in and whiling to help

@sbernard31

At least for Leshan we have difficulty to follow you (OMA).

IMO sensible standard body should follow the implementation and not the reverse (e.g.: spitting tons of doc which clearly not implementable as-is and wait for fix).

[jvermillard]

@boaks

@sbernard31

My bad! I always thought, you're a committer here as well. But sure it's, David, Julien, and me.

I think he was in the initial project proposal, but his name was lost in the project creation process. If Simon is ready to code more C I think he would be a great addition :smile:

[sbernard31]

This is not about coding more C, this is more about having time to do it. :sweat_smile: Already difficult to manage Leshan and SBULB. I haven't time enough for Californium, I'm inactive on tinyDTLS and already abandon LDT :cry:. I don't feel I could add one project more.

But there are already, very active contributors which are identified to renew the team.

[dnav]

@jvermillard

@sbernard31

At least for Leshan we have difficulty to follow you (OMA).

IMO sensible standard body should follow the implementation and not the reverse (e.g.: spitting tons of doc which clearly not implementable as-is and wait for fix).

Allow me to reply to this particular comment. The work on the LwM2M specification at the OMA is following implementations.

Each feature from 1.0 to 1.2 is coming from a real world usage and the technical solution comes from what was implemented to answer it. OMA members then contribute to the standard for the sake of interoperability.

The best proof that the specifications are implementable is the several testfests organized by the OMA.

[hannestschofenig]

@sbernard31 and @jvermillard: Point taken regarding paying more attention to the Github issues. I will take a look at the raised issues and bring them up in our weekly conference calls.

[hannestschofenig]

Regarding "IMO sensible standard body should follow the implementation and not the reverse (e.g.: spitting tons of doc which clearly not implementable as-is and wait for fix)." I believe you need to have a healthy middle-ground. For the v1.2 spec we have had protoyping efforts for selected features but some features are exploratory.

[rettichschnidi]

The election of @sbertin-telular has failed: This election failed to receive the required number of votes in the alotted time.

What now? is this the time to formally replace the current team and reboot the project with a new one?

[sbernard31]

What now? is this the time to formally replace the current team and reboot the project with a new one?

FMPOV, I think it is.

[rettichschnidi]

Now that he got elected, what are the next steps? I would love to see the 1.1 LWM2M branch of @sbertin-telular finally getting merged and then moving on with cleaning up the PRs, improving the infrastructure, etc. so that new stuff can be more easily get added.

[sbertin-telular]

I have now been successfully elected as a committer. In order to officially be a committer and be able to merge pull requests, I need to complete an ICA.

Since I was first approached about becoming a committer back in January, my manager has left the company. I'm working with upper management to get approval to sign the ICA, but encountering some resistance.

[fdesbiens]

Hi @sbertin-telular!

Please let me know if there is anything I can do to help.

[sbernard31]

Project should be back on track now. See #488

I think we can close this one.

(Do not hesitate to reopen if needed)

[sbernard31]

This looks like an unexpected comment ? should I delete it ? (@dnav)

[dnav]

should I delete it ?

Yes please. Sorry for this.

I'm investigating to see how this email could end up here.

[boaks]

To be frank, sometimes I miss really some advertisement demonstrating the usage of eclipse open source projects.

But I don't think, that an more than year old closed issue is the intended place.

[boaks]

Deleted.

[slurfer71]

Join us for this unique online event on 8 Sept. where we discuss LwM2M and its capabilities from a developer and engineering perspective.

ioterop_logo (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpb_V5mNXLV3Zsc37CgSnpW1lycCL2gnlYnW1QrLjm6jwp-zW1c3s4R7RrXysN24F51QRxz6jW18nLBR59KTw1W1PJCj89l1rCZW35wtQ63BFl_7W3B5S1k8scFTJW4fnB9K8lzQl6W189J5B7YYHCgW6_3dFZ1cQ6BPN1FdBrJCR8rFW76wrXY8rrNKFW8SsZcW2NhQ7tW2kWGqP8Xt_zbVnK_Nn5BtTCyW54NLNm3k_8_7W6c58VM1jC157W97vbnV2DxCGRV9vDXH6FH45zW18ymlt8mp_d0W8w5NG_6hgX1MN5SQcw1LBX2QW4FXnNS3JSkYpW5QW-MT3LkBkwW54PM4y2GMSVMW5StS0w2MWGJKW5s0r3z3dJ2q4W1_0cF-1xVrb5W7Gcw3L7_qVyRW5Th4FK6Zg_wmW19JbJs7BKzvpW5W-WW37n_DzpW4WRrjK7m4F_-3jmh1 )

email-header-dev-forum-unlock-your-organizations-iot-device-management-capabilities-with-lwm2m-2r (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc1m5mNZcV3Zsc37Cg-hXW67SL8S6ppH05VC3Pjd7h6HQFW31q5NY2fZPQQW2fY0pW3CVT8vW2xy8HK2Lzth7N7_JXc8bC3XTW8ZRHH14YCC72N983RnS9bxSfW9lYzb-2HnDc6W7pCR098zc8rgW4BCB7P7-_HSTW3gf6rf7B94CqW5fKWmw4Mrm9xW7C2sqP23lHG_W8M4qp2658gDpW9bRJ7D39_wT-W3zqVwt232Dw0W3NRqZY8kXl58W9j68sw3Kgc0GW4T6_Pp6Qzj0BW4PRK0X7P0-WmW4dgszV6QQ4HWW13hVsZ5-sR6WW204mG48RycsqW1Pv5Wf4lPLpyVnfVY73ZBlN0W4rbkd14xzDKBW45mM0t2QbvChW83VTCn55cP-nW5FKptz5_bK_QW7cpFrH7xp5jsW2xhwg51BQmFMW2F_3H46rwN2tW6dYYFR1NQftjW7WknY-7gK2zSW7xk3PP2FcRPsW5W6mBf30_S52W8JLjsP4v3fq1W22SXQx87GbM6N1FGj_xdF4TFN3kLXlrH6gTDVDnTvk2s75ppN7D4wSvnL7jWW5TPYyl48-N9s3kZn1 )

[Developer's Forum]

Unlock Your Organization's IoT Device Management Capabilities with LwM2M

The benefits of using the Lightweight Machine to Machine (LwM2M) protocol to connect and manage IoT devices are noteworthy: reduced power and data consumption, firmware over the air (FOTA) updates and using latest security are just a few of the highlights. The freedom of not having to rely on a proprietary technology or build and maintain your own network is why many organizations looking for a sustainable IoT solution have chosen LwM2M.

But what exactly is LwM2M, and how does it stack up against the other technologies, such as MQTT? How difficult is it to implement, and what are the implications for an engineering or dev team? Join us for this free forum on 8 September at 16:00 CET and discover the potential that LwM2M has to offer.

Register + Learn More (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc1m5mNZcV3Zsc37CgQLfW8s1FBq107WGKW3mpsD7146M5fW2LVwP010W_-QW83P3L6698DZmW7qTlHf1WRh22W4cFj232KPVs-W7FtxLk34Jys_W929ttC597s60W5TK-FG8RpV0cM1CpCQHRh58W6lmBbY6TblhrW40ZPKZ4Qkn5KW6x8FsF55Lt-2W6pmV_H4lHnLFW4M07Bh387T_ZW9711tS8Bbjg3VQtgkC5vW_7nW8_3QzR65-mZ3W3wLPwN8Jj-PQVGzyZc28RF70W2v7JrX8vZVDvW5NwwhZ6js_qtW5KqZYD28dP3ZW4TWW9529Kv-NW5_h7jm8tKQymW8lVfzX63Hzx-W6slMpL1dxKZdW1BPTLr5n4Z9gN79VRzycb6bSW3NcyZd7G5Ht4W51hNdg4F78gzW5LsNXm5SlzxlW2h1_V41n7LhyW8hKjzV3mrHHsM_XRBGQLNpZN773NfPVLS0mW65qdd05Hlw_CW3N_Nx93c_nC2W2_CZdd17P5lwW8lmw924H7f9tW1NRVJH8z9_T-W1QgSyq3CYt5CW3_6wkR8G8S-_W8jr-lF6zV7V13pc31 )

Webinar Speakers Include

bio-photo-circle-harald-naumann (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc095mNY1V3Zsc37CgXTNW1b61ck3KXy-bW7MFnTl897YjzW1czFmW4fCxQbW54TKq06yp_NTW5w8jhr17yv-mW1yc0Mn7TVzy2W3DQ4Y26t1zKgN8GRvfgd3mjpW1F2BmR5jHp1RN5YlN9XjdB9YW6GcBZN184w8kW1b_RnZ1SX1XlW5r584B1xhJy3W3x1_cB3b8WrHW87lNRR2YD2LTW1HwzFG7mB1C9W4kj8kK65JC4-W4krfl_72whKcW8-tshB8l0Zt8N5MX1BpWF57dVDHVml43q49bW8pGzyk4nYs1zVDL6lG8KHYCWW6yBg1G2QSZ7SW644Xg54YR3W0Vkk6T72h_XV7W2Gr9V94Bg9GpW76zH6l4wg-2SW7CQ4NF82-mW8W8v597k58gKt9N2Sxw85vbdBtW1RDLVK8H58WvW800Sg28KhsLDW64FgYr5V5dTVVJds682lPywvW3c3zP68qCPfb35Yz1 )

Harald Naumann

email-logo-crout (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpb_V5mNXLV3Zsc37CgGDSW2twTFy7jndQtW2skdft8R2v5pW4-FvqJ5xwjsHW2N2r-F55GZZ5N2NNVwhSpG4-W6DDQRc3zGK2VW314hW567xbxcW5Rg-0w47ZC5HW8Ky9QJ18QslYW8tW9db496TR3W8Yl8yx62z2gGW94CDHT5ZMCpjW1Lgw_05VgFdhW783pVj4dG2lTV-fx6x30b1JjW1Mc7_-5f2tClW7RjFBZ4_TvnrW9dmcnF9hG5SbW3PJ1zw60tvWMW6-GWnN74QGYmW6_PPzg8S4R4WW5pFDKC7L3nr9W7hB1g299w1PyW1pYwgT7hgYN4W6WpDFK1yBqvxW4f-PWd1Dtch_W5ZNZH21q6S7cW57YQLB2RLPVXN5gYgBYzPNJfW8kTQSJ6BsDflW6QC9Bk5XGl8xW1BX5p18YH1g_W8rfDBt8R7mJyW5vHScT51pmFp3mc71 )

bio-photo-circle-friedhelm-rodermund (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc0t5mNYkV3Zsc37CgzSmW8VV46y5V4CzVW3ZMky06Ln2CmW8FSSKN4dBrz3VvTcqS7YKP1nW671FH76TQjq_W7F65kq57Y_xhW7Q3xj_7BHy46N3cVJq3sLps2W8zcZjY8wv_FHW2z_61t2LtVrbW1MmzQK9fqNcvW1gJSJm6krF4qW1QXptY1zFV0-W5wfGLX4S_JTqW1rkV8T7PJG3TW5Zs92H3N7jYHW5P340N6HJVHzVQ7CVB4zV5pcW7QS7Bs7ppq3MW8sY5VC3Hv2rpW6K3Q5g7c7xYQN7gR-96qJX1pN5Yp5r2GGGXvW33Cbvg4tXSMrW3FS_G98fD5thW70cVNm80CpyDW2J-pKk612JlcW50-Jw376mTgpW6028Rf8-fmJXW56zT6D1246mxW91XM5R47HhvvW1lmWD28lMnPkW2qfVL98vvmcBW3gk6FW7PLFB1W5yjWbX8hxpfdW7sfwjw6j--DTW8kV6tK6FwHX3Vb_QfP1Xc_wD3bGp1 )

Friedhelm Rodermund

email-logo-iotecc (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpb_V5mNXLV3Zsc37CgHL_W33HZH14b9-XKN2sBNQxDtBWmTL9R_8w9PPMW8F_b9x7c35PdW6TJqkx8l-65WVy7S584CCV2ZW4lQs3q7X8qq6W70_7tW7ZHR4MVDjn1J4ljy15W896wvF4DyW7dW8r3g9W2ntxmfW7MqtHJ6y1tG3W6_6sLW1sCs_-W8Db1y63428PxW1Pt6_x5FfJm0W7Q9Cpk2Dsn5lVFx6Y52TKJdNW1CtKsf658hxVW7nsYG13GCXgRW6XSht_7DFvKJW3W9FFZ2K3xcTW8CVl2l5tQXPJW4B-MHp4gJNdJW4YhBYx83NcwcW7p7W-53CDPLGW74mzb_2yzsdpW5FhnHk6SZh3kW49vqwK3Jd9H5VnW8wn49z84wVn7fxS9kQZjDW5TBWMM1f0FSJVL7NFl3jyd-7W32StwZ4vjG8pW6BstMg8BvSNZ3j1x1 )

bio-photo-circle-david-navarro (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc0t5mNYkV3Zsc37CgNvyW7JJNcW4nPTbyW2057rx45qlLGW4hK9JR7XCw_ZW3nv_Vv8PMfFYW5yF8Wp2T8FTnW27HnpP1CzRnmW4DYlzJ2YqzkBW1lHcJZ5wWvm6W2vWw28181QxrW9kr7lK53T5sMW3bLBBp3xzrnsW6Zjm4W4v2f2DW4z0QH04WY2NqW22K7yS8qZYr1VN7_TT9cBhb_W91w8np2QN-XhW5nJt5w278lsbW4jG2lX6Dv8sLW6PZflM1PJkFrW7g0MZ44BlqCFW3rcgXZ5yrLqqW4g85Yk2TkCj6W1Z1Jd54rZ62NMghbCXvbgdmW4LV3mD5JDg-zW6cGydb38Gr5MVGQ22X24BM78W2MHbPG74zCKQN47KT_fVY1djW4FYJ0Z18VxDMW64MtVg5C9BfrVl827f6zcLgVW2BJDG54p78gKW7gbzQ26GXTVnW2kG-nJ17MZ9cW99ZS7y84tTd7W1yr7Xr98DHSLW98qhHc5T__rX3hkF1 )

David Navarro

email-logo-ioterop (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpb_V5mNXLV3Zsc37CgSnpW1lycCL2gnlYnW1QrLjm6jwp-zW1c3s4R7RrXysN24F51QRxz6jW18nLBR59KTw1W1PJCj89l1rCZW35wtQ63BFl_7W3B5S1k8scFTJW4fnB9K8lzQl6W189J5B7YYHCgW6_3dFZ1cQ6BPN1FdBrJCR8rFW76wrXY8rrNKFW8SsZcW2NhQ7tW2kWGqP8Xt_zbVnK_Nn5BtTCyW54NLNm3k_8_7W6c58VM1jC157W97vbnV2DxCGRV9vDXH6FH45zW18ymlt8mp_d0W8w5NG_6hgX1MN5SQcw1LBX2QW4FXnNS3JSkYpW5QW-MT3LkBkwW54PM4y2GMSVMW5StS0w2MWGJKW5s0r3z3dJ2q4W1_0cF-1xVrb5W7Gcw3L7_qVyRW5Th4FK6Zg_wmW19JbJs7BKzvpW5W-WW37n_DzpW4WRrjK7m4F_-3jmh1 )

Would you like to talk?

We'd be pleased to speak with you. Schedule a meeting with our team at your convenience.

Schedule a Meeting (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc0t5mNYkV3Zsc37CgJKQW8X901b1QQbB5N3tWTdnvXJ_GW6LmfGc39XLcpW2rtbKc2jXQ-5W5gsppG2dkZDLW6c4gZw5Dy-rXW1dR2mZ3Vbg5xW6rl8CN9h1FtsW1P-Xd036S1t_W8YVN3v8hxVjDW8BlX5t5wSRYWW8SPY8-7KRbK4W5lM1lP7z6Xx_N581SBQd2QPlW4XVVKc6B7KQJVZMGZ46JJgNSW59wWbY1ZmtTHW7sGZKt6WcMCTW7KXR9w1yxc4kW1BmLDQ61q0nkW6CSxmy4hg9b2N7k9L9v1kjZRW1cts3W1vS3BgW27B8006S8MmnV8hwDN5gNZYXW6n9J8s1bfVX8N5QlFZf_7Fx_W1_hvNj7s_8HBW11pbWd7cnKx9W7N98dD93GFxtW2J1zC14X7qT_VmwTP445vwrbW2SC-K_7FDgbfW3Py0dd3RvZ-hN3RdyvvHQYhLW62p_5D7j1bBgW8mv6z47Fc7MwW8kFZHz2GwT143jj31 )

LinkedIn (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc095mNY1V3Zsc37Cg-4yW4LCsTQ7rKpWKW5g_z0g5gq-yNN4s4XVc2H1CZW4tZkp28qbs9_MM9kvHyv-xbW1ghV6b18SZHYW5k7NtT4m0hF-W8kDRP87_MqX4W8WY5KQ1vLFWxW1QLmJT2Kv5YpV2lVdG5q8-hkN1HnSW0jXZ2-VPQX_v5sytl3VqpG5z8d4xZwW3yrgtf6_HkKQW6DPlX81-YkCRW888RV_29Z_SkN1kVfP-DdZKgW2DLwPh4-Ss3YN4m0yrjygXftW5zkxhz5sKppzW3HPZNy3P22QZW1KbyPt58bnWSW2G-mpx3dspglVjWH_97BlVt6N2S3YzRB_yXwW77H-744ThSkzV7g55M7lk4JyW2l5YMV2c7PZlW8chYk_8KL9p0W5m2rN915dCHkW3Q_2l218S54JW1sFrV73FDBtGW2STyMT2L89ktW7RWQhv3-YhlyW3qTlLH3pDlRl3dh81 )

Twitter (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc095mNY1V3Zsc37CgTRkW4XvcpW8P7XXBW7W8D4n7dRMCLN9j5byzHnGcVVFWchT3MMGQMW4vYhbF2-PzgxW6Sf9bw3qbMs4W4vPQX-169K3dW4mfQd_5pmXmkW2lYmpy7NT9V5W6yZxY88jHyD1VRsVwj6zVgBRW36tlmp7ggRs3W529nVk51tRYRW2SGcqP56g2KXW8bPS1y4XfSzwW1rNGXF7rGQChW3RqMRM8JlVjzW1RG0xV2RDxT5W2YZrTB3cXkbNW90ftJc665fJJW7LfGQD22nB2sW30qC3Z4KR60nW83c-4x6z3XQWW5WT_xp5K5jwzW6dYK7c7Q4b9XW4gbrf74dgbkTW5xppn0307l2nW7pB6T31lXryRW7Nk6tn8n4Xy0W8LKT0h701S3wW2t56yL6dpZs1N22sHVWr93djW11psgf2_3k3jW1MJLkY9kDz-2W8DsJ2b7Cylr5W17SBXg2zWZP5366z1 )

Facebook (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VWJwXw6TW_V3W1s5MmF8D0V5nW67tPB74Pk_c6N2bpc095mNY1V3Zsc37Cg-jxW6_3V5l2JC33GW7VNkGH82Fh8qW7M11m_74NyFmW8FmVvY31KK_LW1vwg-c7K5HRsW5xRkfc4v7pMXW6R22w95PD16bW2MHWG17MVjtkW3PnG8S6wwyjYW2KRNnw2cwW1hW65D3QZ89p9wrW32t58k23b2SGW3sYVd55Qsbx1W7CwdXT4KVjLzW404n6s8LbVjDW8wGdDg6n0TpKW7-wWcL933qFMW6gBJVs47-wxBV4XWpN65fnk9W6gSrQ572XZRQW9kj8wl5KsB99W8FD4kc8hCxt6W1JRJZf4cvlJ2W7GRvWV6w-RjQW3G_8kS48MT-4W63kmNx2BbtJ9VqR6H86Zz8bVW8xv-qk4m7Ww4W8L2hhk1sxQCJW45qTGg8MH2P0W7SjJsB5GZCBdN8rt9JQvRcvgN1ZdYW1mN4sfW4zT7z083SX0pVlCpb791t-7tW690D6V8PtzJ934X51 )

www.ioterop.com, 621 Rue Georges Méliès, Montpellier, Herault 34000, France

Unsubscribe (https://email.ioterop.com/hs/manage-preferences/unsubscribe-all?languagePreference=en&d=VnzSxR6NRQzXW49KwbH4r48VrW3P0R2g3zkz0xW3R41vr21k00lW4fhF6R3LG-nsW3LG7NQ4kBrC-W3Q-cG64rxk1cW2m8Bdx3-1rV9W3T3R4J3BKSWwW3_fV8V4MxMlmVmWFdM5MWYy-N5MR9GW25tQnW9gWYzw85_vB7VWQBjh8KYxDxMXk_7QbvV00W3YK8Q04FgN3DN6sPZKFpDTC33gfV2&v=3&_hsenc=p2ANqtz-_1ZRpq1YrA6ztOMpkLSP_n-E2peKP8qHoOb9d-6RAxU148CIXySL5jRP7BRGPkiKk-GdLygDVQWhlxaOS5PQ351xQGM6o7AVI7DaVvRTob1VxlVad_SyTrsOOc5dYyRthZcX7k0q4ZqVieel0M7eiIOby23w&_hsmi=224359241 )

Manage preferences (https://email.ioterop.com/hs/manage-preferences/unsubscribe?languagePreference=en&d=VnzSxR6NRQzXW49KwbH4r48VrW3P0R2g3zkz0xW3R41vr21k00lW4fhF6R3LG-nsW3LG7NQ4kBrC-W3Q-cG64rxk1cW2m8Bdx3-1rV9W3T3R4J3BKSWwW3_fV8V4MxMlmVmWFdM5MWYy-N5MR9GW25tQnW9gWYzw85_vB7VWQBjh8KYxDxMXk_7QbvV00W3YK8Q04FgN3DN6sPZKFpDTC33gfV2&v=3&_hsenc=p2ANqtz-_1ZRpq1YrA6ztOMpkLSP_n-E2peKP8qHoOb9d-6RAxU148CIXySL5jRP7BRGPkiKk-GdLygDVQWhlxaOS5PQ351xQGM6o7AVI7DaVvRTob1VxlVad_SyTrsOOc5dYyRthZcX7k0q4ZqVieel0M7eiIOby23w&_hsmi=224359241 )

[sbernard31]

I'm investigating to see how this email could end up here.

@dnav, it seems the problem is still there :) :point_up:

[slurfer71]

Learn how South East Water is bringing leadership to the Utilities market using innovative IoT and water saving measures.

ioterop_logo (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp1c3kWF5V1-WJV7CgFbvW1X6Jf81cBM94W3MZ6rr2sQd8-W4VLB8T4tfhX7MpGM-TZLbmtW1DgkHz5gR2hpN8BszYnM8GMBW8hKRGn6H3Gx9W7JQdp31F2skGW4hD_kK55VRffW1dLZlr71fQCRW3nn-2v9dgj6hW7PYCtL8Mv31LW2l2_RX5bqFnXW56xzzp4r5vMPN6GpYVhx43jnW8-CXNK3Q3MKxW7QJhF74rwb_7W1xKJ1h1-qCjTW5L-Jkg7jjQW3W8RDhxG4yPzVjW67yWgs74qh5PW1J7Db31Zl4y93c-x1 )

email-header-from-our-blog-july-2022 (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp1w3kWFpV1-WJV7CgZ7tW4nvMhX8wpbZYW11xvwV2JbhgNVvH4YQ46l7V2W9cDMBK5XqQ6KW14Y0q71jhXLmW25t9CD4dtwkwW2wx0yQ1QMYtWW2xCntK4WjxTdN6pFg8jhP0fQW44Znr01D96zcW7nGP_F5DhGpjW79Pwt176qz_YW7tTc8k5nxcScVXKDWW1gqzPlW3wz29l4L_1bcW8LdcVB4HTG8rW5sqhr94Wq663W1rqRDJ7Rtn93W3yBrG933lsbyW36lY_k8n5R6JW7-xtLT5MHmTCW7JnMpL8B_N4cW1BtdQK10w-VsW7HnJ7g13V7Jz3kcd1 )

From Our Blog

Don't miss our most recent blog posts, featuring a visionary use case from a major Australian utilities company (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp2p3kWGhV1-WJV7CgSF9W5hblkS4MG7f7W5-63hZ7MK9BhN934y7SfSRF_W2kd6Zs8qZCLzW35rmjW70Frt2W6Sb7f11Sz0vSW3_K49t4H3wFNN54KL2J1DDlsW7H3mRk80rK07W563Xvd90lKSjN3-_6-JFJDCwN2JJ2bFjw7qzW34FddR3Vn0XSW16bz9K7YZYP7W2zmxpL8LnJKTVt91Gv6K0pzTW5TNLTz1Pvtz1W3pHfjD5rBSkGN4vdm-zlySYJW3nPTz03JG1P1W7f2Ry41ss4FWVBDGm72stbFxW6TJLg64d8_04W3WsMLF199L4yW2cNGJy58jDzjW2JynH480tzflVr3T8s645h2SVsy6QY7TcKZTW6V1wss3-KGxFW8KnJ5P6BTxMw2w11 ) , an overview of the benefits of Cellular IoT, and Counterpoint Technology Market Research's perspective on IoTerop's offer.

Why IoT is Vital for Water Utilities Struggling to Meet Demand

email-from-our-blog-july-2022-img-1 (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp2p3kWGhV1-WJV7CgSF9W5hblkS4MG7f7W5-63hZ7MK9BhN934y7SfSRF_W2kd6Zs8qZCLzW35rmjW70Frt2W6Sb7f11Sz0vSW3_K49t4H3wFNN54KL2J1DDlsW7H3mRk80rK07W563Xvd90lKSjN3-_6-JFJDCwN2JJ2bFjw7qzW34FddR3Vn0XSW16bz9K7YZYP7W2zmxpL8LnJKTVt91Gv6K0pzTW5TNLTz1Pvtz1W3pHfjD5rBSkGN4vdm-zlySYJW3nPTz03JG1P1W7f2Ry41ss4FWVBDGm72stbFxW6TJLg64d8_04W3WsMLF199L4yW2cNGJy58jDzjW2JynH480tzflVr3T8s645h2SVsy6QY7TcKZTW6V1wss3-KGxFW8KnJ5P6BTxMw2w11 )

IoT-driven smart water solutions could help optimize water scarcity issues, but they will have to be standardized to be viable as one of the biggest water utilities in Australia is currently pioneering.

Read More (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp2p3kWGhV1-WJV7CgSF9W5hblkS4MG7f7W5-63hZ7MK9BhN934y7SfSRF_W2kd6Zs8qZCLzW35rmjW70Frt2W6Sb7f11Sz0vSW3_K49t4H3wFNN54KL2J1DDlsW7H3mRk80rK07W563Xvd90lKSjN3-_6-JFJDCwN2JJ2bFjw7qzW34FddR3Vn0XSW16bz9K7YZYP7W2zmxpL8LnJKTVt91Gv6K0pzTW5TNLTz1Pvtz1W3pHfjD5rBSkGN4vdm-zlySYJW3nPTz03JG1P1W7f2Ry41ss4FWVBDGm72stbFxW6TJLg64d8_04W3WsMLF199L4yW2cNGJy58jDzjW2JynH480tzflVr3T8s645h2SVsy6QY7TcKZTW6V1wss3-KGxFW8KnJ5P6BTxMw2w11 )

IoT Industry Converges on Cellular as the Wireless Platform of the Future

email-from-our-blog-july-2022-img-2 (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp0k5js6pV3Zsc37CgSd8N1Dpdf3R5pDdW8V2-Xm1r3w2fW4Z5K-n5BcJ0ZW8x_8ly8yXSYhW6DVz5z1Fy2vYN8x41lPgfdL5N3tl-3HycX_xW2SJ0984Hlxt-W7S6B7B39QsC9W2fhzFn2D02SkW22LlhM6C1ZPsVh95fz8kyhBrW704s_Q7nyw9YVgcxYg35R1ryW9k0KKP3pX6sdW7PcFcC93nkjGW8GYDlS9ksYnYW6nz3JK25FX_jW4g9lWj1HhwxgW6Mndp74JT7S-N4Kb4GkNh2PvW8yznv03Jq2S-W3rSg2g9f32VnW1P_rYV8Ck0RJW8SH4bH2Mlf5qW77kF6J9gbC27W6ZbcmJ2_FRqfW1XZZCc2XBSPSW5dWSRq2HXDl6VgqjB47G_QtBW6X7-Fm3TcxP1W7dND712Mv0Qs3qhp1 )

Recently announced changes in France around LoRaWAN will cause pain for customers in the short-term but could lead to a brighter future if it leads to more standardization in low power, wide area IoT networking.

Read More (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp0k5js6pV3Zsc37CgSd8N1Dpdf3R5pDdW8V2-Xm1r3w2fW4Z5K-n5BcJ0ZW8x_8ly8yXSYhW6DVz5z1Fy2vYN8x41lPgfdL5N3tl-3HycX_xW2SJ0984Hlxt-W7S6B7B39QsC9W2fhzFn2D02SkW22LlhM6C1ZPsVh95fz8kyhBrW704s_Q7nyw9YVgcxYg35R1ryW9k0KKP3pX6sdW7PcFcC93nkjGW8GYDlS9ksYnYW6nz3JK25FX_jW4g9lWj1HhwxgW6Mndp74JT7S-N4Kb4GkNh2PvW8yznv03Jq2S-W3rSg2g9f32VnW1P_rYV8Ck0RJW8SH4bH2Mlf5qW77kF6J9gbC27W6ZbcmJ2_FRqfW1XZZCc2XBSPSW5dWSRq2HXDl6VgqjB47G_QtBW6X7-Fm3TcxP1W7dND712Mv0Qs3qhp1 )

IoTerop in the News

Article by Counterpoint Technology Market Research

email-from-our-blog-july-2022-img-3 (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp2p3kWGhV1-WJV7CgMWHW5NKLV-6nHbcrW3KWt1w29hHKDW5qfWBS4n-TYFN2PTRplnpZymW480JL74chjJ8W37svRc3F6WchW8MmDmT3yPN8xW2Z0JdQ3bkhfXW7Hxpb24T13Y8W5f8vfK8fnVJRV7knG62FqQgLW8CHdSj1nlVmcW3fBv7r4yWG8sW4kt3vm8C8bXGW6dKLfN5zTdZmW3BYNr-4d1ZXgMYHZyJlXHxKW5hHjvv94tMzQW2MHD8s1975w9W4vwW9W1mwhpqVsNg8z36bSvnN4H6JVH6SnsGW85r2J758PzPQW6jw0G-4jNxBZW54HyTQ1G27sLW7GdZ5B5gLQmWW2Hntbq99bjn9W4HC4zP5zC-hhW3l2rW653135XW41v4Kq71HvJ23fx91 )

IoTerop Betting on LwM2M for Massive IoT Adoption

The IoT ecosystem is maturing and the entire IoT module/device connectivity to the cloud is now managed by IoT platforms. The IoT platform space is getting crowded as players have just started to capitalize on this blue ocean opportunity.

Continue reading (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp2p3kWGhV1-WJV7CgMWHW5NKLV-6nHbcrW3KWt1w29hHKDW5qfWBS4n-TYFN2PTRplnpZymW480JL74chjJ8W37svRc3F6WchW8MmDmT3yPN8xW2Z0JdQ3bkhfXW7Hxpb24T13Y8W5f8vfK8fnVJRV7knG62FqQgLW8CHdSj1nlVmcW3fBv7r4yWG8sW4kt3vm8C8bXGW6dKLfN5zTdZmW3BYNr-4d1ZXgMYHZyJlXHxKW5hHjvv94tMzQW2MHD8s1975w9W4vwW9W1mwhpqVsNg8z36bSvnN4H6JVH6SnsGW85r2J758PzPQW6jw0G-4jNxBZW54HyTQ1G27sLW7GdZ5B5gLQmWW2Hntbq99bjn9W4HC4zP5zC-hhW3l2rW653135XW41v4Kq71HvJ23fx91 )

Would you like to talk?

We'd be pleased to speak with you. Schedule a meeting with our team at your convenience.

Schedule a Meeting (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp253kWF_V1-WJV7CgZDsW5c4jPn94KT6fW5QnmNy1ylfp7W5w3T_G8Df7c4W772XN79d4nM_W5Jvvq21CmjHdW8dwh7d3tV6GfW6yf21T1J0cfVW5xTDx76xTry7N6KjNvB2jt76W2x_BMd1vRjpdW64TXzP2scJTfN3F7wysqy6wWW5-D_JT4K_0wyW5TSQKV3XhtkSV72G4H2LTsXHW2K_xjF5Cw6WcW3X4hcG3P9JdCVSM9dd7q5zN9W73cCgb4RbX6lW5SdFRy27h64TW4pmrDZ20ztWWW8_87MK5Z3RCwW4Jxf5l7xkvvsVjmJGS795KGXW6pDb2q8_-z2HW33jB9q8WNR7RW1NXtVX6fF9yrW595JHj4rgYzY3nnT1 )

LinkedIn (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp1Q3kWFJV1-WJV7CgJP3W6rXt_V23WKzfW69Zpc34yGtPQW5q9wtR98zQJ5W23hlyT3l9q3kMvYVV4llbmYW5Kgt6P6vL1nPW3HYcW51zjhtZW2F9M0r6vmmHRW4NftkD62G-gkW3P-CYt1fl8shVsXVGG65G6l0W4sqj1689tzHZW89qN0-1-bc8KW4QhZq97Bd3X1W4r3fND4DF4tBN4x19W0Kd_7xW8k95Bx5JhZrfN8gQ_JcFv0pWW8mM5Gt13pw5fW7HL3cr88B8n7W5_MLNl7WQYNHVGJLb_1TS72gW7CZWM5219d3YVRbrJ343FXw9W3PCNb56dsQs8THC7_8FgbDk360S1 )

Twitter (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp1w3kWFpV1-WJV7CgGQHW82ZY5t57ftc5W3sy6vp8lqkS6W5FlYS146NjvWW6j73xT8X1BNtW8sDmZg88_Gg6W58D5922WBrnkVZpvNZ2mSkzVW3DyThX5Kr_q0W6yNHv82xdXtXW26g64K4wFfLgW5nwYkV2KkHDHMPbSGNdYrD1W60chmS4s-FS3W7F9Nd16-MLsVW9lTvVK3xrD1sW7W6-3y83CXD8W5J28Ry49YnMMW7R9px_2nGxtKW3Rb9XH2wxc1pW6Y-p_q4s6pKmW2Pkbpy3s-lwCW53GPkG7XklBwW1f5q_d4ymvy1V9ksRk6bX_fN3p0R1 )

Facebook (https://email.ioterop.com/e3t/Ctc/ZP+113/cb-tY04/VVYzkB58m6kRW2X3YLH5D1HwPW2x7JLQ4MnYDJN2lhp1Q3kWFJV1-WJV7CgRybW4B3HYK1KhxCxW6FrTjK5LyZ7PW6nGctR2-QbQwVRT9ky1wFNTnW2F1Z0s38QmkcW3nY-BT2lzXnzW1b3XJ671KjDxW8n7c4j78VdxtW7_NDjd75gNhkVnfWDM92kpP7V_f-J_3CMh51W6GMt5Q7s7dHzW4FvX2Y6_g2PmW7GhCCj1m93B5W2Pn_t456yxg1W4w8Wt897_FcyW9b84kL3rjpKLW3F1s_l3qWhLFW932tpL2Fh3BvW4sCpP_1HJnfNW5tZW8c7dtglhW6xc_gY3c1dCxW5BnY1F3VJB1JW70NRVz4VXnNWW3ff_PD2SBQZCW4xkns-90Xqt-3dLl1 )

www.ioterop.com, 621 Rue Georges Méliès, Montpellier, Herault 34000, France

Unsubscribe (https://email.ioterop.com/hs/manage-preferences/unsubscribe-all?languagePreference=en&d=Vnzr3b6NRQzXW49KwbH4r48VrW3P0R2g3zkz0xW3R41vr21k00lW4fhF6R3LG-nsW3LG7NQ4kBrC-W3Q-cG64rxk1cW2m8Bdx3-1rV9W3T3R4J3BKSWwW3_fV8V4MxMllVmWcNG8w4bSGN7MhMGk25yk2W6bGb2_4R0YtbW71V4fH5R4VqtV1yf0N3067xqW475k0X32B_wQW6Lk0nt3V-0l32473&v=3&_hsenc=p2ANqtz-_CLi4vRCcd8db9aCM8kN7yjOQvXjKF7DggrZy5SRyHfTAEF5ZK8kRMaMU0vX1IjHRZAVO-zCl4ctG4AeGKflsg7_uG_nqAHkn5GiTCp3G8HK_tUJXTbJuzdW6i0NL26x5v4NLMrHkV1TcAAo3qNvbW0in8eQ&_hsmi=219317894 )

Manage preferences (https://email.ioterop.com/hs/manage-preferences/unsubscribe?languagePreference=en&d=Vnzr3b6NRQzXW49KwbH4r48VrW3P0R2g3zkz0xW3R41vr21k00lW4fhF6R3LG-nsW3LG7NQ4kBrC-W3Q-cG64rxk1cW2m8Bdx3-1rV9W3T3R4J3BKSWwW3_fV8V4MxMllVmWcNG8w4bSGN7MhMGk25yk2W6bGb2_4R0YtbW71V4fH5R4VqtV1yf0N3067xqW475k0X32B_wQW6Lk0nt3V-0l32473&v=3&_hsenc=p2ANqtz-_CLi4vRCcd8db9aCM8kN7yjOQvXjKF7DggrZy5SRyHfTAEF5ZK8kRMaMU0vX1IjHRZAVO-zCl4ctG4AeGKflsg7_uG_nqAHkn5GiTCp3G8HK_tUJXTbJuzdW6i0NL26x5v4NLMrHkV1TcAAo3qNvbW0in8eQ&_hsmi=219317894 )

[sbernard31]

I'm investigating to see how this email could end up here.

@dnav, or somebody from interop could you try resolve this or at least give us an update about this ?

On my side I will try to contact eclipse support to maybe block this @slurfer71 user. (https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2067)

[dnav]

Once again I'm deeply sorry for this.

We purged our distribution lists for any github email address. But apparently the problem is coming from elsewhere as we did not send any newsletter in the last days. And the one published here this morning was sent in July...

Anyway we investigate it.

[sbernard31]

@dnav thx for update. The user was blocked by eclipse support, so this should not affect projects in eclipse organization anymore. If at sometime, you think the user should be unblock let us know.