►
From YouTube: 2020-02-23-Package Maintenance Team 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
B
It's
been
extended
again.
I
believe
it
was
due
to
close
yesterday
so.
A
Okay,
so
it's
closed.
Okay,
then
I
don't
have
anything
either.
So,
let's
move
on
to
the
issues
tag
for
the
agenda.
The
first
one
is
opengs
world's
2020
cfp.
So
I
think
glenn
and
let's
go
ahead.
B
A
Okay,
so
that
was
submitted
you
you
were
submitting
the
panel
right
yeah
and
then
I
think
separately,
dominicus
and
beth.
Were
you
submitting
a
talk
to
or
darcy
and
I
darcy
and
you
okay,
so
that's
gone
in.
Do
you
think
beth
or.
A
A
Is
there
it
is.
B
C
A
Okay,
so
that
that
has,
I
guess
I
could
share
the
schedule
here:
share
screen.
A
A
A
A
That
one,
I
don't
see
any
more
comments
or
anything.
I
don't
know
if
anybody
has
anything
to
talk
or
discuss
on
that
front.
A
Okay,
the
next
one
is
suggest,
ignoring
a
vulnerability
by
the
package
maintainer
this
one.
I
know
that
the
you
know
the
collaboration
space
was
approved,
there's
gonna
be
an
announcement
going
out
and
I
did
start
and
spend
some
time
with
darcy
setting
up
repos
and
stuff
like
that
in
the
open.js
foundation
repo.
So
we
should
see
that
being
kicked
off
pretty.
A
A
Well,
there's
two
two
things
one:
it
took
us
a
very
long
time
to
submit
it
that
doesn't
help.
You
know,
honestly
in
terms
of
getting
it
approved.
I
just
didn't
follow
up
fast
enough.
It
was
approved,
I
think
I
you
know
we
had
an
agreement
to
approve
it
within
two
weeks,
just
to
give
people
time
to
to
think
and
read,
and
then
I
didn't
follow
up
for
a
week
after
that
or
something
like
that.
So
that's
why
it
took
a
little
bit
longer.
A
C
A
Well,
it's
yeah
and
that's
pretty
much
what
it
was
it
does
take.
I
mean
you
have
to
give
people
time
to
think
and
read
you
can't.
You
can't
expect
them
to
just
drop
things
immediately,
so
probably
around
a
two
week.
Turnaround
time
is
about
as
good
as
you
should
expect
from
a
group
but
yeah.
It
was
longer
than
that
and
it
was
kind
of
because
I'd
we
we'd
said
like
hey.
A
A
A
A
A
Next
steps
on
support
levels
and
package
jason,
I
think
I
mentioned-
and
I
I
don't
remember
if
it
was
last
week-
but
I
think
probably
been
since
then
so
this
is
the
link
blog.
I
just
want
to
find
that
blog.
A
A
The
inclusion
in
in
the
red
hat
note
shift
modules.
We
will
talk
to
some
of
the
other
teams
within
red
hat
to
see
if
we
can
get
it
added
there
as
well.
So
I
guess
the
other
thing
that
happened
was.
We
also
landed.
The
support
landed,
the
the
create
command
in
the
support
module,
pkg
support,
module.
A
A
A
A
I
don't
know
if
there's
anything
else,
people
have
to
suggest
that
we
should
do
or
you
know
people
we
think
we
should
reach
out
to
in
terms
of
trying
to
to
sort
of
get
the
momentum
going
on
that
front.
A
Is
we
did
have
a
proposal
in
with
npm
in
terms
of
having
the
information
added
on
the
dui
for
npm,
which
I
haven't
haven't
chased
yet,
but
I
but
darcy
did
give
me
the
name
of
who
I
should
sort
of
reach
out
to
so
I'll.
Do
that.
A
Okay,
that
takes
us
to
the
end
of
the
agenda.
I
don't
know
if
there's
anything
else,
we
wanted
to
talk
about
this
week.
B
I
was
gonna
because
I
don't
get
a
lot
of
time
to
with
dominic,
because
I
was
gonna
offer
to
do
some
more
stuff.
On
wibby
I
looked
the
other
day.
I
looked
I
I
must
say
I
just
looked
at
the
top
one.
You
said
you
were
already
doing
that,
so
I'm
now
going
to
look
down
and
look
at
the
second
to
top
one,
which
is
a
naming.
C
B
It
I
started
at
christmas
when
I
got
into
it.
I
must
say
I
didn't
understand
all
of
the
new
interfaces
that
we
have
and
I'm
still
coming
up
to
speed
on
github
actions,
but
using
number.
B
C
55
that's
dev
dependencies.
I
have
that
almost
done.
The
reason
it's
not
done
done
is
because
it
depends
on
some
of
the
other
ones.
Today,.
C
B
I'm
willing
to
to
lend
more
of
a
hand
there.
Thank
you
just
need
some
guidance.
C
Yeah
and
then
we
can
yeah,
I
need
to
review
the
the
mvp
stuff
as
well
again
yeah,
the
the
the
blocker
there
I
I
I
picked
also.
I
spoke
to
mateo
that
maybe
we
should
try
to
get
that
set
up
on
web
on
sorry
on
fastify,
and
that
is
an
option.
But
then
I
started
going
through
what
that
would
mean
for
webby,
and
I
figured
that
there's
just
teeny
bit
more.
That
needs
to
be
done
before
we
can
call
it
an
mvp
and
suitable
for
human
consumption.
There's
actually
a
project
there.
B
Actually
one
of
the
things
I
didn't
we've
got
to
improve
the
readme,
because
when
I
read
the
I
had
to
go
and
read
the
code
afterwards,
because
I
didn't
understand,
I
didn't
actually
understand
what
it
was
doing,
but
once
I
read
the
code
I
was
fine,
so
I
think.
C
A
B
Why
I
raised
the
issue
to
read
me:
that
was
a
classic
reasoning.
A
Yep,
okay,
any
other
things
we
should
talk
about
before
we
close
up
for
today.
A
If
not
great
thanks,
everybody
and
we
will
get
together
another
couple
weeks
and
we'll
talk
to
you,
then.