►
From YouTube: Weekly Package Meeting 08-19-2019
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).
B
Just
for
everyone's
attention:
okay,
how's,
that
we're
trying
to
hit
right
now.
The
main
focus
for
us
is
Emma's
per
engineer
per
month.
I'll
share
a
quality
dashboard
link
in
the
document
so
that
we
can
all
get
to
it,
be
go
check
that
quality
dashboard.
If
you
can't
see
it,
let
me
know
the
orange
should
be
able
to
see
that,
so
it's
really
meant
to
just
be
an
average.
B
We've
all
talked
about
doing
smaller,
not
faster,
so
you
know
we
keep
talking
about
it,
and
you
know
our
process
that
we're
coming
up
with
is
the
next
well.
The
third
one
I'll
move
into
here
is:
it's
gonna
is
supposed
to
help
contribute
to
that.
So
overall,
I
just
wanted
people
to
be
sort
of
thinking
about
that
as
something
we
care
about,
we'll
have
a
look
at
the
quality
dashboard
and
we
can
follow
up
with
that,
and
the
other
thing
I
wanted
to
address.
B
The
third
thing,
at
least,
is
the
regular
virtual
coffee
chats
with
other
team
members.
It's
something
that
I've
mentioned
a
few
times
with
Pete
I.
Think
it's
important,
particularly
in
GG's
case
who's,
likely
watching
this.
After
the
fact
I
gave
you
two,
you
know
just
for
stay
in
touch.
It
didn't
have
to
be
every
week,
maybe
every
other
week,
some
cadence
that
actually
works,
but
like
try
to
actually
set
those
up
regularly.
I
know
Tim
I,
think
you
have
them
already
in
with
Gigi,
so
I'm
Nick
I'd
like
to
actually
set
when
I.
B
B
Sarah
has
a
NPM
dependencies
tag
in
dependency,
support
and
she's
been
working
on
this
Emma
for
a
while
we're
starting
to
get
a
little
bit
of
pressure
from
customers.
So
I
made
a
comment
on
the
Emma
a
little
while
ago
about
you
know
we
can't
you
know,
because
Sarah
has
a
normal
life
job
like
where
she
actually
gets
paid
from
it.
We
can't
expect
her
to
like
be
committed
to
delivering
us,
but
she's
super
close,
so
I
don't
know
if
you
have
Steve
Steve.
You
have
two
minutes.
B
C
B
A
I
think
we
could
punt
this
until
the
next
meeting
when
he
is
here
but
yeah.
Basically,
Ian
wanted
to
give
a
five
or
ten
minute
overview
of
the
findings
from
the
user
research
that
we've
been
doing
for
the
container
industry
and
what
we're
going
to
do
moving
forward.
I
won't
I'll,
save
it
for
him.
So
maybe
next
week
week
we
could
go
over
it.
A
And
then
the
next
item
is
mine,
so
yeah,
one
of
the
things
that
came
up
during
the
coffee
chat
with
Gigi
was
I
thought
we
were
going
to
switch
these
meetings
like
every
second
week
or
something
we
were
gonna
push
them
to
theirs
again.
Every
second
week
we're
gonna
push
into
the
time
that
could
work
for
Australia
yeah.
B
B
A
B
D
C
Yeah
mine
is
more
of
just
a
question
of
kind
of
like
something
I've
noticed
this.
You
know
just
like
how
should
we
prioritize
when
we've
got,
you
know
work
in
the
current
milestone
versus
there's
many
other
pieces.
You
know
in
other
milestones,
future
or
even
past
so
and
sometimes
that
can
be
blocking
work
from
four
people
on
the
team.
So
how
should
it
be
prioritizing
someone
you've
got.
You
know
something.
That's
blocking
someone
versus
something,
that's
on
the
current
milestone.
C
Assuming
that
you
know,
if
you
were
to
help
out
with
unblocking
or
with
you
know,
helping
get
something
done,
but
it's
not
in
the
current
milestone
and
it's
gonna
like
take
a
while.
How
should
that
be
prioritized
with
like
current
work
and
I
just
asked
it
because
it's
you
know,
I,
don't
like
saying
no,
when
people
ask
for
help.
B
Okay,
I'm
gonna
start
off
by
saying,
saying
now
is
an
excellent
skill
to
have
it's
something
you
should
certainly
get
get
good
at,
because
there's
there's
certainly
more
things
that
we
could
possibly
do.
Then
we
have
people
and/or
time,
so
you
have
to
learn
to
figure
out
what
your
top
priorities
are.
B
I
mean
as
far
as
helping
build
one
unblocking,
I'm,
not
sure
it's
I
mean
we
can
talk,
talking,
generalities,
I
suppose,
but
I
think
it's
easy
to
talk
about
these
things
in
with
specifics
of
what
scenario
so,
whether
that's
helping
Sarah
with
air
em
are
helping
get
some
of
these
community
contributions
across
the
line
and
sort
of
the
way
I
look
at
that
is
they're
all
community
contributions.
If
they're
not
within
our
team,
they
might
be
get
loud,
team
members,
but
they're
part
of
the
community,
if
they're
contributing
to
our
code
base.
B
So
how
do
we
help
those
people
best
get
that
work
done
now?
If
it's
in
my
head
at
least
that
makes
sense
that
anything
that
ends
up
being
a
community
contribution.
Isn't
you
know
top
priority
because
otherwise
we'd
be
working
on
it
right
so
I
think
in
a
general
sense
I
would
want
to
say
we
want
to
spend
at
least
some
time
per
week,
helping
with
community
contributions.
Now
it
may
be
like
the
composer.
B
A
mother
of
one
of
our
community
members
has
contributed,
for
example,
is
not
some
over
expecting
you
get
done,
but
it's
already
in
review
and
there's
a
lot
of
work
going
on
with
it.
So
maybe
we
don't
need
to
help
a
lot
there,
but
it's
worth
keeping
an
eye
on
so
I
would
set
aside
a
little
bit
of
time
to
actually
do
that
a
week.
B
I
don't
have
a
number
in
my
head,
but
I
don't
mind
spending
a
couple
hours
like
if
your
world
of
work-
but
you
know
100
percent
of
your
time-
is
your
active
work.
Then
we
probably
need
to
make
sure
you
have
a
little
bit
more
free
time
so
that
you
can
contribute,
because
the
community
contributions
are
really
important.
I,
don't
know
what
are
your
thoughts
Tim.
A
C
E
I've
got
a
real
example
that
I
I
always
can
ask
about
work
when
he's
not
quite
ready
yet
so,
basically,
I've
done
a
bit
of
work
on
sorting
the
package
reg
package,
which
free
list,
and
that
involves
some
back-end
changes.
So
my
plan
was
that
I
was
gonna.
Ask
as
pretty
glass
you
Dan
if
I
could
borrow
some
of
Eva's,
Steve's
or
GG's
time
to
discuss
the
backend
changes
that
I've
implemented
and
whether
or
not
they're
like
suitable
good
bars,
whatever
so
yeah
that
there's
a
possible
real-life
scenario
coming
up
relatively
soon
yeah.
B
And
I
think
from
from,
if
I
put
my
my
manager
hat
on
for
a
second,
my
answer
would
be
well
you'd
have
to
our
statement
gg
whether
they
have
time
to
finish
the
work
they've
committed
to
this
month
or
this
milestone,
because
it's
not
you
know,
my
job
is
to
help
set
priorities
and
give
context.
And
if
Steve
you
like,
you
can
complete
the
work
that
you
have
without
assistance
and
you
can
get
it
all
done
and
you're
gonna
have
time.
B
Yeah
I
mean
go,
spend
the
time
you
think
is
necessarily
a
give
to
give
me
a
hand
once
that's
those
sorts
of
things
come
into
our
priorities
from
product
or
from
you
know,
discussions
we
all
had
with
with
Tim.
At
that
point,
it's
like
okay.
Now
we
need
to
allocate
someone,
but
up
to
that
point,
I
would
say
that
Steve
and
Gigi
Liberty
to
decide
what
time
they
can
give
to
you
or
Sarah
or
community
or
whatever
community's
a
little
different
just
because
we
do
want
to
allocate
specific
time
to
that
per
milestone
per
week.
B
So
I
think
that
would
be
a
little
different,
so
yeah
I
would
chat
with
Steve
if
it's
a
rails
thing
chat
with
either
of
them,
so
yeah
I
think
you
get
to
go
just
to
talk
with
them
and
figure
out.
If
they
can
have
in
tribute
time,
they
probably
want
to
see
what
you've
done.
Give
it
a
little
look
over
and
decide
how
much
time
is
involved
for
them
and
then
sort
of
allocate
time
accordingly,
and
that's
totally
funny
because
we
made
commitments
about
specific
things,
we're
trying
to
deliver.
A
On
release,
I
think
we're
maybe
in
more
of
a
unique
place,
because
the
community
stuff
we
get
is
mostly
focused
on
pages,
and
we
actually
have
like
an
incentive
for
from
being
involved
in
that
stuff,
because
our
team
doesn't
have
a
lot
of
go
experience,
and
so
the
the
people
that
are
working
on
pages
like
want
to
get
involved
in
those
community
Amar's,
because
that
helps
them
level
up
on
their
go
and
then
also
helps
like
add
features
into
the
product.
And
so
so
we've
been
spending
a
little
bit
more
time
focusing
on
that
stuff.
A
Just
just
because
it
sort
of
supports
like
bigger
initiatives
on
the
pages
side
anyway,
in
terms
of
like
other
other
community
em,
ours
I
think
we
spend
a
little
bit
of
time
on
it.
I
really
do
you
think,
like
every
team
is
different
and
depending
on
like
how
many
folks,
you
have
to
look
at
stuff,
I
suppose,
probably
where
it
packages
out
right
now,
he
probably
have
like
bigger
objectives
that
need
need
the
focus
unless,
like
that
community
stuff
is
driving
towards
one
of
those
those
goals.
A
But
I
don't
know
it's
it's
a
bit
of
a
balance
to
try
to
get
like
you
don't
want
to
like
alienate
people
either,
but
I
I
do
think
that
there's
in
my
experience
anyway,
the
expectation
around
community,
like
the
the
feedback
loop
on
community
contributions,
is,
is
typically
much
slower.
You
know
so
we
get
to
it
when
we
get
to
it.
I
actually
saw
like
this
whole
Twitter
exchange
with
DHH
over
the
weekend,
where
someone
was
like
complaining
about
this.
A
This
this
PR
that
they
made
into
rails
like
a
year
ago
and
been
addressed
and-
and
you
know,
is
his
time.
It
was
like
its
best
effort.
You
know
we
get
hundreds
of
stuff,
hundreds
of
contributions
every
you
know
every
month,
and
so
we
do
what
we
can
so
I
think
you
go
to
fall
in
line
with
priorities
and
I
think
it.
You
know
if
it
even
makes
sense
to
to
dig
into
something
go
for
it
but
I.
A
B
I
think
they
do
want
to
go
into
our
shared
or
then
just
open
any
chillness
so
that
we
can
talk
through
it
in,
in
my
opinion,
really
it's
up
to
you.
If
you
feel
like
you,
can
complete
everything
you
have
spare
time
to
help,
go
ahead
and
help
I
think
it's
important
in
our
case,
the
community
contributions
we
have
it
directly
and
what
we're
trying
to
do
now.
They're,
not
right
now,
priorities
otherwise
again
we'd
be
prioritizing
them,
but
like
composure,
and
then
we've
got
ruby
gems
and
then
we've
got
a
couple
of
other
tools.
C
C
A
Always
happy
to
if
you
want,
if
you
feel
like
saying
no
but
don't
want
to
offend
someone
or
you'd,
want
some
backing.
I'm
always
happy.
You
could
just
see
see
me
and
I'll
be
more
than
happy
to
say.
There's
no
time
well
we're
this
is
what
we're
working
on
and
and
jump
in.
So
it
feels
like
in
most
cases
you
could
probably
say:
oh
I
don't
have
time
for
that
now,
I'll
get
to
it
next
week.
But
if
it
feels
like
you,
you
don't
want
to
do
it.
B
And
I
think
on
that
note,
I
would
say
if
you
see
something
come
in
that
you
think
is
worthwhile
escalated
to
the
whole
team.
Let's
all
talk
about
it
and
decide
if
it's
a
priority,
I,
don't
if
you
feel
like
you
need
support
absolutely
as
Tim
said,
I'm
happy
to
back
you
up,
but
I,
don't
think
you
need
it
I
think
you
can
easily
say
to
someone.
No
I!
B
Don't
actually
don't
have
time
for
this
right
now
and
my
priorities
are
these
things
if
you
say
to
someone
I'm
gonna
get
back
to
it
next
week,
you're
making
a
commitment
to
get
back
to
it
next
week.
So
like
don't
just
palm
someone
offered
at
some
distance
because
that's
easier
to
deal
with
I
really
be
careful
about
I
can
commit
to
getting
back
to
you
on
this
date
or
next
week
later
in
the
week
and
I'll
follow
up
with
you.
B
B
D
Sorry
about
kind
of
barreling
in
here
I
wanted
to
take
an
opportunity
to
share
some
of
the
results
of
the
research.
Tim
and
I
have
been
doing
I
likes
to
make
sure
we
do
this
as
a
team
just
so
that
everyone
can
get
the
context
of
where
we're
coming
from
with
certain
aspects
of
priority
choices,
and
things
like
that,
starting
off,
we
did
Tim
did
a
bunch
of
research
interviewed
eight
different
individuals,
focusing
in
on
kind
of
the
retention
policies
and
garbage
collection
for
images.
D
We
interviewed
a
people,
although
we're
engineers
which
isn't
really
surprising
so
I,
can
go
into
kind
of
the
detail
of
that
if
you'd
like
in
the
later
time,
but
I
want
to
give
you
kind
of
the
highlights.
I
also
added
a
link
in
the
agenda.
If
you
want
to
go
through
and
see
kind
of
what
the
synthesis
notes
were
and
the
details
of
the
process,
we
went
through
really
what
I
want
to
go
through
now
and
kind
of
on
a
regular
basis
is
the
learnings
highlight-reel.
D
These
are
kind
of
the
high-level
points
that
we
learned,
or
we
thought
were
interesting
that
could
kind
of
impact.
How
you're
thinking
about
building
the
products
so
I'll
just
go
through
those
real
quick?
First
off,
we
got
great
validation,
that
retention
policies
and
garbage
collection
is
a
feature
or
users
once
that
was
8
for
8
users,
which
is
pretty
unusual
that
all
eight
people
committed
to
like
yes,
this
is
the
thing
I
would
use,
and
this
is
the
thing
I
want.
So
it's
always
kind
of
a
wonderful
experience
to
have
that
validation
from
real
people.
D
One
interesting
thing
was
the
end.
Result
of
everyone's
retention
policy
was
basically
the
same
thing.
There
are
kind
of
a
collection
of
sacred
images
and
packages
that
we
want
to
make
sure
utilized
and
are
safe
and
protected
and
stable
that
everyone
should
be
using,
and
then
there
is
a
whole
bunch
of
other
images
and
assets
and
artifacts
that
are
created
on
the
side
as
part
of
commits
and
merge
requests
that
get
used
once
and
then
never
really
get
used.
D
So
they
want
to
be
able
to
remove
all
of
the
junk
and
then
keep
these
kind
of
sacred
things.
Users
are
going
about
it
in
very
different
ways
to
kind
of
get
that
end
result,
but
it
was
interesting
that
the
goals
kind
of
felt
the
same
something
that
popped
up
for
me
was
the
CLI
I
was
kind
of
surprised
to
hear
that
a
quarter
of
the
people
we
talk
to
use
the
command
line,
to
interact
with
packages,
whether
it
was
creating
them
or
pushing
them,
or
even
just
viewing
the
details.
D
Let's
see
what
else
couple
more
images
and
packages
are
being
created
at
different
rates
and
scales
across
different
organizations.
Some
are
generated
once
a
month
as
part
of
an
overall
release
cycle
and
then
on
the
opposite
side.
There
are
teams
that
are
making
new
images
and
new
packages
multiple
times
a
day,
so
users
are
kind
of
experiencing
a
broad
range
there.
D
So
we
have
an
opportunity
to
kind
of
directly
link
them
back
to
what
they're
trying
to
figure
out.
You
know
where
did
it
come
from?
How
is
it
built
so
it's
kind
of
a
different
perspective
from
what
like
Jay
frog
and
some
of
our
competitors
do
so
that's
it.
I
just
want
to
share
some
highlights.
If
you
have
any
questions
about
it
feel
free
to
reach
out.
That's.
B
That's
super
cool.
Thank
you
very
much
for
that
Ian
really
interesting.
Do
we
have
like
a
sense
of
this?
You
I'm,
like
a
I,
get
bell
curve
of
what
the
sort
of
data
usage
is,
because
in
my
head
at
least
I
had
understood
that
there
were
very
few
customers,
ie
us,
but
are
using
petabytes
of
data
like
actually
really
huge,
and,
what's
that,
what's
that,
look
like.
D
I
don't
know
if
we
have
enough
data
to
really
get
that
kind
of
Factory.
We
only
talked
to
about
eight
people
and
a
lot
of
users
didn't
have
any
idea
what
size
it
was
because
there
was
just
kind
of
part
of
the
rest
of
the
size,
but
the
ones
I
did
know
we're
dealing
with
that
Terran
petabyte
area.
So
those
are
the
ones
that
I
think
we
need
to
watch
out
for
because
they're
the
ones
experiencing
issues,
because
their
registries
are
becoming
so
large.
Nice.
B
D
So
that's
a
great
question:
only
one
user
that
I
remember
specifically
called
out
using
an
alternative
method.
They
were
manually,
pushing
images
using
docker
up
to
the
registry,
everyone
else
either
kind
of
mentioned
or
alluded
to,
or
just
boldly
confirm
that
they
were
using
the
seei
pipeline
to
create
these
images.
There
was
definitely
a
strong
correlation
between
the
ones
that
are
using
the
CIA
pipeline
and
the
ones
that
have
a
lot
of
extra
artifacts
that
aren't
getting
used.
So
that's
a
detail.
We
should
pay
attention
to
all.
B
B
I
think
Tim,
but
it
certainly
come
up.
It's
bubbling
up
the
priority
list.
Pretty
quickly
is
we
need
to
be
instrumenting
our
stage
so
that
we
can
report
smell
stage,
monthly,
active
users
and
we're
not
able
to
do
that
right
now.
I
did
add
an
issue
last
week,
but
being
able
to
have
this
database
support
what
Ian's
doing
and
what
Tim's
doing
and
what
we're
all
doing
is
like
really
important,
so
I
think
we're
gonna
have
to
really
come
up
with
strategies
here,
where
we
can
start
adding
something
to
help
us
collect
this
data.
B
D
D
Another
initiative,
that's
going
on
right
now
and
I
mentioned
this
to
Tim
recently,
is
that
gitlab
is
trying
to
implement
pendo
to
kind
of
gather
user
data
so
that,
given
that
we're
at
an
early
stage,
we
might
be
able
to
get
some
really
good
coverage
quickly
as
the
rest
of
the
company
is
trying
to
implement
that
feature
or
that
tool.
Excuse
me.
D
There
were
quite
a
few
opportunities
that
yeah
I
was
kind
of
surprised
that
they
were
things
that
people
wanted.
One
was
being
able
to
link
back
into
you
know
what
file
ended
up
built
in
building
this
artifact,
what
pipeline
built
it?
So
there
were
some
surprises
there.
Some
features
also
included
like
you
know.
Users
would
use
garbage
collection
if
it
was
available,
so
this
is
a
feature
that
they
can
use
the
API
for
so
being
able
to
surface
that
there's
a
couple
of
little
things.