►
From YouTube: GitLab 15.2 Kickoff - Package:Package
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-
this
is
katie,
I'm
the
product
designer
for
the
package
stage
and
I'm
joined
by
tim
who's,
the
product
manager
for
the
package
stage,
and
today
we're
going
to
talk
to
you
about
everything
that
we're
up
to
in
milestone
15.2.
So,
first
up,
I
wanted
to
highlight
a
user
experience
improvement
in
the
container
registry.
A
Currently
we
show
this
very
long,
full
path
that
shows
the
full
path
to
the
image
and
when
you're,
looking
in
the
group
view,
especially
there's
a
lot
of
the
same
information
repeated
and
we
heard
from
customers
that
it's
a
little
bit
hard
to
parse.
So
the
first
improvement
that
we're
going
to
be
making
is
to
kind
of
truncate
the
repeated
information
with
the
option
to
expand
it
by
clicking
on
this
ellipsis
and
showing
the
full
path.
A
So,
hopefully
that
makes
it
a
little
bit
easier
to
kind
of
find
the
image
that
you're.
Looking
for
in
a
similar
vein,
we
are
also
going
to
stop
appending
the
root
image
on
the
ui.
So
at
the
moment,
when
you're
looking
at
the
container
registry,
you
might
see
this
root
image
when
you're
building
a
image
from
your
project
and
the
problem
with
this
is
that
the
filtering
does
not,
if
you
type
in
root
image,
it
doesn't
actually
return
anything
back.
A
So,
in
the
similar
vein,
as
the
last
issue,
just
to
kind
of
simplify
things
and
make
the
ui
a
little
bit
easier
to
parse,
we
are
no
longer
going
to
be
showing
root
image
on
the
ui.
A
Next
up,
I
just
want
to
talk
a
little
bit
about
some
problem:
validation,
research
that
we're
going
to
be
undertaking,
so
we're
going
to
be
looking
at
the
package
detail
page.
So
when
you're
in
the
package
registry
and
you're,
looking
at
a
specific
package,
we're
considering
making
some
improvements
and
we'd
really
like
to
understand
when
people
are
viewing
the
package
detail,
what
are
they
doing?
Are
they
troubleshooting?
What
workflows
are
they
following?
What
information
is
the
most
important?
A
Is
there
any
features
or
information
that
is
missing
and
then,
in
terms
of
additional
metadata
at
the
moment
for
some
package
formats,
we
show
some
additional
metadata
and
we
want
to
understand.
You
know
what's
helpful
about
that.
What's
missing,
is
there
anything
else
that
we
should
be
showing
so
we'll
be
looking
to
speak
to
some
customers?
Users
of
the
package
registry
in
15.2
and
another
piece
of
research
that
we
are
going
to
look
into
this
milestone
is
to
promote
the
single
project
workflow.
A
So
we
hear
from
some
customers
that
it
could
be
a
little
bit
confusing.
Like
do
you
put
your
registries
in
a
bunch
of
separate
projects,
but
then
how
do
people
access
them
and
we
have
in
our
documentation
proposal
or
suggestion
to
have
a
single
project
where
you
might
keep
your
package
registry
or
your
container
registry?
A
So
this
is
some
problem
validation
to
understand
a
little
bit
more
about.
You
know
how
this
workflow
might
work
for
customers
and
how
can
we
best
kind
of
optimize
it
and
promote
it?.
B
B
And
didn't
know
it
existed,
so
I
think,
having
a
way
to
make
this
easier
to
discover
will
be
great.
I
would
just
like
to
highlight
a
couple
of
issues.
The
first
one
is
in
in
15
2.
We
plan
on
releasing
the
mvc
of
package
cleanup
policies.
B
So
the
mvc
of
the
clean
up
policy
will
allow
you
to
set
a
maximum
number
of
duplicate
package
files
to
keep
and
the
rest
will
be
deleted,
so
very
excited
for
this
to
help
you
manage
your
storage
and
also
just
make
the
user
interface
easier
to
to
use
the
next
one
is
a
change
in
permissions
for
the
job
token,
which
is
used
from
the
gitlab
pipelines
right
now,
you,
the
job
token,
does
not
have
permission
to
access
internal
packages,
so
this
is
for
self-managed
instances
where
a
project
can
be
internal
where
it's
available
for
everyone
on
that
instance,
but
they
can't
use
the
job
token.
B
So
this
small
change
should
help
you
to
be
more
efficient
and
and
and
secure
in
how
you're
giving
up
managing
authentication
for
self-managed
customers
and
finally,
another
change.
I'm
particularly
excited
about
is
right
now,
the
your
basically.
The
package
registry
follows
the
same
level
of
visibility
as
the
code
repository,
which
means
that
it
was
impossible
for
you
to
be
able
to
set
your
package
registry
to
public
and
your
repository
to
private.
B
A
B
Exciting
issues
on
15-2
and
yeah:
let
us,
if
you
have
any
questions,
let
us
know
in
the
issue
and
we
look
forward
to
another
awesome
milestone
thanks.
Everyone.