►
From YouTube: 2020-04-22-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
B
A
A
So
now
I
know
last
time
we
talked
rx
marbles
had
so
rick
had
agreed
to
reach
out
to
wes
and
do
some
sort
of
knowledge
transfer
handover
in
terms
of
getting
stuff
out.
A
He
did
provide
an
update
on
the
issue
itself
that
they,
you
know
they
met
and
talked
about
some
of
the
the
the
projects
and
status
and
he's
setting
up
a
project
board
which
is
linked
in
the
issue,
and
I
guess
zach
you've
raised
your
hand
to
try
and
get
to
getting
get
involved
there
as
well.
C
So
I
believe
rick
had
said
that
he
wanted
to
set
up
some
time
with
myself
and
wesley
for
sinking
on
it.
So
I
assumed
we
would
do
that
today
or
if
you
want
to
do
that
over
the
github
issue,
we
can
do
that
as
well.
A
So
I'm
just
gonna
note
that,
basically,
you
three
are
starting
to
to
talk
and
move
forward,
which
is
great
because
it
would
be
nice
to
have
something
where
we
can.
You
know,
add
in
automatic
creation
of
things
like
the
support,
the
package,
support
info
and
other
things
that
you're
going
to
need
when
you
want
to
create
a
new
module.
So
thanks
thanks
for
working
on
that
anything
more
before
we
move
on
to
the
next
issue,.
A
A
There
was
a
comment
that
support
info
was
added
to
commander.js,
which
is
great.
Thank
you
very
much
to
shadow
span.
For
that
I
know
I
think
dominique
has
you
were
checking
in
near
form
any
sort
of
update,
or
still
still
doing,
that
that
would
be
just
yet
sorry,
okay
and
yeah.
I
have
similar
action
within
the
red
hat
and
ibm
larger
community.
We
did
it
for
for
one
the
node
chip
modules,
but
still
pursuing
that.
So
all
right.
D
I
was
gonna
say
I'm
also
pursuing
in
in
getting
this
added
or
looking
to
get
this
added
for
one
of
our
bigger
open
source
packages
docked
to
it
with
a
lot
with
the
team
and
then
one
of
the
the
direct
owners
of
that.
D
Where
we're
looking
over
the
documentation
that
I
that
we
wrote
up
what
it
is,
so
I
told
him
I
would
love
to
get
his
thoughts
and
ideas
about
it,
getting
it
at
it
or
you
know
what,
if
that's,
what
they
were
looking
for
doing
but
yeah
it's
one
of
the
things
I
I
brought
to
our
on
our
site
so
hoping
to
get
some
more.
I
guess
push
around
it
in
terms
of
just
a
lot
of
our
open
source
stuff
that
we
keep
moving
out.
It's
our
big
initiative.
A
Okay,
well,
no
thanks
a
lot
for
doing
that.
I
think
if
we
all
kind
of
advocate
for
it
in
our
orgs,
since
we
might
be
able
to
get
start
getting
some
momentum,
which
is
good
thanks.
Any
other
updates
before
we
move
on
to
the
next
issue,.
D
I
had
just
once
like
from
the
last
document
notes.
I
volunteered
to
add
myself
like
add
to
the
spec
forget
what
the
issue
or
what
the
thing
was,
the
top
of
my
head
in
our
previous
docs.
A
D
D
A
D
A
A
But
here
I'll
paste
it
in
the
chat.
D
This
one
yeah
so
right
there,
it
was
just
add
a
dock
in
the
same
place
as
spec
in
terms
of
people
orgs,
we've
added
that
where,
in
our
repo
is
that
location
for
the
dock,
is
that
under
the
drafts
or
is
that
under?
A
The
spec
right,
okay,
in
terms
of.
D
It
starting
to
work.
I
was
starting
to
look
into
that
and
then
I
was
like.
I
don't
know
where
that's
at
I
haven't
found
it
couldn't
find
it.
A
I
wonder
if
people
think
about
just
adding
it
into
the
existing
package
support
markdown
file
versus
its
separate
file,
so
the
package
support.md
yeah
this
one.
A
B
Yes,
that's
what
I'd
like
to
bring
up,
so
I'm
I'm
working
doing
some
work
on
there.
Dominic,
because,
as
we
do,
work
is,
as
with
all
things
we
think
more
deeply
and
we
are
coming
across
new
possibilities
of
problems
and
opportunities
in
there,
and
I
thank
you
for
that
one.
I
didn't
even
understand
that
problem
you
raised
until
I
read
it
in
the
morning
rather
than
in
the
evening,
which
I
find
is
a
good
time
to
read
problems
rather
than
sunday
night.
So
what
are
our
next
steps?
For
that?
G
B
G
For
ruby
overall,
so
I
think
that
existing
branch
handling
issue-
it
was
a
vlogger
in
my
head
for
a
lot
of
time
right,
I'm.
I
can't
find
a
sane
and
simple
solution
to
that,
and
without
that
you
are
pretty
much
guaranteed
that
it's
going
to
be
very
cumbersome
to
use
like
branches
are
going
to
exist.
People
are
going
to
be
kicking
off
wb
test
multiple
times,
they're,
not
going
to
bother
kicking
off
will
be
clean.
So
there's
there's
multiple
paths
that
I'm
thinking
about.
G
One
is
try
to
get
it
installed
in
a
couple
of
places
right
for
that
we
would
then
need
to
simplify,
will
be
clean
so
that
you
don't
need
to
run
webby
clean
from
your
local
command
line
to
clean
up
the
branches.
So
we
need
an
action
for
that.
That
is
one
path
and
then
try
it
out.
G
As
is
right
just
you
know,
it
is
what
it
is
you
you
have
to
be
clean
after
you
will
be
test
and
it's
a
trial,
and
but
but
at
least
we
get
exposure
and
we
get
some
input,
and
you
know
we
try
it
out.
Another
path
is
to
actually
try
to
solve
this
and
I
kind
of
have
it
solved.
I
just
can't
put
my
finger
on
it
and
write
it
down
and
it's
it's
still
a
bit
blurry
in
my
head.
G
The
correct
approach
that
I'm
thinking
is
basically,
I
think
that
yeah,
I
saw
your
comment.
I
didn't
read
through
it
in
detail
to
analyze
it
properly,
but
my
current
thinking
is:
I'm
leaning
towards
the
fact
that
use
cases
b
and
c
specifically
linking
multiple
packages,
multiple
versions,
multiple
packages
into
one
with
the
test,
because
you
might
be
testing
multiple
deleted
packages
with
a
similar
feature
that
spans
them
is
valuable
and
making
changes
is
also
valuable.
G
I
think
these
are
very
valuable,
useful
core
features
that
should
be
there,
so
I
think
that
they
need
to
be
catered
for
more
than
the
ruby
clean
thing
and
then
yeah
that
basically
leads
to
the
path
that
to
rerun
with
the
test.
Then
you
need
to
do
a
commitment
and
force
push
into
the
branch.
If
there
is
no
change.
G
G
You
know
outdated
branch
problem,
but
these
features
I
I
feel
that
therefore,
from
my
experience
of
having
a
similar
tool
and
just
at
least
how
we
develop
in
in
in
in
daily
job
that
I'm
doing
right,
where,
where
we
have
it's
not
exactly
similar
to
link,
but
the
webby
is
one
of
the
missing
pieces
that
we
do
need,
but
we
do
have
some
related
similar
problems
that
we're
solving
and
depending
on
how
you
structure
your
repositories,
you
may
experience
this
more
or
less,
and
I
find
that
these
features
yeah.
A
G
Kind
of
critical
to
have
so
solving
them
in
some
way
would
be
nice
before
asking
people
for
more
feedback,
because
that
is
going
to
be
the
first
feedback
that
you're
going
to
get.
G
B
B
No,
no
we're
talking
the
repo,
because
I
honestly
I
the
first
I
didn't
and
then
I
thought.
Oh,
that
is
a
bit
of
a
problem.
Yes,
but
we'll
we'll
do
that
in
in
the
reaper
and
in
the
the
issue.
So.
G
G
Me,
the
pandemic
and
real
life.
A
little
bit
intervened
over
the
past
few
weeks,
so
my
capacity
is
a
little
bit
down
but
fingers
crossed
you
know
all
tests
came
back
negative.
I
should
be
in
a
better
position
next
week
and
maybe
we
should
just
jump
on
a
call
and
try
to
maybe
brainstorm,
and
so
I'm
I'm
happy
to
do
that
as
well.
If
we
can.
G
Solve
that
issue,
I
think
then
it's
a
go,
that's
it
so
we
either
need
to
build
a.
I
think
we
probably
need
to
build
a
really
clean,
github
action
extension
as
well.
So
I
think
that
handles
it
will
be
clean
common
and
then
and
then
and
then
yeah,
then
maybe
we
can
actually
basically
start
to
start
start
using
it
in
real
life
and
see
how
it
behaves
and
reorient
and
and
see
how
it
works.
That's
that's
my
thinking
right
now.
B
A
G
A
F
H
I
guess
one
thing
that
might
make
sense
is
to
start
with
just
like
a
google
doc
and
we
can
start
adding
some
questions
into
it
and
then
once
we've
got
a
few
questions
in
there
and
we
have
a
plan
for
what
we're
going
to
talk
about
for
30
minutes
then
go
from
there,
because
it's
a
panel
talk,
isn't
it
so
we
just
need
some
prepped
q,
a.
H
I
think
we
submitted
two,
but
I
think
just
the
panel
got
accepted.
G
Yeah,
I'm
on
a
different
laptop,
so
logging
into
all
accounts.
Okay,
your
submissions
were
was
accepted,
and
this
says
dear
glenn
note
package
here
three
and
that's
the
one.
G
F
B
So
yeah
you
have
to
help
me
search.
I
can
search
my
scent
box
that'd
be
smaller
than
my
inbox.
What
are
you
searching
on
js
nation?
Oh
sorry,
open
js,
world.
A
B
I
I'll
find
it
well,
so
we
I
would
do
exactly
what
beth
said.
I
I'll
take
the
lead
in
organizing
a
document
setting
up
a
document
refining
with
the
emails
and
setting
this
up
again
I
do.
I
do
have
the
movie.
I
know
it's
in
my
send
folder
because
I
sent
it
to
everybody
as
soon
as
I
got
it.
B
B
B
So
I'll
kick
this
off.
Send
some
emails
out,
get
some
information
done
start
off.
The
document
put
some
outline
in
it
that
we
can
critique
and
change
sound
like
a
plan
and
I'll
have
to
go
and
look
up
and
see
what
a
moderator
does.
A
D
I
just
want
to
make
sure
I
don't
have
a
lot
of
conflicts
honestly,
I'm
pretty
open
tomorrow
for
sure
I'm
not
sure
about
wes.
I
was
hoping
he'd
be
here
to
take
account
for
that.
I've
got
a
good
understanding
from
him
when
we
chatted,
but
he
of
course,
a
lot
of
this
isn't
was
under
his
name
and
started
it
and
so
like
he
has
the
finer
details.
D
He
can
explain
he
is
in
slack
too
so
we
could
probably
are
you
in
any
of
the
like?
Are
you
in
the
node.js
lock
or
the
open,
jsf
slack
server
by
chance?
No
I'm
on
none
of
those
which
one
should
I
join.
D
I
honestly
we
were
chatting
in
the
open.
Js
jsf
select
server.
Initially
we
were
talking
about
this,
but
I
mean
you
can
join
both
of
them
they're,
both
good
sources
to
have
like
not
just
for
this
working
group
but
like
in
general,
across
the
open
js
world,
but
yeah.
D
We
could
start
up
a
thing
on
the
open,
jsf
one
and
a
three-way
dm
and
just
see
if
we
can
make
it
king
see
if
we
can
just
go
ahead
and
get
that
scheduled
up
because
yeah,
I
think,
he's
probably
a
little
busy
or
he
might
be
out
on
vacation
who
knows
what's
his
west
is
everywhere.
D
But
yeah
I'm
open
tomorrow,
after
about
9
30
mountain
standard
time
for
me,
so
whatever
that
would
be
for
you
just
let
me
know
send
me
an
invite.
We
can
get
that
going
and
then
we
can
get.