►
From YouTube: Geo Scheduling Call - 2019-07-19
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
I've
also
put
the
meeting
agenda
in
the
calendar,
invite
so
that
people
have
access
to
that
now
and
Fabian
I
think
the
document
is
shared
with
you,
I
think
you're
in
it
at
the
moment.
Yes,
so
the
only
thing
I
want
to
just
say
for
people
watching
this
is
a
new
process.
They
are
probably
going
to
be
things
that
don't
work
so
well.
B
I
think
I
think
just
for
for
us
also
to
to
reiterate
and
describe
the
process
on
a
high
level.
So
we
essentially
has
three
relevant
boards
or
for
this
meeting
and
I
can
probably
actually
share
my
screen
and
then
we
can
just
quickly
describe
the
flow
and
actually
the
state
of
affairs,
as
is,
if
you
don't
mind,
yeah.
A
B
So,
as
you
can
see,
this
is
the
plan
board.
There
are
no
open
issues
near
because
I
still
have
to
like
push
items
in
here.
So
the
idea
behind
the
on
board
is
that
essentially
we're
a
couple
of
months
ahead
in
the
tickets
that
are
or
the
issues
that
are
on
this
board,
so
they're
not
actually
being
actively
worked
on
by
the
team
right
now.
They
are
issues
that
I
need
to
look
at
and
look
at
with
the
team
to
validate
the
problems.
B
So
I
think
here
that
elasticsearch
support
for
given
up
Giro
is
a
good
example.
Actually,
because
you
know
we
have
that
on
the
list
to
do
but
I
think
it's
still
a
little
bit.
You
know
like
amorphous
and
there's
some
discussion
in
the
issue,
so
I
need
to
actually
look
at
this
and
describe
the
problem
is
a
bit
better
and
from
there
I
move
it
to
the
solution.
Validation,
where
I'll
also
work
very
closely
with
an
engineer
to
actually
describe
okay.
B
What
what
would
we
be
able
to
do
in
order
to
support
the
elastic
such
better?
How
could
that
look
like
and
then?
Lastly,
the
planning
breakdown
when
we
are
in
a
state
where
we
are
pretty
sure
this
is
a
problem
we
want
to
fix
and
there
is
a
solution
more
or
less
described,
but
it's
still
something
that
requires
breakdown
and
potentially
a
little
bit
more
more
polished
and
I.
Also
added
the
needs
weight
in
here.
B
I'm,
not
sure
I
want
to
want
to
keep
that,
but
the
essential
idea
is
that,
when
issues
make
their
way
through
this
at
the
end,
they
are
in
a
state
where
they
belong
to
an
epoch,
so
they
ideally
they
should
be
going
to
larger
effort.
They
have
a
good
description,
so
people
actually
know
what
what's
in
them.
They
are
weighted
in
terms
of
effort
and
they
are
like
more
or
less
ready
for
development,
which
you
know
basically
means
they.
They
should
be
able
to
be
picked
up.
B
A
A
What
needs
to
be
done
and
how
to
move
things
forward
here
and
in
my
role
on
this
board
is
to
just
be
kept
to
make
sure
that
I
keep
myself
up
to
date
about
going
through
here
in
the
discussions
that
are
happening
and
making
sure
that
I'm
giving
engineers
good
support
for
what
they
need
to
help.
You
figure
out
what
health
to
make
things
work
here.
Yes,.
B
So
like
in
essence,
I
would
at
the
moment
this
is
sort
of
where,
like
I,
need
to
triage
parts
of
our
backlog
well
or
at
least
the
list
of
open
tickets
and
decide.
You
know
which
ones
I
actually
want
to
invest
more
time
on
based
on
customer
feedback
and
then
I'll
put
them
in
this
board
and,
as
I
said
in
an
ideal
world,
we're
actually
quite
a
bit
ahead
of
the
building
process
here,
which
allows
for
proper
investigation
and
I.
B
Think
that
should
prevent
you
know
a
situation
where
you
just
pick
up
things
that
are
really
fine
very
quickly,
but
that's
sort
of
in
the
future.
Okay
I'll
go
to
the
scheduling
board,
and
this
is
the
first
time
that
we
are
actually
looking
at
this,
and
so
what
I've
done
is
I've
pulled
in
issues
here
that
are
scheduled
for
12.2.
So
this
is
me
optimistically
scheduling
things
for
for
the
12.2
milestone
ahead
of
the
introduction
of
this
process,
so
I
think
what
later
on
I
need
to
do
today.
B
He
has
actually
decide
out
of
those
issues
that
are
open
and
ideally
already
have
a
way.
I
think
that
quite
a
few
that
don't,
which
is
I,
think
I
think
that
I
would
like
to
discuss
with
you,
because
we
don't
know
how
they
they
are
to
decide,
essentially,
which
ones
are
in
a
state
to
actually
move
them
into.
B
It
raishin
cycles
on
deciding
what's
next
right.
We
can.
We
can
be
a
little
bit
more
nimble
in
that
regard,
rather
than
having
to
do
like
a
huge
planning
exercise
when
once
a
month
to
plan
for
the
milestone.
Where
is
here
more
or
less
continuously,
we
are
going
to
show
the
built
board
for
the
engineers
so
that
it
is
more
of
a
pipeline
rather
than
a
stop-start
process.
B
B
A
As
to
how
much
we
can
be
pulling
into
the
active
into
the
active
column
here,
because
we
don't
want
to
have
this
huge
active
column
that
is
actually
just
so
much
work
that
we're
never
going
to
get
to
the
end
of
it.
We
want
this
to
be
like
a
manageable
set
of
work.
That's
probably
only
one
to
two
weeks
worth
of
things
that
are
in
here,
which.
B
A
It
and
the
goal
for
me
is
to
make
sure
that
we're
always
working
on
the
most
important
thing
is
because
they're
going
to
be
things
that
come
up,
that
we
need
to
insert
into
this
process
somehow,
because
we
find
them
through
customer
calls
or
various
different
methods,
and
at
least
this
way
we
can
always
be
working
on
the
important
things
and
it's
easy
to
get
them
added
in,
but
I
think
for
at
least
in
my
mind.
The
long-term
for
me
is
that
this
board
no
longer
has
the
needs
weight,
column
by
degree.
B
A
B
True,
so
like
the
reason
why
I
did
it
is
to
adjust
for
reality
where
that
is
not
the
case,
but
we
we
could
because
I
also
have
it
over
here.
One
thing
that
I
could
do
is
I
can
actually
move
them
back
out
of
their
scheduling
for
now,
because
I
think
we
have
enough
to
feel
like
a
week
or
two
already
here
and
then
actually
make
that
an
a
priority
for
the
next
week
like
get
the
weight
on
all
of
those
things.
I
think.
A
That
that
would
actually
be
better
because,
as
part
of
the
adding
the
weight,
it's
also
just
to
confirm
the
people
that
whoever,
if
these
are
in
epochs,
to
confirm
that
the
owner
has
provided
enough
information
and
that
they're
comfortable
with
needs
to
be
doing
here.
It
needs
to
be
done
here,
but
if
they're
not
part
of
an
epic
just
to
be
completely
sure
that
that's
correct
and
just
double-check
that
there's
anything
that
might
stop
us
from
from
building
it.
A
B
A
Do
it
I
was
just
thinking
while
you
do
that
we
should
actually
have
one
other
board,
that's
just
planning
scheduling,
building
and
then
we
can
just
quickly
drag
them
between
the
two
but
I.
Suppose
we
don't.
We
won't
really
need
that
on
a
day-to-day
basis.
It
was
just
I'm,
looking
at
all
the
different
ways.
We
can
use
these
scoped
labels
filters
and
creating
workflows,
but
it's
it's
an
awesome.
It's
nice
and
quick
to
be
able
to
not
have
to
add
one
and
remove
another.
That's
for
sure
yeah.
B
B
B
A
I
click
on
Geno
planning
everything
else.
Everything
shows
up
again.
Oh
you
know
why,
because
you've
used
geo
planning's,
nothing
so
there's
one
there's
two
you're
planning
breakdown
and
then
you've
got
another
label.
That's
geo
planning!
You
see
the
dirt.
That
is
so.
If
you
go
to,
if
you
go
to
on
on
your
needs,
wait
column.
There
click
on
one
of
the
gray,
labels
that
says
geo
planning,
just
click
on
it
and
you
know
in
the
in
the
column
where
your
cursor
is,
you
can
see
geo
planning,
breakdowns,
yeah,.
B
A
A
A
A
B
A
A
A
A
B
A
B
I
think
that's
actually
I
think
this
is
how
we
describe
that.
So
in
my
in
my
planning
board,
let's
say
and
I'm
also
like
this
one
is
peel
you
bone,
so
we
can
actually
fix
this.
So
this
has
the
needs
weight,
but
it
actually
has
a
weight.
That's
mislabeled!
So
if
I,
if
I
remove,
needs
weight
here
and
I
now
actually
add
ready
for
development
and
geo
scheduling,
okay,.
B
A
B
B
A
So
I
don't
want
to
get
distracted
on
this
one,
but
that
was
an
11
which
seems
like
it's
very
big
yeah.
A
A
B
A
I'm
just
quickly,
looking
all
the
way
from
the
right
I'm,
just
checking
that
that
geo
cluster
test
was
done
by
Douglas.
So
that's
great
I
like
to
check
from
the
right,
because
those
are
the
things
that
are
closest
to
being
done,
and
also
ordinarily,
before
this
meeting
I
should
have
gone
through
everything,
and
so
that
I
can
quickly
like
without
having
to
look
everything
I'd
be
able
to
say
this
is
the
state
of
everything
I
think
trying
to
get
ready
for
this?
A
B
B
A
A
Okay,
there
is
only
one
major
quiz
that
is
outstanding,
which
actually
looks
like
it
was
closed.
That
one
was
closed
Artic
entirely,
so
all
of
the
mood
requests
looks
to
be
completed.
So
what
I'm
going
to
do
on
this?
One
is
just
ping
tone
to
ask
what
the
status
of
this
is
yeah.
Can
you
do
that
quickly?.
A
A
A
A
A
B
A
So
the
next
column
is
the
in
dev
column,
so
I
know
that
the
support
for
replication
for
daca
registries
has
the
end
up
being
much
bigger
than
than
we
expected.
So
that's
still
in
progress
and
I
think
there's
quite
a
bit
of
work
still
outstanding
on
those,
so
those
are
small
in
there,
then
the
object,
storage
one
when
I
spoke
with
Gabrielle
earlier
in
the
week
he
said
that
there
were
a
couple
more
days
after
development
before
this
would
be
ready
to
go
for
the
big
review.
Okay.
A
This
has
been
quite
a
lot
of
quite
a
lot
of
work,
and
this
one
and
the
docker
issue
are
two
examples
where
we
could
have
found.
We
should
have
and
out
that
this
was
bigger
than
we
thought
earlier
on.
Yeah
I'm,
hoping
that
this
new
process
helps
us
find
that,
because
having
two
unbelievably
huge
issues
at
the
same
time
is
quite
quite
I,
don't
think
it's
ideal
because
things
can
be
parallelized
and
it's
going
to
be
quite
difficult
to
review.
So
no.
B
B
A
B
A
Correct
in
the
next
one,
the
rake
task
fails
on
do
dat
get
leprechaun.
This
is
one
that
I
know
that
Devin
and
Douglas
have
been
working
on
together.
I
know
that
the
infrastructure
team
has
been
under
pressure
to
they've,
had
some
challenges
on
github.com,
so
I'm
not
expecting
this
to
progress
quickly,
but
it's
something
that
I'm
keeping
an
eye
on
just
because
we
need
to
get
this
up
and
running,
but
I
think
that's
going
to
sit
on
the
board
for
a
while.
While
we
help
while
we
help
them
through
some
things.
Okay,.
A
B
B
B
A
B
B
A
A
B
A
B
B
A
So
I
think
in
that
case,
and
with
this
one
specifically
if
this
is
something
that
we
want
to
get
done
because
we're
in
this
weird
beginning
state,
because
we
can
ping,
you
know
we
could
ping
Douglas
and
start
the
conversation
today
about
what
needs
to
be
done.
I
mean
not
today,
so
you
don't
leave
but
as
to
what
needs
to
be
done,
break
it
down.
Stick
it
straight
back
onto
the
boat
outside
of
a
scheduling
meeting,
so.
B
A
A
B
A
B
B
A
B
B
A
B
A
A
B
A
B
I
would
say
that
the
automatic
verification
items
are
probably
at
like,
as
they
are
right
now
quite
important,
because
if
you
open
them,
if
you
look
at
this
I
think
this
is
one
of
the
continuation
of
verifying
or
replicated
data.
And
if
you
look
at
that
ethic
I
like
there's
still
like
quite
a
few
items
that
are
needing
to
be
worked
on,
most
of
which
actually
like
a
sign
to
12.2,
because
I
really
want
to
finish
this
epoch
and
I
think
the
biggest
items
in
order
to
actually
get
there
are
the
automatic
verification.
B
A
A
This
is
Gabriel,
yes,.
B
Exactly
so,
like
I
asked
him
to
assign
weights
to
some
of
the
other
like
issues
last
week,
but
I
don't
think
he
has
gotten
around
doing
this
yet,
but
maybe
this
year
requires
a
little
bit
of
a
breakdown
and
I
know
that
mike
has
some
insight.
So
this
is
something
that
ideally,
let's
say
next
week:
I
can
schedule
it
both
Gabriel
and
potentially
Mike
just
to
like
break
this
down.
Yes,.
A
B
A
B
B
A
B
A
A
B
A
B
A
B
A
B
A
B
A
B
B
A
Know
so
previously
we
did
the
work
I
think
to
actually
store
the
checksum.
That
was
done
in
eleven
point
in
so
this
is
to
show
the
differences
now
do
we
need
you,
EXO
UI,
to
tell
us
how
to
do
this,
or
do
you
think
we
we
have
a
good
enough.
Do
you
think
this
is
a
simple
enough
thing
to
add
to
the
screen?
I?
Don't.
B
A
A
A
I
have
a
pink
burner,
I've
been
Gabriel
for
that,
so
I
think
we
need
to
leave
this
one
where
it
is
until
we
know,
because
if
we
need
uux
aport,
we
need
to
get
them
involved.
What
I
would
what
I
do
think
is
when
we're
adding
things
to
the
screen,
we
need
to
have
a
screen
shot
of
what
this
is
going
to
look
like,
even
if
it's
you
know
drawn
on
a
piece
of
paper
screenshots,
yes,.
B
B
B
A
B
A
I'm
fine
for
that
one
to
get
pulled
over
as
well.
That's
someone
just
needs
to
look
at
it:
okay,
non-empty
tracking
database
I.
Remember
this
one:
okay,.
A
B
A
A
Good
question
so
I
have
the
three
things
we
pulled
over
were
warned
push
no
no
I'm
already
on
the
Billboard,
so
yeah
I
see
okay,
so
you're.
Looking
at
the
scheduling
board,
I've
got
the
Billboard
open
warm
and
get
push.
I
see
that
the
rake
the
drops
but
cannot
recreate
so
I
can't
get
that
break
to
your
check
automatically.
Yes,
I
see
that
one
prevent
non-empty.
Yes,
I,
see
those
three
okay.
A
B
A
A
B
A
A
Okay,
then,
the
last
piece
of
these
meetings
needs
to
be
going
through
a
bug
list
and
the
technical
data
items,
but
I
think
that
we've
already
got
into
an
hour
on
this
meeting,
so
I
think
in
future
meetings.
This
first
part
will
go
much
faster
because
they'll
be
less
of
the
explaining
in
the
talking
and
the
figuring
stuff
out,
and
we
had
stuff
with
the
two
scoped
labels
that
did
the
show,
and
then
we
can
talk
about
bugs
and
technical
data
in
the
second
piece
of
the
meeting,
I.
A
B
B
A
A
B
A
A
I
think,
therefore,
moving
this
into
active
I
would
want
to
read
this
I
just
want
to
make
sure
that
I,
don't
think,
there's
enough
stuff
that
we
have
already
prepared.
I
just
want
to
read
that
and
make
sure
that
I
understand
what's
in
there
and
that
anything
else
has
been
thought
of
for
anything
about
uploads
and
sorry
about
upgrades.
I
just
want
to
make
sure
that
I've
been
keeping
a
closer
eye
on
things.
B
B
A
A
B
No
I,
agree
and
I
think
I
think
it'll
be
I.
Think
one
of
the
main
advantages
I
can
see
is
that
there's
a
little
bit
more
sort
of
like
if
checks
is
maybe
too
strong,
but
before
we
actually
move
things
forward,
will
at
least
have
to
have
spoken
about
it
a
little
bit.
Make
sure
that
we
understand
it
right
that
you
know,
like
the
content
of
the
issue,
makes
sense.
B
So
it's
it's
weighted
all
of
those
things
so
when
when
they
are
actually
being
worked
on
by
you
tone
or
somebody
else,
you
don't
have
to
worry
that
much
about
you
know.
Oh
I,
have
this
amorphous
item
I,
don't
really
know
what
it
is
now
I'm
supposed
to
do.
Something
I
think
that's
what
we
want
to
avoid.
Yeah.
A
Well,
we
want
to
pull
all
of
those
strange
questions
back
out
into
the
beginning
and
by
the
time
we're
actually
developing
it's.
When
all
of
those
questions
are
answered,
then
we
know
what's
happening
like
we
know
how
to
get
this
done
and
I
think
also
I
mean,
as
we've
seen
from
both
that
dr1
and
the
object
storage.
A
Sometimes
we
get
these
issues
at
this
stage,
where
there's
so
many
open
questions
and
the
thing
lands
have
been
so
much
bigger
than
we
expected
and
I'm,
hoping
that
this
process
helps
us
not
have
those,
because
it
can
be
quite
frustrating
when
you
start
coding-
and
it's
like
oh
well.
Actually,
this
is
huge.
This
is
massive,
so
yeah,
that's
it
anyway.
I
must
get
to
another
call.
So
thank
you
very
much
for
this
I'll
upload.
The
recording
sounds.