►
From YouTube: 2022-04-12 Package Quad Weekly Planning
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
Yeah
thanks,
so
there
are
two
issues.
One
of
them
is
the
pipelines
field
in
graphql
in
the
package-related
graphql
types.
C
That
makes
sense
to
me:
I
I
I'll
move
the
pipelines,
the
remaining
issue
to
15-0
and
or
at
least
add
it
to
the
planning
issue
and
then
still
better
than
doing
the
removal
and
deprecation.
I
think,
because
if
we
did
it,
then
we
would
have
several
a
couple
milestones
of
work
from
other
teams
to
accommodate.
That
so
seems
like
a
nice
overall
change,
even
though
it's
taken
a
bit
longer,
yeah.
B
B
C
And
it's
really
about
how
long
of
a
delay
is
there
or
how
much
of
a
delay?
Are
we,
okay
with
when
reporting
the
store,
usage,
yeah,
more
or
less,
and
is
that
on
just
the
registry
page
or
is
that
will
that
also
affect
the
the
main
usage
quotas
page
like
the
admin
dashboard.
B
It
will
be
the
same
field
if
we
go
for
a
single
field
in
the
statistics
structure,
I'm
assuming
that
it
will
be
the
same
field.
So
in
both
ways
they
will
be
delayed.
Okay,.
C
C
Okay,
that
is
a
I
would
not
want
it
to
slip,
if
not,
if
possible-
and
maybe
it's
okay-
to
have
the
delay
for
now
and
then
we
could
come
back
and
revisit
it
later
to
remove
the
delay.
This
way,
we
could
just
make
sure
that
we
unblock
the
utilization
team.
B
Yeah
to
me,
the
we
should
go
for
having
a
single
field
in
the
api
that
reports
the
the
size
use
that
even
if
we
can
have
a
delay
in
its
accuracy
and
if
we
need
a
more
precise
field,
we
can
always
add
another
field
for
that
in
a
later
or
future.
Iteration.
C
D
D
C
C
C
E
Yeah
we
have
there's
one
non-deliverable
item.
That's
currently
scheduled
for
1410,
it's
being
worked
on
a
community
contributor.
It's
just.
It
involves
logging
for
the
container
registry
client.
E
They
are
still
working
on
it.
I
think
they're
out
for
a
few
weeks,
but
at
the
current
rate
I
don't
think
it'll
make
1410.
So
I
wanted
to
raise
that
just
in
case.
That
is
a
concern
at
all.
A
The
rule
for
contributions
is
the
mrs,
are
the
ones
that
we
don't
add
milestone
now,
because
it's
part
of
the
bot
on
how
they
are
applying,
but
for
the
issues
we
can
do
it
whenever
we
want
to
change
the
issues
and
the
issues
is
just
for
us
to
track
what
we
are
working
as
a
team
so
yeah,
let's
just
change
it
to
15
and
it's
okay
cool.
A
If
I
see
the
board,
then
do
we
have
something
else
pending
from
the
milestone.
I
think
those
are
the
only
ones
that
we
have.
F
A
So
on
the
plan
for
15
00
to
align
on
what
we
want
to
do
and
team,
please
correct
me
if
I'm
saying
something
wrong,
we
want
to
do
the
container
register
aloud
and
we
want
to
do
a
storage
visibility
and
management
just
to
clarify
in
here
to
everyone.
We
don't
want
to
unblock
utilization,
so
the
work
that
we
need
to
do
is
important
for
utilization
to
do
the
the
display
of
usage
on
the
admin.
A
So
that's
the
reason
that
is
our
second
priority
and
those
include
also
some
issues
that
we
have
jose
working
on.
A
B
Yeah,
I
think
we
can
close
this
change.
I
was
just
waiting
for
its
deployment
and
verification,
but
it
seems
that
joa
went
a
step
further
great.
A
D
I
think
that
the
exposed
duplicated
size
through
the
api
won't
slip
right
david.
It
won't
slip
because
we
decided
to
follow
the
alternative
implementation.
Yeah.
B
Yeah
but
but
for
that
you
need
the
there
is
an
issue
worked
on,
which
is
update
the
project
level
statistics
which
will
add
this
new
metric
for
the
container
registry
to
the
project
statistics.
And
then
we
can
expose
these
new
values
through
apis.
F
A
A
My
next
question
is
from
the
issues
that
you
have
listed
on.
The
epic
is
there
something
else
that
we
need
to
do
for
supporting
notification
for
the
namespace
and
group.
D
A
And
last
we
have
easter
holidays,
so
people
is
going
to
be
out
and
I'm
very
happy
that
people
are
going
to
be
out
taking
breaks.
If
we
see
the
board
by
the.
A
A
A
C
Okay,
yeah
I'll
catch
up
on
that
today,
good
well,
I'm
just
looking.
I
see
migrate,
get
lab.org
images
with
less
than
100
tags
and
migrate,
free
tier
images
with
less
than
100
tags.
That
is
very
exciting
to
see
that
knowing
it's
in
production,
it's
very
cool.
A
I
I
want
to
really
really
say:
congratulations.
Last
week
finishing
the
testing
is,
is
really
really
amazing,
so
nigel
definitely
protesting
and
planned
future
work.
Are
we
still
on
track
to
plan
fifteen
one
or
fifteen
two
for
some.
C
I
think
we
said
15
2
or
15
3.,
but
I,
if
I
could
make
yeah
I'm
I'm
on
board
with
having
a
milestone
in
the
next
one
or
two
months.
That's
focused
on
that.
So
if
you
want
to
start
sending
me
issues
that
you
have
in
mind
for
that,
I
can
make
sure
that
we
start
to
add
them
to
a
specific
milestone.
A
It
katie
added
that
we're
going
to
have
a
release
survey
for
customers
to
understand
how
they
would
like
container
registry
data
presented.
C
Yeah
and
that's
really
about
sort
order
and
the
whether
or
not
we
show
the
full
path
or
not
so
try
to
get
some
statistical,
relevant
data
on
what's
useful
and
what's
not.
C
And
yeah
this
week
I
mentioned
well,
I
mentioned
that
informally,
but
we're
interviewing
five
or
s
five
to
seven
people.
I
was
just
looking
at
my
calendar
about
integrating
the
container
scanning
feature
with
the
container
registry
ui
so
for
the
mdc.
They'll
focus
on
scanning
the
gitlab
container
registry
for
the
latest
tag,
and
so
that
would
make
its
way
into
the
user
interface.
So
we're
doing
some
solution.
C
Validation
for
that
today,
or
this
week
and
yeah
nick
sent
me
a
note
that
said
he's
leaving
git
lab
in
his
last
day
will
be
on
april
19th,
so
yeah
we
just
recommend
reaching
out
and
saying
see
you
later
and
connecting,
and
we
have
an
issue
to
transition
to
a
person
I
haven't
met
yet,
but
their
name
is
clayton.
So
if
you
have
any
reviews
coming
up,
I
think
you
could
start
to
to
cc
clayton
on
any
documentation
updates.
A
E
I
was
curious,
I
was
thinking
about
with
all
the
phase
two
stuff
we've
worked
through.
I
know
we've
talked
about
like
I
think
we're
gonna
eventually
have
a
retro
for
like
the
whole
thing,
but
would
it
be
helpful
to
have
like
a
retro
like
now
that
we
just
finished,
like
all
the
testing,
to
kind
of
while
it's
still
fresh
in
our
mind,
look
back
on
how
testing
went
or
how
testing
and
development
went
and
then
once
we
do
the
roll
out?
We
can
look
back
on
on
that
as
well.
C
D
D
A
No,
I
do
think
we
should
celebrate
when
we
finish
the
migration
from
free
theory.
We
should
celebrate
that's
one
thing
as
a
team,
but
I
also
would
like
to
make
sure
that
everybody
save
your
time
like
it's
a
good
opportunity
to
disconnect
at
some
point
like
recharge,
take
time
with
your
family
and
then
come
back
for
the
next.
A
C
Okay,
I
just
want
to
make
sure
we're
gonna
have
a
nice
celebration
after
so,
and
also
the
recharge
is
important
too.
I
agree
I
think,
and
resetting
expectations
for
a
future
milestone.
It
can't
be
possible
for
to
work
at
the
pace
that
we've
been
working
at
so
forever.