►
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
All
right,
so,
according
to
the
slack
I,
think
we're
gonna
have
a
pretty
light
call
today,
which
is
okay
because
number
one.
This
section
is
pretty
dependent
on
some
of
the
other
sections
and
by
our
following
meeting
on
October
15th.
We've
got
some
deliverables
that
we'll
need
to
bring
in
and
discuss
so
I
just
wanted
to
start
out
today
on
the
agenda.
Is
there
anything
open
or
new
that
we
do
want
to
discuss
and
I
will
still
leave
us
open
for
discussion
for
the
next
five
minutes
or
so.
C
You
know
just
just
real
quick
when
we
do
have
some
folks
involved
with
GitHub
and
get
lab
within
the
open,
ssf
I'm
wondering
if
maybe
we
should
just
kind.
You
know
like
save
your
for
GitHub
I,
doubt
that's
exactly
the
right
people,
but
maybe
we
should
give
them
a
heads
up:
hey
yeah,.
A
Yeah,
if
you'd
be
able
to
follow
up
on
this,
because
my
contacts
with
GitHub
are
in
the
Deni
section,
but
they're
not
going
to
be
really
useful
for
this,
but
if
I
can
hand
you
a
current
goal
for
the
next
two
and
a
half
weeks-ish.
A
That
would
be
excellent.
Okay,.
C
Yeah
I'm
wondering
should
I
just
if
I
were
to
share
with
them
a
URL.
What
URL
should
I
share.
C
Gotcha,
okay:
do
would
you
mind
throwing
that
in
the
chat
or
where
I
want
to
make
sure
I
use
the
right
one
I'm
kind
of
overwhelmed
with
tabs?
If
that
makes
any
sense,
yeah.
A
C
I
mean
posting
on
GitHub.
Is
you
know
having
your
raw
pointing
to
GitHub
is
great
I
just
want
to
make
sure
I
use
the
right
one
yeah.
C
A
C
C
I'm
feeling
good
today
so
I
I
got
you
all
right.
So
I'll
ask
Xavier
I,
doubt
he's
the
right
person,
but
he
at
least
has
a
shot
of
knowing
the
right.
B
People,
let
me
tell
you
what
I
do
know
about
that.
So
Xavier
told
me
that
he
does
control
the
bug
bounties
at
GitHub,
like
that's
part
of
his
responsibility.
They
also
have
a
lot
of
ideas.
I,
don't
know
if
Glenn
shared
them
yet,
but
this
was
technically
in
a
chat
with
me
and
Glenn
and
Xavier,
but
they
also
have
because
he
typed
out
like
three
or
four
different
ideas
of
how
he
could
work
together.
If
you'd
like
I
could
send
them,
I
could
copy
and
paste
them
or.
A
D
A
Cool,
oh
and
one
quick
note:
we
do
have
one
new
person
on
the
call
today.
So
Aaron
is
on
my
devrel
team
at
sonotype
and
works
as
one
of
our
technical
writers
and
is
really
interested
in
helping
us
build
out
some
of
these
incentivizing
programs
and
better
communication
around
them.
So
welcome
Aaron,
anything
to
say
for
yourself
and
who
is
everyone
else
on
the
call.
D
Yes,
I
think
Sal,
hi,
David
and
Randall
yep
I
work
with
Sal
on
a
Deborah
team
and
have
assisted
in
a
few
other
pieces
of
content
creation
and
I
was
interested
when
Sal
brought
up
working
on
rewarding
and
incentivizing
Developers,
for
which
you
guys
are
currently
working
on
so
yeah
thanks
for
just
we're
just
listening
in
today.
So
that's
happy
to
be
here.
A
Well,
anyway,
David
is
on
mute
now,
but
is
in
charge
of
a
lot
of
the
educational
initiatives
out
of
Linux
foundation
and
developed
the
original
cyber
security
education
through
Linux
foundation.
So
we're
really
having
a
chance
here
to
move
that
work
forward
and
then
Randall
you're,
the
only
one
on
the
call
today
right,
yes,
Randall's
here.
B
A
B
C
Yeah
I
don't
think
that
involves
rewarding
and
yeah
that
that's
more,
the
fixings.
A
D
A
So,
okay,
for
the
moment,
let
me
just
like
literally
keep
this
on
the
side
here
and
I'm.
Gonna
propose
that
back
into
that
1.1
section,
because
this
actually
gives
us
really
good
next
action
statements:
okay,.
B
A
A
Definitely
do
respond
back.
Let's
get
that
engagement
because
we
absolutely
so
there
can
be
two
tandem
goals
here.
So
I
think
we're
gonna
need
David
a
separate
contact
by
you
to
GitHub
get
lab,
if
possible,
to
confirm
what
certifications
they
have
or
may
have
coming.
If
there's
anything,
we
can
co-coordinate
around
developing
new
content
equally
important.
C
C
As
far
as
the
code,
ql
I,
don't
know
is
Xavier
still
the
right
person.
We
can.
C
D
B
B
A
Never
go
to
the
right
section
in
this
one
where's
that
mobilization
so
I,
just
gotta
go
to
files,
don't
I.
A
A
Sorry
this
is
a
really
stupid
thing
to
spend
our
time
on
so
I'm
gonna
bring
up
the
1.1
at
the
end
of
this
call
and
make
sure
that
we
put
it
into
the
right
section,
but
for
now
there's
just
a
couple
of
things
that
I
want
to
make
sure
that
we've
gotten
Awareness
on,
because
we're
going
to
have
to
start
moving
by
about
November.
A
A
A
But
let's
do
a
little
bit
of
thinking,
perhaps
not
on
this
call,
but
asynchronously
around
the
proposed
cyber
security
and
Matrix
Focus.
So
this
is
at
a
very
high
level
what
I
would
recommend
or
provided
recommendations
for
the
different
sort
of
technical,
Stacks
technical
sort
of
focuses
that
we
should
have
so
I'd
say:
supply
chain,
Cloud
security,
data
security
as
the
top
three
priorities
for
year,
one
because
those
are
our
sort
of
biggest
efforts
and
also
the
ones
that
we
have
some
of
the
most
content
around
mid
priority
training.
A
A
B
A
That's
what
I
was
thinking
I'm
wondering
do
we
want
to
move
and
also
there's
just
going
to
be
like
way
more
support,
generally
from
a
couple
of
the
contacts
that
I
have
around
this
appsec?
A
So
do
we
want
to
move
that
into
a
priority
for
the
first
section,
and
is
there
anything
that
we
would
want
to
remove
from
this
in
order
to
have
that
Focus
I
personally
always
want
to
keep
in
supply
chain
and
Cloud
security
because
I'm
a
kubernetes
developer?
That's
why?
B
A
Yeah
so
I
think
I'm
going
to
move
this
as
a
just
an
idea
for
now,
but
I
do
think
so.
An
action
item
that
we
should
have
is
coordinate.
A
With
section
one
to
confirm
certification,
Pathways,
existing
certification.
A
Right,
Within,
These,
stacks
and
I
will
take
that
up
and
make
sure
that
we're
doing.
B
A
Yeah,
okay
and
well:
let's
just
absolutely
make
sure
that
that's
a
column
in
that
as
well,
so
that
it's
easy
to
search
through
that
we
can
identify
where
trainings
and
what
are
certs
but
I
think
that's
the
only
a
lot
of
this
is
so
contingent
on
part
one
and
two.
If
those
mobilize
these
get
mobilized,
that's
my
only
discussion
point
for
this
part,
and
we've
only
only
got
three
sections
to
cover.
Is
there
anything
that
we
want
to
add
or
consider
to
this
3.1.
A
Okay,
incentives-
really
this
cannot
be
done
yet
we're
still
in
the
space
of
identifying
the
incentives
within
and
outside
of
LF.
I
think
that
this
is
really
going
to
come
again
in
tandem
with
developing
out
what
are
those
certain
courses
that
exists,
so
this
isn't
even
on
the
docket
for
us.
A
We
can
put
a
timeline
to
this,
but
I
want
to
I
said
before
that
we
should
identify
these
gaps
by
around
like
December
of
this
next
year,
so
I
think
we're
out
on
that
and
again
this
could
be
a
short
reading
because
there's
not
as
many
people
on
board
but
for
the
rest
of
these
most
of
these
really
need
to
wait
for
a
couple
of
months
until
the
other
sections
move.
I
did
want
to
give
a
very
brief
update.
A
However,
on
oh
it's
in
section
two,
so
I
wanted
to
take
a
moment
to
talk
about
a
coordination
that
we
could
have
with
section
two,
which
means
I'll
have
to
bring
it
up.
Okay,
just
a
second
which
one
is
it.
B
B
A
Cool
okay,
good
to
know
I
would
never
do
get
back
on
mobile
okay,
but
for
so,
let's
do
two
last
quick
action
items
for
this
meeting.
A
I
want
to
do
a
quick
discussion
around
how
section
two
and
three
will
be
interrupting
in
a
specific
location,
so
alternative
Delivery
Systems
for
Content,
so
I've
reached
out
to
Major
League
hackathons,
who
have
recently
created
an
entire
pathway
of
training
that
takes
you
from
a
you
know,
early
to
mid
career
developer,
to
a
specific
training
and
hiring
inside
of
SRE,
which
is
a
very
similar
educational
pathway.
What
best
we'll
need
for
cyber
security,
so
what
I've
asked
them
to
deliver
us
by
October
14th?
A
The
next
meeting
is
an
overview
of
exactly
what
that
looks
like
how
that
coordinated
with
the
open
source
projects
and
what
the
success
and
failure
rates
were
of
that
I
would
then
like
to
have
a
consideration
with
what
we
can
do
to
be
providing
them
upfront,
educational
resources
and
certifications
that
allow
us
to
identify
those
who
might
be
good
sort
of
pathway.
Candidates
for
that
mlh,
really
the
benefit
of
mlh.
A
The
big
reason
why
I
need
them
to
be
engaged
to
this
is
that
education
is
worth
nothing
unless
they
become
valuable
contributors
and
maintainers
and
mlh
has
really
got
the
pathway
and
the
support
system
readily
defined,
to
be
able
to
make
sure
that
there
are.
You
know
people
on
keyboards
with
mentorship
in
place.
A
So
when
we
come
into
the
next
meeting,
I'd
love
to
discuss
a
little
bit
about
what
that
looked
like
for
their
SRE,
what
it
could
look
like
in
sort
of
the
final
end
of
the
pipeline
for
this
education,
some
of
the
key
statistics
that
we
would
want
from
that
and
then
start
really
thinking
about
what
this
educational
looks
like
from.
You
know,
starting
at
beginning
of
content,
to
actually
getting
potentially
a
cyber
security
identified
maintainer.
That
would
be
my
ideal
class
to
create
so
there's
no
more
actions
to
take
on
that.
A
C
A
Okay,
so
the
last
thing
that
I
want
to
briefly
go
over
love
the
idea
by
the
way,
yes
I
know
it's
a
dream
of
Dreams
I've
had
for
many
years
and
now
now
I'm
gonna
do
the
rewards
incentives
to
get
it
done.
I'm.
A
So
in
this
section,
I
believe
it's
down
at
the
end,
so
I
think
what
we're
talking
about
here
really
makes
sense
around
working
with
well
at
least
GitHub
and
stack
Overflow.
So
give
me
just
a
quick
second
to
submit
this
PR.
A
D
C
D
C
Okay,
no,
no
okay,
so
I've
I
have.
While
we
were
talking
about
that
I've
emailed
Xavier,
CCU
and
I've
contacted
Brian
to
see
who
who
in
get
lab.
We
should
contact
because
I'm
not
sure
who
that
is,
I
really
have
no
indeed
for
it
indeed,
and
for
LinkedIn,
but
let's
start
with
GitHub
gitlab,
and
we
do
eventually
need
to
contact
indeed
and
LinkedIn
at
least,
and
if
there's
other
I
mean
there's
many
many
job
boards,
I'm
sure
so
I
just
know
who
to
where
those
seem
like
the
obvious
places
to
start.
A
There
yeah
yeah,
let's
focus
on
the
major
players.
It's
definitely
get
GitHub
really
involved
and
then
see
what
the
trickle
off
effect
is
of
that.
So,
just
coming
back
to
this
quick
discussion,
we
were
having
sorry
I
like
threw
it
in
my
notes
here
so
foreign.
A
A
Yeah
and
who
was
the
key
contact
again:
Xavier
yeah
right,
okay,
perfect.
A
A
Which
1.10
goal.
A
So
I
know
cool
I,
think
that
that
is
it's
always
so
satisfying
when
readme
documents
are
able
to
merge,
so
I
think
right
now,
we've
got
our
next
steps
here
should
be
updated.
Now.
A
So
apologies
on
skipping
around
here,
but
we're
happy
with
the
proposed
security
plan.
A
I'm
going
to
reach
out
to
well
I'm
going
to
be
providing
an
overview
of
mlh's
pipeline
for
OSS,
engagement
and
I.
Think
at
this
moment
in
time
we're
pretty
clear
aside
from
the
email
that
you've
already
sent,
David
and
sort
of
the
ongoing
discussion,
we
should
probably
have
with
Xavier,
probably
through
that
section
one
though
that
fits
perfectly,
and
that
was
really
a
dead
space
that
we
didn't
have
immediate
next
steps
on
so
that
closes
the
loop
I.
A
Think
it's
a
good
time
to
reach
back
out
and
say,
like
we're,
not
just
interested,
we
really
really
care,
and
we've
already
set
aside
budget
to
get
this
done.
So,
let's
figure
this
out
cool
I'm
happy
with
this
I
think
we're
good
to
go.
A
Are
there
any
last
things
that
we
want
to
cover
from
section
three
or
I
think
we're
set?
We
can
discuss
on
slack,
get
some
of
these
aspects
moving
but
make
sure
you
do
tune
in
on
October
14th,
because
I
think
that's
going
to
be
a
really
interesting
chat
and
that's
going
to
set
us
off
cool
I'm,
all
good
cool.
Thank.
C
A
Right
well,
thank
you
all
for
joining
in
Erin.
Thank
you
for
coming.
It's
usually
double
this
amount
of
people,
but
that's
okay.
It's
a
light
week!
Next
time,
though,
I'll
make
everyone
come.
This
was
just
a
real
like
quick
overview.
So
thank
you.
Everyone
I
hope
you
have
excellent
Fridays.
Oh
not
true.
I
do
have
one
more
thing
for
everyone.
Sorry,
okay,
we're
running!
This
isn't
a
personal
note,
but
you
should
all
be
excited
about
this.
A
The
security
slam
is
live
where
we
are
getting
as
many
projects
as
we
can
within
cncf
to
have
100
security,
compliance
and
they've
already
started,
including
kubernetes
and
I've,
been
going
in
and
yelling
at
everybody
about
their
security
stances
on
their
githubs
and
their
slacks
and
enjoying
it
very
very
much
so
we
will
be
seeing
some
improvement
in
that
space.
I'm
excited
to
show
the
stats,
but
the
stats
will
improve
more.
If
everyone
knows
about
it,
so
do
send
that
out.
A
A
They
get
recognized
and
really
creating
that
sort
of
healthy
Community
level
support
around
cyber
security
and
open
source
that
hasn't
traditionally
been
there
and
doing
my
favorite
thing,
which
is
making
sure
that
in
some
way
the
maintainers
get
paid.
So
do
let
people
know
about
this,
because
this
is
my
way.
This
is
my
like
best
way.
So
far,
personally,
if
I
can't
say
myself,
this
is
the
best
thing
I've
done
so
far
to
complete
my
operation
say.
Thank
you
to
maintainers.
A
Good
work,
thank
you,
I'm
super
excited,
but
that
is
all
for
today.
So
look
at
it
check
it
out,
see
if
you
want
to
get
engaged
but
I'm
happy
to
close
this
out
and
give
you
all
a
little
bit
more
of
your
Fridays
back.