►
From YouTube: Package Maintenance Team meeting - 28/01/2020
Description
A
C
So
I
think
problem
from
there's
groups.
Perspective.
I
will
just
need
to
update
this.
This
request
to
include
the
new
options
and
and
document
the
pros
and
cons
and
I
think
then
there's
the
implementation
details
which
is
all
up
to
NPM,
so
we
may
as
well
continue
discussion
there.
I
did
leave
a
comment
there
on
the
issue
asking
when
are
the
RFC
meetings,
because
I
couldn't
find
the
calendar.
B
C
It's
close
to
what
we
expected.
Yes,
I,
think
it's
a
bit
unclear
what
the
MVP
is,
because
it's
talking
about
a
package
but
when
they
say
a
package,
I
think
what
they
mean.
There
is
a
tarball
as
in
a
single
version,
so
you
would
only
be
allowed
a
single
tarball
in
staged
in
staging
essentially
and
that
sort
of
Hazard
vacations
for
cember.
And
how
do
you
do
things
there
and
how
do
you
manage
multiple
ones
and
yeah?
And
then
there's
the
question
of
permissions
and
I
think
the
it
is
a
bit
unclear
from
the
RFC.
C
How
would
that
work?
Because
at
the
moment
you
can
enable
two
FA
for
everything
or
for
just
authorization,
and
there
is
no
more
fine-grained
control
and
you
would
obviously
need
to
afraid
to
publish
things,
I,
basically
unstaged
things,
whereas
you
would
like
to
do
not
use,
do
FA
in
to
stage
a
package
which
is
the
whole
point
of
having
that
right
and-
and
it
is
a
bit
unclear
from
the
RFC.
If
and
how
that's
going
to
happen,
because
that
sort
of
implies
a
permissions
model.
B
B
A
Did
list
over
and
express
I
don't
know
if
I
have
the
exact
issue
he
did
document
the
last
five
steps
before
express
fire
can
be
released
liked
his
list
of
things
to
do
and
some
of
those
I
believe
the
Piazza
reopen
and
other
things
are
just
getting.
Consensus
and
agreement
to
move
meeps
and
code
around
or
get
the
actual
code
landed.
So
I
think
all
the
code
works
actually
done,
but
maybe
maybe
we
should
follow
up
afterwards.
I
think
they
were
aiming
for
January,
but
that
that
may
slip.
B
A
E
B
A
A
B
So
all
I
did
was
we
had
like
a
sponsored
field
which
I
think
overlapped
with
the
funding
field,
so
I
removed
that
and
I
replaced
it
if
you
scroll
up
just
a
little
bit
with
no
sorry
down
a
little
bit,
I
guess
with
the
NPM
funding.
So
the
you
know
with
that
description,
the
project
is
asking
for
funding
and
can
be
funded
through
the
links
provided
in
the
funding
field
within
the
package
at
Jason
and
I
wasn't
sure
if
we
needed
anything
more
than
that.
F
A
B
B
A
B
B
B
B
B
Bree
says:
I
have
connection
rate,
but
you'd
like
to
raise
awareness
to
the
working
group
that
they're
starting
to
work
on
an
RFC
to
add
support
to
Mono
repos
workspaces
in
NPM.
Anyone
has
strong
opinions
about
it,
I'm
currently
collecting
feedback
through
user
story
interviews,
and
we
can
schedule
a
follow-up
meeting
or,
alternatively,
just
feel
free
to
express
your
opinions
here.
If
we
have
the
time.
B
A
B
G
I
felt
as
I
was
late
to
this
meeting.
I'm.
Sorry,
if
I
have
bad
audio
right
now,
I
got
stuck
in
transit
here.
I
just
want
to
maybe
circle
back
on.
Maybe
some
public
safety
level
or,
if
you
have
a
burst
on
to
82
I,
know
that
we
open
up
our
see
I'm,
not
sure
if
I
talked
to
that
already
and
then
I
actually
have
to
follow
a
lot.
G
That
should
be
on
NPM
doc
community.
So
if
you're
there
that
the
calendar,
our
calendar,
public
events,
boundary,
should
be
accessible
from
that
page
and
then
you
can
add
it
just
like
the
owner
foundation
or
the
open
areas,
foundation,
calendars
and
our
open,
RC
bi-weekly
meeting
should
be
scheduled
within
that
and
that
can't
work.
So
you
can
follow
along.
It's
usually
that
I
recreate.
E
G
G
E
G
E
G
B
G
I
think
there's
an
opportunity
there
to
like
create
something:
that's
a
little
bit
easier
for
the
community
to
consume,
so
we're,
hopefully
gonna
be
able
to
get
ownership
there
switched
over
and
given
to
the
PK
j
EK
TJ
escort,
and
then
we
can
decide
how
we
want
go
by
guest
schools
for
that.
So
this
might
be
a
way
forward
for
the
support
schema
to
just
like
to
land
in
a
meaningful
way.
B
The
other
thing
we
talked
about
just
before
you
made
it
was
I'd
opened
a
PR
which
tries
to
integrate
NPM
funding
and
it's
3:12.
The
main
question
was
like:
if
is
that
enough
in
terms
of
addressing
the
overlap,
or
do
we
need
to
be
more
go
further?
What
I
did
is
I
just
added
to
the
backing
field,
I
removed
the
sponsored
since
I
think
that
was
the
one
that
overlapped
and
replaced
with
NPM
funding.
As
you
know,
basically,
you
can
say:
hey.
B
B
And
so
the
question
is
is
like
that
reasonable,
or
is
it
that
well
it'sit's
gonna
overlap
with
a
bunch
of
the
other
things
too.
So
we
need
to
take
out
more
make
backing
just
a
reference.
So
I
I
didn't
do
that,
just
because
some
of
the
things
didn't
seem
to
overlap
with
that,
but
looking
for
people's
thoughts
on
that
one
sure.
B
A
I
created
the
issue
to
talk
about
like
summer
startling
or
how
module
offers
tests
across
LGS
versions,
etc.
I,
don't
you
think
we
got
many
response
to
the
doodle
very
early
on
so
I'll
are
so
a
new
doodle
covering
the
next
couple
of
weeks,
or
so
with
a
bit
more
time
for
people
to
respond
in
advance,
and
hopefully
we
get
something
set
up.
I
think
it
was
like
six
or
seven
people
interested.
So
we
just
need
to
create
a
new
doodle.
I
can
do
that
after
the
meeting.
B
G
B
B
B
Messiah
is
is
now
using
that
as
the
basis
to
make
recommendations
to
the
open,
J's
foundation
he's
just
doing
some
research.
In
terms
of
you
know
what
projects
already
have
in
terms
of
security
reporting
and
then
he's
gonna
use
that
as
the
basis
to
say,
okay
and
here's.
What
we
recommend
for
member
projects,
I.
D
B
E
E
Okay,
hi
everyone,
so
the
PR
at
the
moment,
essentially
just
us
an
NPM,
install
into
a
directory,
then
runs
an
NPM
tests
using
Sitchin
on
all
the
installed
dependence.
It
doesn't
have
tons
of
functionality
at
the
moment.
There's
no
test
of
documentation
as
it's
work
in
progress,
but
I
may
need
post
upon
switching
to
try
and
get
an
idea
of
whether
this
was
the
right
approach
to
go
about
testing
and
which
was
dependencies
using
system
or
if
there
was
a
better
way
of
doing
it.
B
B
C
Just
slightly
different
concerns,
but
yeah.
So
this
is
about
testing
our
stuffs
of
the
ecosystem
in
node,
cannery
and
cannery.
Your
own
modules,
yeah
I
I,
have
that
on
my
to-do
list,
so
I'll
get
to
it.
They'll
have
at
least
an
MVP
at
some
point,
but
also
because
this
is
something
that
could
be
useful.
At
least
parts
of
it
could
be
useful
for
the
client
project
that
I'm
currently
working
on
and
I
might
even
get
some
funding
to
actually
speak
that,
oh
sorry,
which
okay,
the
part
yeah.
They.