-
Notifications
You must be signed in to change notification settings - Fork 374
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
List of Wakaama Users and Consultancy Companies/Individuals #470
Comments
@rettichschnidi, should we close this one ? Or do you want to create a new issue like eclipse-leshan/leshan#830 and pin it ? From my experience getting information about adopter is not so easy. Users don't give feedback about this spontaneously, you need to be proactive and ask when you have some good interaction with users through an open issue or PR. |
@sbernard31 I like eclipse-leshan/leshan#830 and I would like to do something similar. Until then, I think it makes sense to keep this issue open. I reword the original message once we managed to get stuff merged to master again. |
Husqvarna uses wakaama both as an embedded client on constrained devices and as a serverer as a library on iOS |
Cybercom has identified Wakaama as a project of interest for our IoT business/consultancy |
I am evaluating whether Wakaama could be part of my employers upcoming IoT platform.
Even before doing a deep analysis, two potential problems got identified:
The last commit to master is more than one year old.Wakaama got rebooted!There seems to be no show-case product/company using Wakaama. At least not in a way, which would make it easy for me to convince management to got with it.Actually, there are a few!Both potential problems could be eased if this project had lists of:
Looking at the top contributors they all seem to be either not working for a consultancy company or not active for a long time.Please note: I created or am watching similar tickets for Leshan (eclipse-leshan/leshan#830, eclipse-leshan/leshan#853) and Zephyr (zephyrproject-rtos/zephyr#18473).
The text was updated successfully, but these errors were encountered: