►
From YouTube: Package Retro 06-21-19
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
Dan
says
still
a
lot
going
on
and
feels
like
he's
lacking
context.
In
some
areas
they
don't
have
a
full
team.
Yet
so
it's
difficult
to
understand
what
we
need
to
and
can
improve
as
well
as
execute
on,
and
that
we
need
to
be
more
careful
to
understand
our
processes
around
asynchronous
engagement.
Things
like
agendas
for
things
are
searchable,
but
videos
aren't
I.
Think
that's
a
comment
about.
A
For
me,
I
have
an
excitin.
It's
not
real.
I
had
actually
a
great
week,
and
my
small
item
was
that
I
had
to
put
together
that
presentation
for
the
group
meeting
and
I
hadn't
put
together
a
polished,
PowerPoint
presentation
and
quite
a
while
and
so
I
had
to
shake
off
some
serious
cobwebs
in
terms
of
designing
a
nice
presentation.
But
once
I
got
there,
it
was
fine.
B
Yes,
I,
basically
we're
just
waiting
for
me
to
get
access
to
dev
kit
lab
calm
and
which
is
what's
required
for
me
to
get
a
license
to
work
on
one
of
the
upcoming
issues.
I
was
supposed
to
work
on
so
I.
Don't
have
access
to
welcome
out
locally
and
yeah,
just
because
John's
been
so
busy
with
without
hiring
and
everything
else
has
been
going
on.
It's
taking
a
little
while
to
get
your
question
and
then
that's
taking
a
little
while
to
now
process
as
well,
okay,
but
should
be
resolved
soon,
hopefully
yet
like.
B
A
C
B
Yes,
I
I've
stopped
being
plugging
away
on
a
merge
request
this
week
for
one
of
my
first
issues-
and
there
was
quite
a
lot-
I
had
quite
a
lot
of
trouble
trying
to
get
it
already.
You
know
getting
past
tests,
and
things
like
this
and
like
the
pipeline
was
failing
quite
often
and
then
yeah
there
was
like
changes,
I
had
to
make
and
all
of
that
kind
of
stuff.
B
So
it's
just
basically
getting
used
to
the
whole
process
and
and
minute
not
being
particularly
confident
about
it,
but
over
the
course
of
the
week,
I
feel
that
I've
gotten
quite
a
bit
more
confident
about
how
the
whole
thing
works,
which
is
one
of
my
good
notes.
It
was
just
yeah,
it
was
just
like
I
was
having
a
bit
of
travel
the
other
day,
getting
a
rebase
to
work,
and
it's
actually
apply
correctly.
Got
there
in
the
end,
but
yet
Mike
might
get.
C
For
me,
I
was
sick
Monday
so
that
that
wasn't
fun,
but
actually,
despite
that,
I
was
probably
one
last
week's
that
had
the
other,
not
so
well,
it
was
kind
of
it's
it's
both
in
the.
What
went
well
and
not
so
well,
is
that
you
know
just
like
the
the
sort
of
public
face
of
the
reg
requests.
Reviews
is
a
bit
humbling
of
you
know
like
just
like
here's
all
this
stuff
that
you
could
have
done
better
and
and
then
reality
like
I've
never
actually
worked
somewhere.
C
B
A
That's
cool,
seeing
the
merge
requests
in
the
comments
and
how
engaged
people
are
who
aren't
on
our
team,
or
you
know
really
going
through
and
paying
a
lot
of
attention
to
how
the
code,
what
code
gets
merged
and
getting
back
and
stuff
it's
excellence,
I've,
never
been
part
of
a
company
that
was
so
thorough
in
that
way.
Either
it's
pretty
cool
I
mean
probably
intimidating,
though
as
well.
Well,.
A
Okay,
so
the
what
went
well
Porsche
is
I
can
go
first.
Steve
I'll
just
say
that
the
issue
that
you
put
together
for
the
NPM
subgroups
was
or
the
comments,
and
that
issue
was
really
helpful
for
me
and
then
the
patient
explanation
and
walking
me
through
how
each
use
case
could
possibly
work
and
the
pros
and
cons
and
limitations
was
really
helpful
for
me
and
maybe
really
grateful
to
have
a
team
like
you
know,
just
be
me
and
and
it's
helping
to
drive
my
understanding
of
the
product
and
everything
so
that
was
awesome.
A
I
really
appreciate
that
you're
welcome
and
Dan
and
Jason.
My
boss
were
both
super
helpful
with
preparing
for
the
group
conversation
which
I
wasn't
aware
of
until
Sunday
that
it
was
gonna
happen
on
Wednesday,
and
so
they
both
helped
me
with
the
presentation
and
help
me
practice
a
little
bit
and
then
Dan
obviously
chimed
in
and
was
answering
some
questions
and
Jason
was
asking
some
friendly
questions
that
he
knew
that
I
knew
the
answers
to
which
is
really
helpful.
Oh
yeah
I
was
grateful
just
for
all
the
teamwork
this
week.
B
A
Can't
let
Bobby
bias
to
action.
Our
team
is
great
here.
It's
the
smiley
face
and
speaking
of
team,
three
of
four
of
the
vacancies
have
signed,
and
one
has
a
verbal.
Yes,
so
we're
really
building
out
the
team
quickly,
which
is
great
and
the
investigation
into
the
future
work
for
the
container
industry
has
been
extremely
informative.
I
agree
as
I
could
second
I
thought
as
well
and
I
guess:
I
could
read
John's
as
well
since
I'm
on
a
roll
having
fun
studying
rails
with
folks,
that's
fun
for
me
as
well.
A
It
seems
like
the
group
is
growing
as
well.
We
just
added
someone
else
from
release.
Team
Nick
is
doing
an
awesome
job,
completing
his
assigned
issues
and
acclimating
to
get
LEM
I
agree
with
that.
It's
great
to
see
you're
already
closing
out
issues
in
12,
which
is
full
milestone
ahead.
That's
pretty
awesome.
C
Yeah
earlier
this
week,
my
first
bridge
request
got
merged,
so
that
was
just
like
a
good
feel-good
moment
and
then
my
second
request
is
in
review
right
now
and
that's
some
like
super
good
feedback
on
that,
and
it's
just
you
know,
teaching
you
how
to
think
about
and
write
some
better
code
overall.
So
that's
really
awesome.
C
I've
had
some
really
good
moments
this
week,
some
sort
of
like
aha
moments,
of
just
kind
of
understanding,
the
code,
how
some
of
the
structure
of
the
code
is
set
up
and
how
the
NPM
system
works
in
general
and
then,
as
I
said
before
this
week,
has
been
great
and
just
kind
of
really
loving
everything
about
get
lab
and
how
get
a
lot
of
work,
flow
works
and
I'll
just
kind
of
awesome
right
now.
That's
awesome.
B
Okay,
yes,
if
you
me,
it
was
basically
just
down
to
my
mr,
where
I've
learned
so
much
from
going
through
all
those
trials.
I
had
lived
with
the
merging
and
the
danger
bar
and
feedback
saying
all
of
that
is
just
resolved
in
like
a
really
sort
of
a
positive
feeling
that
actually
it's
quite
intimidating
at
first,
but
actually
it's
really
not
that
bad.
You
just
have
to
like
jump
in
and
get
stuck
in,
I
suppose,
and
it's
very
similar
to
what
Steve
said
as
well.
B
I
also
come
from
a
previous
job
where
there
was
no
such
thing
as
motor
quest
like
we
barely
had
more
than
one
master
branch
you
know
like
it
was
it
was.
It
was
chaos,
thinking
back
to
it,
so
how
we
used
to
do
things.
So
it's
very
like
yet
coming
here,
it's
fairly
illuminating
to
sort
see
I
like
some
real
development,
I
suppose
actually
happening,
and
not
just
like
a
bunch
of
other
Cowboys
just
thrown
code
into
a
repository.
So
I'm
really
like
to
join.
That
and
I
feel
this
like
a
lot
to
learn.