Hi Michele, thanks for the update, and sounds good, count me in!

​

Sent with Notion Mail <https://www.notion.so/product/mail>

On Wed, 29 Apr 2026 21:28:59 GMT Michele Sciabarra <[email protected]>
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
​[email protected] 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à - [email protected] - 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/>

​

Reply via email to