►
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
B
So
our
when
someone
wants
to
use
this,
so
we
will
need
a
fork
of
the
boss
release
most
probably
or.
D
So
yeah
there
was
a
lot
of
confusion
about
it,
so
it.
D
Like
three
four
files,
because
the
for
the
AWS
CPI,
the
goaling
CPI
and
that
kind
of
stuff,
so
everything
that's
awf,
Ruby
Dash
3.1
package
and
we
just
renamed
it
to
AWS
Ruby
3.1
package
and
then
we
can
and
from
then
on
out.
We
can
just
do
easily
render
our
every
time
when
there
is
a
new
new
update.
A
D
A
Yeah
I
think
he
was
confused
like
say
they.
What
was
like
the
wash
packages
will
be
will
be
released
like
the
the
question
is,
is
the
package
is
the
the
package
name
somewhere
in
the
in
here
we
have
packages.
So
if
we
have
this
package,
does
this
have
any
reference
to
the
package
name
because
it
does
put
in
the
compile
and
right.
A
D
B
A
A
B
D
B
A
A
Yeah
try
to
actually
partner
it
with
I,
don't
know
a
CPI
or
something
right.
So
we
know
if
there's
other
things
that
are
hard
coded,
that
we
didn't
foresee
like.
If
there's
something
in
the
package
that
hardcodes
the
Bots.
D
A
C
A
A
Yes,
yeah
I
think
that
that
is
not
a
wasted
effort
right
and
I'm
and
then,
if
it
doesn't
work
right,
then
we
you
can
I,
don't
know,
raise
an
issue
with
the
CLI
and
yeah
fix
it.
But
then
you
don't
have
to
wait
for
like
cutting
like
we
don't
have
to
wait
for
like
creating
a
more
CLI
release
before
we
we're
gonna
take
start
working
on
the
next
step.
Basically
that
yeah.
A
A
Okay,
but
yeah.
A
B
D
B
D
And
he
fixed
most
of
Brian's
stuff.
C
D
You
know
constantly
ask
for
what
is
the
the
speed
and
then
yeah
that
it
was
provided
today
a
few
days
ago,
because
one
day
I
went
through
Monday
and
Tuesday
I
went
through
all
the
issues
and
closed
things
and.
A
B
D
A
A
D
C
A
A
A
Okay,
yeah,
but
actually
I
looked
at
the
code,
so
I'm
gonna
break
this
as
well,
because.
B
D
Still
for
but
someone
else
needs
to
review
it,
so
we
can
so
we
can
merge
it.
A
Like
was
this,
for
this
is
for
the
issue
that
was
raised
by
yeah
yeah.
D
This
is
the
using
openssl
instead
of
the
other,
the
the
airlift
or
something
I
don't
know.
C
D
C
D
Okay,
it
just
needs
to
be
reviewed,
the
code
needs
to
be
reviewed
and
the.
A
C
D
It's
basically
loading
now
that
both
libraries
and
there
seems
to
be
the
solution
that
RC
slot
Community
is
saying:
I
looked
it
up,
so
I
see
these
kind
of
suggestions
all
over
the
place
in
the
community
boards.
So.
D
D
B
D
D
Yeah,
it
was
not
really
necessary
because
I
would
just
cherry
pick
it
back,
but
apparently
he
made
a.
A
C
B
D
This
is
the
syslog
thing
that
needs
to
be.
C
B
B
But
if
you
go
to
the
bottom
somewhere
else,
I
was
lost
working
in
this
at
the
beginning
of
the
week.
B
Yeah
I
was
probably
so
this
one.
Oh.
D
C
D
A
D
B
A
So
why
I'm
asking
is
because
here
the
thing
is
that
the
RCs
or
the
Sith
log
release
depends
on
these
RCS.
Look
that
lives
on
the
stem
cell
right.
It
doesn't
chip
it's
and
we're
changing
the
config
and
the
we
are
not
actually
testing
it
in
the
stem
cell
Builder
like
we
are
not
doing
an
integration
test,
we're
just
testing
that
the
the
conflict
file
is
what
it
that
what
we
expect.
We
don't
test.
If
that
config
file
actually
functions
properly,.
C
A
A
D
D
Because
it's
really
only
on
high
workloads,
specific
network
issues
so.
B
D
D
So
I
they
are
saying
they're
they
can
verify
it.
That's
what
I
understood
from
them
that
they
tested
this
so
I
we
can.
We
can
verify
it
again.
I.
B
B
Files
don't
have
context
here,
I
need
to
leave.
Unfortunately,
okay.
A
I
basically
want
Benjamin
or
Carl
Carson
to
sign
off
on
this
or
to
at
least
be
okay.
With
this.
A
D
A
D
Its
own,
this
is
basically
overriding
its
own
stuff
right.
D
A
A
A
C
C
A
I
think
that's
the
the
blocker.
A
A
And
you
already
went
through
the
open
issues.
D
D
A
We
have
our
cities
it'll,
just
sprinkle,
some
RFC
on
this.