►
From YouTube: Package Team weekly retro July 5th
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
A
Alright,
everyone,
this
is
the
package
teams
weekly
retro
for
July,
if
I'm
gonna
read
for
Tim,
unless
at
least
for
the
work
went
not
so
well
since
Tim
is
out
today
he's
on
holiday,
which
is
awesome
starting
off.
He
said
a
few
uses
flaked
on
their
user
interviews,
so
ended
up
with
three
internal
users
and
five
external
here's
hoping
on
three
and
eight
second
item
was
spent
a
lot
of
time
in
meetings
with
the
short
week.
A
It
feels
painful
to
him
next
week
and
make
time
for
documenting
learnings
from
user
interviews
and
thinking
about
the
information
architecture
and
that
Konan
MVC
is
a
bit
behind
schedule
and
may
be
shipped
late,
which
is
kind
of
a
bummer
cuz.
We're
all
excited
about
that.
All
right
go
ahead.
Stick
yeah,.
A
Cool
yeah
and
I
think
I
think
there
is
an
effort
ongoing
right
now
to
increase
the
number
of
maintainer
Xandra
viewers,
so
yeah.
It
might
just
be
because
we're
growing
and
there's
a
lot
of
other
work
and
we've
had
a
couple
of
production
issues
as
well.
So,
like
I,
think
people
getting
pulled
around
a
fair
bit
sore
I
hope.
That's,
not
a
standard
thing.
Okay,
yeah.
B
A
Thinking
we're
actually
have
ongoing
discussions
on
both.
You
know,
code,
maintainer
and
database
maintained
errs
and
there
we
do
have
a
fairly
serious
shortage,
but
the
base
maintain
is
even
more
so
so
yeah
I.
Don't
think
this
is
gonna,
be
a
long-term
issue,
but
it's
certainly
understanding
that
would
affect
you
cool.
A
Is
that
sorry
I
didn't
mean
to
change?
If
you
had
more
thoughts
well
and
ended
up.
This
is
my
mind.
Reading
for
myself
now
maybe
I
should
have
someone
else.
Reading
for
me
ended
up
feeling
like
was
running
around
a
lot
this
week
and
not
getting
things
done.
I
think
that
comes
down
to
just
having
a
lot
to
do
and
trying
to
make
sure
I'm,
prioritizing
things
and
I
think
sometimes,
when
you
get
through
your
top
priorities,
you're
like
okay.
A
Now
what
do
I
do
because
you're
like
okay
I've,
got
all
the
main
things
out
of
the
way,
so
I
think
I,
think
I'm,
just
sort
of
working
towards
it'll
be
helped.
Once
we
have
people
joining
the
team,
the
engineers
we've
hired
and
the
team
starts
filling
out.
It'll
feel
a
little
more
clear
what
I
have
to
do?
After
that,
but
I
haven't
come
up
with
a
great
plan
for
the
time
zone
spread
starting
Monday.
There
is
a
plan,
but
I
don't
think
it's
ideal.
I
definitely
would
like
some
feedback
from
everyone.
A
We're
gonna,
probably
trial,
just
having
every
second
or
third
meeting
for
our
team
meetings
will
be
on
the
alternating
time
zone,
which
will
mean
we'll
have
to
really
be
careful
about
the
agenda
right
now.
It's
gonna
be
a
little
bit
odd,
just
because
Nick
you're
in
the
UK
and
then
Georgian
is,
is
going
to
be
in
Australia,
so
it'll
be
one
person
on
either
side
of
the
spectrum,
so
I
think
alternating
right
now,
maybe
for
this
month,
and
then
you
just
might
one
of
those
meetings.
A
You
just
have
to
make
sure
you
put
stuff
and
they
gender,
then
the
video
will
be
online,
so
you'll
be
able
to
watch
it,
but
that
is
going
to
become
more
of
a
concern,
as
we
add
more
people
to
team
because,
as
you
know,
we'll
have
people
in
Switzerland
and
other
places.
So
if
there's
anything
back,
you
have
about
how
that's
happening
or
whether
it's
working
I'll
certainly
want
to
hear
about
it.
A
We
have
go
work
that
we
have
to
do
for
container
registry
maturity
and
we've
hired
people
who
are
all
in
the
rails
world,
so
we're
trying
to
work
through
a
good
way
to
do
that
and
just
to
manage
that
that
dependency
I've
raised
it
with
everyone.
There's
ongoing
efforts,
hoping
to
get
that
sorted
sooner
rather
than
later,
but
it'll
take
time.
A
Unfortunately,
so
that
means
container
registry
is,
is
some
component
that's
going
to
end
up
in
workhorse
anyway,
which
is
which
is
go
so
definitely
thinking
in
terms
of
the
team
coming
up
to
speed
with
go
work,
because
it
will
be
a
necessity
for
what
we
do,
but
not
being
expected
to
know
how
to
fix
everything
on
the
spot
right,
because
the
expertise
takes
time.
So
that's
the
other
thing,
I'm
working
through
good
Yannick,
cool.
D
So
I've
had
a
pretty
good
week
this
week,
with
the
only
real
issue
that
I've
experienced.
Is
that
my
some
some
issues
with
like
r-spec
tests,
because
it's
not
something
I'm
like
really
overly
familiar
with,
where
they
weren't
really
passing
locally
I,
can't
really
figure
out.
Why
so
the
artifacts
that
they
were
generating
just
didn't
show
the
right.
I
just
had
things
disabled
that
should
have
been
there.
But
the
weird
thing
is:
is
that
when
I
was
running
them
on
the
pipeline
in
mr
in
an
mr,
it
did
actually
work
fine.
D
So
it's
a
little
bit
concerning,
but
yeah.
So
I
sort
of
am
not
worried
about
it
too
much,
because
if
it's
working
on
the
pipeline,
then
that's
okay
and
it's
also
just
a
local
thing.
My
site,
that's
preventing
it
from
working,
although
I
really
can't
see
what
I've
done
differently
locally,
especially
because
I
haven't
really
touched
that
area
to
code
us
a
Selfy
enough
to
sort
of
like
Park
in
day.
I'll
worry
about
that
later.
D
A
And
it
always
like
always
remember
to
reach
out
when
you
have
questions
and
I
think
I
think
you
did,
but
if,
if
you
didn't
just
like
we're
all
here
to
support
each
other,
so
like
I,
don't
think
I
necessarily
could
have
been
helpful,
but
Steve
might
have
been
able
to
be
helpful
or
it
may
be
that
someone
on
Gabby's
team
or
someone
else's
team
will
be
like
oh
yeah.
I
ran
into
that
is
the
fix
for
it
and
then
maybe
it
goes
in
the
documentation.
A
Once
we
work
out
what
the
drum
it
is
generally
assumed
that
we're
all
smart
people,
and
so
if
we
have
some
problem
in
setup,
it's
probably
because
the
documentation
is
like
missing
a
little
assumption
that
we'll
other
people
have
been
making.
So
I
generally
encourage
people,
although
I
do
it
to
myself
all
the
time.
I
generally
encourage
people
not
to
assume
that
you're,
the
one
making
the
mistake,
because
it
just
might
not
be
clear
right,
it's
so
hard
not
to
assume
that
it's,
my
people,
you
know
yes,
I
get
it
I
totally.
A
Have
that
feeling
myself,
but
definitely
don't
I
just
time
box.
It
is
really
the
best
advice.
I
can
give
give
you
something
you
can't
work
it
out.
Yeah,
you
found
a
workaround,
you
got
it
going
cool
great,
but
next
time
you
go
to
deal
with
that,
you
can
have
to
deal
with
it
again
right
so
like
it's
definitely
worth
asking
for
assistance
and
if
I
can
be
of
assistance.
Let
me
know:
I
can
hook
you
up
with
some
other
people
or
or
ask
the
other
front-end
peeps
on
your
team
because
they
might
have
had
experience.
A
B
A
Yeah,
you
are
next,
but
I
think
I
think
both
of
those
things
were
really
helpful
in
our
discussion
to
make
I
don't
think
you're
in
that
discussion.
But
the
way
I
think
about
creaming
is
a
little
different.
From
that
meeting
we
had
where
we
kind
of
went
through
what
we
were
planning
on
putting
into
a
12-2.
My
idea
of
grooming
is
going
through
the
backlog
of
stuff
and
identifying.
You
know
what
items
we
care
about
and
those
sorts
of
things,
and
you
can
only
chip
off
a
little
bit
at
a
time.
A
B
A
And
I
think
they
are
the
benefit.
Excuse
me
that
comes
out
of
that
type
of
meeting.
Is
that
I,
when
Nick
you
run
out
of
stuff
to
do
because
you've
been
killing
it?
Thank
you.
You
know
we'll
have
a
better,
clearer
idea
of
like
okay.
This
thing
is
coming
up.
We
could
probably
do
that,
whereas
right
now
I'm
still
trying
to
get
my
interim
that
so
but
yeah,
that's
also
sorry
go
ahead.
Steve.
B
Yeah
so
this
week,
I
started
looking
at
the
12:2
issues,
which
has
gone
well
feeling
a
lot
more
comfortable
with
you
know
what
they
are
where
they
are.
What
needs
to
be
done?
So
that's
that's
a
good
feeling
and
then,
in
addition
to
that
I
just
kind
of
did
it
a
little
overview
intro
of
helm,
cuz,
it's
something
that
I
know
nothing
about
and
had
never
even
really
heard
of
before
starting
here,
and
so
that
was
good.
B
A
Yeah
great
thanks
for
me
processes
in
be
working.
Okay,
right
now,
I
think,
a
lot
of
that.
You
know
we're
still
everyone's
getting
up
to
speed.
I
know
I
still
in
you
know,
I
think
with
their
cadence.
We
have
of
monthly
releases.
You
we
only
cycle
through
this
process
like
once
a
month,
so
it's
slowed
to
sort
of
learn
from
that
and
improve
so
without
constant
deployment.
A
Work
coming
forward
means
that
we're
gonna
have
a
faster
cycle,
I
think
and
so
that'll
mean
that
we
have
a
more
opportunity
to
improve
and
because
the
cadence
is
increased,
so
like
I
feel
like
everything's,
pretty
good
right
now,
but
yeah,
it's
probably
just
going
to
get
better,
which
is
good.
Both
of
you
have
been
doing
great
work.
Thank
you
very
much
like
I
feel
like
you're,
both
getting
through
your
work.
Pretty
quickly.
A
I
definitely
tend
to
sort
of
want
to
start
people
out
with
simple
things
and
then
increase
it
as
we
realize
we're
capable
so
I'm
gonna
probably
start
looking
at
just
adding
a
few
more
items
to
the
list.
The
work
to
do
because
you're,
both
getting
through
everything,
pretty
quick
and
I,
just
want
to
say
thank
you
very
much
for
your
hard
work.
So
it's
been
really
good.
A
D
One
of
the
issues
in
particular
had
quite
a
lot
of
like
significant,
like
handle
changes
and
I
think
coming
if
it
was
last
month
time
before,
I
did
mention
that
wasn't
too
familiar
with
the
ham,
syntax
and
so
being
able
to
get
that
issue
through
without
actually
actually
having
any
like
recommended
updates
from
the
review
or
something
was
I
was
really
quite
happy
about
that.
So
I
guess
I,
guess
I'm
starting
to
know
how
hammer
works.
D
Suppose
the
yeah
it's
pretty
I
was
pretty
happy
about
that
and
then
finally
I'm
just
getting
way
more
comfortable
with
that
that
mr
and
reviewing
process
and
just
understanding,
what's
expected
of
me
and
what's
expected
of
the
reviewers
and
that
kind
of
stuff,
and
that's
just
like
giving
me
way
more
confidence
that
can
actually
do
more
issues
and
I'm,
confident
that
I'll
be
at
her
like
deliver
those
issues
and
not
get
stuck
in
some
process
somewhere,
where
I'm
doing
something
slightly
wrong
or
against
the
flow
or
whatever
so
yeah.
That
feels
good
as
well.
D
A
Yeah,
but
you
definitely
both
been
I've,
been
really
happy
with
that,
and
I
mean
Hamels
Hamels
kind
of
weird,
but
it's
it's
good
too
and
I
think
that's.
This
is
part
of
the
reason
why
we
try
and
keep
the
issue
Campbell
when
you're
starting
out,
obviously
so
that
you
can
work
all
this
stuff
out
and
get
some
level
of
comfort
with
it.
Also
like
this
is
great
there
and,
as
we
add
people
to
the
team,
it
means
you
can
sort
of
help
guide
them
through
it.
So
that's!
A
That's
really
all
I
got
I
think
the
only
thing
is
just
that.
Another
reminder
that
Georgian
is
is
starting
on
Monday
and
that'll,
be
Australian
Monday
that
he'll
be
starting.
So
that
means
before
we're
all
awake,
so
keeping
in
mind
that
yeah,
it's
here's
a
onboarding
buddy
who's
in
the
same
time
zone.
A
A
It's
a
good
thing
to
keep
in
mind
that
if
you're
sort
of
looking
for
feedback
or
information
from
someone
that's
any
different
times,
either
check
where
it
is,
and
everyone
make
sure
you
slack
settings,
aren't,
can
be
pinging
you're
late
at
night
and
all
that
sort
of
stuff.
Because
if
that's
not
that's
not
desirable,
so
cool,
it's
all
I've
got
anyone
else
have
anything
before
we
call
it.