Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When awa client with support for lwm2m 1.0 will be released (version 0.2.6)? #361

Open
cimber opened this issue Jul 31, 2017 · 2 comments
Open
Labels

Comments

@cimber
Copy link

cimber commented Jul 31, 2017

Hi,
When Awa Client with support for lwm2m 1.0 will be released (version 0.2.6)?
We use it on a few our prototype unit, and it is crucial for us to know, due to our server has stopped supported candidate release of lwm2m.

best regards
Tomasz Ciombor

@berezovskyi
Copy link

So I guess the project is dead?

@DavidAntliff
Copy link
Collaborator

DavidAntliff commented Mar 5, 2018

I was one of the lead developers on this project. After Imagination Technologies announced the dismissal of everyone involved in this project, we worked hard to open-source it and make sure it did not disappear. Unfortunately, open source projects live or die based on their contributions. All of the original developers have moved on, and none of us are currently involved with "device management". The Connectivity Foundry has never contacted me and I have no idea who is actually behind it. I've never seen anyone who appears to be from Connectivity Foundry contribute or comment on this project.

Personally I don't have a current need to manage hundreds or thousands of deployed devices, so it is hard to maintain a project when there is no personal incentive. I had hoped, given the good quality of this project compared with other implementations, that a significant third party might contribute.

Adding support for LWM2M 1.0 is probably not difficult - the specification is unlikely to be much different from the release candidate 1.0 that was published for several years. The code is well written, there are many built-in tests, and the API is well designed and well documented. However it will need someone or some organisation with access to time, infrastructure and devices to take this forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants