You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openserverless.apache.org by Michele Sciabarra <mi...@nuvolaris.io> on 2026/04/29 21:28:32 UTC

It is time to release and apply for graduation!

Hello everyone, call to action and also call to show you are here and you
are following the discussion.

Our mentors are concerned there is no activity on the maling list and no
attempts has been made to do a release.

The project is actually very active, we have important adopters like big
cloud providers, defense contractors and government agencites, and
countless private companies. And there has been commits as you can see here

https://github.com/apache/openserverless-task/graphs/commit-activity

There are also contributors from different sources. But we have neglected 3
important standards for the apache: using the maling list.  doing a source
release and also respond to security advisories.

To be honest those advisories where something I was not aware of, but they
are important.

The truth is: we communicate in multiple channels, whatapp discord slack
linkedin google meet but we do not use the maling list simple
because almost all of us are not used to do that.

And we did not do a source release because the way we distribute the
software works for us, with a cli downloaded that pulls the. tasks and the
images on demand from github and docker hub.

But since we want to be an apache project this have to change.

So now it is time to do a source release and we have to do that using the
maling list.

To coordinate the release we need a strong technical directions. There has
been volunteer but unfortunely they did not make progresses in the attept.

The only people who cnl realistically coordinate the release are me,
Francesco or Bruno. And both Francesco and Bruno are busy for personal
reasons, although they are willing to help. I was very busy as the CEO of
Nuvolaris so to do the coordination by myself was not an option, until now.

But this now changed: I handed over the role of CEO precisely because I
want to focus more on technicalities and now I am going to use the free
time to coordinatethe release.

And I will do it USING ONLY THE MALING LIST.

Let me say it again: no whatapp. no discord. no slack. no google meet. Only
this maling list.  And expect a lot of messages.

So please go on you gmail and change settings to be sure messages from
dev@openserverless.apache.org pops up clearly and you can read

I contacted all the contributors to ask them to join the list and now I am
asking everyone to show you are reading the messages .

So please let's start the process of building the source release and lets
do it introduciont yourself and the skills you have and we can use.

This is the list of what we need:

- shell, python and jascript programming for the task
- go programming for the cli engine
- kubernetes and python programmig for the operator
- bascially all the the languages for the runtimes
- also the visual studio code exntsion needs maintenace

Do you copy? Can you help ? Where?
Please reply.
Thanks.

--
Michele Sciabarrà - msciabarra@apache.org - linkedin.com/in/msciab
Apache OpenServerless committer - reddit.com/r/openserverless
Apache OpenWhisk PMC member  - Author Learning Apache OpenWhisk
<https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/>

Re: It is time to release and apply for graduation!

Posted by Carlo Longhitano <ca...@uva-sys.com>.

Hello,
Carlo here, hope I can help in some way!
I was just now configuring a dev machine for the purpose.


On Wed, Apr 29, 2026 at 11:29 PM Michele Sciabarra <mi...@nuvolaris.io>
wrote:

> Hello everyone, call to action and also call to show you are here and you
> are following the discussion.
>
> Our mentors are concerned there is no activity on the maling list and no
> attempts has been made to do a release.
>
> The project is actually very active, we have important adopters like big
> cloud providers, defense contractors and government agencites, and
> countless private companies. And there has been commits as you can see here
>
> https://github.com/apache/openserverless-task/graphs/commit-activity
>
> There are also contributors from different sources. But we have neglected 3
> important standards for the apache: using the maling list.  doing a source
> release and also respond to security advisories.
>
> To be honest those advisories where something I was not aware of, but they
> are important.
>
> The truth is: we communicate in multiple channels, whatapp discord slack
> linkedin google meet but we do not use the maling list simple
> because almost all of us are not used to do that.
>
> And we did not do a source release because the way we distribute the
> software works for us, with a cli downloaded that pulls the. tasks and the
> images on demand from github and docker hub.
>
> But since we want to be an apache project this have to change.
>
> So now it is time to do a source release and we have to do that using the
> maling list.
>
> To coordinate the release we need a strong technical directions. There has
> been volunteer but unfortunely they did not make progresses in the attept.
>
> The only people who cnl realistically coordinate the release are me,
> Francesco or Bruno. And both Francesco and Bruno are busy for personal
> reasons, although they are willing to help. I was very busy as the CEO of
> Nuvolaris so to do the coordination by myself was not an option, until now.
>
> But this now changed: I handed over the role of CEO precisely because I
> want to focus more on technicalities and now I am going to use the free
> time to coordinatethe release.
>
> And I will do it USING ONLY THE MALING LIST.
>
> Let me say it again: no whatapp. no discord. no slack. no google meet. Only
> this maling list.  And expect a lot of messages.
>
> So please go on you gmail and change settings to be sure messages from
> dev@openserverless.apache.org pops up clearly and you can read
>
> I contacted all the contributors to ask them to join the list and now I am
> asking everyone to show you are reading the messages .
>
> So please let's start the process of building the source release and lets
> do it introduciont yourself and the skills you have and we can use.
>
> This is the list of what we need:
>
> - shell, python and jascript programming for the task
> - go programming for the cli engine
> - kubernetes and python programmig for the operator
> - bascially all the the languages for the runtimes
> - also the visual studio code exntsion needs maintenace
>
> Do you copy? Can you help ? Where?
> Please reply.
> Thanks.
>
> --
> Michele Sciabarrà - msciabarra@apache.org - linkedin.com/in/msciab
> Apache OpenServerless committer - reddit.com/r/openserverless
> Apache OpenWhisk PMC member  - Author Learning Apache OpenWhisk
> <
> https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/
> >
>

