►
From YouTube: Foundational Infrastructure Working Group [May 5, 2022]
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
Anyone
from
the
foundation
is
showing,
I
should
just
start
hello.
People
wait
I'll
share
my
screen
and.
A
Then
yeah
so
agenda
items
we
have
a
few
for
change.
Yeah.
I
heard
from
ramon
that
the
bionic
stem
cell,
by
from
experiencing
some
gcp
upload
stem
cell
issues,
which
apparently
also
affect
already
published
stem
cells.
I
don't
know
if
it's
only
biomech
just
like
something
to
keep
an
eye
out,
for
it
seems
to
work
with
light
stem
cells.
Maybe
there's
like
a
gcp
api
issue
that
they
have
something
it's
timing
out
on
uploading
stem
cells,
so
don't
know
yet
yeah.
There.
A
Yeah
and
I
will
be
having
vacation
so
there
will
be
two
goals
where
I
won't
be
able
to
attend.
So
I
was
wondering
if
someone
can
take
over
maybe
baehan,
but
we
can
also
talk
about
that
offline.
C
Yeah,
let's
talk
off
what
talk
of
when
I
have
to
check
my
calendar
like.
A
I
just
want
to
bring
that
up:
let's
go
over
the
open
vrs
before
we
start
ben.
Do
you
have
any
items
that
you
want
to
discuss.
D
Yeah,
I
was
just
gonna.
I
was
we've
done
something
a
long
time
ago
that
I
wanted
to
bring
up
in
a
working
group
we're
looking
at
deprecating
the
event
log
forwarder
for
windows
with
windows,
syslog
release,
and
so
that's
something
that
there
should
be
currently
a
feature
to
replace
it.
A
D
The
new
feature
for
windows-
syslog
release,
is
already
out.
There
is
versions
of
windows,
syslog
release.
I
believe
that
have
that
new
job
in
it
and
I've
added
a
notice
to
event
log
release.
That
says
it
is
deprecated.
E
C
D
All
you're
writing
is
the
the
the
short
explanation
as
to
why
is
the
old
project
was
written
in
sharp.
It
didn't
support
it
split
up
across
two
repo,
so
it's
kind
of
hard
to
manage.
We
kind
of
haven't
so
far
and
it
also
doesn't
support
tls
either.
So,
okay,
that's
that
nice.
A
A
A
A
Okay,
this
has
no
steel,
bots
yeah.
This
is
gonna,
probably
be
closed.
A
Yeah,
this
still
needs
to
be
rebased.
Probably
it's
gonna
maybe
be
close,
because
nobody
cares
about
this.
A
C
A
E
A
For
that,
so
this
is
a
spending
review
now
right
off
the
grate
yeah
yeah.
A
Let's
wait
for
that
felix
and
florian
now
that
we
have
both
of
you
in
the
call.
Maybe
it
makes
sense
to
go
over
these
again.
G
Oh
so
I
was,
I
was
on
vacation
for
the
last
two
weeks,
so
it
hasn't
been
worked
on
since
then.
I
guess
that's
the
short
version
and
right
now
we
our
focus,
is
on
up
bumping
the
net
address
gem
and
after
that
we
will
potentially
look
into
this.
H
Okay,
that's
that's
fine,
but
we
would
also
work
first
on
bringing
in
that
flag
for
most
deprecated
errand
behavior,
because
that's.
H
A
G
So
we
are,
we
were
just
creating
a
release
and
we're
testing
that
on
one
of
our
deaf
landscapes
to
check
that
all
the
packaging
scripts
and
everything
works
as
expected,
and
until
that
we
had
that
remained
as
a
draft
drop
it's
currently
being
deployed.
And
when
that
is
successful,.
A
H
A
Yes,
yes,
that's
true,
okay,
I
will
just
wait
for
that.
A
We
already
looked
at
that.
Yes,
the
magical
flips
one
I'm
actually
working
on
this
now,
so
I
finally
found
some
time.
Yeah
almost
got
this
working
so
onto
this
one
yeah.
I
already
discussed
it
with
justin
the
other
day.
A
B
I
wasn't
able
to
build
any
ubuntu-based
stem
cells
because
there
was
missing
some
if
statements,
because.
A
B
That
sucks,
yeah
okay,
I
will
do
it
tomorrow,
but
now
to
go
in
yeah.
There
were
so
the
problem
was:
is
that
once
I
fixed
something
I
came
up
to
an
extra
there,
there
are
so
like
some
a
lot
of
packages
that
are
the
docu.
The
funny
thing
is
that
it's
well
documented,
because
it
says
this
is
specific
for
red
hat,
but
there
is
no,
if
statement
behind
it
like
if
this
is
only
for
red
hat
based
os,
I'm
going
to
install
this
package.
These
are
all
the
only
thing
that
I
I
came
into.
B
So
I
think
that
should
be
addressed
first
and
then
we
can
take
a
look
further.
Okay,
do
you
remember
which
stage
it
was
from?
There
were
multiple
stages:
okay,
because
first
I
I
fixed
one.
It's
basically
all
the
packages
that
were
specific
for
red
hat.
B
F
A
But
that's
that's
fine,
so
who's
gonna
take
action
like
justin.
Are
you
just
gonna
try
to
build
this?
The
ubuntu-based
stem
cell
or
is
ramon
gonna
put
some
comments
in
there.
I
don't
know
what
to
use.
A
A
Okay,
thanks
yeah,
that
was
it.
That's
all
the
opening
issues,
another
open
pr,
and
then
we
have
this.
A
E
E
A
F
A
And
then
the
g
ga
will
take
some
time
because
that
so
ga
will
be
like
one
once.
We
have
confidence
that
all
the
upstream
things
like
cf
deployment
and
stuff
work
on
it
and
that's
all
still
a
bit
slow
right.
So
we
want
to
know
when
we
need
to
like,
if
there's
still
like
a
moment
that
we
need
to
make
breaking,
we
want
to
keep
the
ability
to
make
breaking
changes
to
jammy
until
we
are
fairly
confident
that
everything
works
right.
A
Okay,
it
has
been
a
while.
I
wasn't
I
mean
I
was
around,
but
I
wasn't
this
closely
involved
with
the
whole
senior
or
trustee
to
xenial
transition
or
the
bionic,
the
bionic
one
I
was
involved
with,
but
that
was
different
because
back
then
like
a
lot
of
the
bionic
work
was
done
and
then
it
was
paused
for
a
long
time
and
then
roman
and
I
finished
the
bionic
work
basically,
but
then
most
of
cfc
deployment
already
worked,
and
now
we
are
actually
really
on
top
of
it.
As
in
we
have
jamie.
A
Jamie
went
out
like
just
the
jimmy
beta
beta
went
out
just
after
canonical
cut
the
ga,
and
I
think
we
have
so
there
is
like
a
timeline
that
has
been
shared
here.
Isn't
it
here.
B
A
Yeah,
I
know
yeah
so
there's
like
some
upstream
issues,
so
one
blocking
thing
is
the
tretup
right,
trent
typos.
A
Yeah
there's
no
date
here.
I
thought
there
was
something
where
there
was
a
date.
B
Yeah,
that's
for
the
sea
of
deployment
that
was
for
cf
deployment.
D
B
I
think
some
cf
deployment
components
are
already
being
tested
with
dme,
but
I'm
not
sure.
B
A
Then
I'm
stop
this
meeting
thanks
all
for
joining
see
you
later
bye.