[Elinux-discuss] How to start multi-entity embedded work on specific topics? (boot time, for example)

[Bird, Tim]

Hello embedded Linux strategists,

I bet you thought this list was defunct.
Well, I've finally gotten around to using it.

I'll jump right in.

I'd like to start some collaboration on reducing embedded Linux boot time.

The problem is that this work potentially crosses sub-systems, architectures,
software project boundaries, build systems, companies, trade associations, etc.

I've got an "embedded and IOT" microconference scheduled for Plumbers in Vienna
in September.  I'm soliciting topics for boot time reduction, for this micro-conference.

What is the best way to do outreach for this?
I know of a few people I'll be contacting directly to see if they want to repeat
material I've seen from them in the past.  But I'd like to make sure other
people know about the session.  Any suggestions for people I should contact,
or groups, companies or lists that I should announce this on (besides linkedin
and this list)?

I'd also possibly like to start some kind of ecosystem-side workgroup on this topic.
This is partly inspired by Khasim Syed Mohammed's presentation
at last year's Plumbers, were he talked about requirements for automotive boot time and
some ideas for specific improvement areas.[1]

The LF's embedded Linux Project is no more, so I need a place to organize discussions,
and possibly store code in-flight.  I can put some ad-hoc things on the elinux wiki,
but is there a better place to do this?  In AGL?, in Linaro?, in CIP?, In Yocto?  At
a specific embedded Linux company?  At a processor or product company?

Any of these might be a good place to "home" the workgroup.  But there are pros
and cons to each location.

Let me know what you think.

Regards,
 -- Tim

[1] https://lpc.events/event/17/contributions/1499/