Re: It is time to release and apply for graduation!

Posted by Michele Sciabarra <mi...@nuvolaris.io>.

Thanks RIccardo. Can you write in the ML the links to the work you did to
implement the Flask runtime?


Michele Sciabarra | CEO

m: +44 747 984 8388
e:  michele@nuvolaris.io
l:   https://linkedin.com/in/msciab
Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US
www.nuvolaris.io linkedin.com/in/msciab


On Wed, 29 Apr 2026 at 22:42, Riccardo La Malfa <
riccardo.lamalfa94@gmail.com> wrote:

> Ho,
>
> Yeah… I find way more comfortable using the Discord channel as you said
> previous la, but I can try to communicare more often via mailing list too
> at this point
>
> On 29 Apr 2026, at 23:32, Alessandro <al...@sanino.dev> wrote:
>
> 
> Hello,
>
> Alessandro here.
>
> Loud and clear. I agree we must stick more to the mailing list now.
>
> What are the next steps with biggest priority now?
>
>
> ----------
>
> [image: 1767884826087001_170458169.png]
>
> *Alessandro Sanino*
>
> SENIOR MULTI-CLOUD / AI ARCHITECT
>
> Mobile:
>
> *(+39) 393 559 8693*
>
> Email:
>
> *alessandro@sanino.dev <al...@sanino.dev>*
>
> Website:
>
> alessandro.sanino.dev
>
> The content of this email is confidential and intended for the recipient
> specified in message only. It is strictly forbidden to share any part of
> this message with any third party, without a written consent of the sender.
> If you received this message by mistake, please reply to this message and
> follow with its deletion, so that we can ensure such a mistake does not
> occur in the future.
>
>
>
> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
> questa.
>
>
>
> ---- Il mer, 29 apr 2026 23:28:32 +0200 * michele@nuvolaris.io
> <mi...@nuvolaris.io> * ha scritto ----
>
> Hello everyone, call to action and also call to show you are here and you
> are following the discussion.
>
> Our mentors are concerned there is no activity on the maling list and no
> attempts has been made to do a release.
>
> The project is actually very active, we have important adopters like big
> cloud providers, defense contractors and government agencites, and
> countless private companies. And there has been commits as you can see
> here
>
> https://github.com/apache/openserverless-task/graphs/commit-activity
>
> There are also contributors from different sources. But we have neglected
> 3
> important standards for the apache: using the maling list. doing a source
> release and also respond to security advisories.
>
> To be honest those advisories where something I was not aware of, but they
> are important.
>
> The truth is: we communicate in multiple channels, whatapp discord slack
> linkedin google meet but we do not use the maling list simple
> because almost all of us are not used to do that.
>
> And we did not do a source release because the way we distribute the
> software works for us, with a cli downloaded that pulls the. tasks and the
> images on demand from github and docker hub.
>
> But since we want to be an apache project this have to change.
>
> So now it is time to do a source release and we have to do that using the
> maling list.
>
> To coordinate the release we need a strong technical directions. There has
> been volunteer but unfortunely they did not make progresses in the attept.
>
> The only people who cnl realistically coordinate the release are me,
> Francesco or Bruno. And both Francesco and Bruno are busy for personal
> reasons, although they are willing to help. I was very busy as the CEO of
> Nuvolaris so to do the coordination by myself was not an option, until
> now.
>
> But this now changed: I handed over the role of CEO precisely because I
> want to focus more on technicalities and now I am going to use the free
> time to coordinatethe release.
>
> And I will do it USING ONLY THE MALING LIST.
>
> Let me say it again: no whatapp. no discord. no slack. no google meet.
> Only
> this maling list. And expect a lot of messages.
>
> So please go on you gmail and change settings to be sure messages from
> dev@openserverless.apache.org pops up clearly and you can read
>
> I contacted all the contributors to ask them to join the list and now I am
> asking everyone to show you are reading the messages .
>
> So please let's start the process of building the source release and lets
> do it introduciont yourself and the skills you have and we can use.
>
> This is the list of what we need:
>
> - shell, python and jascript programming for the task
> - go programming for the cli engine
> - kubernetes and python programmig for the operator
> - bascially all the the languages for the runtimes
> - also the visual studio code exntsion needs maintenace
>
> Do you copy? Can you help ? Where?
> Please reply.
> Thanks.
>
> --
> Michele Sciabarrà - msciabarra@apache.org - linkedin.com/in/msciab
> Apache OpenServerless committer - reddit.com/r/openserverless
> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk
> <
> https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/>
>
>
>
>

