►
From YouTube: 2019-02-12 Rook Community 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
Okay,
the
recording
has
started
so
this
is
the
February
12th
2019
rook
community
meeting
and
we'll
go
ahead
and
start
by
taking
a
quick
look
at
any
of
the
0.9
patch
releases
that
we
have
to
do.
I,
don't
know
of
anything,
that's
upcoming
there.
It
looks
like
on
the
board.
All
we
have
is
this
Kassandra
wrong
mount
point
issues
still
there
that
from
my
last
recollection
of
it
is
that
it
had
backward
compatibility
or
migration
concerns
and
I.
A
Don't
think
that
there
was
a
solution
that
Yanis
was
able
to
spend
time
on
yet
because
of
his
work
on
his
thesis,
I
think
so
I
think
that's
still
in
progress,
they're
still
working
on
it.
I
don't
know
depending
on
you
know,
when
that's
the
solution
for
that
is
found.
Maybe
we
won't
back
port,
it
I'm,
not
sure,
but
we'll
have
to
see.
What's
I,
don't
think,
there's
any
progress
on
that
one.
Did
you
already
think
about
that?
Travis?
No.
B
A
Cool
yeah
we'll
see
how
that
goes.
Then.
Ok,
let's
go
ahead
and
take
a
look
at
the
1.0
milestone
and
so
we're
looking
at
the
milestone
first
here
and
scrolling
through
everything
yeah.
You
know
we
have
a
somewhat
not
quite
as
much
as
4,
0.9,
I
think,
but
as
somewhat
aggressive
attempt
at
putting
a
lot
of
issues
into
the
milestone
here.
So
we
see
that
there
are
still
a
fair
amount
that
don't
have
assignees
or
owners
for
the
issues.
Yet
so
you
know,
hopefully,
as
the
milestone
continues,
where
we're
targeting
sort
of
quarterly
release
cadence.
A
So
sometime
around
the
you
know,
middle
to
end
of
March
is
when
we'd
be
targeting,
so
so
through
that
process,
we're
hoping
that
you
know
more.
If
these
issues
we'll
be
able
to
pick
up
owners
as
either
you
know,
other
contributors
come
to
the
project
or
contributors
that
are
already
working
on
issues
here
finish
these
and
move
on
to
the
next
ones.
So
let's
take
a
look
at
the
board
as
well.
I.
B
A
A
Okay,
so
are
there
any
any
of
these
issues
in
progress
here?
They
we
want
to
be
discussing
I,
think
they
I've
seen
a
whole
lot
of
you
know
emails
and
discussions
on
pull,
requests
and
stuff
that
on
more
issues
in
just
these,
so
it
seems
like
we're
yeah.
We
don't
have
all
the
issues
in
the
right
status
right
now,.
B
A
C
A
That
sounds
good.
One
thing
that
I've
been
doing
pretty
diligently
is
that
when
an
issue
gets
resolved
or
closed,
you
know
with
a
commit
to
master
that
will
be
in
the
1.0
release.
I've
been
making
sure
that
all
of
those
gets
the
one
auto
milestone
assigned
to
them
and
there's
so
there's
been
a
fair
amount
of
that
have
come
through
that
we've
closed,
but
we
haven't
put
into
the
milestone.
A
B
A
A
No,
probably
not
that's
again,
certainly
not
as
entertaining
as
a
Nintendo.
Okay.
So
there's
a
topic
on
here
for
the
rookie,
Oh
redesign
and
dock
site
changes.
Well,
it
looks
like
Alexander
is
now
on
the
call
Alexander.
Have
you
gotten
much
of
a
chance
to
sync
up
with
the
efforts
that
Chris
is,
is
putting
into
redesigning
the
rook
that
IO
site.
A
Know
that
at
least
we
have
you
know
we
have
where
communication
has
been
open
there
at
least
any
shared
with
you,
the
your
the
designs
and
some
of
the
things
there
yeah.
So
we've
started
with
that,
at
least.
So
what
are
you
thinking
right
now,
Alex
in
terms
of
the
static
generator,
and
you
know
what
changes
have
been
made.
You
know
Michael
Gough
had
made
some
changes
recently,
too.
A
You
know
you
make
the
rubygems
that
the
site
depends
on
just
be
github
pages,
so
we
don't
have
to
continuously
track.
You
know
our
own
dependencies.
Do
you
think
that
that's
a
good
approach
for
you
know
minimizing
the
maintenance
burden
of
keeping
things
up
to
date,
or
are
you
pretty
sold
on
the
Hugo
static
generator
or
what
are
your
thoughts
on
that?
Well,.
D
D
D
D
A
All
right,
cool
yeah,
so
so
I
think
that
we'll
continue
following
up
on
that,
though
we're
you
know
the
the
design
changes
that,
to
you
know,
update
the
rocket
at
I/o
sites
and
streamline
some
of
the
documentation
will
continue
following
up
on
making
sure
that
that's
in
agreement
in
alignment
with
you
know
on
the
technical
side
of
being
able
to
generate
the
site
using
a
static
page
generator
from
you
know,
from
the
source
documentation.
So
we'll
have
to
keep
following
up
on
that.
So.
B
A
Anything
excited
about
it,
yeah
Chris
Chris
said
had
had
a
you
know,
some
design,
sketch
project
stuff
that
he
had
started,
putting
together
and
I
believe
that
you
had
seen
a
link
to
that
from
an
email
thread
that
you
Alex
and
I
were
discussing
it.
You
know
I,
don't
know
where
I
will
have
to
follow
up
and
see
where
he
is
on
it
right
now,
but
you
know
the
design
changes
I
think
well.
It
at
some
point
soon
should
be
something
that
we
can
all
comment
on.
Yeah.
B
A
What
we'll
follow
up
to
just
make
sure
that
you
know
good
sign
changes
that
the
Chris
would
like
to
see
are
fully
compatible.
You
know
with
on
the
technical
side
what
we
can,
what
we
can
do
to
generate
the
site
and
make
sure
that
you
know
ever
all
the
effort
from
both
sides
there
on
the
technical
side
of
the
design
side
are
in
alignment.
A
B
One
question
I
have:
is
the
yesterday
the
dynamic
bucket
a
bucket
provisioning
discussion,
I
had
to
drop
off
that
call
early
and
it
sounds
like
it
ended
up
in
a
different
place
where
then,
when
I
dropped
off?
As
far
as
going
for
a
general
solution
again,
could
we
just
review
that
design
for
the
group
briefly
or
word
that
yeah.