►
From YouTube: Package Retro 06-14-19
Description
Weekly team retrospective where we talk about what went well and not so well.
B
B
He
want
to
kick
it
off,
please
team,
yeah
I
would
say
just
one
of
the
things
that
went
not
so
well.
For
me,
this
week
was
working
with
a
enterprise
customer
on
troubleshooting,
an
issue
that
they
had
the
way
that
the
request
went
from
their
account
rep
to
us.
An
issue
wasn't
opened
and
it
was
really
not
great
communication.
B
It
solved
the
problem,
so
that
was
a
little
frustrating
I'd
like
to
resolve
that
to
make
sure
we
improved
that
moving
forward
and
then
not
really
that
it
didn't
go
well,
but
I
had
big
plans
for
the
week.
I
wanted
to
tackle
a
lot
of
big
issues,
but
ended
up
getting
sucked
into
a
lot
of.
There
was
a
lot
more
little
details
that
I
needed
to
get
done
before
I
could
work
on
those
big
issues,
so
it
was
helpful
but
a
little
disappointing
that
editing
gets
a
tackle
but
sort
of
the
bigger
problems.
B
C
So
I
had
a
just
my
few
small
things,
that
kind
of
went
not
so
well
just
overall
kind
of
like
diving
into
the
docker
registry,
and
you
know
how
all
of
that
works
and
everything
to
do
with
it.
There's
just
so
much
information,
it's
kind
of
one
of
those
things
that
were
like
the
deeper
you
go,
the
more
there
is
so
it's
just
sort
of
a
feeling
of
you
know.
C
I've
still
got
a
ways
to
go
in
terms
of
learning
all
that
which
is
expected
and
in
addition
to
that,
just
not
really
getting
as
much
time
to
work
on
the
NPM
subgroup
issue,
as
I
had
hoped.
There's
just
a
lot
of
other
stuff
going
on
this
week,
which
has
been
good,
there's
tons
of
work.
So
that's
exciting,
yeah.
A
Cool,
thank
you
and
I'm,
not
sure
if
people
feel
like
good
about
making
this
an
interactive
experience,
but
definitely
if
you're
feeling
like
a
little
bit
unsure
about
where
you're
going
we
you
know,
we
tried
to
make
sure
you
have
a
buddy
with
Jason
and
other
people
and
if
there's
anything
that
I
can
be
doing
to
help
I.
Please
let
me
know
and
I'll
keep
an
eye
on
your
one-on-ones
closely
to
try
to
do
that.
A
For
me,
I
think,
let's
go
feel
like
I'm.
Getting
up
to
speed,
I
mean
it's
week.
Six!
So
that's
expected,
like
you
said,
right,
Steve,
it's
like
yeah,
it's
kind
of
expected
that
you
don't
know
things
so
that's,
but
it's!
It
feels
a
little
frustrating
to
my
cart.
There's
so
much
I
want
to
be
doing,
and
it's
there's
a
lot
of
surprises,
or
at
least
new
knowledge
that
I'm
getting,
which
is
good
as
well,
I.
A
Suppose,
a
lot
of
management
aside
things
next
one
was
the
lots
of
work
to
be
getting
to
done
getting
to
a
point
where
we
can
move
forward
with
container
registry.
I
have
a
lot
of
things
to
get
together.
I
had
a
chat
in
my
one-on-one
with
with
my
director
and
yeah.
That's
been
helpful,
but
I
still
I
still
know,
there's
a
lot
to
get
through
and
there's
a
lot
to
learn
in
that
process
as
well.
E
Say
for
me,
then:
I
have
eyes
just
get
a
little
bit.
I,
don't
know
frustrate
it's
the
wrong
word,
but
just
wasn't
sure
about
myself
with
one
of
my
night
requests
that
I
was
doing
for
one
of
my
issues
where,
because
I've
done
like
an
experimental
change
on
the
back
end,
just
so
that
I
could
do
the
front-end
development
work,
it
was
friend
a
lot
of
errors
when
I
was
doing
the
pipeline
jobs
when
I
when
I
was
committing
to
the
motor
quest
I.
E
Wasn't
a
hundred
percent
sure
like
like
how
to
fix
those
or
whether
or
not
I
was
going
to
cause
problems
by
just
constantly
pushing
up
there's
quite
a
few
that
I
had
to
work
for
you
like
one
at
a
time
and
like
it
would
be
a
push
and
then
wait
for
it
to
the
way
for
the
job
to
sort
of
fail
and
then
figure
out
what
went
wrong
and
then
do
another
push
and
I
had
to
do
that
all
three
or
four
more
times,
it's
just
a
little
bit
unsure
about
myself.
This
place
unique.
A
E
So
yeah,
it
was
nothing
to
do
with
with
that.
It
was
more
about
just
the
process
of
care.
It's
not
really,
perhaps
understanding
it
or
just
being
a
bit
new
to
it,
I
guess
and
unsure
about
how
to
proceed.
I
think
was
probably
it
for
me.
E
D
No,
not
at
all
just
I
just
want
to
mention
that
like
thank
you
for
saying
that,
but
we're
totally
good
no
ball,
dropping
no
balls
were
dropped.
So
for
me
geek
botted,
my
only
bad
thing
I
feel
like
this
week
went
pretty
well
from
my
perspective,
so
he
bought
ignored
me
for
a
couple
days.
Had
me
really
wondering
if
it
was
me
if
I
did
something
Daniel
said:
I
missed
its
birthday,
that's
probably
true!
D
So
I
was
a
little
bit
upset
about
that
I
felt
like
I,
wasn't
able
to
accurately
report
what
was
going
on
so
Mike.
My
week
was
was
just
you
know,
I
kind
of
updated
everybody
today,
geek
Bob
picked
me
back
up
today,
so
I
feel
good
about
that.
We're
friends,
geek
bye,
my
friends
again,
I
just
wanted
to
mention
that
was
kind
of
a
bummer.
B
Ok,
so
I
could
start
with
what
went
well
and
had
a
great
conversation.
A
synchronous
conversation
with
Amelia
and
Dimitri
about
improving
navigation
for
overall
package
features
so
combining
it
under
one
top
level
knob
and
and
what
does
that
look
like?
It
was
great
going
back
and
forth
with
a
designer
and
getting
feedback
and
updating
the
issue
was
was
really
helpful
for
me.
Oh.
B
I
thought
all
the
conversations
that
Daniel
and
Steve
that
you
guys
were
having
with
people
like
Camille
and
and
Maren
were
really
helpful
for
me
to
listen
in
to
and
to
help
capture
some
notes.
It
was
really
great
to
see
how
those
conversations
are
progressing
and
to
see
how
sort
of
your
minds
are
changing.
As
the
conversations
happen.
So
I
was
really
glad
to
be
a
part
of
that
and.
C
Yeah
I
can
ii
actually
that
the
calls
about
the
container
registry
with
various
people.
Those
have
been
great
for
me,
they're,
giving
some
good
insight
and
giving
me
places
to
look
and
learn
as
well.
So
those
are
our
very
good
and
helpful
for
me
and
then
the
big
thing
that's
been
going
really
well
this
week,
for
me
is
my
first
marriage
request:
I've
been
learning
a
ton
about
just
like
how
the
process
works.
A
That's
awesome
and
that
that
links
into
one
of
my
one
of
my
things
that
went
well
is
this
I
thought
you're
getting
up
to
speed,
really
quick
Stephen.
Your
work
is
really
appreciate
it
and
it's
really
it's
really
exciting.
For
me
to
say
it
makes
me
really
happy
that
you
you're
actually
getting
integrated
I,
wouldn't
look
at
that
MRR
that
you
had
an
old
feedback
you're
getting
and
it
looks
really
cool.
Initially,
I
went
looking
for
it
in
the
in
the
EE,
repo
and
I
couldn't
find
it.
I
was
like
wait.
What.
A
So
super
glad
that's
happening
for
me.
Lots
of
work
to
be
done.
The
container
registry
maturity
so
I
have.
This
is
a
negative
and
a
positive,
because
it's
really
exciting
actually
and
we're
doing
a
lot
of
really
good
work.
Having
speed
conversations
so
I
feel
like
this
is
one
of
the
areas
where
I
feel
like
I'm,
actually
like
doing
something
valuable
and
succeeding.
Even
though
often
it
feels
like
I'm,
just
always
learning
new
things
and
realizing
I
got
to
do
stuff
different
or
whatever
it
is
so.
A
This
has
been
really
cool
and
and
I
feel,
like
I,
just
generally,
I
feel
like
I'm,
getting
a
bit
more
of
a
handle
on
things
which
is
nice.
There's
a
lot
to
learn
and
take
in
here
and
particularly
excited
about
hiring.
We
actually
had
someone
sign.
I
will
be
starting
in
early
July.
That
person
is
an
AIPAC
which
would
be
very
exciting.
A
I'm
gonna
reach
out
to
Dylan
cuz
some
help
there
ever
are
localized
on
Boateng
buddy,
at
least
in
the
same
time
zone,
and
we
also
are
sending
it
off
of
somebody
who
is
going
to
be
a
senior
and
that's
really
important
for
our
team.
I
want
to
make
sure
we
have
someone,
that's
like
legit
senior
and
that
we
can
have
people
teaching
each
other
and
stuff
so
very
excited
about
that
cool,
auntie,
John.
D
Thanks
Daniel,
so
yeah
I,
just
wanted
to
say
positive
perm
for
me
is
Nick,
is
nearly
on
boarding.
I
think
we're
pretty
close
to
wrapping
that
up
and
he's
also
doing
a
great
job
digging
into
his
first
couple
issues.
We
had
a
chat.
We
had
a
chat
earlier
this
week
about
the
issue
in
Daniel,
its
you
had
mentioned,
and
so
Nick
I'm,
just
feeling
very
positive,
I
think
you're
doing
awesome
job,
and
so
thank
you
for
all
of
that.
Just
want
to
share
that.
E
Cool
thanks
a
lot
so
as
to
me,
yeah
started
to
write
my
first.
It's
a
front
end
code
this
week,
which
is
really
cool
and
that
they
went
well.
Let
the
fact
metal
pieces
went
well
and
like
the
testing
and
learning
how
the
testing
framework
stuff
works
was
interesting
and
that
went
really
well
as
well
and
I
feel
pretty
confident
that
we
can
sort
of
do
some
really
cool
stuff
on
the
front
end
for
the
Pretender
interesting
stuff.
E
There's
lots
I've
got
lots
of
ideas
and
they
lots
of
feedback
that
I
need
to
write
down
and
share
out
and
it
can
be
discussed,
but
yeah
on
the
whole
feeling
really
positive
about
what
can
actually
be
done
here.
The
opportunity
that
is
in
front
of
us
as
well
for
what
we
can
do
as
well.
It's
really
cool
other
than
that
I'd,
some
really
cool
like
coffee,
chats
and
things
with
that
and
more
interaction
with
more
developers
over
the
course
of
the
week,
which
has
been
really
awesome
as
well
so
and
just
yeah.
A
Yeah
Nick
I
just
want
to
say
we're
all
really
glad
you're
on
the
team.
It's
awesome
to
have
like
us
turning
into
an
actual
team
so
as
if
I
was
just
being
Porton
sitting
there
by
himself
going
when
do
I
get
people
in
my
team
to
help
me
and
so
a
big
way
as
we've
added
people
like
Joe,
we've
all
had
that
experience.
That
being
like,
didn't
you
say
it
was
a
team
right.
A
So
it's
great
to
have
you
here.
It's
awesome.
We're
definitely
going
to
try
to
manage
some
of
the
meetings
and
I've
been
speaking
with
other
managers
about
how
they
handle
having
you
know
these
really
disparate
time
zones,
because
to
two
of
the
engineers
who
are
starting
in
August,
one
is
in
Romania
and
ones
in
Switzerland,
and
then
the
engineer
starting
in
July
is
actually
in
Australia.
So
that
means
we're
spread
all
over
the
globe.
So
we're
going
to
come
up
with
strategies
to
sort
of
allowed
people
to
be
in
meetings.
A
That'll
mean
we
won't
be
all
be
able
to
go
to
all
of
the
meetings,
but
it'll
mean
that
we
want
to
schedule
regular
meetings
for
people.
So
that
people
can
like
just
get
to
see
each
other,
because
that's
really
important
I
think
but
bear
with
me,
while
we
figure
that
out
I
definitely
would
like
people's
input
John
or
anyone
who's
who
sort
of
got
that
experience.
If
you
minds
that
offers
suggestions
and
how
we
might
go
about
doing
that,
please
feel
free.
A
Put
it
in
package
channel
happily
discuss
everything
out
they
out
then
I'm,
not
gonna
need
to
have
private
conversations
about
that
stuff.
You
know
action
items,
I
think
probably
Tim
put
these
down
asking
whether
we
think
we
should
do
quick
demos
in
this
meeting.
Everyone
can
speak
up
if
you
feel
passionate
about
it.
I.
B
Thought
it
would
be
cool
to
get
more
involved
in
some,
even
if
it's
just
a
quick
review
of
something
that
you've
been
working
on,
it
doesn't
even
have
to
be
related
to
work.
It's
something
that
just
give
people
the
chance
to
show
something
specific
and
talk
about
it,
because
I
really
like
this,
the.
What
did
we
learn
portion
of
our
stand
up
each
day,
it'd
be
cool.
If
we
had
a
piece
of
this
retro
that
was
like
and
here's
something
that
I
learned
this
week
or
I.
B
A
I
feel
like
what
I
actually
really
like
that
I've
worked
in
companies
where
we
have
a
scheduled,
Lunch
and
Learn
or
Thursday
learnings.
We
call
it
and
where
people
can
just
talk
about
something
it
doesn't
even
have
to
be
work-related.
Where
you're
doing
the
presentation,
it
helps
you
to
start
learning
out
of.
Can
you
had
effectively
that
everyone
right
I
mean
so
there's
a
lot
of
benefits
to
that?
A
Aside
from
just
here's,
the
thing
I
did,
which
is
really
cool,
to
write
like
I'm
gonna
see
what
people
are
working
on
well,
I
should
know
that
already
do
you
know
what
I
mean,
but
I
don't
I
wouldn't
want
to
muddy
up
the
retro
with
that.
So
I
actually
really
like
that
idea,
but
I
think
it
probably
better
served
having
a
meeting
for
that.
A
A
Coordinator
a
presentation
on
it,
but
maybe
he
does
maybe
he's
excited
about
it.
Maybe
Nick
does
some
front-end
thing
that
looks
awesome
and
he's
like
this
thing
is
really
cool.
I
want
to
show
us
that,
and
that's
something
that
he's
motivated
to
do
a
couple
of
minutes.
Talk
on
so
I
really
like
that
idea,
but
I
think
he'd
be
better
served
in
another
format.
What
does
everyone
else
think
about
it?
I.
C
D
A
You
know
I
think
the
cadence
is
more
around
when
I
finish
something
right
like
so
we
have
a
regular
meeting
that
is
like
every
week.
You
have
to
tell
us
what
you
worked
on.
It
becomes
like
a
chore
right,
it's
not
what
it's
supposed
to
be
it's
supposed
to
be
at
least
in
my
head,
and
everyone
can
disagree
on
it.
But
you
know
it's
just
my
opinion.
Midi
in
my
head.
A
The
way
that's
supposed
to
be
representative
something
I'm
excited
about
and
I
want
to
share
with
the
team
and
an
opportunity
to
teach
someone
else
on
the
team
who
maybe
doesn't
know
what
I've
been
working
on
and
something
that
you
know
an
opportunity
to
teach
other
people
on
a
team.
How
to
do
so.
So
I
think
that's
like
really
cool.
You
know:
Steve
Nick,
John,
Tim,
everyone.
A
A
Can
you
finish
a
feature
that
you've
been
working
on
Steven
or
Nick,
or
whoever
and
go
hey
I'm
really
excited
about
this
I
really
want
to
present
this
to
the
team
and
just
you
can
think
of
it
as
an
opportunity
to
teach,
but
also
an
opportunity
to
practice
those
presentation,
skills
and
communication
skills,
and
that's
actually
really
helpful.
That's
valuable
work,
it's
one
about
one
about
like
core
things.
We
have
been
our
experience
as
we're
sort
of
thinking
about
growing
our
career.
It's
actually
an
important
part
of
it.
C
Like
in
that
terms
like,
if
it's
something
that
you
really
want
to
like
share
it
present,
then
yeah
we'd,
like
kind
of
mention
it
and
like
say,
okay,
I,
want
to
present
this
like.
Let's
pick
a
time
and
you
know
whoever
can
come,
can
come
and
check
it
out
and
then
like
if
there's
just
something,
that's
like
really
small
that
you're,
just
like
hey
I
thought
this
was
cool.
Just
wanted
to
share
this
like
real
quick.
We
could
throw
that
into
like
the
weekly
sync
meeting,
or
something
like
that.
A
I
think
that's
a
good
idea
and
I
appreciate
Tim
suggestion
of
adding
it
to
a
meeting,
because
that
doesn't
feel
like
you've
got
to
fill
up
like
10
minutes
or
15
minutes
with
something.
The
other
thing
that
would
might
make
sense
is,
if
you
do
a
presentation
and
record
it
which
you
should
be
doing
anyway,
then
it
gets
async
and
then
the
people
who
can't
attend
because
they're
in
a
whole
other
time
zone-
and
it's
like
4:00
in
the
morning
and
I
deal
with
this-
don't
get
to
actually
enjoy
that
process
as
well.
A
A
Actually,
probably
spell
that
right
and
then,
when
we
start
with
that
and
then
I
think,
if
there's
something
even
bigger
than
that,
maybe
5
over
10
minutes
or
something
you
just
do
a
quick
presentation
and
have
people
join
and
and
then
just
record
it
and
knowing
that
not
everyone
will
attend,
and
that
would
just
be
a
thing.
But
it
will
be
part
of
our
sort
of
our
video
of
stuff
online.
It
makes
sense
to
people
yeah.
A
Well
and
the
other
thing
there
is
like,
as
as
engineers,
building
up
a
reputation
as
being
part
of
the
community
is
actually
really
valuable,
like
that's
actually
a
big
deal
like
think
of
it
as
you're
like.
Oh,
this
is
my
open
source
contributions
and
then
you're
actually
talking
about
what
you've
contributed.
As
an
engineer,
you
can
also
point
to
videos
that
are
actually
are
now
on
the
YouTube
channel
and
be
like
yeah.
This
is
this
thing
I
built.
A
B
Yeah
I
think
this
one
was
from
last
week
actually,
but
we
wanted
to
schedule
time
to
review
the
NPM
PM
integration
and
record
and
share
with
the
team
we
mentioned
just
having
sort
of
a
doing
exactly
that,
a
demo
of
how
the
feature
works.
I
think
we
could
do
that.
Maybe
once
Steve
gets
a
little
further
into
the
issue
with
subgroup,
and
maybe
that
could
be
something
that
we
do.
We
have
a
meeting
and
we
and
we
go
over
how
that
works
and
and
what
you've
uncovered
and
covered
in
a
little
bit
more
depth.
A
B
A
A
separate
note
we're
coming
up
one
time:
I,
don't
want
to
take
too
long
with
this,
but
I'd
like
to
get
people's
thoughts
on
whether
they
want
to
do
this
as
a
more
of
an
interactive
thing.
I
don't
want
to
make
this
for
me
at
least
I
like
having
interactive
experiences.
Saying
I
was
struggling
with
this
and
someone
saying.
Oh
what
about
that
or
hey
come
to
me
with
this,
like
it's
a
little
bit
more
interactive
rather
than
just
sort
of
like
here's.
A
A
thing
is
a
thing:
here's
a
thing
so
I
I
personally
find
that
helpful.
If
people
don't
also
find
that
helpful,
we
can
continue
with
this
format.
It's
totally
fine
I'm,
not
trying
to
dictate
how
we
do
this
meeting.
It
should
be
valuable
to
people
right
and
it
should
be
helpful
to
be
able
to
let
people
know
where
you've
succeeded
and
failed
and
the
question
we
should
succeed.
It
felt
sorry
where
we've
had
like
things
that
didn't
work.
Well,
it
didn't
work,
did
work
well.
A
What
we're
really
trying
to
do
here
is
I
then
identified
the
things
we
that
worked
well
and
keep
doing
more
of
those
things
right,
I
mean
it
shouldn't
be
as
much
of
a
I
did
a
thing
and
I've
done
this
myself.
It
shouldn't
be
as
much
of
an
idea
thing,
but
you
know
more
of
a
hey.
This
is
a
process
or
a
way
of
doing
things
that
really
helped
me
and
it's
meant
to
be
sharing
with
the
team.
This
methodology
worked
for
me
and
the
other
people
can
go
our
suite,
that's
great,
a
great
suggestion.
A
D
This
is
very
valuable.
Kennedy
hear
me,
okay,
my
I
think
this
is
very
valuable,
especially
in
the
sense
that
we're
all
a
blue
team
and
we're
all
learning
how
to
work
with
each
other
and
still
learn
and
get
that
processes
and
all
of
those
things.
I
think
this
is
very
valuable.
Just
to
get
an
insight
into
is
anybody.
You
know
feeling
like
they're
struggling
a
little
bit
or
are
we
getting
good
lots
of
wins?
C
Yeah
I'm
all
for
it
I'm
the
same
way.
I
I
love
interactive,
more
interaction,
as
is
good
for
me
and
yeah
I.
Think
it's
just
a
good
sort
of
like
wrap
up
like
to
the
week
whether
or
not
we
keep
it.
You
know
synchronous
or
asynchronous,
as
the
team
grows
that'll
be.
You
know
a
per
question,
but
I
do
think.
It's
helpful
and
yeah
cool.
E
Absolutely
I
was
gonna
say
that
I
I
really
devalued
the
whole
interactive
thing
as
well.
I
think
he's
probably
gonna
result
in
like
better
ideas
coming
from
things
when
somebody's
trying
to
explain
something
and
you've
got
five
six
seven
other
people
listening
in
and
feel
that
they
can
actually
contribute
as
well.
The
end
result
is
going
to
be
like
ideas
and
brainstorming,
and
things
like
that
I
think.
That's
gonna
be
really
useful.
E
The
only
thing
I
would
say
that's
slightly
about
that
is
that
it
can
like
if
it's
unstructured,
it
can
lead
to
like
meetings
taking
longer,
and
you
do
have
to
like
it's
pretty
hard,
but
you
do
have
to
sort
recognize
how
thick
we
are
drifting
here
and
we
need
to
sort
of
real
this
in
or
go
have
a
discussion
about
this
elsewhere
or
or
yeah
basically
do
something
like
that.
Just
what
just
crushes
that
time
but
yeah.
E
B
A
Yeah
I
think
that's
a
good
suggestion.
I
think
everyone
should
feel
free
to
do
that
I'm,
just
in
the
interest
of
time
we're
right
at
time
right
now.
But
what
I
want
to
do
is
the
next
one.
Let's
just
make
sure
we're
hammering
through
our
points,
so
they
can
get
through
them
quickly.
Right
now,
I
said
it
a
little
bit
of
pausing
and
stuff,
let's
just
get
through
them,
real,
quick,
so
that
we
can
actually
use
this
more
interactively
sounds
like
everyone
enjoys
this
meeting.