►
From YouTube: 2022-07-05 Package: Weekly Team Meeting
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
Hi,
everyone
welcome
today
is
july
5th,
and
we
are
on
our
package
sync
meeting
and
we
have
some
topics
here,
mostly
discussion
around
our
q3
goals,
so
reminder
for
everyone
that
tim
is
going
to
be
out
and
parentally,
which
means
we
want
to
make
sure
that
we
complete
our
work
to
plan
the
archetriggers
and
our
milestone
plans.
So
we
can
cover
for
him
and
while
I
was
reviewing,
I
saw
some
topics
that
I
still
need
some
refinement
or
some
input
from
the
team.
A
A
Can
we
really
do
this
in
three
months
with
all
the
other
things
that
we
have
in
there?
Are
there
any
dependencies
between
the
different
epics
that
we
have
in
there
in
the
issues
or
with
other
teams?
So
pretty
much
just
taking
a
look
on
it?
One
is
the
improvements
for
the
package
registry
ui
and
the
other
is
all
the
improvements
for
sorting
searching
and
this
collaborative
for
the
computer
register
ui,
which,
by
the
way,
I'm
very
excited
that
we
are
now
working
on
nice.
Things
for
the
continued
registry.
B
You
could
see
the
work
for
the
I
think
for
the
package
registry.
I
don't
expect
there
to
be
as
much
back-end
work
but
for
the
contain
registry.
If
we
want
to
do
improved,
sorting
or
sorting
by
like
most
relevant
date,
we
might
need
to
do
some
back
end
work
as
well.
So
I
think
I
would.
I
would
recommend,
looking
closer
at
there
and
there's
issues
listed
in
one
of
the
comments
for
what
we
would
want
to
get
done.
There.
B
Sorry
go
ahead.
One
thing
missing
from
I'm
just
looking
and
one
thing
missing
from
that
top
table
that
we
wanted
to
try
to
fit
in,
for
the
container
registry
was
the
auto
deployments,
and
so
it
seems
like
a
big
project
but
having
maybe
just
thinking
of
what
is
reasonable
for
the
next
quarter.
What
we
could
do
for
the
auto
deployments
for
the
container
registry,
if
anything,
and
that
would
help
us
to
sort
of
define
an
iteration
that
we
can
achieve.
A
Yeah,
the
first
part
is:
we
need
to
coordinate
with
other
teams
with
distribution,
to
have
the
database
automated
and
with
the
scalability
to
have
the
redis
instance
that
is
going
to
block
more
on
the
auto
deployments,
but
we
can
also
review
the
epic
to
see
what
else
is
going
to
be
there.
Sofia
needs
to
continue
working
on
some
stuff.
She
just
got
a
bonus
about
that
and
yeah.
We
can
review
a
little
bit
of
the
work
that
we
need
to
do
on
our
side,
okay,
good
and
on
our
next
topic.
A
Part
of
our
next
prioritization
framework
is
the
last
update.
We
are
not
going
to
force
teams
to
adjust
to
the
percentage
that
we
were
proposing,
but
it
is
still
important
for
us
to
keep
some
hygiene
on
our
issues
and
keep
an
eye
on
the
percentage
that
we're
using
for
maintenance,
the
presentation
that
we're
using
for
for
features
and
for
books.
A
One
of
the
important
thing
here
is
that
we
are
seeing
a
high
level
of
undefined
work,
which
means
issues
that
don't
have
maintenance,
feature
or
bug.
The
problem
in
here
is
these:
dashboards
are
not
considering
the
meta
label,
which
probably
we
need
to
move
those
issues
to
a
project
that
is,
for
example,
the
package
project,
but
also
the
other
thing
is
we
have
some
issues.
For
example,
the
bumping
version
for
the
container
registry.
Don't
have
any
quarter
label.
C
Yeah
actually
to
follow
that
up
when
we
have
issues
like
like,
for
example,
like
the
milestone
planning
issue,
that's
assigned
to
the
milestone,
what
type
of
label
should
those
like
non-like
mr-related
issues
get,
because
I
think
I
started
looking
through
the
list,
and
it's
like
you
know,
there's
a
lot
that
it's
kind
of
it's
just
a
discussion
issue
or
something
that
doesn't
necessarily
have
work
attached
to
it.
At
this
point.
A
In
the
past,
for
those
ones,
we
were
using
the
meta
label,
but
the
dashboard
that
the
expertisation
board
group
is
using
is
not
considered
in
that
label.
So
I'm
in
conversations
right
now
to
see
if
they
are
going
to
include
that
label
on
the
on
those
dashboards
and
the
other
solution
that
other
teams
have
is
they
have
another
project
that
is
not
in
those
ones?
C
A
Yeah,
like
our
users,
can
still
find
the
issues
because
we
use
the
labels
right
and
if,
if
we
have
the
epic
stills
gitlab.com,
the
issues
are
going
to
still
be
there.
But
definitely
discoverability
is
not
that
easy.
B
B
So
let
me
milestones,
keep
keep
turning,
so
I
have
the
plan
for
15
3
here,
and
I
would
highlight
that
we
have
one
security
issue
planned.
This
is
the
last
of
the
three
that
came
up
last
month,
so
hopefully
we'll
be
able
to
address
that
on
the
container
registry
side,
continuing
the
focus
on
the
migration,
so
the
migrating
finishing
the
premium
and
ultimate
non-vip
migration
and
then
doing
the
vip
migration
in
15
3
and
we've
been
coordinating
with
the
account
management
team.
B
On
that
we
started
hearing
back
about
customer
messaging
and
timing
and
things
the
other
one
here
is.
This
is
using
the
creation
timestamp.
So
this
is
a
huge
performance
improvement
for
the
container
registry
cleanup
policies.
B
This
will
be
something
on
on
the
rail
side,
the
continuing
our
investigation
into
how
to
supply
a
gm
email
for
the
container
registry
or
user
level
data.
So
this
will
be
very
important
for
actually
getting
credit
for
how
big
the
package
stage
is
and
then
some
usability
changes.
So
we
have
a
couple
of
things
like
improving
the
settings,
which
is
important
for
some
of
the
work
we
have
planned
for
the
rest
of
the
year.
That
will
expand
the
settings.
B
Another
improvement
to
the
cleanup
policies
and
another
improvement
to
the
container
registry
ui.
So
some
subtle
improve
usability
improvements
that
will
make
a
big
difference.
B
Then
I
tried
to
pull
in
there's
been
some
dependency
proxy,
bugs
that
have
been
blockers
for
people.
One
is
preventing
anyone
from
using
as
azure
object,
storage,
so
resolving
that
will
unblock
a
whole
audience
from
from
using
the
dependency
proxy
and
then
we've
been
pretty
consistently
seeing
this
bug
where
the
feature
is
not
working
with
project
access
tokens-
and
this
is
particularly
blocking
some
of
our
dog
fooding
usage
of
the
feature
as
well,
so
be
nice
to
unblock
that
and
go
back
to
dog
fooding
and
then,
as
a
follow-up
to
that
issue.
B
I
just
mentioned
adding
some
tests
to
the
our
feature
test
that
will
test
with
different
authentication
mechanisms
and
on
the
package
registry.
There
is
some
authentication
improvements,
so
making
sure
that
you
can
use
the
list
api
with
the
or
the
that
you
can
view
the
list.
Sorry,
so
you
could
view
packages
using
the
job
token
and
continuing
the
work
on
the
settings
layout
that
katie
and
rahul
have
been
working
on,
and
then
I
have
a
couple
of
stretch,
goals
here
more
on
the
settings
and
then
there's
an
npm
bug.
B
That's
been
hitting
a
few
of
our
customers.
Recently,
we've
been
trying
to
prioritize
this,
but
I
did
try
and
keep
it.
It
is
a
little
bit
lighter
on
the
rail
side.
We
do
have
some
time
off
for
steve
and
david
during
the
milestone,
so
I
wanted
to
make
sure
that
we
planned
something
that
we
really
only
chose
the
most
important
thing.
So
for
me,
from
the
rail
side,
really
the
performance
improvement
for
the
cleanup
policies
and
the
dependency
proxy
bugs
are
the
most
important
things.
B
A
A
Good,
do
we
have
any
other
open
top
for
today.