►
From YouTube: 2022-02-09 Sharding Group Sync EMEA
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
All
right,
hello,
everyone!
This
is
the
group
sharding
sync
meeting
for
the
us
friendly
time
zones
that
also
overlaps
with
parts
of
europe,
but
is
not
good
for
people
in
apac.
So
here
we
are
the
summary
from
the
earlier
meeting.
Welcome
omar,
for,
I
think
our
newest
team
member.
So
please
set
up
coffee
chats
with
him
to
get
to
know
him
a
little
bit
better
yeah
you
wanna
at
least
quickly
say
hi
again,
you
don't
have
to
do
the
entire
sphere
that
you
did
in
the
morning.
I
think.
B
Yeah
hi
everyone.
I
think
I
met
more
people
in
this
meeting
than
in
the
previous
one
yeah
I
there's
there
are
new
people,
like
patrick
yeah,
feel
free
to
reach
out
to
me
anytime.
If
you
want
to
have
a
chat
or
if
you
want
to
know
me,
I
also
want
to
know
everyone
more
yeah.
That's
it.
I
think,
there's
a
weird
sound
from
my
neighbor
who
has
chosen
the
worst
time
to
do
some
construction
now
yeah,
that's
it
for
myself.
C
Thank
you,
oh
by
the
way,
omar
your
your
microphone
probably
not
connected
well,
your
voice
is
volume
is
low.
B
A
A
We
also
quickly
reviewed
a
question
that
was
to
do
with
infrastructure's
priorities,
because
that
came
up,
I
think,
for
now.
The
most
important
thing
is
to
get
the
ci
production
cluster
deployed.
A
You
know
it's
the
next
thing.
Maybe
that
can
be
parallelized
a
little
bit.
That
depends,
I
think,
more
mostly
on
infrastructure.
A
Yeah
we're
rolling
out
and
foreign
key
fair
queueing.
I
think
that's
actually
ongoing,
so
adam
was
doing
that
and
then
I
shared
a
bit
of
reading
that,
I
think,
is
quite
interesting.
There'll
be
a
product
management
book
club
probably,
but
for
those
interested,
otherwise
a
good
article
about
people
being
non-fungible
and
team
topologies.
C
Yeah
number
two.
Actually
I
have
a
question
for
number
one
c:
actually
I
told
infrastructure.
If
you
recall
you
understand,
on
monday
I
told
the
infrastructure
that
pidgey
bouncer
is
the
immediate
priority
for
infrastructure,
but
something
like
the
the
production
ci
cluster
is
more
important.
So
I
just
we
have
a
stand
up
today
in
about
30
minutes,
so
I
can
change
that
to
say
that
this
is
a
more
higher
priority.
I
mean
the
ci
cluster
deployment
in
production,
but
I
can
see
they
are
working
in
parallel.
A
Yeah,
I
think
my
impression
from
the
outside
is
they're
doing
exactly
the
right
thing,
they're
working
in
parallel
on
it,
so
I'm
not
sure
there's
any
need
to
do
anything
now.
We're
not
blocked
so
like
I'm,
not
sure
if,
if
I
would
overthrow
statements
in
the
fear
of
causing
more
confusion,
but
I
think
that
is
that's
what
came
out
of
the
morning.
Okay,
I
will
just
you
know,
stand
up,
keep
two
items
there
and
just.
C
Attach
based
on
the
progress
and
won't
repeat
again,
which
one
is
more
important.
And
unless.
A
C
I
don't
recall
the
name.
The
first
name
starts
from
our
the
that
person
is
working
working
on
the
on
the
pidgey
bouncer.
C
Yeah,
okay,
thank
you.
The
number
the
way
yeah
the
number
two.
The
number
two
item
I
have
is
just
a
question.
So
the
cia
cluster
orifice
three
production
deployment
that
looks
like
the
same
cluster
will
be
available
on
the
25th,
that's
roughly
about
two
weeks
later
than
initially
planned.
C
So
my
question
is:
is
that
two
weeks
delay
exactly
two
weeks
delay
to
the
overall
timeline?
The
reason
I
don't
think
that
is
the
case,
because
our
our
our
staging
and
the
production
you
know
deployment
are
two
work
streams.
They
are
not
exactly
coupled
to
each
other,
I
mean
they
are,
but
but
what
I
see
is
our
phase
four
staging
can
still
move
on
and
is
independent
on
the
phase
3
production
deployment.
C
A
A
Even
if
the
production
cluster
is
not
available,
but
if
the
production
cluster
is
two
weeks
late,
it
means
that
we
can
start
the
phased
rollout
on
production
two
weeks
later
and
unless
we're
willing
to
reduce
the
time
the
burn
in
time
of
these
phases
in
production,
it
will
essentially
mean
two
two
weeks
longer
until
we
we
are
going
to
sort
of
finish
the
deployment,
because
at
least
that's
my
understanding.
So
the
later
production
cluster
available
means.
C
I
see
your
point
yeah,
so
basically
the
production
work
stream
actually
is
delayed.
That
is,
that
contributes
to
the
overall
timeline.
A
Yeah,
because
we
we
consider
the
end
of
the
the
project
when
we've
delivered
a
decomposed
database
in
production.
That
is
when
we
say
like
we
claim
success
beforehand.
It's
it's
on
staging
and
it
may
may
run
there
for
a
longer
time.
Okay,
yeah,
that's
my
understanding
and
where
is
that
correct?.
D
C
Okay,
so,
ideally
we
shall
we
still
want
to
finish
phase
three
production
baking,
the
two-week
baking
time
before
proceeding
or
before,
actually
entering
the
phase.
Four
staging.
A
You
know,
cluster
that
would
be
need
to
be
need
to
be
maintained
and
sas
and
like
with
all
the
bells
and
whistles,
and
I
think,
like
I'm,
not
sure
how
much
we
can
compress
the
timeline
without
with
sort
of
forcing
them
to
compromise
on
the
quality
there
either,
which
will
then
bite
us
later
on.
You
know
has
bitten
us
once
like
where
they
discovered
the.
A
C
D
It
didn't
happen
yet
so
application
was
not
yet
dependent
on
any
significant
changes.
So
I
I
think
there
is
really
hard
to
say
if
there
is
like
a
way
to
compress
this
timeline,
maybe
maybe
later
when
we
see
that
things
are
going
significantly
better,
but
right
now
I
think.
C
Thank
you.
Thank
you
for
the
information
yeah,
I'm
clear
thanks
for
helping
me
understand
the
time.
Lastly,.
A
Cool
well,
I'm
very
excited
to
have
omar
and
the
team.
That's
really
cool
and
I'm
also
excited
to
have
kanye
back.
So
I
can
pester
him
for
coffee
chats
now.