►
From YouTube: 2022-02-17-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
All
right,
okay,
we're
live
so
welcome
to
the
node.js
package,
maintenance
team
meeting
for
february
17
2022.
we'll
follow
the
agenda
in
the
issue
that
was
created
in
the
repo
which
is
issue
number
511.
A
Okay,
if
not,
let
me
just
take
a
quick
note
there
and
then
roll.
A
B
Yes,
during
the
past
week,
I
have
submitted
the
talk.
B
I
don't
have
any
updates
from
from
organizers,
but
wait
for
for
it,
and
I
I
talk
about
opengs
world
and
also
I
submit
the
paper
for
whole
gs
conference.
This
is
one
of
the
biggest
conferences
in
russia
local
conference
in
russian.
B
I
have
one
talk
with
the
program
committee,
but
also
there
are
no
some
kind
of
commitments
on
so-and-so,
but
now
my
work
in
progress,
I'm
waiting
for
results
from
program
committees
and
also
I
cook
some
stuff
for
for
further.
For
further
events,
I
mean
I
write
draft
of
my
paper
and
I
think
that
maybe
in
march
we
can
talk
about
it.
A
Okay
sounds
good,
I'm
just
looking
at
the
the
issue
itself
to
see
so
some
of
the
pro
promo
activities
you
had
like
an
article,
the
talks
which
you
just
gave
us
an
update.
If
those
were
updated
and
then
a
round
table
was
the
other
one
where
we
were
talking
about,
I
think
getting
some
some
people
together.
B
We
can
I
decide
that
we
can
talk
about
roundtable
after
that
conferences,
progress,
but
I
think
that
we
can
talk
about
article
after
I
can
show
my
draft
results
with
with
speech,
because
I
think
that
article
and
conference
talk
can
be.
A
Okay,
that
makes
sense,
sounds
good.
Any
questions
that
people
have
before
we
move
on
to
the
next
issue.
A
C
I
was
curious
what
the
like
the
description
or
the
topics
that
you
submitted.
So
that
way,
someone
doesn't
resubmit
for
something
you
might
have
already
yeah.
A
Yeah
yeah,
of
course,
maybe
you
could
post
five.
B
A
And
titles
in
the
issue
itself:
okay,
sure
sure,
are
you
do
it
right
now?
Okay,.
C
D
Not
this
year,
I
haven't.
I
don't
think
that
there
is
a
a
formal
like
you
know,
we'll
give
you
thing
talks
for
for
sure,
but
generally
I
I've
seen
those
get
accepted
and,
like
my
perception
has
been
that
it's
like,
oh
yeah,
it's
from
the
working
group.
Well,
we
can
go
ahead
and
find
a
spot
for
this.
It
has
that's
been
my
perception
whether
or
not
that's
the
reality
this
year
I
don't
know,
but
I
I
imagine
something
will
get
accepted
so
maybe.
C
A
C
Makes
sense,
cool
all
right,
well
I'll,
see
what
I've
all
submitted
and
see
if
there's
anything.
A
A
You
know
the
core,
not
the
people,
who
are
already
collaborating
more
interested
involved,
whatever
right.
C
Yeah
cause
I'm
also
trying
to
think
of
what's
a
good
way,
because
I
know
like
documentation
is
something
we're
probably
more
willing
to
share,
as
opposed
to
like
the
early
beta
of
the
action
that
dominicus
has
been
working
on.
So
we
might
have
like
two
distinct,
so
don't
want
to
publicize
something
we're
not
ready
to
share
if
we're
just
trying
to
keep
it
beta
or
something
like
that,
because
some
of
that
stuff
is
cool.
But
I
know
we're
just
being
more
cautious
around
that.
C
E
C
Yeah,
I
guess,
if
you
want
to
comment
that
you
know
just
so,
we
don't
get
like
double
submissions.
You
know,
because
I
think
that
would
be
a
great
one
to
demonstrate,
go
ahead
and
submit
whatever
well,
it
would
be
a
better
authority
on
the
actions
one
I'd
just
be
putting
it
out
so
anyway,
all
sounds
good.
A
D
One
thing
I
would
like
to
poke
out
on
this
is
there
I
think
I
opened
a
discussion
in
core
about
automatically
booting
people
from
the
org,
and
I
think
that,
having
an
extension
of
that,
like
reusing,
that
same
process
for
teams
is
probably
a
good
thing.
Like
sure
I
I
think
automated
org
wide
booting
is
fine
and
like
having
it
on
a
you
know,
year
and
a
half
time
timeline
of
like
if
you've
not
done
anything
we're
just
gonna
boot.
D
You
is
reasonable,
but
I
think
you
can
reuse
that
same
logic
to
do
like
six
months
or
whatever.
Whatever
time
frame
we
want
to
enforce-
and
I
think
re
minimizing
duplication
of
this
effort
is
probably
smart.
D
So
if
we
want
to
do
that,
and
that
also
might
be
a
way
that
this
team
can
help
implement
it
in
the
org,
since
that's
probably
an
action
that
we
could
build
or
not
an
action,
but
you
know
the
script,
do
we
want?
Do
we
want
to
try
to
do
this
automatically
rather
than
manually.
A
I'll
add
my
my
two
cents
like
I'd
agree.
If
there
was
like
a
standard
approach
in
in
the
in
the
org,
then
that
that
would
be
great
and
like
working
groups
could
say
well
that
applies
to
me.
Let's
just
inherit
it
or
they
could
say
well,
no,
we've
got
some
special
reasons,
that's
just
something
different,
but
most
likely.
I
think
they
would
just
be
inherited
your
question
about
like
do.
We
want
to
automate
it
it's
like
if
somebody's
got
time
to
automate
it.
I
think
that's
fantastic.
A
This
one
was
a
like.
We
know,
there's
a
lot,
there's
a
lot
of
interest
in
the
beginning,
many
of
those
people
haven't
participated.
So
let's
do
a
manual
pass
through
and
clean
that
up,
but
you
know
from
my
perspective,
if,
if
we
had
something
to
automation,
to
turn
on
I'd,
be
plus
one,
and
we
can
ask
what
everybody
else
thinks,
but
I
wouldn't-
I
wouldn't
tie
this
one
to
that.
I
think
like
we're
well
through
this,
let's,
unless,
unless
the
automation
is
just
already
done
by
the
time,
this
is
ready.
C
Is
that
upstream
discussion
linked
because
I
think
I
think
maybe
one
of
the
points
probably
worth
capturing
at
either
level
is
kind
of
what
those
I
guess
policies
are
like
it's.
You
know
activity
after
this
or
you
know
if
you
haven't
but
you've
commented.
You
know,
I
guess
newer
than
michael's
point.
If
there's
a
way
to
articulate
that
kind
of
threshold
or
criteria,
then
you
know
it
can
at
least
be
done
manually
until
it's
automated
or
something
like
that,
but
at
least
that
is
transparent.
So
everyone
knows
like.
C
C
D
And
doing
work
is.
C
D
Only
the
last
github
only
keeps
either
the
last
300.
Well,
if
you're
checking
a
repo,
you
can
figure
it
out,
but
you
cannot
check
a
user
as
easily.
You
have
to
catch
all
of
their
interactions
or.
D
Like
gh
archive
github
only
stores
the
last
300
act,
you
know
actions
or.
E
D
E
D
Or
the
last
90
days,
whichever
is
smaller,
so
most
people
who
are
active
are
going
to
be
hitting
the
300
before
they
hit
the
90
days.
C
D
Check
the
repo
and
then
honestly,
the
way
I
do
it
is
I'd.
Look
at
the
team
make
sure
the
team
has
control
of
all
of
the
repos
that
are
relevant.
So,
like
you
know,
package
maintenance
team
should
have
back
maintenance
repo
as
something
in
their
scope
and
then,
if
someone
is
active
in
that
repo
or
any
of
the
repos
that
that
team
owns.
A
I
think
if
we
have
some
tool
and
support
like
it
might
drive
some
other
things
like
there's
a
number
of
people
I
can
see
who
were
chiming
in
who
are
like.
Well,
you
know
I
don't
come
to
the
meetings,
but
I
am
listening
and
following
so
like,
I
could
see
that
driving
like
okay.
We
could
have
like
members
and
observers
right
where
members
actually
get
access
to
be
able
to
do
things
in
the
repo.
A
C
Yeah
yeah
there's
a
really
good
yeah,
because
I
think
I
think
in
general
surfacing
the
various
ways
that
github
allows
you
to
selectively
stay
informed
of
a
repo.
So
it's
not
just
like
a
giant
fire
hose.
It's
like.
Oh,
I
just
want
issues
or
just
want
discussions
also
if
it
gives
people
a
little
more
sense
of
sustainability
that
it's
like
I'm
not
going
to
get
flooded
with
everything.
If
all
I
care
about,
is
you
know
new
issues,
so
it
could
be
just
a
general
knowledge
surfacing,
but
I
think
yeah.
Do
we?
C
A
In
this
case,
we
were
just
doing
an
initial
pass
and
anybody
who
says
they're
still
interested
oh
right,
it
was
just
a
come
first
serve
kind
of
thing,
it's
kind
of
a
if
there's,
no
response,
no
activity.
I
think
you
know.
I
know
jordan
had
mentioned
that
like
maybe
we
should
do
another
pass,
which
is
more
driven
or
something,
but
that
one
like
if
the
work
that
tierney
mentions
happens,
is
or
is
going
to
happen
soon
enough.
We
might
just
choose
to
adopt
that
right.
Yeah,
yeah.
D
C
A
A
D
I
I
one
thing
I
would
like
to
maybe
recommend
is
given
all
of
the
interest
that
all
of
those
people
seemingly
have
I'd,
love
to
see
them.
I'd
love
to
see
us
try
to
push
them
to
contribute
to
the
pkg
pkg.
D
A
Right
are
you
back
to
the
the
membership
review.
A
D
Yeah-
and
I
I
I
think
perhaps
in
a
you
know
in
a
next
pass-
we
can
here,
you
know,
maybe
maybe
a
pass
or
two
down
the
line
on
this.
We
can
start
saying
like
hey:
let's
have
this
be
people
who
are
actively
contributing
to
gjs
and
the
the
package
maintenance
group.
I
I
think
that's
a
reasonable
thing
to
to
have
the
team
be
scoped
too
yeah.
D
A
A
Cool
okay,
I
guess:
okay,
it's
no
update
on
pkgs
crate.
The
next
one
is
suggested
list
of
models
to
get
support
info.
I
don't
think
there's
any
update
on
that
one
either.
I
leave
it
on
so
that
eventually
I'll
I'll
do
something.
The
last
one
was
2fa
in
ci.
A
I
think
we
did
discuss
that
a
little
bit
last
time,
but
dominique.
Do
you
remember
what
what?
If
anything,
we
should
sort
of
do
his
next
steps
on
that
one
I'd
have
to
rewatch
the
video.
F
E
And
also
I
do
know
that
neoform
has
done
some
pretty
cool
work
with
the
release
action.
I
think
simonia
posted
at
the
end,
I'm
not
sure
if
they
have
any
demos
anywhere,
but
I've
seen
the
demo
end-to-end
and
it's
it's
it's
pretty
cool.
What
what
what
they've
built
from
from
from
there.
I
think
they
will
be
submitting
that
to
some
conferences,
but
I'm
not
sure
so.
Maybe
I
can
invite
them
to
give
a
demo
here
but
yeah
that
yeah.
A
B
E
Yeah
I,
if,
if
we
figure
that
maybe
we
tag
it
with
a
date
and
say
this
was
then,
and
maybe
somebody
can
update
what
is
now
and
we
can
merge
it,
I'm
happy
to
do
that
right,
closing
it.
I
I'm
not
willing
to
let
it
go
just
yet.
No.
A
It
was
more
the
do
we
want
it
on.
Do
we
want
it
as
yeah.
A
C
And
there
is
like
a
I
just
created
like
a
general
activities
for
this
year,
like
kind
of
kanban
board,
so
you
know
at
least
the
things
that
we've
been
talking
about.
You
could
just
go
to
that
board
and
they'll
be
there.
So
you
know
it
was
more
like
if
they
fall
off
the
agenda,
but
we
kind
of
still
want
a
little
visibility
into
what's
in
progress.
C
So
if
you're
ever
looking
for
it
or
whatever
we've
been
up
to,
you
can
always
click
on
that
and
kind
of
see
the
state
of
things
as
well.
So
we
can
take
things
off
and
not
necessarily
worry
about
them
falling
off
into
the
issue.
Clip.
A
Sounds
good
so
that
actually
takes
us
to
the
end
of
the
things
that
we're
tagged
for
the
agenda.
Are
there
other
things
we
should
talk
about
this
week?.
F
Yeah
did
we
ever
land
on
the
setup,
node
action
moving
it
to
the
node.js
org.
I
know
we
last
emailed
myself.
A
Any
other
public
things
we
should
talk
about
this
week.
C
Making
the
meme,
but
pretty
far
out
it
was
okay,
yeah
beamed
to
death
on
twitter,
but
memes
aside,
that
was
pretty
excellent.
Yes,.
D
Very
very
excited,
and
that
is
something
that
I
think,
credit
huge
credit
to
the
indici
folks
to
ethan
arroway.
E
D
Roan
ag
to
matteo,
of
course,
you
know
everyone
involved
on
that
side.
Yeah
made
that
happen,
and
it's
it
was
really
cool
to
see
that
go
from
like
a
prototype
to
being
implemented
in
core.
C
Yeah
fantastic
good
stuff,
but
I'm
not
sure
if
it
what
version
it
was,
but
as
json
modules
is
in
node.js
now
right:
yes,
not
jericho.
Okay,
I
know.
D
E
C
C
D
A
Okay,
anything
else
for
the
public
session
nope.
Okay,
I'm
going.