►
From YouTube: 2020-09-09 Multi-Large Working Group
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,
let's
get
started
so
I
rescheduled
this
meeting
because
monday
was
a
holiday
in
the
us,
and
so
I
figured
there
would
be
a
bunch
of
people
that
wouldn't
show
up
that.
I
really
wanted
to
show
up.
So
I
took
the
risk
of
just
rescheduling,
so
bfs
for
pages
and
fs
is
on
its
way
to
production.
A
This
was
a
thin
layer
that
jekyll
did
a
a
poc
for
which
allows
us
to
essentially
hide
what's
behind
the
disk
access
layer,
which
is
great
because
it
should
enable
us
to
do
the
various
things
that
we
need
to
do
and
originally,
when
we
talked
about
it,
I
I
thought
that
was
the
the
best
thing
to
be
able
to
handle
migrations
very
gracefully.
A
So
I'm
happy
to
see
that
hidden
production
at
some
point
soon
and
then
gregor's
finished
the
the
two
blueprints
for
the
gitlab
pages
architecture
and
then
the
guild
box
what's
happening
next
is
there
is
work
to
decouple
puma
from
pages
nfs,
and
then
I
know
there
is
work
happening
to
improve
observability
for
the
build
logs,
so
we're
making
progress
there
and
then
marion.
A
Just
let
me
know
that,
there's
something
else
that
apparently
uses
nfs,
which
is
the
mailer
queue
which
rachel
is
going
to
be
chasing
for
us,
so
we'll
have
more
information
come
next
week
to
understand
what
the
work
is
involved
in
and
removing
that
all
right.
A
So
the
one
item
that
I
had
for
discussion
was
that
in
looking
at
the
epics
and
the
work
that
is
plotted
or
that
is
planned
from
here
to
mid-october-
it,
it
sounds
to
me
like
nfs-
should
be
gone,
not
from
gitlab.com
from,
but
that's
our
requirement
for
the
product
to
operate
under
kubernetes.
A
B
Yeah,
I
just
added
a
page:
a
distribution
here
actually
consolidated
a
list
of
the
bloggers
for
deploying
pages
on
kubernetes.
In
addition
to
those
two
issues
and
epics
you'll
code
out.
A
All
right,
well,
the
working
group
will
continue
to
meet,
so
I
will.
I
will
track
those
three
items
and
then
I
would
imagine
that,
probably
in
the
first
week
of
october,
this
one
will
will
start
gearing
up.
You
know
we'll
have
a
better
idea
of
when
these
items
are
completed
and
the
way
I'm
thinking
about
this
is
when
we
we
put
together.
The
working
group.
Gitlab.Com
is
kind
of
part
of
this
equation,
but
not
a
blocker,
and
what
we
mean
by
that
is
that
we
know
gitlab.com.
B
A
Yeah
again
I'll
I'll
taste,
all
of
that,
but
as
a
general
idea,
it
looks
like
mid-october
is
when
we
all
think
we
would
be
down
with
a
bunch
of
these
things.
A
B
Increase
the
visibility
to
the
pm
I'll
call
it
out.
That'll
be
great.
Let
me
look
the
history
of
that
epic.
There
is
some
chatting
there
to
schedule
or
prioritize
those
items
for
the
pages,
so
those
are
the
things.
What
are
down
the
helm
chart
will
be
unblocked
earlier,
so
we
don't
have
to
wait
until
next
mid
next
year.
A
There
is
no
no
specified
date,
but
I
will
mention
that
to
eric
like
based
on
the
the
progress
that
we're
making
and
the
work
that
is
happening.
These
look
like
kind
of
the
dates
where
we
might
be
able
to
start
doing.
You
know
the
next
few
large
milestones
and
then
see
what
the
feedback
on
that
is
so.
C
Yeah
and
the
other
way
I
approach
it.
The
way
at
least
I'm
approaching
from
our
site
is,
is
our
great.
Our
dates
are
aggressive
and
if
we're
off
by
a
month,
then
that's
acceptable
from
that
perspective,
as
opposed
to
hard
dates
where
we
really
need
to
hit
it
on
the
mark.
So
if
you're
getting
if
you're
getting
visibility
january,
that's
one
discussion
like
if
we
had
you
know
we
hit
october
and
then
we
actually
end
up
in
november.
To
me,
that's
just
normal.
C
You
know
unknowns
that
kind
of
come
up,
but
if
we
need
to
be
ready
by
november
1st
and
and
there's
money
riding
on
it,
then
that
that
level
of
that
level
of
expectation
expectation
definitely
needs
to
be
pushed
with
product.
So
they
understand
it.
A
A
A
A
Right
and
I
think
we're
setting
expectations
based
on
how
we
see
things
progressing.
So
if,
if
the
data
we're
offering
to
eric
and
sid
and
and
scott
makes
sense,
then
I
think
everybody's
comfortable.
I
will
keep
also
following
up
on
that
from
time
to
time,
with
with
eric
just
to
make
sure
that
there
are
no,
oh,
my
god.
No,
we
expected
this
like
three
weeks
ago
so
anyway,
not
that
that's
ever
happened
all
right.
A
So
the
only
other
follow-up
item
that
I
had
was
that
gregor's
mentioned
that
we
don't
have
a
specific
dri
for
the
pages.
Nfs
work
there
at
least
three
people
that
I
know
have
been
working
on
various
aspects
of
this.
A
We
had
a
conversation
in
the
architecture,
kickoff
group
as
to
what
exactly
that
meant-
and
there
was
a
little
bit
of
confusion
in
interpreting
the
whole
relationship
between
okay
arts
and
blueprints
and
whether
it
would
be
senior
folks
that
would
be
owning
these
things
I'll
try
to
find
those
with
eric,
but
I
just
wanted
to
make
sure
the
group
is
comfortable
with
you
know.
This
work
is
fairly
complex,
so
to
have
a
single
vri.
A
I
don't
know
if
it's
makes
sense
or
not.
If
nothing
else.
A
I
am
apparently
the
one
drive
for
this
entire
working
group,
so
I
can
continue
to
chase
these
things
and
just
sort
of
keep
taps
on,
like
I'm
comfortable
with
several
people
working
on
these
several
aspects
without
having
to
have
a
single
ic
that
owns
the
entire
pages
and
nfs
so
but
christopher
I'll
follow
up
with
nicole,
and
you
know
if,
if
we
do
decide
to
put
somebody's
name,
then
we'll
do
it.
If
not
we'll
just
continue
as
we
are
today.
C
Yeah-
and
this
is
I
want
to
make
on
this
one-
I
want
to
make
a
distinction
between
technical
decisions
and
like
execution,
obviously
they're
married
to
a
certain
extent,
but
you
know
nicole,
should
have
a
pretty
good
grasp
and
like
on
the
not
424
4283,
but
on
the
pages
side
on
her
side,
she
has
pretty
recent
update
on
status
actually
of,
I
think,
as
of
today
kind
of
what's
being
worked
on
versus
not
worked
on.
C
So
I
feel,
like
I
feel,
like
we've
got
good
status
for
that
piece
of
it
in
place.
Distribution
team
obviously
has
some
additional
work.
It
sounds
like
that.
We've
got
to
make
sure
kind
of
lines
up
from
that
perspective,
and
you
know
are
very.
We
have
some
variants,
obviously
with
unknowns
from
that
perspective,
but
talk
to
nicole
and
let
me
know
what
your
thoughts
are
and
if
we
need
a
technical
dri,
we
can
do
that
as
well.
A
Yeah,
I
think
it's
probably
the
execution
dri
I
mean
this
all
came
from
crackers
and
some
of
the
comments
he
made
to
me
about
you
know
these.
Various
people
are
are
working
on
this.
I
think
from
a
technical
standpoint,
that's
going
to
be
really
hard
right,
because
I
mean
we've
had
some
really
smart
people
working
on
this
problem
and
you
know
they've
done
pocs
and
all
that
and
finally,
they've
reached
a
decision
of
it's
been
a.
I
wouldn't
say
that
it's
been
consensus-driven,
it's
been
very
data-driven
and
it
was.
A
A
Talk
to
nicole,
yes,
cool!
Thank
you.
I
don't
see
any
other
items
so
unless
anybody
has
any
last
minute
things
we
are
done
for
today,
cool.
Thank
you.
Everyone
later.