Hi,
may I ask for repository under https://gitlab.com/CentOS/automotive/rpms to
be able to build oci-delta package for Automotive SIG distribution?
oci-delta package is developed in https://github.com/containers/oci-delta
so the requested repo will be used just to build RPM packages.
Thanks,
Martin
--
Martin Perina
Principal Software Engineer, Red Hat In-Vehicle Operating System
Red Hat Czech s.r.o.
While I agree, I would also say that "tangibly" is open to interpretation.
"used normally" in this case really means "can it be built into a
reasonable SDV architecture", which is mostly in the domain of automotive
manufacturers and suppliers rather than individual enthusiasts. AutoSD's
prevalence in SOAFEE and Eclipse SDV is definitely tangible in community
terms, but you cant really put your hands on it or make smoke come out. For
the latter, a larger community effort would be necessary. That said, if
someone in the community wants to use it for something fun, I'd be glad to
help hunt for resources to support such an effort.
Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com
Distinguished Community Architect
Automotive, Edge, & Hardware Enablement Communities
Red Hat Open Source & AI Program Office
Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9
On Tue, May 26, 2026 at 11:07 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
> On Tue, May 26, 2026 at 10:30 AM Jeffrey Osier-Mixon <jefro(a)redhat.com>
> wrote:
> >
> > Of course. In addition to AutoSD being used in several other open source
> communities (Eclipse SDV, SOAFEE, Autoware) it is of strong interest to
> other transportation entities - think trains, farming equipment - as well
> as robotics applications. To my knowledge no one has deployed it on an RC
> car but there is no reason not to. We had some discussions internally a few
> years ago about f1tenth. It would have to be a community effort, though.
> >
>
> As long as there's nothing people can tangibly use it with, it's going
> to be hard to attract and retain enthusiast contributors. Do you have
> anything you can show off so people can actively work with it in a
> meaningfully similar way to how it would be used normally?
>
>
>
> --
> 真実はいつも一つ!/ Always, there's only one truth!
>
>
Of course. In addition to AutoSD being used in several other open source
communities (Eclipse SDV, SOAFEE, Autoware) it is of strong interest to
other transportation entities - think trains, farming equipment - as well
as robotics applications. To my knowledge no one has deployed it on an RC
car but there is no reason not to. We had some discussions internally a few
years ago about f1tenth. It would have to be a community effort, though.
Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com
Distinguished Community Architect
Automotive, Edge, & Hardware Enablement Communities
Red Hat Open Source & AI Program Office
Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9
On Tue, May 26, 2026 at 10:20 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
> On Tue, May 26, 2026 at 9:46 AM Jeffrey Osier-Mixon <jefro(a)redhat.com>
> wrote:
> >
> > Sounds good, thanks, we can definitely use a meeting room.
> >
> > I would call this less a regression and more a response to the
> community's expressed preference. Meeting attendance has declined
> significantly - we aren't having those discussions in the automotive SIG,
> which we started before things like Eclipse SDV existed. I would love to
> reel them back in. One reason we wanted to move this meeting to Matrix is
> to encourage further communication, as many people have conflicts for a
> physical meeting who would otherwise be able to attend one on chat. Also
> willing to move the time around, but every time is bad for someone.
> >
> > In regard to the other questions about where people are talking and
> where we should introduce AutoSD, let's cover that in next week's meeting :)
> >
>
> Is there yet a way for people to do something with AutoSD that doesn't
> involve being an automaker? Like affordable RC cars or something like
> that? It's rather hard to hold a community together that can't do
> anything...
>
>
>
> --
> 真実はいつも一つ!/ Always, there's only one truth!
>
>
Sounds good, thanks, we can definitely use a meeting room.
I would call this less a regression and more a response to the community's
expressed preference. Meeting attendance has declined significantly - we
aren't having those discussions in the automotive SIG, which we started
before things like Eclipse SDV existed. I would love to reel them back in.
One reason we wanted to move this meeting to Matrix is to encourage further
communication, as many people have conflicts for a physical meeting who
would otherwise be able to attend one on chat. Also willing to move the
time around, but every time is bad for someone.
In regard to the other questions about where people are talking and where
we should introduce AutoSD, let's cover that in next week's meeting :)
Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com
Distinguished Community Architect
Automotive, Edge, & Hardware Enablement Communities
Red Hat Open Source & AI Program Office
Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9
On Tue, May 26, 2026 at 9:31 AM Jeff Ligon via devel <devel(a)lists.centos.org>
wrote:
>
>
>
> On May 26, 2026 at 9:22:52 AM, Neal Gompa (ngompa13(a)gmail.com) wrote:
>
> On Tue, May 26, 2026 at 9:16 AM Jeffrey Osier-Mixon via devel
> <devel(a)lists.centos.org> wrote:
> >
> > Hi folks - we are moving the CentOS Automotive SIG meeting to Matrix
> chat going forward. Currently it will be at the same time - first
> Wednesdays of each month at 1400 UTC = 10:00am EDT, 16:00 CEST. The
> difference is that instead of a call, the meeting will be held on our
> Matrix channel at
> >
> >
> https://app.element.io/?updated=1.11.3#/room/#centos-automotive-sig:fedorap…
> >
> > I'll change the meeting invite today. If you have any trouble reaching
> the channel or need any help, please reach out to myself or Leo.
> >
>
> Could you please use one of the meeting rooms instead? That way
> there's the ability to leverage the meeting bot and logging in
> meetbot.fedoraproject.org.
>
> I dislike this move as I see Matrix as an outdated communication platform
> that just keeps the same people talking to the same people who are already
> there.
>
> Where is the Automotive Open source community talking? where are the
> people who don't know Linux that we want to introduce to AutoSD so that we
> can make a bigger impact.
>
> Going to where we already are feels like a regression. Could be worse.
>
> But I'll see you there since i'm there anyways. As Neil says,
> fedora-meeting-1
>
> -Jeff
>
>
>
> --
> 真実はいつも一つ!/ Always, there's only one truth!
> _______________________________________________
> devel mailing list -- devel(a)lists.centos.org
> To unsubscribe send an email to devel-leave(a)lists.centos.org
>
> _______________________________________________
> devel mailing list -- devel(a)lists.centos.org
> To unsubscribe send an email to devel-leave(a)lists.centos.org
>
Hi folks - we are moving the CentOS Automotive SIG meeting to Matrix chat
going forward. Currently it will be at the same time - first Wednesdays of
each month at 1400 UTC = 10:00am EDT, 16:00 CEST. The difference is that
instead of a call, the meeting will be held on our Matrix channel at
https://app.element.io/?updated=1.11.3#/room/#centos-automotive-sig:fedorap…
I'll change the meeting invite today. If you have any trouble reaching the
channel or need any help, please reach out to myself or Leo.
best,
Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com
Distinguished Community Architect
Automotive, Edge, & Hardware Enablement Communities
Red Hat Open Source & AI Program Office
Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9
Hi everyone,
Following the enablement of the NXP board (S32G/S32N), we request the
creation of new repositories for the NXP-specific kernel extra
modules. These modules are essential for our hardware enablement
within the Automotive SIG ecosystem.
Please create the following repositories:
Source Repository:
https://gitlab.com/CentOS/automotive/src/kernel-ivos-nxp-extra-modules
These modules provide the necessary drivers and out-of-tree
enhancements for NXP hardware compatibility within the IVOS
(In-Vehicle Operating System) environment.
Best regards,
Enric
Hi all - Leo will be running this month's call on Weds, and one thing we
were just discussing is moving the monthly meeting to Matrix, as office
hours starting in June. This is in line with how some other SIGs operate in
CentOS and Fedora, and we feel it would make the meeting more accessible.
If you have any thoughts on this, positive or negative, please discuss on
this thread.
thanks
Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com
Distinguished Community Architect
Automotive, Edge, & Hardware Enablement Communities
Red Hat Open Source & AI Program Office
Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9
Hi everyone,
I would like to move the autopack project (https://gitlab.com/mkemel/autopack) to the automotive-sig accounts. Autopack automates the release-to-CBS pipeline and is already used by automotive-image-builder and fusa-gcc-plugin.
I would need the following repositories to be created:
- https://gitlab.com/CentOS/automotive/src/autopack
- https://quay.io/repository/centos-sig-automotive/autopack
Currently, autopack uses GitLab project tokens to create releases and propose MRs to distgit repos. This works, but for scalability it would be better to either use a single group token for all projects under https://gitlab.com/CentOS/automotive, or have a bot user that can be given permissions to specific projects. Which approach would be preferred?
For CBS builds, I currently use my personal CentOS certificate. It would be better to have a dedicated bot account with permissions to run CBS builds for automotive packages. What would be the process to set that up?
Thanks,
Mark