►
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).
B
A
A
Very
simple
for
me:
I
like
spring,
because
the
winners
are
super
cold
and
windy
here
and
usually
by
February
I'm,
just
like
over
that
three-month
period
of
time
where
it's
just
gray,
skies
below
zero
most
of
the
days
and
then
with
windchill
like
we,
we
get
to
like
negative
I,
don't
know
negative
20
negative
40,
Fahrenheit,
volte,
yeah
Fahrenheit,
so
I
can
I,
don't
know,
I!
Think
that's!
A
A
D
A
B
B
It's
it's
not
like
the
it's
still,
not
the
best
part
I
think
of
the
year,
and
also
because,
like
in
in
the
summer,
there's
so
so
many
mosquitoes
here
that
and
it's
also
so
hot
that
it's
not
actually
the
best
season
and
in
spring
we
already
have
long
days,
good
weather
and
not
that
many
mosquitoes,
but
they
start
to
arrive
now
so
yeah
and
and
also
because
there's
way
less
tourists
in
the
spring
compared
to
summer.
So
we'll
see
actually
this
term
how
it
will
go
because
of
the
coated
19th
but
yeah.
D
D
So
that's
so
true
for
the
wet
the
wet
season.
I
would
say
because
it's
cooler
and
it's
more
windy
yeah
if
I
were
to
choose
one
of
the
four
seasons,
probably
spring
or
fall
to
me,
it's
from
a
perspective
off
light.
Where
can
I
go
in
these
places?
It
places
they
have
these
seasons
so
I
guess
it
depends
on
like
which,
where
or
which
country
or
which
latitude
it
is,
it
will
be
different,
so
gosh
I,
don't
know
how
to
answer
this.
C
Just
like
it
feels
like
winter
and
and
something
in
the
middle
like
a
fall
and
spring,
it's
more
like
it.
They
are
counseling
changing
like
it's.
Just
it
feels
like
when
Winker
is
small
code
and
after
winter
is
costly,
changing
and
through
to
summer
and
summer
is
very
hot
and
then
back
to
something
that
it's
constantly
changing
and
then
becomes
injured
and
I
really
don't
like
whether
I'll
step
over
it,
because
sometimes
I
need
to
wear
ball,
coasters
and
sometimes
I,
don't
and
it's
annoying.
C
A
The
first
is
an
engineering
key
reviewers
this
week.
I
think
I've
shared
this
before,
but
this
is
usually
where
Mac
or
one
of
the
cue
EMS
I
think
I
might
do
this
one
review
the
KPIs
with
Eric
and
the
rest
of
engineering
leadership.
The
main
item
to
note
next
over
mech,
usually
three
records.
A
video
for
this
and
I'll
share
that
in
the
team
channel
when
he
does.
The
the
one
thing
to
note
is
there
was
a
pretty
significant
increase
in
cost
per
pipeline
from
where
we
were
towards
the
start
of
last
week.
A
It
seem
like
there's
builds
that
are
like
going
ten
times
the
maximum
threshold
which
I
hadn't
really
seen
before
and
then
in
a
higher
frequency
of
runner
or
timeout
errors
than
we
have
encountered
previously.
So
there's
some
details
towards
the
bottom
of
the
issue.
Really.
The
top
artists,
like
me,
just
like
mentally,
like
going
through
what
I'm
fighting,
but
the
bottom
has
some
good
summary
on
it
is
I,
asked
Amash
and
Camille
if
they're
aware
anything
that
would
have
caused
those
those
and
we'll
see
what
we
hear
back
last
announcement
is
I.
A
A
Last
week
was
a
week
that
I
found
myself
like
really
overloaded
with
stress
in
general
and
the
days
when
I
didn't
sleep
well
or
like
check
in
with
my
with
family
I,
found
that
my
quality
of
work
suffered
and
just
my
like
my
overall
mindset
and
stress
suffered
so
later
in
the
week,
I
did
I
tried,
do
better
sleeping
and
I
thought
that
really
helped
wanted
to
reiterate
that
message
here:
football
team
as
well
any
other
doubts
once
anyone
wants
to
add
I
can
note.
That's
me.
A
Also,
now,
okay,
one
of
the
things
I
was
considering
after
last
week's
meeting
where
MEC
attended
is
rescheduling
one
team
meeting
per
month,
at
least
like
pushing
it
back
a
little
bit.
So
it's
easier
for
him
to
attend.
If
you
would
like
and
I
propose
an
hour
or
an
hour
and
a
half
later
it
Albert
and
gentian-
that's
it
seems
like
just
moving.
It
would
be
good
in
general,
gentian.
B
For
me,
it's
yeah,
it's
okay
and
it's
actually
even
better,
because
I
tend
to
kind
of
have
my
lunch
at
this
time.
Usually
no.
D
A
So
I'll
just
push
it
an
hour
later
than
for
every
meeting
and
we'll
we'll
see
how
that
new
time
works,
I
think
that'll
be
better
for
Mack
I
think
he
would
like
to
attend
once
a
month
is,
it's
kind
of
you
know,
making
it
earlier
than
or
later
than
5:00
a.m.
this
time
would
I
think
you
would
appreciate
that,
so
all
right
over
to
reviewer
roulette.
D
A
Thank
you,
I
was
just
a
little
like
I
was
looking
to
update
the
some
of
the
reviewer
roulette
issues
that
they've
kind
of
come
up
lately
and
the
one
specifically
to
use
timezone
that
came
up
in
the
retro
I
want
to
make
sure
I
was
clear
on
the
plan
or
how
we
would
use
slack,
and
thanks
for
linking
to
that
comment
in
general
was
my
summary
there
correct,
then
we'll
use
wool
like
computed,
JSON
and
publish
it
with
pages
and
then
read
that
end
by
reviewer,
Latins
they're,
bringing
it
from
the
website.
Yeah.
A
Awesome
I
will
get
the
those
two
issues
updated
for
these
note,
that
plan
somewhere.
So
but
that's
out
of
the
comment,
if
it's
and
maybe
I
missed
those
I'd
be
there.
But
thank
you
for
clarifying
for
me.
You
want
to
skip
down
to
I,
took
the
neck,
the
last
the
next
one
and
just
asked
in
slack
since
Marcus
yeah.
B
B
Oh,
yes,
and
now
that
we've
changed
that
to
put
the
gems
in
the
cash
instead
of
Hindu
artifacts
like
it's,
it's
the
best
practice
with
the
cash
is
to
catch
the
project
dependencies
and
to
use
artifacts
for
actual
things
that
are
built
from
one
job
and
that's
another
job.
It's
consuming
so
yeah
that
led
to
a
problem
when
you
had
an
empty
cache,
mostly
like
in
a
few
cases
that
could
happen
so
yeah.
B
We
fix
that
this
morning,
but
it
was
just
so
I
just
put
this
item
to
recap
that,
and
also
in
general,
to
pinpoint
that
guitar
is
Eponine
studies,
it's
quite
convoluted
and
with
like
over
the
years
that
there
have
been
new
things
added
to
like
workaround,
to
problems
that
we
had,
and
maybe
it's
a
good
time
to
like
take
a
step
back
and
see.
If
we
can
improve
that
I.
C
Now
we
are
trying
to
use
cash
key,
the
fire's
catchy
fires
to
s
s
o
cache
key.
So
every
time
when
the
dependent
block
fire
changed,
we
just
use
a
new
cache
and
I
start
to
wonder.
If
this
is
the
right
approach,
because
landings,
we
essentially
use
a
new
cache
when
there's
a
version
change-
and
this
means
we
we
are.
C
We
will
have
a
lot
of
different
caches,
for
example,
when
there
are
ten
merge,
request,
update
the
dependency
and
we
will
have
ten
cash
and
and
the
cache
will
actually
never
be
still
because
if
we
change
a
budget,
then
we
use
a
new
cache
and
if
we
don't
change
a
virgin,
then
of
course
it's
up
to
date.
So
it's
all
or
nothing
and.
C
B
So
at
one
point
another
point
about
adding
many
caches
because
of
the
the
cache
keys
that
are
now
based
on
the
by
the
truck
and
get
elevation
height,
I
I
think
that's
yeah
I.
Basically,
what
ideally
we
should?
What
I
see
is
that
we
are
consumers
of
gitlab
CI
and
that's
up
to
like
infrastructure
to
clean
caches
that
are
old
or
something
like
that.
B
I
mean
we
don't
have
we
don't
as
users
of
github
CI,
we
don't
have
a
way
to
say
caches
that
are
older
than
next
days
should
be
removed
like
yeah,
it's
an
infrastructure
concern,
but
we
could
definitely
like
get
in
touch
with
them
and
just
ask
because
I
don't
know.
What's
the
strategy
right
now
does
the
cache
is
like
regularly
cleaned
up
when
we
hit
a
volume
or
a
day,
it's
like
an
aged
I.
Don't
know!
That's
a
good
point:
we
should
probably
check
that
with
infrastructure
and.
B
B
B
B
Way
we
had
the
best
of
both
world
like
we
have
one
like
we
limit
the
number
of
caches,
because
it
would
only
update
an
on
master
and
we
could
even
use
a
fixed
key
or
not.
That's
another,
that's
another
program,
but
we
would
also
have
good
performance
because
we
wouldn't
get
the
cache
on
requests
and
most
much
requests
don't
have
that
the
de
balances,
so
that
would
be
fine
and
even
if
they
do
that,
just
in
studying
a
few
gems,
it's
not
very
long.
You
know
yeah
I,
think
that
that
would
be
idea
so
I.
B
D
D
B
B
C
A
B
D
A
A
Good
discussion,
though,
where
should
we
ask
infrastructure?
Should
we
just
infer
lounge
or
just
create
an
issue
and
ask
for
those
questions,
because
I
think
those
would
be
good
things
to
look
at?
How
can
we
identify
how
much
we're
spending
on
cash
to
see
how
it's
changing
as
we
change
our
caching
policy
and
then
are
there
best
practices
that
we
should
look
that
they
they
suggest.
A
B
B
Methods
that
are
from
sort
for
some
reason
like
impossible
or
hard
to
implement
in
go
so
we
we
still
need
this
Ruby
cycle
project
and
I
asked
that,
like
two
weeks
ago,
I
think
about
that
and
yeah
there's
no
plan
to
get
rid
of
it
in
the
near
future.
So
we
still
need
so
that's
really.
The
annoying
part
is
that
Hitler
pythons.
B
C
A
The
one
thing
I
did
walk
all
out,
I
didn't
have
this
in
the
agenda.
Is
it
does
look
like
some
of
the
changes
or
cost
per
pipeline
so
like
the
Foss
removal,
when
I
was
looking
at
the
cost
of
it,
like
I
added
a
chart
for
daily
cost
per
pipeline,
it
was
down
to
167
for
yesterday
to
close
the
day
so
that
looked
pretty
pretty
good
fingers
crossed
that
those
results
hold.