Hi team, sorry for the late reply.
Yes I do confirm that on my side. I’ve been quite slow recently, will update as soon as I have something. Cheers! Sent with Notion Mail <https://www.notion.so/product/mail> On Fri, 09 Jan 2026 18:19:57 GMT Michele Sciabarra <[email protected]> wrote: Hello Valerio pleased to meet you - the main tasks are: embed in the cli the tasks as they are normally downloaded by github and this is not acceptable for a release update the build using the latest images from the openwhisk project, most notably the standalone one To the best of my knowledge: - Federico Zambelli was working on the embedding - Luca Pandis was working on the image - Franscesco Tiberi already contributed long ago the suitable images we can just use Can you guys please update Valerio so he can coordinate? We can setup a periodical meeting also. OpenWhisk used to have one every 2 weeks. Michele Sciabarra | CEO m: +44 747 984 8388 e: [email protected] l: https://linkedin.com/in/msciab Nuvolaris Inc | 1209 Orange Street , Wilmington DE www.nuvolaris.io [image: linkedin icon] <https://www.linkedin.com/company/nuvolaris-io> [image: youtube icon] <http://bit.ly/nuvtube> [image: twitter icon] <https://twitter.com/NuvolarisIo> On Fri, 9 Jan 2026 at 19:15, Valerio Jiang < [email protected]> wrote: > Hi everyone, > I recently subscribed to the dev mailing list after reading the threads > from the past weeks regarding the upcoming OpenServerless release and the > work needed to make it fully Apache-compliant. > I’d like to propose myself as a coordinator to help move this effort > forward in a concrete and structured way. > My intention is not to introduce new requirements or make decisions, but > to help ensure that what has already been discussed converges into an > actual release. > From what I understand so far: > > * > there is a clear list of tasks and open items tracked in GitHub issues > * > some work has already been started (notably by Luca Pandis and Federico > Zambelli) > * > progress risks stalling without regular coordination and visible > checkpoints > > To help with this, I’d like to suggest: > > 1. > Using this mailing list as the primary coordination and decision-record > channel > 2. > Referring to the existing GitHub issues as the single source of truth for > tasks and blockers > 3. > Organizing a short sync call every two weeks (30 minutes, time-boxed) > 4. > Periodically checking in on open items and blockers directly on the > mailing list > > If the community agrees, I’m happy to: > > * > propose a first short call and share a draft agenda > * > summarize outcomes and action items on the mailing list after each sync > * > regularly ask for status updates to keep things moving > > Before doing that, it would be great to get a quick status update on: > > * > what is currently in progress > * > what is blocked > * > whether there are missing owners or decisions needed to move forward > > Feedback, corrections, or alternative suggestions are very welcome. > Best regards, > Valerio > >
