Hello Frederic,
Thanks for your response, really appreciate it.
We could consider to get involved, when you have time with no hurry we can get in contact and decide how to proceed.
Regards
Davide
From: Frédéric Desbiens <frederic.desbiens@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, July 5, 2024 4:54 PM
To: ThreadX community discussions <threadx@xxxxxxxxxxx>
Cc: Davide Dal Frà <d.dalfra@xxxxxxxx>
Subject: Re: [threadx] [threadx-dev] New ThreadX mailing list for end-user questions
Hi, Henrik and Davide.
Thank you for your candid emails. I understand where you are coming from. We obviously underestimated the complexity of the transition and, as we are implementing all the required processes, did not communicate enough with the community. However, the Foundation
is firmly committed to ThreadX and to maintaining its safety certifications.
The ThreadX open source project is fully operational, and its committers are working on features and improvements. They meet every week and gradually learn how to function as an open source community under the guidance of Foundation staff.
You can expect them to communicate soon about what they are working on. In particular, a very active committer from ST Micro is working on platform support improvements. We also discussed how to tackle the accumulated issues and pull requests on our major
repositories. So, from a code perspective, we are getting there.
Of course, ThreadX will only progress with the contributions of its community. There is no single company in charge like in the past. Contributions of patches, improvements, and new features are all welcome. If ThreadX is a strategic part of your software stack,
you should consider getting involved. I can tell you how.
Where we are late is the safety side of things. TheadX is a pioneer at the Foundation as the first safety-certified project. Naturally, this means we need to deal with unanticipated issues along the way. We have made good progress in the last few weeks. However,
we can only share more details once we can deliver on our commitments.
One of the questions you raised concerns funding. We are a non-profit, so our intent is to fund future ThreadX safety certifications by selling access to our safety documentation. This, of course, involves liability management. The Foundation is known for its
strong intellectual property policies. Adopters of Eclipse technologies can leverage them with the assurance that IP due diligence has been performed on the code and its dependencies. We bring the same mindset to safety certifications. This means we need robust
legal agreements that will protect ThreadX adopters while ensuring we properly manage our legal liability. Getting those things right takes time, as anything related to laws and regulations.
Naturally, if your projects are highly time-sensitive, nothing prevents you from picking up the code today and performing the full safety certification yourself. Several of our members can assist in that process, having certified ThreadX-powered
products in the past. You can see the list here: https://threadx.io/services-and-support.
Eclipse ThreadX stands as the sole open source RTOS certified for safety applications. As a one-of-a-kind initiative, it is currently experiencing growing pains. With your support and patience, I am convinced we can overcome them.
Best Regards,
Hello Folks,
I fully agree with Henrik.
From our side we decided to invest time and money developing new products with ThreadX. Of course the USBs(device/host) stack , FileX and NetX was one of the major decision that pushed us to jump from FreeRTOS to AzureRTOS.
Stability of such a professional product is for sure a big pro compared to what was available before (FatFS, FreeRTOS , LwIP & so on).
Despite that we bought o.s. profiling tools (Tracealyzer) believing that also silicon manufacturers will stay on AzureRTOS/ThreadX.
I recently feel that ST seems to be jumping back on RTOS, while others (NXP, Renesas) seems to stay on the original decision of staying with ThreadX.
For sure a prompt response from the foundation , showing up what will be the direction of this project will for sure help everyone in taking right decisions.
Regards
Davide
-----Original Message-----
From: threadx <threadx-bounces@xxxxxxxxxxx> On Behalf Of hmnews--- via threadx
Sent: Friday, July 5, 2024 12:20 PM
To: Frédéric Desbiens via threadx <threadx@xxxxxxxxxxx>
Cc: hmnews@xxxxxxxxxxx
Subject: Re: [threadx] [threadx-dev] New ThreadX mailing list for end-user questions
Hi Frédéric,
The announcement that Microsoft withdraws from ThreadX/NetXDuo was made last year.
Since then I patiently was waiting to get some updates how the whole project will move forward and still nothing concrete and now we have to wait again months to hear what the plan is?
By that time more and more users will have made the decision to abandon the platform due to the uncertainty.
May I suggest to provide more certainty to the present user base how future development is organized and in particular how it will be funded.
Regards,
Henrik
Frédéric Desbiens via threadx wrote on 4/07/2024 7:12 AM:
> Hi Naresh.
>
> There are no ThreadX community meetings scheduled for non-members at
> this time. Our current focus is to complete ThreadX's transition to a
> community-supported open source ecosystem. This includes setting up
> the financing and processes required to support safety certifications
> in the future.
>
> The project's committers are currently working on small additions and
> changes to the codebase. They will eventually share details about
> their work on the threadx-dev mailing list.
>
> We will have plenty of things to announce and share with the ThreadX
> community in the upcoming months. I plan to organise a first virtual
> ThreadX community meeting that will be open to all later in the year.
> Details will be shared on this mailing list.
>
> Best Regards,
>
> *Frédéric DESBIENS*
>
> *Senior Manager — Embedded and IoT | **Eclipse Foundation*
>
> Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx
> <mailto:fdesbiens@xxxxxxxxxxxxxxxxxxxxx>
>
>
>
>
> On Tue, 2 Jul 2024 at 07:54, Ravuri, Naresh <Naresh.Ravuri@xxxxxxxxx
> <mailto:Naresh.Ravuri@xxxxxxxxx>> wrote:
>
> Hello,____
>
> __ __
>
> Any ThreadX WG meetings scheduled?____
>
> __ __
>
> __ __
>
> __ __
>
> __ __
>
> Thanks____
>
> Naresh Ravuri____
>
> Senior Manager- Software____
>
> __ __
>
> *MAGNA ELECTRONICS____*
>
> 30020 Cabot Drive ____
>
> Novi, Michigan 48377 ____
>
> __ __
>
> __ __
>
> __ __
>
> *From:*threadx-dev <threadx-dev-bounces@xxxxxxxxxxx
> <mailto:threadx-dev-bounces@xxxxxxxxxxx>> *On Behalf Of *Frédéric
> Desbiens via threadx-dev
> *Sent:* Thursday, June 13, 2024 10:49 AM
> *To:* ThreadX community discussions <threadx@xxxxxxxxxxx
> <mailto:threadx@xxxxxxxxxxx>>;
threadx-dev@xxxxxxxxxxx
> <mailto:threadx-dev@xxxxxxxxxxx>
> *Cc:* Frédéric Desbiens <frederic.desbiens@xxxxxxxxxxxxxxxxxxxxxx
> <mailto:frederic.desbiens@xxxxxxxxxxxxxxxxxxxxxx>>
> *Subject:* [threadx-dev] New ThreadX mailing list for end-user
> questions____
>
> __ __
>
> WARNING: This e-mail originated from outside of Magna. Be cautious
> with links, attachments and QR codes.____
>
>
> ----------------------------------------------------------------------
> --
>
> Hi everyone.
>
> The ThreadX developer team asked me to create a new mailing list to
> handle questions from end-users. So, if you are building devices or
> applications that leverage ThreadX and have questions, please send
> them to the threadx-users mailing list.
>
> You can subscribe to the list here:
> *https://accounts.eclipse.org/mailing-list/threadx-users*
>
> So, to summarise:____
>
> * *threadx@xxxxxxxxxxx <mailto:threadx@xxxxxxxxxxx> *is the
> general community mailing list. You will receive release
> announcements, community news, community meeting invites, and
> more on it. You can ask non-technical questions about the
> ThreadX open source project and**the ThreadX special interest
> group there.____
> * *threadx-dev@xxxxxxxxxxx <mailto:threadx-dev@xxxxxxxxxxx>* is
> the ThreadX developer mailing list. The project contributors and
> committers of ThreadX will use it to collaborate and discuss
> technical matters in an open setting. You can discuss pull
> requests and such matters there. ____
> * *threadx-users@xxxxxxxxxxx
> <mailto:threadx-users@xxxxxxxxxxx>* is the list of ThreadX
> end-users. If you have technical questions about ThreadX and its
> subcomponents (FileX, GUIX, NetX Duo, USBX, etc.), you can use
> his one.____
>
> If you are unsure where to send your email, feel free to ask me
> ahead of time.
>
> Best Regards,____
>
>
> ____
>
> *Frédéric DESBIENS*____
>
> *Senior Manager — Embedded and IoT | **Eclipse Foundation*____
>
> Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx
> <mailto:fdesbiens@xxxxxxxxxxxxxxxxxxxxx>____
>
> Image removed by sender.____
>
>
>
> _______________________________________________
> threadx mailing list
> threadx@xxxxxxxxxxx
> To unsubscribe from this list, visit
https://accounts.eclipse.org
>
_______________________________________________
threadx mailing list
threadx@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
_______________________________________________
threadx mailing list
threadx@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
|
