►
From YouTube: SEM Weekly Updates 09 14 2020
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
All
right,
my
schedule,
so
I'm
not
sure
if
you
all
know
this,
but
I
have
every
other
friday
morning.
I've
been
doing
this
for
several
years
now
and
it
really
helps
with
my
so
feel,
free
to
communicate
with
me
on
friday.
So
if
I
don't
get
back
to
you
or
get
back
too
quickly,
it's
because
I'm
not
but.
A
Accomplishments
so
matt
he
won.
Matt
was
one
of
the
first
three
letters
of
the
great
gitlab
handbook,
bouncy
knight,
and
this
song
was
created
to
find
board-looking
statements
elegance
that
aren't
in
the
handbook,
and
you
get
free
gitlab
slack
for
those
statements.
Examples
are
here
like
anticipate,
believe
estimate
and
attorneys,
like
that.
A
I
did
want
to
congratulate
andre
for
being
a
parent
participant
for
a
topic
on
a
panel
on
working
and
managing
on
distributed
teams
from
an
ic
and
perspective.
It's
not
in
english,
but
you
can
understand.
But
I
definitely
wanted
to
congratulate
andre
for
representing
my
here.
A
A
Community
contributions,
so
we
are
going
down
by
just
a
little
bit
down
by
five
community
contributions
that
have
been
open
for
60
days
or
more.
Please
take
a
look
right
here
and
see
if
any
of
your
team
has
any
community
contribution.
Animals
have
been
open
for
60
days
and
if
they
do
take
a
moment
to
reach
out
to
the
community
contributor
and
see
if
they
need
support
or
if
they
are
no
longer
working
with
you,
I
create
another
chart.
A
Here's
the
precisely
dashboard
and
you
can
click
here
to
see
it,
but
you
don't
really
ever
have
to
look
at
it.
I'm
just
looking
at
it
for
myself,
but
I'm
keeping
track
of
you
know:
goals
yeah,
I'm
keeping
track
of
the
days
to
merge
in
mr
across
the
three
teams
and
there's
four
buckets
seven
days
or
less
is
yes,
we
want
eight
to
15
days.
You
know
possible
areas
of
improvement,
you
never
know.
What's
going
on,
there
could
be
exceptions
16
to
30
days
and
31
plus
days.
A
We
really
want
to
start
looking
at.
Are
these
exceptions
or
are
these
work
habits
that
can
be
improved
or
opportunities
for
iteration?
So
what
I'm
going
to
do
is
keep
track
of
it
every
week
to
see.
Obviously,
these
buckets
will
all
grow,
as
the
team
is
still
working
on
mars,
but
the
seven
days
of
us
is
really
what
we're
going
for.
We
can
take
the
eight
to
fifteen
days,
but
keep
in
mind
if
it
takes
you
two
weeks
to
do
an
amount.
A
You're
not
gonna,
have
that
kind
of
meaning,
but
I
just
want
to
give
this
to
your
attention
last
weekend.
Discussion
topic,
I
think,
about
half
of
us
responded.
Please
take
a
look
at
this
issue.
This
came
from
the
exit
criteria,
the
exit
interview,
presentation
and
it
looks
like
some
of
our
team
members
are
not
being
recognized,
so
I
do
want
to
discuss
advocating
in
different
ways
that
we
can
recognize
our
team
members.
I'd
love
for
everyone
to
contribute
to
these.
A
This
week's
discussion
item
is
pretty
good.
This
is
about
mr
coaching,
and
maybe
that's
word
for
it,
but
this
happens
to
all
of
us.
We
have
a
team
member
who
is
taking
a
very
long
time
to
work
on
mrs
regularly,
I'm
not
saying
that
random
exceptional
case,
I'm
saying
the
other
team
member
who's
constantly
taking
people
towards
the
completed.
A
Mr,
and
what
would
you
say
or
what
happened
such
team
members
to
help
coach
them
into
either
better
any
better
or
communicating
better
like
once
you
find
out
what's
wrong,
what
type
of
advice
do
you
give?
What
tips
do
you
give
them?
I
was
hoping
we
could
all
discuss
that
you
don't
have
to
use
names
but
just
share
ideas
and
how
we
post
this
with
our
team
members,
so
that
maybe
some
of
us
give
you
ideas
on
how
to
fix
this,
and
I
know
there's
different
reasons
for
this
to
occur.
A
But
if
you
can
share,
I
think
in
this
case,
when
this
happens,
maybe
it's
because
the
person
is
not
ensuring
that
the
mr
has
been
reviewed
in
a
proper
period
of
time
or
maybe
the
person
is
not
iterating.
There
could
be
multiple
reasons,
but
let's
talk
about
this
on
monday.