►
From YouTube: Geo Scheduling Call - 2020-02-10
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
A
B
B
A
B
B
A
B
B
B
A
B
B
Means
nothing
gets
forgotten
and
we
know
that
it
was
done.
Ok,
this
was
also
staging.
The
replication
was
lagging
on
staging,
so
we
switched
I
think
we
have
switched
to
streaming
or
application
now.
I
think
we
have
here,
and
we
also
decided
that.
Oh,
that
was
also
the
thing
I
turned
out.
That's
streaming
didn't
actually
solve
everything,
I
need
to
double-check
and
reread
everything,
but
we
need
to
review
how
we're
doing
certain
database
queries
at
scale.
Yes,.
B
B
C
B
B
A
Really
like
I
mean
it's
sometimes
for
me,
easy
to
forget
that,
like
a
few
months
ago,
like
four
or
five
months
ago,
we
we
didn't
do
any
of
this
and
we
didn't
have
a
clear
understanding
of
how
to
do
it
either.
And
now
we
have
a
process
whereby
this
happens
every
month
and
that's
very
nice,
I
think
I
think
we
made
a
really
nice
improvement
over
time
here.
So
happy.
A
B
A
B
B
A
B
B
B
B
B
B
A
B
A
B
Just
I'm
interested
as
to
how
it
how
it
happened
in
the
beginning,
because
I
don't
think
that
this
code
was
new.
I
might
be
confusing
to
issues
though,
but
that's
why
I
wanted
to
go
into
it
and
double
check,
because
I'm
interested
as
to
how
we
only
found
it
now
or
if
it's
like.
If
it's
something
that's
been
in
there
for
a
while,
and
we
just
didn't
push
the
button.
So
we
didn't
know
that
I
think.
A
B
B
B
B
B
B
B
Maintainer:
okay,
it's
moving
along
we're
getting
there.
That's
our
first
piece
of
work
for
wiki,
sorry,
forum
backup/restore
as
well.
I,
don't
know,
okay,
improve
reference
counter.
This
was
part
of
the
production
problem
that
they
had
with
doing.
The
hash,
storage,
migration
and
Gabriel
was
dead
done
some
work
of
arts
improving
the
reference
counter.
A
A
New
merge
request
that
actually
handles
fork.
Networks
has
been
merged,
which
is
great
news,
but
now
the
backfill
actually
still
has
to
be
merged
because
we
need
to.
We
need
to
like
do
this
for
all
repositories
and
when
that's
done,
we
can
I
think
we
can
merge
our
our
pruning
tasks,
because
then
that
should
be
fine.
Okay,.
A
B
A
B
A
B
Induce
yeah
things
in
developments,
okay,
adding
the
service
to
the
checksum.
Would
you
add
service
to
check
some
of
the
package
files
on
the
primary,
so
I
know
that
Valyria
had
picked
this
one
up?
I,
don't
expect
he's
gotten
too
far
with
us.
If
he's
had
other
things
that
he's
been
working
on
as
well,
that's.
B
Okay,
adding
monitoring
to
staging
I
need
to
see
where,
where
people
I
put
this
one
because
I'm
sure
there's
been
movement
and
I
just
haven't
gone
through
my
emails,
it
planned
failover
using
GHA.
I
know
that
this
is
our
nationÃs
for
this
week,
fingers
crossed
he
gets
there
improve
the
logging
of
sync
services.
I
saw
in
Ash's
update
this
morning
that
he
was
working
on
this,
so
I
think
that's
active
and
in
progress
this
one
I
contacted
Craig
to
talk
about
what
shape
of
infrastructure
we
need
so
that
we
can
start
costing
that
and
he's.
B
A
B
I'm
also
hoping
that
the
group
conversation
might
also
be
a
spot
to
get
the
inputs
that
we
need
there,
okay,
rewriting
the
form
in
view,
I
think
this
one
has
been
around
for
a
little
while
now,
let's
just
have
a
look
at
the
major
quest:
okay,
this
one's
active,
nine
and
that
one's
on
work
in
progress.
So
this
one
looks
like
it's
with
Clement
so
and
it
will
be
backwards.
First,
one
okay
Gio,
fails
to
replicate
avatars.
This
was
the
bug
that
tone
was
looking
in
for
a
customer
mm-hmm.
B
B
Add
to
my
list
of
stuff
to
have
a
look
at
after
the
call,
because
we'll
need
to
do
something
can't
wait
for
him,
so
we'll
figure
out
something
else.
Oh
we
can
do
here.
Okay,
enable
object,
storage
on
secondary
node
on
staging
I
need
to
read
out
more
about
this.
This
is
shown
of
recently
and
last
one
track
investigate
the
orphaned
repositories
in
the
tracking
database
named
is
interesting.
I'll
have
to
go
read
up
as
to
what
that
is,
because
there's
also
showing
up.
That's
click.
B
B
Well,
it
was
expected
that
we
would
find
things.
Yes,
we
just
need
to
finish
kneading,
Craig
and
Dave,
and
so
that
they
can
go
back
to
their
teams
like
actually
get
to
a
point
that
we
don't
need
them
as
much
anymore.
So
I'll
try
posting
with
Douglas
and
see
what
we
can
do
see
what
we
needs.
Don't
let.
C
A
A
All
right
that
seems
up-to-date,
okay,
so,
let's
start
at
the
top.
This
is
a
small
improvement
where
we
don't
display
the
right,
UX
and
the
right
design
component
here.
So
it
should
be
a
model,
but
it
isn't
right
so
I
think
sintering
has
proposed
that
we
actually
changed
this
and
I
believe
there
is
there.
A
I
missed
but
I
just
said
it
I
agreed,
yeah
I
mean
I.
Think
we
can.
We
can
pick
this
up.
I,
don't
I,
don't
mind
it's
one
of
these
small
iterative
improvements.
It's
not
the
most
important
thing,
but
I
think
this
is
something
that
I'll
just
put
it
at
the
bottom,
but
this
will
be
picked
up
by
Zack
when
he
has
time
so.
I
think
that's!
Okay,.
A
Yeah,
this
was
a
weird
bug
that
custom
encountered
where
that
is
very
similar
to
something
that
I
think
Valeri
encountered
on
the
docker
repositories,
where
essentially,
we
can't
download
NFS
files
from
a
primary
when
it's
in
s3
with
our
proxy
download.
So
the
way
I
understand
it.
It's
like
this
is
not
particularly,
it
should
just
work
and
it
doesn't
and
we
should
fix
it
so
I
think
it's
fine
to
have
it
in
here.
If.
B
B
B
A
A
B
A
C
B
B
A
In
that
light,
we
can
maybe
do
a
little
bit
of
shuffling
here.
These
two
things
are
too
difficult
and
I
think
that
the
distribution
team
depends
on
this
to
certainly-
and
so
it
actually
put
them
at
the
top
here,
because
we're
also
unblocking
other
folks
with
this
I'll
move
this
down
just
for
visibility,
because
this
is
already
this
way
demo
install
in
govt
ahem
chart
it's.
B
B
A
B
B
B
A
That's
fine
that,
and
so
the
thing
is
if
I
review
this.
This
is
certainly
the
least
important
thing.
If
that's
just
a
nice-to-have
item,
you
know
the
documentation.
Change
is
like
if
somebody
had
time
this
year
is
something
that
is
for
Jenny.
This
is
for
for
Zach,
so
I'm
happy
to
keep
them
in
here.
This
is
a
I
think
relatively
impactful
like
bug,
fix
and
happy
with
it,
and
these
are
two
deliverables
which
are
at
the
top,
which
are
also
I.
Think
one
of
the
most
important
things
we
can.
A
The
package
file
replication
so
as
far
as
I
understand
this
is
really
like.
I'm,
not
100%.
Sure
like
these
are
these
these
three
items
here
and
those
should
have
been
worked
on
already
in
the
spike
and
so
I
think
what
is
missing
from
them
here
is
not
the
entire
implementation
is
testing
and
actually
closing.
B
A
B
A
B
B
A
A
So
so
this
is
like
a
little
bit
like
I.
Haven't
really
I
mean
I'm
doing
this
now,
but
some
things
may
change
so
I
made
some
comments
right.
So
in
essence,
I
think
for
12.9
I
feel
like
sort
of
theme
of
this
release
will
be
continuation
of
things
that
we
are
doing
in
12.8,
plus
the
sprinkling
of
additional
like
features,
because
I
think
none
of
the
things
like
like,
essentially
all
the
things
that
may
slip
in
12.8
will
be
the
priority
to
be
delivered
in
12.9.
A
They
will
not
go
away
all
right,
so
I'm
I'm
not
going
to
just
not
do
with
them,
and
we
just
have
to
finish
them
right
and
so
in
terms
of
how
I
think
this
should
look
for
calm,
so
geo
is
enabled,
but
they
are-
and
this
is
not
a
surprise
right.
This
is
I-
think
something
you
predicted
in
your
infinite
wisdom.
Like
last
night,
like
we
didn't
quite
like
I,
don't
know,
maybe
we'll
get
the
monitoring
done,
but
that
is
something
that
may
may
slip,
but
I
think
darkness
is
on
it.
A
So
that's
actually,
let's
say
that
may
make
it,
but
for
12.9,
I,
think
the
update
strategy
right
and
the
documentation
are
the
two
items
that
are
outstanding
in
order
for
us
to
actually
close
this
out,
and
if
we
look
at
the
issues
here
or
the
ones
that
I
think
are
most
relevant.
So
this
one
here
is
as
far
as
I
know,
the
only
thing
that
is
outstanding
to
close
this
one,
which
is
sort
of
a
metal
issue.
Yeah.
B
A
A
That
may
not
actually
happen,
and
these
here
may
be
Direction
items
for
for
twelve
point:
nine,
because
I
think
those
are
the
big,
the
big
items
and
then
we
talk
actually
I
think
about
all
of
those
sort
of
three
items
here
which
are
sort
of
generated
by
a
Douglas
while
working
on
it,
so
I'm
not
going
to
label
them
Direction
items
or
deliverables,
because
this
would
have
happened
more
dynamically
if
that
makes
sense.
Yeah,
but
I
expect,
like
my
hope,
is
that
in
12.9
we
could
just
completely
close.
A
Now
the
big
one,
so
we've
done
quite
a
bit
of
work
on
this
service
framework
and
I
think
into
F
port
9.
We
kind
of
need
to
double
down
on
that
and
I
think
this
is
now
like
this
is
where
it
becomes
a
little
bit
challenging.
I
just
highlighted
we're
going
to
do
a
target
contribute
right
and
we
said
we
want
replication
and
verification.
So
the
way
I
see
this,
they
are
essentially
in
12.9
the
following
things
that
we
need
to
do
we
need
to
like.
This
is
something
we
discussed
here.
A
These
are
the
three
items
that
may
slip
from
12.8
I,
don't
know
yet
they
may
not
mine,
but
those
will
need
to
happen,
but
these
are
the
ones
that
are
here
actually
I.
Think
I
forgot
about
that
one
here
then
this
one
here
is
the
I.
Didn't
this
one
is
the
last
outstanding
item
for
the
replication,
I
think
right
so
I
think
in
12.9
we
should
be
able
to
close
replication
off
completely
for
verification
we
have
like.
A
B
C
B
B
A
That's
fair
this
one
here
I
would
just
keep
in
because
that's
something
for
a
sec
and
it's
like
it's
like
a
machine.
He
needs
to
be
like
yeah
and
so
yeah,
but
that's
fine,
but
then
we
could,
for
example,
this
one
and
this
one.
If
we
wanted
to
be
a
little
bit
proactive
right,
these
are
two
items
that
we
could
actually
already
put
into
into
the
billboard.
If
we
wanted
to,
but.
B
B
A
These
are
the
three
verification
of
verification:
reputation,
yeah
I
haven't
marked
them
deliverable
by
the
way.
Yet
because
that's
something
we
still
have
to
decide
on,
but
the
point
is
that
there
is
a
good
amount
of
work
here
in
the
verification
side
of
things.
So
we
should
be
mindful
where
we
spend
our
deliverable
labels.
I
personally
think
we
should
spend
them
here,
because
then
we
can.
We
have
a
talk
coming
up
at
contribute,
so
this
is,
you
know,
focus
area.
A
B
C
B
Doesn't
have
experience
with
graph,
QL
and
I've
said
to
him
that
he
needs
to
take
the
time
to
understand
what
he's
doing
and
then
do
the
work
so
I'm
keen
for
this
to
be
like
a
and
noted
items,
but
I
would
be
cautious
of
adding
the
deliverable
label
because
he
needs
to
skill
in
yourself
she'll
there.
That's.
A
A
A
A
You
know
like
so
my
thought
is
the
following:
we've
done
two
pcs
in
12.8,
Thank,
You,
Valerie,
you're
awesome
for
the
lead,
only
maintenance
mode
and
for
the
pause
resume
replication.
The
pause
resume
replication
has
a
clear
next
implementation
MVC,
which
is
the
command-line
tools
to
actually
do
this
right.
So
I
think
that
is
something
we
can
actually
do
in
12.9,
because
it's
a
very
self-contained
minimal,
viable
change.
We
understand
what
needs
to
be
done.
That
makes
sense
to
me
for
the
read-only
in
the
maintenance
mode.
A
We
have
a
successful
POC,
but
I
would
argue
that
we
haven't
really
broken
down
the
next
steps
for
the
maintenance
mode
yet
sufficiently
so
Jing
and
I
did
a
I
think
a
really
fun
piece
of
work
on
Friday
to
look
at
the
user
flow
for
this,
but
I
think.
Actually,
if
we
spent
you
know
12.9
like
really
defining
exactly
what
we're
going
to
do.
You
know
validating
the
interface
with
some
systems,
administrators
that
would
be
sufficient.
A
But
that
means
we
don't
need
to
do
any
implementation
work
for
maintenance
moved
in
12.9,
and
so
that's
sort
of
my
my
it
like
in
terms
of
we
need
to
do
everything
I
would
say,
like
the
the
maintenance
mode.
Implementation
doesn't
have
to
happen
into
a
point:
nine.
We
can
do
that
release
later
and
then
it
would
be
much
better
defined,
so
I'm
I,
actually
added
this
to
a
this,
is
not
going
to
progress
as
implementation.
A
B
B
Think
what
we
need
to
do
before
applying
their
deliverable
labels
to
things
as
I
think
we
need
to
have
a
conversation
with
Mike
about
how
much
I
got
how
to
effectively
fan
out
the
work
for
the
self-service
framework.
That's
correct,
because
if
we
can
fan
the
work
out
in
a
in
a
good
way,
we
will
be
able
to
get
through
an
awful
lot
of
it.
I
mean
we
see
now
what
we
were
able
to
accomplish.
B
If
we
concentrate
and
put
our
heads
down
on
that
spine,
we
did
an
awful
lot
of
leeway
there,
but
I
think
we
need
to
have
a
conversation
with
him
to
see.
What's
realistic
for,
for
the
well
not
were
too
realistic,
because
we're
aiming
for
this
as
a
goal,
I
think
it's
more
about
what
else
we
can.
We
can
plan
around
it
because
I
want
to
say.
Yes,
we
should
do
this
command-line
tool
in
12.9.
A
With
that,
this
is
what
you
know
I'm
already
like
considering
cutting
scope.
We
can
move
these
things
around
a
little
bit
as
well.
It's
because
they,
the
liked
the
commandment
to
this
plant
right,
that's
something
that
is
ready
to
be
done
right,
but
so
I'm
not
so
worried
about
doing
it.
I'm
mainly
worried
about
capacity
yeah.
B
B
A
B
A
A
A
B
A
A
We
have
all
the
issues,
they
are
ready
to
be
picked
up
and
we
we
could
do
this.
You
know
if
we
put
this
as
a
deliverable
or
not
is
something
we
have
to
decide,
but
it
is.
It
is
something
that's
scheduled,
able
and
can
be
picked
up
and
I.
Think
from
the
complexity
that
I'll
see.
This
is
also
manageable.
I
think
it
would
be
nice
to
do
one
of
those
like
SSH
or
HTTP
in
12.9,
because
it's
a
nice
contained
piece
of
work.
A
A
These
are
the
interviews
that
we
don't
have
to
do
with
customers,
which
I
think
we
will
get
done
in
12.9,
which
I'm
quite
excited
about
read-only
maintenance
mode.
We
have
to
think
about.
You
know
like
how
to
break
it
down
specifically
validated
some
assumptions.
This
is
continuing
a
stretch.
Isn't
you
know,
installation,
prep
thinking
about
and
then
maintenance
mode
won't
progress?
Backups
won't
really
progress.
Much
that's
it.
A
So,
if
I
had
to
summarize
this,
this
year
is
essentially
get
this
done
right
it.
It
kind
of
just
needs
to
wrap
up.
The
self-service
framework
is
significant
sort
of
portion
of
work,
especially
because
of
the
verification
here
and
the
graticule
API,
and
that,
given
that
we
want
to
put
this
and
something
that
we
present
have
contribute,
should
be
the
focus
of
the
entire
thing.
A
Potentially
you
know
in
in
12.9,
in
addition
to
like
this
work
here
and
if
I'm
honest
I'd
like
to
have
at
least
one
like,
so
the
feature
delivered
in
12.9,
because
otherwise
you
know
this
is
important.
You
know
and
the
customer
value
will
come
over
time,
but
it
is,
it
is
spec,
nd
I
think
I'd
like
to
be
able
to
say
we've
also
at
least
moved
one
sort
of
immediate
thing.
A
B
And
like
it,
I
think,
one
of
the
things
that
I'm
always
nervous
about
is
because
we
went
through
a
phase
where
we
over
committed
and
other
random
stuff
would
show
up
in
the
sprint
when
we
were
still
doing
months
and
I
am
always
nervous
of
over-committing.
Given
how
much
other
stuff
shows
up
in
a
in
even
in
a
week
and.
C
B
Think
my
caution
here
is
that
we
seem
to
be
uncovering
things
from
rolling
out
on
staging.
That
makes
the
list
longer
and
longer
all
the
time
and
I
think
that
the
self
service
framework
is
a
bit
more
controlled
and
planned
in
that
we're.
Finding
less
stuff
is
just
showing
up.
I
mean
it
is
unfortunate,
we'll
end
up
breaking
master,
and
that
became
something
for
us
to
do.
B
Yeah
I
think
it's
about
just
about
being
mindful
of
that,
but
I
think
we've
got
a
couple
of
days
now
to
get
ahead
of
the
self
service
framework
and
see
how
that's
getting
on
or
what
needs
to
happen.
Next
and
from
there
we
we
can
figure
out
what
we
can
commit
to
before
the
end
of
12
or
9.
So
no
that's.
A
That's
sort
of
my
thinking
as
of
today
and
yeah
we
can.
We
can
certainly
revisit
this
the
week
you
can
see
you
know
what
we
can
and
can't
do,
I
totally
appreciate
that
not
everything
can
be
done
at
the
same
time,
but
similarly
I
think
it's
also
not
bad.
To
show
that
we
appreciate
that
those
things
are
valuable
and
you
know
that
we
like
focus
on
the
things
that
are
valuable
for
our
customers
and
a
lot
of
them
like
other
noise.
A
That
will
always
happen
whenever
we
need
to
be
mindful
in
not
getting
too
distracted
and
I.
Think
that's
always
the
challenge
right
and
I
hope
that
the
clearer
we
are
on
our
own
priorities,
the
easier
it
is
to
also
you
know,
say
no
to
other
things,
because
again
you
can
say
yes,
your
thing
is
also
important,
but
here
is
my
list
of
things
that
are.