►
From YouTube: Geo Scheduling Call - 2020-02-12
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).
B
A
I
make
it
wider
for
this
call,
because
I
know
that
it
doesn't
do
widescreen
unless
you
tell
it
to
be
wide,
just
like
okay
in
the
clearest
columns,
okay
in
the
close
column.
Today
this
is
merged,
which
is
wonderful
and
lovely
yeah,
and
this
also
helps
us
unblock
getting
Gio
on
staging
working
performing
telework,
and
so
this
is
wonderful
that
this
is
not
in.
A
B
A
B
A
B
B
B
And
I
think
you
can
actually
move
this
into
ready
for
development
now
that
we
we
are
at
it
I
think.
The
two
things
as
I
understand
that
need
to
happen
is
enable
this
on
staging
and
actually
see
that
it
works
and
then
also
test
it
on
local
GCP
items
because
local,
like
a
DCP
installation
and
run
some
tests
there,
and
then
we
could
remove
it.
Okay,
yeah
I,
like
with
a
self-service
developer
framework,
I,
decided
to
keep
it
in
the
release
post
because
that's
more
developer
focused
right
and.
A
A
B
B
B
A
See:
okay,
but.
A
When
I
asked
him
does
this
means
that
two
to
seven
one
nine
no
closed,
because
it
says
here
this
should
close
that,
but
it
hasn't
and
Michelle
is
closed,
this
some
classic.
If
we
should
close
that
lots
of
this,
isn't
that
and
it's
ending
this
okay,
so
I'm
gonna
leave
that
where
it
is
I'm
not
gonna,
take
it
off
the
closed
column,
okay,
enable!
Oh,
that's
new
I
didn't
see
that
enable
object,
storage.
Closing
this
since
the
shift
changes
have
been
merged.
We
can
access
the
project
page.
Oh
no
was
last
night
hooray
that.
A
Yeah,
it's
I'm
great,
it's
it's
coming
along
now.
This
is
really
good.
Okay,
we're
moving!
Those
are
replicating
objects
in
object,
storage,
right,
shade,
just
removal
and
resync.
This
is
the
bug.
Yes,.
B
A
A
A
A
A
A
A
A
We
get
the
team
that
is
working
with
us
to
do
the
works
and
fix
it
and
ship
it
and
at
the
time
and
I
still
agree
that
we've
made
the
right
decision,
because
we
can't
always
be
picking
up
everything
in
the
whole
codebase,
even
though
we
land
up
finding
stuff
just
because
of
the
nature
of
geo.
So
you.
B
A
A
A
B
B
A
A
A
But
I
see
that
that
oh
right,
this
is
the
one
there's
the
following
needs
to
be
added:
he
reopened.
It
he's
changed
the
description,
but
there
hasn't
been
any
other
commits
here
like
an
awful
lot
about
this.
A
Investigate
orphaned
registries,
okay,
this
is
this-
has
been
an
interesting
one,
because
it's
hard
like
that,
a
problem
that
could
also
happen
for
customers
who
do
this?
What
happened?
Was
we
reactivated
the
node
and
said?
Please:
sync:
everything
realized
that
we
couldn't
sink
everything
because
things
were
timing
out,
so
we
narrowed
it
down
to
just
be
selective
sync,
but
that
means
that
there's
a
whole
bunch
of
orphan
projects,
so.
B
A
A
B
A
A
A
A
A
It's
going
to
be
really
good.
This
is
the
second
generic
component
that
he's
been
able
to
put
together
and
yeah.
It
sounds
like
it
has
a
potential
for
a
nice
and
in
fact,
that's
really
possible
and
last
one
here
this
one.
This
follows
off
the
back
of
the
other
single
source
of
truth
anymore,
moving
things
into
the
registry
tables,
and
it
was
for
job
artifact,
uploads
and
projects,
as
requested
by
Douglas,
so
that
we
could
unblock
staging
even
further
and
he's
done
it
for
job
artifacts
and
uploads.
B
B
A
A
B
We
like
this
is
kind
of
three.
It
isn't
it's
like.
If
we
look
at
the
framework
idea
of
this
right,
I
think
this
is
the
kind
of
stuff
that
in
the
backend,
we
should
make
it
as
simple
as
possible
right
and
not
rely
on
complex
things
like
this
and
I.
Think
we
can.
We
can
sort
of
tag
it
on
right,
as
as
a
part
of
making
this
framework
easy
to
use
right
also
for
end
users
like
reduce,
upgrade
problematics
and
so
on
and
so
forth.
B
A
That
sounds
great
I'll,
be
really
happy
when
that's
when
that's
there,
because
as
I
mean
I
understand
why
foreign
data
ruffle
was
used
initially,
but
there
are
some
complexities
to
it.
So
by
removing
it
we're
just
going
to
make
it
simple
in
so
many
places.
It's
really
really
good
right.
That's
everything
in
dev
so
shall
I
use,
switch
control
over
to
you
sure.
A
B
B
B
B
B
A
B
For
the
verification
part,
we
have
one
already
in
progress.
The
the
second
one
in
the
epic
is
this
one
here
insurer
package
file
checksum
on
primary,
which
is
over
here
I,
could
move
it
over,
but
I
think
then
we
have
certainly
enough
in
the
in
deaf
section.
We
could
also
leave
it
here,
but
I'm
kind
of
inclined
to
move
it
over
I.
B
A
B
A
B
This
was
a
has
actually
closed
right.
The
when
deployments
are
issued
for
staging
on,
kill
comm.
This
one
is
being
worked
on.
This
has
not
been
worked
on
yet,
but
we
have
a
little
bit
of
time
for
the
self-service
framework.
These
three
like
these
four,
are
now
all
ready
for
development
and
and
scheduled
mm-hmm.
A
B
B
A
B
B
Think
that's!
That's.
It
I
think
for
like
from
a
planning
perspective.
What
I
need
to
do
in
the
next
in
the
next
couple
of
weeks
is
I
had
quite
a
few
very
productive
discussions
based
on
some
customers.
We
take
feedback
on
potential
for
proxying
requests
for
the
secondary
web
interface
and
I.
Don't
know
if
you've
seen
this
I.
B
So
we
sort
of
swap
around
at
some
point,
which
I
think
will
mean
that
we
we
don't
have
to
wait
for
a
major
release.
You
know,
but
in
the
next
major
release
we
can
kind
of
retire
the
secondary
work
interface
if
it
doesn't
make
much
sense
and
yeah.
So
that's
that's
one
of
the
discussions.
I
think
this
is
a
PVC
that
we
need
to
do
to
establish
how
this
could
work.
I
would
have
quite
a
few
advantages
and
open
up,
I
think
entire
pathway,
so
for
additional
improvements
over
over
time.
That's.
B
That's
an
interesting
thing
to
think
about.
It's
also
nice,
because
that
is
another
opportunity
where
we
won't
get
to
it
this
month,
maybe
not
in
next
month,
but
then.
Actually
at
that
point
we
may
have
a
really
nicely
broken
down
epic,
with
an
established
POC
where
we
can.
You
know
then
actually
do
the
things
relatively
swiftly,
at
least
to
sort
of
a
first
MVP
iteration
I,
think
that
would
be
quite
valuable
for
quite
a
few
of
our
customers.
A
And
I
like
how
this
issue
is:
quite
it
also,
it
actually
does
lay
out
a
path
forward.
It's
not
just
in
general.
This
might
be
an
idea.
It's
like
these
are
the
things
that
we
could
actually
do
to
do.
This
yes
and.
B
B
Yeah,
it's
it's
a
it's
a
bit
tricky
because
we
don't.
We
have
a
little
bit
of
uncertainty
regarding
the
users
of
the
Geo
web
interface
itself.
That
being
said,
I've
spoken
in
the
last
few
months
to
enough
customers
who
have
concerns
regarding
the
usability
of
the
secondary
web
interface.
That
I
feel
quite
confident
that
an
alternative
with
a
like,
like
that,
makes
the
user
experience
better
right
is
something
that
many
of
our
customers
would
value
and
we
could
minimize
the
risk
of
taking
something
completely
away
by
just
swapping
the
defaults.
That's
my
current
thinking.
B
It's
like
we
don't
disable
the
thing
as
it
is
like
right
now,
but
we
just
say
by
default,
the
behavior
will
change.
You
could
still
go
back
to
the
old
behavior
if
you
want
to
yeah
we'll
see,
I
think
that
that
could
that
could
be
quite
quite
interesting
and
we'd
see
how
it
goes,
but
I
like
I
think
this
is
something
that
some
Jim
can
also
help
with
yeah,
like
I
feel
like
with
the
with
the
user
experience
side
of
things
with
the
secondary
web
interface.
We've
boxed
ourselves
in
the
little
bit.
B
B
B
Right
now
is
like
the
is
ask
to
recovery
angle
right
and
the
self
service
framework,
but
I
think
we
have
quite
an
interesting
opportunity
here
to
start
thinking
about
this
in
parallel
to
improving
the
administrator
interface,
to
sort
of
make
make
significant
improvements
in
in
the
UX
of
of
geo
overall,
and
not
only
in
like
that
sort
of
robustness
of
the
system
and
additional
features
in
in
the
arm.
The
main
problem
is
that
I
would
love
to
be
like
to
have
like
twice
as
many.
B
A
A
B
A
A
Well,
I
mean
that
then
it
becomes
enough
inefficient
to
just
constantly
switch
everything
it's
about.
This
is
the
project
that
we're
working
on,
and
the
next
thing
that
will
that
will
come
up,
can
change
at
a
moment's
notice
until
the
implementation
starts
and
I
think
that's,
what's
so
valuable
about
this.
It's
not
saying!
Well,
we
that's
the
next
project
because
we've
decided
it
even
though
it's
not
really
important
anymore,
it's
decided
so
we're
going
to
do
it,
which
exactly
is
where
I
think
long-term
planning
fails
a
little
so
but.
A
If
that's,
the
state
of
play
can
I
have
five
minutes
of
your
time
after
I.
Stop
the
recording
sure.