►
From YouTube: 2020-11-04 meeting
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
B
B
A
A
B
Yeah,
so
we
yeah,
so
there
there's
basically
like
how
many
of
us
are
on
the
team.
Now
about
four
or
five
of
us
on
the
team
and
every
we
take
two
weeks
and
then
we
just
rotate
through
all
of
us.
B
B
B
He
was
yeah,
he's
a
great
engineer,
but
so
there's
five
of
us
now
until
he
leaves
then
there'll
be
four
of
us.
So
wait
not
for
your
total.
A
B
Actually,
six
people,
because
there's
one
person
for
the
go
portion
right
now,
but
yeah
there's
there's
a
lot
more
for,
like
the
agent,
the
other
agents
like
java
and
javascript
and
python
and
ruby
and
all
of
those
and
then
there's
a
lot
more
for.
A
A
A
C
B
A
C
A
We
have,
I
actually
have
a
slack
tag
in
mailchimp
slack
called
bob
the
unlucky,
because
I
had
like
a
disproportionate
amount
of
overnight
pages
on
my
team
is
like
I
had.
I
think
I
had
something
like
50
or
60
in
a
year
and
the
next
highest
percent,
like
four
it
was
like
every
time
I
went
on
class.
Something
bad
happened,
it
was,
it
was
like
you
couldn't.
A
What
I
said
people
didn't
seem
to
take
too
kindly
to
that
all
right.
Well,
I
guess
we
can
get
going
with
our
discussion
today.
So
the
one
thing
that
I
needed
to
make
sure
that
I
talked
about
today
was
the
maintainers
are
doing
a
user
researching
and
dog
fooding
guide.
So
there
I
opened
an
issue
for
this.
It
is,
let
me
pull
it
up.
A
206.
and
so
issue
number
206
talks
about
dog,
fooding
and
end
user
research.
It's
basically
a
google
doc
that
somebody
can
fill
out
that
talks
about
like
going
through
a
very,
very
basic
implementation
of
our
repository
and
like
making
notes
about
where
things
are
sticky,
we're
making
notes
about
where
things
are
difficult
to
implement
or
don't
work
or
whatever,
and
I
think
that
that
would
be
use
useful
feedback
to
get
from
somebody.
And
this
would
be
an
excellent
thing
to
get
from
my
new
contributor.
A
A
The
other
things
that
I
had
to
talk
about
riddick
opened
up
pr
for
the
otop
exporter.
It's
working
through
last
minute
things
with
code
coverage
amber.
I
don't
know
how
you,
how
strongly
you
feel
about
this
decreasing
and
increasing
code
coverage
as
a
blocker
for
a
pr.
I
have
like
sort
of
mixed
feelings
about
this.
My
positive
feelings
are
like
if
we
can
avoid
reducing
code
coverage
during
pr
mergers.
A
B
I
like
that,
the
code
coverage
is
there.
Maybe
we
can
think
about
if
it
decreases
it
by
a
certain
percentage.
It's
okay,
but
I
think
yeah
I
mean
if
it
decreases.
That
means
there
hasn't
been
enough
tests.
So
that's
also
a
concern
because
we
want
to
make
things
show.
Things
are
well
tested
before
they
go
in.
So
I
think
it's
a
fine
line
there
like.
Maybe
you
can
have
some
percentage
metric
where
you
say.
If
it's
within
this
percentage,
then
it
shouldn't
be
a
blocker,
but.
A
Yeah-
and
I
also
think
at
least
from
my
perspective-
it
also
depends
on
the
pr
too,
like
some
things
are
inherently
a
lot
more
difficult
to
test.
I
don't
think
this.
This
particular
pr
is
incredibly
difficult
to
test,
but
maybe
I
don't
know,
maybe
we
should
come
up
with
the
long-term
strategy
for
that.
I'm
gonna
noodle
on
that.
Maybe
we
can
talk
about
that
again
next
week
when
we
have
more
people
here,
because
I.
A
Something
that's
worth
bringing
up
so
that
we
have
like
a
common
convention
there
because,
like
it's
like
this
decreases
by
two
and
a
half
percent,
this
decreases
code
coverage
by
two
and
a
half
percent.
Is
that
a
big
deal
not
right
now?
But
then,
if
you
do
that
for
every
pr,
then
it
gets
to
be
like
an
exponential
right,
50
code
coverage
sort
of
deal
rather
than
where
you
know
where
we
are.
We've
worked
so
hard.
A
A
Let
please
ask
questions
if
you
have
them
so
that
we
can
make
sure
that
we
get
enough
code
coverage,
because
that
I'm
not
certain
if
this
is
a,
I
don't
know
how
to
write
the
write.
The
other
test
code,
yeah
sure
thing.
Really,
I'm
not
sure.
If
it's,
I
don't
know
how
to
write
these
tests,
or
I
don't
think
that
they're
pertinent
to
the
code
that
I
wrote
or
whatever.
So
that's
that's
good.
A
A
A
A
Yeah
they're,
they
seem
to
be
neat
tools,
it's
just
like.
So
now
we
have
tests
yeah
unit
and
integration
tests.
Php
stands
some
php
unit
or
what
I
mean
we
have
and
then
we're
going
they're
working
on
mutation
testing.
B
A
B
I
was
going
to
look
at
the
project
board.
Oh,
and
there
was
one
thing
I
wanted
to
say
about
the
project
board:
the
the
is
remote
function,
even
though
it's
closed,
it's
still
showing
in
that
in
the
project
board
in
the
pending
review
column,.
A
B
A
B
A
A
A
A
A
Then
people
some
if
I
know
that
you're
working
on
it,
how
about
that.
A
A
Let's
see
yes,
there
you
go
after
a
hard
refresh
sure
enough.
I
can
assign
it
to
you.
That's
really
goofy,
oh
yeah,
all
right!
Well,
it
sounds
like
you
guys
on
the
workout.
I'm
gonna
take
some
of
the
issues
too
from
the
backlog
and
try
and
prioritize
them.
It's
tough
for
me
to
do
a
lot
of
these,
because
I
don't
have
anybody
that
can
review
them
for
me,
but
maybe
that
shouldn't
preclude
me
from
working
on
them.
B
A
A
So
which
one
were
you
which
you
were
asking,
what
were
you
asking
about.
B
I
guess
I
was
wondering
about
like
I
had
been
looking
at
these.
B
A
B
B
A
C
A
Yeah,
I
think,
all
the
I
think,
all
the
rest
of
these
above
here,
like
the
I
should
probably
close
these
old,
these
old
alpha
0.2
requirements.
Those
are
just
like
dangling
things
that
we'll
probably
never
hit,
because
we're
going
to
go
probably
go
straight
to
like
a
0.6
or
like
one
of
the
more
recent
versions,
but
we
haven't
made
that
decision
yet.
So
I
I
guess
I
should
I'll
just
close
those
so
that
this
board
is
a
little
bit
clean.
The
issues
board
is
a
little
bit
cleaner.
C
A
No
problem
just
happy
to
I'm
really
thankful
that
y'all
are
helping
out
with
us,
it's
nice
to
have
some
more
people
working.
We
have
we've
had
like
momentum,
swings
up
and
down,
and
up
and
down
I'd
really
like
to
just
continue
to
push
forward,
but
sometimes
it's
tough
to
get
people
engaged,
especially
on
stuff
like
this,
so
a
cross-section
of
people
that
can
and
are
willing
to
work
on
this
is
zero.