►
From YouTube: Pages Priority Sync
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
Yeah,
basically,
it's
just
a
state
status
update
for
what
happened
in
the
last
few
weeks,
so
camille
had
a
big
poc
and
basically
there
were
two
parts.
First
part
was
refining
what
jacobs
did
on
the
vfs
work
and
the
second
is
actual
implementation
of
zip
archives
storage,
as
this
vfs,
so
we
merged
his
part
completely
and
like
there
is
one
small
test
fix
which
I
already
approved.
I
will
see
like,
I
hope,
jaime
will
approve
it
and
I
will
merge
tomorrow,
but
yeah.
This
part
is
finished.
B
It's
already
in
production
as
of
today
and
nothing
broke
so
far.
So
that's
awesome,
yeah
also
yeah
and
jaime
works
on
the
next
half
of
this
work,
which
is
basically
taking
this
yeah,
zip
archive
storage
and
attaching
to
the
vfs.
So
we
merged
the
first
big
chunk
of
it.
I
guess
yesterday
or
monday-
I'm
not
entirely
sure,
even
though
I
did
that
anyway,
so
we
merged
that
and
yeah,
he
has
another
piece
of
it
but
yeah.
B
I
I
I
guess,
since
we
have
like
a
week
to
the
end
of
this
release,
I
like
I'm,
not
sure
that
we
can
actually
test
it
on
dogsgitlab.com
by
the
end
of
this
milestone
but
yeah.
Hopefully
that
will
be
soon
enough,
but
actually
I
didn't
think
with
jaime
on
that.
So
I
I
guess,
like
rails
part,
is
already
merged.
So
if
you
want
to
get
the
best
like
estimate,
it's
probably
best
to
ask
crimey
on
that
part.
B
So
yeah
that's
about
the
camera's
work.
So
what
I
did
is
on
my
part.
I
also
finished
my
small
chunk
to
test
on
dogsgitlab.com.
Then
I
speak
to
spoke
with
camille.
He
actually
provided
me
a
very
nice
hint
to
the
very
similar
work
verify
team
did
recently,
so
I
just
took
this
and
broke
down
deployments
issue
up
to.
I
don't
know
10
separate
small
issues,
so
yeah
we'll
work
on
this
but
yeah.
B
I
hope
that
I
can
actually,
I
don't
know,
get
like
four
of
them
into
this
release,
but
review
work
currently
takes
too
much
time,
I'm
not
sure
and
yeah.
I
basically
just
started
yesterday
on
one
of
them,
so
I
probably
won't
get
four
of
them,
maybe
one
or
two
indeed.
B
No,
no,
no,
no,
that
basically,
first
time.
First
test
is
gitlab.com
right
for
this
test.
We
took
the
shortcut
and
we
basically
already
have
artifacts
archives
uploaded
to
the
storage,
also
to
object
storage
on
the
gitlab.com,
so
we
decided
that
yeah
we
can
just
surf
from
these
artifacts
without
any
more
work.
We
need
to
actually
do
to
serve
other
pages.
I
don't
know
so.
This
big
new
epic
about
the
deployments
is
basically
copying
these
archives.
B
Once
pages
are
deployed,
we
want
to
have
a
separate
a
place
in
the
object
storage
from
these
archives
and
copy
these
archives
there,
because
archives
can
be
like
artifacts,
can
be
destroyed
at
any
moment
just
because
user
deleted
a
build,
a
pipeline
or
something
or
just
yeah
delete
it
archives
directly
through
the
api
or
through
the
button
in
the
ui.
So
we
want
to
persist
this
in
the
separate
storage.
B
So
this
whole
new
epic
is
about
taking
this
artifacts
archive
on
the
deployment
and
copying
that,
but
we
not
there
will
be
another
epic
which
will
be
just
packing.
What
we
already
have
on
the
disk
storage
right
now
and
uploading
it
to
the
same
place,
but
it
actually
should
be
quite
simple.
We
also
discussed
that
with
camille,
basically,
just
taking
our,
I
don't
know,
30
000
something
projects
or
40
000.
I
don't
remember
the
exact
accounts
and
just
zipping
the
directory
and
uploading
it.
B
Yeah
and
the
others,
the
other
thing
which
is
happening
pages
right
now,
is
that
static
site
generator
team
wanted
to
like
they
weren't
weren't
happy
with
the
future.
Some
of
the
pages,
one
of
features
they
lacked
were
the
redirects,
so
finally,
camille
actually
also
chiming,
and
this
suggested
how
we
can
implement
this
nightly
fire
directs
quite
easily.
B
So
I
have
a
nmr
in
front
of
me
right
now
and
reviewing
that.
Actually
I
wrote
that
something
weren't
working
I
actually
figured
out
and
it
works
for
me
locally,
as
expected.
It
just
literally
behavior
is
quite
strange.
They
by
default
use
301
redirects,
which
is
like
permanently
moved,
which
kind
of
makes
it
persistent
in
your
browser
questions.
B
Not
a
lot
doesn't
allow
you
easy
testing,
but
since
we
kind
of
followed
an
se5
pattern,
I
guess
it's
okay
to
do
the
same
for
the
gitlab
pages,
but
maybe
that
was
a
mistake
on
their
part
when
they
were
implementing
it
for
the
first
time
yeah
anyway
I'll.
Try
to
finish
the
review
today
and
camille
already
approved
it,
so
it
should
be
in
a
very
good
good
shape.
Hopefully
we
can.
We
can
merge
it.
B
A
B
Basically
default
permissions
on
the
api
were
changed
and
pages
was
relied
pages,
relies
on
these
default
permissions
because
currently
default
permissions
is
api
scope,
which
is
like
you
can
do
anything
using
this
user
credentials
and
they
restricted
it
to
the
read
user,
which
is
like
smallest
portion.
You
can
do
anything.
B
You
can
just
see
that
this
user
has
this
name
so
that
broke
a
lot
of
apps
like
it
broke
jenkins
integration,
it
broke
pages
and
probably
a
lot
of
other
stuff
which
nobody
noticed
in
this
like
eight
hour
window,
while
it
was
broken,
yeah
funny
thing
is
that
this
time,
like
the
last
time,
access
control
in
pages
was
broken.
B
Somebody
noticed
that
in
like
an
hour-
and
there
was
a
lot
of-
I
don't-
know-
unhappy
people
about
this-
and
this
time
it's
like
somebody
inside
the
company
noticed
that
and
it
was
like
six
hours
already
broken
by
that
time.
So
that's
strange,
that's
I
don't
know
not
many
users
complain
this
time.
Don't
know
why.
A
Yeah,
I
don't
know
why
either
I
wonder
if
they
change
something
in
their
usage
pattern.
B
A
Okay,
awesome:
well,
that's
a
good
update!
Thank
you
so
much
for
walking
me
through
this
stuff
I'll
work
on
a
release
post
announcement
for
redirects,
given
that
you
feel
like
that,
they'll
make
it
in
13.4
and
that
way
we
can
start
promoting
that.
B
Actually,
it
will
be
behind
the
feature
clock
so.
B
Now,
actually
we
just
we
use
this
api
only
to
verify
that
user
have
access
to
specific
projects.
So
we
do
that
only
for
projects
which
enable
access,
control,
okay,
right,
interesting,
okay,
thanks
yeah.
B
No,
not
really,
I
guess
we're
working
on
it,
not
sure
like
I
felt
a
little
more
speed.
I
guess
a
couple
weeks
ago,
right
now,
when
I
have
a
lot
of
these
small
issues
in
front
of
me,
it
feels
like
there
are
too
many
of
them,
but
I
don't
know
at
the
same
time.
B
I
know
what
we
need
to
do,
which
is
great
and
ideas
highly,
also
feels
confident
in
his
part.
So
that
sounds
I
don't
know
promising.
I
actually
had
one
more
question
shall
we
like?
I
read
the
agenda
for
the
team
meeting
like
yesterdays,
and
we
have
this
like
most
important
items
on
the
top.
I
wonder
if
we
should,
I
don't
know,
make
pages
part
of
it,
because
I
don't
know
right
now.
A
Yeah,
we
can
definitely
add
the
object
storage
as
because
it
is
a
release.
P1
and
nicole
is
responsible
for
adding,
like
the
deliverable
label
for
it.
So
I
think
that
we
do
have
several
issues
that
have
deliverable
label
on
it
and
that's
typically,
how
we're
tracking
those
top
issues
and
the
agendas
if
it
has
a
release,
p1
and
a
deliverable
on
it,
because
there
are
release
p
ones
that
I'm
like
okay.
Well,
after
you
finish
your
deliverables,
this
is
your
next
crop
to
start
picking
up
and
the
next
crop.
A
So
I'll
ask
her
if
there's
work
that
we
know
is
assigned
to
like
13.5,
that
we
can
add
a
deliverable
label
to
it
and
make
sure
that
we're
indicating
that
priority
against
release
management
features.
I
think,
what's
a
little
bit
challenging
for
me,
is
when
I
talk
to
product
leadership.
A
They
are
advising
me
not
to
de-prioritize
release
management,
core
scope
for
page
scope,
but
it
feels
like
we're
doing
that.
You
know
so
and
we're
doing
that,
because
engineering
is
saying
this
is
an
important
priority,
and
so,
although,
like
I'm
getting
told
not
to
de-prioritize
efforts,
I
think
we
do
need
to
start
taking
into
account
that
object.
Storage
has
been
deemed
a
company
priority,
even
if
it's
not
by
the
product
manager,
and
that's
that's
okay.
A
I
guess
so
yeah
I'll
talk
with
nicole
about
that
piece,
and
we
will.
We
can
add
the
deliverable
and
pull
them
into
the
pull
them
into
the
agenda
for
us
to
follow
up
on.