►
From YouTube: 2021-03-17 Code Review Group Weekly
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
Thanks
kai
yeah,
I
added
a
point
there.
It's
not,
I
think,
terribly
urgent,
but
it's
something
that
I've
been
thinking
about
and
I
haven't
been
doing
an
amazing
job
of
contributing
to
the
iteration
retrospectives.
A
It
usually
takes
me
a
bit
to
go
back
and
post
some
comments
there,
but
I
noticed
that
at
least
for
the
first
three.
The
status
for
me
is
not
clear
and
also
in
a
few
of
them.
The
engagement
doesn't
seem
very.
B
A
Or
what
I
would
expect
so
I
just
wanted
to
know.
I
mean
in
this
case
it
was
also
for
for
michelle,
but
you're
you're
here
andre.
So
I
also
wanted
to
hear
what
your
thoughts
on
it
and
what
we
can
do
to
help.
C
Yeah,
that's
a
great
question,
so
one
of
the
things
we've
been
trying
to
do
is
to
do
more
of
these,
where
I
think
we
have
been
failing
at
is
wrapping
them
up
and
we
usually
open
them
without
a
deadline.
We
just
opened
them
like
at
eterna
and
ping
people
to
participate.
C
I
think
maybe
it's
I
don't
know
if
it's
something
that
you
as
a
team
can
help
except
participating
on
them.
Of
course,
it's
more
like
what
can
we
change
in
ways
to
make
it
more
visible
about
right?
We
have
a
deadline
there.
We
need
to
weigh
in
after
a
couple
weeks
give
time
for
everyone
at
least
two
weeks
to
account
for
pto
and
stuff,
but
like
have
shorter
deadlines,
I
think,
or
have
a
deadline
would
be
nice
just
so
they
have
people
understand
that
they're
expected
to
participate
within
a
time
frame.
C
I
think
that's
mostly
what
I've
got,
what
I've
gathered
over
the
ones
that
we
have
created
in
the
past.
Anyone
has
any
any
thoughts
on
it.
A
Yeah
my
my
question
was
mostly
like
what
what
are
we
planning
is?
Is
there
anything
that
we're
planning
to
do
with
the
information
there
and
right
I
mean
you,
you
already
answered
a
little
bit
ma
the
engagement
question.
C
A
Yeah
yeah,
I
think
that's
valid
right.
So,
even
if
we
at
a
certain
point,
we
have
to
close
the
retrospective
and
if,
if
we
that's
the
outcome
and
saying
like
we
recognize
that
there
are
like
everything
is
perfect
or
that
there
are
some
things
to
improve,
but
they're
not
actionable
at
the
moment
or
something
for
us
to
monitor.
I
think
that's
a
valid
outcome
as
well.
C
Yeah,
but
thanks
for
raising
this,
I
think
we
need
to
to
get
better
at
closing
them
and
and
because,
if
we,
if
we
close
them
more
often,
then
we'll
have
a
moment
in
time
to
share
the
conclusions
until
then,
it's
just
the
people
participating
in
them.
Reading
the
other
comments
and
getting
the
lessons
there
and
trying
to
absorb
them
in
their
in
the
day-to-day
lives,
but
all
right,
I
think
I'll,
take
a
a
note
to
look
into
through
each
one
of
those
and
because
they
do
have
due
dates.
C
So
I
see
that,
for
example,
the
reviewers
one
has
a
due
date
for
january
18,
which
is
passed
right
yeah,
it's
fast,
so
it
feels
like
we
definitely
take
an
action
on
that
go
through
them
see
if
they
have
enough
juice,
summarize
get
the
highlights
and
share
it
here
on
the
weekly.
I
guess
that
would
be
a
good
point,
a
good
way
to
circulate
that.
So,
thanks
for
coming
out.
C
Okay
in
separating
the
issues,
so
what
you're
suggesting
that?
Sometimes
we
might
need
to
separate
the
actual
issue
right,
have
an
issue
for
documentation,
correct,
okay,
when
would
be
the
best
time
to
assess
that
so
on
with
quality,
we're
the
one
one
way
we
do
that,
so
they
also
have
to
go
through
the
assigned
deliverables.
B
B
C
C
I
can't
type
today
cool
any
other
points
we'd
like
to
discuss.
D
D
Cool
will
everyone
enjoy
the
rest
of
your
day.
Have
a
good
week,
we'll
we'll
see
you
on
the
internet
thanks
everyone.