►
From YouTube: CentOS Automotive SIG meeting - 2022-03-02
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
welcome
everyone
to
the
centos
automotive
sig
meeting.
As
we
know,
this
is
a
special
interest
group
of
within
centos,
specifically
for
automotive.
We
meet
about
once
a
month
in
the
past
over
fall.
We
were
also
meeting
in
an
alternate
two-week
time
frame
for
informal
office
hours,
and
we
haven't
kicked
that
off
yet
this
year.
A
One
of
the
things
I'd
like
to
talk
about
today
is
whether
that
would
be
of
interest
to
go
ahead
and
get
that
started
again
and
in
the
meantime,
we
just
kind
of
roll
on
through
the
big
thing
today
and
most
of
these
meetings,
honestly
is
the
technical
status
update,
for
which
I
will
probably
hand
most
of
it
off
to
pierre,
and
then
we
can
go
through
some
administrative
stuff
after
that,
to
kind
of
you
know,
ease
everybody
down
from
the
excitement
of
the
technical
status.
A
I
do
want
to
go
over
our
goals
again
for
2022,
just
to
make
sure
that
we
are
all
in
sync
on
that
and
to
talk
about
the
future
meeting
schedule.
One
of
the
things
that
always
comes
up
about
this
meeting
and
every
meeting
is
that
it's
impossible
to
find
a
meeting
schedule
that
fits
everybody's
needs.
This
one,
this
time
frame
is
not
terrible
for
the
us.
It
tends
to
be
pretty
good
for
europe
as
well.
A
A
One
of
the
things
we
try
well
we'll
go
through
it
once
we
get
down
there.
Let's
see
I
tend
to
dive
into
the
administrative
stuff
first,
but
I
think
that
everybody's
really
more
interested
in
the
technical
status
update
and
the
the
auto
sd
distro
and
how
all
that
works.
D
C
Work
on
the
on
the
red
side,
so
the
way
the
way
well
is
developed
is
we
have.
We
have
something
called
sensor
stream
that
is
just
ahead
of
offrail
and
that's
where
basically,
all
of
red
hat's
developers
are
working.
You
know
unless
everything,
that's
private,
so
embargoes
or
cvs.
Those
will
not
be
working
on
central
stream,
but
everything
all
the
development
of
well
is
currently
public
and
is
available
via
the
what
we
call
santa
stream.
C
So
center
stream
is
a
product
of
the
santos
community
and
red
hat
and
and
everything
that
is
inside
the
stream
is
meant
to
be
on
rel.
You
don't
necessarily
know
which
version
of
well
it
will
land,
but
the
idea
is
that
everything
inside
the
stream
will
be
in
real.
C
C
C
It's
not
something
that
will
learn
in
rel,
but
if
you
want
to
have
a
newer
systemd
on
your
kernel
using
the
center
stream
for
the
for
the
rest
of
your
infrastructure,
that's
something
that
type
of
scale
can
provide
you,
and
this
is
a
very
powerful
model,
because
we
have
we
have
a
communi.
We
have
a
community
of
people
that
are
interesting
to
build
on
the
top
of
the
product.
C
We
have
a
public
intervention
in
development
version
of
the
product
that
people
can
leverage
and
access,
and
then
we
have
the
product
with
all
the
added
value
that
that
provides
in
it.
So
the
idea
is
to
reuse
that
model
for
the
automotive,
offering
we'll
have
the
redating
vehicle
os
operating
system.
C
That
is
the
product
with
all
the
the
added
value
that
roulette
provides,
but
we'll
have
also
a
public
in
development
version
of
this
product
and
that's
the
automotive
stream
distribution
and
behind
next
to
that
we'll
have
the
automotive
sig,
which,
which
is
meant
to
provide
added
value
or
to
enhance
to
add
more
capabilities
to
what
the
the
you
know
what
auto
sd
has
today.
So
the
id
is
like,
if
you
you
know,
if
we
want
to
do
a
hardware
environment,
that's
a
place
where
the
six
can
do.
C
If
you
want
to
experiment
on
you
know
a
new
version
of
systemd,
a
new
version
of
a
gcc
compiler
flag.
These
are
things
that
the
sig
can
work
can
provide,
can
help
with
and
that's
a
place
where
we
as
a
community
can
experiment
on
everything
we
want
to
do,
based
on
using
auto
sds
database
and
just
diverging
from
a
touristy
where
the
community
sees
interesting.
C
That
could
be
adding
new
packages
that
are
compatible
with
auto
sd.
That
can
be,
you
know
any
of
the
idea
of
what
the
company
wants
to
brings
every
of
the
idea.
What
the
sig
wants
to
be
wants
to
be
doing,
and
next
to
that
we
love
the
automating
stream
distribution,
which
will
always
be
you
know
it's
going
to
be
based
on
center
stream,
because
most
of
the
the
the
red
hats
in
vehicle
operating
system
is
going
to
be
based
on
rail.
C
C
Okay,
thank
you.
The
next
slide
is
basically,
if
we
take
a
step
back
on
the.
C
Of
of
how
it
works
so
we'll
have
to
open
source
the
the
entire
flow
works
from
you
know
the
open
source
project
that
exists
out
there
to
how
they
work,
how
they
land
into
well.
D
C
B
C
Id
it
is
basically
about
three
years
ahead
of
well.
So
if
you
work
on
it
today,
you
have
an
idea
of
what
will
be
in
real.
You
know
three
years
from
now,
then
there
is
a.
There
is
a
small
project,
part
of
the
federal
project
that
is
called
eln,
which
does
not
stand
for
enterprise
linux
next
and
it's
meant
to
basically
every
time
there
is
a
change
made
in
federal
to
something
that
is
part
of
well.
C
We
rebuild
that
change
into
the
into
the
rail
build
route,
and
that
gives
that
gives
redhat
an
id
or
that
gives
the
community
an
idea
about.
If,
if
we,
if
rail
was
to
branch
off
federer
today,
if
the
next
major
version
of
rail
was
to
branch
off
era
today
in
which
state
will
it
be,
do
we
have
to
recompile
the
entire
world?
Do
we
have
to
to
fix
everything
or
is?
C
Is
it
you
know
in
a
fine
state,
and
we
have
to
polish
around
the
angles,
but
most
of
the
work
is
done
so
this
gives
this
gives
an
idea
of
a
continuous
rebuild
of
the
the
changes
that
land
in
federal,
but
then
in
an
enterprise
context
on
a
on
a
real
bitrate,
and
that
gives
them
a
that's,
basically,
a
continuous
site,
not
testing,
but
yeah
continue
feedback
about.
C
What's
the
state
of
federal
or
what's
the
state
of
the
package
that
are
in
fedora,
that's
also
in
well
and
how
you
know,
what
are
the
states
and
how
good
is
it
once
rel
decides
to
branch
off
federer?
That's
where
center
stream
comes
into
play,
so
the
stream
is
the
next
minor
version
of
well.
So
you
know
we
are
working
towards
rel
nine
zero,
so
center
stream
today
is
tracking
both
the
next
version
of
rail,
nine,
so
the
dot
zero
one,
as
well
as
the
next
version
of
the
of
rail
eight.
C
C
So
federer
is
the
next
metro
version
of
l
center
stream
is
the
next
minor
version
of
rail
and
that's
and
that's
where-
and
you
know,
once
all
the
work
has
been
done
in
center
stream.
It
lands
in
real
the
and
then
the
rest
of
the
diagram
is
something
we've
talked
about
before
the
center
sigs
sit
on
the
top
of
center
stream,
and
they
are
here
to
ex
to
provide
more
to
expand
the
capabilities
of
sunshine.
I'm
trying
to
find
a
different.
C
But
I'm
actually
running
out
of
ways
to
say
it.
So
if
someone
has
a
synonym,
I'm
happy
to
to
take
a
suggestion
here,
it
provides.
You
know
it
provides
things
that
are
not
part
of
center
stream
provide
experiments.
It
provides
ids
new
features,
new
packages
that
are
not
part
of
center
stream,
but
that
are
compatible
with
it.
C
C
This
change
is
we've
been
testing
it.
This
challenge
looks
important
to
us.
Is
that
something
you'd
be
willing
to
consider
right?
That,
then,
has
the
choice
of
accepting
or
rejecting,
with
a
reason
of
why
they
believe
it's
it's
not
suited
for
photon
stream,
we've
always
the
id
if
the
sig
contributes
to
center
stream,
that
changes
will
land
in
rail
down
the
line
and
so
on
the
top
of
center
stream,
similar
to
a
sig.
That's
where
the
automative
stream
distribution
will
be,
and
then
we
have
another
layer
where
the
automotive
sits.
C
C
So
this
is
what
we
have
been
working
on,
the
if
you
go
to
the
documentation.
So
that's
in
the
first
slide
that
jeffree
mentioned
this
is
six.centers.org
automotive.
The
documentation
has
been
updated
to
reflect
the
the
three
artifacts
that
the
sig
is
working
on.
So
these
three
artifacts
are
basically
the
automotive,
the
automotive
stream
distribution
itself.
C
So
that's
a
rpm
repository
that
gives
you
an
idea
of
what
is
or
what
will
be
in
the
indian
vehicle
operating
system
down
the
line,
the
automotive,
sig
rpm
repositories
that
expand
the
capabilities
of
the
the
subset
of
packages
that
are
in
the
product
or
that
will
be
in
the
product,
as
well
as
the
sample
images.
That
are
that
we
have
been
communicating
thinking
about
over
the
last
few
months,
where
we
provide
ways
of
building
images
in
ways
using.
C
Autosd
as
to
the
base
for
these
images
and
in
ways
that
could
be
of
interest
for
for
the
automotive
industry,
so
it
provides
information
there.
If
there
is
any
information
that
you
see
missing
or
you
know
typos,
I'm
not
a
native
english
speaker.
So
I
have
been
I've
been
working
on
this
one
and
I
know
a
few
people
have
reviewed
it,
but
you
know
the
more
set
of
eyes
the
better.
So
if
you
see
typos
or
item
missings
feel
free
to
to
report
them.
C
C
One
thing
we're
looking
into
is
to
have
a
proper
you'll
you'll,
see
some
links
down
there,
which
point
to
an
ip
address.
We
we're
actually
working
on
getting
the
domain
name
sorted
out.
I
have
high
hopes
that
you
know,
hopefully,
by
the
end
of
the
week
next
week
at
the
latest,
we'll
have
a
a
more
decent
looking
url
than
a
random
ip
address
on
the
internet.
C
Yeah
that
does
look
a
little
sketchy
same
thing.
It's
it's
uses
the
product,
build
terminology
here
and
fast
that
we
renamed
this
because
product
build
does
not
make
any
sense
in
the
context
of
the
sig.
The
sample
image
is
here.
You'll
have
some
containers
there,
but
this
is
very
much
proof
of
concept,
so
don't
necessarily
rely
on
them
today.
C
So
I
would
really
much
prefer
to
have
them
compress,
rather
than
having
to
download
eight
gigabytes
of
data
to
be
able
to
test
how
they,
how
these
images
work
on
my
raspberry
pi.
C
So
yeah
a
lot
of
this,
so
the
name
has
been
announced.
Yesterday.
It's
been
presented
on
blogs.center.worked
this
morning,
we're
discussing
about
it
today.
So
a
lot
of
this
is
very
new.
A
lot
of
things
are
still
in
flux,
so
we'll
you'll
see
some
more
changes
to
the
documentation.
You'll
see
you
know
proper
urls
coming
in
proper
folder
names
coming
in
as
well
and
so
on.
So
they
reverse,
as
things
are
still
a
little
bit
a
little
bit
rough.
G
Just
one
question:
you
know
pierre,
I'm
new
to
the
group
I
joined
once
in
december
and
then
now
so
I
lost
the
links
to
the
automotive
group.
Somebody
can
just
send
that
on
on
the
chat
here.
Maybe
I
can
just
use
it
for
my
for
my
purpose
to
pick
up
onto
the
program.
C
Everybody
you
will
find
there
the
mailing
list
that
we,
so
we
we
try
to
send
weekly
newsletter
to
the
automotive
mailing
list.
It's
very
low
traffic
mailing
list,
don't
be
afraid
about.
You
know
filling.
C
I
think
the
average
is
probably
about
one
email
per
week,
so
it's
okay,
it's
fairly
low
traffic.
So
that's
one
is
potentially
of
interest.
If
you
want
to
follow,
I'm.
C
But
yeah,
if
you
look
at
the
documentation,
six
that
enters
the
target
at
the
top
automotive,
that's
the
first.
The
first
two
link
that
you've
roman
sent.
This
should
be
linking
to
the
wiki
to
to
gitlab,
but
we
should
also
link
the
wiki
back
to
the
other
ones.
A
A
Any
questions
about
this
new
distro,
that's
coming
from
the
stick.
This
thing
this
is
kind
of
what
we've
been
working
for.
C
E
C
D
C
I
don't
know
if
yeah
uberty's.
E
A
H
Who's
had
a
question
I
think
right.
Sorry
yeah.
I
saw
the
answer
to
my
question
flash
up
in
the
slide
for
a
second,
so
I
withdraw
my
question.
Thank
you.
Okay,.
A
Good
I
wanted
it
looks
like
we're.
It's
excellent,
we're
doing
some
actual
work
in
the
in
the
comments
section.
That's
awesome,
ci
pipeline
is
work
in
progress.
It
is
the
I'm
guessing.
That
means
that
the
auto
that
auto
sd
will
be
done
through
a
ci
cd
pipeline.
Is
that
no
longer
work
in
progress,
or
is
it
still.
C
It's
still
working
progress.
It
is
moving
further
ahead.
Hubert
you
work
on
this.
I
know
it's
a
very
short.
Well,
you
basically
didn't
sign
up
to
be
on
call,
but
do
you
want
to
to
give
few
words
about
this
or.
F
Yeah
sure
so,
auto
sd
is
basically
the
product
build.
We
have
right,
so
we
only
really
have
to
put
it
into
a
different
folder
now,
but
it
takes
a
bit
of
time
with
the
versioning
we
have
of
the
pipeline
and
the
pipeline
itself,
and
so
we
do
a
lot
of
shuffling
around
with
s3
buckets
that
host
those
product
builds
and
the
the
entire
step
that
actually
goes
into
building
it
and
publishing
it
so
yeah.
It
is
still
in
progress.
It
is.
F
It
is
going
to
be
there
by
the
next
release,
but
it's
just
going
to
be
or
not
not
the
next
release,
but
by
the
16th.
I
think,
which
is
where
that
epic,
that
should
complete,
that
we'll
be
done.
C
One
thing
that
you
may
have
seen
in
the
last
weekly
studies
is
that
the
images
we
were
using
had
not
been
had
not
been
updated
to
use
the
new
kernel
package,
so
we
were
still
using
a
kernel
package
from
december
and
all
the
builds
that
were
done
since
were
actually
not
part
of
the
image
we
were
building.
C
Fixed
we're
now
using
you,
know
more
recent
kernel
package
or
updated
kind
of
packaged.
You
know
the
one
that
our
channel
developer
are
actually
working.
D
F
And
yeah,
just
to
mention
that
the
automotive
kernel
should
be
in
rsd
soon
enough.
We're
just
setting
a
few
upstream
issues
with
zentas
that
introduced
a
bug
with
openssl,
but
that
should
be
complete
by
the
16th
as
well.
C
C
This
has
been
tracked
in
in
red
because
that
affects
well,
and-
and
hopefully
that
will
be
resolved
soon
enough-
that
we
can
restart
building
images
again.
A
Let's
see,
I
mean
yeah,
so
we're
this.
This
is
actually
old
news.
The
migration
was
completed
over
to
centos
stream,
nine.
How
are
we
doing
with
tests
moving
into
the
pipeline.
C
It's
it
says:
well,
work
in
progress,
there
is
the
qe
is
working
on
trying
to
see
which
tests
are
our
finch
race
and
so
on.
We
are,
we
have
you
know
a
bit
of
the
internal
process.
We
have
a
ticket
jira
ticket
that
tracks
that
ask
about
documentation
on
what
is
being
tested
and
how
to
onboard
new
tests
as
well.
So
at
some
point
there
should
be
documentation,
lending
about
what
is
being
tested
currently
and
how
we
can
expand
on
this
test.
Suite.
A
C
And
find
out,
you
know
this
thing
I
will,
I
will
ask,
I
will
say
if
you
do
have
any.
You
may
also
ask
the
question
by
email.
You
don't
have
to
wait
for
the
next
meeting
to
ask
that
question.
A
Definitely
ask
on
the
mailing
list
we're
also
working
on
putting
together.
We
do
have
an
irc
channel
that
is
not
really
being
used.
There
has
been
a
request
to
create
something
other
than
irc,
so
we're
looking
into
matrix
and
possibly
creating
a
matrix
channel.
A
It's
okay
to
ask
higher
level
questions
too.
If
there's
anything
here,
that's
confusing!
This
is
mostly
a
status
for
people
have
been
here
for
a
while,
but
if
you're
new,
then
please
yes,
go
ahead.
D
Yeah,
hello,
hello,
yeah.
I
wonder:
what's
the
the
difference
between
the
centos
streams,
kernel
config
and
this
initial
version
of
auto
sd,
auto
sd
card
config,
I
just
saw
the
config
pre-empt
rts
in
the
chatting
the
window.
Is
this
only
the
difference
or
can
someone
please
elaborate?
I
mean
brief.
Was
the
initial
some
configuration
a
difference
compared
to
centos
stream.
C
I
don't
have
the
technical
knowledge
to
go
deep
into
what's
the
difference
between
the
the
stock
center
stream
kernel
and
the
one
in
in
auto
sd.
I
do
know
that
it
is.
D
C
Have
an
rt
channel
for
ct4.
I
do
not
know
more
about
the
specific
about
which
models
are.
I
know
some
of
the
modules
for
support
for
for
the
raspberry
pi
4
have
been
integrated
because
it's
just
a
convenient
platform
to
development,
but
I
don't
have
the.
I
don't
have
the
details
on
that.
I
don't
know
if
al
you
have
more
details.
C
Otherwise
we
should
try
to
get
someone
from
a
canal.
The
canal
team,
maybe
too.
E
Yeah
you,
you
can
do,
make
this
configs
and
see
what
the
the
differences
are,
but
mostly
it's
just
enabling
a
few
odds
and
ends
that
are
not
normally
enabled
and
sent
us
for
the
smaller
dev
boards,
with
some
concentration
on
the
raspberry
pi.
E
Well,
as
well
as
the
rt
stuff,
but
yeah,
I
don't
have
the
entire
list
off
the
top
of
my
head.
But
it's
pretty
easy
to
figure
out
just
by
looking
through
the
comparison,
but
the
other
configs.
D
I
remember
so
the
at
the
moment
the
raspberry
pi
is
the
reference
target
hardware
in
the
auto
seek
right.
Is
there
any
plan
to
use
the
other
target
on
hardware
reference
target
hardware.
D
Yeah,
I
don't
know
actually
what
will
be
the
best
reference
target
for
this
auto
sig.
So
my
content
is
using
specific
boards,
but
it's
not
sort
of
a
raspberry
pi,
the
open
hardware
and
yeah.
Just
wonder
yeah,
because
you
know
the
qmu
is
probably
I
don't
think
it
has
a
better
performance
compared
to
the
other
machine
yeah.
So.
E
Yeah,
there's
there's
a
bunch
of
different
sscs
that
we
could
look
at
one
of
the
the
issues
that
we
run
into
is
availability,
especially
with
a
lot
of
the
supply
chain
issues
these
days.
So
so,
for
example,
I've
been
trying
to
get
a
hold
of
some
nxp,
socs
and
they're
extremely
hard
to
get
to
I'm
actually
getting
responses
from
some
vendors
saying:
there's
a
52-week
delay,
so
I
had
never
seen
that
before
in
a
back
order.
So
that
was
pretty
amazing.
E
There
are
other
processors
that
might
be
available
as
well,
but
for
good,
better
and
different.
The
raspberry
pi
has
just
been
one
that
has
been
readily
available
till
now
and
even
that's
starting
to
eat
a
little
difficult.
D
C
D
The
other
exact
use
case
is
the
one
because
you
have
a
display
device,
so
in
in
my
interesting
area,
is
the
one
that
doesn't
have
a
display
device
mostly
used
for
the
computing
use
cases.
D
So
if
you
are
planning
to
have
kind
of
some
doco
image,
so
yeah
probably
doesn't
make
sense
because
probably
depends
on
the
host
devices
kind
of
setting.
So
but
at
least
in
the
the
middleware
centos
autoseq
auto
as
this
middleware
stuff,
maybe
it
can
be
testable
using
a
local
image
with
some
better
performance
in
the
desktop
environment.
E
I
I
Yeah
wind
river
has
a
anyway,
I
think
jc
is
not
living
in
korea
anymore,
but
I
met
him
many
times
in
korea
and
we
had
a
lot
of
good
times
together.
D
Yeah
we
met
in
seoul
so
many
times
with
soju
and
yeah.
One
time
is
probably
in
san
francisco
in
the
journey
right,
taizen
the
conflict-
yes,
yeah,
yeah
good-
to
see
you
again
here.
I
really
surprised
that
you
are
working
for
red
hat
world
is
too
small.
I
H
First
hi
june
you
mentioned
docker.
Is
it
okay
if
it's
a
workflow
that
uses
builder
and
podman
to
launch
your
container
image.
H
I
probably
should
have
said
belda,
but
I'm
just
wondering
if
you're
really
needing
the
the
docker
specific
parts
of
the
workflows
or,
if
you,
if
you're,
really
looking
to
run
a
container.
D
So
the
main
main
reason
I
am
thinking
about
using
documents
as
a
the
reference
sentence
or
to
seek
or
test
the
image
is,
you
know
when
we
use
the
qm
muse
the
some
simulator
environment
in
the
desktop?
It's
a
performance
is
very
bad.
D
In
my
company
case,
we
are
moving
to
docker
image
for
testing
some
software
in
the
target,
the
linux
environment.
It
has
a
better
performance
than
a
vm,
rare
or
qmu
basic.
The
hardware
emulator,
and
only
the
difference
is
the
corner
configuration
right.
So
the
docker
image
can
have
exactly
the
same.
Middleware
configuration
system
deconfiguration
what
we
are
looking
for
in
the
the
product,
the
imagery
so
so,
yeah.
D
You
know
if
it's
part
man
based
system
mg
or
the
other.
You
know,
I
don't
think
it's
yeah
any
anyways.
H
Thanks
because
that
helps
me
think
about
developers
using
containers
because
they
have
a
lightweight
capability
versus
some
folks
are
interested
in
containers
because
they
offer
a
lot
of
control
boundaries
to
help
keep
the
container
from
doing
bad
things
to
other
containers.
And
so
it's
interesting
to
hear
the
viewpoint
about
what
drives
container
use.
So,
thanks
for
sharing.
D
So
I
think
one
of
the
key
features.
D
In
the
vehicle
os
is
the
container-based
orchestration
right,
but
I'm
not
talking
about
that
at
this
point.
Just
thinking
about
yeah,
probably
docker
imagery.
The
basic
release
is
also
probably
a
helpful
for
some
use
case,
like
my
case,
compared
to
the
qmu
based
one,
but
but
I
think
the
premium
is
also
fine,
because
yeah
it
is,
it
is
easy
to
run.
There's
no
hard
work
to
test
the
entire
system
immediately.
Just
you
can
just
pass
the
downloaded
raw
image
disk
image
with
the
current
command
so
yeah.
D
For
that
purpose,
only
I
think
it
is
usable,
but
if
we,
the
development
team,
use
the
autoseq,
sorry
centos
or
auto
sd
the
release,
weekly
or
monthly,
releasing
easy
if
it
is
available
using
the
docker,
then
probably
very
easy
to
use
it
as
a
kind
of
some
development
environment,
because
it
has
a
high
performance
like
a
performance
compared
to
qmu.
A
One
thing
I
threw
in
here
is
it'd,
be
it'd,
be
great
to
know
what
kind
of
external
hardware
people
are
using
other
than
just
the
soc
I
mean
we
do
tend
to
focus
on
that,
because
that's
what
we
have
to
enable
the
operating
system
to
do.
A
But
you
know
I
have
a
feeling,
there's
going
to
be
quite
a
variety
of
external
stuff,
that
we
will
need
to
support
in
terms
of
cameras
and
screens
and
less
types
exactly
yeah,
so
it'd
be
great
to
know
any
details
that
anybody
has
to
share
on
that.
A
That's
a
good
question.
Also
is
one
thing
that
that
one
question
that
I
was
asked
yesterday
that
I
I
hadn't
we
haven't
had
an
answer
for
because
we're
still
bootstrapping
this
project
is:
how
are
we
going
to
be
interacting
with
some
of
the
other
x?
Some
of
the
other
technical
communities
that
are
developing
automotive
platforms,
like
the
eclipse
software
defined
vehicle
group
and
sophie
is
doing
this
within
within
the
arm
world.
A
So
I
don't
know
that
we're
ready
to
to
really
talk
to
that,
because
those
groups
are
really
just
spinning
up,
but
I
did
want
to
throw
out
that
you
know
as
those
as
those
groups
narrow
down
on
things
like
hardware
and
hardware
enablement
and
linux,
kernels
and
other
kinds
of
kernels
that
we're
definitely
at
least
within
red
hat.
A
We
are
tracking
those
red
hat
is
a
member
of
we're
a
board
member
on
the
board
for
sophie,
and
we
are
a
founding
member
of
the
eclipse
software
defined
vehicle
project
as
well
and
doing
a
lot
of
work
within
elisa.
I
should
put
up
a
slide
at
some
point.
One
of
these
meetings
about
some
of
the
other
places
where
red
hat
at
least
is,
is
participating.
A
A
E
A
So
yeah,
yeah
and
and
yeah
those
are
all
those
all
these
communities
that
are
now
starting
up.
It's
a
it's
a
very
interesting
and
dynamic
world,
there's
a
whole
lot
going
on
in
automotive,
automotive
software
in
general,
but
an
open
source,
automotive
software
and
open
source
linux
based
automotive
software
in
particular.
A
So,
okay,
well,
we've
got
about
18.
Do
we
want
to
move
on
and
talk
about
the
administrative
stuff
that
is
sort
of
my
domain,
or
is
there
any
other
questions
on
the
technical
stuff?
The
technical
side
is
much
more
interesting
to
most
people
here.
I
think,
and
I
I
would
never
want
to
derail
that
to
talk
about
meeting.
G
G
Yeah
we're
doing
something
with
lge,
and
this
question
keeps
coming
up
often
and
they're,
trying
to
derive
the
whole
architecture,
and
you
know
there's
no
answers
as
of
now
to
that
question,
but
I
think
shortly
they'll
get
they
get
addressed.
I
think,
in
the
coming
days,.
E
Could
could
you
please
restate
the
question?
I'm
not
sure
I
understood
if,
if.
G
I
need
to
have
a
linux.
You
know
operating
system
enabled
for
acell
compliance
asl
a
to
d.
After
a
and
b
it's
fine,
then
the
problem
comes
especially
d
and
e.
You
re
is
out
of
question
even
c
and
d.
Also
it
gets
difficult
to
make
it
compliant.
That's
the
issue.
A
Dividing
lines
between
acell
b,
bravo
and
then
c
and
d
is
in
delta.
There's
a
lot
of
a
lot
more
diligence
required
for
the
higher
levels.
I
Yeah,
I
hope
it
was
clear
that
our
our
work
around
safety
certification
for
linux
is
public
in
the
elisa
forum
or
lisa
project
we're
targeting
acyl
b,
but
as
we
should
all
know,
higher
safety
levels
are
possible
to
achieve
through
redundancy
in,
in
addition
to
individual
acel
decertification
having
redundant
elements
both
at
aslb
can
lead
to
higher
acyl
designations.
I
I
A
Yeah,
thank
you
for
posting
me.
I
was
doing
that
we
are
working
directly
through
elisa
too.
Our
workflow
has
been
made
public.
Our
safety
process
that
we
are
following
was
discussed
by
by
gabrielle
in
the
elisa
workshops
in
november,
and
then
there
was
a
follow-up
at
open
source
summit
in
japan
and
we'll
be
following
up
with
that.
This
year
we
functional
safety.
Is
it's
obviously
an
ongoing
effort,
but
it
is
one
of
the
primary
things
that
we
want
to
bring
to.
A
A
A
This
is
the
list
that
we
talked
through
for
in
the
last
meeting
with
contribution
guidelines.
There
is
a
start
at
these
within
centos,
because
centos
itself
has
its
own
contribution
guideline.
We
do
need
to
set
a
contributing
file
in
all
of
our
repo,
any
any
repos
that
are
associated
with
sig.
You
have
a
contributing
file,
so
people
know
how
to
contribute.
A
These
are
things
I
think
we've
touched
on
already.
Definitely
need
some
more
robust
documentation
than
wiki
and
more
likely
in
the
actual
zig
documentation
about
porting.
A
A
We
do
have
expectations
for
low
traffic,
at
least
if
irc
is
anything
to
go
by
we,
but
it
is
important
to
have
a
a
synchronous
touch
point
available
so
that
people
can
can
split
off
into
discussions
that
are
maybe
will
have
maybe
are
are
better
when
they
happen
live
rather
than
having
memorabilia
but
are
still
trackable
and
circular
and
matrix
matrix.
Definitely.
A
So
we
have
also
talked
about
having
a
board
farm
once
we
have
more
hardware
support
right
now
with
raspberry
pi's.
The
reason
that
we've
settled
on
the
pie,
as
the
initial
piece
of
hardware
to
target
was
because
most
there's
a
lot
of
them
out
there
in
the
world
and
they're,
not
that
they
haven't.
A
Hard
to
find,
at
least
not
until
until
now,
with
the
current
state
of
thing,
I
can
tell
you
that
they're
impossible
to
find
in
canada,
but
I
know
that
they're
still
findable
in
the
us,
at
least
in
some
places,
and
hopefully
in
other
places
in
other
parts
of
the
world
as
well,
but
there's
also
the
question
of
what
other
hardware
do
people
want
to
be
supported,
as,
as
was
mentioned
earlier,
we've
been
talking
about
reports
from
nxp.
I
know
that
nvidia
justin
has
come
up
in
the
past.
A
We
need
to
figure
out
how
we
would
fund
these
things.
Obviously,
within
red
hat,
we
have
some
resources
to
go
out
and
track
some
of
these
boards
down,
but
the
idea
is
also
to
make
them
accessible
by
people
other
than
just
the
group
within
that.
So
how
are
we
going
to
do
that?
How
would
we
fund
the
board
farm
and
stuff
like
that?
A
A
And
we
also
wanted
to
find
out
what
are
the
expectations
of
people
when
they
come
to
this
group.
What
you
want
to
learn
about,
we
do
have
a
regular
meeting
schedule
now,
it'll
be
in
this
time
at
this
time
in
the
first
week
of
each
month,
probably
around
the
first
wednesday,
sometimes
my
theory.
A
The
meeting
times
are
always
going
to
be
posted
on
the
sig
page,
hopefully
earlier
than
two
days
before,
which
is
when
I
got
it
this
week,
but
I
I
have
a
standing
order
to
to
go
and
update
the
wiki
page.
That's
one
of
the
actions
that
I
will
be
pursuing
and
yeah
other
than
that
they
know
we're
gonna
be
keeping
continuing
to
soldier
on
with
the
with
the
release
with
the
the
auto
sd.
A
And
does
anybody
have
any
any
other
questions,
we've
kind
of
run
out
of
supplies
dive
into
some
of
the
the
older
introductory
stuff,
but
also
give
people
eight
minutes
back
in
their
day.
A
Pounding
like
a
ladder
might
be
a
preferable
option,
so
I
think
we'll
do
that.
Let's
go
ahead
and
give
everybody
eight
minutes
back,
and
I
really
appreciate
you
being
here
and
participating
and
feel
free
to
jump
on
the
mailing
list.
Ask
any
questions.
Let
us
know
what
you're
up
to.
Let
us
know
how
in
the
dress
you
need
and
we'll
stop
it.
There
have
a
great
rest
of
your
day.
Everybody.