►
From YouTube: 2021-05-10-Next 10 years of Node.js
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
So
welcome
to
the
node.js
next
10
meeting
for
may
10
2021
we'll
follow
the
agenda
that
we
had
tagged
in
the
issue
and
the
issue
was
number
66.
If
anybody
wants
to
go
look
for
that
one
all
right,
so
we
have
a
couple
things
on
the
issue.
One
was
the
survey
to
get
feedback
from
the
needs
of
the
the
nodejs
constituencies
and
we
have
that
data.
A
So
I
think
we
should
spend
some
time
going
through
that
we
also
have
on
the
agenda
the
key
technical
areas
brainstorm,
which
we
generated
a
list
and
we've
got
some
more
feedback
from
collaborators
because
we
posted
it
to
collaborators.
So
that's
great,
and
then
we
have
the
next
10
years
of
collaborators,
but
I
think
probably
the
first
two
will
keep
us
busy
for
for
the
meeting.
A
A
So
there's
two
files
here:
one
is:
the
survey
results
the
sort
of
raw
survey
results.
Let
me
open
that
up.
If
I
can,
is
there
a
way
to
do
that?
No,
I
didn't.
A
Am
I
going
to
be
able
to
do
this
easily?
I
should
be
able
to
maybe
view
file
here.
We
go
okay,
so
rachel
put
this
together
for
us,
which
was
great.
The
first
thing
is,
is
it
you
know,
thanks
to
everybody
who
participated,
because
we've
got
20
over
2
800
responses,
which
is
really
fantastic,
chose
the
level
of
interest
in
this
and
sort
of
that?
That's
really
good.
A
A
You
know
people
identified
with
multiple
library
package,
authors,
core
node.js,
core
maintainers
was
a
smaller
number
and
organizations
with
investment
in
node.js
was
also
a
smaller
number,
but
actually,
I
think
those
are
also
pretty
good
numbers.
If
you
look
at
like
how
many
core
maintainers
we
have,
you
know,
that's
expected
to
be
a
smaller
number
and
even
when
you
look
at
an
organization
you
know
there's
maybe
going
to
be
fewer
of
those,
so
that
actually,
I
think,
is
a
pretty
good
coverage.
A
Now
that
the
follow-on
question
was
like
okay
did
we
miss
any
any
constituencies
and
it
sounds
if
we
looked
at
that
we
did
get
about
five
percent
of
people
who
said
we're
not
in
one
of
those
and
95.
So
we
got,
I
think,
pretty
decent,
but
maybe
it's
worthwhile
now
flipping
over
to
look
at
what
the
we
had
a
question
which
was
like,
if
you
were
part
of
these,
which
ones
were,
were
you
so,
let's
maybe
we?
You
know
why?
D
A
A
D
A
It's
it.
Could
I
guess
I
like
it's
like
you
know
you
could
be
an
investment.
I
think
the
way
I
read
that
one
a
little
bit,
though,
was
like
hey,
I'm
I'm
a
company
and
I'm
actually
investing
in
node
as
a
strategic
part
of
my
you
know
what
I'm
going
to
run.
My
business
on
that
that
I
can
see
being
is
a
little
different
than
I'm
operating
a
cloud-based
infrastructure,
a
cloud
offering
so
that
that
might
be
worth
let's
we
can
kind
of
go
through
them,
but
yeah
that
one
direct
end
users
application.
A
D
That
sends
out
to
me.
We
definitely
didn't
cover
that,
because
there
was
another
one
later
further
down
and
said
teaching
node,
which
I
feel
like
like
education,
maybe
would
be
right
constituency
there
that
would
sort
of
group
their
needs
right,
because
I
imagine
teachers
and
students
sort
of
want
the
same
sort
of
support
and
resources.
A
B
D
We
would
need
to
separate
that
out
right,
because
the
assumption
would
be
that
their
goal.
While
they
may
take
a
different
view
on
the
topic,
their
goal
would
be
to
best
support
their
application
developers,
or
you
know,
library,
authors
on
their
team.
So
in
theory
they
should
have
the
same
goals
and
same
needs.
A
A
A
View
game
developers.
D
Were
learning
I
would
sort
of
consider
that
part
of
application
development,
but
I
but
I
have
to
say
from
the
game
developers
I've
talked
to
they
don't
necessarily
see
themselves
in
the
same
bucket
as
like
a
web
service,
you.
D
Yeah
or
or
any
of
the
things
we've
listed,
I
imagine
that
might
be
just
a
self
like
how
they
see
themselves.
You
know
right
the
greater
scheme,
but.
A
D
D
D
They
also
support
you
know
our
java
ecosystem.
They
support
a
bunch
of
other
like
cloud
security
aspects
that
have
nothing
to
do
with
node
right,
so
they're
sort
of
this
umbrella
that
that
spans
a
lot
of
different
things
and-
and
I
wouldn't
like
if,
if
I
was
thinking
about
how-
where
I
would
have
slotted
some
of
those
folks
in
this
this
conclusion,
I
don't
know
that
they
would
fit
anywhere
other
than
maybe
organizations
with
investment.
A
D
Yeah
and
if
we
think
about
the
like
collab
space,
we're
kicking
off,
that
is
actually
the
point
there
is
that
we
haven't
reached
some
of
those
types
of
folks
through
the
existing
channels
right
and,
and
we
think,
there's
value
there,
so
so
maybe
calling
that
out
on
the
project.
D
I
know
I
I
wish
mary
was
here,
because
I
know
we
had
talked
about
trying
to
figure
out
how
to
get
more
involved
in
triaging,
and
you
know
supporting
the
security
aspects
and-
and
it
was
you
know,
brought
up
sort
of
as
a
partnership
that
we
might
engage
with
with
our
security
teams
and
then
integrate
with
the
node
ecosystem.
D
And
to
me
just
having
that
conversation
makes
it.
You
know,
I
think,
pretty
clear
that
there
is
another
constituency,
because
otherwise
we
would
have
just
said:
oh
okay,
yeah,
we'll
we'll
do
it.
You
know
as
as
sort
of
the
next
right
let's
get
through,
but
but
that
wasn't
quite
enough,
I
think
so.
Can
you
hear
me
hey.
B
A
Okay,
you
know
that
that's
good,
so
yeah,
no,
I
I'm
I'm
leaning,
let's
get
through
the
rest
of
the
list,
but
then
it
sounds
like
we
definitely.
We
probably
have
a
few
to
add
so
developers
from
africa.
So
we
haven't
actually
based
things.
Geogra,
geography,
wise
either.
Is
that
something
we
would
want
to
consider
different
requirements
for
different
geographies
or.
D
One
of
the
main
things
I
would
think
out
of
this
answer,
and
there
was,
I
think,
one
other
one
that
related
to
geography
but
would
be.
D
We
have
a
really
strong
presence
like,
for
example,
I
know
I
chatted
with
some
folks
who
were
building
some
stuff
in
china
and
the
the
the
chinese
community
had
totally
torqued
the
express
docks,
because
there
wasn't
enough
support
for
the
you
know
what
need
to
be
done
there
in
in
the
chinese
language
specific
version-
and
you
know
if
there's
similar
endeavors
in
the
node
project
like
knowing.
That
would
be
good,
whether
or
not
that's
a
constituency
as
we've
defined
it.
I
I
kind
of,
don't
think
so
I
think
that's
just
a
you
know.
B
Right,
the
one
caveat
I'd
say
there
is
that
there
are
going
to
be
certain
things
that
are
represented
in
different
constituencies,
especially
ones
that
are
not.
You
know
like
north
american
or
eurocentric
specifically
like
china
is
gonna,
have
certain
you
know,
firewall
things
that
come
up
and
that
might
be
impactful
to
them.
B
Africa
is
going
to
have
different,
like
compute
needs
and
also
there's
a
lot
more
people
who
are
starting
and
growing
rather
than
people
who
are
like,
rather
than
a
majority
of
like
in
the
us
like
senior
or
you
know,
mid-level
developers
and
so
making
like
there
is
going
to
be
a
correlation
to
that,
and
I
think
making
one
potential
benefit
to
collecting.
B
That
information
is
seeing
both
cert
like
survivorship
bias
and
seeing
what
areas
we're
missing,
that
we
might
not
be
collecting
the
input
on
and
which
would
allow
us
to
go
and
get
that
information
more
targeted.
B
That
we
cover
them.
So
I
agree,
and
I
think
what
part
of
what
I'm
saying
is
it's.
I
agree
that
it's
not
a
separate
developer
constituency.
What
I,
what
I
think
it
is
is
it's
I
I
assume
y'all
have
seen
the
the
world
war
ii
airplane,
where
there's
the
survivorship
bias
and,
like
certain
areas
of
the
plane,
are
never
shot
or
don't
ever
come
back
with
bullet
holes,
because
when
those
areas
get
shot,
they
get
cut
off
and
the
plane
doesn't
come
back.
B
It
very
much
feels
like
that
in
that
having
having
that
data
and
knowing
hey
we're
we're,
you
know,
if
we're
talking
to
someone
in
africa
or
someone
in
china
or
someone
in
russia
or
wherever
making
sure
that
we're
actually
hearing
from
a
non-trivial
part
of
the
people,
there
helps
us
ensure
that
what
we're
looking
for
in
the
constituencies
is
actually
reflecting
the
global
needs,
rather
than
the
needs
just
right.
North
america,
because.
B
Be
different
needs,
like
you
know,
I
I
think
we
will
probably
see
higher
windows
usage
in
africa
than
we
will
in
america
like
there's
going
to
be
less
people
using
linux
and
mac
in
africa
than
there
will
be
in
america,
and
so
that
there
will
be
a
disproportionate
number
of
disproportionate
bias.
B
Outside
of
you
know,
right
africa
to
those
two,
those
other
systems,
whereas
that
might
not
be
as
well
represented
yeah
if
we
don't
make
sure
we're
actually
doing
additional
outreach,
make
sure
we're
getting
coverage
for
africa
or
other
countries
like
different
subject,
different
country,
but
same
problem
right.
B
A
B
I
don't
know
if
it
means
we
should
do
additional
work
right
now,
but
I
do
think
that
that's
a
good
thing
to
keep
in
mind
for
the
future.
A
A
B
A
I
want
to
re-word
that
one
yeah
I
agree
like
it's
it's,
because
that
core
maintainers
actually
has
perhaps
you
know,
maybe
should
be
like
node.js,
maintainers
or
node.js.
A
A
good
okay
requirements,
management.
A
A
A
A
C
B
Sorry
go
ahead.
I
was
gonna
say
on
that.
One
is
that
potentially
an
area
that
we've
left
out
around
like
aiml
as
a
use
case,
is
that
potentially
something
that
we
haven't
considered.
D
I
would
have
yeah
too
specific
so,
like
I
was
thinking
the
same
kind
of
thing
for
the
one.
Well,
a
couple
of
the
ones
up
up
further
up
were
like
yeah.
A
Yeah-
and
I
could
see
it
coming
out
through,
like
the
other
thing
we
have
on
the
agenda-
is
looking
at
strategic
technology
areas.
I
could
see
it
coming
out
as
one
of
those
and
then
you
know
when
you
look
at
the
constituencies
through
the
lens.
You
know
so
say
you
say
you
know.
Supporting
aiml
with
javascript
is
key
to
the
successive
node.
You
can
then
look
through
that
lens
to
say:
okay,
what
does
that
mean
to
developers?
A
F
A
Application
developer.
Well,
I
think
we
have
application
developer
coverage
right.
That's
application,
developer,
yeah,
alternative
javascript,
runtime
maintainer.
A
D
A
Yeah,
the
only
way
I
could
see
is
like
if
it
was
chakra
or
you
know,
spider
monkey.
But
again
it's
pretty
specific.
It's
just
pretty.
A
B
B
A
Right,
if
it's
in
that
category,
then
they've
explicitly
said
well,
I'm
using
something
else
so
and
and
the
other
one
is
small
enough,
so
yeah,
I
think
teaching
note
at
university
level.
I
think
we
talked
a
bit
about
that
that,
like
maybe
we
should
come
up
with
something
for
education,
so.
B
Yeah,
I
agree
with
that.
There's
I
have
a
friend
who's,
an
amazon
person
who
apparently
is
in
one
of
the
first
courses
that
like
or
was
in
the
first
course
it
some
the
college
in
washington
who
their
teaching
note
is
a
part
of
that
course
and
so
yeah.
I
think
that
we're
gonna-
maybe
you
know
as
a
refresh
of
their
old
java
c,
plus
plus
cs
courses,
so
I
think
we
might
start
seeing
this
more
and
that's
probably
a
good
thing
to
plan
for
for
the
next
10
years.
A
A
What
I
think
yeah
that's
what
I'm
saying
kind
of
like
they're
covered
by
an
application
developer
and
then,
when
we
look
through
the
lens
of
technologies,
it
may
be
that,
like
supporting
api
services,
is
a
strategic
thing
or
not,
but
yeah
instrumentation
developers
working
to
create
application,
runtime
diagnostic
tools.
A
A
Because
it's
it's,
you
know
things
like
the
async,
local
storage
and
even
async
hooks
and
the
things
around
you
know
around
the
debug
ability
and
all
that
is
kind
of
it
is
kind
of
a
different
audience
but
yeah.
Maybe
it's
that
the
apms
are
really
like
a
company
who's,
providing
something
to
that
application
operator
audience.
B
D
A
Right,
it's
like
you,
can
you
know,
because
there's
a
whole
bunch
of
application
development
tools
as
well,
and
you
could
make
the
same
argument
for
calling
out
well
like
people
who
do
build
tools
for
application
developers
right
and
it's
probably
better
to
say.
Well,
no,
the
people
were
serving
are
the
operators
and
the
developers
there
happen
to
be
companies
who
build
tools
for
them
and
they
may
they
may
be
the
ones
who
are
most
active
in
helping
us
understand
what
the
operators
and
the
developers
need
or
want.
B
The
the
one,
the
one
additional
caveat
I
might
have
there
is
there
is
a
smaller
but
different
constituency
than
apms,
where
it's
people
who
are
building
this
kind
of
tooling.
That
is
not
built
on
node,
but
it
is
something
node
would
hook
into,
and
I
don't
know
if
that
is
distinct.
B
The
this
is
something
like
like
open
tracing
or
whatever.
It's
called
that
kind
of
stuff
might
be
distinct,
but
I
don't.
I
have
a
feeling.
Wes
probably
has
a
stronger
feeling
of
where
that
would
fit
than
than
I
do.
D
I
mean,
I
think
I
it's
a
good
point
and
we
we
leverage
that
you
know,
and
I
think
the
way
we
do
it
is
just
as
like
again
librarian
off
an
operator
view.
Like
library,
author
and
operator
view
it's
not
it's
not
going
to
be
anything
meaningfully
different
than
than
those
two
constituencies
would
already
represent
right
like
so.
I
think
it's
safe
to
say
that,
like
that
could
actually
to
michael's
point
earlier
about
the
other
things
is
that
could
be
just
a
technology.
D
Maybe
we
say
like
we
say
you
know
a
a
technology
that
we
think
is
worth
you
know
supporting
and
investing
in
would
be.
You
know,
tracing
hooks
right
or
something
you
know
yeah
and
then,
and
then
it
just
so
happens
that
that
serves
two
or
three
different
constituencies,
but
I
don't
think
those
folks
would
see
themselves
outside
of
that
that
box
in
the
constituency.
A
It
kind
of
comes
back
to
we
could
slice
this
up,
but
if
we
get
to
30,
it's
not
useful
right.
So
I
I
come
from
the
it's.
The
operators,
we're
really
trying
to
serve,
there's
some
other
people
who
will
be
trying
to
help
them,
but
we
don't
want
to
necessarily
say
application
operators
and
then
people
who
help
application
operators
and
then
application
developers
and
people
help
application
developers
right.
So
I
think,
for
even
though
they
might
be
slightly
different.
A
Where
I'm
coming
from
okay,
so
instrumentation
developers
so
yeah,
I
think-
and
I
think
we'll
see
very
much
from
some
of
the
other
data
that
that
will
be
pretty
strongly
recommended
as
a
need.
So
I
don't
think
we're
going
to
forget
that
either
command
line
tools
and
applications.
D
A
D
A
Now,
I
guess
I
guess
purely
so.
If
we
looked
at
command
line
tools
and
applications,
that's
one
thing:
I'm
not
sure
that
covers
scripting
users,
quite
as
well,
though,
because
like
if
I
want
to
write
myself
a
quick
script,
I'm
not
writing
a
library,
but
I
actually
want
to
do
something
and
instead
of
writing
it
in
bash,
I'm
going
to
write
it
in
node.
A
B
D
A
A
D
E
A
F
One
thing
you
might
want
to
be
clear
when
you
say
one-off
scripts,
there's
two
different
use
cases
we
saw,
especially
since
for
the
esm
loader
we
don't
support
extension-less
files.
There
are
people
who
want
to
run
things
without
extension
than
people
who
are
fine,
running
things
with
extensions,
and
there
is
a
very
clear
divide
actually
on
this.
What
do
you
mean
with
extensions.
F
And
that
is
one
of
the
main
complaints
that
people
have
about
it
and
they
don't
like
that.
We
removed
it
because
web
assembly
forward
compatibility.
D
Yeah,
I
have
a
question:
do
you
do
you
see
having
dealt
with
those
folks
and
like
under
trying
to
understand
their
needs?
Have
do
you
see
them
more
as
end
users,
or
do
you
see
them
fitting
into
one
of
these
other
constituencies
like
when
they
come
with
that
need?
Presumably
they
have
these
stronger
opinions
from
doing
something
in
the
ecosystem
like
what
what
do
they
fit,
mostly
in.
F
So
usually
they
are
people
a
little
bit
of
both.
Unfortunately,
these
are
it's.
When
you
fit
in
both
categories,
you
start
to
fall
apart
if
you're,
just
a
direct
person
running
a
different
author's
application.
We
don't
see
complaints.
F
However,
if
you
are
the
author
of
the
application
and
you
want
to
distribute
it
without
having
an
extension,
we
do
see
complaints
because
they
want
to
be
able
to
distribute
single
files
rather
than
packages.
D
So
it
sounds
to
me
like:
maybe
we
should
make
sure
the
library
author
use
case
covers
non-traditional
deployment
methods
of
some
sort
right.
So
really
what
you're
saying
there
is
they're,
a
library,
author
and
they're
not
publishing
to
npm,
where
some
of
this
stuff
is
covered,
they're
like
shipping,
a
file
in
a
tarball
or
like.
Well,
I
guess
that's
basically
an
npm,
I
don't
know
some
other
like
they
put
it
on
and
you
curl
curl
bash
it
or
something
right
like
what
like
is
that
covered.
D
Okay,
so
I
see
that,
to
be
honest,
I
see
that,
like
it's
in
my
lo
my
home
directory
repo,
I
see
that
as
end
user
and
I
I
fit
into
that
category-
I
have
quite
a
bunch
of
things
that
are
just
node
scripts.
In
my
you
know
bash
profile,
but
then
I
see
the
other
aspect
that
you
were
describing,
which
is
people
who
want
to
distribute
it
to.
D
You
know
to
others
as
the
library
author
again,
even
if
they
don't
fit
into
the
traditional
one,
which
is
like
publishing
to
the
npm
registry,
which
I
think
is
a
valid
use
case
in
some
ecosystems.
I'd.
A
Okay,
so
I
think
that's
we're
thinking
we
just
again:
maybe
we
try
and
make
sure
we
improve
our
descriptions
to
to
cover
people,
so
they
see
they're
in
those
those
two
decision
maker
on
use
of
technologies,
tokyo,
cto,
technical
executive.
B
The
the
one
thing
I'll
say
is,
I
know,
I
know
who
I
hate
it,
but
I
know
that
the
it
decision
maker
thing
is
like
still
huge
and
it's
basically
how
a
lot
of
technology
gets
bought
and
if
we
don't
have
a
category
that
I
guess
relatively
directly
associates
that
that
that
kind
of
person
is
different
than
like
a
node.js
developer.
B
Perhaps
we
want
to
list
roles
there
as
well,
in
addition
to
like
the
actual
organization
type
since,
since
it
is
like
as
x,
person
who's,
not
necessarily
a
direct
like
javascript,
no
dev.
A
B
B
A
A
Okay
and
I'm
thinking
that
you
know
we're
probably
on
this
first
question,
gonna
pretty
much
use
your
time.
We
might
spend
a
little
bit
of
time
working
on
what
that
revisions
to
these
would
be
while
it's
fresh,
okay,
scripting
users.
We
already
talked
about
good
morgan,
support
and
issues
analysis,
so
I
think
that's
operators,
in
my
mind.
D
A
G
Would
that
be
something
like
who
link?
I
I
don't
know
some
kind
of
the
w3c
that
will
try
to
to
bring
or
to
follow
the
javascript
standard
to
import
into
node.js,
maybe
so,
which
is
maybe
not
only
including
people
which
are
really
working
into
node
core,
but
maybe
just
people
would
think
that
fetch
would
be
great
to
be
nerd
or
don't
know
which
other
stuff
maybe
it's
for
me.
I
understand
it
like
that,
but
maybe
I'm
wrong.
D
We
were
going
to
change
that,
I
think,
should
cover
it
and
if
not,
we
should
work
to
make
sure
that
it
does,
because
I
think,
no
matter
what
in
the
end,
the
goal
is
to
have
a
collaboration
between
what
is
built
in
node
and
what
is
specified
in
you
know
tc39
or
you
know,
w3c,
and
if
it
makes
sense
to
have
a
collaboration
there.
I
think
the
the
group
that
is
being
served
is
really
the
like
people
working
on
note
right.
It's
making
sure
that
the
spec
is
going
to
work
in
node.
D
G
A
But
not
not
saying
that
we're
doing
everything
we
should,
but
more
than
we
used
to
that.
I
still
worry
that
we're
going
to
forget
about
them.
If
we
don't,
if
we
just
say
because,
like
the
core
collaborators,
they
couldn't,
you
know
it's
sort
of
like
the
standards
and
what
this
happened
a
while
back
is
kind
of
like
the
standards
groups
did
their
own
thing.
The.
B
A
A
Yeah
yeah
yeah
that
perfect
yeah.
Okay.
So
let
me
go
back
to
the
yeah
this
one
right
here:
perfect,
yeah,
okay!
So
let's
we
wanted
to
add
students,
education,.
D
B
D
And
put
underneath
it,
you
know:
teachers,
students,
curriculum,
you
know,
yeah,
I
think,
just
in
general,
like
university
programs,
would
be
a
really
interesting
constituency
like
I
know,
I
follow
a
fair
number
of
folks
on
on
twitter,
who
are
just
educators,
trying
to
figure
out
how
to
structure
their
their
comp,
sci
programs,
and
it's
like
choosing
node
versus
java
or
whatever.
As
the
the
platform,
I
think
would
be
an
interesting
lens
to
look
at.
You
know
even.
A
G
She
should
be
splitted
between
really
education
as
a
school
and
university,
and
people
who
learn
who
try
to
learn.
Maybe
they
want
to
change
from
one
job
to
another,
because
it's
not
really
the
same
target
at
on
one
side,
it
will
be,
let's
say,
a
bootcamp
or
two
three
months
really
to
learn
into
one
technology.
On
the
other
side
in
a
school
or
university,
they
will
have
an
overall
multiple
technology
framework
and
language.
So
for
me
I
think
it's
not
really
exactly
the
same
between
those
two
kind
of
of
people.
A
A
B
Like
boot,
camps
and
stuff
are
a
subset.
Also,
the
you
know,
college
universities
outside
of
the
you
know,
direct
comp
side,
teaching,
there's
a
lot
of
other
stuff
that
comprises
that
four
years,
which
fills
that
out,
like
it's,
not
four
years
of
node
in
javascript
learning,
right.
C
Did
we
lose
the
certification?
I
I
well
yeah,
I
didn't
know
what
they're
calling.
B
The
the
one
the
one
concern
I
have
there
is:
if
people
have
some
kind
of
node.js
certification
they
might
sell,
select
into
that
one.
That's
not
necessarily
what
we're
looking
for
in
in
that.
So
are
we
looking
for
people
operating
those
programs
like
certification
programs?
Are
we
looking
for
people
who
have
taken
them.
D
I
actually
think
it
should
cover
both.
So
my
thinking
on
that
is
we
what
we,
what
we
would
want
to
provide
is
validation
to
employers,
to
college
programs,
to
all
sorts
of
things
that
people
learned.
D
You
know
the
the
content
and
so
whether
or
not
it's
so
it
might
be
that
that
a
certification
provider
comes
to
the
project
and
says
here's
the
certification
test,
I'm
planning
on
doing.
Is
it
good
right
and
that's
one
aspect
and
then
and
then
having
you
know
it
verified
by
the
core.
You
know
the
node
core,
like
could
be
a
service
that
we
you
know,
I
mean
I
say
service,
just
thinking
you
know
out
loud
here,
but
but
you
know,
the
idea
would
be
that
we
want
to
make
sure
those.
D
You
know
people
aren't
providing
scam,
certifications
right.
It
would
be
a
valid
thing
for
the
the
us
to
say
we
we
help
with
also
on
the
other
side.
Somebody
saying
I
want
to
be.
You
know
I
want
to
validate
to
my
employer
that
I
learned
node
right
and
that's
two
sides
of
the
same
coin,
because
you
know
we
might
say
well.
We
worked
with
an
opengs
foundation
to
validate
the
certification
process.
D
B
D
Programs,
programs,
programs-
I
don't
know
how
to
restructure
it
but
sure.
A
D
Posture
or
whatever,
could
it
be
people
who
are
involved
in
the
life
cycle
of
security
issues,
because
it's
not
just
that
they
necessarily
manage
it?
It's
also
people
who
respond
to
security
issues,
for
you
know
companies
from
like
a
pr
everything
from
a
from
a
like
incident
response
to
actual
code
to
pr
involvement,
like
I'm
sure,
there's
a
bunch
of
stuff
involved
in
the
life
cycle
of
responding
to
security
incidents.
D
G
Do
we
include
people
doing
pen,
tests
and
stuff
like
that
into
security
issue,
or
is
it
a
separate
stuff
because,
after
all,
I
hope
in
most
of
the
case,
that's
it's
people
doing
pen
testing,
which
first
found
the
issue
and
not
a
black
hat,
so.
A
A
And
we're
out
of
time.
So
if
people
can
remember
like
there
was
a
few
notes
about,
we
want
to
expand
on
some
ones
as
well.
If
you
can
remember
and
just
jot
some
notes
in
there
I'll
do
my
best
to
remember
as
well
later
on
today,
but
if
you
can
add
your
thoughts
I'll
then
take
that
and
put
it
into
a
pr
as
a
revision
based.
A
You
know
a
first
revision
based
on
the
feedback
we
got
here
and
I
guess
next
time
we
will
continue
on
looking
at
the
rest
of
the
survey
data,
but
that
was,
I
think,
a
really
good
discussion.
Some
really
good
feedback,
and
you
know
again,
if
anybody's
watching
who
participated
in
the
survey.
Thank
you
very
much
for
for
doing
so.
A
Otherwise,
we'll
see
everybody
in
the
next
meeting
in
two
weeks,
yep.
Okay,
thank
you.