►
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
B
First
item
is
issue
issue
402
regarding
refactoring,
so
January
has
any
ideas
of
venereal
disease
year.
Ecosystem
I.
Think
Iran
is
not
to
tell
you
about
to
talk
about
that
right
now.
As
he's
doing
something
else,
it
seems
to
be
in
good
shape
to
managers
that
have
been
serving
a
couple
things
to
get
last
opinions
on
that
topic
gets
to
say:
hey
I,.
C
Yeah
so
LuAnn
basically
worked
on
the
generation.
I
made
a
proposal
for
how
the
ideas
should
be
generated
in
the
future.
There
haven't
been
any
comments
for
a
while,
now
and
I
think
we
can
move
on
with
this,
and
the
deadline
is
basically
in
five
days
and
nobody
objected
until
now,
so
until
nobody
objects
until
then,.
D
I
think
maybe
in
just
you
were
like
a
final
thing.
You
can
just
make
them
again
for
in
case
they
missed
it
last
time,
but
a
great
address
like
we've.
It's
been
open
for
a
while
now
and
we
haven't
received
anything
different
and
it
feels
like
we're
all
in
agreement
just
when
I
do
I
that
maybe
went
to
tie
thickness,
maybe
as
like
a
first
good
first
contribution
to
maybe
someone
I
was
not
yet
on
the
working
group
that
they
can
try
and
get
involved.
So.
D
B
B
So,
let's
move
to
the
second
item
of
our
agenda
today,
which
is
item
three
five,
nine.
So
as
a
statute,
this
is
going
pretty
well
currently
for
the
setting
up
of
the
of
the
repository.
So
we
are
mourning
the
linearity
that
either
in
their
own
repository
of
this
seems
too
busy.
This
turned
out
other
communities.
E
So
actually
I.
So
there
are
two
ways:
actually
we
could
you
know,
get
the
repo
P
or
you
know,
pushing
back
to
the
github
thing
of
working
the
CIB
step
of
synchronization.
We
could
either
use
the
books
or
use
Travis
is
Travis
only
for
doing
that,
so
I
don't
know
which
one
would
be
better,
but
Travis
would
be
easier
to
set
up
I
guess,
I.
B
C
D
Think
I
tried
to
bring
in
a
couple
times
so
whether
I
think
we
can.
We
just
need
to
review
them
like
see
if
the
is
are
compliant
with
what
we
were
releasing
and
I
guess
we
can
just
march
down,
but
right
and
probably
review
will
be
them
also
with
micro
is
also
involved
in
the
notes:
North
Korea
security.
So
maybe
you
can
just
to
quick
review
with
him.
I
I.
G
G
C
C
D
But
Congress
it's
a
bit
points
like,
let's
see
like,
hopefully
we're
not
going
to
have
many
node
core
security
releases,
but
if
we
do
we
can
it's
a
good
point
to
kind
of
just
too
retro
later
on,
like
see.
If
we
get
a
lot
of
this,
so
you
know
still
pr's
about
it
and
if
it
becomes
like
a
in
ordinary
things,
then
we
can
should
probably
see
how
to
fix
it.
Let's
get
it
marks
really
quickly.
D
We
usually
do
but
even
be
ours
for
for
the
ecosystem
we
usually
kind
of
like
even
if
comes
some
people
approved
it
kind
of
a
little
bit
more
like
the
the
CBS
s
core,
maybe
settings
or
like
missing
stuff
so
like
just
for
other
people
under
still
wait.
I
think
not
for
like
there's
not
a
predetermined
time
that
we
wait
for
like
a
week
or
two
before
March,
but
it's
to
get
more
eyeballs
at
it.
What
we
get.
D
I
think
so
because
we
have
also
like
a
reporting
tool
that
creates
it
out
of
when
programmatic
code
ooh
generally,
the
format
is
not
something
that
you
do
manually
unless
you're
not
using
the
pool,
but
still
it
is
to
me
some
stuff,
maybe
just
the
data
or
like
you
maybe
created
it
before
it
was
disclosed
so
like
the
date
would
be
like
the
epic
time
and
stuff
like
that.
So
you
know
it
happens
when
we
make
like
kind
of
mistakes
like
that.
So
just
generally,
we
just
wait
it
out
for
a
little
bit.
Okay,.