►
From YouTube: 2021-07-15-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
Sounds
good
thanks?
Okay,
let's
move
on
then
to
the
first
issue,
tagged,
which
was
community
maintenance
of
action,
setup
node.
A
I
think
dominique
last
time
you
you
mentioned
that
you'd
reached
out
to
miles,
but
that
it
might
take
a
little
while,
for
you
know,
some
sort
of
action
or
progress
on
that
anything.
We
should
talk
about
this
week
on
that
one.
C
I
did
get
a
response
thanks
miles
if
you're
watching
this
yeah.
I
don't
know
how
much
of
what's
in
these
emails
should
I
go
with
publicly
just
yet,
but
I
mean
we
started
the
discussion
and
we'll
see
if
we
can
take
it
forward
in
some
forms
in
some
medium,
so
yeah,
it's
moving
forward
I'll,
give
an
update
when
there's
more
to
update.
A
A
Okay,
next
steps
status
and
updates
the
next
steps
for
pkgs
create.
A
B
Yeah
all
that
came
in
the
past
hour,
basically,
but
what
I
think
I
forgot
to
so
I
I
followed
up
with
wes
after
our
last
meeting
and
him
and
I
chatted
and
what
it
came
down
to
is
basically
momentum.
I
put
some
updates
about
that
in
the
linked
issue,
but
it's
basically
just
momentum
time
whatnot.
I
personally
went
and
started
looking
at
it
and
I
had
to
wrap
my
head
around
the
intent
of
it
at
first,
and
so
I
put
an
update
in
this
thread
a
little
bit
about.
B
B
You
know,
there's
also
been
talk
about
npm,
maybe
moving
their
create
their
npm
init,
basically
packaged
to
have
it
be
supplanted
and
supported
by
this
working
group
and
this
package
so
yeah
it's
basically
just
it's
looking
for
people
to
work
on
it
and
for
me,
what
I
needed
was.
I
needed
a
clear
idea
of
what
actually
it
was
trying
to
solve,
so
I
kind
of
linked
some
of
the
things
that
have
helped
me
figure
it
out
a
bit
better.
A
B
The
create
package
json
is
wes,
said
he's
willing
to
do
that
for
sure,
okay,
and
also
one
of
the
one
of
the
takeaways
that
he
mentioned
too
specifically
was
getting
some
commitments
to
people
in
this
group
or
or
just
people
that
want
to
con.
You
know
contribute
to
that
thing
specifically,
so
he's
not
the
blocker
on
a
lot
of
it
because
he
hasn't
had
the
time
to
devote
to
it
more
or
less
so.
A
B
Yeah
he's
the
only
one
with
a
commitment
on
that
particular
repo,
so
I
can
reach
out
to
him
on
twitter
or
something
and
see
if
he
I
I
think
he
has
permissions-
you
guys
would
know
better
than
me
probably
to
move
that
repo
into
this
org
and
if
he
does,
then
I'd
love
to
prod
him.
To
do
that.
Basically,
I.
B
A
B
B
A
A
B
Yes,
I
will
tweet
him
after
this
meeting
yeah
I
mean
I'm
excited
about
this
project.
I
want
to
work
on
it
too,
but
I
think
everybody
has
said
that
they're
excited
about
it,
but
nobody's
had
the
time
to
work
on
it.
Yet
so.
B
Yep,
I
think
the
next
steps
on
that
is
immediately
getting
it
moved
in
and
then
getting
some
getting
some
stuff
merged
in
over
there,
and
I
could
probably
try
to
follow
once
that
happens.
Then
I
can
post
something
about
hey.
B
Does
anybody
want
to
have
a
meeting
just
about
this,
because
we've
had
a
lot
of
people
that
are
interested,
but
I
think
everybody's
looking
for
somebody
to
kind
of
be
in
charge
or
something
not
sure
who
that
would
be,
but
at
the
very
least
we
can
get
a
meeting
where
people
can
try
to
get
on
the
same
page
with
it.
So
I
think.
A
B
Yeah,
that's
the
wall
that
I
ran
into.
I
was
asking
a
bunch
of
what
I
think
were
implementation
detail
questions
of
myself
and
without
anybody
to
bounce
them
off,
so
right,
that's
solvable.
I
I
like
to
work
on
that
at
some
point.
It's
a
cool
thing
to
me
so,
okay,
but
I
will
I'll
I'll
contact
wes
about
it.
Okay,
stop
moving.
A
A
We
we've
defined
the
support
info
and
you
know
we
have
the
tool
under
ptgs
support
that
lights
helps
you
validate
it,
and
this
is
around
trying
to
you
know,
get
broader
usage
throughout
the
ecosystem.
So,
like
I
know,
at
red
hat
we've
added
it
to
a
number
of
our
packages.
A
Darcy
was
working
on
on
his
side,
and
so
it's
kind
of
like
you
know
just
working
as
we
can
to
try
and
get
more
packages
to
have
a
support
info,
because
the
more
that
do
the
more
useful
it
gets,
the
more
interesting
it
gets
to
build
tools
that
look
at
that
info
and
help.
You
know
the
consumers
understand
what
the
the
package
owner
is,
trying
to
communicate
to
them
and
and
what
that
means
them
in
terms
of
you
know
their
own
business.
B
A
A
B
Yeah
I
I
reached
out.
I
was
looking
for
something
to
work
on
and
I
reached
out
to
them
after
looking
at
so
for
anyone,
that's
not
familiar
open.
Telemetry
is
a
broad
overarching
project
that
has
it's
creating
a
standard
for
tracing
and
metrics
and
logging
etc.
Amongst
all
the
different
apms
application
performance
monitoring
companies,
it
is
the
second
most
popular
project
in
the
cloud
native
computing
foundation.
B
So
there's
different
special
interest
groups
for
each
language.
You
know,
there's
a
javascript
one,
there's
a
python
one,
etc
it's
as
big
over
over
arcing
project
and
it's
pretty
interesting
stuff.
It's
got
a
lot
of
support
from
vendors
and
stuff,
but
I've
been
reaching
out
to
the
js
special
interest
group
to
try
to
see
if
I
can
contribute
and
whatnot
and
it's
it's
a
really
well
run.
You
know:
they've
got
the
governance
and
the
processes
from
the
cncf.
B
So
there's
a
lot
of
people
involved,
there's
a
lot
of
stuff
going
on
there.
But
my
follow-up
essentially,
is
that
you
know
I'm
probably
gonna
work
on
it
sure
fine,
but
they
weren't
aware
of
this
working
group,
I'm
so
I've
met
with
some
of
the
lead,
maintainers
there's
three
there's
three
maintainers
of
like
you
know
explicit
maintainers
and
one
of
them
daniel
him
and
I
met
and
he
was
like.
Oh,
he
was
excited
about
the
working
group
and
had
some
questions
that
he
was
like.
B
I
haven't
known
who
to
ask
about.
You
know
this
particular
package
management
stuff.
He
has
some
questions
around
peer
dependencies
and
certain
decisions
that
they're
making
with
their
you
know
they
have
a
whole
bunch
of
different
internal
packages
that
are
dependencies
of
the
project
and
they're
trying
to
figure
out.
He
had
some
some
questions
that
basically
I
told
him.
B
I
don't
have
the
answer
to
this,
but
if
you
open
up
an
issue
in
the
package
maintenance
repo,
then
you
could
probably
get
some
people
who
definitely
do
know
more
about
this
than
I
do
to
give
you
some
some
support,
or
at
least
a
direction
and
a
nudge
in
the
right
direction.
So
my
point
is
to
keep
an
eye
out
for
that
issue.
B
He's
been
pretty
swamped,
so
we
talked
to
just
yesterday
about
this,
and
I
told
him
I
know
you're-
probably
not
going
to
get
it
in
by
the
meeting
today,
but
I'll.
Let
everybody
know
to
kind
of
be
on
the
lookout
for
it.
B
It's
I
think
it's
a
very
impactful
and
very
interesting
project
and
there's
some
node
core
contributors
floating
around
doing
contributions
to
various
like
vendor
implementations
of
this.
So
they
they're
like
they
are
working
with
some
node
core
people,
but
they
weren't
aware
of
this
working
group,
and
they
have
you
know
basic
questions
that
a
lot
of
maintainers
have
like.
I
don't
know
how
to
structure
documentation
in
a
way
that
makes
sense,
which
I
know
we
don't
probably
have
an
answer
for
that.
B
But
I
was
getting
some
really
good
feedback
from
him
about
like
here's,
the
problems
and
questions
that
maintaining
a
big
huge
thing
is
bringing
up,
and
I
don't
know
who
to
go
to
for
it
so
so
yeah,
hopefully,
hopefully,
he'll
get
a
issue
filed
here,
and
maybe
some
people
can
help
with
that.
So.
B
Yeah,
it's
they're,
I
mean
so
that's
been
going
on.
I
think
the
repos
have
existed
for
at
least
a
year.
Things
are
just
starting
to
get
stable.
Most
most
of
it
is
all
at
you
know,
version
zero
still,
but
they're,
making
a
lot
of
progress
for
sure
and
daniel.
The
contributor
that
I
spoke
to
directly
he's
he's
passionate
about
it
and
he,
like
is
really
really
receptive
and
was
really
excited
to.
B
You
know
to
basically
like
have
an
exchange
of
information
between
this
group
and
him
essentially
or
their
group
too.
So
I
think
it
could
be
a
really
good
opportunity
specifically
because
they
have
so
much.
You
know
they've
done
a
lot
of
the
work
already
of
having
governance
and
having
processes
and
having
meetings
and
there's
also
basic
stuff
that,
like
they
record
their
meetings,
similar
to
how
our
working
groups
do,
but
their
meetings
aren't
labeled
on
youtube.
B
You
know,
so
it
makes
it
really
there's
just
all
kinds
of
small
things
where
I'm
like.
They
could
definitely
there's
some
conversation
between
at
least
the
openjs
foundation
and
cncf.
That
could
be
really
fruitful.
I
think
for
these
individual
maintainers
and
stuff.
So
he
luckily
is
also
on
the
governance
board.
This
particular
individual,
daniel
daniel
dillon,
I
think
dylan.
B
So
you
know
it
would
be
cool
if
he
could
run
that
kind
of
stuff
up
the
flagpole
to
get
some
get
some
feedback
and
whatnot,
because
it
honestly
made
it
extremely
difficult
to
watch
their
meetings
is
because
they
all
were
just
labeled
with
the
date
they
happened
on
and
there's
like
five
different
groups
that
meet
on
the
same
day.
So
it's
almost
impossible
to
find,
but
yeah
he's
receptive
and
wants
to
talk
to
the
group.
So
I'm
just
waiting
for
him
to
hopefully
open
up
an
issue
or
something
so
sounds.
A
Good,
okay,
I
assume
just
this
just
as
for
the
notes.
The
it's
the
open,
telemetry,
open,
telemetry
js
is
the
right
repo.
B
Yep,
I
can
drop
a
link
if
you're
looking
for
it
to
help
you
with
the
minutes
to
capture
some
of
that
stuff.
B
Because
that's
one
of
the
things
is,
they
have
like
so
many
different
repos
and
whatnot,
and
it
there's
a
lot
of
packages
going
on
over
there.
So
I
think
that
they
would
be
a
really
interesting
project
to
talk
to,
because
I
mean
this
stuff's
getting
used
too,
like
it's
not
even
stable
yet,
but
like
a
lot
of
there's
a
lot
of
use
happening.
B
Essentially
it's
it's
also
even
it's
a
very
interesting
project,
because
it's
primarily
being
consumed
by
other
package
maintainers
at
these
vendor
specific
companies
and
as
a
result,
as
an
end
user
like
a
regular
open
source
user,
it's
extremely
overwhelming
to
try
to
get
up
to
speed
on
it
all
it's
so
there's
so
many
complex
topics
and
their
documentation
is
admitted
they're,
admittedly
lacking
in
docs,
where
it's
basically,
the
main
consumers
of
the
project
are
people
who
are
paid
to
integrate
that
stuff
into
their
employers
software.
B
So
they
have
a
lot
of
typical
needs
and
questions
about
like
how
do
we
maintain
examples
across
all
of
these
different
packages
and
repos
and
versions,
and
the
different
website
that
I,
the
main
website
that
I
don't
have
access
to?
Yada
yada,
so
I
think
it
could
be
an
interesting
conversation
to
have
for
sure.
B
A
Okay,
that
was
the
last
item
on
the
current
agenda.
Is
there
anything
else
that
we
should
talk
about
this.