►
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
A
Okay,
it's
okay,
yeah!
So
this
week
for
the
package,
quad
planning
meeting,
I
was
thinking
that
we
could
review
the
current
plan
for
milestone.
Fourteen
three
and
since
I'm
going
to
be
out,
I
put
together
a
draft
of
14
4.,
I'm
sure
we'll
need
to
change
as
we'll
get
closer,
but
this
way
we
could
at
least
have
an
idea
of
what's
coming
too.
A
Okay,
you
can
see
the
milestone
plan
right,
not
the
agenda,
okay,
so
for
14.3,
I
think
for
the
hilly
and
juan
for
the
container
registry.
I
pulled
in
the
basically
the
one
of
the
testing
issues.
I
think
there's
probably
one
or
two
more
that
I
should
pull
in,
but
you
could,
let
me
know
which
one
do
you
think
we
can
would
feel
comfortable
as
a
deliverable
issue,
but
I
pulled
in
this.
The
simulate
failed
database
schema,
there's,
probably
a
couple
of
other
those
simulate
failure.
Scenarios
right.
B
A
C
There
are
a
couple
that
are
marked
for
14
3
that
are
related
to
the
importer
that
we
do
need
to
get
done,
but
they're
not
as
urgent
since
the
import's
not
happening
for
a
minute.
So
we
can
either
reschedule
those
and
prioritize
priorities.
Other
issues
are
we
can
get
those
in
since
they
are
a
little
more
complicated.
B
I
I
think
we
can
push
those
issues
forward,
because
they're
only
really
really
really
needed
for
phase
two.
We
need
to
do
them,
but
the
priority
now
is
getting
the
testing
done.
A
Haley
appreciate
that,
okay,
I'm
moving
moving
on
into
the
some
of
the
package
issues.
So
really
I'm
was
trying
to
focus
on.
You
know
we're
trying
to
focus
on
sas
reliability
and
performance.
So
I
tried
to
choose
issues
that
were
in
line
with
that,
but
also
attempted
to
move
our
roadmap
ahead
as
well,
so
you'll
see
a
heavy
focus
on
the
dependency
proxy
as
you're
reading.
Through
these
the
first
one
is
actually
related
to
our
error
budget.
A
There's
we
see
high
latency
scores
for
the
npm
endpoints
in
the
package
registry,
so
scheduling
that
investigation
as
a
p1,
I've
kind
of
brought
it
in
as
a
stretch
goal
for
the
previous
couple
of
milestones
and
it
keeps
getting
punted.
But
I
really
want
our
error
budget
to
be
zero
would
be
nice,
and
so,
if
we
can
we're
close
to
it.
So
if
we
can
that's
the
first
issue,
I
have
the
next
one.
A
D
A
D
D
Like
125
000
or
something
like
that,
but
yeah
it's
hard
to
say
at
what
point.
We
need
to
consider
that.
A
D
A
A
Okay,
perfect
I'll
open
that
issue
today,
okay,
so
the
next
one
I
thought
might
be
useful
right
now
is
for
the
dependency
proxy
user
interface.
We
don't
really
show
information,
except
for
the
configuration.
I
thought
it
would
be
helpful
to
add
a
graphql
endpoint
that
would
show
image
and
manifest
as
well
as
some
of
the
other
information
that
feels
like
it's
going
to
help
like
as
we
move
forward
too,
with
adding
other
registry
support
as
well.
A
A
The
next
one
is
actually
related
to
the
container
registry.
I
think
this
is
the
one
that's
most
at
risk
at
moment
at
the
moment,
so
the
group
container
registry
api
has
and
allows
you
to
list
all
of
the
image
repositories
and
tags
for
a
given
group
and
turns
out
there's
one
particular
customer
who
will
not
name
right
now,
but
who
are
using
it
the
most
heavily
and
it's
impacting
the
the
latency
we
reached
out
to
them.
A
A
Since
we're
talking
about
the
dependency
proxy
so
much,
we
don't
have
any
user
level
data
for
it.
We
do
and
we
do
have
a
general
sense
of
how
many
images
are
being
pulled
and
how
many
are
being
pulled
from
the
cache.
But
we
don't
have
anything.
That's
like
that.
We
could
add
towards
our
group
monthly,
active
users,
so
it'd
be
great
to
start
measuring
that
and
we
could
see
how
user
usage
growth
grows
over
time.
A
Kind
of
this
one
it
seems
like
it's
a
doesn't
belong
it's
a
little
bit
different,
but
a
few
milestones
ago
we
released
a
feature
for
preventing
or
allowing
maven
duplicates,
but
there's
a
bug.
That's
preventing
people
from
using
it
where
certain
types
of
maven
files
are
still
are
still
being
allowed
to
upload
as
duplicates
so
fixing
this
bug,
which
has
been
identified
as
a
blocker
for
a
few
customers
into
fully
adopting
the
feature.
A
Okay,
then
I
added
a
test
issue
so
that
this
milestone
actually
14
2.
Where
added
we
had
resolving
a
bug
with
the
dependency
proxy
and
single
sign-on.
So
adding
a
test
for
that.
So
we
have
a
test
where
it's
testing
on
a
saml
instance
would
be
really
helpful
to
make
sure
that
there's
no
remediate
progressions.
A
A
And
then
continuing
on
testing
package
uploads
with
different
storage
providers,
so
testing
uploads
with
tcp
storage.
We
have
this
milestone,
14.2
we
knocked
out
aws
and
minio.
A
So
moving
on
to
google
cloud
and
then
two
front-end
issues
nico's
not
here
right
now,
but
he's
out
for
a
bit
this
milestone,
so
we're
bringing
in
two
front
end
issues
one
to
display
the
available
metadata
for
pipi
and
the
other
one
for
composer.
So
right
now
we
have
metadata
for
those
package
types
but
we're
not
displaying
them
in
the
front
end.
So
just
doing
that
would
be
helpful.
A
Nice,
I
I
tried
to
get
the
stretch
goals
under
control.
I
didn't
realize
what
a
problem
I
had.
I
was
just
scheduling
like
10
stretch
issues
and
realizing
that,
maybe
that's
not
realistic.
It
just
took
me
a
couple
of
milestones
for
that
to
set
in
so
I'm
going
to
try
to
keep
the
stretch
goals
limited
to
like
two
or
three,
I
think
is
more
realistic
for
everybody.
A
The
result
of
my
of
that
was
I
had
yesterday
I
had
to
clean
out
a
very
crowded
milestone,
fourteen
four
and
five
to
balance
it
so
for
stretch
goals.
I
was
thinking
any
of
the
work
that
we
can
continue
on
the
pipelines
for
packages.
I
know
david
shared
something
in
the
issue
yesterday
in
mdc,
I'm
really
interested
in
this
generic
package.
A
I
still
have
a
db
impact
support
for
debian
in
here,
which
I
think
will
continue
into
next
milestone
potentially,
and
I
know
that
we
still
had
the
instance
level
nuget
endpoint
that
we're
working
on
and
refining
some
of
the
queries
for
so
for.
D
Dbm
I
commented
below,
but
it's
ready
for
rollout.
I
think
we're
just
trying
to
find
time
to
do
the
feature,
flag,
rollout
and
it
seems
like
this
one
might
take
a
little
longer
than.
A
A
Any
questions
or
comments
move
on
to
14
4,
just
a
quick
overview,
if
not.
A
Okay,
so
14
4,
I
tried
to
just
keep
it
minimal
just
get
to
get
so
we
have
an
idea
of
what's
coming
because
usually
things
is
pretty
dynamic
from
month
to
month,
but
I
did
bring
forward
to
confidential
security
issues.
We
have.
These
are
like
p3s
that
we
need
to
work
on
and
then
the
dependency
proxy
workhorse
migration
implementation
plan.
So
the
create
source
code
team
is
working
on
the
rail,
the
workhorse
portion
in
14
3,
so
we'll
have
to
work
on
the
the
rails
portion
and
14
4..
A
We
have
a
dependency
proxy
bug
where
they
fail
to
pull
from
dr
hub
on
ec2
instances,
finishing
up
the
package,
ui
change
or
to
use
graphql
instead
of
view
and
then
extracting
npm
metadata
and
then
two
improvements,
the
container
registry
user
interface
and
then
have
some
stretch
goals
there.
I'm
sure
we'll
need
to
add
the
container
registry
testing
on
staging
or
migrating
to
prod.
At
that
point,
depending
on
where
we're
at
the
schedule,
but
I
think
we
could
add
those
as
we
get
a
little
closer.
D
D
That's
just
kind
of
speculation
at
this
point,
but
that
was
worth
mentioning
and
then
for
the
dependency
proxy
workhorse
plan.
I
did
want
to
mention
like
as
soon
as
the
other
team
has
kind
of
decided,
which
path
they're
going
to
take
on
how
it's
going
to
be
implemented
in
workhorse.
We
can
do
this
at
the
same
time.
We
don't
have
to
wait
for
them
to
be
finished
at
all.
We
just
have
to
know
which
direction
they're
going
to
take.
A
D
A
And
the
investigation
will
help
to
identify
a
solution.
How
we'll
do
it?
True?
Okay,
I
think
I'm
doing.
I
haven't
seen
too
much
action
from
the
workhorse
portion
of
the
work
yet
but
yeah.
If
we're
midway
through
the
milestone
and
they're
done,
I
think
we
could
swap
something
from
14
3
pretty
easily.
A
Cool
I'll,
stop,
sharing
any
anything
else
to
add
or
sophia,
and
you
were
quiet
today,
usually
have
some
changes
for
me.
E
A
All
right,
well,
I'm
excited
for
for
the
next
couple
of
milestones.
I'm
writing
the
release
post
now
for
14.2,
and
we
definitely
have
a
bunch
of
cool
features
coming
out.
So
it's
very
exciting
yeah
I'll
stop
the
recording
and
the
meeting.
If,
if
there's
nothing
else
say
thank
you
bye.
Everyone
I'll
talk
to
you
soon,
bye.