►
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).
C
B
B
B
But
there's
another
one:
it
was
about
the
validation
with
Mike
and
Gabriel,
we're
talking
about
how
much
testing
was
done
and
I
think
that
they
were
satisfied
that
in
that
testing
was
done.
So
I
was
wondering
if
we
can
actually
put
this
into
the
board,
actually
that
we
need
to
have
a
discussion
about
if
enough
testing
was
done
here,
that
we
can
remove
the
flag,
so
I'll
follow
up
with
that.
After,
let
me
open
up
the
discussion.
B
A
I
haven't
also
a
follow
up
to
do
here.
I
think,
a
long
time
ago,
I
actually
load
the
release
post
entry
for
this,
but
I
think
that
is
probably
out
of
date
now
so
I
will
also
need
to
open
an
emergency
quest
against
the
12.4
release
post
and
get
it
reviewed
by
by
Gabriel
and
dr.
market
so
that
we
have
that
as
a
release
post
item.
A
Which
one
the
release
post
manager
for
12.4,
but
from
what
I
hear
so
the
new
process
of
actually
having
merge,
requests
against
unreleased
features
and
being
able
to
write
them
ahead
of
time.
I.
Think
it's
great,
because
I
can
do
this
this
week
for
things
that
we
know
we
are
very
likely
to
ship,
and
that
means
that
you
know
in
the
time
before
actually
having
to
get
it
done.
You
know,
if
you
did
it
earlier.
It's
way
less
stressful,
so
like
that.
A
The
only
thing
that
just
comes
to
mind
that
we
probably
have
to
think
about
a
little
bit
more
in
the
future
is
when
we
do
this
and
I
still
have
to
write
the
release
post
items,
the
clothes
things
actually
sort
of
go
away
into.
The
ether
of
you
know
like
clothes
geo
items,
so
maybe
we
need
to
put
them
into
like
verification
or
some
other
stage.
Just
thinking
about
it.
Just.
B
A
C
B
C
B
B
The
one
thing
that
we
can
be
doing
better
with
the
design
repository
work
is
having
more
people
on
it.
It
feels
like
we
deliberately
split
everything
up
and
having
more
people
working
on
this
would
make
it
go
even
faster.
I
mean
I
know
that
you
can't
paralyze
everything
across
the
entire
team.
That's
a
bit
much,
but
just
having
one
other
person
with
veneering
I,
think
good,
isn't.
A
D
A
C
B
C
A
Was
nice
I
actually
I
personally
I
really
like
when
he
small
things
like
this
happen,
because
this
feels
like
usually
they're
hard
to
overlook
no
they're
easy
to
overlook
and
then
they
just
stick
around
because
they're
not
that
bad.
But
if
you
make
them
part
of
a
larger
effort
and
all
of
a
sudden
you
just
clean
up
a
little
bit
and
I
think
that
in
the
some
is
quite
appreciated
right
and
that
makes
the
best
internal
overall
look
more
more
polished
and
consistent
for
customers
and
I.
Think
that's
quite
nice!
Now
I.
B
Like
that
as
well,
it
feels
like
the
right
thing
to
do
is
when
you're
working
in
an
area
you
just
find
all
the
other
little
things
that
you
feel
you
can
do.
That's
that's
a
reasonable
I
mean
I,
know
that
that
can
quickly
escalate
to
just
doing
an
awful
lot,
but
you
know
just
handling
one
or
two
or
three
little
things
at
the
same
time,
I
think
it's
a
great
idea.
A
And
I
think
maybe
this
is
just
a
note
that
we
can
put
into
the
scheduling
document
because
I,
maybe
it
was
even
in
you
Tony
I,
can't
quite
remember
some
someone
came
to
me
and
said:
hey
I,
have
this
small
issue
and
I'm
actually
like
I'm
picking
it
up
right
now.
I
just
want
to
let
you
know
that
it
is
on
the
scheduling,
board
and
I
think.
Obviously
there
is
a
balance
if
people
do
a
lot
of
unplanned
work
and
they
don't
get
your
priorities.
A
That's
not
good,
but
I
also
think
that
if
something
comes
up
and
you
can
proactively
pick
it
up
and
they
you
know
it's
a
it's
a
small
thing
to
do.
You
know
and
you
in
there's
a
couple
of
hours.
I
think
it's
perfectly
fine
to
you
know,
take
that
agency
and
do
it
because
I
don't
want
the
prompt,
like
the
whole
process
to
be
so
rigid
that
people
feel
like
they
can't
and
independently
anymore.
That
also
reduces
velocity.
So
in
my
view,
you
know
it's
a
little
bit
of
common
sense
right.
A
If
you
pick
something
up
because
they
quickly
want
to
fix
it
and
then
all
of
a
sudden,
you
spend
four
weeks
on
it
right.
But
if
you,
if
you
have
something-
and
you
just
see
it,
what
do
you
say
like
that's
customer
relevant
I'm
just
going
to
do
it
I
think
that's
a
really
good
sign,
but
you
still
need
to
apply
the
right
labels,
but
you
can't
feel
empowered
to
do
with
yourself.
A
B
B
A
B
A
A
B
A
B
I
think
there
is
a
larger
discussion
around
how
I
mean
I'm
trying
to
work
with
him,
some
makers
a
process,
that's
the
same
for
everyone,
the
more
I
do
things
it
just
feels
like
Jia
is
different,
but
the
process
I
understand
why
the
process
needs
to
be
the
same,
so
I'm
working
with
them
to
try
and
figure
out
how
to
do
that
in
a
way.
Yeah.
A
I
think
what
we
should
acknowledge
below
is
that
and
I
think
we
kind
of
do
this
year,
that
this
issue
is
different
from
the
usual
issues
that
we're
facing,
but
that
difference
actually
doesn't
mean
it's
not
important.
It
is
still
very,
very
important
to
do
it.
Just
is
a
little
different
and
I
think
that
needs
to
be
accommodated.
Yeah.
B
B
B
B
Yes,
drive
checks
on
coda,
but
to
be
very
specific
about
this
and
I
think
that
being
specific
here
actually
helped
the
contributor
pick
the
item
up,
because
something
like
this
is
very
vague
and
ambiguous.
Whereas
this
one
is
quite
specific
and
from
looking
through
a
list
of
issues,
they
were
probably
able
to
look
at
it
and
say:
I
can
do
that
and
I
just
wanted
to
encourage
that
kind
of
practice
going
forward,
because
I
completely
didn't
expect
that
a
contributor,
a
community
contributor,
would
pick
this
up.
B
A
B
Yeah
I
think
it's
brilliant
okay
in
blocked.
We
still
have
this
rake
task,
that's
failing
and
I'm,
considering
taking
this
out
of
the
active
state
and
actually
putting
this
back
on
so
the
epic
and
just
taking
the
status
off,
because
we
I
I
did
I'm
trying
to
think
of
this
this
whole
the
the
project
to
move
on
to
get
calm,
I
think
needs
a
whole
separate
section
in
this.
B
A
B
Just
I
feel
like
it's
constantly
here:
we
always
talk
about
it
and
we're
not
gonna
get
to
it
in
the
next
two
weeks.
So,
let's
just
put
it
aside
and
I.
Think
once
we've
gone
through
the
planning
board,
we
can
come
back
and
talk
and
talk
about
the
wording
out
to
get
a
block
on
project.
Okay,
I've,
great
documentation,
this
one's
also
blocked,
and
this
was
blocked
on
an
omnibus
ticket.
If
I
remember,
that's.
B
A
B
A
Can
upgrade
the
edge
a
cluster
without
upgrading
post-race
version
and
I
think
in
order
to
up
to
test
the
upgrade
documentation?
That
would
actually
be
enough.
We
still
need
to
test
the
Postgres
document
the
post
press
upgrade,
but
we
can
do
that
after
that
version.
So
essentially
what
I
mean?
What
I'm
saying
is
that
I
think
we
can
pick
up
the
the
issue
as
well
in
parallel
and
then
that
should
become
unblocked,
because
I
would
like
this
to
to
move
soon
again,
so
that
we
can
actually
release
it
any
into
a
point.
Four:
okay.
B
E
E
A
A
I
think
both
are
quite
important,
but
the
I
think
in
terms
of
timeline
and
being
able
to
release
the
H
a
instructions
I
think
the
upgrading,
the
upgrading,
the
entire
cluster
to
the
next
version
is
probably
a
little
bit
more
important.
It's
more
time-sensitive,
it's
more
urgent,
but
they're
both
important
so.
B
Tony
is
that
a
would
you
be
okay
with
switching
out
the
manually
upgrade
poster
is
for
the
upgrade
ghg
OHA
installation
issue
and
doing
that
ones.
I,
don't
have
any
preference
on
point.
Okay,
then
I'm
gonna
switch
that
I'm
gonna
switch
those
around.
Then,
if
that's
okay,
because
let's
do
the
one
that
is
the
time-sensitive
one.
A
B
Well,
I'll
switch
those
around
so
that
should
help
them.
Okay
in
dev
column,
sequel
statement
times
out.
When
doing
this,
Irish
spoke
to
Douglas
about
this
last
week
he
said
he
was
going
to
have
a
look
at
this
this
week
and
see
how
he
got
on,
because
this
was
about.
The
one
hand,
was
just
getting
the
customer
to
make
some
changes
to
the
time
out,
but
that's
not
really
enough.
We
have
to
know
what's
going
forward
and
what
this
gonna
look
like.
Oh
yeah,
so.
A
Yes,
also
I
need
to
follow
up
today,
because
I
I'm,
not
sure
the
customer
in
question
here
is
actually
in
a
working
state
at
the
moment
and
so
I
think
there's
also
just
for
me
to
follow
up
I'd
like
to
know
what
can
we
do
to
you
know,
get
the
customer
into
a
working
state
and
is
that
separate
from
having
an
implementation
for
this
SQL
statement?
I
just
don't
know,
I
have
to
dig
through
my
pile
off
of
emails,
that's
something
you
can
also
discuss.
Okay,.
B
A
The
one
thing
the
one
interesting
thing
in
question
there
is
if
this
may
require
another
back
port,
just
putting
it
out
there,
because
it
is
twelve
point
O
to
twelve
point
one
and
at
the
moment
the
the
way
this
is
configured
is
that
this
will
happen
automatically
and
the
sort
of
the
guardrails
we
have
in
place
here
are
a
warning
label
in
the
documentation.
Saying:
please
don't
do
it
automatically.
A
B
Know
I'm
completely
kicking
myself,
because
I
saw
this
coming
like
I
saw
that
this
is
gonna,
be
complicated
and
I'm
frustrated
with
myself
for
not
being
more
vocal
about
it.
When
we
did
it,
like
think,
I
put
one
comment
on
one:
we
should
probably
have
a
look
at
this,
it's
like
no.
We
should
have
done
anyway.
We.
B
We
need
to
be
clear
that
this
is
going
to
work
because
of
all
of
these
reasons,
but
and
I
think
that,
while
I'm
hoping
that
we've
we've
all
learned
from
how
challenging
this
has
been
to
how
we
need
to
address
this,
when
we
up
go
up
to
the
next
version
of
firebase,
because
we
all
have
to
do
this
again,
yeah
there's
been
some
activity
once
and
it's
done
forever.
We're
gonna
have
we're
gonna.
Do
this
repeatedly.
So
next.
B
C
B
Okay,
then
it's
not
what
Alice,
Trish,
okay,
Douglas
and
hinari
we're
taking
a
look
at
this
and
I
think
Douglas.
Just
having
a
look
at
this.
Okay,
all
right
Douglas
is
having
a
busy
week:
okay,
customizable
clone
URL.
When
I
asked
Mike
about
this
on
Friday,
he
said
he
was
taking
a
look
at
this.
He
was
actively
looking
at
this
last
week,
so
that's
fine
I
think
there's.
A
B
Okay,
yeah,
that's
good,
and
the
last
one
on
the
list
is:
we've
already
talked
about
that
being
the
upgrade.
So
that
concludes
everything
on
the
in
dev
side
of
things
so
shall
I
switch
over
to
you
favoring,
yes
and
I'm
gonna
stop
my
show
before
we.
We
open
up
your
screen
to
do
the
next
piece,
which
is
the
scheduling
into
the
ready
for
development,
maybe
now's
a
good
time
to
just
have
a
quick
chat
about
the
enabling
geo
on
github.com.
Yes,.
A
B
I
think
I
mean
we
had
a
brief
discussion
about
it
yesterday,
not
yesterday,
last
week
about
you
know,
how
can
we
push
forward
with
this
and
maybe
if
we
actually
need
to
be
putting
more
emphasis
and
more
focus
on
this
project?
So
the
way
that
I've
been
thinking
is
either.
We
can
start
scheduling
those
items
onto
the
board
and
we
just
start
or
we
spend
the
rest
of
this
week,
finishing
shaping
the
project
up
and
then
in
the
next
a
chilling
call.
We
start
seeing
those
issues
showing
up
on
the
board.
A
B
A
B
A
So
I
think,
actually
this
is
sort
of
maybe
going
ahead
a
little
bit
for
12.4
landing.
A
12.5
planning
to
me
sort
of
we
spent
we'll
probably
spend
most
of
12.4
finishing
up
some
of
these
small,
the
are
related
items
that
was
describing
it
anyways,
and
if
we
can
come
to
a
point
where
we
can
say
these
are
actually
the
next.
A
You
know
five
or
six
items
that
are
scheduled
and
on
the
board
for
the
are
for
12.5
I,
think
that
would
be
great,
and
if
we
can
do
this
within
the
next
week
or
that
would
align
actually
the
next
week,
I
would
align
really
well
with
my
my
planning
schedule
for
for
the
next
week.
So
I
think
this
is
good
and
I
think
this
is
probably
we
should
do
something
I'll
commit
to
probably
in
the
afternoon
today
I
will
revisit
the
ethics,
and
that
would
probably,
on
the
ethic
level
say:
okay,
I've
had
a
look.
A
These
are
the
outstanding
things
that
I
believe
need
to
happen,
and
you
know
you
can
look
at
the
mesh
can
look
at
them
and
then
we
can
kick
off
this
same
discussion
on
the
project,
but
I
think
if
our
goal
can
be
a
Friday
for
the
next
scheduling
call
to
have
a
much
better
understanding
of
the
Geo
D
our
project,
with
a
bunch
of
issues
that
we
feel
are
scheduled
both
for
for
work
with
the
team.
I
think
that
would
be
a
nice
thing
to
accomplish
this
I
think.
A
B
I
think
you're.
Your
approaches
is
more
sensible.
Then
let's
just
do
stuff.
That
sounds
good.
That's
it
they're
gone
for
Friday,
that's
good!
Yeah
I've
seen
it.
So
this
is
not
on
the
schedule
and
cool,
but
it's
just
something
about
the
back
port
I've.
Seen
that
Mariners
request
some
information
go
into
the
post
for
the
back
port
I'm
thinking.
We
can
probably
do
that
straight
after
the
call.
A
Can
you
see
the
board
okay
so
in
development,
updating
the
documentation
for
application
of
data
using
the
object,
storage,
I,
think
this
is
the
next
thing
we
need
to
do.
If
we
want
to
release
our
object,
storage
replication,
we
need
the
documentation,
updated,
so
I
think
that
that
should
remain.
There
I
think
a
real
is
on
vacation.
This,
yes,.
A
B
A
A
A
I'm
happy
with
this
and
then
the
PostgreSQL
upgrade,
so
we
we
already
switch
this
around,
but
I
think
this
is
also
still
something
that
actually
needs
to
needs
to
happen
and
ideally
relatively
soon,
because
I
would
like
to
confirm
here.
You
know
two
things
as
an
you
know:
how
will
we
do
this?
Is
there
any
additional
documentation
that
we
actually
need
to
be
to
write
to
make
that
easier
or
all
of
those
things,
and
also
to
just
upgrade
our
own
cluster
to
the
recommended
post
based
version?
A
A
A
B
So
is
it
a
right
if
I
asked
Zack
to
look
at
these
ones?
I
mean
I,
haven't
a
number
of
other,
quite
small
things
that
I'd
like
him
to
look
at
just
to
get
comfortable
with
the
development
of
this,
but
I
think
what
I
would
like
to
do
is
get
him
to
talk
to
Valerie
straightaway
in
his
first
week
about
these
two
issues
and
starts
to
pick
them
up
it.
Are
you
fine
with
that
I.
A
Am
fine
with
that,
let
me
put
them
in
the
ready
for
development
column.
My
like
my
understanding,
also
from
that
list,
was
that
this
is
essentially
I.
Think
for
for
for
this
iteration.
This
is,
do
the
same
thing
for
designing
repositories
that
we
are
doing
for
other
data
sources
as
well,
and
you
know
we
can
talk
about.
If
you
know,
we
need
to
revamp
the
entire
like
system
and
display
that
users
a
little
bit
later,
but
I
think
for
now,
yeah.
B
I
agree
with
that:
I
think
we
just
need
to
get
the.
We
were
already
so
close
to
getting
the
design
repositories
done.
Let's
just
do
the
UI
in
the
same
way
and
parts
of
bringing
zircon
borders
to
help
us
work
with
product
design
and
UX
to
figure
out
the
right
way
to
be
displaying
this
stuff,
but
for
now,
let's
just
do
this
the
same
and
we
can
do
the
real
work,
the
rear,
I,
don't
know
it's
not
rebrand,
just
a
redesign
for
the
next
one.
Okay,.
A
Okay,
so
the
next
one
here
so
this
seems
to
be
a
low-hanging
food.
So
there
is
some
some
discussion
and
I
actually
have
to
look
into
it
in
you
know
how
setting
a
geo
node
name
sometimes
is
is
tricky,
but-
and
there
are
slash
issues
and
there's-
maybe
a
a
piece
of
work
but
I
think
there
is.
This
is
a
documentation,
only
change
where
Mike
essentially
says
we
should
just
instruct
in
the
documentation
to
set
this
get
let
rails
geo,
node
name
and
there's
like
some
backwards
compatibility,
add
trailing
slash
logic.
A
So
I
think
this
is
a
second
piece
right.
We
need
to
deal
with
this,
but
if
we
can
already
make
it
a
bit
easier
just
by
improving
the
documentation,
I
think
we
should
do
so,
and
that
has
popped
up
a
number
of
times
in
the
in
the
next
weeks.
So
I
am
in
favor
of
spending
in
a
couple
hours,
just
fixing
it
for.
B
This
one,
can
you,
can
you
please
update
that
description
to
add
as
a
specific
link
to
where
in
the
docs?
It
is
because
I
think
also
that
this
is
the
type
of
thing
that,
because
it's
a
documentation,
only
change
you're,
asking
Zack
to
take
a
look
at
this
as
well,
because
he'll
need
to
get
familiar
with
how
to
make
documentation
only
changes,
yep.
A
B
A
A
I'm
lying
I
have
many
more
things
to
discuss,
but
you
want
to
point
out
from
for
at
all,
don't
made
a
proposal
to
minimize
steps
to
run
an
upgrade
with
our
post-deployment
migrations.
So
we
have
a
lot
of
interesting
and
wonderful
business
and
setting
things
up
when
doing
so
sort
of
disabling
post-deployment
migrations
and
tone
made
it
proposed
on
how
to
change
it.
I
like
that
proposal,
even
pitched
in
a
week
ago,
so
that
should
be
possible.
A
A
B
A
E
A
A
D
A
What
did
I
want
to
say
so?
The
first
one
is
I.
I
have
to
go
through
my
100
emails
with
notifications,
but
I
spoke
with
the
customer
last
week
about
being
willing
to
actually
put
us
in
touch
with,
let's
say,
regular
developers
who
could
use
geo
because
they
are
in
a
remote
office
and
they
were
quite
enthusiastic
about
it.
A
So
this
is
good
because
we
can
now
accelerate
sort
of
our
interviewing
phase,
which
I
think
would
be
quite
exciting,
so
I'm
in
touch
with
that
customer
now
and
we
may
be
able
to
actually
conduct
some
user
interviews
about
how
they
interact
with
Hitler
from
a
remote
office
and
I.
Think
that
would
be
first
step
to
actually
understanding
how
folks
that
you
know
don't
let
say
care
about
you
for
professional
reasons.
You
just
need
to
use
it
actually
to
use
it
or
not
use
it.
So
that's
exciting!
No.
A
Think
this
is
this
is
something
I
would
like
to
I
would
like
to
look
into
relatively
soon,
so
this
will
probably
not
be
implementation
work
first,
but
it
will
be
similar
to
what
we
did
with
the
geo
upgrade
process
with
tone,
actually
understanding
where
we
at
right
now
what
other,
like
main
problems,
what
can
we
do,
and
that
is
something
that
I'd
like
you
eventually
kick
off
in
12.5
the
planning
that
is
not
the
implementation.
Okay,
my
current
thinking
right
it
may
it
may
evolve.
A
B
One
thought
about
that
and
anything
that
I
wanna
talk
about
the
promotion,
demotion
and
failover
the
way.
That's
the
way
that
Valerie's
been
doing
this
thing
with
easy
last
week
about
this
delight
project.
Maybe
the
first
thing
to
do
to
kick
off
the
promotion,
demotion
and
failover
is
actually
to
try
and
perform
the
actions.
B
The
delight
project
is
just
DZ
gets
in
touch
with
a
random
developer
of
his
choice
and
spend
a
week
working
with
them
in
a
specific
area
where
they
pretty
much
test
out
once
they
do
see.
What
it's
like
from
a
customer's
perspective,
raise
any
issues,
perhaps
trying
to
address
some
of
the
issues
in
their
time.
But
it's
just
four
days
a
week
with
a
different
engineering,
but
I
was
thinking
from
the
point
of
view
of
kicking
off
the
promotion,
demotion
and
failover.
What
was
so
helpful
with
the
upgrade
project?
Is
we
started?
A
I
think
that's
absolutely
the
way
to
go.
I
think
this
is
something
I
think
we
did
for
installation
as
well.
I
think
the
first
step
should
certainly
be:
let's
do
it
and
see
what
happens
for
ourselves
and
I.
Think
I
mean
if,
if
the
Geo
upgrade
process
is
any
indication
for
for
this,
it
may
not
be,
but
there's
going
to
be
a
lot
of
interesting
sort
of
thought.
A
A
Know,
but
we
can,
we
can
talk
about
this.
I
just
want
to
say
that
if
we
look
at
the
roadmap
right
now,
the
disaster
recovery
will
certainly
extend
further
than
this,
and
you
know
we
can
we'll
be
planning
on
it.
The
verification
of
all
replicated
data
is
kind
of
similar.
It
will
will
require.
You
know
like
work,
but
we
are
a
little
bit
more
flexible.
A
We
want
to
do
this
year,
the
automatically
choosing
the
geo
node
for
the
best
user
experience
will
actually
close
out
if
we,
if
we
get
lucky
from
an
implementation
perspective,
with
the
work
that
Mike
assuming
and
then
the
I
may
actually
make
the
user
interviews
and
all
of
this
a
separate
epoch
right
so
that
we
can.
You
can
close
this
simplify
the
geo
upgrade
process,
I
think
with
the
release
of
eh
a
documentation
and
the
release
of
upgraded
zero
downtime
instructions.
A
I
think
this
is
so
that
the
first
bit
here
is
is
done
right
and
we
need
to
actually
think
about
what
the
next
steps
are
adding
on
replicated
data
types
not
going
to
end
for
a
while.
The
most
interesting
thing
there
is
littler
pages,
which
is
kicking
off
in
the
degree
implementation,
I
think
in
a
separate
team.
A
A
Anyway,
that's
sort
of
my
my
current
thinking
but
I
think
we
have
an
opportunity
to
shift
focus
a
little
bit,
because
a
lot
of
the
things
that
we
did
in
the
last
two
or
three
month
are
actually
coming
to
a
good
point,
or
we
should
actually
draw
a
line
in
the
sand
and
say
this
is
good
enough
for
now.
Let's
see
you
know
what
the
next
iteration
is
yeah.
B
A
D
A
A
B
B
A
C
D
B
B
D
B
D
A
A
B
A
B
Because
I
think
we
have
to
figure
out
like
to
fix
this,
we
need
to
figure
out
what
the
right
thing
here
to
do
is
and
I'm
wondering
if
the
right
thing
is
actually
connected
to
restyling
this.
Yes,
because
I'm
sure
that
this
is
just
working
off
the
exact
same
thing,
that's
happening
for
a
lot
of
job
artifacts.
This
isn't.