[Openembedded-architecture] Improving Node.js developer workflow

[Esquivel, Benjamin]

Hello Henry,

> -----Original Message-----
> From: openembedded-architecture-bounces at lists.openembedded.org
> [mailto:openembedded-architecture-bounces at lists.openembedded.org]
> On Behalf Of Bruce, Henry
> Sent: Tuesday, November 15, 2016 1:12 PM
> To: openembedded-architecture at lists.openembedded.org
> Subject: [Openembedded-architecture] Improving Node.js developer
> workflow
> 
> I have a proposal for a theme for Yocto Project 2.3 development and it has
> been suggested that I post to this mailing list. In short it's about making life
> easier for Node.js developers by enhancing devtool and its supporting tools
> (e.g. recipetool). The rationale behind this proposal can be found
> at https://wiki.yoctoproject.org/wiki/Nodejs_Work
> flow_Improvements which also includes more details on the proposal and
> some opens.
I think Node.js is projected strong in the IoT industry and it theoretically fills the gap better than other programming languages when it comes to expected IoT market size. I support your point.
> 
> I'd appreciate feedback on whether people think that Node.js merits this
> attention. I'd also be interested to know what level usage drives the
> transition of recipes from meta-oe into core.
I have a question here, what do you think as the acceptance criteria for the Node.js developer workflow looks like? I'll throw in one obvious point:
- it is possible for IoT developers to create Yocto Project images with Node.js support.
That is just a top level acceptance criteria and it would help very much to clarify the scope of this YP-2.3 proposed theme if you could add further acceptance items.
> 
> Thanks for your time,
> 
> Henry
> 
> 
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-
> architecture
benjamin