►
From YouTube: Package: Quad Planning: Jan. 18th, 2022
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
to
the
weekly
quad
planning.
We
have
a
crowded
agenda,
so
we
can
just
jump
right
in
on
the
first
well,
first,
an
order,
an
announcement
in
order
of
business
that
content
from
2021
was
moved
to
a
separate
document.
So,
if
you're
ever
looking
back
and
saying
what
did
we
discuss,
you
can
just
click
on
that
2121
agenda
and
moving
on
to
checking
out
commitments
from
the
current
milestone.
A
B
A
Okay,
great
and
the
the
second
on
the
list,
there's
a
confidential
container
registry
issue
and
jaime.
If
you
are
seeing
this,
could
you
let
us
know
if
that
issue
also
needs
to
to
move
back.
A
Okay-
and
I
wanted
to
also
ask
if
there
are
any
questions
about
the
14.8
milestone
plan,
is
there
any
open
questions.
B
I
haven't
pointed
in
the
issue,
but
basically
from
what
I
see
in
the
content
of
the
milestone,
I
I
did
add
some
quality
elements
there,
but
they
were
not.
B
They
were
not
addressing
directly
the
issues
of
work
because
I
just
really
didn't
realize
how?
How
could
we?
How
could
we
work
together
in
the
milestone
with
quality,
perhaps
because
the
focus
wasn't
really
exactly?
But
today
today
we
had
an
incident
where
I
was
working
with
david
and
david
actually
made
a
really
good
suggestion,
so
I'll,
probably
reprioritize
the
milestone
and
include
that
issue,
and
that
suggestion
in
in
the
14
in
13.8.
C
The
mrs
for
the
cleanup
have
been
merged
today,
so
we
should
be
good
to
go
and
yeah
the
basically
for
both
well,
one
of
them
is
already
merged
for
the
security
fix.
The
bulk
of
the
work
is
already
done,
so
we
should
have
a
small
or
no
impact
on
the
current
capacity.
A
C
No,
for
now
it's
not
currently
included
because
the
rc
commit
has
been
created
yesterday,
my
time
and
this
has
been
merged
today,
my
time,
okay,
it's
this
situation
where
yeah
it's
this
situation,
where
perhaps
if
they
continue
to
include
more
commits
from
master
until
tomorrow,
we
might
get
included,
but
for
now
it's
not.
A
Okay,
I
have
added
a
bunch
of
strategy
updates,
some
so
yeah.
I
just
could
start
to
work
through
those
there's,
no
other
questions,
so
we're
launching
the
new
container.
Well
we're
in
the
process
of
launching
the
new
container
registry
and
during
the
kickoff
video
I
unknowingly
called
it.
The
next
generation
of
the
gitlab
container
registry-
and
I
just
wanted
to
get
your
opinion
as
developers.
Does,
that
make
your
ears
hurt?
A
Okay,
thanks:
okay,
just
checking
so
I've
been
mentioning
in
the
planning
issues
and
to
anybody
that
would
listen
that
our
focus
for
the
next
quarter
is
really
on
the
prod.
The
registry,
migration,
storage,
visibility,
storage
management
and
then
we'll
also
have
a
series
of
breaking
changes
for
15-0.
That
will
need
to
be
addressed
for
that
milestone.
A
But
I
wanted
to
call
out
that
katie-
and
I
are
also
in
an
effort
to
get
ahead-
are
doing
some
user
research
thinking
about
well.
What
are
we
going
to
work
on
in
in
the
latter
half
of
the
year,
so
we
for
on
that
front,
katie's
been
working
on
dependency,
proxy
ui
research,
which
she's
wrapping
up
and
synthesizing.
Now
we're
also
interested
in
the
settings
configurations
for
the
stage
so
how
our
settings
trickle
down
from
group
to
subgroup
to
project
and
where
do
they
live
on
the
page?
That's
something
that
we've
been.
A
So
the
risk
of
that
focus
is
that
there
are
bugs
that
will
that
we
just
will
not
be
able
to
address
in
a
timely
manner
and
particularly
worried
about
npm
and
maven,
since
those
are
the
most
used
formats.
But
I
just
I
will
we
have
to
stay
strong,
because
these
projects
need
to
get
done
on
time.
So
I'm
just
trying
to
set
clear
expectations
in
the
issues
that
we
will.
We
will
not
be
able
to
get
to
those
and
that
our
focus
is
on
the
aforementioned
projects.
A
And
finally,
well
next
I
presented
at
the
cab,
which
is
the
customer
david.
Were
you
going
to
ask
something?
Sorry,
okay,
I
presented
at
the
cab
last
week,
which
is
the
get
lab
customer
advisory
board.
It's
a
collection
of,
I
think,
probably
around
30,
of
our
sort
of
vip
customers
that
get
together
and
the
idea
is
more
for
them
to
talk
through
how
they're
solving
challenges
and
what
their
use
cases
are
versus
us
presenting.
A
So
I
had
a
presentation
that
was
basically
how
can
you
get
more
value
out
of
get
lab
package
and
we
had
five
different
customers
attend
and
it
was
really
interesting.
All
five
of
the
customers
were
mentioned
that
they're
currently
on
artifactory,
but
that
they
are
planning
on
and
are
interested
in
migrating
off
of
artifactory
and
moving
to
gitlab.
A
They
all
talked
about
their
motivations
and
they
all
matched
each
other
so
that
the
first
was
cost
licensing
costs
and
they
also
mentioned
just
reduced
maintenance
and
overhead
for
admin,
and
this
was
a
new
one
that
I
haven't
heard
as
much
but
developer
experience,
so
that
was
kind
of
cool
to
hear
people
that
are
using
gitlab
and
saying
that,
oh,
it's
a
much
better
user
experience.
Gitlab
is
than
artifactory,
so
they
want
to
make
it
their
developers
lives
easier,
and
they
all
mentioned
that
they
have
sort
of
executive
buy-in
and
backing
for
this.
A
Although
they
did
have
concerns
about
the
migration
right,
we
kind
of
talked
about
what
their
concerns
were
there
and
what
each
customer
brought
up
is
that
it
will
just
take
time.
People
brought
up
their
jenkins
and
github
migrations,
saying
that
you
know
it's
been
two
years
on:
git
lab
and
they're
still
only
70
of
the
way
through
those
migrations.
So
they
expect
things
to
take
time
because
it
take,
they
have
thousands
of
developers
and
it's
kind
of
hard
to
get
everyone
moving
in
one
direction,
but
that
it
does
help
to
have
executive
buy.
A
A
The
distinction
that
I
would
make
is
for
some
that
meant
virtual
registries
like
for
the
bigger
customers.
They
were
saying.
Well,
we
pull
from
you
know
they
always
it
kind
of
always
goes
the
same
way
like
we
pull
from
10
different
sources.
Well,
actually
it
might
be
more
like
30,
actually
it
might
be
more
like
40.
A
A
We
have
a
plan
for
that
for
npm
and
bayview.
We
have
issues
all
open
and
everything
and
then
some
missing
formats
that
were
identified,
which
is
great
because
it
also
matches
our
roadmap,
rpm,
debian
and
ruby
gems
came
up
for
everybody.
Puppet
came
up
for
one
customer,
although
they
seem
slightly
ashamed
about
it
as
well.
A
Just
because
it's
an
older
format-
and
I
think
puppet
actually
would
go
more
through
the
configure
group
and
the
infrastructure
as
code,
so
I
think
they
they
would
work
work
on
that
more
than
us,
but
see
it
felt
nice
to
kind
of
have
that
roadmap,
validation.
And
finally,
there
was
a
lot
of
interest
in
security
and
compliance
features.
So
a
lot
of
people
asking
about
the
dependency
firewall
and
how
they
can
control
which
dependencies
are
downloaded.
A
They
want
visibility
into
how
packages
are
being
used
by
projects
and
by
people,
and
they
want
to
be
yeah.
They
just
want
more
control
over
what
gets
downloaded
into
their
ecosystem.
I
think
log4j
is
on
everyone's
mind
and
as
part
of
that,
it
was
also
brought
up
about
dependency.
Signing
was
the
other
another
thing
that
came
up
so
that's
also
motivating
my
research
desires.
A
Any
questions
on
that.
A
Cool
yeah
it
was,
it
was
a
fun
experience
and
hearing
customers
talk
through
their
own
use.
Cases
was
really
interesting.
I
could
see
if
people
are
interested
the
next
cab,
it's
they're
kind
of
fun
to
attend,
because
you
get
to
hear
like
we
heard
a
major
customer,
say
customer
name
a
major
customer
talking
through
why
they
purchased
gitlab
and
how
they're,
using
it
and
and
how
they're
not
using
it
yet.
So
it
was
quite
quite
interesting.
A
A
And
finally,
okrs
for
q1
will
be
finalized.
This
week
we
had
an
op
section
review.
Last
week
we
added
the
a
draft
of
the
okrs.
I
think
they
still
need
to
be
refined
and
okr
affired
like
the
right
language
and
then
also
there's
some
that
I
think
should
be
cut
just
based
on
capacity,
but
so
I'll
ping,
you
all
in
the
issue.
Once
I
have
a
second
draft
complete,
which
I
expect
to
be
today
or
tomorrow.