Hi Jehudi,
Here are my thoughts on the questions you raised:
1. What are the advantages and consequences of changing the location?
It will allow people with write access to NuttX to review and approve
PRs, removing the pressure from a few individuals and the vendor's internal
queue.
2. What is the goal of changing the location: closer to NuttX and it's
style?
In addition to the point above, the goal is to prevent NuttX from
becoming increasingly dependent on external agents, especially vendors.
3. Who will be responsible?
The community, meaning anyone who is interested in contributing.
4. Who will write the code?
The community, meaning anyone who is interested in contributing.
5. Who will maintain the code?
The community, meaning anyone who is interested in contributing.
6. Who will ensure that newer devices are supported?
The community, meaning anyone who is interested in contributing.
Best regards,
Felipe Moura de Oliveira
Em sex., 14 de ago. de 2026 às 12:44, Laczen JMS <[email protected]>
escreveu:
> Hi Felipe,
>
> Hosting the repository like zephyr style would just mean moving it
> under nuttx but leaving the merge rights to people from espressif.
> They understand how this repository is updated and what the work is
> when changes are applied. I wouldn't mind this at all, but I don't see
> any advantages. In zephyr the repo is there to ensure that whatever
> version of zephyr is checked-out it has the correct library, in NuttX
> this is achieved in a different way with less work by updating the
> commit-sha of the repository.
>
> Please read the statement from espressif carefully: when the comunity
> would decide (according to community rules) that the esp_hal_3rdparty
> is to be moved under nuttx (and possibly the merging rights would be
> changed) espressif will evaluate whether contribution is feasible.
> This could lead to the decision that contribution is no longer
> feasible, leaving NuttX behind with less support. Up to now espressif
> has reviewing and
> creating PR's for NuttX because they understand how the interaction
> with esp_hal_3rdparty is happening, expecting espressif to do the same
> for a library that is handled by NuttX could be wishfull thinking.
>
> I would conclude with the following questions:
>
> 1. What are the advantages and consequences of changing the location?
> 2. What is the goal of changing the location: closer to NuttX and it's
> style?
> 3. Who will be responsible?
> 4. Who will write the code?
> 5. Who will maintain the code?
> 6. Who will ensure that newer devices are supported?
>
> If any of these questions has an unclear answer it is better too leave
> it as is and embrace the work that espressif is doing for NuttX (both
> in PR and publicity on their blog).
>
> Kind regards,
>
> Jehudi
>
>
> Op vr 14 aug 2026 om 14:56 schreef Felipe Moura Oliveira <
> [email protected]>:
>
> >
> > Hi Laczen,
> >
> > Following our last discussion, and given Espressif's statement that they
> > will conform to community rules and are waiting for the community to
> decide
> > first, are you now more comfortable with hosting the repository like
> Zephyr
> > style?
> >
> > Is anyone else concerned about this?
> >
> > Em sex., 14 de ago. de 2026 às 09:01, Tiago Medicci Serrano <
> > [email protected]> escreveu:
> >
> > > Hi Felipe,
> > >
> > > It may have been lost in this huge thread, but the official position I
> have
> > > is the one that I already sent to the list:
> > >
> > > 1) Espressif always said it would conform to community rules; hence,
> why we
> > > > have been absent. The community must decide first, and then we can
> see
> > > > whether the contribution is feasible.
> > > > 2) We do not block contributions, and we never saw ourselves as
> 'owning'
> > > > Espressif support in NuttX. We do have opinions, and we do try to
> > > optimize,
> > > > and we do listen to others. We actually expect more people willing to
> > > help.
> > > > 3) So far, the discussed options were:
> > >
> > >
> > > -
> > >
> > > Total AI rewrite (I assume at the register level).
> > >
> > > -
> > >
> > > Fork, taking it from there - maybe going Zephyr style.
> > >
> > > -
> > >
> > > Replacing HAL slowly, piece by piece.
> > >
> > >
> > >
> > > Best regards,
> > >
> > >
> > > Em qua., 12 de ago. de 2026 às 08:10, Felipe Moura Oliveira <
> > > [email protected]> escreveu:
> > >
> > > > Hi Tiago,
> > > >
> > > > Do you have any feedback from the Espressif team regarding this
> thread?
> > > > Could you check with your team if we could maintain the esp-hal
> under the
> > > > NuttX GitHub organization? This way, we would be able to add more
> > > reviewers
> > > > to help with the process.
> > > >
> > > > Best,
> > > >
> > > > Em sáb., 8 de ago. de 2026 às 08:33, Alan C. Assis <
> [email protected]>
> > > > escreveu:
> > > >
> > > > > Exactly!
> > > > >
> > > > > And for Zephyr the HAL for ESP32 chips already existed before
> Espressif
> > > > > started contributing to it.
> > > > >
> > > > > NuttX also had a native port before Espressif started contributing.
> > > > >
> > > > > When ESP32 chip was created, some engineers from Espressif was
> willing
> > > to
> > > > > use NuttX instead of FreeRTOS and sent some boards to Greg. He did
> the
> > > > > basic port, but because their internal FreeRTOS port was more
> advanced,
> > > > > they decided to keep using it.
> > > > >
> > > > > BR,
> > > > >
> > > > > Alan
> > > > >
> > > > > On Saturday, August 8, 2026, Laczen JMS <[email protected]>
> wrote:
> > > > >
> > > > > > Hi Felipe,
> > > > > >
> > > > > > Indeed, just like your PR was committed (merged) into
> > > esphal_3rdparty.
> > > > > The
> > > > > > hal_espressif for zephyr is maintained by espressif. The only
> > > > difference
> > > > > > between NuttX and zephyr is where it is located, not who
> maintains
> > > it.
> > > > > >
> > > > > > Kind regards,
> > > > > >
> > > > > > Jehudi
> > > > > >
> > > > > > On Sat, Aug 8, 2026, 09:31 Felipe Moura Oliveira <
> > > [email protected]>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Laczen,
> > > > > > >
> > > > > > > I think you might be confusing the author with the committer.
> > > > > > >
> > > > > > > The change was indeed committed by someone from Espressif who
> has
> > > > write
> > > > > > > access to the repository, but the actual author of the code
> was an
> > > > > > external
> > > > > > > contributor using a @gmail
> > > > > > >
> > > > > > >
> > > > > > > *--Felipe Moura de Oliveira*
> > > > > > > Linkedin <https://www.linkedin.com/in/felipe-oliveira-75a651a0
> >
> > > > > > >
> > > > > > > On Sat, 8 Aug 2026 at 02:31 Laczen JMS <[email protected]>
> > > wrote:
> > > > > > >
> > > > > > > > Alan,
> > > > > > > >
> > > > > > > > That person is from espressif, and the commit of your
> previous
> > > > > > reference
> > > > > > > > was also done by someone from espressif.
> > > > > > > >
> > > > > > > > Kind regards,
> > > > > > > >
> > > > > > > > Jehudi
> > > > > > > >
> > > > > > > > On Fri, Aug 7, 2026, 22:51 Alan C. Assis <[email protected]>
> > > > wrote:
> > > > > > > >
> > > > > > > > > Ok, so this one the also the maintainer of something else
> and
> > > > this
> > > > > is
> > > > > > > why
> > > > > > > > > is has a commit there:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > https://github.com/zephyrproject-rtos/hal_espressif/commit/
> > > > > > 34795d7847426426c618002789af2667cc262f6d
> > > > > > > > >
> > > > > > > > > There are many commits from people outside Espressif, what
> you
> > > > said
> > > > > > is
> > > > > > > > (to
> > > > > > > > > avoid saying I'm accusing you) "not accurate".
> > > > > > > > >
> > > > > > > > > BR,
> > > > > > > > >
> > > > > > > > > Alan
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > *--Felipe Moura de Oliveira*
> > > > Linkedin <https://www.linkedin.com/in/felipe-oliveira-75a651a0>
> > > >
> > >
> >
> >
> > --
> >
> > *--Felipe Moura de Oliveira*
> > Linkedin <https://www.linkedin.com/in/felipe-oliveira-75a651a0>
>
--
*--Felipe Moura de Oliveira*
Linkedin <https://www.linkedin.com/in/felipe-oliveira-75a651a0>
