►
From YouTube: Node.js Community Committee Meeting 2021-03-18
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
Cool
thanks
everyone
for
joining
us
for
another
community
committee.
I
almost
said
cpc.
I
don't
know
why.
I've
never
said
that
for
the
cpc,
but
thanks
for
joining
us
for
another
cpc
god,
another
comic
con
meeting
yeah.
I
guess
we
could
just
get
started
and
skip
over
me
doing
that
failure
again
yeah.
So
we
have
a
few
things
on
the
agenda
this
week,
which
is
nice.
I
assume
we
will
blow
through
them
relatively
quickly,
they're
all
pretty
low
barrier.
A
One
note
if
folks
could
take
or
help
with
minutes.
We
would
appreciate
that
I
will
drop
the
minutes
link
in
half
a
second
when
I
copy
the
right
link
and
not
the
issue.
B
Sorry,
I
don't
mean
to
interrupt.
I
did
try
to
add
an
item
to
the
agenda
and
I
I
guess
it
didn't
populate
that
no.
A
Great
thanks
yeah,
so
sorry.
D
It
looks
like
it
looks
like
it
did:
wind
up
on
the
the
agenda
cindy
you're,
talking
about
helping
comcom
manage
the
comcom
repository
219
and.
A
You're
fine
also
for
those
who
are
here.
I
think
I
might
have
just
broken
that
link
for
those
who
are
here.
If
you
could
add
yourself
to
the
attendance
or
the
presence
list
present
not
presents
I'll
take
presents
if
you
have
them,
though,
if
yeah,
if
you
could
add
to
yourself
to
that,
that
would
be
excellent
cool
yeah.
So
I
guess
let's
do
initiative.
A
A
I
have
none
from
none
from
examples.
I
did
imminently
come
to.
A
D
Yeah,
I
guess
I'll
I'll
go
yeah
so
for
mentorship.
I
think
we're
pretty
much
all
set
with
napi
they've
got
their
mentee.
He
attended
their
meeting,
and
so
I
think
that's
all
going
fine
michael
yeah
yeah.
E
D
Great
I'd
love
to
love,
to
hear
that,
and
I
think
other
than
that
it's
probably
just
a
little
bit
more
of
the
same
of
us
trying
to
figure
out
who
to
help
next
and
we
do
have
something
on
the
agenda
related
to
that,
and
I
don't
know
I
might
be
forgetting
something,
but
I
think
that's
the
gist.
A
Oh
one,
one
question
I
have
in
that:
have
you
all
presented
or
participated
in
the
tse
meetings
at
all.
D
D
E
B
D
E
E
C
G
F
F
Yeah
and
we
are
continuing
to
get
kind
of
drive-by
doc,
docs
changes
which
is
kind
of
normal,
and
I
also
created
some
issues
on
like
component
updates
and
for
the
community
page,
and
I
don't
think
anyone's
volunteered
for
that
one
yet
to
create
a
sidebar.
G
That's
about
it
cool!
Let
me
let
me
ask
a
question.
That's
sort
of
related
because
I
I
I've
been
thinking
about
this
from
a
conversation
you
and
I
had
a
little
bit
ago.
Do
we
have
does
node.js
have
a
docs
team?
Have
we
ever
had
a
docs
team?
Is
it
something
that.
A
We
we
have
had
a
doc's
team
and
it
has
failed.
I
think
two
times
now
to
I'm
sure
michael
also
has
opinions
or
thoughts,
or
at
least
contact
objective
context
around
this,
but
there's
been
a
doc's
team
twice
in
general.
It
ends
up
getting
either
not
enough
traction
or
there's
too
many
barriers.
So
that's,
I
think
how
that's
happened.
A
If
we
want
to
try
it
again,
I'm
happy
to
try
that
I
would
prefer
not
to
lead
it,
but
I
would
be
happy
to
help
with
that,
especially
just
because
I'm
I
am
still
working
on
basically
a
full
rewrite
of
the
docs,
with
ethan
airwood
to
propose
with
we're
physically
working
on
tooling
first,
but.
G
That's
that's
interesting.
Your
last
comment
there
because
I
think
that
relates
to
what
ben
and
I
were
talking
about.
You
know
like
in
looking
at
integrating
the
docs
to
the
new
platform.
You
know
gatsby
and
everything
the
way
things
are
written
in
the
docs,
some
of
the
like
kind
of
flags
and
and
stuff
that's
picked
up
by
the
tooling
just
trying
to
figure
out
how
we
could
migrate,
that
to
a
new
website
and
and
kind
of,
like
you
know,
build
process.
G
So
that's
very
interesting.
I
don't
know
what
what
work
you
and
ethan
have
done,
but
that's
I
mean,
maybe
maybe
the
maybe
the
five
of
us
have
a
or
four
of
us.
However,
many
have
a
doc's
team
assembling
as
we
speak.
A
Yeah,
I
so
sorry,
I'm
just
I
realized
I
forgot
to
put
out
a
tweet
that
we're
live
so
ethan
and
I
I
proposed
a
while
ago
that
node.js
moved
to
electron's
docs
parser
tooling.
That
tooling
was
custom
built
for
electron.
A
It
basically
allows
them
to
statically,
generate
or
generate
types
from
docs,
which
is
something
that
is
interesting.
It
basically
builds
out
a
typed
structure
of
json
into
or
from
markdown.
So
you
have
to
type
very
specific.
You
have
to
write
your
markdown
very
specifically,
which
in
converting
some
of
our
documents,
we
are
not
consistent
in
how
we
write
markdown
at
all
at
all,
like
even
in
the
same
dock,
so
that
like
and
it's
it's
not
hard-
it's
just
like
getting
it
to
the
same
spot.
A
I
believe
michael
requested
that
we
first
have
a
linter
rather
than
use
it
like
we,
we
move
to
this
and
we
kind
of
go
through
a
linting
process.
So
we
can
have
that
developer
experience
rather
than
having
to
like
know
how
to
write
the
docs
and
then
like
run
it
in
a
pr
which
is
fine.
I
totally
agree
with
that.
A
A
It
locally
for
sure,
right,
yeah
and
so
like
you
can
do
it
locally
and
it's,
but
it's
wonky,
and
so
it's
like
having
a
linter
is.
I
totally
agree
that
having
a
linter
is
ideal
and
also
that
would
benefit
electrons
so
they're
like
they
don't
have
a
linter,
so
it
makes
sense.
This
led
ethan
and
I
down
a
path
of
okay.
A
Well,
we're
going
to
strip
out
how
they
do
the
parsing
and
make
that
a
unique
module
have
electron
consume
that,
since
they
don't
care
about
that
and
then
yeah
have
electron,
consume
the
the
parser
or
like
the
parsing
of
markdown,
on
the
basically
the
ast
that
they
build
and
then
also
be
able
to
use
that
same
module
for
for
linting,
and
then
that
led
a
little
bit
further
down
the
path
of
they
were
doing
it
a
little
bit
unoptimally
and
by
a
little
bit
I
mean
like
they
were
doing
it
twice
when
they
needed
to
do
it
once,
and
so
we
have
gone
further
down
that
path
of
starting
from
basically
starting
from
scratch.
A
With
their
rules.
Ethan
has
done
an
immense
amount
of
work
on
this.
I
want
to
take
no
credit
for
the
amount
of
work
that
he's
done.
It's
he's
done
a
lot,
and
so
you
know
we're
we're
still
poking
at
that.
As
time
goes
on,
and
so
it's
not.
It
definitely
might
seem
like
a
solid
thing
from
that
from
that
issue.
If
folks
are
interested
in
helping
with
this
that'd
be
cool,
but
it's
also
like
definitely
not
a
guarantee
that
node
will
accept
it.
A
So
you
know
there's
that
caveat,
but
I
think
that
we
can
get
it
to
a
point
like
ethan,
and
I
definitely
have
in
mind
that
this,
like
a
goal
for
this,
is
to
get
allow
node
to
use
this
and
to
make
it
generic
enough
that,
like
others,
could
use
it
too,
which
has
a
lot
of
other
benefits
ecosystem-wide
for
a
lot
of
reasons
that
I
I
won't
get
into,
but
yeah
it's
something
that
we're
working
on.
A
If
that's
something
you
two
would
be
interested
in,
helping
with
I'm
happy
to
to
start
a
discussion
with
ethan
joe,
I
think
you've
been
talking
to
ethan.
So
I
think
you
know
him
enough
to
do
you
have
a
channel
tim.
G
Yeah,
I
just
I
actually
just
had
a
meeting
with
him
before
this
meeting.
Yeah
yeah
and
he's
great
he's
really
doing
a
lot
of
great
stuff
yeah.
I
mean
I
think
this
is
really
interesting
and
it
seems
like
the
work
aligns
in
terms
of
the
work
that
would
need
to
be
done
to
have
it
function
in
the
new
website
as
well.
A
F
F
A
A
That
jason
is
relatively
primitive
and
doesn't
have
it's
like
you
know,
there's
like
html
in
it,
I
believe,
like
there's
raw
text,
html,
that's
in
the
json,
and
the
benefit
of
this
was
would
be
another
benefit
of
this
would
be
that
you'd
get
a
lot
more
granular
and
useful
information
from
a
similar
but
more
informed,
more
complete
json
file
that
could
be
used
in
something
consumed
from
something
like
gatsby,
without
actually
having,
apparently
without
having
to
build
node.
So
you
know
that's
another
benefit
that
we
get
there.
A
One
thing
one
thing
I
also
do
want
to
say
is
like:
if
you
know
you
know,
as
we
continue
down
the
path
of
website
redesign,
one
of
the
things
I've
noticed
about
the
node
site
is
like.
If
I
type
like
fs.promise
into
google,
I
get
node
10
docs,
which
is
not
good.
A
A
G
That's
the
common
problem.
I
find
this
all
the
time
where
I
search
something
I
end
up
on
a
docs
page
and
I'm
like
oh
shoot.
You
know
a
variety
of
languages
and
platforms.
No,
and
we
can
note
that
that's
something
we
should
figure
out
long
term
yeah.
So
I
don't
know-
maybe
maybe
the
four
of
us
should.
I
don't
want
to
derail
the
comcom
meeting
here,
but
maybe
the
four
of
us
should
get
together,
talk
about
the
state
and
and
see
how
we
can
work
together
to
move
things
forward.
G
I
can
start
a
group
slack
and
then
we
can
take
it
from
there.
A
Okay,
any
other
initiative
updates.
Oh
also
david.
I
think
michael
had
a
a
question
for
you
in
the
zoom
chat.
Any
other
initiative
updates
things
like
that.
G
I
feel
like
I
had
something,
but
now
I
forgot
what
it
was.
Oh,
this
is
a
I'm
gonna
post
it
in
the
chat
here.
This
is
more
of
an
announcement
than
initiative
update.
I
just
wanted
to
make
sure
that
folks
know
the
next
10
survey
is
live.
This
is
a
survey
born
out
of
the
next
10
work.
You
know
node.js
next
10..
So
if
you,
you
know
anybody
here
in
the
group,
but
also
streaming
an
hour
later,
you
know
if
you
have
interest
in
helping
shape
the
direction
of
node.js.
G
The
future
work
check
out
that
tweet
from
the
node.js
handle
and
and
take
the
survey.
It's
a
tweet
thread
too.
So
there's
a
blog
post
in
the
second
tweet
and
the
third
tweet
has
a
link
to
the
repo.
If
you
have
any
interest
in
any
of
that,
please
take
a
look.
E
E
We
had
some
great
discussions
so
we're
hoping
it's
good
but,
like
you
know
it's
it's
only
a
smaller
number
of
people
participating
and
we
really
need
the
the
broader
community's
help
to
make
sure
that
that
that
sort
of
understanding
of
what
people
need
is
correct
and
that'll
make
sure
that
you
know
the
basis
that
we're
making
some
of
the
the
next
sort
of
discussions.
You
know
what
we
think
is
key
for
the
success
of
the
next
10
years
are
on
a
solid
foundation,
so
yeah,
please,
please
go
out
and
fill
that
out.
G
A
Yeah,
so
I
think
I
I
think
that's
a
good
point.
Definitely
it's
not
a
calm
combination,
but
it
is
a
good
thing
to
update
joe
and
I
shipped
some
worked
on
some.
We
didn't
fully
ship
but
worked
on
some.
A
Automation
for
for
the
twitter
account
for
lack
of
a
better
word
in
the
tweet
repo.
It
turns
out.
We
need
a
a
unique
non-github-provided.
A
Pers
get
a
personal
access
token,
because
for
security
reasons,
github
actions
can't
run
trigger
other
github
actions
with
the
github
provided
or
with
an
actions
provided,
say
I
toke
or
get
up
access
token.
So
we,
I
think
we
have
approval
for
this.
At
this
point
yep
we
do,
I
think
yeah
I
will
be
on
ref,
so
I
can.
I
can.
I
don't
know
who
I
need
to
ask
for
that.
Michael,
you
might
know
who
I
need
to
ask
for
a
personal
access
token,
but
that's
a
thing.
A
We
need
to
ask
for
yeah.
A
A
E
If
you
want
to
schedule
a
time
with
me,
we
can
probably
like
I
should
have
access
to
go
and
see
if
I
can
figure
out
how
to
log
into
the
bot
account
I've
never
done
it,
but
I
I
shouldn't
have
the
access
to
get
the
credentials.
We
could
then
take
a
look
and
see
like
is
that
where
everything
is
and
if
so
then.
E
A
Yep
sounds
good.
I
I
will
do
yeah
so
I'll
do
that
so,
theoretically,
now
we
should
be
able
to.
With
that
personal
access
token,
we
should
be
able
to
automate
prs
for
the
build
appreciation,
tweets
and
the
end
the
job
tweet
that
doesn't
also
exclude
like
we're
not
only
doing
those
it's
just
those
are
the
ones
that
are.
You
know
the
lowest
hanging
fruit
that
we
know
we
wanted
to
do.
I
imagine
we
will
also
add
a
hey.
A
Here's
what's
happening
this
weekend,
node
tweet,
with
a
link
to
the
calendar.
I
I
think
that's
the
lowest
lowest
hanging
fruit.
If
someone
wants
to
add
a
query
like
add
a
pr
to
or
pr
query
to
get
like
the
entries
from
the
calendar
or
something
that'd
be
cool
too
or
if
we
wanted
to
start.
If
we
want
to
completely
change
how
we
do
everything
and
have
everything
through
code
in
a
centralized
repo,
like
sure
that's
another
way,
we
could
do
it.
A
I
guess-
and
we
could
get
it
from
that,
but
I
don't
think
anyone's
gonna
be
doing
that
work.
So
yeah
yeah,
that's
those
are
the
kind
of
updates
there.
Just
waiting
on
that
to
that
process
of
getting
a
personal
access
token
to
to
do
that
cool,
but
yeah
we
should
be
good.
There
does.
G
Anybody
here
have
access
to
the
calendar.
It
would
be
great
if
we
got
that
social
team
meeting
on
the
calendar.
Oh.
A
Yeah,
I
can
do
that
joe.
What's
what
was
the
time
again.
G
I
think
was
it
wednesday
at
one
on
the
off
week
from
com
com,
so
not
this
week,
but
next
week.
A
G
From
the
cpc
side,
I'm
trying
to
think
what
what's
what's
to
report
there.
You
know
the
open.js
world
stuff
has
been
going
on
the
cfp
close
working
through
the
the
proposals
there.
I
think
I
I
don't
remember
the
timing,
but
acceptance
stuff
should
start
to
go
out
in
the
next
week
or
two.
What
have
we
been
working
on?
I
actually
missed
the
last
meeting,
so
I'm
not
exactly
sure.
A
There
was
the
meeting
prior
was
coc
discussion
and
then
the
last
meeting
was
oh,
my
god.
The
last
meeting
was,
I
can't
recall,
yeah.
G
Some
diversity
work,
which
is
which
is
great,
we're
kind
of
aligning
with
some
other
groups,
like,
I
think,
the
w3c
and
maybe
chaos.
I
think
we're
kind
of
gonna
start
collaborating
with
them
to
really
kind
of
figure
out
how
to
measure,
but
also
improve
diversity,
equity,
inclusion,
yeah
and
we
we
have
found
that
our
code
of
conduct,
like
moderation
guidelines,
have
some
work,
some
clarity,
some
gaps.
So
we're
working
on
that.
G
I
think
the
next
working
session
will
be
on
that,
but
you
know,
I
think
I
think
it's
good
work
that
we've
we've
found
these
things
and
can
make
things
more
clear
and
documented.
Clearly.
E
A
E
F
E
E
G
E
So
those
are
ones
where,
like
you
know,
I
I
really
believe
there's
there's
no
impact
to
just
changing
it.
On
the
other
hand,
I'm
I
haven't
just
done
that,
because
it's
kind
of
like
hey,
I'm
not
active
in
those
repos.
It
would
be
at
least
good
to
do
something
that
says:
hey
whoever.
B
A
It
might
be
worth
just
also
creating
like
a
templated
issue,
that
you
can
copy
paste
and
say,
like
hey,
here's,
this
message,
you
know
if
there's
any
objection
to
us
changing
changing
the
language
here,
you
know
in
seven
days,
yep,
you
know
responded
otherwise,
like
you
know,
we're
gonna.
Do
this
yeah.
A
G
The
the
openjs
slack
channel
for
the
redesign
or
for
the
internationalization
is,
you
know
on
again
off
again
kind
of
active.
You
know,
I
think,
if
we
pinged
in
there,
we
we'd
probably
get
a
response
too.
So
I
think
it's
just
i18n
and
no
jsi
18n
and
openjs
slack.
A
I
yeah
I.
I
also
think
that
going
through
that
the
the
process
might
be
a
good
one,
just
like
hitting
like
saying:
hey
we're
gonna.
Do
this
like
there's
even
you
know,
I
mean
there's
even
comcom
repos
that,
like
I'm
sure,
still
could
do
this
yeah.
So
like
do
you?
Do
you
have
that
list
somewhere,
michael.
A
G
And
michael's
got
a
handy
script
too,
that
he
runs
that
I
probably
generated
this
list.
If
anybody
is
yep
yeah.
A
E
D
A
Okay,
cool
yeah,
so
that's
a
thing
that
we
can
do
joe.
Are
you
up
for
that?
Like
we're,
writing
a
template
with
me
and
then
we
can.
G
E
Yeah
we
can
do
those
ones
and
then
there's
probably
a
whole
bunch
of
other
ones
too,
like
not
even
just
the
internationalization
ones,
but
there's
a
whole.
There
are
a
lot
of
repos.
It
might
even
be
that
we
should
like.
We
could
just
put
it
into
all
the
repos
right.
It's
kind
of
a
you
know.
Is
there
anybody
who's
active
and
has
an
issue,
and
if
not,
you
know.
A
Sense
cool,
I
think,
with
that
we
should
probably
get
into
agenda
items.
I
will
go
ahead
and
move
us
move
us
into
that
cool.
So
the
first
agenda
item
is
going
to
be
tsc,
introduce
async
votes.
I
think
we
said
we'd
pull
the
label
off.
That
is
that,
okay,
if
I
remove
that
label
michael.
E
A
Another
thing
I
I
would
suggest
is
that
we
remove
the
cc
review
label.
I
don't
think
we've
ever
used
that
in
well,
except
for
maybe
the
first
like
six
months.
I
don't
think
we've
actually
used
it,
though
so
that
might
be
a
thing
we
want
to
to
go
ahead
and
nuke
from
from
some
repos.
As
we
see
it,.
E
F
A
A
Cool
commented,
so
that's
removed
next
issue
is
create
new
github
bot
for
personal
access
token
for
v8
automation.
I
believe
I
commented
on
this.
The
reason
this
is
admin
five,
eight
seven.
I
put
it
in
the
chat
the
way
if
we
could
get
help
with
notes,
that'd
be
great.
I
I
commented
on
it.
A
Oh
I'm
just
commenting
or
writing
a
note
on
the
etsc
issue.
I
I
commented
on
this
today.
We
they
were
missing
one
more
comcom
review.
I
have
given
that
comcom
review
of
plus
one,
so
we
should
be
good
to
go
or
they
should
be
good
to
go.
If
other
folks
want
a
plus
one,
please
feel
free,
but
yeah.
I
think
that
I
think
that
should
be
resolved
at
this
point.
A
A
Nice
teamwork.
There
is
also
the
node.jshe
team,
which
is
an
in
extremely
inactive
team.
From
what
I
can
tell
one
of
the
members
said
they
don't
care.
A
I
believe
previously
there
was
a
minus
one
from
a
team
member
last
year,
but
it
was
someone
who
is
not
like
hasn't
con,
contributed
to
anything
in
the
org
and
they,
they
basically
say
said
they
would
like
to
stay
a
member
of
the
org
to
watch
which
they
can
do
without
being
a
member
of
the
org,
which
is
what
the
result
of
this
would
be
and
and
they've
they've
not
been
active
in
the
last
five
years.
A
Yeah,
I'm
generally
plus
one
on
this.
I
I
don't
have
any
issue
with
it,
but
yeah
feel
free
to
go
ahead
and
build
your
own
opinion.
E
The
node.js
he
team,
I
think
like
in
that
one
everybody
is
chimed
in
saying
it
was
fine.
E
E
A
E
A
E
Open
it
in
the
admin,
repo
and
yeah
it
was
like.
I
was
like
good
idea.
We
just
need
a
volunteer
who's
gonna,
you
know
actually
help
to
do
the
audits
rich
mentioned
that
he's
been
doing
them
kind
of
like
ad
hoc,
but
like
no
promise
on
when
they
get
to,
but
the
issue.
Okay,
so
I
I
will
add
the
same
comments
as
I
had
the
other
one.
Michael,
we'll
close
this
one
out
by
removing
team
myco
will
open
issue
in
admin
repo
to
cover
larger
audit,
and
then
what
can
that
issue
can
go
on?
A
Goes
cool,
I
don't
see
any
anything
else.
Does
anyone
else
have
questions,
concerns,
objections,
etc?.
A
Cool
we
can
move
on
next
issue
is
mentorship
219,
which
is
the
one
that
I
believe
cindy
added.
Do
you
wanna?
Do
you
wanna
present
that
cindy.
B
Sure
so
I
guess
I
had
noticed
an
issue
in
the
community
committee
repo
about
like
the
levels
of
activity
in
hong
kong,
and
I
guess
I
was
thinking
that
well,
we
could
find
someone
to
help
work
on
documentation,
for
I
guess
well,
yeah
just
help
out
with
the
documentation
and
while
that
doesn't
address
the
like
level
of
engagement,
which
you
also
pointed
out
in
the
issue,
perhaps
like
good
documentation,
leads
to
other
good
things
happening
as
well.
That's
my
thinking,
but
yeah.
D
B
Don't
know
if
that
actually
solves
your
problem
and
in
addition
I
don't
know
like
I
guess
if
we
find
someone
to
help
out
with
documentation,
I
don't
know
if
you
want
to
do
that
in
the
capacity
of
like
mentor
mentee,
in
which
case
that
means
someone
has
to
sign
up
to
be
the
mentor
or
like
if
you,
if
we
just
found
someone
who
knows
some
documentation
already
like
had
to
do
that,
then
they
might
not
need
that
much
guidance.
C
B
I
was
thinking
they
could
just
like
show
up
to
meetings
and
just
get
caught
up
with
like
the
with
what
people
are
talking
about,
and
then
the
level
of,
like
guidance,
necessary
from
comment
members
would
be
like
low.
That's
just
like
unsolicited
help,
if
that,
if
that
helps
you
guys
or
y'all,
then
like
yeah,.
A
Absolutely,
I
think,
that's
a
a
good
idea.
I
I'm
relatively
for
this.
Perhaps
myself
and
joe
as
the
like,
the
the
people
who
are
like
representing
well
joe,
are
you
hold
on?
Are
you
you're
the
cpc
representative
to
the
con
or
to
the
cop
for
the
comcom
yeah?
So
the
two
of
us
do
we
need
to
reelect
that
at
some
point
I'm
I'm
realizing
that
I
don't
I
I
don't
know
if
we
need
to
if
we
have
a
process
for
that.
Anyway.
Sorry,
that's
that's
a
process
discussion
that
can
happen.
E
F
C
E
A
A
So
I
think
that
will
be
the
time
we'll
have
to
double
check,
but
just
like
when
that
election
happened,
I
yeah
it
will.
You
know,
have
to
check
that
and
see
but
yeah.
Sorry.
I
didn't.
I
absolutely
derailed
the
discussion
here.
That's
another
topic
that
we
can
should.
A
That'd
be
good.
I
also
think
it
might
be
worth
it
to
see
if
we
can
michael
build
some
kind
of
thing
like
an
action
to
run
these
or
to
have
these
run
automatically.
A
Yeah
and
like
it
could
create
it,
create
the
poll
and
everything
like
yeah
it
could.
It
could
basically
do
a
lot
of
this
for
us,
and
just
we
don't
like.
I
know
for
both
of
us,
the
tsc
and
comcom.
It's
like
a
thing,
and
it's
like
we
actually
have
to
remember:
there's
calendar
entries
and
stuff,
so
that
might
be
a
good
one.
Anyway,
sir,
I
am
extremely
distracting
from
cindy's.
B
A
A
I
I
think
that
there
are
like
I
can
definitely
point
to
specific
places
of
like
oh,
we
need
to
work
on
this
or
oh,
we
need
to,
like
you
know,
make
sure
all
this
stuff
is
like
actually
accurate,
because
there's
like
stuff
that
just
doesn't
exist
that,
like
we
said,
exists
and
then
in
practice
it
doesn't
so
that
kind
of
stuff
might
might
be
helpful
to
to
get
someone
to
to
work
on,
and
then
I
I
think,
or
to
work
with
to
like
help
them
get
involved
and
work
on,
and
then
I
also
think
for
docs.
A
That
might
be
an
interesting
one.
I
think
we
should
wait
on
that
pending
the
discussion
that
joe
benn
and
myself
and
ethan
ethan
era
would
have
yeah.
I
think
that
that
might
be
a
good
good
direction
to
go,
though
yeah
cool,
any
any
opposition,
or
I
guess
anything,
any
other
kind
of
comments,
questions
thoughts
on
this
one.
A
Cool,
I
guess
cindy,
what
would
what
would
next
steps
from
us
be.
D
It's
just
gonna
more
or
less
be
the
standard
mentorship
process.
Tierney
you've
gone
through
it
before.
If
you're
going
to
take
the
lead,
we
can
just
set
up
a
meeting
and
figure
out
what
you
know,
types
of
skills
and
and
attributes
of
said
mentee
should
have
and
then
we'll
we'll
find
one
or,
if
joe
wants
to
take
the
lead,
we
can
do
that
with
jeff.
A
G
A
Sounds
good
yeah.
I
like
this
idea,
thank
you
for
I
I
wouldn't
have
thought
of
it,
but
I'm
glad
you
thought
of
it.
I
appreciate
it
cool
next
next
agenda
committee
committee,
mentorship
initiative,
so.
A
Okay,
so
this
is
just
a
generic
like
if
someone's
interested,
if
a
working
group,
initiative
or
team
is
interested,
help
get
help
here.
Basically,.
B
Yeah,
so
I
guess
I
when
I
made
the
issue
I
intended
for
it
to
be
included
with
the
previous
agenda,
and
I
think
we
had
talked
about
like
the
timing
of
it.
But.
C
B
The
automation
picked
it
up
and
added
it
to
this
week's
agenda,
but
it
seems
like
there
has
been
a
decision
made
about
how
we're
going
to
go
forward
with
that.
So.
A
Awesome,
yeah
cool:
do
you
think
the
cc
agenda
label
can
be
removed.
A
Or
should
it
stay
on
for
for
future
meetings
too?
I
can.
I
can
take
it
off.
Okay,
cool,
I
just
wasn't
sure
if
you,
if
you
all
wanted
to
keep
it,
keep
it
on
or
not
cool
excellent.
With
that
we've
hit
the
end
of
our
our
agenda,
any
other
agenda
things
I
I
have
something
outside
of
the
agenda.
If
we're
not
for
not
missing
anything.
G
No
just
doubling
back
on
the
election
conversation,
I
created
an
issue
michael
shared
an
issue
in
the
chat,
although
I
think
it
may
have
just
been
to
me.
G
Issue
that
I
had
created
the
issue
and
the
issue
it
was
march
of
last
year,
so
we're
kind
of
you
know
it's
at
it.
G
So
you
know
we
can
we
can
spin
that
up
soon
and
go
through
that
process.
Cool
sounds
good.
Let
me
ask
two
before
we
move
on
related
to
the
com
com.
Mentee.
If
I
understood
the
conversation
tierney
were
you
suggesting
that
it
could
be
related
to
the
doc's
work
as
well,
or
would
that
be
a
different
mentee
program.
A
I
I
think
that
would
be
a
different
one
like
I.
I
would
assume
that
if
we
wanted
to
have
a
mention
for
that
this,
what
would
be
worked
on
that
would
be
different.
This,
the
the
the
requirements
and
requests
for
that
would
be
different
than
someone
working
on
hong
kong,
stuff.
G
Well
then,
maybe
before
we
start
to
go
down
the
comcom
mentee
path,
maybe
you
and
I
can
just
get
together
and
brainstorm
some
ideas
that
we
think
on
them.
Okay,.
A
The
other
thing
I
have
michael,
is
there
weird
sorry
I'm
looking
at
it.
I
had
a
pr
open
from
compcom
and
someone
just
commented
the
name
of
the
branch
on
it
is
there.
E
B
E
A
Okay,
the
automatically
removed
thing
is
not
what
we
have.
We
have
asked
them
if
they
want
to
say
if
they
want
to
stay
and
if
they
plan,
if
they
say
yes,
they
are,
they
stay
the
the
problem
with
that,
I
know
why
we
did
that
it
was
to
be
more
inclusive
of,
like
you
know,
people
who
have
flexible
times
and
stuff
or
other
other
things
like
that.
A
It
turns
out
that's
a
loop
where
people
will
just
say
yes
right
and
then
yeah
that
happens
so
either
either
saying
like
up
yes
up
to
once,
and
then
you
know
if
that
activity
is
not
continued,
automatically
removed
or
modifying.
That
is
something
I
I
think
we
should
consider
I'm
happy
to
submit
a
pr
for
that
phrasing.
Where
is
what
would
this
be
under?
What
is
is
that
governance,
michael
yeah,.
E
B
E
E
A
A
E
A
B
A
A
No
it's
somewhere
here,
I
don't
know
where
I'll
have
to
find
it,
but
yeah.
No,
that
exact
phrasing
is
in
section
three
establishment
of
the
community
committee,
which
I
I
am
probably
going
to
spend
some
time
on
then,
like
I
there's
even
someone
who's
leading
a
working
group
who
I've
messaged
multiple
times
who
just
hasn't
responded,
and
I
like
it's,
been
a
while
and
yeah
it's
just
like.
We
need
to
to
do
do
stuff
with
that,
so
yeah
yeah
totally
totally.
A
E
G
So
I
I'm
finding
in
the
charter
tierney
section
three
membership
is
for
six
months.
The
group
will
ask
on
a
regular
basis
if
the
expiring
members
would
like
to
stay
on
so.
A
That's
so
that
that
is
roughly
what
I've
done,
that
that
is
specifically
what
I've
said
or
that's
what
I've
looked
at.
I've
not
looked
further
down.
Yeah
I've
not
like
gone
further
down.
I
honestly
might
end
up
building
some
tooling
to
do
this.
Just
so
like
it
does
it's
not
on
an
individual
but
yeah.
A
The
the
I
guess
we
have
to
a
standard
come
come
motion.
I
guess
that
would
be
the
a
motion
to
remove
people.
No,
but
so
the
this
text
is
actually
incorrect.
There
there's
two
contradicting
our
statements
in
it.
There's
a
comic-con
member.
It
may
be
removed
from
the
comcom
by
voluntary
resignation
or
by
standard
comcom
motion,
but
it
also
also
says
that
they
may
be
automatically
removed
if
they
attend
less
than
that.
The
meetings
and
don't
don't
participate
in
discussions
and
does
not
participate
in
common
votes.
A
Yeah,
so
the
the
there
is
a
contradiction
in
the
charter,
which
is
unfortunate
and
that
contradiction
also
might
exist
in
the
tst
charter.
Well,
I.
E
F
F
A
Yep
yep,
that
makes
sense
yeah.
I
guess
I
will
follow
up
I'll,
have
to
do
a
query
or
something
to
see
who's
been
inactive
and
and
who,
because
I'm
sure
that,
like
there's
a
few
people
who
have
commented
in
something
but
yeah,
there's
there's
not
a
ton
who
are
actually
particularly
active
in
the
project
right
now.
A
So
I
thank
you
for
that
link.
I
will
see
if
I
I'll
investigate
this,
because
I
unfortunately
I
think
doing
this,
which
I
think
is
the
right
thing
to
do-
would
probably
cut
our
membership
significantly,
which
makes
sense,
but
is
also
unfortunate,
so
yeah.
A
Yep
yeah,
I
think
we'll
have
just
us
three
actually
as
active
members,
but.
A
A
Yep
yeah,
so
I
I'll
talk
about
this
and
I
also
I
don't
think
I
will
like
I'm,
not
gonna
make
a
pr
without
talking
to
people
first
without
peeing
people
and
saying
like
you've.
You
know
this
is
a
thing
yep,
I'm
not
gonna
like
just
pr
you
out
but
like
this
is
a
thing
so
yep,
okay,
all
right,
we're
we're
roughly
a
time
but
yeah.
That's!
That
is
a
thing.
So
cool
thanks!
Everyone
for
another
comcom
meeting.
I
will
catch.