►
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).
A
B
B
B
A
B
Because
the
new
issues
have
been
created
and
attached
to
the
new
ethics,
which
is
also
which
is
also
good,
because
we
were
able
to
figure
out
that
that
was
actually
way
bigger
than
11
and
that's
good
to
know
now,
rather
than
when
we're
halfway
through
it.
Investigative
updating.
The
tracking
database
is
necessary
on
secondaries.
B
Yes,
that's
right!
The
related,
mr,
was
closed.
So
we
got
that
closed
and
we
determined
about
that
that
it
can
we
determined
that
it
can
be
done.
It
can
automatically
be
run
when
upgrading
so
done.
Awesome
I'll
go
through
those
after
the
call
and
get
rid
of
the
Geo
active,
because
we
can
move
those
out
and
actually
I
like
doing
this.
B
As
part
of
this
call,
because
we
can
see
that
the
work
that's
been
done
in
the
week
and
if
it's
closed
out
immediately
afterwards,
we
can
see
that
every
week,
yeah
okay
in
review,
I
need
to
close
some
things
up
here.
So
I
have
some
space:
okay,
support,
replication
for
docker
container
registries.
As
far
as
I
understand
the
last
Valerie
was
busy
doing
the
testing
and.
B
A
B
I
know
that
he's
focusing
on
yeah
he's
definitely
back
on
that,
after
being
on
the
sidekick
stuff,
he's
waiting
for
a
review
on
sidekick
from
Camille,
which
I
think
must
have
happened
by
now,
but
he
was
doing
this
while
he
was
waiting
for
that
improving
the
general
upload
steps.
You
were
doing
that
with
having
some
fun
as
danger.
Yep.
B
A
B
B
B
Okay,
I'm,
not
gonna,
okay
blocked
ones.
I
spoke
to
Valeria
about
this
one,
and
we
agreed
that
he
has
enough
to
do
on
the
dock
container
registry
right
now.
So
as
soon
as
he's
finished
on
that,
he
will
pick
this
one
back
up
again,
so
that
we
can
finish
that.
The
reason
that
this
was
blocked
was
because
we
needed
access
to
staging.
We
have
access
to
staging
now,
so
either
ash
tone
or
Douglas
will
run
this
for
Valerie
or
I
will
just
request
staging
access
for
Valerie
to
do
it
himself
right.
A
C
B
C
B
A
A
B
A
So
I
think
there,
so
it
is
in
progress
but
I'm,
not
sure
where
it
Stone
has
done
any
coding
on
this.
Yet
alright.
So
there's
a
lot
of
discussion
about
the
upgrade
steps
and-
and
things
like
that,
so
we
could
argue
that
technically,
like
I,
don't
know
if,
if,
if
tone
has
done
any
any
code
on
this,
yet
it's
maybe
something
to
follow
up
yeah.
B
A
I
know
that
tone
is
very
active
on
the
understanding
of
the
updates.
That's
necessary
zero,
downtime
bitcoins.
So
in
a
way
it's
it's
really
nice,
because
there's
a
lot
of
discussion,
I
think
on
what
are
the
steps
that
we
actually
need
to
do
and
why
do
they
exist
in
the
first
place?
That's
I
think
definitely
preliminary
work
before
yep
before.
B
B
Because
I
know
that
he's
been
there,
we
go.
He
finally
got
this
piece
merged,
so
this
is
related
to
the
worn
on
get
push.
As
far
as
I
understand,
this
is
related
to
the
one
on
get
push
and
because
this
is
finally
done,
I
think
simplify
internal
post
receive
yeah,
so
this
piece
is
finally
done,
which
means
he
can
now
come
back
to
wrapping
up,
so
he
has
been
working
on
this.
It's
just
that.
It's
been
on
this,
mr
okay,.
B
A
C
A
B
Really
good
feedback,
yeah,
yeah,
cool,
okay
way
to
give
the
404
yeah
I
saw
someone
else
precursor,
yep,.
B
A
B
A
B
A
B
Okay
right
well,
this
is
really
good
that
we
have
a
community
person
doing
this.
It's
bad
that
it's
now
got
an
problem
with
the
endpoint,
but
okay
move
on
close
tabs
to
the
right,
and
also
thank
you
to
tone
for
already
taking
a
look
at
the
mo
okay,
specs
failing
and
master
I
did
ping
ash.
There
is
still
no
movement
on
this
yeah.
B
Having
a
trouble
replicating
I've
tried
locally
using
the
same
dog
images
and
without
success
I'm
starting
to
wonder
like
I
mean
this
is
we're
putting
in
a
lot
of
effort
for
this,
and
we
can't
actually
figure
out
what's
going
on.
So
maybe
we
need
to
step
back
and
look
at
what
the
the
spec
is
doing
and
if
this
trick
is
actually
right,
I
think.
A
B
B
Cool,
what's
next
consider
alternative
methods
for
replicating
data,
so
when
I
last
chatted
with
Douglas,
he
was
working
on
a
proof
of
concept
over
here
and
I
did
think
the
whole
team
looking
for
comments
on
this
earlier
in
the
week
and
I
see
ash
has
been
commenting,
which
is
great
and
I've,
dated
the
my
description
with
the
next
steps.
Next
steps
to
do
control
the
concurrency
put
it
in
the
flag
and
hair
tests,
awesome
cool.
A
I
mean
so
I
had
a
discussion
yesterday
with
with
Josh,
and
he
I
think
made
the
good
point
and
we're
kind
of
addressing
this
already.
That
I
think
one
of
the
issues
that
we're
going
to
say
is
as
a
team
or
maybe
are
already
facing,
is
that
adding
new
data
to
geo
is
not
so
straightforward
and
in
a
way
like
at
the
moment,
we
are
I,
think
replicating
less
than
half
of
all
the
data
sources
right.
A
That,
as
part
of
this
we'll
see
and
in
general
think
we
should
probably
start
thinking
about.
How
can
we
make
it
really
easy
to
add
new
data
to
geo
and
replicate
new
data,
and
that,
like
that,
can
take
different
forms
and
shapes.
But
I
worry
that
we
will
end
up
in
a
position
where
we're
kind
of
the
bottleneck
and
the
gatekeepers
for
for
this,
and
that
that's
not
going
to
scale
particularly
well.
Nothing
but.
B
I
think
that's
why
it's
useful
that
Douglas
is
working
on
this
alternative
methods,
because
at
the
moment
we
saw
from
the
docker
registry
stuff,
it
was
hard
in
a
number
of
ways,
and
it's
always
going
to
be
hard
from
the
perspective
that
different
data
types
will
take
different
forms
and
I.
Don't
we're
never
going
to
be
able
to
get
past
that,
but
we
can
make
it
easier
from
the
Geo
perspective
of
not
having
to
do
all
of
these
things
all
over
the
place,
with
the
way
that
the
code
is
now
so
exactly
so.
A
I
agree
and
I
think
but
I
think
that
maybe
we
we
can
take
that
a
step
further
in
a
little
while
and
say:
okay,
you
know
what
would
it
actually
take
to
allow
other
people
to
think
about
geo
right?
How
can
we
make
it
maybe
easier
or
like
what
is
sort
of
the
system
for
this
going
forward,
because
I've
seen
this
now
at
least
twice
where
we
looked
at
Oh?
How?
How
can
we
do
custom
books
and
then
turn
out?
A
B
The
other
thing
that
needs
to
happen
as
well
is
and
I
don't
know
how
this
I
mean.
I,
don't
know
how
to
do
this,
but
what
I
see
is
when
people
start
talking
about
adding
a
new
data
type,
we
need
to
get
involved
in
the
discussion
right
then,
and
an
engineer
from
geo
has
to
be
involved
in
the
design
of
whatever.
That
is
so
that
we
know
that
we
can
replicate
it,
but
I
don't
know
how
to
see
what
those
when
the
teams
are
thinking
about
that
no.
A
But
I
think
we
can
also
think
about
like
some
some
things
like.
Maybe
if
you
know
a
new
data
source
is
being
added,
we
can
who
can
add
geo
to
the
definition
of
done.
I
can
say
you
are
not
done
unless
this
actually
supports
geo,
and
here
is
the
maybe
the
checklist
or
the
process
or
whatever
it
ends
up
being
in
the
first
iteration
that
you
will
that
he
will
need
to
like
consider.
You
know,
because
otherwise
it's
not
happening
and.
A
Yeah
I,
so
we
have
a
similar
like
well,
it's
not
similar,
but
it's
kind
of
similar,
similar
problem
in
in
my
previous
place,
where
you
know
we,
we
processed
a
lot
of
biological
data
and
every
bit
of
data
looks
different
writers,
essentially
an
ETL
pipeline,
and
you
need
to
normalize
them
and
do
all
sorts
of
transformations
of
them.
And
if
you
have
only
one
team
that
can
do
this
and
other
teams
want
to
do
other
things.
Your
bottleneck
stuck.
C
A
It's
stuck,
and
so
then,
essentially
the
idea
was:
let's
provide
a
framework
for
people
that
describes
very
clearly.
If
you
want
to
do
this,
you
will
need
to
do
these
five
things
and
that
I
devious
then
well
documented
it
understood,
and
then
people
are
empowered
to
do
it
by
like
themselves.
I,
don't
know
if
that's.
A
B
B
B
Cool
last
one
cleaning
up
orphaned,
project
repositories,
I
was
reading
this
last
week
in
my
brain
is
oh
right.
I
had
a
discussion,
so
valeera
had
done
a
bunch
of
work
on
this
and
then
I
started.
Reading
that
Gabriel
and
Douglas
were
starting
to
talk
about
different
things
and
I
started
to
get
concerned
that
now
we
were
going
to
have
to
go
a
different
route
from
what
Gabriel
has
her
from
what
Valerie
had
already
done.
But
after
some
discussion
we
can
come.
B
We
can
merge
when
it's
when
the
mood
when
it's
been
reviewed
and
everything
we
can
merge.
What
has
been
done
here
and
the
issues
that
may
not
necessarily
be
covered
by
the
work
that
is
done
can
be
done
as
a
separate
can
be
done
as
a
separate
issue.
We
don't
have
to
go
back
and
wait
so
I'm
much
happier
about
this
and
that's
why
there's
this
last
comment:
I'll
move
this
side
discussion
to
a
new
issue
because
it
is
actually
a
separate
issue,
oh
yeah.
A
B
A
Not
ideal
and
I,
you
know
I
think
Eric
has
been
really
good,
dropping
in
information
on
how
they
should
look
and
I
actually
opened
a
merge
request
for
like
something
unrelated
here,
which
is
to
update
the
to
create
a
link
to
the
troubleshooting
guide
when
people
are
checking
the
upgrades,
because
that's
I
think
that
was
also
hard.
Like
you,
you
check
your
upgrades,
you
get
an
error
message
and
they
don't
know
where
to
go.
B
A
B
It
was
just
I,
took
it
straight
out
of
the
comment
that
Mike
made
at
the
bottom,
where
it
was
just
much
more
specific
about
what
needed
to
be
done
and
I
think
that
helps
whoever
picks
it
up
to
know
that
this
is
not
an
open
request
for
please
refactor
all
the
things.
That's
please
do
this
very
specific
thing.
Yeah.
A
A
B
A
B
Mentioned
in
merge
request,
he
was
looking
at
this
with
I
think
this
has
come
out
of
looking
at
that
stuff
with
Jenny
about
automating.
Maybe
that's
what
it's
for.
B
A
B
A
B
B
B
B
B
B
C
A
A
B
A
B
A
B
A
B
C
B
A
B
C
B
So
what
we
need
to
do
for
that
issue
that
you've,
that
you've
got
on
the
screen
at
the
moment
is
the
plan
was
to
take
the
ansible
project
that
we
already
have
and
updated
to
do.
H
a
stuff
and
I'm
still
of
the
opinion
that
if
there's
no
decision
about
the
provision
of
project
that
we
need
to
just
crack
on
with
that
yeah.
C
B
B
You
have
twelve
point
three
or
twelve
point
four
or
twelve
point
three,
but
we'll
see
what
happens
and
just
because
any
work
that
we
do,
it
would
be
better
to
put
it
into
the
thing:
that's
going
to
be
for
customers
and
I'm,
really
hoping
that
they
make
a
decision
so
that
we
can
support
what
they
do,
but
if
they
haven't
done
it
by
the
time
we
need
to
do
this
thing.
We
need
to
just
carry
on
okay.
B
C
C
B
A
Here
it
may
be
because
it
you
know,
it's
not
the
next
thing
that
we
can
we
pick
up.
There
are
two
small
sort
of
documentation
web
pieces
here
that
are
part
of
the
upgrade
it's
which
I'm
actually
happy
to
put
on
the
to
put
on
the
Billboard.
This
one
doesn't
have
a
that's
a
wait.
It's
not
good,
but
I
can
give
you
the
wait.
That's
it
but
I
don't
know.
A
A
B
A
B
B
A
B
A
B
B
A
B
A
B
C
A
Think
so
too
I
think
we
have
plenty
of
things
in
the
backlog
that
are
ready
to
be
done.
So
in
terms
of
the
planning
stuff,
the
planning
breakdown
here
so
I
am
going
to
work
with
Douglas
today,
I
think
he
we
have.
We
are
going
to
upgrade
his
sage,
a
cluster
from
12.1
and
as
part
of
that
I'm
going
served.
What
the
individual
things
that
we
are
you
with
your
microphone
again.
Sorry.
A
A
So
this
is
like
something
where
we
have
no
documentation
on
the
lju
upgrade
for
AJ
and
I
would
like
to
document
very
clearly
like
okay,
creating
this
documentation.
What
does
that?
Actually?
What
are
the
individual
things
that
we
need
to
do
so
I
work
on
that?
Actually,
today,
I
haven't
heard
back
here
from
from
the
customer.
I
don't
need
to
follow
up
and
then
I
honestly
I
need
to
like
go
through
a
lot
of
my
solution,
validation
items
here
and
just
make
sure
that
they
are
in
good
shape.
A
A
So
I
would
like
to
see
people
actually
in
a
remote
office
using
it
lab
with
secondary
configured
and
just
trying
to
understand
you
know
when,
when
you
ask
them
hey,
can
you
show
me
how
you,
for
example,
create
new
issues
right?
How
do
you
do
that
right
and
just
to
understand
the
vocabulary
that
people
use
when
they
interact
with
geo
to
understand
a
little
bit
further?
A
A
A
Yeah
yeah
so
that's
happening,
and
then
there
are
just
a
few
other
things
that
I
need
to
need
to
track
here
with
garbage
collection
for
container
registries,
restrictive,
selective
sinks.
This
is
there's
a
lot
of
sort
of
probably
bigger
items
in
here
that
you
know
are
making
its
way
their
way
through
to
a
stage
where
you
can
work
on
them.
Well,.
A
A
B
B
A
A
B
B
A
Validation
say
is
because
we
already
know
that
we're
going
to
do
this
and
I
think
that
will
become
the
schedule
of
all
really
quickly
because
we
want
to
push
forward
with
us,
and
that
means
that
in
the
scheduling
board
you
know
like
maybe
in
a
week
or
so
there
may
be
new
things
that
we
know
we
need
to
do
for
or
like
maybe
in
two
weeks
right
for
12.4
that
are
related
to
disaster
recovery.
But
we
don't
have
those
items
yet
so,
okay,
so.