►
From YouTube: 2023-03-21 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
All
right
recording
has
started,
and
this
is
the
March
21st
2023
Rook
community
meeting.
So
we
will
jump
on
into
our
Milestones
before
going
into
the
community
topics
and
questions
as
well.
The
agenda
Doc
is
open
for
folks
that
want
to
add
any
suggestions
or
topics
that
they
want
to
explore
together.
So
in
the
zoom
chat,
I
am
dropping
a
link
to
the
agenda
doc
directly
there.
So
you
can
hop
in
there
and
add
some
ideas
if
there
are
things
that
you
all
want
to
talk
about,
that
aren't
currently
on
the
agenda.
A
All
right,
so
1.10
looks
like
in
about
a
week's
time,
maybe
a
little
bit
less
I.
Guess
no
exactly
I!
Guess
there
is
the
1.10.13
patch
release.
That's
planned,
I,
don't
recall
anything
driving
that
explicitly
or
things
that
must
go
out.
So
probably
typical,
Cadence
release
there
or
Travis.
Do
you
want
to
kind
of
catch
us
up
on?
What's
included
in
that
release,.
B
Yep
yeah,
there
are
a
few
fixes
in
it.
I
don't
recall
offhand,
which
ones,
but
if
you're
interesting
to
get
it
out
in
the
release
that
yeah
I
figured
next
week,
I
proposed
next
Tuesday
just
to
be
I,
think
that'll
be
four
weeks
since
the
previous
release,
since
1.10
is
more
stable.
Just
doing
it
less
often
at
this
point
makes
sense,
so
I
felt
right
to
wait
just
a
bit
longer
on
that.
B
B
B
A
That
sounds
very
reasonable.
All
right,
let's
hop
in
into
one
of
dot.
11.1
looks
like
that
will
take
a
bit,
though
oh
sorry
hold
on.
We
did
1.11.1
apologies
that
is
already
out.
That's
the
link
to
the
release
there.
That
was
before
we
got
that
one
out
before
the
last
community
meeting
right.
A
B
B
B
B
But
otherwise
yeah
things
are
in
progress,
yeah
I,
don't
know
what
else
to
point
out
from
this
board.
Unless
somebody
has
some
more
specific
questions.
A
Right
well,
then,
sounds
like
then
that
we
will
follow
up
on
getting
that
1.11.2
patch
release
out
today,
and
we
can
move
on
to
the
community
topics
then
so,
yes,
the
Travis
was
just
mentioning
that
that
the
slack.rook.io
link
or
site
is
is
down
and
not
functioning.
A
So
it
is
not
possible
to
currently
use
that
that
typical
link,
that
is
in
a
lot
of
places
it's
in
the
readme.
It's
in
you
know,
presentations,
we've
done
it's
all
over
the
place
right.
That
is
like
the
front
door
for
joining
our
slack
community
and
it
is
currently
down.
As
you
will
see
here,
you
get
an
application
error.
A
Okay,
so
quick
update
on
this
Travis
because
I
have
you
know,
I've
been
directly
working
on
on
debugging
this
Behavior,
so
I
might
have
a
little
bit
more
context
than
you
do,
but
it
looks
like
there
are
a
number
of
issues
that
are
blocking
that
are
that
are
we're
running
into
now,
so
well,
first
off
we
do
have
a
workaround
where
we
have
this.
You
know
a
link,
that's
generated
by
slack,
to
be
able
to
join
still
and
go
through
that
workflow.
A
The
the
one
downside
of
this
is
that
it's
the
over,
like
I,
think
there's
a
maximum
of
you
know
400
people
that
can
join
using
that
link,
so
you
do
have
to
refresh
it
over
every
so
often,
and
it's
it's
not
very
easy
to
remember
either
slack.rook.io
is
a
nice
vanity.
Url
that
you
know
is
is
easy
to
link
to
easy
to
go
to
easy
to
find,
so
that
has
been
a
very
nice
experience
having
that
up
for
discoverability
of
joining
our
community
there.
A
So
we
do
have
this
workaround,
but
it's
not
really
ideal.
So
just
a
quick
summary
of
the
issues
here
is
that
with
stock.io
it's,
it
is
actually
an
application
called
slack
in
that
is
hosted
in
Heroku
and
it
is
fairly
out
of
date.
Application
It,
Was,
Written
I,
don't
know
like
five
six
years
ago,
and
it
no
longer
has
current
maintainers
on
it.
A
So
some
things
in
the
slack
API
have
since
changed,
since
the
application
was
originally
written,
so
we're
calling
some
deprecated
apis
or
things
that
no
longer
existed
running
into
errors,
along
with
that,
it
is
using
a
very,
very
ancient
version
of
node
and-
and
that
appears
to
have
issues
with
its.
You
know-
certificate
trust
chain
that
it
that
it
that
it
uses
and
is
not
able
to
make
successfully.
A
Ssl
https
Network
calls
so
a
couple
of
different
things
that
need
to
be
tackled.
There,
I'm
working
on
updating
the
node,
runtime
and
being
able
to
successfully
do
SSL,
https
stuff,
and
then
another
contributor
is
working
on.
You
know
updating
the
logic
itself
to
call
updated
slack
apis,
so
I'm
really
hoping
for
a
resolution
to
this
this
week,
because
it
is,
it
is
definitely
blocking
growth
and
expansion
of
the
community
and
more
adopters
coming
in.
A
But
you
know
we
have
this
work
around
in
the
meantime
and
Travis.
Do
you
have
any
ideas
about
how
to
spread
this
workaround
a
little
like
for
more
visibility?
In
the
meantime?
You
know
it
would
be
nice.
If
you
know
you
could
do
DNS
to
say,
slack.io
is
actually
now
this
link
with
these
parameters
in
this
this
path.
But
you
can't
do
that.
Yeah.
B
A
C
A
Yeah,
that's
totally
that's
totally
possible
Alexander.
The
the
one
downside
is
that
you
know
that
the
slack
for
security
reasons
do
not
they
they,
these
links
expire
and
they
have
to
be
refreshed
over
time.
So
it's
I
think
it's
you
can
set
it
so
that
time
wise
it
does
not
expire,
but
a
number
of
of
invitations.
It
does
expire
and
that's
that's
400,
which
isn't
it's
I
mean
that's
a
fair
number.
That's
if
that's
probably
I,
don't
I,
don't
know
actually
I'm,
not
quite
sure
how
long
that
is.
A
But
it's
probably
like
a
couple
months
or
something
like
that
right.
So
it's
so
people
will
probably
run
into
oh.
This
doesn't
work
and
we'll
have
to
go
and
refresh
it
and
that's
kind
of
annoying
that
we'd
hit
that.
But
this
that
is
a
reasonable
suggestion
to
throw
throw
away.
You
know
simple.
You
know
static
site
that
redirects
to
this
link.
B
But
actually,
in
parallel
of
Jared,
you
and
Alvaro
I
think
investigating
this.
This
slacken
replacement.
If
we
could
just
set
that
up
Alexander
in
the
meantime
and
say:
hey,
does
this
work
and
because
we
would
want
to
do
that
if
we
don't
get
the
other
one
working
right,
I
think
that
would
be
useful.
A
You
should
because
that's
we
have
self-service
that
maintainers
get
access
to
that.
So,
if
we,
if
we
don't
have
access
to
it,
we
should
get
you
access
to
it.
There's
no
reason
not
to
have
that
so
yeah.
We
could
do
that
while
we're
along
this.
At
the
same
time,.
B
C
I
think
for
the
main
part,
either
I
will
try
to
test
it
like
just
a
simple
GitHub,
Pages
or
something
like
I
think.
The
worst
idea
I
already
had
now
was
to
why
don't
we
have
GitHub
actions
just
run
CI
every
five
minutes?
You
know
and
regenerate
the
link,
but
you
know
to
Jared
and
Travis.
One
of
you.
B
Yeah
that
also
help
with
you,
okay,
well
so
Jared,
Jared
and
Alvarez,
from
working
on
the
Seth
trying
to
get
the
Seth
link
up
for
slack
and
so
yeah,
while
they're.
Looking
on
that
perspective,
if
we
can
do
and
get
this
other
GitHub
Pages
working
with
the
redirect
I
think
that
that'd
be
a
nice
thing.
C
To
recap:
so,
as
I
said,
it
had
to
run
a
few
minutes
later,
we
had
a
customer
incident
like
I
should
have
put
it
like
the
Heroku
platformer.
Where
is
it
running
right
now
or
where
should
it
be
running
at
the
moment?.
A
Heroku,
what
do
you
mean?
What
do.
B
A
Alexander
so
yeah
dude.
That
would
be
super
helpful,
Alexander.
A
That
no,
that
the
chatter
is,
is
increasing,
like
everyone's
being
hit
by
this
just
just
last
week.
Yeah,
but
a
lot
I'd
say
that's
somewhat
constrained,
though,
because
some
people
moved
on
from
you
know
using
an
ancient
non-maintained
node.js
project,
whatever.
C
Yeah
well
I'm
not
going
to
argue
with
it
at
all.
B
A
A
C
A
That's
that's
like
yeah,
and
that
can
be
a
secondary
thing
because
I
think
it's
you
know
it's
not
gonna.
The
the
link
will
be
valid
for
probably
at.
C
A
Sounds
good
man?
Thank
you
very
much
for
being
willing
to
take
that
on
buddy
all
right.
So
that's
that
issue,
and
so,
let's
move
on
to
CI
tests
that
are
now
regularly
failing.
B
Oops
Yeah
for
the
last
couple
of
weeks
well
even
longer
than
that
we've
had
a
bunch
of
intermittent
tests
that
are
failing,
or
maybe
one
or
two
consistently
failing.
So
we
got
we're
starting
to
get
up
on
top
of
that
and
then
just
realized
that
oh
well
now
we've
got
four
consistently
failing,
but
some
of
are
the
some
of
the
same
that
were
intermittent
are
now
consistently
failing.
If
I
opened
this
issue
yesterday
to
finally
say:
okay,
here's
some
more
clues.
B
A
Sorry
I
was
on
mute,
my
bad,
but
yeah
thanks
for
capturing
that
Travis
and
following
up
on
it
so
that
we
can,
you
know,
have
reliable
tests
and
you
know
be
able
to
not
get
decent
styles
to
to
non-green
colors,
all
right
anything
Travis
to
update
on
here
for
coupon,
Amsterdam
and
collecting
ideas
for
the
talk.
I
know
you've
been
soliciting
that
a
little
bit
and
you
want
to
make
more
update
there.
B
Seen
any
responses
on
slack
so
just
if
anybody
has
input
on
what
they
like
to
hear
tubecon
and
we're
collecting
input
on
how
we
can
do
the
panel
and
hopefully
all
four
of
us
can
get
there
in
order
to
be
still
working
on
her
visa
and
all
that
so
anyway,
hope
that
all
works
out
and
we'll.
B
A
All
right
sounds
good,
Travis,
okay,
so
that
was
everything
that
was
in
the
agenda
document.
So
if
there
does
does
anybody
have
other
topics
that
I
wanted
to
bring
up
now.
A
Alrighty
well,
that
is
all
then
we
can
go
ahead
and
adjourn
for
the
week
and
you
know
we'll
follow
up
on
the
stock
invitation
thing
and
hopefully
get
something
up
and
running
soon.
There,
with
Alex's
glorious
web
development
skills.
A
C
A
Okay,
you
go
on
buddy,
you
go
on
all
right,
everybody
good
to
see
everybody
here,
we'll
see
you
on
on
slack
for
those
that
are
already
in
there
all
right
see
you
everybody
yeah.