Hi Nathan, If that is the case, I suggest we don't accept this option because we know the consequences.
Since this is an open-source project, if companies want to use their HAL internally (behind closed doors), they should maintain the entire fork themselves. This way, users won't complain to us about not getting their code submitted to the vendor HAL and the vendor never merges it. BR, Alan On Wed, Oct 21, 2026 at 11:24 AM Nathan Hartman <[email protected]> wrote: > On Wed, Oct 21, 2026 at 8:35 AM Alan C. Assis <[email protected]> wrote: > (snip) > > > My suggestion is: HALs that can't be hosted at ASF should be hosted at > > github.com/NuttX/HALS/vendor-hal-name (or any other github account under > > the control of the NuttX community). > > > I thought Justin just explained: > > On Tue, Oct 20, 2026 at 8:24 PM Justin Mclean <[email protected]> wrote: > (snip) > > > github.com/NuttX is not controlled by the ASF, so it is not “under our > > control”. Code the project maintains must be housed in ASF repositories, > > see https://infra.apache.org/project-repo-policy.html. That rules out > > NuttX committers maintaining vendor HALs there. > > > If third parties want to create repositories of things that can work with > NuttX, that's their choice and that's great, but it can't be considered > part of *this* project and it can't be presented as "NuttX" or > github.com/NuttX. As Justin explained, when *this* project hosts > something, > it needs to be hosted at the ASF, in ASF repositories. >
