►
From YouTube: Geo Scheduling Call 2019-11-04
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
B
Right
I'm
gonna
share
my
screen
on
the
bull
board,
which
looks
very
very
full
today,
just
lovely
okay,
that's
too
much
border.
Okay,
close
to
column
today,
I
was
very
happy
to
share
that.
You
see
that
the
Chardon
worker
one
is
closed.
I
know
that
we,
it
was
inconclusive
at
the
end,
but
I
think
that
valeri
had
a
really
good
summary
at
the
bottom
here
about
why
we
should
close
and
I
completely
agree
with
all
of
these
things.
So
I'm
happy
with
that.
Let
me
take
the
labels
off
yeah.
B
B
A
A
A
B
B
A
B
A
A
Maybe
I'll
actually
add
that
to
the
the
checklist
here
and
say
like
upload
this
to
Hitler
unfiltered
and
then
link
it
in
the
issue.
I
have
to
admit
I've
enjoyed
having
a
checklist
to
go
through
I
thought.
That
was
good
for
something
that
is,
let's
say,
unfortunately
highly
manual,
but
it
needed
to
well.
B
Have
you
maybe
I
mean
I
know
that
at
the
moment
we're
going
to
that
water
I?
What
I
was
going
to
suggest
is
actually
making
a
template
for
the
upgrade
issues.
But
if
the
long,
if
the
long
process
the
so
the
the
long-term
process
is
to
automate
it
then
I'm
not
sure
how
much
of
any
there
isn't
having
the
template.
But
I
don't
know
how
many
more
we're
gonna
have
to
do
before.
It's
automated
further
I
think.
A
Okay,
so
I
think
the
first
question
is
the
Geo
upgrade
demos
I
think
everything
that
we
intended
to
do
until
twelve
point
four
is
now
actually
done,
and
so
this
is
going
to
never
really
end
right,
because
we
always
have
to
do
it.
It
was
made
mainly
a
way
for
me
to
actually
link
them
in
one
place
and
I'm
also
I'm
also
happy
to
close
it.
If
people
would
like
I'd
like
I,
think
it
doesn't
matter
either
way
really
well.
B
A
B
A
A
B
A
B
B
A
B
A
B
A
A
A
B
A
B
Yeah
and
I
think
what's
also
made
a
difference
is
because
I
split
into
each
of
these
little
pieces,
it's
become
a
much
more
tangible
result.
Then
we
did
a
bunch
of
stuff
to
improve.
Upgrades
like
these
are
the
specific
things
we
did
to
improve
up
great
these
four
things
and
I
think
that
is
a
much
more
real
thing
that
customers
can
appreciate
rather
than
a
degree
stuff
around
upgrades,
so
awesome,
I'm,
very
happy.
Okay
for
any
data
tables
three
more
to
go.
B
B
Things
and
that's
all
the
testing.
Okay,
awesome,
that's
good
news,
okay,
verification,
so
there's
two
items
in
there
that
one
we've
just
spoken
about,
and
this
one
is
about
the
fact
that
the
screen
is
gone.
So
the
that
was
also
release.
Note
I
really
wanted
to
add
there.
Okay
in
review
and
start
at
the
top
right.
I
know
that
some
Ashe
and
Devon
have
been
going
back
and
forth
from
this.
One
is
the
mr
list
anymore.
It
catches
me
because
it's
in
a
different
project,
yeah.
B
Okay,
so
they've
still
been
caught,
but
they've
still
been
chatting
and
I.
Think
what's
going
to
be
helpful,
is
with
having
the
saris
come
and
join
us
MSS
being
agreed.
So
as
soon
as
that
happens,
we
can
push
that
even
faster,
which
would
be
great.
Okay,
expose
an
API
for
the
design,
replace
that's
good
that
that's
interview
as
well.
This
was
exposing
the
API,
so
there's
a
can
hook
up
with
Frank
Ian
property.
That's.
B
A
B
B
Okay,
that's:
let's
try
that
again.
B
Nakano
this
bottom
I'm
gonna
walk
this
blocked
on
the
board,
because
it's
blocked
with
having
an
RC
to
test
with
I,
don't
I
see.
This
is
when
we
have
the
12.5
RC.
B
A
B
B
B
A
A
B
B
B
A
B
B
B
Yeah
I
think
it's
I
think
it's
Gio,
because
anything
that
the
team
does
the
M
R
itself
needs
to
be
youth
egged,
but
this
one's
merged.
So
suppose
this
is
the
one
that
he's
done.
They're
nice
God
needs
to
do
these
other
ones.
I
think
what
I'm
going
to
do
is
then
I'm
going
to
untag
so
I'm
sure
that
we
didn't.
Oh
it's
because
I
put
the
active
label
in.
B
Okay,
I'm
gonna
just
take
that
the
Geo
active
office,
because
it
doesn't
actually
need
to
appear
on
our
boards.
This
is
something
that
Ash
is
doing
in
the
background
and,
as
you
can
see
like
it's
bits
and
pieces
over
a
long
time
frame,
so
this
doesn't
need
to
be
something
that
we're
tracking
on
our
border
sounds
good.
B
B
A
B
B
B
B
That's
I've
got
a
note
here
that
I
need
to
set
up
the
meeting
on
number
one
on
my
little
my
little
car
repaired
trying
to
use
up
all
my
extra
stationery
very.
B
I
figure
once
you've
had
something
like
that
for
10
years.
You
can
just
use
it
and
get
rid
of
it
anyway.
Right
exposed
sink
information,
so
this
is
the
front
end
portion
of
the
API
surface
wall,
I
think
with
it
being
Zechs
first,
one
I
think
he's
just
had
some
challenges
figuring
out.
They
get
that
way
of
things,
but
he's
been
actively
working
on
that
so
yeah
right
then.
The
last
three
issues
in
here
are
the
test
cases
for
the
upgrade
stuff.
B
Now
the
reason
that
I
decided
to
put
the
test
cases
into
the
board
is
because
I
felt
that
it
would
just
give
some
more
visibility
to
these
items.
I'm
open
to
like
suggestion
about
or
comment
about
that,
but
I
just
thought
by
going
through
these
regularly
they'll,
be
subject
to
the
same
process
of
the
rest
of
the
issues
are
and
I
think
that
that's
a
better
way
of
bringing
this
quality
work
into
the
team
property.
B
B
A
B
B
A
A
A
Yeah,
so
this
is
my
my
impression
is:
this
is
something
where
once
Mike
is
done
with
all
of
his
work
in
progress.
Mrs
on
the
related
issues
for
this
it's
very
likely
to
to
either
need
to
be
picked
up
and
or
determined.
If
this
is
the
relevant
or
not
so,
I
think
I'll
leave
it
in
here,
so
that
we
can
make
sure
to
close
this
one
off
I
think
this
guarantees
that
it
will
be
will
be
touched
once
and
not
be
forgotten.
I.
A
It's
also
the
foreign
table,
so
I
I
dragged
in
all
of
the
sort
of
the
straggling
issues
from
the
ethics,
and
we
can
make
sure
that
we
actually
close
them
off,
which
I
think
will
be
agreed
to
do
this
one
here
at
section
two,
dr.
So
this
is
part
of
the
promotional,
emotion
and
failover,
so
I
I
think
we
can
actually
move
this
back
into
scheduling.
A
A
A
Downgraded
from
areas
yes
from
an
e
to
a
Cee
some
time
ago
and
I
think
this
is
just
something
we
should
fix.
So
it's
a
small
item,
I
think
high
rate
of
cannot
obtain
a
nice
to
say
fleece
message.
So
this
was
also
a
small
bug
that
we
discussed
a
little
while
ago.
I
think
Valeri
has
actually
picked
this
up
so
I'm
going
to
move
this
over.
B
A
Yeah
I
think
this
is
just
I,
had
a
discussion
with
Valeri
on
Thursday
because
he
he's
waiting
on
some
reviews
and
was
interested
in
say
seeing
what
else
he
can
pick
up
at
the
moment
and
those
are
some
sort
of
technical
debt
items
that
are
I,
think
ready
in
that
regard.
B
A
So
I
I
have
one
item
that
I
I
looked
at
earlier.
That
I
think
we
should.
We
should
move
forward,
which
is
the
move
geo
settings
bits
here.
This
is
also
relevant
for
for
Zack
yeah
I
looked
at
this
again
and
I
think
the
way
forward
here
is
we
had
a
customer
recently
that
upgraded
all
the
way
from
eleven
ten
to
twelve
point
four,
so
upgrades
happen,
sometimes
like
they're,
very
jumpy
for
enterprise
customers
and
so
I
think.
A
The
strategy
that
must
have
laid
out
here
to
transition
by
essentially
redirecting
automatically
and
giving
a
banner
is
correct.
I
really
like
that
and
I,
also
feel
that
we
should
be
conservative
with
this,
because
when
people
don't
find
the
admin
panel
anymore,
they
I
think
they
can
get
quite
confused.
So
I
like
this
suggestion,
you
were
automatically
upgraded
redirected,
yes,
redirected
I'm
still
with
upgrades
yeah,
redirected
and
I
think
actually,
if
we
automatically
redirect
I,
don't
believe
there's
any
harm
in
by
now
where
we
are
in
in
the
release
cycle
to
redirect.
B
A
A
I
looked
at
it
because
I
I
thought
that
this
is
maybe
the
next
thing
that
ii
can
pick
up.
It
doesn't
have
a
wait
yet,
but
I
am
happy
to
schedule.
It
I
made
a
comment
already
that
that
he
can
apply
a
wait,
but
I
think
that
is
maybe
the
next
thing
for
him
after
the
design
repository
work.
Okay,
are
you
happy
with
that?
Yes,.
A
A
We
are
ramping
up
new
new
epochs
right
and
the
one
epic-
and
we
have
quite
a
few
actionable
items
I
think
here
for
for
enabling
gon
comm
but
I
think
we're
still
a
little
bit
stuck
with
where
the
next
steps
really
are
and
what
the
next
issues
are.
I
think
that
may
actually
become
a
little
bit
more
dynamic
in
the
next
week
or
so
yeah.
B
I
think
that
the
next
item
that
we
do
need
to
pull
over
is
that
monitoring
there's
the
one
at
the
top
of
the
open
column,
but
it
is
still
a
little
bit
unclear
what
that
actually
means.
We
need
to
do
the
monitoring,
but
we
also
need
to
figure
out
what
monitoring
is
required.
So
I'm
I
would
be
okay
with
pulling
that
over
to
the
development
column.
But
we
need
to
change
the
description
to
save
figure
out.
What
monitoring
we
need
to
actually
do
and
then
go.
B
B
A
But
I
think
that
is
that's
going
to
I
think
this
is
also
maybe
for
us
a
little
bit
this
geo
dot-com
bid
is
going
to
be
a
little
bit
more
project
like
right.
Things
will
come
up
that
need
to
be
done
and
then
I
think
we
should.
We
should
track
them
by
creating
the
issues
for
it,
but
it
is
a
little
bit
different
to
feature
development
or
a
bug
fixing
and
in
that
regard,
because
I
think.
B
A
B
I
think
that
as
I'm
glad
that
you're
happy
to
be
flexible
with
that,
because
I
think
that
it's
the
only
way
we're
gonna
get
this
deployed
is
with
some
flexibility
here.
I,
don't
think
that
we
will
ever
know
everything,
that's
going
to
need
to
be
done
to
get
this
rolled
up
until
we're
actually
doing
it.
B
A
So
for
like
for
the
demotion
and
promotion
failover,
my
idea
for
this
week
is
actually
to
sit
down
and
create
some
some
epics
and
also
isolate
some
of
the
feature
requests.
Let's
say
that
I
I
think
our
most
valuable
at
the
moment
and
then
in
conjunction
with
an
engineering
owner,
define
exactly
what
needs
to
be
done
because
I
think
there
is
a
lot
a
lot
to
be
done
here,
but
I
I
still
need
a
little
bit
more
time
to
define
what
the
with
the
most
important
next
step
is.
A
I
know,
there's
a
lot
of
documentation
updates
required,
but
I
think
it
may
also
be
an
opportunity
for
us,
because
there
is
not
that
much
documentation
for
the
disaster
recovery.
Category
I
think
there
may
be
an
opportunity
to
say:
can
we
we
like?
Can
we
restructure
this
as
well
in
a
way
that
is
maybe
a
bit
more
accessible
and
what
could
that
look
like,
for
example,
I.
A
I
have
to
think
about
it:
okay,
yeah
and
then
I.
The
last
thing
I
would
like
to
highlight
and
I
had
a
discussion
so
about
the
scaleable
self-service
geo,
replication
gratification
framework,
a
small
ask
that
I
expect
to
be
delivered
within
around
two
weeks:
okay
No,
so
you
asked
to
raise
the
questions
like
what
is
the
priority
and
the
way
I
see
this
is
and
I
will
I
will
try
to
reflect
that
in
the
structure.
A
B
A
A
Limited
right
so
in
a
way
we
need
to
like
shift
gears
and
say:
okay,
how
can
we
do
this
differently?
And
this
is
what
this
this
idea
here
will
become
and
in
order
to
actually
start
because
again,
I
think
there
is
a
lot
of
work
here,
but
and
I
think
it
will
encompass
how
we
verify
things,
how
we
replicate
things.
A
You
know
a
definition
of
some
some
interface
I
thought
and
I
mean
that
was
also
echoed
by
Valerie
and
I,
had
a
chat
with
him
this
morning
that
the
best
way
to
kick
this
off
is
actually
with
a
small
POC
but
I'd
like
to
get
your
opinion
on
it
and
the
idea
there
was.
We
have
a
lot
of
discussion
in
the
team
at
the
moment
about
you,
know
the
current
limitations
of
replication
and
some
proposals
on
how
that
can
be
done
differently.
I
think.
A
The
main
thing
here
is
the
event-driven
architecture
proposed
by
Douglas,
and
then
there
is
other
proposals
for
for
verification
which
I
have
to
admit
on
a
technical
level
and
100%
sure
how
that
works,
mm-hmm
and
then,
lastly,
anything.
This
is
sort
of
the
missing
piece.
This
I
don't
think
we
have
a
good
handle
on
how
an
interface
could
look
like
the
best
we
have
at
the
moment
is
a
proposal
by
by
toun.
You
know
that
if
we
wanted
to
make
it
easy,
it
could
look
like
something
something
like
that
right.
Yeah.
B
A
I
think
the
purpose
would
be
more
to
facilitate
discussion
on
a
sort
of
concrete
example
of
what
could
that
even
look
like,
and
do
we
think
that
this
makes
any
sense,
because
I
think
the
risk
here
is
that
if
we
say
like
yes
we're
going
to
do
it
and
then
we
start
another
legacy,
effort
like
working
on
the
event
driven
system
and
working
on
verification,
but
we
will
not
see
sort
of
how
all
of
those
things
can
and
so
I
made-
and
this
is
not
you
know
to
be
perfectly
transparent.
This
is
not
100%.
A
My
idea
that
came
out
of
a
discussion
with
Valerie,
so
thank
you
very
much.
So
I
wrote
up
a
little
in
the
morning
saying
like.
Can
we
actually
and
I?
Don't
know
how
realistic
this
is,
but
can
we
actually
create
a
POC
four
hours
of
main
repositories
with
all
of
these
like
or
these
three
different
things
sort
of
in
mind
right.
Some
iteration,
like
very
rough
on
an
interesting
interface
to
add
data,
a
draft
implementation
of
dissident
based
system
and
some
verification
bits
but
like
I,
want
to
be
very
clear.
A
Like
not
do
everything
and
it's
going
to
be
done,
but
it's
really
about
saying:
do
these
things
even
like
match
up
in
code
and
then
then
facilitate
the
discussion
in
the
team
and
actually
like?
This
is
a
suggestion
also
from
Valerie.
He
thought
that
maybe
something
that
needs
to
be
done
a
little
bit
more
like
synchronously,
where
you
know
we.
We
need
some
discussion
on
the
mrs,
but
also
just
get
the
team
together
to
to
look
at
this
from
sort
of
an
architecture
standpoint
and
make
sure
that
everybody
has
contributed
because.
B
In
general,
yes,
we
need
to
do
a
proof-of-concept
first
and
having
a
minimal
iteration
proof-of-concept.
That
does
the
that
shows
what
the
interface
will
look
like
and
has
the
verification
piece
done
so
for
replication
and
verification.
Yes,
but
I
haven't
concerned
that
putting
the
event
system
inside
of
this
is
going
to
make
it
too
big
and
I
think
that
the
event
system
should
be
a
second
iteration
or
a
separate
piece,
because.
B
Picking
things
out
of
a
database
and
scheduling
them
for
work
I
think
is
a
separate
problem
from
replicating,
which
is
also
a
separate
problem
from
verifying
but
I
think
that
replicating
and
verifying
or
closing
together
to
be
considered
as
the
same
POC
and
I
think
could
be
considered
at
the
same
time.
So
I
would
I
say
in
general,
yes,
but
I
think
that
they
have
been
stuff
should
come
and
be
separate.
I
think
that
if
we
can
pull
an
issue
like
this
into
the
share
dealing
column,
it
would
also
help
us
get
this
done
faster.
B
B
So
this
is
what
what
repository
looks
like
this
is
what
file
looks
like,
and
this
is
what
something
else
looks
like,
at
least
for
at
least
three
of
them,
and
the
reason
that
I'm
saying
that
is
because
we
may
have
a
really
good
structure
for
a
framework
that
works
really
well
for
repositories,
but
for
some
reason
it
doesn't
then
extend
itself
nicely
and
at
least,
if
you've
already
considered
the
extension
as
part
of
the
proof
of
concept.
We
all
know
that
that
would
be
good
I.
A
I,
don't
necessarily
have
to
like,
so
actually
that
came
up
as
well
like
we
would
we're
thinking
about
uploads
sort
of
faster,
the
next
thing,
but
the
question
there
was
again
isn't
that
is
that
too
big?
Can
you
manage
and
I'd
like
I?
Don't
know,
but
that's
so
if
we,
if
we
say
like
hey,
can
we
have
in
this
PSD
with
posit
or
E's
and
files,
and
something
else
I'm
happy
with
that?
But
if
well.
B
I'd
say
at
least
two
is
a
code
of
that
I
would
be
if
we're
looking
at
framework
like
the
idea
of
framework,
or
you
know,
extensibility,
and
we
only
do
a
proof
of
concept
for
one
item,
I'd
be
worried
that
we
make
decisions
that
we
that
are
not
extensible
later
and
I
know
that
people
will
have.
You
know
best
intentions
of
keeping
that
in
mind
and
all
those
good
things,
but
at
least
with
the
proof
of
concept,
it
becomes
completely
obvious.
B
A
So
the
I
didn't
want
to
schedule
this
just
like
that.
I
wanted
to
have
a
quick
discussion
about
that.
First
and
I've
weighed
this
tentatively
myself
at
5:00,
but
this
is
just
a
suggestion,
because
I
think
five
is
an
idealized
work
week
and
my
like
this
is
more
about
like
making
it
very
explicit
that
I
would
like
this
scope
to
be
small
right,
as
in
I.
B
A
A
What's
the
minimal
like
next
step,
all
right
and
then
I
think
if
that
can
be
sort
of
the
dynamic
I
think
we
can
then
say
like
okay,
maybe
now
it's
a
good
time
to
like
test
out
this
little
thing,
for
we
need
to
like
test
this
out
for
a
new
data
type
I
think
that's
kind
of
the
the
idea
that
I
have
and
then
we
can
also
say
like
we
can.
We
can
shunk
it
up
nicely,
rather
than
doing
everything
everything
at
once.
Yeah
now.
A
A
B
Are
the
list
of
data
types
that
we
support?
Pick
please
pick
one
please,
please
do
you
base
to
choose
something
that
we
were
really
supportive?
Yes,
you
don't
choose
something.
We
support
we're
going
to
ask
your
lots
and
lots
of
questions.
So
you
know
these
are
all
the
things
you
can
choose
from,
or
else
we
need
to
talk.
Yeah.
A
We
can
also
like
I'm,
going
to
hold
off
creating
an
epic
to
track
all
of
this
until
those
are
done,
because
I
think
then
we
can
also
say
like
we've,
we
had
a
look
and
it
this
does
not
look
feasible
like
we
can
still
sort
of
turn
around
and
say
like
hey,
let's
do
something
else,
but
if
we
are
happy,
then
we
can
actually
say:
okay
more
concretely.
What
are
the
things
alright
and
I?
A
Think
that's
that's
okay
and
lastly
yeah
so
my
week
other
than
and
this
I'm
going
to
spend
on
promotion,
emotional,
failover
and
actually
thinking
through
the
next
steps
and
what
we,
what
we
should
do,
there's
tons
of
issues
that
are
related
to
this.
So
it
will
take
me
a
little
while
to
to
get
going.
B
A
B
Would
be
a
good
idea
to
start
with
it
with
your
clean
brain
before
reading
all
of
these
issues
and
trying
to
see
where
they
fit
into
your
ideas,
but
rather
just
start
from
the
idea
of
this
is
what
we
need
to
accomplish,
and
then
we
need
these
things
bubble
into,
because
there's
some
stuff
in
here
I'm,
not
sure
if
we
should
actually
be
doing
it.
No.
A
My
intention
is
to
say
like
these
are
the
four
or
five
things
that
I
believe
we
need
to
deliver,
and
these
are
the
things
that
we
need
to
do
when
some
of
those
issues
may
fit
in
some
others,
because
let's
say
there
is
quite
a
bit
of
discussion,
for
example,
about
database
support
on
the
secondary
right,
and
you
know
what
that
would
mean
before
production
instance
right
and
that's
nice.
But
what
are
we
trying
to
actually
accomplish
here?
Yeah
yeah,
but
that's
it
would
be
great
to
have
somebody
to
bounce
off
my
my
ideas
here.