►
From YouTube: Foundational Infrastructure Working Group [Dec 16, 2021]
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).
B
Okay:
let's
go
to
the
board,
let's
run
the
sync
first,
that
should
so.
We
have
a
tool
or
I've
developed
a
tool
to
sync
all
the
open
issues
that
are
in
one
config
file
and
that
config
file
mimics
what
we
have
in
the
foundation
null
infrastructure
working
group,
all
the
repos
there.
B
B
You
can
create
different
views,
so
you
can
have
like
kanban
style
views
and
then
you
have
like
scopes
or
filters
basically
on
the
whole
list
and
you
can
create
custom
fields
on
all
your
issues,
so
I
have
added,
for
example,
an
area
field,
and
that
way
we
can
also
look
at,
for
example,
all
the
pr
from
uaa.
We
will
go
do
that
later,
let's
start
with
the
porsche
things,
and
then
we
go
from
right
to
left
so
things
that
are
ready
to
be
merged.
We
go
over
first.
A
B
I
will
also
prove
this
one
and
we
have
two
approvals
so
within
the
there's
working
group
guidelines
or
things
that
they're
working
on
and
the
idea
there
is
that
there
should
be
two
approvals
to
get
something
merged
and
we
will
go
at
some
point,
maybe
to
auto
merging,
but
that's
currently
not
it's
not
there
yet
so.
A
C
Yeah,
I
think
it
was
last
week
also.
B
B
Okay,
pending
review
discussion.
B
So
why
we
have
double
labels
is
because
you
can
have
only
one
prior
or
no
not
priority.
It's
the
stat
state
or
something
every
issue
can
only
have
one
state,
but
it's
shared
between
issues
and
pull
requests.
So
pending
review
is
not
really
appropriate
for
an
issue.
So
there
it's
discussion.
B
Yeah,
they
still
need
to
fix
yeah
sure
sure,
but
I
need
to
iterate
on
this.
A
Okay,
yeah.
B
I
don't
know
if
anybody
has
any
more
contacts,
but
this
one
has
been
open
for
a
while.
We
had
a
discussion
offline
with
donatello
from
who's
from
softlayer
and
they
have
an
issue
and
we
are
now
they
are
unblocked.
So
it's
not
that
urgent
anymore
because
they
fixed
the
just
use
an
older
agent,
but
still
there
needs
to
be
a
fix
in
the
long
term,
so
we
cannot
just
close
it,
but
this
one
was,
I
guess,
really
trivial
right
can
I
can
it
have
a
lot
of
questions
again.
B
B
On
another
review,
I
mean
this
wow,
I
don't
know
how
we
got
in
this
stage
and
it's
also
quite
a
small
change
with
a
lot
of
tests
and
then
there's
even
questions
for
more
tests
on
this
okay.
C
So
from
my
point
of
view,
this
also
we
have
the
test
cases
for
the
new
use
cases,
but
I
am
the
owner
of
the
pr
I
cannot
approve
it.
B
B
Okay,
let's
wait
for
that,
not
that
something
is
totally
blocked
on
this
or
something
oh.
This
is
a
big
one.
I
think
this
is.
C
C
B
Okay,
so
we
should
put
it
in
waiting
for
changes
what's.
Why
am.
C
C
Yeah,
because
I
am
seeing
that
I'm
not
anymore
in
the
my
state
was
in
how
to
approve
again
yeah.
B
They're
they're
we're
creating
a
separate
pipeline
to
test
fibs,
pipe
stem
cells
and
we're
I'm
also
in
a
conversation
with
the
foundation
and
canonical
to
see
if
we
can
get
like,
maybe
publish
something
for
the
broader
community,
not
in
its
current
form,
but
we
would
need
some
agent
changes
to
inject
the
ubuntu
advantage,
token
and
runtime.
Otherwise
you
can
basically
use
it
without
paying
for
it.
That's
not
nice
for
canonical
but
yeah
that
discussion.
B
That's
a
broader
discussion
going
on,
but
where's
that
ramon
has
been
setting
up
ci
for
this,
but
this
is
more
of
like
us.
C
B
Yeah,
so
that's
why,
like
maybe
there's
someone
on
your
team
that
wants
to
take
a
look
at
this
as
well,
because
we
at
vmware
are
also
really
quite
interested
in
this,
because
we
have
some
customer
customers
asking
for
this,
and
now
that
canonical
is
stepping
up
to
actually
make
this
happen
right.
That
would
be
an
awesome
scenario.
C
I
have
to
check,
I
have
to
check
how
whether
this
is
known
on
our
side.
Most
probably.
Yes,
I
think.
B
Yeah,
I
have
a
pink
felix
about
this,
but
he
is,
I
don't
know
on
leaf
or
something
so
he
redirected
me
to
someone.
I
don't
remember
his
name,
a
slack
crashed
so,
but
I
will
yeah
we
can
follow
up
on
this
offline
yeah.
B
If
you
find
out
someone,
that's
sap
who
wants
to
also
look
at
this
okay
now
we
have
some
new
ones,
we're
almost
through
it.
That's
good.
B
And
this
is
on
the
bionic
one:
yes,
okay!
So
now
so
it
makes
sense
that
constantine
who
created
this
original
code
has
approved
this
change
and
ramon
on
bionic
branch.
So
I'm
gonna
go
ahead
and
merge
this.
A
B
That's
a
really
big
one:
yes,
okay,
we're
gonna,
run
the
lottery
foundational
infrastructure.
A
D
B
F
So
it
may
be
related
to
my
recent
patch
that
for
taking
the
actually
mounted
devices
in
order
to,
but
oh.
F
No,
no,
my
using
touch
just
was
just
checking
actually
mounted
devices
on
varbic
app
store.
F
To
properly
report
no
assistant
disk
stats,
whenever
even
when
the
directory
exists,
the
capstone
directory
may
exist,
nothing
is
mounted,
and
previously
there
were
wrong
statistics
that,
were
I
see
that
change
yes,
and
now
the
one
point
are
checked.
F
So
somehow
I
don't
remember
how,
but
I
I
didn't
do
it.
I
am
using
some
thing
that
already
exists.
I've
been
using
some.
B
That's
it!
Okay!
Before
we
go
to
issues,
I
think
it's
good
to
also
now
that
we
have
marcus
on
the
call
and
also.
B
Yeah,
let's
go
over
the
ua
prs,
maybe
not
all
of
them,
but
maybe
no.
G
B
G
Yeah,
you
may
know
that
this
is
a
historic
view
and
because
of
this
many
changes
of
their
responsibilities
in
the
ua
area
the
last
year.
So
to
say
this
is
the
few
of
open
issues
and
prs.
Nobody
feels
really
responsible
for
yes
and
therefore
my
hope
was
that
peter
is
also
in
this
call
peter.
F
B
G
Yeah,
okay,
you
have
put
it
different
project
into
this
view,
because
here
you
see
that
this
declined
and
for
ua
we
have
two
different
clients.
The
uae
itself
should
also
yeah
it's
also
here
there.
B
G
Yeah,
okay,
exactly
that
is
one
from
the
the
very
last
is
a
new
created
one
and
I
already
worked
on
it,
so
I
have
no
access
to
this
board,
so
I
cannot
move
this
bullets
into
a
different
state,
but
you
can
move
it
into
pending
for
review,
because
I
have
created
a
pull
request.
B
It's
but
I
I
think
I
can
just
give
you
access.
That
would
be
also
good.
B
I
think
I
can
just
is
the
whole
f.
No,
then
it's
not
the
health
foundation.
Those
themes
are
still
wrong.
What's
the
what's
your
s.
B
G
B
All
try
to
do
if
we
so
we
assign
so
okay
there's
the
reviewers,
that's
good.
I
also
try
to
assign
it
because
then
that
shows
up
on
the
board,
so
the
reviewers
don't
show
up
on
the
board,
but
in
the
so,
if
you
assign
it,
then
you
see
the
icon.
Okay.
B
Here
I
don't
know
that's
and
you
can
filter
on
that
as
well.
B
A
B
But
yeah
that's
useful,
okay
and
then
this
one.
G
Only
the
client
libraries
is
something
I've
tried
to
come
with
peter
to
a
conclusion
which
client
library,
for
example,
will
ally
will
be
alive
after
our
decision,
because
we
have
a
go
and
a
ruby
that
is
for
ruby,
and
currently
I
have
no
access
to
this
project
so
because
of
this
renewal
process
with
the
working
group
leads,
I
only
have
access
to
ua
and
ua
release,
which
is
fine
for
me,
but
if
it
belongs
everything
to
uaa,
then
we
should
all
have
access
to
this.
B
Yeah
I
mean
like
the
they
want
to
move
to
a
pr
based
model
or
pr
only
model.
So
that's
the
plan,
but
the
access
rights
are
currently
still
there's.
We
have
a
pr
going
to
create
some
automation
and
some
standardization
about
around
this,
but
that's
not
there
yet
so,
okay,
but
you
see
here's
also
peter
assigned.
B
Yeah
I
saw
it,
but
I
I
can
give
you
access
later
yeah.
A
B
You
can,
can
you
send
the
repos
that
you
don't
have
access
to
to
me
on
slides?
I
will.
I
will
send
it
to
you,
yes,
because
we
don't
have
to
do
that
with
everybody,
but
that
yeah
I
see
it.
It's
assigned.
B
It's
not
that
interesting
here
like
because
it's
only
two
of
you
right
so
yeah
yeah.
G
Is
also
responsible
for
credit,
so
that
is
why,
I'm
so
to
say
we
both
in
charge
of
uaa
and
krathap,
and
he
does
almost
all
from
gretap
and
the
ua
stuff
belongs
to
me
so
to
say
yeah,
but
we
have
additional
colleagues
bruce
richards.
I
don't
know.
I
have
not
talked
to
him
since
some
weeks,
but
he
was
also
in
this
area
active
also
for
the
contributions.
B
There
might
be
another
approver
coming
soon
like
that.
We
should
add
to
the
working
group.
G
Yeah
we
have
that
so
torsten,
which
is
also
in
the
call,
is
colleague
of
mine
who
could
do
the
job
so
to
say
we
have
about
three
or
four
sap
colleagues
and
three
or
four
vmware
colleagues,
but
actively
working
on
that.
It's
me,
peter,
I
would
say
yeah.
B
But
I
mean
I
would
it
would
be
nice
for
both
of
you
to
to
spread
review
load
a
bit
right.
B
I
mean
like
I
I
could
imagine
like.
Maybe
it's
enough,
I
don't
know
what
the
I
don't
have
a
good
handle.
Yet
on
like
how
many
incoming
pr's
there
are
each
week
like
so
in
the
bosch,
eco
or
wash
area
we
have
around,
I
would
say
seven
till
maybe
ten,
I
don't
know
on
a
good
week.
We
have
ten.
G
No
feature
request
one
per
week,
I
would
say,
but
our
problem
is
that
we
have
to
really
fast
decide
whether
we
need
a
fix
or
not.
If
pull
requests
from
a
bot
comes
in
and
or
some
cves
pop
up
and
so
on.
That's
yeah.
B
The
pr
from
from
bots
we
leave
out
of
I
mean
if
you
want,
but
we
can
get
them
here,
but
we
have
filtered
out
them
at
least
for
the
bosch
part,
because
otherwise
it
would
be
too
much.
And
it's
not
that
useful
to
look
at
those,
at
least
in
the
bosch
on
the
on
the
board
side.
We're
trying
to
go
to
a
model
where
we
have
like
ci,
just
test
those
things
and
then
merge
it
or
not.
B
Even
merge
but
just
bump
dependency
dependencies
in
ci
to
run
the
test
and
then
just
commit.
Because
I
don't
know
if
it's
pretty
useful,
always
what
we.
G
Often
have
is
an
issue
created,
but
most
of
them
are
so
to
say
consulting
issues
where
someone
expect
that
that
should
work
and
or
not,
and
then
it's
expected
that
we
create
a
feature
based
on
yeah
this
consulting
and
therefore
we
should
have
a
automatic
close
of
these
issues.
Pull
requests
are
totally
okay.
I'm
I
tried
to
bring
most
of
them
into,
but
we
have
many
issues
which
yeah.
B
G
B
For
issues
we
are
we're
also
looking
at
the
steel
bots
to
like
start
auto,
closing
things
that
are
open
for
more
than
an
x
number
of
days
without
any
activity,
because
what
you're
saying
is
true,
like
there's
a
lot
of
like
those
issues
that
are
just
keep
dragging
on
or
there's
no
activity
anymore,
and
I
mean
we
can
leave
it
open
in
a
state
of
like
waiting
for
contribution
and
then
we
can
leave
it
open
for
a
few,
maybe
weeks,
and
then
it
closes
because
I
mean
in
the
end.
B
G
G
That
is
with
ge
colleagues,
former
tea
colleagues
asked
internally
for
a
fix
yeah.
That
is
exactly
where
I'm
waiting
for
a
response
created
that
pull
request
and
ask
the
requester
who
is
not
in
this
ticket.
But
I
he
contacted
me
directly
while
slack-
and
I
asked
him
to
test
this
if
it
is
working
or
not
yeah,
because
it
is
a
special
scenario
which
only
ge
has
in
place
so
to
say.
G
G
B
G
Yes
and
therefore
I
cannot
yeah,
I'm
also
unsure
what
we
have
to,
and
this
is
a
special
scenario
and
therefore
it's
only
I'm
asking
the
colleague
if
they
really
run
this
scenario
and
if
yes,
then
we
have
to
think
about
changes
because
it
is
not
for
for
us
vm
and
sap.
We
do
not
use
this
scenario.
We
have
to
find
a
solution
that
does
edge
cases
come
to
a
situation
where
we
have
switches
that
others
can
yeah
right
now
it.
He
thinks
that
this
is
a
security
issue
for
my
point
not
but
yeah.
G
G
Yeah
but
yeah
he
should
now
right
yeah.
I
will
also
ping
my
slack
later
and.
B
Then
explain-
or
I
think
you
mean
like
get
up
issue
because
then
it
like
becomes
visible
or
we
are
waiting
on
close.
G
To
github
issue,
because
he
saw
that
it
was
a
security
issue,
there
should
be
something
attached
to
it
or
linked
to
so
linked
like
search
if
this
issue,
it
is
a
closed
issue:
okay,
private
yeah,
but
I
will
have.
I
will
contact
him
directly
and
from
now
the
list
on
the
very
left
side.
I
think
it's.
It
goes
now
in
this
yeah
in
this
area,
where
it's
hard
to
decide
yeah.
That
is
typical
thing:
okay,
also
from
tr
tre,
former
ua
colleague
from
ge.
G
Well,
I
simply
don't
know
if
we
really
should
support
this.
Ua
itself
is
in
a
mode
that
we
say
we
do,
of
course,
security
fixes.
We
try
to
bring
some
enhancements
from
op,
mighty
connect
or
from
these
standards,
but
ua
will
not
move
into
a
complete
new
authentication
service,
and
that
is
a
feature
that
is.
G
So
the
others
should
decide.
Therefore,
I
added
the
complete
group-
and
maybe
you
can
also
assign
the
maintainers
in
in
total,
that
they
see,
because
that
is
a
case
where
at
least
one
from
other
companies
should
provide
feedback.
B
B
G
But
it
is
useful
ua
that
you
have
this.
It
is
from
that
point
of
view
not
that
old.
We
have
many
issues
years
ago
created
so
yeah,
but
here
I
simply
need
someone
who
care
decides
if
we
should
bring
ua
in
a
new
position
wanted
to
have
to
change
the
database
model,
for
example
and
yeah.
G
I
think
some
experience
from
sap-
and
I
say
no,
we
should
not
move
into
such
a
direction
because
companies
which
run
ua
for
a
long
time
ago
have
existing
databases.
And
if
we
do
migration
of
these
data
models,
then
we
will
not
bring
only
sap
but
others
also
in
a
situation
where
we
have
to
think
about
how
to
migrate
to
this
new
model
and
so
yeah.
Therefore,
at
least
from
vmware,
peter
or
bruce
should
get
involved
here.
B
G
G
B
That's
good
shall
we
use
the
remaining
15
minutes
to
maybe
go
over
the
bush
issues?
B
A
F
Wish
you
excellent
in
a
few
celebrations,
yeah
and
yeah
see
you
in
january.
C
To
create
the
pr
and
the
to
do
sexually,
they
describe
code,
which
is
not
covered
at
the
moment.
There
are
no
unit
tests
and
I
was
surprised
from
where
the
todos
are
coming.
Or
do
we
still
need
to
do
so?
Yeah
who's,
gonna
do
those
studios.
I
mean,
I
don't
know
yeah
and
justin
just
created
the
issue.
I
think
we,
I
don't
think
we
should
strive
for
100
coverage.
C
Maybe
we
should
have
a
strategy
to
improve
the
test
when
we
touch
something
trying
to
have
100
percent
coverage
is
source
not.
A
A
D
A
I
think
that's
it
anything
else.
B
Because
otherwise,
I
give
you
all
a
bit
of
your
time
back
five
minutes.