►
From YouTube: Foundational Infrastructure Working Group [Nov 11, 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).
A
Okay,
welcome
all
to
the
third
foundational
infrastructure
working
group
meeting.
There's
a
lot
of
people
now.
So
that's
nice
shall
we
maybe
start
with
new
faces,
like
do
a
short
introduction
round,
so
everybody
knows
who's
who?
A
Okay,
I
will
start
I'm
reuben
koster.
I
work
for
vmware.
I've
been
active
in
the
cloud
foundry
ecosystem,
for
I
don't
know
eight
years
or
something
recently
joined
vmware
before
that
I
worked
with
stark
wayne
and
I'm
currently
the
tech
lead
for
this
working
group
together
with
leihan
leon.
Do
you
want
to
go
next.
B
Yep
hi,
I'm
behind
from
sap,
I'm
also
involved
in
the
cf
community
for
the
last
six
seven
years,
mainly
in
bosch
yeah
yeah.
C
Hi
yeah
joseph
palermo
working
for
vmware
been
doing
cf
stuff
since
about
mid-2010s.
I
think
currently
working
on
bosch
and
bosch
related
things
gareth.
How
about
you
next.
D
All
right,
so
I'm
gareth
also
vmware
been
in
cloud
foundry
since
2015,
something
like
that
I've.
I
have
worked
on
garden
data
services,
backup
restore
various
other
bits
and
pieces.
D
E
Hey
everyone
I'm
chris
clark,
I
work
for
the
cloud
foundry
foundation
and
yeah
I've
been
doing
that
for
a
good
five
years.
Now
it's
a
pretty
good
run
so
yeah.
If
you
need
anything,
you
know
technical
tool
related
or
anything
like
that
or
have
any
questions
at
the
foundation
you
can
reach
out
to
me.
F
Hi,
I'm
chris.
I
work
at
vmware,
I'm
on
the
docs
team.
I've
also
been
dealing
cf
related
things
for
since
20
2017
for
docs
and
yeah
just
working
on
anything
that
has
to
do
with
vmware
docs.
I
mean
old,
pivotal
docs,
so
you
know
touched
everything
before
bosch
and
whatnot
yeah
richard.
G
Well,
that's
what
chris
said,
except
when
we
go
back
to
2019
and
yeah.
I
touched
the
docs
bbr
docks
and
bosch
stocks
a
tiny
bit,
but
not
so
much
these
days
and
I'll
phone
to
samuel,
who
I
bet
is
gonna,
say
much
the
same
thing.
H
I
Hi,
my
name
is
ram.
I
work
with
chris
at
the
cloud
foundry
foundation.
I
am
officially
a
developer
advocate
there,
but
recently
I've
had
the
chance
on
working
with
everything
from
marketing
to
any
support
that
the
community
needs.
So
it's
been
fun
and
very
happy
to
see
and
meet
a
lot
of
the
other
folks
who
are
here
and
mildly
intrigued
about
a
lot
of
docs
related
folks
on
the
call
today
very
happy,
but
just
a
little
intrigued.
A
Okay
with
that
out
of
the
way
garrett,
do
you
have
enough
context
on
the
proposals
from
diego
okay?
Let's
dive.
G
A
The
first
one
into
the
first
one
I
mean
international
date
format.
That's
pretty
easy.
I
assume
that's
for
this
date
format
or
is
there
something
else
he's
referring
to.
A
Okay,
do
we
want
a
year
in
front.
D
A
Okay,
we'll
do.
H
A
D
So
maybe
we
want
to
be
deliberate
about
it.
Maybe
we
want
to
have
our
tech
writers
own
that
stuff.
A
That
makes
sense,
but
I
think
that's
more
of
a
broader
discussion
because
at
that
point
like,
if
then
you
probably
want,
maybe
even
a
dog's
working
group
or
something
right.
G
If
you'd
like
us
to
look
over
pls
and
such
you
should
continue
giving
us
access
to
these
repos,
even
if
you
move
them
around
a
bit,
I
think
that's
about
as
demanding
as
we're
going
to
be
in
terms
of
the
docs
working
group.
It's
unlikely
that
I
I
I
don't
think
that
there
is
powers
that
be
would
want
just
spending
that
much
time
on
this
stuff.
I
just
it
is
not
on
our
way
down
much
as
it
is
anyway.
So
that
means
there's
a
politics
discussion
I
guess
about.
G
If
there
were
an
actual
doc's
working
group
like
how
much
I
would
be
devoting
to
these
two
open
source
cloud
boundary
things
nowadays,
because
a
lot
of
a
lot
happened
since
we
were
assigned
to
this
sort
of
thing.
Can
you
do
do
samuel
or
christopher
wish
to
speak
to
that.
H
Yeah
I
mean
I,
I
don't
know
if
we
really
need
a
doc's
working
group,
because
we
don't
actually
do
any
work
on
these
docs
anymore.
We
only
merge
and
edit
pr's
and
we're
quite
happy
just
how
things
are
now
without
having
any
an
extra
meeting
to
have
to
attend.
A
A
Yeah,
I
mean
it's
not
up
to
us
as
in
I'm
okay
with
that,
but
we
have
to
create
a
pr
against
the
foundational
infrastructure
working
group
document
in
the
community
repo
and
then
the
toc
needs
to
be
decide.
They.
They
have
like
a
final
say
on
that
and
I
think
there's
a
similar
br
for
the
backup
and
restore
related
repos
right.
A
So
who
wants
to
do
that
work?
I
think
it
makes
sense
to
do
that
from
from
the
docs
people,
maybe
because
they.
A
Have
an
or
yeah
the
ask
is
from
them,
I
guess,
or
is
it
from
the
so
there's
this
repo?
I
will
just
show
and
there's
currently
a
pull
request
really
similar
to
move
zoom
out
of
the
way.
H
H
G
Okay,
that's
awesome.
I'm
also
happy
to
get
out
of
vantage
hopefully
classified
this.
Is
this
really
isn't
our
baby
anymore?
We're
happy
with
things
business
to
continue
as
usual,
and
if
you'd
like
us,
to
continue
work
on
ps,
just
make
sure
that
we
have
development,
permissions,
yeah.
H
We'll
we'll,
like
the
url
of
the
repo
change
or
anything.
D
H
D
A
A
And
what
we
do
with
that
this
list
is
used
so
to
auto,
assign
or
it's
currently
manual,
but
the
plan
is
to
eventually
auto
assign
people
from
that
pool
to
prs
that
are
incoming
right,
because
we
want
to
optimize
the
we
want,
all
the
pr's
to
be
quickly
reviewed
and
merged.
That's
the
whole
purpose
of
the
this
working
group
to
facilitate
the
contribution
workflow,
so
yeah,
so
so
that's
the
the
ask
we
ask
is
that
that
will
contribute
some
time
to
review
vrs
that
are
in
common.
H
We
actually
on
this
on
our
services,
docs
team.
Have
you
know
we
have
a
an
aim
to
sort
of
merge
and
edit
prs
within
three
three
days
and
we
are
currently
working
with
like
one
person
on
the
team,
who's
actually
working
on
services
stuff
each
week,
because
we've
got
other
projects.
So
I
mean,
if
you
were,
to
sort
of
auto
assign
it
it.
Probably.
It
could
possibly
be
a
different
person
working
on
the
pr
than
the
auto
assigned.
A
A
That's
how
they
set
up
this
whole
foundation
thing.
So
it's
and
we
still
don't
know
yet
really
how
that
works
or
translate.
So
what
we
have
in
the
bosch
team,
for
example,
is
that,
like
only
a
a
set
of
people
within
the,
not
all
the
people
in
the
team
actually
have
approval
rights.
A
A
Reassign
it
yeah,
you
could
really
assign
it
to
someone
else,
but
that
person
needs
to
be
an
approver.
H
H
A
And
that's
why
I
thought
maybe
it
makes
sense
to
make
this
pr
from
your
team
right,
because
you
know
the
people
and
their
handles.
I
mean
this
is
all
it
is
right.
It's
just
like
moving
it's
changing
this
document.
This
is
for
disaster
recovery,
it's
just
a
list
and
then
moving
some
vrs
or
some
repos
around.
A
But
I
think
in
this
case
it'll
only
be
two
two
repos
right,
so
there's
a
new,
a
new
heading
and
then
the
official,
the
repos
that
fall
under
this
area
and
then
there's
a
list
of
people
that
that's
like
all
there
is,
and
then
we
haven't
done
any
of
the
github
automation,
but
that
will
be
our
that's
still
being
worked
on.
So
these
things
are
not
enforced,
but
it
is
the
official
place
to
do
these
things.
A
H
J
A
Yeah,
I
think
the
we
can
go
over
the
boards,
but
so.
A
If
there's
going
to
be
a
separate
area,
that
probably
also
means
that
there
will
be
a
separate
board.
So
we
currently
have
github
project
boards,
where
we
review
those
things
or
the
things
that
come
in
like
new
pr's.
A
H
A
What
will
you
have
so
for
visibility,
like
one
of
the
objectives,
is
to
to
have
like
visibility
for
the
community
like
transparency,
and
that's
why
we
have
like
the
separate
projects,
but
this
is
all
like
still
a
bit
experimental,
but
the
aim.
So
this
one
is
some
a
project
we
are
actually
updating,
so
we
have
things
coming
in
in
the
inbox
and
that's
really
like,
and
then
we
assign
reviewers
from
that
pool
of
reviewers
and
then
they
go
through
this
board
and
eventually
the
pr
gets
merged
and
removed.
A
F
Just
a
clarification,
so
are
we
only
specifically
talking
about
like
the
bosch
and
the
bbr
repos?
Are
we
talking
everything
inside
cloud
foundry?
No,.
A
We
are
talking
about
everything
in
this,
so
there's
different
working
groups,
and
so
this
goal
that
you're
currently
attending
is
about
the
foundational
infrastructure
working
group
and
the
foundational
inc
foundation.
Infrastructure
working
group
has
a
bunch
of
people
with
roles
and
then
there's
different
areas
with
technical
assets,
so
vm
deployment
and
life
cycle
is
one
area
which
actually
is
porsche
and
then
there's
all
these
repos
there's
uaa
under
here
as
well,
krathop
and
integrated
databases
and
then
system,
logging
and
metrics,
so
that
all
falls
within
this
group.
A
Yes,
so
that
one
would
probably
should
be
moved
them
to
that
separate
area
for
the
docs
people,
but
that's
dogs
within
this
working
group
right,
so
there's
other
working
groups
as
well
and
they
have
dots
as
well.
So
you
would
have
to
attend
those
meetings
for
those
groups
and
then
fpr's
to
get
that
figured
out
as
well
right.
So
is
there
a
list
of.
A
Belong
to
which
group?
Yes,
that's
all
in
this
repo,
so
working
groups
and
then
there's
here.
The
different
groups
and
some
of
the
groups
are
still
under
pr
right.
So
they
are
still
being
reviewed
and
worked
on
working
group,
or
maybe
everything
got
merged
now
so
yeah.
So
there's
app
runtime
platform
and
runtime
interfaces
and
there's
probably
docs
in
here.
A
F
A
So
that's
why
that's
where
the
toc
comes
in
right,
so
the
toc
is
a
technical
oversight
committee
and
they
meet
every
week
and
they
decide
on
things
that
concern
multiple
groups.
So
if
you
want
to
have
like
a
standardized
way
of
doing
docs
or
maybe
create
a
separate
working
group
or
docs
right,
then
you
would
talk
to
the
toc
okay.
D
I
So
ruben,
if
I
may
just
interject,
could
you
open
the
pull
request
tab
that
you
have
open
and
if
you
scroll
right
down
to
the
bottom,
there's
number
150,
the
second
from
last
the
one
before
class
yeah
yeah.
A
I
Yeah,
if
you
go
to
like
the
file
yeah.
A
I
Just
to
give
folks
a
little
bit
of
background,
there
is
a
working
group
that
is
in
discussion.
So
to
say
this
is
one
of
the
working
groups
that
hasn't
been
fully
formed.
I
Yet
so,
just
by
way
of
background
cloud,
foundry
moved
from
having
a
pmc
based
governance
structure
to
a
toc
driven
governance
structure,
more
in
line
with
some
of
the
cncf
and
other
projects
have
been
doing
so
after
having
moved
like
elected
the
toc,
the
team
has
been
busy
in
creating
working
groups
for
different
areas,
so
the
toc
regularly
meets
every
single
tuesday
and
the
meeting
is
available
on
the
cloud
foundry
community
calendar.
So
if
there
are
folks
who
are
on
this
call,
who
would
like
to
join
that
as
well
you're?
I
More
than
welcome
to
it's
an
open
call,
folks
can
come
in
and
air
any.
You
know
issues
they
have
or
contribute
any
ideas
they
have
or
what
have
you
so
it's
fairly
open.
So
past
meeting
recordings
are
available
on
youtube.
If
that's
a
little
tedious,
there's
also
like
a
link
to
the
notes
in
the
hashtag
toc
channel
on
slack,
so
you
can
definitely
get
access
to
that.
I
But,
generally
speaking,
there
is
a
working
group
that
the
toc
has
in
mind
that
will
focus
on
community
assets
and
public
facing
assets,
particularly
documentation,
and,
as
you
can
see
from
the
state
of
this
particular
pr,
there
hasn't
been
much
progress
on
that
front.
So
this
is,
you
know
who
we
expect
that
will
sort
of
be
responsible
for
a
lot
of
the
documentation
work,
but
we
don't
have.
I
What
can
I
say
we
don't
have
closure
on
this.
We
don't
even
have
like
a
beginning
on
this,
so
if
folks
here
have
an
opinion
or
would
like
to
participate
in
that,
you
are
more
than
welcome
to
do.
F
I
No,
so
that's
a
time
zone
problem.
I
guess
there's
one
meeting
every
tuesday.
F
I
So,
on
the
community
calendar
there's
a
10
30
to
11
30
a.m.
Meeting
for
the
eastern
time
zone;
okay,
that's
the
one
I
would
want.
Thank
you.
A
Yeah,
so
maybe
it
makes
sense
to
have
a
pr
against
this
foundation
against
the
foundational
infrastructure
working
group,
but
maybe
it's
also
better
to
first
join.
The
tlc
meeting
have
the
broader
discussion
there
and
then
we
can
move.
Maybe
some
things
over
to
a
separate
working
group
which
I
think
is
more
in
line
with
what
you
actually
want,
because
then
it's
global
right,
it's
globally
scoped
and
all
the
working
groups
will
adhere
to
that.
H
A
Then
we
will
just
continue
with
going
over
at
least
the
bore
specific
stuff.
Are
there
any
they
on?
Are
there
any
requests?
Do
you
think
that
need
special
attention?
I
think
we
have
merged
quite
a
few
things.
A
B
Are
all
fresh
I
reviewed
today
the
vrp,
the
openstack
cpi,
one.
B
Yeah,
what
about
the
one
regarding
the
cpi
works?
It
has
been
that
much
already.
B
Cpi,
the
the
walks,
the
cpi
walks
yeah
yeah,
that
one.
B
Yeah
because
yeah
we
that
one
had
two
reviews,
two
approvals
that
was
yeah
ready
to
be
much
fun.
Yeah.
A
So
yeah,
I
don't
think,
there's
much
here
to
discuss.
I
did
some
work
on
the
new
github
projects
got
some
automation
to
to
sync
all
the
open
issues
to
here,
but
it's
still
missing
some
some
functionality.
So
I
will
just
keep
experimenting
with
this
because
there
it's
in
beta,
currently
the
plan
for
us
to
to
move
to
this,
is
or
why
this
would
be
useful.
A
Is
that
there's
a
hope
that
we
would
be
able
to
have
all
projects
in
one
or
all
areas
in
one
view,
and
then
just
use
fields
to
filter
things?
So
we
can
have
different
views.
Customized
customized
views,
but
look
at
the
same
list
of
things.
A
A
So
this
one,
I
think,
just
got
approved
or
something
and
then
like
it,
jumps
to
a
different
column
automatically.
So
yeah,
that's
quite
nice.
We
don't
have
to
do
it
manually.
A
F
A
J
J
Cool
cool
I'll
catch
up
with
those
folks
later
on.
Thank
you.
A
Okay,
if
there's
nothing
else,
I
think
we
can
I'll
get
some
time
back
for
a
day.