►
From YouTube: 2021-11-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
we'll
follow
the
agenda
that
was
in
the
issue
within
the
repo
which
was
issue
number
494..
A
Okay,
if
not
I'm
just
going
to
drop
the
link
to
the
minutes,
if
people
can
add
themselves
to
it,
that
would
be
great.
So
I
don't
forget
you
I'm
going
to
do
that
for
me.
While
we
talk
no
announcements,
okay,
so
the
next
one
is
first
issue
on
the
list
is
promote
security
guidelines
from
draft.
This
is
492.
A
A
Just
taking
see
if
we
can
look
at
the
view.
C
Yeah,
I'm
surprised
I
hadn't
approved
it
yet,
but
yeah
these
were
a
couple
of
the
ones
that
we
identified,
that
could
probably
just
lift
and
shift
and
so
to
figure
out.
If
that
would
be
the
case
or
not,
you
know,
the
best
way
was
just
to
make
the
pr
and
hope
for
the
best.
So
there
there's
a
couple
right
there.
A
A
A
A
It's
not
necessarily
that
the
the
working
group
is
completely
gone,
but
they
definitely
don't
handle
any
security
vulnerabilities.
We
wound.
You
know.
I
was
involved
in
helping
to
wind
down
that
program
and
hand
over
the
backlog
to
snick,
so
otherwise
I
think
you're
right
otherwise
otherwise
looks
good.
A
They
took
over
the
database,
they
took
all
the
reports
so
there's
you
know
there
was
no,
they
didn't
sort
of
take
the
database
and
publish
themselves,
but
like
everything,
every
all
the
reports
which
we
hadn't
accepted
and
handled
were
redirected.
Like
we
basically
closed
them,
saying
please
report
over
here.
Instead.
D
A
B
B
C
A
D
B
I
did
just
do
I
just
did
the
review
should
have
f4
on
there.
Now
sorry.
A
A
B
Don't
think
there's
any
updates
for
go
ahead.
Yeah
decide
to
seem
to,
as
I
mean
I
know
july
seems
only
like
the
other
day.
It's
it's
stalled,
a
little
bit
progress.
Let
me
read
up
and
try
and
catch
up
on
that
there's.
It
doesn't
appear
to
be
any
updates
on
that
john
church
is
the
last
one
to
look,
and
there
are
a
couple
of
pr's
open.
A
A
C
Yeah,
so
I
think
yeah
so
there's
just
will
be
a
couple
left,
so
I'll,
publish
or
I'll
merge
the
not
the
security
guidelines,
so
the
deprecation
guidelines
and
the
publish
guidelines
which
should
leave
after
I
merge
those
two.
Then
it's
just
continuous
and
there's
just
one
more
left
after
okay,
okay,
so
that's
great,
be
able
to
check
out
a
couple
boxes
in
a
minute.
C
Okay,
so
that's
good!
All
I
want
for
christmas
is
the
documentation.
A
D
I
did
have
some
chats
on
twitter
generally.
Maybe
it
was
twitter.
A
D
D
There's
I
I
I
spent
time
some
time
on
the
pkgs
action,
so
I
wasn't
looking
at
willy
for
the
past
for
the
last
few
months,
so
yeah
I'll
be
getting
back
to
that.
I
think
now
that
we
have
the
shareable
workflows,
it
will
simplify
the
installation
a
little
bit
and
maintenance
and
then
I
think
what
needs
to
be
done
there
is.
This
is
the
second
time
that
I
had
somebody
ask
for
a
better
explanation,
so
we
do
have
an
issue.
I
think
glenn.
If
you
still
have
yeah.
B
B
You
because
I
have
some
time
off
for
christmas
and
I
find
documentation
quite
relaxing
until
it's
challenged.
A
D
Yeah
sure,
okay
yeah,
if
you
still
want
to
look
at
that,
then
yeah,
let's
happy
to
have
a
chat,
happy
to
have
a
call,
and
then
there
was
something
yeah.
I
normally
link
people
to
the
video
that
we
did
last
year.
I
think
things
have
changed
a
little
bit
since
then,
so
maybe
it's
worth
re-reviewing,
where
we're
at
where
we're
at
right
now.
I
know
that
fastify
is
very
much.
D
The
line
to
get
installation
and
setup
is
still
tricky
and
it
still
requires
forks
and
then
it
requires
some
tokens
to
be
set
up,
so
that
bit
is
not
even
necessarily
documented
properly
and
that
there's
something
like
so
it
would
be
nice
to
get
some
teams
using
it
and
then
then
we
can
get
some
feedback
in
it
to
return
it
better.
I
think,
from
the
functionality
perspective,
I
think
I
was
mostly
yeah.
It
was
close
to
close
to
close
to
being
usable,
but
yeah.
A
That
sounds
good
anything
else
we
should
talk
about
before
we
close
out.
D
I
do
have
an
open
pr
in
pkgs
action
if
anyone
has
to
have
to
take
a
look,
not
a
problem,
not
a
blocker,
but
just
something
to
move
forward.