Re: It is time to release and apply for graduation!

Posted by Riccardo La Malfa <ri...@gmail.com>.

Ho,

  

Yeah… I find way more comfortable using the Discord channel as you said
previous la, but I can try to communicare more often via mailing list too at
this point

  

> On 29 Apr 2026, at 23:32, Alessandro <al...@sanino.dev> wrote:  
>  
>

> 
>
> Hello,
>
>  
>
>
> Alessandro here.
>
>  
>
>
> Loud and clear. I agree we must stick more to the mailing list now.
>
>  
>
>
> What are the next steps with biggest priority now?  
>  
>  
>
>
> \----------  
>
>
>  
>
>
>
> ![1767884826087001_170458169.png](cid:0.28869225960.9152755809372337012.19ddb2807c3__inline__img__src)  
>
>
> | |
>
>  **Alessandro Sanino**  
>  
>  
> ---  
>  
> SENIOR MULTI-CLOUD / AI ARCHITECT  
>  
>  
> |
>
> Mobile:  
>
>
> |
>
>  **(+39) 393 559 8693**  
>  
>  
> ---|---  
>  
> Email:  
>
>
> |
>
>  **[alessandro@sanino.dev](mailto:alessandro@sanino.dev)**  
>  
>  
> Website:  
>
>
> |
>
> [alessandro.sanino.dev](https://alessandro.sanino.dev/)  
>  
>  
>  
>
>
> The content of this email is confidential and intended for the recipient
> specified in message only. It is strictly forbidden to share any part of
> this message with any third party, without a written consent of the sender.
> If you received this message by mistake, please reply to this message and
> follow with its deletion, so that we can ensure such a mistake does not
> occur in the future.  
>
>
>  
>
>
> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
> questa.  
>  
>  
> ---  
>  
>  
>
>
>  
>
>
>  
>  \---- Il mer, 29 apr 2026 23:28:32 +0200 **michele@nuvolaris.io** ha
> scritto ----  
>  
>
>

>> Hello everyone, call to action and also call to show you are here and you  
> are following the discussion.  
>  
> Our mentors are concerned there is no activity on the maling list and no  
> attempts has been made to do a release.  
>  
> The project is actually very active, we have important adopters like big  
> cloud providers, defense contractors and government agencites, and  
> countless private companies. And there has been commits as you can see here  
>  
> <https://github.com/apache/openserverless-task/graphs/commit-activity>  
>  
> There are also contributors from different sources. But we have neglected 3  
> important standards for the apache: using the maling list. doing a source  
> release and also respond to security advisories.  
>  
> To be honest those advisories where something I was not aware of, but they  
> are important.  
>  
> The truth is: we communicate in multiple channels, whatapp discord slack  
> linkedin google meet but we do not use the maling list simple  
> because almost all of us are not used to do that.  
>  
> And we did not do a source release because the way we distribute the  
> software works for us, with a cli downloaded that pulls the. tasks and the  
> images on demand from github and docker hub.  
>  
> But since we want to be an apache project this have to change.  
>  
> So now it is time to do a source release and we have to do that using the  
> maling list.  
>  
> To coordinate the release we need a strong technical directions. There has  
> been volunteer but unfortunely they did not make progresses in the attept.  
>  
> The only people who cnl realistically coordinate the release are me,  
> Francesco or Bruno. And both Francesco and Bruno are busy for personal  
> reasons, although they are willing to help. I was very busy as the CEO of  
> Nuvolaris so to do the coordination by myself was not an option, until now.  
>  
> But this now changed: I handed over the role of CEO precisely because I  
> want to focus more on technicalities and now I am going to use the free  
> time to coordinatethe release.  
>  
> And I will do it USING ONLY THE MALING LIST.  
>  
> Let me say it again: no whatapp. no discord. no slack. no google meet. Only  
> this maling list. And expect a lot of messages.  
>  
> So please go on you gmail and change settings to be sure messages from  
> [dev@openserverless.apache.org](mailto:dev@openserverless.apache.org) pops
> up clearly and you can read  
>  
> I contacted all the contributors to ask them to join the list and now I am  
> asking everyone to show you are reading the messages .  
>  
> So please let's start the process of building the source release and lets  
> do it introduciont yourself and the skills you have and we can use.  
>  
> This is the list of what we need:  
>  
> \- shell, python and jascript programming for the task  
> \- go programming for the cli engine  
> \- kubernetes and python programmig for the operator  
> \- bascially all the the languages for the runtimes  
> \- also the visual studio code exntsion needs maintenace  
>  
> Do you copy? Can you help ? Where?  
> Please reply.  
> Thanks.  
>  
> \--  
> Michele Sciabarrà - [msciabarra@apache.org](mailto:msciabarra@apache.org) \-
> linkedin.com/in/msciab  
> Apache OpenServerless committer - reddit.com/r/openserverless  
> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk  
> <<https://www.oreilly.com/library/view/learning-apache-
> openwhisk/9781492046158/>>  
>
>
>  
>

Re: It is time to release and apply for graduation!

Posted by Michele Manzani <mi...@gmail.com>.

Hello everyone,

Let me introduce myself to those who don't know me.  I'm Michele Manzani,
Mick to friends, and I've been working at Nuvolaris for the last 4 months.

I'm ready to support this amazing project and its evolution.

Let me know how I can help.

Regards,
Michele


On Thu, Apr 30, 2026 at 8:37 AM Fabio Ziviello <f....@gmail.com> wrote:

>
>
>
> Fabio Ziviello
>
> On Thu, 30 Apr 2026 at 00:05, Alessandro <al...@sanino.dev> wrote:
>
>>
>>
>> Sure thing. Let me coordinate with Lorenzo then.
>> ----------
>>
>> [image: signatureImage]
>>
>> *Alessandro Sanino*
>>
>> SENIOR MULTI-CLOUD / AI ARCHITECT
>>
>> Mobile:
>>
>> *(+39) 393 559 8693*
>>
>> Email:
>>
>> *alessandro@sanino.dev <al...@sanino.dev>*
>>
>> Website:
>>
>> alessandro.sanino.dev
>>
>> The content of this email is confidential and intended for the recipient
>> specified in message only. It is strictly forbidden to share any part of
>> this message with any third party, without a written consent of the sender.
>> If you received this message by mistake, please reply to this message and
>> follow with its deletion, so that we can ensure such a mistake does not
>> occur in the future.
>>
>>
>>
>> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
>> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
>> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
>> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
>> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
>> questa.
>>
>>
>>
>> ---- Il mer, 29 apr 2026 23:43:40 +0200 * michele@nuvolaris.io
>> <mi...@nuvolaris.io> * ha scritto ----
>>
>>
>> The goal is to be able to do
>>
>> git clone https://github.com/apache/openserverless --recurse-submodules
>> cd opemserverless
>> ./build.sh (to build everything in a local docker images - this is
>> missing)
>> ./bin/ops setup mini (this already works but pulls images from docker
>> hub, not locally)
>> ./test.sh (run the test suite that is now separate)
>>
>> when this works we can think of doing a tarball of everything
>>
>> Lorenzo is already working on compiling the openwhisk image
>> @Alessandro Sanino <al...@sanino.dev>  since you are a go expert,
>> would yuo try to checkout the cli and see if you can compile it ?
>>
>>
>>
>>
>>
>>
>>
>> - update the images of OpenWhisk (and Lorenzo is working on it)
>> - build everything on a local docker from a
>> - find a way to run the tests LOCALLY
>>
>>
>>
>>
>> Michele Sciabarra | CEO
>>
>> m: +44 747 984 8388
>> e:  michele@nuvolaris.io
>> l:   https://linkedin.com/in/msciab
>> Nuvolaris Inc | 1209 Orange Street, 19801
>> <https://www.google.com/maps/search/1209+Orange+Street,+19801+Wilmington+DE+-+US?entry=gmail&source=g>Wilmington
>> DE - US
>> <https://www.google.com/maps/search/1209+Orange+Street,+19801+Wilmington+DE+-+US?entry=gmail&source=g>
>> www.nuvolaris.io linkedin.com/in/msciab
>>
>>
>> On Wed, 29 Apr 2026 at 22:32, Alessandro <al...@sanino.dev> wrote:
>>
>> Hello,
>>
>> Alessandro here.
>>
>> Loud and clear. I agree we must stick more to the mailing list now.
>>
>> What are the next steps with biggest priority now?
>>
>>
>> ----------
>>
>> [image: signatureImage]
>>
>> *Alessandro Sanino*
>>
>> SENIOR MULTI-CLOUD / AI ARCHITECT
>>
>> Mobile:
>>
>> *(+39) 393 559 8693*
>>
>> Email:
>>
>> *alessandro@sanino.dev <al...@sanino.dev>*
>>
>> Website:
>>
>> alessandro.sanino.dev
>>
>> The content of this email is confidential and intended for the recipient
>> specified in message only. It is strictly forbidden to share any part of
>> this message with any third party, without a written consent of the sender.
>> If you received this message by mistake, please reply to this message and
>> follow with its deletion, so that we can ensure such a mistake does not
>> occur in the future.
>>
>>
>>
>> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
>> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
>> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
>> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
>> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
>> questa.
>>
>>
>>
>> ---- Il mer, 29 apr 2026 23:28:32 +0200 * michele@nuvolaris.io
>> <mi...@nuvolaris.io> * ha scritto ----
>>
>> Hello everyone, call to action and also call to show you are here and you
>> are following the discussion.
>>
>> Our mentors are concerned there is no activity on the maling list and no
>> attempts has been made to do a release.
>>
>> The project is actually very active, we have important adopters like big
>> cloud providers, defense contractors and government agencites, and
>> countless private companies. And there has been commits as you can see
>> here
>>
>> https://github.com/apache/openserverless-task/graphs/commit-activity
>>
>> There are also contributors from different sources. But we have neglected
>> 3
>> important standards for the apache: using the maling list. doing a source
>> release and also respond to security advisories.
>>
>> To be honest those advisories where something I was not aware of, but
>> they
>> are important.
>>
>> The truth is: we communicate in multiple channels, whatapp discord slack
>> linkedin google meet but we do not use the maling list simple
>> because almost all of us are not used to do that.
>>
>> And we did not do a source release because the way we distribute the
>> software works for us, with a cli downloaded that pulls the. tasks and
>> the
>> images on demand from github and docker hub.
>>
>> But since we want to be an apache project this have to change.
>>
>> So now it is time to do a source release and we have to do that using the
>> maling list.
>>
>> To coordinate the release we need a strong technical directions. There
>> has
>> been volunteer but unfortunely they did not make progresses in the
>> attept.
>>
>> The only people who cnl realistically coordinate the release are me,
>> Francesco or Bruno. And both Francesco and Bruno are busy for personal
>> reasons, although they are willing to help. I was very busy as the CEO of
>> Nuvolaris so to do the coordination by myself was not an option, until
>> now.
>>
>> But this now changed: I handed over the role of CEO precisely because I
>> want to focus more on technicalities and now I am going to use the free
>> time to coordinatethe release.
>>
>> And I will do it USING ONLY THE MALING LIST.
>>
>> Let me say it again: no whatapp. no discord. no slack. no google meet.
>> Only
>> this maling list. And expect a lot of messages.
>>
>> So please go on you gmail and change settings to be sure messages from
>> dev@openserverless.apache.org pops up clearly and you can read
>>
>> I contacted all the contributors to ask them to join the list and now I
>> am
>> asking everyone to show you are reading the messages .
>>
>> So please let's start the process of building the source release and lets
>> do it introduciont yourself and the skills you have and we can use.
>>
>> This is the list of what we need:
>>
>> - shell, python and jascript programming for the task
>> - go programming for the cli engine
>> - kubernetes and python programmig for the operator
>> - bascially all the the languages for the runtimes
>> - also the visual studio code exntsion needs maintenace
>>
>> Do you copy? Can you help ? Where?
>> Please reply.
>> Thanks.
>>
>> --
>> Michele Sciabarrà - msciabarra@apache.org - linkedin.com/in/msciab
>> Apache OpenServerless committer - reddit.com/r/openserverless
>> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk
>> <
>> https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/>
>>
>>
>>
>>
>>

Re: It is time to release and apply for graduation!

Posted by Riccardo La Malfa <ri...@gmail.com>.

Regarding the wsgi implementation, I am currently waiting for news from
Bruno on his runtimes' update and then I'll update my runtime and make the
pr.
The last runtime update is here:
https://github.com/94lama/openserverless-runtimes/tree/flask

Best,
Riccardo La Malfa

Re: It is time to release and apply for graduation!

Posted by Fabio Ziviello <f....@gmail.com>.

Fabio Ziviello

On Thu, 30 Apr 2026 at 00:05, Alessandro <al...@sanino.dev> wrote:

>
>
> Sure thing. Let me coordinate with Lorenzo then.
> ----------
>
> [image: signatureImage]
>
> *Alessandro Sanino*
>
> SENIOR MULTI-CLOUD / AI ARCHITECT
>
> Mobile:
>
> *(+39) 393 559 8693*
>
> Email:
>
> *alessandro@sanino.dev <al...@sanino.dev>*
>
> Website:
>
> alessandro.sanino.dev
>
> The content of this email is confidential and intended for the recipient
> specified in message only. It is strictly forbidden to share any part of
> this message with any third party, without a written consent of the sender.
> If you received this message by mistake, please reply to this message and
> follow with its deletion, so that we can ensure such a mistake does not
> occur in the future.
>
>
>
> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
> questa.
>
>
>
> ---- Il mer, 29 apr 2026 23:43:40 +0200 * michele@nuvolaris.io
> <mi...@nuvolaris.io> * ha scritto ----
>
>
> The goal is to be able to do
>
> git clone https://github.com/apache/openserverless --recurse-submodules
> cd opemserverless
> ./build.sh (to build everything in a local docker images - this is
> missing)
> ./bin/ops setup mini (this already works but pulls images from docker hub,
> not locally)
> ./test.sh (run the test suite that is now separate)
>
> when this works we can think of doing a tarball of everything
>
> Lorenzo is already working on compiling the openwhisk image
> @Alessandro Sanino <al...@sanino.dev>  since you are a go expert,
> would yuo try to checkout the cli and see if you can compile it ?
>
>
>
>
>
>
>
> - update the images of OpenWhisk (and Lorenzo is working on it)
> - build everything on a local docker from a
> - find a way to run the tests LOCALLY
>
>
>
>
> Michele Sciabarra | CEO
>
> m: +44 747 984 8388
> e:  michele@nuvolaris.io
> l:   https://linkedin.com/in/msciab
> Nuvolaris Inc | 1209 Orange Street, 19801
> <https://www.google.com/maps/search/1209+Orange+Street,+19801+Wilmington+DE+-+US?entry=gmail&source=g>Wilmington
> DE - US
> <https://www.google.com/maps/search/1209+Orange+Street,+19801+Wilmington+DE+-+US?entry=gmail&source=g>
> www.nuvolaris.io linkedin.com/in/msciab
>
>
> On Wed, 29 Apr 2026 at 22:32, Alessandro <al...@sanino.dev> wrote:
>
> Hello,
>
> Alessandro here.
>
> Loud and clear. I agree we must stick more to the mailing list now.
>
> What are the next steps with biggest priority now?
>
>
> ----------
>
> [image: signatureImage]
>
> *Alessandro Sanino*
>
> SENIOR MULTI-CLOUD / AI ARCHITECT
>
> Mobile:
>
> *(+39) 393 559 8693*
>
> Email:
>
> *alessandro@sanino.dev <al...@sanino.dev>*
>
> Website:
>
> alessandro.sanino.dev
>
> The content of this email is confidential and intended for the recipient
> specified in message only. It is strictly forbidden to share any part of
> this message with any third party, without a written consent of the sender.
> If you received this message by mistake, please reply to this message and
> follow with its deletion, so that we can ensure such a mistake does not
> occur in the future.
>
>
>
> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
> questa.
>
>
>
> ---- Il mer, 29 apr 2026 23:28:32 +0200 * michele@nuvolaris.io
> <mi...@nuvolaris.io> * ha scritto ----
>
> Hello everyone, call to action and also call to show you are here and you
> are following the discussion.
>
> Our mentors are concerned there is no activity on the maling list and no
> attempts has been made to do a release.
>
> The project is actually very active, we have important adopters like big
> cloud providers, defense contractors and government agencites, and
> countless private companies. And there has been commits as you can see
> here
>
> https://github.com/apache/openserverless-task/graphs/commit-activity
>
> There are also contributors from different sources. But we have neglected
> 3
> important standards for the apache: using the maling list. doing a source
> release and also respond to security advisories.
>
> To be honest those advisories where something I was not aware of, but they
> are important.
>
> The truth is: we communicate in multiple channels, whatapp discord slack
> linkedin google meet but we do not use the maling list simple
> because almost all of us are not used to do that.
>
> And we did not do a source release because the way we distribute the
> software works for us, with a cli downloaded that pulls the. tasks and the
> images on demand from github and docker hub.
>
> But since we want to be an apache project this have to change.
>
> So now it is time to do a source release and we have to do that using the
> maling list.
>
> To coordinate the release we need a strong technical directions. There has
> been volunteer but unfortunely they did not make progresses in the attept.
>
> The only people who cnl realistically coordinate the release are me,
> Francesco or Bruno. And both Francesco and Bruno are busy for personal
> reasons, although they are willing to help. I was very busy as the CEO of
> Nuvolaris so to do the coordination by myself was not an option, until
> now.
>
> But this now changed: I handed over the role of CEO precisely because I
> want to focus more on technicalities and now I am going to use the free
> time to coordinatethe release.
>
> And I will do it USING ONLY THE MALING LIST.
>
> Let me say it again: no whatapp. no discord. no slack. no google meet.
> Only
> this maling list. And expect a lot of messages.
>
> So please go on you gmail and change settings to be sure messages from
> dev@openserverless.apache.org pops up clearly and you can read
>
> I contacted all the contributors to ask them to join the list and now I am
> asking everyone to show you are reading the messages .
>
> So please let's start the process of building the source release and lets
> do it introduciont yourself and the skills you have and we can use.
>
> This is the list of what we need:
>
> - shell, python and jascript programming for the task
> - go programming for the cli engine
> - kubernetes and python programmig for the operator
> - bascially all the the languages for the runtimes
> - also the visual studio code exntsion needs maintenace
>
> Do you copy? Can you help ? Where?
> Please reply.
> Thanks.
>
> --
> Michele Sciabarrà - msciabarra@apache.org - linkedin.com/in/msciab
> Apache OpenServerless committer - reddit.com/r/openserverless
> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk
> <
> https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/>
>
>
>
>
>

Re: It is time to release and apply for graduation!

Posted by Alessandro <al...@sanino.dev>.

Sure thing. Let me coordinate with Lorenzo then.

----------

Alessandro Sanino

SENIOR MULTI-CLOUD / AI ARCHITECT

Mobile:

(+39) 393 559 8693

Email:

mailto:alessandro@sanino.dev

Website:

https://alessandro.sanino.dev/

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo cortesemente di avvisarmi immediatamente e di distruggere permanentemente l’originale e qualsiasi copia della presente nonché qualsiasi stampa di questa.

---- Il mer, 29 apr 2026 23:43:40 +0200 michele@nuvolaris.io ha scritto ----

The goal is to be able to do

git clone https://github.com/apache/openserverless --recurse-submodules
cd opemserverless
./build.sh (to build everything in a local docker images - this is missing)
./bin/ops setup mini (this already works but pulls images from docker hub, not locally)
./test.sh (run the test suite that is now separate)

when this works we can think of doing a tarball of everything

Lorenzo is already working on compiling the openwhisk image
mailto:alessandro@sanino.dev since you are a go expert, would yuo try to checkout the cli and see if you can compile it ?

- update the images of OpenWhisk (and Lorenzo is working on it)
- build everything on a local docker from a
- find a way to run the tests LOCALLY

Michele Sciabarra | CEO

m: +44 747 984 8388
e: mailto:michele@nuvolaris.io
l: https://linkedin.com/in/msciab
Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US

http://www.nuvolaris.io/
https://linkedin.com/in/msciab

On Wed, 29 Apr 2026 at 22:32, Alessandro < mailto:alessandro@sanino.dev > wrote:

Hello,

Alessandro here.

Loud and clear. I agree we must stick more to the mailing list now.

What are the next steps with biggest priority now?

----------

Alessandro Sanino

SENIOR MULTI-CLOUD / AI ARCHITECT

Mobile:

(+39) 393 559 8693

Email:

mailto:alessandro@sanino.dev

Website:

https://alessandro.sanino.dev/

---- Il mer, 29 apr 2026 23:28:32 +0200 mailto:michele@nuvolaris.io ha scritto ----

Hello everyone, call to action and also call to show you are here and you

are following the discussion.

Our mentors are concerned there is no activity on the maling list and no

attempts has been made to do a release.

The project is actually very active, we have important adopters like big

cloud providers, defense contractors and government agencites, and

countless private companies. And there has been commits as you can see here

https://github.com/apache/openserverless-task/graphs/commit-activity

There are also contributors from different sources. But we have neglected 3

important standards for the apache: using the maling list. doing a source

release and also respond to security advisories.

To be honest those advisories where something I was not aware of, but they

are important.

The truth is: we communicate in multiple channels, whatapp discord slack

linkedin google meet but we do not use the maling list simple

because almost all of us are not used to do that.

And we did not do a source release because the way we distribute the

software works for us, with a cli downloaded that pulls the. tasks and the

images on demand from github and docker hub.

But since we want to be an apache project this have to change.

So now it is time to do a source release and we have to do that using the

maling list.

To coordinate the release we need a strong technical directions. There has

been volunteer but unfortunely they did not make progresses in the attept.

The only people who cnl realistically coordinate the release are me,

Francesco or Bruno. And both Francesco and Bruno are busy for personal

reasons, although they are willing to help. I was very busy as the CEO of

Nuvolaris so to do the coordination by myself was not an option, until now.

But this now changed: I handed over the role of CEO precisely because I

want to focus more on technicalities and now I am going to use the free

time to coordinatethe release.

And I will do it USING ONLY THE MALING LIST.

Let me say it again: no whatapp. no discord. no slack. no google meet. Only

this maling list. And expect a lot of messages.

So please go on you gmail and change settings to be sure messages from

mailto:dev@openserverless.apache.org pops up clearly and you can read

I contacted all the contributors to ask them to join the list and now I am

asking everyone to show you are reading the messages .

So please let's start the process of building the source release and lets

do it introduciont yourself and the skills you have and we can use.

This is the list of what we need:

- shell, python and jascript programming for the task

- go programming for the cli engine

- kubernetes and python programmig for the operator

- bascially all the the languages for the runtimes

- also the visual studio code exntsion needs maintenace

Do you copy? Can you help ? Where?

Please reply.

Thanks.

Michele Sciabarrà - mailto:msciabarra@apache.org - http://linkedin.com/in/msciab

Apache OpenServerless committer - http://reddit.com/r/openserverless

Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk

< https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/ >

Re: It is time to release and apply for graduation!

Posted by Michele Sciabarra <mi...@nuvolaris.io>.

The goal is to be able to do

git clone https://github.com/apache/openserverless --recurse-submodules
cd opemserverless
./build.sh (to build everything in a local docker images - this is missing)
./bin/ops setup mini (this already works but pulls images from docker hub,
not locally)
./test.sh (run the test suite that is now separate)

when this works we can think of doing a tarball of everything

Lorenzo is already working on compiling the openwhisk image
@Alessandro Sanino <al...@sanino.dev>  since you are a go expert,
would yuo try to checkout the cli and see if you can compile it ?







- update the images of OpenWhisk (and Lorenzo is working on it)
- build everything on a local docker from a
- find a way to run the tests LOCALLY




Michele Sciabarra | CEO

m: +44 747 984 8388
e:  michele@nuvolaris.io
l:   https://linkedin.com/in/msciab
Nuvolaris Inc | 1209 Orange Street, 19801Wilmington DE - US
www.nuvolaris.io linkedin.com/in/msciab


On Wed, 29 Apr 2026 at 22:32, Alessandro <al...@sanino.dev> wrote:

> Hello,
>
> Alessandro here.
>
> Loud and clear. I agree we must stick more to the mailing list now.
>
> What are the next steps with biggest priority now?
>
>
> ----------
>
> [image: signatureImage]
>
> *Alessandro Sanino*
>
> SENIOR MULTI-CLOUD / AI ARCHITECT
>
> Mobile:
>
> *(+39) 393 559 8693*
>
> Email:
>
> *alessandro@sanino.dev <al...@sanino.dev>*
>
> Website:
>
> alessandro.sanino.dev
>
> The content of this email is confidential and intended for the recipient
> specified in message only. It is strictly forbidden to share any part of
> this message with any third party, without a written consent of the sender.
> If you received this message by mistake, please reply to this message and
> follow with its deletion, so that we can ensure such a mistake does not
> occur in the future.
>
>
>
> Questa e-mail, nonché qualsiasi file allegato alla presente, è destinata
> esclusivamente ai destinatari indicati in indirizzo o a chi sia stato da
> quelli autorizzato. Se avete ricevuto per errore questa e-mail, vi chiedo
> cortesemente di avvisarmi immediatamente e di distruggere permanentemente
> l’originale e qualsiasi copia della presente nonché qualsiasi stampa di
> questa.
>
>
>
> ---- Il mer, 29 apr 2026 23:28:32 +0200 * michele@nuvolaris.io
> <mi...@nuvolaris.io> * ha scritto ----
>
> Hello everyone, call to action and also call to show you are here and you
> are following the discussion.
>
> Our mentors are concerned there is no activity on the maling list and no
> attempts has been made to do a release.
>
> The project is actually very active, we have important adopters like big
> cloud providers, defense contractors and government agencites, and
> countless private companies. And there has been commits as you can see
> here
>
> https://github.com/apache/openserverless-task/graphs/commit-activity
>
> There are also contributors from different sources. But we have neglected
> 3
> important standards for the apache: using the maling list. doing a source
> release and also respond to security advisories.
>
> To be honest those advisories where something I was not aware of, but they
> are important.
>
> The truth is: we communicate in multiple channels, whatapp discord slack
> linkedin google meet but we do not use the maling list simple
> because almost all of us are not used to do that.
>
> And we did not do a source release because the way we distribute the
> software works for us, with a cli downloaded that pulls the. tasks and the
> images on demand from github and docker hub.
>
> But since we want to be an apache project this have to change.
>
> So now it is time to do a source release and we have to do that using the
> maling list.
>
> To coordinate the release we need a strong technical directions. There has
> been volunteer but unfortunely they did not make progresses in the attept.
>
> The only people who cnl realistically coordinate the release are me,
> Francesco or Bruno. And both Francesco and Bruno are busy for personal
> reasons, although they are willing to help. I was very busy as the CEO of
> Nuvolaris so to do the coordination by myself was not an option, until
> now.
>
> But this now changed: I handed over the role of CEO precisely because I
> want to focus more on technicalities and now I am going to use the free
> time to coordinatethe release.
>
> And I will do it USING ONLY THE MALING LIST.
>
> Let me say it again: no whatapp. no discord. no slack. no google meet.
> Only
> this maling list. And expect a lot of messages.
>
> So please go on you gmail and change settings to be sure messages from
> dev@openserverless.apache.org pops up clearly and you can read
>
> I contacted all the contributors to ask them to join the list and now I am
> asking everyone to show you are reading the messages .
>
> So please let's start the process of building the source release and lets
> do it introduciont yourself and the skills you have and we can use.
>
> This is the list of what we need:
>
> - shell, python and jascript programming for the task
> - go programming for the cli engine
> - kubernetes and python programmig for the operator
> - bascially all the the languages for the runtimes
> - also the visual studio code exntsion needs maintenace
>
> Do you copy? Can you help ? Where?
> Please reply.
> Thanks.
>
> --
> Michele Sciabarrà - msciabarra@apache.org - linkedin.com/in/msciab
> Apache OpenServerless committer - reddit.com/r/openserverless
> Apache OpenWhisk PMC member - Author Learning Apache OpenWhisk
> <
> https://www.oreilly.com/library/view/learning-apache-openwhisk/9781492046158/>
>
>
>
>

R: It is time to release and apply for graduation!

Posted by Alessandro <al...@sanino.dev>.

Hello,

Alessandro here.

Loud and clear. I agree we must stick more to the mailing list now.

What are the next steps with biggest priority now?

----------

Alessandro Sanino

SENIOR MULTI-CLOUD / AI ARCHITECT

Mobile:

(+39) 393 559 8693

Email:

mailto:alessandro@sanino.dev

Website:

https://alessandro.sanino.dev/

---- Il mer, 29 apr 2026 23:28:32 +0200 michele@nuvolaris.io ha scritto ----