►
From YouTube: CentOS Automotive SIG meeting - 2021-11-16 US am
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).
C
A
B
A
A
C
B
All
right,
I'm
gonna
not
do
what
I
just
did,
because
I've
been
trying
to
close
things
but
yeah.
I
am
I'm
being
defeated
by
the
internet
today.
Good
morning,
everyone
we
have
a
much
smaller
crowd
than
normal.
B
Today
know
that
there
were
several
folks
that
I
talked
to
who
said
that
they
would
be
here,
so
we
will
give
them
another
moment
or
so
before
we
really
dive
in.
In
the
meantime,
I
will
try
to
sort
out
which
tab
is
defeating
me.
A
B
All
right
we're
I've
got
906
a.m,
where
I'm
sitting,
I
guess
it's
1206
east
coast
and
it's
probably
getting
late
in
europe
for
anybody
who's
on
from
europe.
So
let's
go
ahead
and
dive
in
we've
only
got
eight
people
which
is
odd
and
I'm
wondering
if
it's
because
of
the
meeting
change,
but
we
can
cover
that
we
can
burn
that
bridge
when
we
come
to
it
so
for
an
agenda,
I've
got
an
introduction
which
I
think,
we've
probably
already
accomplished,
so
anybody
on
the
call
who
has
not
been
here
before.
B
I
think
I
recognize
everybody's
names
pretty
much,
if
not
I'll,
just
give
a
quick
introduction.
I'm
jeff
rowe,
I'm
community
architect
at
red
hat.
I
have
somehow
been
elected
to
be
the
acting
chair
of
this
group
and
I'm
actually
very
happy
to
be
here
because
I
think
the
automotive
stick
is
going
to
be
a
a
real
boon
for
a
lot
of
people
in
the
automotive
industry.
B
So
with
that,
let's
dive
into
the
agenda,
we've
got
some
actions
from
the
previous
meeting.
We've
got
some
status
on
the
goals
I
created
a
goals
slide
a
while
back
for
the
remaining
2021
and
as
2021
is
rapidly
diminishing.
I
think
it's
time
to
go
over
those
goals
and
just
to
see
where
we're
at
and
what
still
needs
to
be
done.
B
The
future
meeting
schedule
clearly
the
current
meeting
schedule
that
I
have
okay.
Thank
you
ian,
maybe
I'll
make
sure
that
I'll
make
sure
to
enter
that
in
the
notes
for
this
meeting
the
onion
article,
the
future
meeting
schedule
or
the
current
meeting
schedule
is
of
today.
B
We
moved
it
from
thursday
to
tuesday
and
it
looks
like
we
went
from
about
35
participants
to
eight,
so
I'm
gonna
maybe
call
that
a
fail
and
we'll
bring
it
up
on
the
mailing
list
and
probably
post
another
doodle
poll
to
find
out
what
would
be
a
good
time
for
us
all
to
meet,
because
this
is
clearly
not
an
improvement
on
the
on
what
we
had
previously
we'll
have
a
quick
technical
status
update.
B
B
We
still
have
some
requests
for
help
specifically
for
developing
contribution
guidelines,
which
we
have
not
yet
accomplished,
partly
because
we've
been
focused
on
actually
getting
a
repo
up
that
people
could
contribute
to
if
they
wanted
to
and
now
that
we
actually
have
that
recall
in
place.
It'd
be
great
for
us
to
get
some
contribution
guidelines
before
the
end
of
the
year.
B
So
moving
on
the
actions
that
we
had
from
the
last
meeting
were
to
continue
the
work
on
developing
infrastructure.
We'll
have
some
discussion
on
that
in
a
few
slides.
I
think
that's
gone
quite
well.
We
currently
have
a
git
lab
presence
there.
It
is,
I
don't
know
if
that's
finally
loading
for
everybody
else.
Is
it
adjusted
for
me
and
we've
got
some
some
good
documentation,
which
is
also
great,
and
these
are
not.
Those
are
actually
the
same
page.
B
Just
make
sure
that
I'm
correctly,
which
also
contains
information
on
how
to
build,
which
is
what
everybody
has
been
really
interested.
B
Finding
a
better
times
to
meet
I've
got
a
separate
slide
on
that
and
then
encourage
all
interested
parties
to
join
this
community.
I
know
that
I
have
been
doing
a
certain
amount
of
work
in
that
regard.
B
I
think
that
it's
great
that
I
keep
hearing
back
from
people
that
they
have
heard
about
the
centos
automotive
sig,
which
is
awesome
without
letting
people
know
about
it.
They
won't
know
it's
here,
so
I
think
we
should
continue
that
effort
specific
goals
through
the
end
of
the
year.
Our
primary
goal
was
to
build
a
foundational
community
and
I'm
hoping
that
the
meeting
schedule
hasn't
thrown
a
complete
wrench
into
that,
but
establishing
working
relationships
among
all
participants.
I
think
we've
had
some
really
interesting
discussions.
B
So
far
with
this
is
our
fourth
formal
meeting
I
believe,
and
we've
also
had
two
office
hours
sessions,
and
there
have
been
some
really
great
discussions
there.
Those
meetings
and
we've
been
re.
As
I
said
a
second
ago
we've
been
reaching
out
to
a
lot
of
different
organizations
within
the
industry
in
the
automotive
industry
to
come
and
join
us.
B
We
still
need
to
develop
contribution
guidelines,
just
as
we
need
to
develop
and
continue
to
develop
plans
for
a
centos
automotive
variant.
We
do
currently
have
a
code
base
and
a
manifest.
We
have
a
build
plan.
B
Built-In
test
infrastructure,
I
think,
is
still
ongoing,
and
so
we
don't
have
a
schedule
right
now
for
publishing
a
centos
automotive
variant
or
when
we're
going
to
be
to
publishing
publishing
that
in
the
context
of
centos
stream.
But
I
would
like
for
us
to
do
that
as
soon
as
we
possibly
can.
I
think
a
lot
of
people
are
waiting
to
get
hands
on
on
an
actual
distribution
as
well
as
code
and
presentation
at
automotive
linux
summit.
I
will
discuss
that
in
a
few
minutes.
I
think.
Well,
maybe
I
won't.
B
I
can
discuss
it
now.
So
the
automotive
linux
summit
is
a
it's
the
a
big
event
for
automotive
linux.
Obviously
it
happens
every
year
in
japan
in
december,
usually
co-located
with
open
source
summit,
japan,
it's
a
linux
foundation
event,
and
we,
the
centos
I
mean
I
did
I
did
there-
were
several
presentations
submitted.
B
B
The
times
are
all
in
japan,
time
zone,
it's
at
3
45
in
the
afternoon,
japan
time
it's
going
to
be
terrible
for
the
east
coast
and
probably
terrible,
not
not
totally
terrible
for
europe
it'll
be
somewhat
early
in
the
morning
for
europe,
but
we're
also
going
to
be
having
a
doing
a
buff,
a
functional
safety
buff
directly
after
that
it'll
be
at
4,
45
pm
japan.
Time
it'll
be
about
midnight
here
on
the
west
coast
of
north
america,
and
I
think
it'll
be
three
o'clock
in
the
morning
for
those
on
the
east
coast.
B
So
I
don't
expect
to
see
a
whole
lot
of
there,
but
hopefully
it'll
be
a
really
vibrant
discussion
about
functional
safety
with
our
our
community
members
in
asia
and
sadly,
I
have
not
managed
to
develop
stickers.
Yet
that
is.
I
know
one
thing
that
people
have
asked
about.
B
Surprisingly
often
so
we're
going
to
continue
to
work
towards
that,
possibly
in
incorporating
the
centos
brand.
I
need
to
talk
with
rich
about
what
the
trademark
guidelines
are
for
that
to
make
sure
that
we
don't
don't
upset
anybody
along
the
way.
B
The
future
meeting
schedule,
as
I
said
a
second
ago,
I
think
that
the
meeting
schedule
change
was
kind
of
a
bust.
The
idea
was
to
continue
to
have
two
meetings
per
month.
This
formal
meeting,
plus
an
informal
office
hours
each
two
weeks
apart.
The
time
on
thursday
was
not
working
for
a
number
of
people
who
wanted
to
join,
particularly
from
some
major
automakers,
and
so
we
wanted
to
kind
of
switch
it
around
a
little
bit.
We
did
a
poll
picked
the
time
that
most
people
responded
to.
B
However,
the
poll
did
not
show
a
clear
path.
There
was,
I
mean
the
of
the
26
respondents.
I
believe
13
said
that
this
meeting
time
was
good.
B
Clearly
that
was
not
a
not
completely
accurate,
because
we
don't
have
13
people
here
today,
so
we're
going
to
be
doing
some
different,
some
different
experimentation
with
that
the
informal
the
other.
The
other
aspect
of
this
is
that
each
meeting
will
have
each
meeting
day
will
have
two
meetings.
We
have
this
meeting
today
scheduled
at
a
relatively
friendly
time
for
the
eu
and
for
the
eastern
u.s,
and
there
is
another
meeting
scheduled
this
afternoon
in
about
seven
hours
that
will
be
at
a
more
asia-friendly
time
and
it'll
be
in
the
evening.
B
B
And,
as
I
said,
we'll
continue
to
experiment
on
that,
so
the
actual
meet
of
this
meeting
is
technical
status
updates.
We
do
have
code
now,
as
we
showed
a
second
ago.
We
have
documentation
really
thanks
to
the
the
technical
folks,
rachel
and
pierre
and
clark
and
ian
and
everybody
else
who
has
contributed
to
these
things.
B
E
Yeah
most
of
the
work
right
now
is
migrating
the
pipeline
from
centos
stream,
eight
to
sentence
from
nine
bits,
so
work
is
ongoing
for
that
there's
also
a
lot
of
tests
that
are
added
but
they're
not
yet
running
in
the
pipeline.
The
qe
is
contributed,
so
we
want
to
be
able
to
tag
those
as
tier
1
and
be
able
to
enable
them
in
the
pipeline
that
will
be
run
on
the
on
the
built
images
but
other
than
that
yeah.
A
lot
of
the
bulk
work
is
moving
to
centos
stream.
Nine.
B
C
C
We
actually
created
a
mirror
from
the
stuff
out
of
the
cintas
streamline
namespace
into
the
automotive
namespace,
just
kind
of
as
a
stop
gap
for
right
now,
figure
out
where
we
want
to
maintain
this.
The
this
kernel
tree.
F
C
C
It
has
mostly
the
real
time
configs
for
from
rail
for
real
time,
we're
going
to
start
refining
that
if,
where
we
turn
off
things
like
oh
infiniband
and
fiber
channel
and
all
those
things
that
we
don't
care
about
in
the
automotive
space
and
turn
on
a
number
of
things
that
aren't
normally
turned
on
in
rail,
which
are
voltage,
regulator,
block
generator
little
things
like
that.
C
So
it's
a
work
in
progress.
I
mean
I
wouldn't
pick
it
up
and
drop
it
into
an
ecu
right
now,
but
we're
getting
there
probably
going
to
try
and
use
the
raspberry
pi
4
as.
D
C
Demo
platform,
just
because
it's
ubiquitous-
and
you
know
I
mean
no
one's-
going-
to
use
an
rpi4
as
an
ecu
controller.
But
it's
it's
something
to
work
with
and
it's
close
to
what
we'll
be
using.
C
B
Right,
which
is
you
know,
I
know.
A
B
Got
a
lot
of
other
hardware
platforms
and
the
raspberry
pi
4
seems
to
be
the
one
that
that
keeps
coming
back
up.
C
I
would
welcome
an
effort
once
once
we
get
this
thing
nailed
down
a
little
bit.
I'd,
welcome
an
effort
to
try
and
extend
it
to
you
know
some
of
the
others.
I
mean
obvious
an
obvious
candidate,
although
they're
not
very
available
right
now,
video
jetsons
yeah
and
there
are
others
around.
I've
got
a
little
board
here.
That
is
just
dying
for
me
to
do
something
with
it
called
a
tinker
edge
or
made
by
asus.
C
C
C
So
I
guess
the
the
short
answer,
which
was
none
of
the
above-
that
was
all
very
rambling
and
long.
The
short.
B
A
And
it's
exciting
to
see-
and
I
want
just
to
add
something
to
that
as
I'm
hoping
that
we
will
develop
a
workflow
around
that
kernel
and
possibly
other
packages
that
evolve,
that
enter
into
this
over
time
that
models,
what
centaur
stream
more
broadly.
Does
that
we'd
like
this
to
be
a
place
where
we
can
show
show
development,
but
also
receive
input.
A
Clark,
I
would
you
bring
this
up
so
often
I'll,
just
throw
I'll
just
put
a
bogey
out
there.
If
you
can
display
the
camera
without
having
to
start
a
process,
then
I
don't
know
I
mean
you
would
have
that
would
back
up
this
this
bluster
of
what
you
need
more
than
the
kernel
with
something
real,
so
I'll,
just
toss
that
out
there.
C
I
have
I
have
the
ability
to
create
a
kernel
thread
so
entirely
possible
that
I
could
get
close,
but
unfortunately
I
don't
have
the
time
to
do
it
right
now
and
so.
B
I
have
a
possibly
a
silly
question,
which
is:
I
know
that
one
of
the
goals
is
to
create
a
two
second
boot
time
or
less
in
order
to
go
from
cold
to
running
a
rear
camera,
because
that's
been
the
requirement
that
people
have
been
working
towards.
B
It
seems
like
there
are-
and
I
know
I'm
not
the
only
person
who
has
thought
this,
but
it
seems
like
there
are
other
strategies
for
that
besides
having
to
boot
the
entire
system
and
then
and
start
up
a
thread
for
a
camera
as
opposed
to
letting
the
camera
be.
I
mean,
I
know
that
my
son
has
a
first
first-person
view
camera
for
a
remote
control
aircraft.
A
Just
one
of
them
so
yeah,
that's
absolutely
true.
We
don't
mean
that
the
whole
system
has
to
be
available,
but
we
do
need
to
start
really.
This
is
the
one.
The
only
other
one
that
has
come
up
in
broad
conversations
is
things
like
the
earlier
telematics
can
be
available,
the
better
yeah
but
yeah
yeah,
and
it
can
be
a
staged
thing.
We
know
we
know
that.
That's
often
the
that's,
the
approach
has
been
taken
in
the
industry
right
now
for
the
camera
in
particular.
I
know
that
I
had
a.
A
I
think,
I'm
not
revealing
anything
since
this
is
my
own
observed
behavior
in
a
vehicle
that
I
owned,
but
that
my
our
chevy
volt
would
display
the
rear
view
camera
when
you
turned
it
on
no
matter
what
and
then
eventually
the
full
infotainment,
but
anyway
I
didn't
want
to.
I
didn't
want
to
dive.
In
I
mean
we.
On
the
one
hand,
this
is
a
great
requirement
because
it's
so
it
is
so
crystal
clear,
but
it's
just
one
of
many
I'll.
C
C
Well,
the
one
of
the
reasons
that
we
we're
looking
at
the
worst
case.
You
know,
obviously,
if
we
can
do
suspender
ram
and
things
like
that,
we
can
wake
up
pleasingly
fast
and
do
all
that.
B
C
Care
that
we
we
manage
to
do
it
properly.
You
know
99.9
percent
of
the
times
they
care
about
that
0.1
percent.
B
Okay,
any
other
technical
status
to
bring
in
anything
that
I
might
have
missed.
B
Okay,
as
far
as
calls
to
action
go,
I
still
need
help
contributing
or
creating
these
contribution
guidelines.
So
as
soon
as
anybody
has
some
spare
cycles,
that
would
be
great
I'd
love
to
do
that
before
the
end
of
the
year
or
at
least
get
started
on
it.
We
do
need
to
develop
some
porting
and
bsp
pages
in
the
wiki.
This
was
brought
up
at
the
last
meeting,
and
that
was
the
place
where
we
were
talking
about
bringing
in
some
hardware
ideas.
B
I
think
the
jetson
is
a
great
one.
I
think
there's
a
number
of
others
that
we
could
probably
target
as
well.
B
No
and
and
I
think
that
that
actually
defines
one
of
the
big
differences
between
a
distro
based
operating
system,
first,
a
a
build
it
from
source
operating
system
in
which
everything
would
be
customized.
C
C
So
we
can
support
it
for
long
periods
of
time,
as
opposed
to
if,
as
you
go
along
and
you've
got
a
10
15
20
year
life
cycle
for
a
a
you
know,
execution
environment,
you
have
to
have
somebody
to
back
it.
A
C
B
That
has
always
been
a
big
challenge
in
the
arm
world.
I
think
that
is
something
that
we
have
been
working
on
and
rhea
as
in
red
hat,
and
it's
something
I
think
that
we,
as
in
the
centaur
sig,
will
continue
to
work
on
in
the
context
of
automotive.
C
Well,
a
bunch
of
us
at
red
hat
have
come
from
the
traditional
embedded
world
and
back
in
the
2000s,
you
know
like
2005
2006,
whatever
it
was,
it
was
not
hard
to
pick
out
the
wind
river
engineers
in
a
crowd
because
they
were
the
ones
missing
patches
of
hair
after
having
pulled
them
out
trying
to
support
all
those.
You
know
board
support
packages.
C
A
B
No,
no
I'm
I've.
I
mean
that
was
one
of
the
reasons
why
why
lenaro
came
into
existence
was
to
help
that
particular
problem.
I
was
actually
at
mata
vista
in
the
in
the
late
latter
part
of
that
decade,
and
I
remember
it
very
well.
We
had
a
board
farm
to
pick
up
as
much
space
as
our
cube
farm.
C
B
Actually
leads
to
our
next
call
to
action.
That's
been
up,
which
is
the
idea
of
a
board
farm
with
remote
access.
You
know
that's
something
that
we
discussed
previously
and
I
don't
know
if
we've
gotten
any
farther
with
it.
C
A
C
C
C
B
One
other
idea
that
I
know
that
this
this
idea
keeps
coming
up
over
and
over
again
in
all
the
various
communities
that
I've
been
involved
with.
One
innovative
idea
that
I
heard
one
time
was
that
rather
having
it
rather
than
having
a
board
farm,
what
if
there
was
a
library
where
we
would
put
together,
distinct
kits
that
would
have
a
you
know.
B
Maybe
it
might
have
a
development
board
and
a
screen
and
whatever
networking
hardware
was
required
and
basically
put
those
in
a
box,
and
people
could
check
them
out
and
they
would
lit.
Whoever
was
in
was
running.
The
thing
would
literally
just
mail
it
to
them
for
a
specified
amount
of
time.
B
B
And
replacing
hardware
that
goes
bad
or
for
one
reason
or
another,
you
know.
I
think
that
there's
a
lot
of
different
things
that
could
go
wrong
with
it,
but
you
can
also
buy
a
whole
lot
of
boards
and
mail
them
around
a
lot
for
the
same
cost
or
less
as
actually
creating
a
board
farm
that
is
useful
and
the
result
would
be
much
more
usable
if
it
was
putting
boards
on
in
people's
hands.
B
I
don't
think
we're
quite
at
that
point
with
the
centos
sig.
Yet
we
have
any
any
very
rich
relatives
who
are
willing
to
put
in
a
whole
bunch
of
money
to
send
boards
out
to
random
people,
but.
C
B
B
And
that's
why
I
think
you
know
focusing
on
things
like
the
raspberry
pi
I'd
love
to
see
some
other
arm
arm
hardware
in
there
besides,
the
raspberry
pi
as
well
a
little
bit
more
supported
than
the
broadcom
chips.
I'm
thinking
maybe
like
the
beagleboards,
are
a
good
idea.
C
B
B
D
B
C
Are
hung
off
of
an
I
squared
c
or
bi
interface
so
that
that
kind
of
limits,
the
bandwidth
as
well
but
they're
so
useful?
You
know
it
may
maybe
a
while
before
can
sunsets.
B
Yeah,
so
if
I
you
know,
if
you
narrow
down
the
number
of
development
boards
with,
can
support,
that's
an
immediate
limiting
factor.
I
believe
that
the
was
it
the
snapdragon,
the
qualcomm
snapdragon.
B
There
was
one
that
would
that
linaro
was
working
with.
I
think
it
was
the
dragonboard
for
10c,
I
believe,
has
can
bus
support.
I
know
they
were
giving
those
away
at
conferences
for
a
number
of
years.
I
know
I've
got
one
or
two
of
them,
so
that
might
be
another
option,
love
to
see
some
nxp
hardware-
and
maybe
even
renaissance
hardware
involved
as
well,
but.
B
You
know
that
that
I
don't
want
to
take
away
from
the
fact
that
we're
not
developing
for
each
one
of
those
boards.
As
said,
we
are
developing
for
one
arm
arm
64-bit
architecture
and
making
sure
that
it
runs
on
each
one
of
those
different
boards
and
then
using
those
boards
and
their
capabilities.
However,
is
this
best.
B
So
you're
right,
maybe
a
board
farm
isn't
what
we
need.
Maybe
we
need
some
other
method
for
for
getting
resources
into
people's
hands.
B
B
G
Definitely
my
name
is
joe.
This
is
my
first
meeting.
I
am
from
vipro
I'm
just
getting
used
to
the
way
this
is
connected.
So
just
give
me
a
few
days
to
cope
up
with
the
base.
B
Sure
welcome
yeah
and
if,
if
you
and
and
your
compatriots.
B
Okay
and
I'd
be
happy
to
I'd,
be
happy
to
get
with
you
offline
as
well,
and
give
you
some
guidelines
and
just
an
overview
of
the
sig.
What
what
we
hope
to
accomplish
here
exactly
there
will
be.
I
actually
do
have
some
some
slides
to
that.
These
are
just
leftover
from
previous
calls,
but
I
don't
know
if
you
were
here
earlier
but,
as
I
said,
this
is
only
our
fourth
formal
call
for
this
for
this.
B
So
it's
really
just
starting
out
we're
just
in
the
process
of
getting
the
infrastructure
working
and
up
to
speed.
There
are
links
in
the
slides
that
I'll
send
around
afterwards.
Okay,
you
can
see
there
is
a
code
base
here.
This
is
actually
mostly
a
list
of
manifests
and
a
build.
It's
more
of
a
build
system
than
a
than
a
code
base.
Okay
and
there's
documentation.
F
F
Well,
welcome
we're
glad
to
have
you
aboard.
Thank
you.
Thank
you
jeffrey,
and
you
know
wishing
you
all
the
same.
Yeah.
B
C
You
know
I
just
just
say:
well
what
else
does
everybody
see
that
I've
got
a
couple
of
weird
little
boards
here
that
I'm
not
sure
are
suitable
but
I'll
I'll
drop
them
in
somewhere?
If
you
give
me
a
place
to
do
it.
A
C
A
C
So
I'd
like
to
see
the
sig
at
least
come
up
with
some.
You
know
some
alternatives
that
we
can
support
as.
A
C
B
I
have
run
across
very
few
development
boards
that
would
even
be
within
the
universe
that
we're
talking
about
that
are
don't
already
have
linux,
well
yeah,
and
so
I
I
think
that
for
hope
from
you're
right
for
most
of
these,
the
the
porting
process
would
actually
be
fairly
easy
and,
and
it
would
be
good
to
have
a
specific
call
about
it.
We
can
dedicate
one
of
our
office
hours,
calls
to
that
or
we
can
just.
C
B
I
was
going
to
say
you
know
I
was
going
to
announce
the
time
for
the
next
office
hours,
which
will
be
in
roughly
two
weeks,
but
I
know
that,
as
we
covered
earlier
in
the
call,
this
meeting
time
doesn't
quite
work
for
a
whole
lot
of
people,
so
we'll
continue
to
iterate
on
meeting
times
and-
and
I
this
is
going
to
be
a
great
discussion
point.
I
think.
Certainly
once
you
get
people
started
talking
about
hardware,
it's
a
it's
a.
It
ends
up
usually
being
a
very
vibrant
conversation.
B
I
know
that
I
know
from
personal
experience
that
there
are
automotive
discussions
going
on
within
the
risk
fight
community
as
well
love
to
see.
I
wasn't
even
going
to
bring
that
up,
but
another
challenge.
I
always
bring
that
up.
B
So
I
think
that
you
know
getting
hands-on.
Hardware
is
even
harder
for
that
particular
community,
but
there's
a
lot
of
hardware
out
there
and
narrowing
down
what
hardware
is
available
and
what
we
should
focus
on
is
a
primary
activity
and
which
is
a
one
of
the
central
parts
of
this
state,
so
so
yeah.
Let's
do
that.
B
We
could
also
start
the
discussion
as
well
on
the
mailing
list.
Clark,
if
you
want
to
send
a
note
to
the
mailing
list,
just
to
say
we're
we're
getting
this
discussion
going,
we'll
be
meeting
in
person
in
a
couple
weeks.
How
can
we
give.
C
B
C
C
B
B
Okay,
cool:
does
anybody
have
anything
else
they
want
to
bring
up
or
share
or
talk
about.
B
Otherwise
we
will.
We
will
continue
on.
B
All
right:
well,
I'm
going
to
maybe
call
the
meeting
and
we
will
reconvene
in
a
couple
weeks
at
office
hours
and
hopefully
have
some
good
discussions
about
hardware.
B
Thank
you
all
for
coming
very
much
appreciated.
We'll
have
the
meeting
notes
and
and
recording
going
up
in
a
little
bit.
B
There
should
be
it,
there
is
actually
a
slot
already
set
up.
It
should
be
on
your
calendar.
If
not,
then
look
well
just
double
check
to
see
if
it
looks
on
your
calendar
and
for
anybody
else
who
isn't
on
the
meeting,
invite,
let
me
know
if
you
would
like
to
be
on
the
meeting.