►
From YouTube: 2022-01-18 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
A
A
Yeah,
let's
move
on
so
it
was
on
my
brain,
though,
of
the
release,
automation,
stuff.
Although
the
automation
stuff,
I
mean
that
wasn't
what
gave
us
problems,
but
still
it
would
be
nice
on
the
I'm
not
sure
what
to
do
have
a
few
options.
A
One,
like
you
mentioned,
honora,
just
override
the
status
check
one.
It
looks
like
the
current
recommendation.
A
A
A
I
was
just
trying
that
out
and
I
mean
there's
you
always
have
to
set
up
a
few
things.
It's
not
bad,
but
I
don't
mind
I
mean
I
don't
mind
the
personal
access
token
I
mean
it
seems
like
not
the
it
seems
weird
mainly
for
a
bot
I
mean
it
seems
like
it
should
be.
A
from
a
bot
account.
A
A
A
It
does
say
to
like
if
you
need
exempt
the
bot,
but
I
mean.
B
A
B
Yeah,
it's
really
just
I
mean
personal
access
can
be
fine
if
it
could
be
sculpt
or
repo
it's
on
the
roadmap,
but
I
think
it's
been
on
the
roadmap
for
a
long
time.
B
A
A
A
You
can
use
the
the
github
off
login.
I
think
you
don't
need
to
use.
B
A
Any
okay!
Well,
why
don't
I
just
since
I
have
had
it
working
basically
with
the
bot?
Let
me
revert
my
last
commit
on
this
the
personal
access
token
and
go
back
to
the
bot
and
we'll
just
plan
on.
If
we
do
need,
you
know,
if
we
don't
get
any
resolution,
we'll
do
this
for
a
couple
of
really
for
a
release
or
two
and
hopefully
we'll
get
something
better.
A
A
B
B
A
A
Okay
document
step:
okay,
I'll
just
push
that
all
back
into
this
pr
with
the
doc.
A
Yeah
I
had
a
last
track.
There
are
too
many
okay
cool,
then
don't
approve
this.
I
will
re.
I
will
just
update
that.
A
Yeah
thoughts
on
I
mean,
obviously
we
wouldn't
delete
this.
We
would,
you
know
at
most,
maybe
rename
it
to
2.17,
but
I
don't
know
if
we
would
we
sort
of
addressed,
I
mean
with
the
appender
we
kind
of
we
bumped
it
kind
of
with
that
expectation
of
somebody
of
that
being
weird.
B
A
A
Just
our
build
has
been
very
flaky.
C
A
C
A
Pretty
yeah
pretty
recent
friday.
A
A
Yeah
I've
been
merging
as
long
as
as
long
as
it's
a
known,
flake
I've
been
merging
it.
I've
been
doing
the
override
a
lot
lately.
This
one,
though,
have
you
seen
the
spring
rmi.
C
A
A
Okay,
yeah,
so
go
ahead,
feel
free
to
override
and
merge
with
the
flaky
stuff.
Just
as
long
as
it's
locked,
it's
not
worth
hitting
retrying
over,
like
more
than
I
don't
know
for
the
more
than
whatever
your
tolerance
is.
A
Anything
that
I
was
just
gonna
go
through
if
there
were
any
pr's
but
anything
on
your
minds.
B
A
Okay,
I
mean
I
review
like
you're
talking
about
the
public.
A
A
B
C
A
Pay
for
the
the
public
stuff-
that's
not
always.
I
don't
know
it's.
A
B
A
I
guess
for
for
public
staff,
I
agree
it's
I
mean
that's
critical
at
least
once
we
declare
stability
of
any
of
them.
A
Maybe
you
can
write
up
just
like
the
basics,
especially
because
contrib
is
gonna,
be
I
mean
it's
gonna.
B
A
From
especially
just
from
the
basics
like
that,
you
mentioned
here
of
the
kotlin
great
using
kotlin,
not
using
groovy
for
tests.
You
know
anything
that
you
know
that
we
want
to
enforce
here.
A
B
C
A
A
A
C
A
Yeah,
I
don't
think
any
oh
yeah
when
you
have
a
chance,
javier
javier,
updated.
A
A
All
right
anything
else
that
we
should
chat
about
today,.
B
A
Oh
go
ahead:
okay,
I'm.
A
A
A
Oh
yeah,
you
could
try
out
the
the
contributor
script
if.
A
Yeah
I
was
trying,
I
was
thinking
about
the
public
stuff
and
how
the
the
the
japanese,
japanese.
A
Yeah-
and
I
wonder
if
that
would
help
us,
even
with
alpha
modules-
let's
pay
attention
to
that
more
we've
never
enabled
it
for
an
alpha
module
before.
B
A
Okay
yeah.
We
can
think
I
think
on
that,
but
I
was
trying
to
think
what
would
help
with.
A
Bringing
sort
of
attention
to
that
yeah,
especially
yeah,
I
kind
of
think
that
might
help
on
the
contrib.