►
From YouTube: Weekly Retro 09-06-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
Okay,
hello,
everyone:
this
is
the
weekly
package,
retro
and
I
want
to
kick
off,
but
just
as
a
point
of
order
and
I
think
in
a
couple
of
places,
people
have
added
someone
that
someone
else
has
added
some
and
then
someone
else's
that
first
person
has
added.
So
if
you
have
items
just
read
through
them
in
order
and
skip
over
that,
we'll
figure
that
out
later
but
I'm,
just
it's
as
more
contiguous
that
way.
I'll
read
for
Gigi,
since
this
is
at
a
time
when
he
can't
attend.
A
This
is
what
went
not
so
well
for
September
6th
tag.
Delete
em
are
still
not
merged,
taking
a
lot
way
longer
than
I
expected.
He
also
says
the
docker
registry
disappointed
again
no
pagination
in
the
tags.
Api
yep
and
those
are
things
we're
pretty
aware
of,
at
least
in
the
generality
of,
like
there's,
not
a
whole
lot
of
development.
In
the
a
case
there
so
and
that's
an
area
that
we're
trying
to
address,
go
ahead.
Steve.
B
Yeah
I've
just
realized
that,
like
I'm,
usually
pretty
productive
in
the
mornings,
that's
like
when
I
eat.
In
my
like
momentum,
flow
and
I've
noticed
that
a
lot
of
times
you
know
having
various
meetings
throughout
the
mornings
breaks
up
that
momentum
for
me,
and
so
I
certainly
don't
get
to
take
full
advantage
of
that
productivity
before
my
afternoon,
food
coma
and
then,
secondly,
we're
just
like
a
at
least
I
feel
like
there's
still
a
lot
to
be
figured
out
with
Conan.
C
I
think
I'm
index
I.
Just
this
week
we
had
a
bit
of
a
snag
with
the
research
survey.
We
are
ready
on
our
side,
but
there's
an
accessibility
issue
that
we
know
about,
but
we
have
to
coordinate
with
the
brand
ambassadors
and
make
sure
that
everything
is
kind
of
smooth
they're.
The
two
people
on
the
research
team
that
are
kind
of
helping
us
coordinate
this
we're
both
on
vacation
and
so,
unfortunately,
it
just
kind
of
kept
stumbling
for
teary
shouts
to
Lori,
and
so
next
week
we
have
a
plan
to
move
forward.
D
Second,
one
is
the
code
review
so
feeling
a
bit
more
like
a
negotiation,
sometimes
rather
than
just
a
code
of
you
and
it's
just
I'm,
just
kind
of
like
it's
an
interesting
feeling
throughout
my
entire
development
career,
I've
optimized
for
delivering
features
as
soon
as
possible
and
with
the
code
reviews.
Here,
that's
not
quite
the
same
as
this
more
about
the
actual
quality
of
the
code
versus
the
features
that
you're
delivering
so
I'm,
just
having
to
change
a
little
bit
and
grow
a
little
bit
as
a
developer.
D
E
E
All
the
movers
are
lifting
heavy
things
I'm,
just
like
moving
boxes
around
in
the
next
day,
I
was
like
you
feel
my
arms,
my
neck
hurts
and
whatever
so
just
it's
fine
and
just
being
a
baby,
and
the
second
one
is
I
was
working
on
sort
of
like
planning
and
I
was
hoping
to
get
to
this
MVC
issue
for
nuget,
which
would
be
like
came
up
in
the
issue.
Some
user
suggesting
just
have
a
feed
of
the
NuGet
packages.
It
doesn't
necessarily
matter
as
much
push
and
pull
I
really
like
that
idea.
E
A
Cool
yeah
I
mean
I,
think
no
one
likes
moving
so
I
think
you're,
okay
to
feel
like
a
baby
there
at
least
I
probably
would
too
still
recovering.
This
is
mine
now
still
recovering
from
whatever
I've
been
ill
with,
which
has
been
on
that
phone
he's
been
feeling
pretty
tired,
but
I
hope
it
goes
away
soon.
A
We
were
working
out
if
there's
a
way
for
us
to
satisfy
the
need
we
had
in
the
particular
area
they
candidate
and
we
couldn't
so
that
is
the
big
bummer
I
think
it's
the
technical
terminology,
so
I
had
been
continuing
the
interview
anyway,
but
it's
a
big
shame
because
they
came
to
that
had
a
lot
of
positive
feedback
so
and
then
our
bug
count
is
going
up.
I
think
we
were
just
discussing
this
in
the
meeting
before
I
think
that's
more
of
a
discovery
situation,
then
a
hey!
Our
code
is
getting
worse.
A
Somehow,
even
though
there's
only
two
people
actively
writing
code
in
our
area.
Three
people,
if
you
can't
Nick
as
well,
which
we
should
I,
should
cannot
make
clinic.
So
it's
more
about
a
discovery
person
survival
hasa
identifying
that
you're
aware
there
are
issues
in
our
code
and
and
sort
of
discovery
like
you
mention.
It
just
means
we're
going
to
need
to
look
at
how
s
ellos
and
make
sure
we're
actually
prioritizing
those
sufficiently.
A
F
F
Think
I'm
next,
so
I
just
had
one
point:
I
just
wanted
to
call
this
out.
I've
been
feeling
super
busy
this
week
and
a
little
bit
behind
I
think
Monday
probably
had
something
to
do
with
that,
but
Friday's
typically
my
ketchup
day,
so
no
worries
feeling
pretty
good
about
wrapping
up
all
my
open
dues,
but
I
know
there's
quite
a
few
pay.
Some
of
those
are
package
related,
so
just
want
to
call
that
out
that
hopefully
I'll
have
those
wrapped
up
today,
so
all
good
over
to
want
what
went
well
and
Gigi
I
think
Dan.
F
Awesome
so
what
went
well
thanks,
Dan,
so
over
commit,
and
my
first
feature
change.
Mr-
was
merged
if
you're
not
using
over
commit
yet
I
recommend
you
give
it
a
try
out
so
awesome,
Thank,
You
Gigi
for
that
and
then
double
thumbs
up
from
Dan
over
there,
which
is
good,
very
positive,
to
have
two
thumbs
up
next
one
one
on
one
help
unblock
progress
with
a
metrics
issue.
That
sounds
pretty
great
too
and
then
last
point
from
Gigi
it
looks
like.
Is
he
got
a
ticket
to
the
components
comp
next
Tuesday?
That
sounds
pretty
awesome.
F
B
This
week,
some
things
that
went
well
I
started
submitting
some
em
ours
and
to
review
for
Conan,
so
I
finally
have
gotten
over
that
hump
of
sort
of
you
know
being
afraid
of
splitting
things
up
and
and
just
kind
of
doing
it
and,
like
we'll
see
what
happens
and
fix
things
along
the
way
as
MMR's
going
to
review,
and
then
I
also
had
a
really
great
sync
with
Nick.
B
Yesterday
I'm
we
had
a
really
good
conversation
just
about
how
the
front
end
and
the
back
end
kind
of
talk
together
and
I
feel
like
I,
have
a
better
understanding
of
how
to
provide
the
front
end
with
what
it
needs
versus
kind
of
my
mentality
of
like
how
could
the
front
end
know
what
to
do
if
it
hasn't
written
the
back
end
or
or
you
know,
I'm
writing
the
back
end.
How
could
I
not
write
the
front
end,
which
is
my
old,
full
stack
mentality.
C
All
right,
I'll
go
next
Tim
and
I
had
a
couple
great
syncs.
This
week,
I
was
a
little
worried
at
the
beginning
of
the
week.
In
terms
of
you
know,
what
is
the
future
of
package?
Look
like
you
know
how
do
I
start
putting
designs
together
got
a
couple.
Great
synchronous
conversations
tended
a
ton
of
work
around
putting
things
together,
so
I'm,
I'm,
excited
and
I
feel
like
I
feel
confident
in
what's
coming
next
I
was
exciting.
Next
up
is
Nick.
D
Okay,
so
first
point
is
my
package
details
page
where
I've
converted
that
interview
Jes
has
been
merged.
That's
my
biggest
mr
today
there's
quite
a
lot
of
changes
in
there.
Quite
a
lot
of
work.
So
I'm
really
happy
that
that
cut
over
the
line
of
yeah
it
was
pretty
epic,
so
that
puts
us
in
a
good
state
for
the
next
point,
which
is
the
more
current
an
you
I
work
can
now
take
place
on
that
page
I'm.
D
Tim
was
watching
and
it's
good
knowing
how
we
can
work
or
having
a
better
idea
of
how
the
front
in
the
back
end
are
gonna,
be
able
to
work
moving
forward
in
package.
My
bad,
we
should
have
probably
should
have
recorded
it,
but
it
was
completely
unstructured.
I
didn't
like
Oh
sis.
No,
it
was
just
a
conversation
more
than
anything
and
yeah.
Probably
my
bad
they're.
E
Cool
thanks
for
saying,
Tim,
listen
because
I
think
that's
a
perfect
summary
of
what
I
was
doing.
A
lot
of
it
was
over
my
head,
so
I
really
was
just
trying
to
you
know
glean
what
I
could
but
I.
Actually
I
was
one
of
my
positive
points,
because
I
think
us
using
alright
the
API
that
we
built
to
power.
The
front
end
is
really
powerful
and
I
think.
E
Maybe
we
could
get
some
of
the
additional
metadata
in
the
container
registry
and
and
package
registry
tables
now,
because
we
do
have
things
like
a
projects
API
that
maybe
we
could
use
or
pipeline's
API,
so
I'm
crossing
my
fingers
that
that's
gonna
be
something
else
we
could
do
and
Ian
and
I
worked
on
a
plan
for
what
we
will
work
on
over
this
next
several
milestones,
so
we
ended
up
fleshing
out
four
key
epochs,
putting
things
into
milestones.
It's
a
high-level
plan.
It's
not
totally,
you
know,
obviously
hasn't
been
shared
with
everyone
team.
E
Yet
but
I'm
looking
forward
to
getting
in
front
of
your
eyes
and
getting
feedback,
see
what's
missing
and
making
the
timelines
a
little
bit
more
realistic,
Jason.
Actually,
I
should
say
mark
has
been
doing
some
reviews
of
people's
strategy
and
Direction
pages
with
C
ICD
I
think
he
did
it
with
secure
sort
of
choosing
the
high
priority
stages,
but
something
that's
come
out
of
that
is
Jason's
been
rewriting
our
CI
CD
vision
and
direction
pages,
and
we
switched
the
templates
from
using
North
Stars
to
using
themes.
And
then
the
themes
have
a
lot
more
details.
E
We
talked
about
what
we're
not
doing
so
just
a
lot
more
thought
has
went
into
how
those
pages
are
updated
and
and
how
we
talk
about
these
things,
and
it's
been
very
helpful
for
me
to
hear
and
also
awesome,
to
see,
Jason
talk
about
all
these
things
and
and
what
the
future
is
in
three
three
years
down
the
road.
So
it's
pretty.
A
I
feel
like
this
week,
ish
we've
made
some
really
good
progress
and
solving
steps
forward
in
our
process.
That
was
some
good
conversation
we
were
having
in
one
of
our
team
issues
on
issue
waiting
and
so
I've
updated
our
team
page
on
Google
AB
on
the
actual
public
website.
So
you
could
actually
look
at
that
process.
I
showed
the
Mr
in
our
channel,
so
I'm
always
expecting
people
to
give
feedback
if
they
have
changes
or
suggestions,
but
I
really
appreciate
working
through
some
of
these
and
improving
the
next
one.
A
I've
felt
like
I've,
been
pretty
productive
this
week,
which
is
nice
back
to
hiring
again
hair
hiring
again,
although
I
said
that
last
time
which
I
you
know
I
like
hiring
so
it's
fun
and
and
I'm
sort
of
having
an
improving
understanding
of
the
organization
and
how
I
get
to
do
what
I
do
so,
that's
nice
and
then
working
with
everyone
goals
is
also
eating,
building
results
and
that's
a
having
lots
of
one-on-one
chats
with
people
and
then
just
other
conversations
in
the
channel
and
helping
people.
How
long
this
else
I
love
about
the
job.
F
Thanks
dad,
so
just
a
couple
things
from
my
side:
niko
starts
on
Monday
Nico
will
be
our
second
front-end
engineer,
so
that
is
super
exciting.
Just
want
to
call
that
up,
I
did
and
then
also
my
other
went
well
was
Nick
and
I
had
some
really
really
really
great
shots
this
week
about
12,
4,
deliverables
and
I.
Think
those
went
really
well
Nick.
So
thanks
so
much
for
those
talks,
I
think
we
had
some
great
outcomes
and
yes
day
and
I
was
literally
just
thinking
the
same
thing.
F
F
F
A
B
Yes,
I
was
curious
with
the
hiring
I.
Don't
know.
If
that's
something
we
talk
about
here,
but
so
you
mentioned
that
one
of
the
candidates
was
dropped
out
was
that
is
that
the
person
that
was
gonna
make
me
start
knocked
over.
That.
A
F
A
F
Yeah
sure
are
you
referring
to
like
how
we're
gonna
kind
of
distribute
the
work
a
little
bit,
yeah,
okay,
so
yeah.
So
what
we're
kind
of?
Where
were
thinking?
What
Dan's
referring
to
is,
as
Nikko
comes
on
board,
we'll
spend
some
time
on
boarding
him
obviously,
and
ask
Nick
to
spend
a
little
bit
of
time,
helping
Nikko
get
up
to
speed
and
kind
of
transferring
some
of
that
domain
knowledge.
And
then,
since
we're
we're
kind
of
a
little
light
on
the
front
inside
right
now
inside
a
package.
F
What
we're
thinking
is
we
would
ask
Nick
to
spend
some
of
his
time,
helping
Nikko
get
up
to
speed
and
answering
any
questions
that
our
package
related
and
then
we'd
also
give
Nick
an
opportunity
to
step
out
a
little
bit
and
help
with
some
of
the
larger
get
lapped
front.
End
issues
that
are
going
on
right
now,
like
shared
components
in
any
of
those
efforts.
That
would
benefit
the
entire
front
end,
while
he's
helping
out
with
Niko
that's
kind
of
where
kind
of
what
we're
thinking
I.
F
A
No
worries,
thank
you.
Thank
you.
That's
great.
We're
really
excited
I,
often
wonder
whether
I've
had
this
experience
recently,
where
I
interviewed
with
someone
said
I've
been
watching
your
team
meetings
because
I
knew
which
team
it
was
and
I've
been
on
Ritchie,
it's
the
truth.
I
love
transparency
is
one
of
my
like
big
values
that
have
I've
always
had
very
high
on
my
list,
but
the
hug.
Someone
said
that
interview
I'm
like
okay.
It
feels
weird
now
yeah,
it's
totally
not
it's
great.
It's
like
and
I
tell
people
to
go.
Look
at
the
meetings.