►
From YouTube: Geo Scheduling Call
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
A
Much
better,
okay,
all
right,
let's
go
through!
What's
on
the
board,
so
support
replication
for
docker.
This
is
paused
at
the
moment,
because
Venera
is
looking
at
sidekick
for
the
production
incident.
He
didn't
have
that
much
further
to
go
with
it
and
we're
still
targeting
12.3,
but
he
does
need
to
look
at
the
production
stuff.
First,
yeah.
B
A
So
I
think
for
this
one:
that's
we
should
follow
up
with
Valyria
on
Monday
for
how
far
he
is
with
the
production
stuff
and
how
much
more
Tommy
thinks
he
needs,
because
if
he
is
going
to
be
pulled
into
that
for
the
entire
milestone,
we
have
to
swap
it
out
for
someone
else
now.
Ironically,
that's
you
know,
rather
than
later
exam
I
will
write
that
down
in
a
little
note
that
I
have
here.
A
A
That's
that's
really
good
right,
then
there's
two
blocked
ones,
so
both
of
these
blocked
ones-
I've
spoken
to
Dave
Smith
about
because
they
were
blocked
on
infrastructure.
This
one
we
now
have
access.
We
already
did,
but
we've
got
access
to
staging.
So
we
can
do
this
ourselves
and
just
basically
tell
them
what
we're
doing,
but
we
can
run
this
ourselves
cool
again,
because
this
is
for
Larry.
I
will
do
this
after
the
darker
work,
but
we
can.
We
can
unblock
this
and
I'll.
A
Put
the
comments
on
there
saying
as
much,
and
it's
the
same
with
this
one.
This
one
was
blocked
on
a
problem
with
Patroni,
but
because
we
now
have
access
to
do
whatever
we
need
to
do.
We
can
look
at
unlocking
that.
So
there
is
a
larger
question
here
about
how
to
prioritize
that
work.
With
getting
dr
enabled,
but
let's
save,
therefore
the
scheduling
part
of
the
pool-
that's
not
speak.
Okay,
then,
in
development
we've
got.
A
A
B
A
Remember.
Writing
it
and
I
thought
how
come
I
didn't.
Maybe
I
did
it
in
sec,
but
no
it's
there.
It
is
okay,
thanks
for
spot
again,
okay,
consider
alternative
methods
for
replicating
data.
I
spoke
to
Douglas
earlier
in
the
weekend.
He
was
taking
a
look
at
these
alternatives
and
with
the
proof
of
concept,
it's
it's
not
a
mode
request
at
the
moment
because
he's
still
doing
the
proof-of-concept,
but
the
result
of
this
would
be
that
all
of
the
other
replicated
types
would
be
then
be
easier
to
add.
A
B
B
A
A
A
A
B
B
B
B
Okay,
so
this
is
something
we
need
to
discuss,
so
I
actually
did
a
little
bit
of
a
sweep
and
I
tried
to
find
all
of
the
like
geo
items.
That
will
work
then
we're
in
labeled
at
with
like
labels
and
didn't
understand.
So
this
thing
here
most
marked
as
English,
but
it
didn't
have
anybody
assigned
so
I
moved
it
to
ready
for
development
just
to
have
a
check
with
you.
I.
Don't
think
this
is
something
we
need
to
do
right
now,
so
I
wouldn't
use
it
out
again.
Yeah.
B
A
Something
you
were
looking
at:
the
dryer
chicks,
I'm,
quite
a
bit
I!
Don't
know
why
I've
only
thought
of
this
now,
but
that's
only
gonna
wait
over
one
and
if
that's
refactoring
with
tasting,
is
it
really
one
I
want
to
take
an
opinion
on
that,
because
that's
there's
something
is
something
that
I'm
just
no
taking
notes
about
that.
A
B
A
C
B
A
B
Think
this
is
something
we
should.
We
should
certainly
think
about,
and
so
part
of
this,
the
archiving
of
old
upgrades
update
steps
right.
It's
part
of
it
and
I
think
once
that
is
done,
I
think
we
should
just
be
visit
this
and
say
like
okay,
given
the
state
it
looks,
it
is
now
you
know.
Are
we
happy
with
the
fee
instruction?
So
I
think
this
is
relatively
straightforward
thing
to
do,
but
I
do
think
it
should.
A
A
B
Don't
know
if
he
has
commented
on
this
yet,
but
yesterday
we
essentially
agreed
that
he
should
break
this
up
into
smaller,
smaller
issues
and
also
essentially
the
the
first
thing
that
we
that
we
can
do
I
think
is
cover
the
the
simplest
possible
use
case
of
checking
for
the
the
file
check,
something
it
to
cover
sort
of
the
bare
minimum,
the
use
the
size
of
the
item,
and
then
we
can
consider
all
of
these
other
interesting
cases
separately
and
do
them
a
little
bit
later.
So,
yes,
I,
think
that
was
the
agreement
yesterday
evening.
B
B
B
A
B
I
would
argue
that
we
have
still
seven
tickets
in
here
and
we
have
six
in
progress
with
a
combined
weight
of
18,
so
I'm
currently
happy
with
those
in
here.
I
I
think
the
first
bits
here
are
actually
like
the
first
five
I,
definitely
really
important
right
now
and
then
the
other
bits
here
you
know-
maybe
maybe
less
so,
but
we
we
want
to
take
a
technical
data
and
bugs
as
well
so
I'm.
B
I
think
I
think
the
upgrade
stuff
will
become
even
more
important,
probably
but
I
think
we
do
need
to
think
about
a
little
bit
what
that
means
and
what
the
individual
other
items
actually
look
like,
but
I
I
think
that
the
day
she
came
work
is
important
and
that
the
single
kid
URL
is
something
that
you
should.
You
should
do
so.
Yes,
okay,.
C
B
Think
so,
because
I
feel
that
we
still
have
enough
to
to
work
on
and
I
need
to
do
a
little
bit
of
shuttling
later
on,
and
if
we
look
at
the
scheduling,
so
the
next
items
are
verification
items.
Then
we
can
I
think
decide
on
once.
The
upload
stuff
is
done,
followed
by
support
for
design
repositories,
which
I
think
is
also
okay,
yeah.
So
I
think
we
have
a
good
backlog
here.
Yeah
I
think
in
terms
of
my
my
plan
board,
so
I
think
there
is
one
item
that
has
to
do
with
GHA
upgrade
documentation.
B
B
B
Check
some
clarification
in
object,
storage,
the
update
process,
I
think
this
is
going
to
close
relatively
soon
Toland
I
just
need
to
get
an
agreement
and
I
think
yeah.
I
think
this
is.
This
is
fine
how
how
it
went,
but
it's
one
of
these
issues
that
we
created
before
the
new
process
and
that
moves
around
a
little
bit
and
yeah.
So
there
are
a
few
interesting
bits
in
here,
but
nothing
nothing
too
urgent
for
problem
validation,
I
think
these
are
some.
B
There
are
some
interesting
things
in
here.
So,
for
example,
partial
replication,
restrictive,
selective
synchronization
I
opened
that
yesterday,
so
I
think
I
haven't
in
this
weekend
have
done
too
much
work
on
this
board,
but
I
thought
quite
a
bit
about
how
these
things
will
be
affected
by
potential.
B
C
B
We,
for
example,
look
at
this,
so
I've
invested
quite
a
bit
of
time.
Writing
up
my
thoughts
on
disaster
recovery
for
Capcom,
so
I
think
we
are
in
a
in
a
debtor
state
in
terms
of
you
know
the
context
of
why
we
want
to
do
that.
We
had
a
discussion
on
Wednesday
as
well,
so
I
think
here,
maybe
over
the
next
week.
A
So
what
I'm
gonna
do
I
have
a
meeting
with
Ashe
on
either
Tuesday
or
Wednesday
and
I'm
going
to
go
through
with
him.
What
we
need
to
do
for
do
to
get
lab
to
come.
Look.
How
do
we
get
that
into
a
working
State?
Yes,
he's
he's
the
most
recent
person
who's
been
working
on
that
with
divin,
and
now
that
we've
got
me
a
massive
thumbs
up
to
just
get
on
with
it.
I'm
gonna
chat
to
him
about
what
exactly
that
means,
but
then
we
have
to
figure
out
what,
from
a
scheduling
perspective.
A
B
For
example,
I
can
give
you
my
my
high-level
thoughts
right
at
the
moment,
so
I
think
the
way
the
roadmap
looks
at
the
moment,
and
we
have
a
few
things
that
we
are
doing,
that
I
think
we
we
can
shuffle
around
a
little
bit.
So
we
have
a
large
number
of
items
to
unreplicated
datatype,
so
that's
more
features
in
a
way
which
we
should
do
and
we
have
one
or
two
quite
well
defined,
but
there's
also
a
lot
there
all
right.
B
So
that
is
something
that
I
think
it's
sort
of
chunk
rubble
all
right
and
we
can
say
like
let's
focus
on
design
repositories
on
get
leadpages
and
so
on
and
so
forth.
So
that
is
something
that
we
may
be
able
to
postpone
a
little
bit
and
then
the
simplification
of
installation
I
think
it's
something
that
we
can
like
I'm
thinking
about
this
right
now,
but
there's
not
much
to
do
here
at
the
moment
or
so.
Every
fix
there's
a
lot
to
do.
B
You
know,
but
we
we
haven't
really
started
so
I
I,
think
I'm,
I'm,
potentially
willing
to
say,
okay,
given
that
we
now
have
like
a
better
mandate
for
an
a
blanket
lab
comm.
Let's
really
try
to
get
that
done
as
fast
as
we
can,
as
as
a
team.
Not
everything
will
be
paralyzed
about
parallelizable,
make
that
a
priority
I.
B
Think
given
recent
issues
focusing
or
doubling
down
on
the
upgrade
process-
and
you
know
the
stability
of
it
and
what
we
can
do
and
can't
do
right
and
at
least
doing
the
things
that
we
feel
are
within
our
limit.
I
think
it's
still
important
and
then
the
this
bit
here
are
automatically
choosing
the
right
geo.
Node,
there's
actually
only
one
actionable
item
at
the
moment
for
for
development,
which
is
the
single
get
URL,
but
I
am
going
to
work
on
surveys,
some
user
research
here,
so
that
I
think
is
fine.
B
This
will
close,
but
we
may
be
able
to
say:
okay,
that's
really
like,
let's
delay
design
repositories
until
we,
for
example,
we
do
the
developer
come
work
or
we
finish
it.
So
we
may
need
to
shuffle
around
a
tiny
bit
depending
on
what
this
actually
means,
because
I
think
at
the
moment
my
biggest
question
here
is:
how
far
did
we
actually
get
and
what
is
still
outstanding
is
this,
let's
say
one
or
two
month
of
works
and
two
releases
and
we
get
it
done.
Is
it
three?
You
know?
B
B
A
B
B
And
I
think
this
is
the
balance
we
have
to
strike
right
because
I
discussed
that
yesterday
with
Mike
on
the
one
hand,
I
don't
want
us
to
invest
a
ginormous
amount
of
effort,
but
I
also
don't
want
this
to
take
six
months
right
and
I
feel
that
the
ask
it
off
they
refined
the
data
that
that
we
replicate.
You
know
it's
also
I,
think
that's
that's
understandable
that
we
should
do
that.
I
feel
I,
think
that
is
what
you
just
happened.
Yeah
well,
I
I,
think,
invest
some
time
today
to
think
about
this
as
well.
B
I,
don't
think
our
and
high-level
priorities
on
verification,
the
upgrade
process
and
the
signal
get
URL
are
wrong,
but
we
have
to
see
right,
and
there
are
some
other
things
that
I
may
want
to
do,
for
example,
the
selective,
selective
sync
or
hundred
posit
or
eise.
I
think
that
has
high
customer
value,
but
yeah
I
need.
I
need
to
clean
up
a
little
bit.
I
think
the
one
thing
that
I
am
not
comfortable
doing
at
the
moment
is
given.
Where
we
are,
I
will
have
to
do
an
announcement.
What
we
do
for
twelve
point.
B
Four-
and
I
will
not
try
to
add
more
to
the
pile
I
think
we
are
already
a
little
bit
behind
and
some
areas
so
I
I
think
what
I
will
aim
to
do
is
either
you
know,
put
I
pull
some
things
away
from
the
pile
and
say
we
are
going
to
do
them
later,
and
then
we
place
them
with
something
else,
for
example
github.com,
but
I
don't
think
we
can.
We
can
just
add
more
at
the
moment
that
will
I
think
only
be
detrimental.