Re: [wakaama-dev] Propositions to make Wakaama better

[jacques bourhis <jacques.bourhis@xxxxxxxxxxx>]

From marketing point of view, merging both is maybe an interesting proposal to solve our minor issue on website and logo.

But doing so, I'm afraid we will lose an important advantage we have today having both separated with different project leads and developer teams.
The fact, each one is implementing on its own the standard with different team and they are working perfectly well together, offers to those developments the status of "reference implementations".
From my point of view, this coupled situation brings a big value for both projects and the overall LWM2M offer at the end by increasing robustness and reliability in regards of standard compliancy.

Le 18/11/2016 à 21:25, Ian Skerrett a écrit :

I think merging Wakaama and Leshan into one project is an interesting proposal. If we have other implementations, like a JS implementation, would it also reside in Leshan?  I am just trying to understand the scope you are suggesting.

 

 

 

From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Julien Vermillard
Sent: Friday, November 18, 2016 11:14 AM
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] Propositions to make Wakaama better

 

Hi Hatem,Thanks for your email.

 

For Sierra Wireless, what we have on our todo list for Wakaama:

 - separate CoAP response: when the processing of the command is long, the CoAP server ack with an empty message and send the response with another message exchange.

 - better testing of wakaama, and having a way to say this version (or commit id) of wakaama works well with this version of leshan

 - more block1 (we did it for client receiving large connect from server but we could need it for client for sending a registration with a large payload)

 - improvement for the registration engine to make it more reliable and using elastic retries

 - expose low level CoAP primitive for mixinfg LWM2M and CoAP resources

For the marketing effort (web site, logo, etc..) I think you can rip the leshan website and ask eclispe to help for the logo.
I would also propose another crazy idea: to fusion wakaama with leshan, by keeping everything with the leshan name, we can use the leshan logo & website for everything, we keep to seperate code repo (leshan-java for current leshan and leshan-C/embedded for current wakaama code). Of course that would also merging the commiter and project lead list.

 

HTH

--
Julien Vermillard

 

On Thu, Nov 17, 2016 at 6:12 PM, Hatem Oueslati <hatem.oueslati@xxxxxxxxxxx> wrote:

Dear Wakaama Community,

 

For the people in this list who don’t know me, let me first introduce myself briefly. I’m Hatem Oueslati, co-founder of the Wakaama project. Indeed, David Navarro, Jacques Bourhis, and I, based on our passion and long experience for embedded systems and communication technologies accumulated at Palm, Access and Intel, we decided from a pure personal initiative to create a reference implementation of the very relevant and promising OMA LWM2M standard. At that time, we were employees of Intel (which we thank for letting us develop it on our spare time) and we naturally got this project hosted by the Eclipse Foundation so that to be spread and used widely by its vibrant open-source community. Thus was born Wakaama.

(BTW we had great fun brainstorming about its name with Ian and Benjamin J).

 

I’m glad to see that the community grew a lot since the project creation, we are now:

-        Almost a 100 members all over the planet

-        At least 17 active contributors

-        And 80 forks!

 

There has been a lot of progresses but we can make Wakaama even better. I think we’re missing:

-        A Website and its content so that developers get better access to relevant information to get started with the project (something equivalent to Leshan’s website).

-        A logo so that Wakaama finally gets its visual identity (we have nothing today).

-        A Roadmap or at least a roadmap discussion so that we, as a community, have a clear understanding of where Wakaama intends to go in accordance with the LWM2M standardization status. We can share our vision and the status of the standardization efforts as we also sit at the OMA and are very active in the standardization efforts.

 

Any objection before we actually put an action plan in place with the Eclipse Foundation so that to articulate the above points?

Who is interested and wants to participate to this?

 

Thank you.

 

Hatem OUESLATI

CEO and Co-Founder

IoTerop

Interoperability, Security and Device Management solutions for IoT

www.ioterop.com

email : hatem.oueslati@xxxxxxxxxxx

mobile : +33.(0)6.04.65.05.87

 

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

 

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