►
From YouTube: Package Weekly Sync: 05-08-20
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
Great
welcome
to
our
weekly
package,
retro
we're
going
off
an
agenda
and
first
for
what
went
not
so
well.
Steve
is
up.
B
So
this
week,
I'm
just
getting
a
bit
stressed
about
delivering
all
the
p1
items
that
are
in
13.0
service
just
as
time
is
ticking
down,
and
I
think
it's
also
magnified
knowing
that
I'm
going
to
be
out
at
the
end
of
the
month.
So
it's
causing
some
additional
stress
and
then
this
week
I
still
am
feeling
like
I'm
not
spending
enough
time
on
the
go
proxy
community
contribution.
B
And
it's
to
the
point
where
I
think
I'm
I'm
the
one
holding
it
up
right
now,
which
isn't
good
over
to
tim.
A
So
for
me
I
spent
significantly
more
time
responding
to
customer
and
prospect
emails
and
writing
the
release
post.
So
I
didn't
get
to
spend
as
much
time
on
issue
grooming,
but
it
was
yeah.
It
was
useful.
A
I
could
read
for
gigi
composer
is
taking
a
little
longer
than
I
was
hoping
with
some
trickier
technical
things
to
sort
out,
and
I
haven't
produced
many,
mrs,
due
to
mostly
sketching
out
a
solution
and
debugging
onto
david.
C
So
this
week
my
mouth
felt
slow.
I
had
a
lot
of
ping
pongs
with
maintainers
just
to
present
and
transmit.
You
know
the
context
around
dnr,
also
the
container
expiration
policy
usage.
So
what
we
have
added
to
the
usage
ping,
I
had
the
missing
piece
to
make
it
usable
on
production,
and
so
now
we
have
to
fix
it
next
week
over
to
nico.
D
One
copy
change,
so
many
changes,
so
the
sidebar
change
ended
up
between
two
different
demar
there's
more
than
35
different
file
changes
and
just
for
a
relay
building.
E
F
All
right,
yeah.
E
F
Getting
the
blob
upload
put
handler
done,
has
it's
been
kind
of
annoying,
since
I
was,
I
was
hoping
to
save
that
until
later
after
we
had
more
experience,
writing
other
handlers,
but
it
ends
up.
Other
handlers
depend
on
it
and
it
needs
to
be
more
integrated
with
the
existing
registry.
It
needs
to
coordinate
with
file
system
rights,
and
it
will
always
have
to
coordinate
with
file
system
rights.
So
it's
tough
to
have
to
do
something
that
needs
to
be
more
refined.
G
To
joe,
there
is
still
no
consensus
about
where
the
registry
data
should
live,
but
it's
been
an
interesting
conversation
on
to
steve
with
the
2012.
B
I
opened
six,
mrs,
which
felt
very
productive,
and
hopefully
this
next
week
is
followed
with
a
closed
version.
Update
of
that
and
my
momentum
has
just
been
very
high
this
week
and
I
think
this
is
sort
of
partially
from
coming
from
a
full
week
of
only
working
half
days
with
the
postgres
training
sort
of
just
left
me
feeling,
like.
I
had
a
lot
more
time
to
do
things,
which
was
good.
A
Yeah
mine's
the
flip
side
of
what
went
not
so
well
so
talking
to
a
lot
of
customers
and
prospects.
We're
getting
a
lot
of
questions
and
interest
in
the
package
registry
and
people
are
feeling
like
excited
and
aligned
with
our
roadmap
and
strategy,
which
feels
like
some
extra
confirmation
we
had
this
week,
which
was
nice
on
to
oh
I'll,
be
gg.
I
feel
like
the
composer
work
is
80
done
with
just
some
final
bits
to
sort
out
and
on
to
david.
C
D
E
This
week
was
pretty
great.
We
were
able
to
get
the
container
registry
ui,
epic
all
created,
that
was
around
15
unique
issues,
and
each
issue
has
to
qualify
like
why
it's
valuable
to
a
user
and
also
includes
the
specific
design
taking
it
from
where
it
is
to
where
we
want
us
to
go.
So
it's
a
pretty
intense
process
and
a
lot
of
refinement
and
a
lot
of
talking
to
niko,
which
I'm
sure
was
annoying
for
him.
E
But
another
cool
thing
that
happened
is
we
had
a
ux
showcase
last
week
about
the
jobs
to
be
done
in
the
research
that
we
had
done
around
that
for
the
package
stage
and
out
of
that
I've
already
gotten
a
huge
number
of
coffee
chats
and
discussions
around
how
other
teams
could
be
doing
the
same
validation
work
that
we're
doing,
which
is
a
really
good
sign,
that
we're
doing
awesome
stuff
and
that
we
can
kind
of
spearhead
and
lead
other
areas
and
how
to
strategize,
which
felt
really
good.
G
F
All
right
so
gitlab
development
kit
uses
our
version
of
the
container
registry
now,
which
is
great.
F
So
and
then
I'm
really
happy
with
our
testing
strategy
with
postgres
is
developing
in
a
in
a
way
that
seems
very
manageable.
It
can
be
tough
to
have
tests
that
are
easy
to
write
and
use
that
also
make
use
of
an
external
service,
and
I
think
we're
doing
a
good
balance
between
really
testing
the
real
thing
and
having
a
convenient
way
to
do
that.