►
From YouTube: 2020 04 28 Geo scheduling call
Description
The weekly Geo scheduling call where we discuss the state of the Geo Build board: https://gitlab.com/groups/gitlab-org/-/boards/1181257?label_name[]=geo%3A%3Aactive
A
B
C
E
B
D
D
In
a
similar
fashion,
we
also
added
a
call-out
to
selective
sync
in
the
header
of
the
node
Cardon
out,
so
you
can
see
that
in
proposed
design.
We
also
consolidated
that
this
is
this.
Actually,
it's
been
important.
We
consolidated
the
term
groups
on
the
front
end,
so
namespaces
can
include
groups
or
a
user
groups,
I
guess
or
you
user
base
repos,
but
we
don't
support
that
right
now.
So
we
kind
of
this
for
you
user
kind
of
not
confusing
our
users.
D
A
That's
great
I
really
like
this
by
the
way,
I
always
felt
that
it
was
really
hard
to
know
what
was
selectively
synced
and
I
fear,
but
now
it's
very
explicit
as
to
you
know
what
is
actually
like
happening,
and
that's
quite
nice,
it's
that
so
it's
this
like
this.
Also
you
can
do
this
by
storage
shard.
Is
that
still
in
there?
Yes,.
F
D
C
C
Okay,
so,
oh
so
I
know
about
this.
One
Gabriel
got
this
merged,
which
mostly
needed
to
fix
something
with
how
you
know
replication
was
working.
There
was
like
one
tiny
little
bug,
plus
he
made
some
improvements
like
little
reef
actors,
as
well
as
adding
code
comments
yeah.
So
this
was
a
nice
improvement
to
our
self-service
framework
stuff.
A
C
C
C
B
A
A
I,
think
we've
used
weights
as
the
implementation
cost
right
like
as
I
knew.
How
long
will
it
take
to
actually
implement?
Whatever
is
asked
in
this
issue
and
I?
Think
syndrome
has
to
kind
of
wait
things
for
her,
like
UX
stuff,
so
I'm
happy
to
add
things
retro
actively
just
put
something
on
it.
I
think
maybe
more
interesting
is
to
assess
our
weights
were
actually
correct.
F
E
F
C
A
C
C
A
B
B
C
C
E
E
F
A
F
F
A
You
know,
write
comments
on
an
issue
to
mimic
the
style
of
somebody
else,
and
then
people
get
who
you
are
actually
imitating
and
I
wonder
if
we
would
be
able
to
actually
pull
that
off.
You
know
as
to
you
know
who
writes
like
like
what,
because
read
so
much
stuff
from
each
other.
It
would
be
quite
entertaining,
but
just
moving
on.
C
A
B
A
B
C
B
C
B
C
A
Yeah
is
it
fair
to
say,
because
I
have
to
the
details
but--my
here,
that
this
is
like?
Well,
there's
a
lot
sort
of
conceptual
okay.
This
is
maybe
what
we
want
to
do,
which
is
hard
to
get
sort
of
right
versus
the
actual
implementation,
which
is
maybe
a
little
bit
easier
once
you
know
how
to
do
it.
So
that's
how
I
interpreted
this
discussion,
yeah
I,
think
that's
accurate,
yeah.
C
This
is
mine,
it
just
got
maintained
a
review
and
I
need
to
address
the
feedback.
Oh
right,
is
this
the
one
yeah
yeah.
This
is
not
the
mr,
so
I
need
to
address
the
feedback
and
send
it
back.
There
wasn't
any
really
huge
feedback,
so
it
should
be
merged
relatively
soon.
Also,
since
that's
actually
in
with
you
yeah,
oh.
B
Yeah
this
is
mine,
and
this
is
a
strict
one.
Oh
stick
longer
than
I
was
expecting
okay.
That
is
one,
mr
openin,
that
you
said
the
four
values
for
these
columns.
There
are
some
solutions
to
meet
Stan,
and
can
you
about
the
proper
way
to
do
this?
I
feel
that
you
find
me
having
to
agreement
the
best
way
that
should
handle
this
I
hope
that
you
can
start
in
having
this
emergency.
A
Cool
that
was
I
I
said
it
earlier.
I
am
reading
the
discussions
between
Camille,
you
and
Stan,
and
I
have
to
admit
that
I
I
am
thoroughly
lost
on
some
of
the
technical
details,
but
it's
a
really
interesting
to
see
sort
of
how
this
developed
and
how
it
was
broken
down.
So
it's
actually
very
exciting.
D
Yep
so
I
have
three
of
the
five
Mrs
out
there
right
now,
and
so
two
of
them
are
a
review
and
then
we're
we're
getting
close
to
being
able
to
actually
merge
the
views
and
once
we
get
that,
then
I'll
be
able
to
add
the
screen
shot
for
you,
Fabian
on
your
release
post,
and
this
should
be
good
to
go.
I
I'm,
hoping
to
have
everything
open
by
the
end
of
this
week,
but
I
think
everything's
on
track
to
make
13
demo
for
sure.
So.
A
Cool
no
excited
I'm
really
excited
what
has
changed.
I
think,
especially
with
the
self
service
framework
getting
like
essentially
implemented.
We
hopefully
accelerate
adding
more
data
types
and
then
the
world
sort
of
UI
pattern
of
adding
additional
things
in
the
sidebar
would
not
have
scaled
at
all
and
actually.
C
G
C
G
A
All
right
so
for
my
understanding,
because
I
wrote
the
release
post
today
for
this
may,
we
may
have
to
actually
rephrase
the
issue
because,
like
I
think
here
the
business
about
the
command
line
to
the
great
task,
but
I
think
what
you've
done
actually
is
September
or
you're
working
on
the
waite
task
right,
but
you're
also
adding
the
API
that
allows
us
to
invoke
those
rake
tasks
from
a
primary
via
the
UI.
Let
somebody
know
it's.
G
H
B
A
A
G
C
G
C
Yeah
so
often
times
we're
kind
of
doing
like
I,
guess,
I,
don't
know
if
we've
discussed
it
for
a
while,
but
there's
a
thing
going
on
right
now
where
the
process
might
be
changing
to
like
domain
domain.
Experts
review
first
do
the
first
review
and
then
you
send
it
to
whichever
maintainer
and
the
Geo
team
has
been
kind
of
doing
that
for
a
long
time
already.
So
we
may
not
have
noticed.
C
C
F
Cool
okay,
you
know
it's
it's
an
adjustment
that
I've
also
been
getting
used
to
because
I
think
with
ecosystem
like
we
had
no
maintainer
x'
and
everybody
was
new,
so
everybody
frequently
used
the
roulette
recommendations
and
where
I've
noticed
with
geo.
It's
kind
of.
I
think
people
are
more
comfortable,
just
assigning
it
to
people
on
the
team,
because
they're
already
a
couple
maintainer
Zitz,
the
roulette
recommendations
are
generally
not
not
followed
as
closely
from
they've
seen
yeah.
C
Good
yeah
and
that's
there's,
there's
benefits
both
ways:
I
think
yeah.
As
far
as
the
process,
like
usually
usually
we'll
do
it.
The
first
reviewer
is
the
domain
expert
and
then,
if
you
want
to,
you
can
also
use
a
geo
maintainer,
because
we
have
a
couple
but
feel
free
to
just
assign
directly
liked
you
can
roll
the
dice.
If
you
want
or
you
can
choose
somebody,
however,
you
feel
like
and-
and
you
can
ping
directly
and
say,
can
you
please
review.
A
C
G
B
A
I
think
there
is
not
that
much
to
talk
about
in
terms
of
the
ready
for
development
column.
I,
think
the
the
general
like
layout
here
is
that
we
are
still
working
on
the
remaining
issues
for
closing.
I
would
be
sets
of
this
package
file
replication,
so
I
think
this
is.
You
know
that
remains
important,
and
there
is
quite
a
few
items
that
are
still
open.
Many
of
them
are
small,
but
I
think
we.
A
We
should
focus
on
that,
just
because
it
would
be
really
great
to
get
this
iteration
out
right,
get
the
front
end
in
place
all
of
those
things
and
ship
the
replication
in
thirteen
point-
oh
so,
like
this
epic
here
I
think,
has
pretty
high
priority
for
for
this
release
overall,
so
you
know
like
these
are
essentially
I.
Think
the
remaining
issues
in
the
in
the
ready
for
development
item
column
are
to
do
with
this.
We
also
have
a
similar
situation
for
the
the
package
file.
Verification
right.
This
is
sort
of
a
parallel
effort.
A
I
I
personally,
like
doubt
that
we
will
go
through
all
of
those
in
this
thirteen
point
O.
So
we
maybe
should
have
a
quick
discussion
on
how
far
we
think
we
get
because
I
like
I.
Just
like
my
observation
rather
maybe
wrong.
You
know
some
of
those
things
I
think
are
a
little
bit
tricky
before
they
they
make
it.
It
takes
a
little
while
so
may
need
to
adjust
a
little
bit,
but
this
should
also
happen
right
so
and
I
have
a
few
sort
of
items
here
in
the
ready
for
development.
A
So
that's
not
news.
I
have
one
minor
concern
which
has
to
do
with
the
hashed
storage
checks.
So
as
far
as
I
know,
we
know
what
we
need
to
do
in
order
to
remove
the
admin
ability
not
to
use
hash
storage
and
to
move.
You
know
some
traction
that
littles
here.
The
the
small
concern
is
that
this
for
science
and
needs
to
land
in
13-point.
Oh
because
of
the
major
release,
you
know
replication
shenanigans.
A
So
if
these
are
small
tasks
that
can
be
picked
up,
I
think
it
would
be
good
to
make
me
pick
them
up
relatively
soon,
because
then
we
like,
if
we
discover
something
unforeseen,
but
then
we
can
counteract
and
to
do
something
and
communicate.
I
think
what
I
would
like
to
avoid
is
a
situation
where,
for
whatever
reason,
you
know
like
relatively
close
to
the
release
deadline,
you
know
we
find
some
things
that
becomes
hectic.
I
would
like
to.
You
know
avoid
that
yeah.
F
A
A
A
Improvements
here
that
that
is
focusing
on
I
mean
so
I
think
that's
also
right,
you
know,
I
would
I
would
love
to
get
those
items
closed
out
again.
You
know
there
are
quite
a
few
small
things
here
right,
so
we
may
not
be
able
to
close
all
of
it,
but
that's
fine
but
like
getting
through.
This
is
really
important
and
that's
for
some
additional
context.
We,
like
I,
just
came
off
the
product
meeting
and
we
have
this
product
priority
list.
A
Essentially
you
know
the
things
that
we
should
consider
and
people
are
I
think
started
to
appreciate
that
performance
improvements
are
quite
important
and
even
though
there
is
a
discussion
on
you
know,
what
exactly
should
be
the
order
of
things
and
priorities.
I
think
the
takeaway
here
is
that
but
I
erase
that
point
as
well.
For
our
users,
you
know
performance
is
named
driver
of
the
user
experience.
If
things
are
slow
right,
they
are
often
not
particularly
happy
about
it.
So,
even
though
this
is
technical,
work
is
very
like
back
and
heavy.
A
Improving
the
performance
of
Geo
is
really
important,
and
it's
really
important
for
our
users
and
for
what
they're
trying
to
accomplish
so
also
from
a
product
perspective.
I
think
there
is
more
and
more
appreciation
that
things
being
slow.
You
know
whatever.
That
means
actually
have
a
really
detrimental
effect
on
our
users
and
I.
Think
that
was
a
survey
and
as
well
for
github.com
users,
which
is
obviously
you'd
like
a
biased
sample,
but
a
main
detractor.
A
So
some
more
people
were
unhappy
with
is
actually
performance
and
that's
one
of
the
things
that
people
really
notice
right
and
we
should
pay
attention
to
it
and
I
think
we're
pretty
good
about
it.
So
for
some
sort
of
a
digital
product
context
and
nobody
likes
four
and
a
Toretto,
so
getting
rid
of
it
seems
to
be
also
a
good
thing.
A
Yeah
and
then
there
are
two
I
think
UI
items
for
like
content,
things
for
for
Zack
and
as
far
as
I
know,
they
are
relatively
small
but
kind
of
nice.
One
is
just
the
empty
state
illustrations
which
are
kind
of
cute
and
awesome,
and
the
other
one
I
think
is
about
the
width
of
our
settings,
page
which
I
never
noticed.
But
apparently
the
width
of
our
settings
is
quite
small
and
the
thing
some
Jenny
had
a
moment
of
spring
cleaning.
A
It
was
just
like
it
needs
to
mister
change,
so
small
things
and
I
think
there
other
things
in
the
pipeline
with
regards
to
labeling
settings
better
and
removing
some
elements
from
the
UI
that
are
coming
up.
I
think
that's
it
so
I'm
quite
happy
with.
What's
in
here,
there
is
a
again
like
this
is
just
something
to
highlight.
A
We
also
have
I
think
a
ready
item
to
be
picked
up
for
the
maintenance
mode,
so
a
read-only
mode
that
is
kind
of
defined
and
we
had
a
POC
and
it's
ready
to
go
and
I
think
a
question
that
we
need
to
ask
ourselves.
Maybe
it's
like
how
fast
or
who,
in
terms
of
capacity
you
know,
has
actually
time
to
look
at
that,
because
it
is
completely
different
from
the
things
that
we're
doing
right
now
and
it's
a
feature.
It
is
important
for
say
Moses,
but
we've
we've
kind
of
like
we're.
A
A
I
am
so
like
this
may
be
an
intricacy
all
the
items
that
are
actively
worked
on
and
are
on
our
billboard
need
this
to
your
actives
scoped
label.
The
reason
for
this
is
that,
unless
you
do
this
and
you
filter
just
by,
for
example,
group
geo,
it
will
have
like
thousands
of
closed
items
here
and
thousands
of
copán
items
in
here,
and
that
feels
make.
E
D
A
I,
don't
think
so.
I
think
the
main
thing
for
four
thirteen
point
Oh
will
be
the
merging
of
the
sub
pages,
so
I
think
that's
perfectly
perfectly
acceptable.
We
also
still
have
quite
a
bit
of
time
in
the
release
and
the
way
I
see
see.
This
is
that
you
know
the
main
or
in
like.
For
me,
the
merging
of
the
sub
pages
has
the
biggest
customer
impact.
A
I
think
that'll
make
a
huge
difference
and
then
yeah
the
other
things
are
obviously
very
nice,
but
I
think
they
are
very
iterative
and
small,
but
and
no
in
the
habit,
especially
for
the
UI
and
the
release
post
to
kind
of
say
this
is
the
main
thing
you
know
that
we've
delivered
this
release,
but
here
are
another
like
four
or
five
small,
like
bits
that
we
actually
delivered
as
well,
that
make
your
life
better
and
so
I
think
that's
totally
fine.
We
can
adjust
that
pretty
quickly
cool.
A
B
A
I
mean
as
a
maybe
as
a
general
comment
in
the
Nick
and
I
spoke
about
that
as
well.
So
there
are
a
couple
of
things
that
we
would
like
to
maybe
like
it's
not
necessarily
an
approval,
but
maybe
a
change.
So
the
one
is
at
least
a
German
saying
it's
like
to
like
touch
my
own
nose.
St,
like
talk
about
what
I
can
do
better.
A
You
know
tech,
routers
and
marketing
folks,
so
that
closer
to
the
release
like
the
merge
deadline,
you
know
this
is
not
something
that
causes
any
stress
for
anyone,
because
then,
like
I,
think
I
hope
that
an
effect
that
that
has
is
that
you
know
if,
for
whatever
reason
you
know
something
is
taking
taking
longer,
then
we
can
catch
that
and
look
a
bit
before
the
deadline.
We
just
moved
the
release
post
item.
That's
it
mine
there
will
there
be
another
release
and
I
think
that
will
help
a
little
bit.
A
I
think
the
other
thing
is
that
we're
doing
these
calls
every
week,
because
we
want
to
continuously
deliver
value
right
and
I
I
think
we
haven't
really
I,
don't
know
like
father
like
had
a
better
conclusion,
but
at
least
speaking
for
myself
and
like
meeting
some
of
the
most
recent
feedback
on
sort
of
maintainer
bits-
and
you
know,
like
pressure
to
review
things
quickly.
I
would
I
would
like
us
to
avoid
sort
of
rushed
last
week.
Went
if
want
to
release
I
think
that
would
like
I
don't
know.
I,
don't
like
that.
C
Say
something
about
that
like
so
the
gitlab
general
process
is
supposed
to
be.
You
deliver
seventy
percent
or
whatever
of
the
things
that
you
plan
to
deliver,
so
it's
kind
of
like
built
in
to
how
we
do
things
that
it's
gonna
be
like.
Oh
actually,
we
can't,
you
know,
deliver
30
percent
of
these
things
right.
So
the
main
thing
is
like
staying
in
constant
communication
more
and
more
especially
leading
up
to
a
week
or
two
before
the
deadline,
so
that
we
actually
know
like.
A
F
Yeah
I
think
that's
a
good
good
point
that
we
we
always
try
to
be
ambitious
in
our
planning,
but
they
yeah
I,
think
part
of
that
is
on
on
Fabian
and
me
to
to
make
the
space
for
people
to
feel
comfortable.
Maybe
delaying
maybe
setting
the
expectation
that
something
might
not
make
it
ahead
of
time
and
not
create
the
the
environment
where
it
feels
like
there's
pressure
to
promise
that
something's
going
to
make
it
and
then
and
then
you
know,
create
stress
and
trying
to
deliver
it
by
that
cutoff.
F
A
And
they
disinvite.
Do
you
like
honestly
and
like
very
few
things
like
that
we
could
have
my
experience
come
out
of
things
that
were
rushed
out
of
the
door,
but
like
most
most
of
the
time,
what
that
does?
Is
it
essentially
kicks
the
can
down
the
road
until
people
try
to
use
it,
and
then
it's
broken
right
and
also.
Similarly,
in
my
experience,
many
of
our
customers
are
very
perceptive
to
us
explaining
why
certain
things
are
not
happening
right,
that's
like
because
they
have
no,
you
know
they.
A
They
have
risk
in
their
business
right
if
they
do
things
that
don't
work,
especially
in
our
area.
So
it
may
be
a
little
bit
different,
but
then
there
may
be
situations
right
and
exceptions
when
certain
things
need
to
happen
at
a
certain
time
right
and
then
that's
always
a
possibility,
but
I
think
the
standard
should
be
different
right.
A
We,
as
do
team,
already
have
a
lot
less
because
we
do
this
every
week
and
you
know
I
think
that's
actually
a
good
thing
and
you
know
we
should
release
as
frequent
as
it's
required
for
our
customers,
but
I
think
you
know
I
think
maybe
you
pointed
out
the
the
other
day
Mike.
It's
like
you
also
release
when
it's
ready,
but
I
mean
I.
Think
we
very
much
care
about
that
and
the
other
note-
and
this
is
an
idea
that
Nick
brought
up
and
I-
think
we
work
with
these
ethics
like
we
can.
A
Actually
we
we
closed
a
lot
of
issues
right
and
we
work
our
way
through
these
effects,
and
you
know
that
is
more
relevant
I.
Think
for
our
like
release
like
for
our
development
progress
in
a
way,
but
when
you
look
at
this
and
says
like
hey,
how
much
have
we
moved
this
forward
right
and
that
is
important
and
when
that
will
be
released
right,
this
kind
of
a
separate
concern,
in
my
view,.