►
From YouTube: 2021-02-08 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
Is
8
30
a.m?
Pacific
time
good
morning
ever
good
morning
good
afternoon,
everyone
today
is
2020
2021
february
days.
This
is
the
multi-large
working
group
meeting.
So
let's
get
started
to
look
at
the
agenda
this
week.
A
Sorry
about
that,
I
was
looking
at
the
other
dock.
Okay.
The
first
item
is
a
what
has
been
done.
First,
one
is:
are
we?
I
have
created
two
habits
for
next
steps,
which
is
one
epic
for
the
web.
Api
knows
to
move
web
api
nodes
to
the
to
on
a
dot
com
to
using
the
home
chart.
The
other
one
is
the
pages
nodes
right
now,
they're
blank.
I
have
another
item
when
is
to
happen
next,
so
we'll
discuss
later
steve.
A
No
stevens-
I'm
here
I'm
going
to
read
his
item
here,
so
the
merge
request
of
the
working
group
actually
criteria
and
the
new
facilitators
are
was
merged
last
week.
So
I
will
be
the
new
dri
or
a
facilitator
for
this
working
group
and
amy
will
be
helping
me
together
to
work
on
both
sides.
A
B
Yes,
so
like
we
started
migration
of
pages
on
production
on
friday
about
I
think
evening,
and
it's
going
pretty
well.
B
B
If
you
are
more
interested
about
our
thoughts
about
that
process
and
like
what
we
are
considering
it's
actually
in
this
issue,
but
actually
we
are
kind
of
now
trying
to
connect
dots
because,
like
it
seems
that
in
some
cases
we
have
like
two
data
sources
of
the
blogging
information,
and
we
are
trying
to
understand
if
we
can
connect
them
together.
B
Like
are
we
kind
of
confident
enough
in
this
the
process
so
far
whether
we
want
to
continue
like
finishing
this
run
or
whether
we
want
to
restart
the
whole
process
again,
even
though,
because
it's
pretty
fast
to
be
honest,
it's
a
little
faster
than
we
kind
of
anticipated.
So
I
mean
we
are
considering
how
safe
we
want
to
be
versus
how
iterative
we
want
to
be
on
this
migration
brent.
You
have
the
question.
C
Yeah,
so
I
know
that
alejandro
and
ahmad
are
helping
here,
but
is
there
any
additional
assistance
you
need
it
on
this
issue
at
this
time,.
B
I'm
kind
of
like
thinking
that
we
had
some
period
that,
like
the
time
zone,
was
like
a
a
key
factor
that
was
making
us
a
little
slower,
but
I
think
us,
I
think
it's
going
pretty
fine
right
now,
because,
like
it
did
move
we
are
migrating
data.
B
I
know
that
what
vadim
like,
if
it's
really
needed,
he
just
asked
sre
encore
to
provide
us
locks.
So
I
guess
like
at
this
point
we
are
fine,
but
I'm
I'm
kind
of
anticipating
that
we're
gonna
need
more
like
and
holding
with
the
sre
probably
later
in
this
week.
C
But
it
sounds
like
you
might
need
some
support
from
somebody
like
an
emea
time
zone,
so
I
can
look
to
transition
from
from
more
alejandro
focus
to
ahmad,
because
ahmad
is
coming
off
call.
So
he
should
have
some
more
cycles
and
he's
he's
in
central
european.
So
that
might
be
more
conducive
to
this
effort.
B
D
Emil,
can
I
interrupt
you
for
a
sec
before
you
continue
with
this
other
topic?
I'm
I'm
wondering
do
you
need
any
help
to
decide
which
path
to
go
because
you
have
two
options,
so
I
didn't
really
understand
whether
you
need
help
to
make
a
decision
or
you're
just
presenting
that
there
are
two
options.
B
B
Like
it's
described
in
clear
what
challenges
we
have
the
current
data
and
if
you
have
some
suggestions
like
about
the
best
way
or
like
the
preferred
way
or
how
safe
we
want
to
be
on
this
process,
feel
free
to
to
post
a
comment
there.
Well,
thanks,
we
haven't
decided
on
that.
Yet
it's
something
it's
something
that
we
are
considering:
we're
kind
of
monitoring,
gathering
data
and
like
looking
how
far
we
can
reduce
the
current
data
versus.
B
I
guess
sit,
I'm
supportive
as
long
as
well
documented.
Yes,
I
I
believe
it's
gonna
be
documented
yeah.
F
Very
happy
to
announce
that
the
cloud
native
get
lab
officially
has
complete
support
of
the
functionality
of
gitlab
pages.
It
has
a
long
road,
it
has
been
challenging
and
it
has
been
many
parts
of
get
lab
to
contribute
to
this.
We
are
extremely
happy
because
we're
going
to
have
many
very
large,
very
happy
customers
as
a
result
of
this.
F
E
Yeah,
it's
really
awesome
and
it's.
It
sets
gitlab
up
for
continued
growth,
as
people
move
to
cloud
native
and
four
months
ahead
of
schedule.
I
don't,
I
don't
think
I
know
of
a
project
that
did
that.
So
thanks.
Everyone
was
clearly
a
team
effort,
but
I
I
think
I
also
want
to
call
out
camille
his
architecture
decision
on
good
lab
pages
that
turned
out
really
really
well.
F
I
will
go
ahead
and
point
out
that
any
fresh
installs
into
the
cloud
native
won't
have
legacy
storage,
so
this
won't
actually
be
a
particular
problem.
Migrations
from
traditional
to
object,
storage
for
the
backing
are
still
in
play,
and
we
will
eventually
have
to
handle
that,
but
at
least
for
those
customers
doing
new,
the
functionality
is
in.
F
F
G
Yeah
thanks
and
yeah
big
congrats.
For
that
I
I
fear.
How
can
I
follow
that
really?
I
know
the
page's
effort
has
been
vast,
so
it's
really
good
to
see
that
moving
forward
yeah.
It's
just
quick
knock,
as
we
mentioned
in
this
workout
before
about
our
recent
progress
on
with
the
the
gitlab
environment.
G
Toolkit
we've
released
our
beta,
which
was
a
big
kind
of
polishing
effort
to
get
it
really
kind
of
a
state
where
our
users
can
actually
use
themselves
with
their
own
environments,
whereas
before
it's
kind
of
it
was
a
lot
more
had
baked
in
config
and
stuff
like
that,
so
that's
all
been
done,
so
we're
ready
for
people
to
start
using
it
in
their
teams.
We
encourage
anyone,
who's
interested
to
head
over
to
our
slack
channel
or
to
read
the
docs
and
hopefully
be
able
to
give
it
a
go
yourselves.
G
D
Grant
well,
while
we
have
you
here,
I
wanted
to
let
you
know
that
we
are
considering
using
get
for
our
secondary
site
in
staging
and
for
the
secondary
geosite
in
staging,
and
that
will
mean
that
we'll
probably
provide
sufficient
work
for
you
for
days
to
come,
because
we're
probably
going
to
find
bunch
of
bugs
not
because
we're
looking
for
bugs,
but
because
we
have
things
that
we
need
in
infrastructure.
D
So
I'll
keep
you
updated
on
that.
But
are
you
the
only
engineer,
working
on
get
full
time.
G
Full-Time,
I
guess
strictly
yes,
but
we
do
have
our
team
members
helping
to
contribute
and
maintain.
So
I
heard
from
my
colleague
nick
about
the.
B
G
B
Yes,
like
we
continue
basically
like
with
discussing
and
like
fixing
edge
cases
and
like
I,
I
think
it's
like
on
the
good
track
to
finish
pretty
soon
so
john.
What
about
you.
A
Yeah,
so
my
my
item
is:
actually
we
need
to
flash
out
the
items
that
needs
to
happen
to
move
the
web
api
and
the
pages
notes
to
help
chart
christopher.
You
have
a
question:
do
you
want
to
verbalize.
I
Yeah,
I
just
want
to
know
where
you
need
help,
if,
if
you
need
any
help
for
me
to
make
sure
to
drum
up
the
right
teams
and
and
whatnot.
A
Here's
somebody's
thinking,
I
think
first
thing
to
happen-
is
to
for
infrastructure
team
to
figure
out
what
needs
to
happen
to
migrate.
The
the
nodes
to
home
chart
then
start
from
there.
We
can
sort
out
what
operational
tasks
are
and
what
the
development
work
are
to
facilitate
those
actions.
So
the
first
step
I
see
is
what
needs
to
happen
to
move
those
nodes.
J
And
we
have
a
couple
of
blockers
that
we
know
about
already,
mostly
at
the
moment
for
the
api.
We
know
about
logging,
it's
most
likely
to
be
the
challenge
as
we
move
on
to
we'll
move
to
canary
and
then
we'll
be
able
to
see
kind
of
the
full
extent.
But
we
have
two
blockers
open,
which
I
can
link
in.
A
E
A
I'm
calling
for
help
from
amy
your
team
or
the
infrastructure
team
to
sort
out
what
needs
to
happen
from
you
know,
step
one,
two,
three,
four:
to
move
those
nodes
from
infrastructure
perspective,
the
start
from
there.
I
think
the
development
team
can
figure
out
what
functionalities
are
missing
to
make.
Those
things
happen.
J
Yeah,
we
can
certainly
take
a
lead
on
on
looking
at
what
we'll
need
for
that
it'll
be
helpful
to
know
which
stage
groups
to
work
with
from
a
kind
of
like
key
application
point
of
view,
so
we
can
bring
them
in
as
well.
A
Yes,
thank
you.
Would
you
mind
to
actually
you
know,
you
know
the
listing
soliciting
the
infrastructure
folks
to
figure
out
what
our
next
steps
for
those
movements
for
those
unknowns.
So
actually
that's
a.
I
feel
that
development
team
may
not
have
a
clear
clue
what
needs
to
happen
on
the
you
know
in
the
infrastructure.
D
That's
that's
also
not
expected
from
development
teams,
so
the
the
work
is
being
done
by
the
delivery
team.
So
next
week
we
are
kicking
off
that
migration,
which
means
all
the
planning
is
going
to
happen
during
that
period.
So
once
we
have
those
details
we'll
be
able
to
share,
but
right
now
we
have
a
couple
of
items
that
we
need
to
wrap
up
before.
We
continue.
A
Great,
let's
make
sure
that
we
link
or
add
those
issues
to
the
epics,
whichever
they
make
sense.
So
we
have
one
place
to
look
for
what
needs
to
happen.
Well,.
J
I've
linked
those
together,
so
I've
added
in
the
main
working
epic,
where
we
have
all
of
the
issues
that
we'll
be
picking
up
from
delivery
side.
We've
also
got
the
blockers
for
each
stage
listed
out
there
as
well,
but
I'll,
add
a
comment
that
ties
that
together.
A
Okay,
I'll
sort
out,
what's
the
best
way
to
manage
those
issues
in
ideally
one
place,
but
I
know
there
are
restrictions
like
the
infrastructure
project
is
separate
from
the
different
arc
project.
So
sometimes
we
have
to
maintain
two
wars.
D
Well,
maybe
we're
escalating
again
to
products
that
we
can't
do
cross
group
epics.
There
is,
I
think,
already
a
couple
of
escalations,
so
it
might
be
worth
mentioning
one
more
time.
D
I'll
I'll
find
you
the
epics
where
this
is
talked
about.
Thank
you.
I
H
I'll
just
I'll
write
it
down
that
we're
hoping
they're
hoping
to
have
the
operator
beta
release
in
1310,
so
that'll
be
pretty
exciting
for
folks.
So
I'm
not
going
to
get
that
out.
Thank
you,
jason
for
capturing,
but
a
combination
of
a
couple
releases
of
work
here
and
we're
seeing
continued
progress
towards
adding
additional
or
remaining
services
to
the
operator.
A
A
Okay,
steve
discussion
item.
E
Yeah,
just
just
wanted
to
offer,
thanks
to
john
and
amy,
for
smooth
switch
to
the
facilitation
and
and
the
changes
to
our
our
scope
and
everything
this
last
week
so
awesome.
Thank
you.