►
From YouTube: Geo Scheduling Call - 2019-10-25
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
A
B
Stuff
next
one,
we
removed
a
modal
about
how
to
work
faster
with
you,
which
is
great
because
yeah
we're
just
taking
this
out
when
I
needed
any
more.
You
now
have
the
features
around
this,
so
that's
great
and
Zack
was
able
to
just
pull
it
out
and
it
was
surprisingly
more
code
was
deleted.
Then
I
think
we
expected,
but
that's
a
good
thing
is.
A
B
A
B
A
B
B
B
B
Sorry
sure,
which
one
is
its
me
a
second
okay,
move
this
one
back
to
verification
here.
A
I
think
the
only
thing
that
is
I
mean
it's
a
little
bit.
I
made
some
changes
to
it,
but
I
think
we
can't
actually
move
this
forward
again
and
until
we've
resolved
the
situation
from
the
last,
a
break
demo,
essentially
I
think
Tom
and
I
agreed
that
the
problem
we
saw
in
the
in
the
upgrades
MO
should
not
actually
be
a
reflection
of
wrong
instructions
on
our
side,
but
until
torn
actually
manages
to
restore
the
cluster.
We
are
sort
of
holding
off
and
saying,
like.
Let's
wait.
B
B
B
A
What's
happening
here
is
there
are
a
number
of
small
items
that
I
list
left
for
the
more
robust
foreign
data
table
updates
and
how
they
exactly
will
get
resolved.
Is
it
something
that
Mike
is
working
on?
Is
my
understanding,
so
I
think
this
is
fine.
I
also
pulled
all
of
the
like
remaining
three
items
into
ether,
scheduling
or
on
the
board,
because
I
think
in
the
next
week,
or
so
we
can
make
decisions
on
some
of
those
where,
like
the
progress,
is
not
exactly
100
percent
clear
and
then
we
should
just
close
this
off.
A
B
A
A
They're
I
think,
like
also,
of
course,
whoever
takes
this
up
needs
to
look
at
it
right
make
a
decision
on.
If
this
is
worth
doing
or
or
not,
and
then
based
on
that
decision,
we
can
either
proceed
or
or
close
it
off,
but
for
that
epoch
because
we
decided
I
think
two
weeks
ago
that
we
wanted
to
ensure
that
we
finish
off
the
sort
of
loose
ends.
I
think
we
should
just
like
visit
these
three
tickets.
A
B
B
That
make
sense,
so
I'll
put
a
note
in
here
that
there's
just
there's
three
issues
left
on
this
epoch,
so
I
think
when
we
get
to
the
shading
part
of
it.
Let's
see
how
it
all
fits
in
exactly.
B
Okay,
right,
I'll
frame
the
shot;
okay.
B
I'm
doing
okay,
let's
see
what
else
is
in
this
board
and
then
we'll
collect
that
right
verification
of
design
repositories.
This
is
the
one
where
we're
having
a
quite
a
bit
of
discussion
around.
What
the
right
thing
to
do
is
so
I'll
leave
that
alone
splitting
this
into
the
two
pieces.
It's
actually
related
to
this
verification
thing
and
Douglas
is
heavenly.
Look
at
that.
B
B
B
A
A
A
Upgraded
from
eleven
eleven
point,
five
to
twelve
point
four
yesterday:
sort
of
I
guess:
I'm
I
have
this
on
muscle
memory,
but
I
need
to
document
it
and
it's
a
very
peculiar
situation,
because
I
encounter
no
errors.
It
works
from
eleven,
only
eleven
to
twelve
points
for,
but
there's
secondary.
It's
not
reachable
at
all
and
I
have
no
idea
why?
Okay,
okay.
B
B
Wasn't
a
leave
it
alone:
okay,
okay,
around
books
for
staging
expose
the
API
for
design
repositories.
These
are
the
two
that
are
working
working
in
conjunction
with
valeri,
doing
the
back
inside
and
then
front
inside,
and
so
they
agreed
on
the
format
of
the
Jason
payload
and
there's
a
bunch
of
working
progress
from
this
yeah.
A
Yeah
I
think
you
know
it's
it's
just
good
practice
and
again
this
is
one
of
those
items
that
actually,
when
it
was
one
issue,
it
had
a
weight
of
five
and
it
was
split
in
two
and
has
a
combined
weight
of
I
think
seven.
So
it's
really
interesting,
like
this
observe
there's
now
a
couple
of
times
and
I
think
it's
really
worth
doing
it
because
it
on
you
know
when
people
look
at
the
individual
things,
they
estimate
I
think
more
time
so
that
the
cumulative
is
higher
than
when
it
is
unsplit.
Yeah.
B
A
Okay,
so
I
think
if
we
sort
of
revisit
our
initial
plan,
we
said
that
we
were
going
to
close
off
the
remaining
epochs
and
two
of
them
automatically.
Choosing
the
right
note
is
done
and
the
documentation
bit
is
is
ongoing
and
I'm
forgetting
something
else
now
the
yeah,
the
object,
storage
replication,
but
we
still
have
the
foreign
data
ripple
and
robustness
ongoing,
and
we
have
the
design
repository
work
ongoing.
So
for
the
design
repository
stuff,
everything
is
actually
currently
I.
Think
development.
If
we
look
at.
B
A
A
There
is
three
open
one
in
progress
and
so
I
think
what
we
should
do
in
terms
of
scheduling
is
focus
first
on
finishing
of
those
remaining
like
issues
whatever.
That
means
right.
They
may
they
may
need
some
more
implementation
work,
but
we
may
not
need
to
do
them,
but
I
believe
that
we
should
just
make
sure
that
these
two
epics
get
closed
and
I.
Think
that
that
was
in
agreement
with
Olli.
We
decided
a
couple
of
weeks
ago
just
so
that
we
can
wrap
them
up
right.
Then
we
can.
A
A
A
A
A
B
Think
what
what
needs
to
happen
is
there's
a
lot
of
work.
That's
in
development
at
the
moment
that
needs
to
flow
through
reviews,
and
the
review
is
also
going
to
take
up
people's
brain
power
to
get
those
done
before
picking
up
new
work,
but
I
think
what
needs
to
happen
is,
as
people
become
open,
we
need
to
falter
people
on
to
the
new
set
of
projects
coming
up.
That's
exactly
my
thing.
A
B
B
A
B
B
B
B
A
So
my
so
I
think
we
need
at
least
at
least
I
need
at
least
like
a
week
or
two
right
to
like
get
those
other
two
things
into
a
state
where
we
can
pull
the
issues
onto
the
board,
which
is
not
a
problem
I
think
at
the
moment,
because
we
have
a
lot
of
other
things
happening
right
now
and
some
bugs
to
fix,
and
if
the
board
is
pretty
busy
but
I
think
that's
that's
kind
of
the
the
next
steps
that
need
to
happen.
Yeah.
A
A
And
I
think
there's
also
a
little
bit
of
opportunity
because,
like
I,
don't
anticipate
there
being
sort
of
looks
lump
in
in
the
built
board
because,
but
if
that
is
the
case,
I
think
we
have
a
number
of
sort
of
technical
debt
items
to
to
consider
as
well.
If
we
ever
fear,
you
know
we
need
a
little
bit
more
time
with
one
of
those
projects
or
scheduling
work.
So
I'm
not
particularly
worried
about
that.
B
A
A
A
I
think
the
I
spoke
with
Jackie
and
the
idea
there
is
to
also
work
out
some
of
the
what
they
call
experience
baselines
so
defining
you
know
what
a
user
needs
to
accomplish
in
the
admin
interface
you
know
and
how
easy
that
is
and
then
proposing
I
think
front-end
change
in
order
to
like
product
designs,
I'd
I'd
say
to
make
that
a
lot
easier.
Okay,.
B
B
A
A
We've
had
relative,
like
we
have
a
few
customer
facing
sort
of
issues
in
the
past.
So
when
doing
this,
you
know
I
think
we
need
to
remain
nimble,
because
the
may
things
may
be
things
that
come
up.
That
may
distract
us
a
little
bit,
but
I
also
spoke
with
Josh,
and
you
know
I
think
those
are
the
important
things
to
do
right
now
and
I
think,
especially
with
sort
of
us
taking
a
step
back
with
the
verification
and
the
adding
things.
A
A
B
A
I
think
honestly,
I
think
we're
in
an
interesting
transition
that
we
say
is
now
where
it's
like.
Some
things
are
winding
down
and
getting
closed
off,
which
I
think
is
super
exciting,
but
other
things
are
winding
up
again
right
and
I.
Think
that
is
that's
cool
and
I
hope
that
the
three
things
that
we
are
working
on
are
exciting
and
interesting
for
the
team
as
well.
A
B
And
I
think
what's
coming
up.
Next
is
a
nice
mix
of
things?
Is
you
know
the
everyone's
interested
in
getting
JIRA
rolled
out
on
github.com
I?
Think
so
that's
a
massive
project
and
then
between
the
promotion,
demotion
and
failure,
though
it's
just
something
that
hasn't
had
any
love
for
a
while
and
then
they
take
them
to
work
with
the
framework.
The
state
machine,
the
validation
stuff,
like
that's,
super
interesting
in
its
own
right.
So
there's
a
good
mix
of
stuff
in
there
at
the
moment,
I
think.
B
B
B
No
I
think
that
the
the
technical
work
stuff
needs
to
be.
It
needs
to
go
through
its
planning
phase,
though
so
the
one
thing
that's
come
to
mind
that
I
think
we
need
to
start
incorporating
in
these
calls
as
well
is
the
testing
stuff
that's
happening,
because
I
know
that
Ginny
is
working
on
pieces
in
the
background,
but
I'm
concerned
that,
because
it's
not
as
visible
as
this,
it
feels
separate.
Yes,
I'm,
happy.
A
B
A
A
B
There's
only
one
two
three
four
five
for
me
to
do.
Then
we
put
you.
Do
then
one
two,
three
four
five
I
was
just
thinking
about
how
it
it's
it
feels
separate,
but
it
doesn't
need
to
feel
separate.
It's
feeling
separate
just
because
it
we're
not
deliberately
yes
doing
more
to
include
it.
So,
let's
just
try
here.
A
By
the
way,
an
interesting
feature
that
I
think
will
be
incorporated
into
issue
boards
relatively
soon.
That
I
think
will
be
super
helpful
for
us
our
work
in
progress
limits,
which
means
you
can
essentially
say
there-
shall
not
be
more
than
X
issues
in
improvements
at
the
same
time,
which
I
think
is
in
a
nice
way
of
highlighting
when
there
are
too
many
things
happening
in
parallel.
B
B
A
B
A
good
thing
that
we
don't
actually
all
work
in
one
office
somewhere,
because
I
would
just
basically
bribe
the
plan
team
with
donuts
and
sweeties
and
making
them
tea
and
coffee
until
they've
got
implemented,
because
I
really
really
wanted
so
badly
yeah
anyway.
Anything
else
we
need
to
go
over
on
this
call.
I,
don't.