►
From YouTube: Education SIG (October 19, 2022)
Description
Meeting minutes: https://docs.google.com/document/d/1Lt8uGpiMFfgws8VF36xtTMaJAeHufha-7Dqz1tjrPGY/edit
A
A
A
B
D
A
E
Sure
so,
link
to
the
agenda
and
notes
document
is
there
if
anyone
like
to
look
at
the
details,
but
the
two
primary
tasks
right
now,
first
and
foremost,
is
getting
the
materials
Matrix
organization
defined.
That
will
happen
by
the
end
of
this
week.
The
first
draft
there
is
a
working
meeting
tomorrow
that
everyone's
invited
to
attend
it's
at
9
00
a.m.
Eastern
time
I
did
send
out
a
invite
to
the
entire
mailing
list.
So
hopefully
you
got
that
if
you
can
attend
and
you're
interested
in
contributing.
E
Please
do
so
if
you
cannot
attend
and
you
have
strong
feelings
about
anything.
Please
add
your
feedback
into
the
spreadsheet
document,
which
is
also
linked
from
here.
This
document
is
a
dependency
for
a
number
of
tasks
across
different
sections,
so
it
is
incumbent
that
we
get
it
wrapped
up
at
least
the
initial
version
of
it
wrapped
up.
E
The
other
thing
we're
doing
is
in
an
effort
to
hit
crowbe's
deadline
date
of
December
1st
for
having
the
plan
together.
So
we
can
give
it
to
the
folks
at
the
TAC.
We
are
working
on
the
various
items
to
refine
that
plan.
The
Milestones
objectives
timelines.
Some
budget
items
all
that
good
stuff
to
to
more
fully
flesh
out
the
details
and
and
try
and
put
a
sentence
of
a
schedule
together
for
what
we
believe
we
can
accomplish
next
year.
C
I
will
be
there
tomorrow
for
that
spreadsheet
workout
on
the
spreadsheet
I
have
put
the
personas
that
we're
trying
to
hit
so
now,
thanks
for
putting
in
that
sort
of
Matrix
style.
That
makes
a
lot
of
sense,
so
we
should
be
able
to
literally
paint
it
red
in
the
spots
where
any
Persona
is
not
hit,
which
would
be
nice
to
see.
B
A
F
At
least
that
is
a
former
curriculum
and
topics
point
of
view
actually
covering
yeah
multiple
of
the
teams
that
we
actually
already
have
in
The
Matrix
and
then
yeah
like
I,
said
at
least
we
have
a
budget
and
a
plan
of
approach.
We
might
need
to
adapt
it
according
to
what
will
be
the
yeah,
the
outcome
of
the
stream,
one
of
course,
but
yeah.
That
is
at
least
something
we
can
work
with
for
now
and
I.
Think
alsoever.
F
We
discuss
as
a
group
that
this
should
be
yeah
the
focus
for
us,
at
least
as
an
MVP
yeah,
anything
else
or
extras
that
we
can
well
extend
the
proposal
and
make
modifications
as
we
go
but
yeah
to
get
going
and
to
deliver
something
that
we
think
as
a
group
really
needs
Focus.
Well,
it's
the
security
development
profile,
sort
of
saying
security,
tester
profile
and,
like
I
said
when
we
classify
the
The
Matrix
and
we
have
more
better,
defining
the
personas
and
the
teams.
F
We
can
correlate
that
all
back
I
mean
it's
just
topics
and
categories
that
are
yeah,
overlapping
and
reused
anyway
yeah,
and
we
also
had
a
couple
of
discussions
actually
with
you
know,
parts
of
the
other
group.
It
was
more
on
the
outrock
base
because
we
were
actually
reading
through
the
stream
one
and
stream
two,
because
they
are
yeah
very
connected
and
close
to
each
other
and
there
we
were
indeed
also
a
bit
yeah
finding
out
what
actually
yeah
it's
defined
there.
F
We
actually
already
well
made
the
Assumption
that
is
going
to
be
the
security
knowledge
framework
platform,
actually
where
we're
going
to
provide
and
host
and
make
all
the
material
available.
So
it
looks
a
bit
redundant
then
to
to
have
yeah
two
separate
places
where
we're
going
to
store
the
information
because,
for
example,
the
other
thing
that
we
were
thinking
about
also
to
make
the
well
generic
approach
for
all
the
materials
like
markdown
formats,
with
images,
etc,
etc.
That
it's
easily
also
consumable.
F
You
know
by
other
platforms
and
and
other
you
know:
yeah,
open
source
platforms
right
and
also
the
capability
we
thought
of
maybe
making
an
API
endpoints
that
you
can
also
through
the
API
again
actually
grab
that
type
of
content
but
yeah.
So
I
I
think
that
was
also
up
for
discussion
actually
as
an
action
point
here,
yeah
if
it
makes
sense
to
indeed
move
that
1.2
also
to
stream
too.
B
C
Well,
so
for
section
three,
our
dependency
was
this
Matrix,
but
I
think
we're
in
a
very
good
spot.
Now
we
know
the
Persona,
the
professional
Persona
that
we're
going
to
Target
the
hardest
first,
so
with
appsec,
now
I'm
going
to
define
a
sort
of
rewards
category
for
each
of
those
training
levels
that
we
know
that
we're
covering
and
with
that
we
can
start
another
discussion
around
what
the
rewards
and
incentives
are
so
rewards.
C
A
E
Anybody
has
any
questions
about
that;
they
want
to
clarify
today.
We
certainly
can
but
we'll
we'll
talk
in
a
lot
of
depth
tomorrow
at
the
meeting
about
that
again.
Just
if
you
can't
make
the
meeting
and
you
have
opinions
or
feelings,
you'd
like
to
share
Now's
the
Time
or
or
forever
hold
your
peace
at
least
till
the
next
version.
C
B
B
Yeah
I'm,
sorry
I,
don't
want
to
unnecessarily
block
unit.
Moving
on
to
the
next
agenda
item:
I:
just
don't
I
don't
get
it.
So
can
you
be
a
little
bit
I'm?
Can
you
be
a
little
bit
more
specific
about
the
kind
of
feedback
that
you're
looking
for
in
this
spreadsheet
and
in
this
Matrix
I'm?
Sorry
sure?
No.
E
No
worries
not
a
problem
at
all,
so
we
we
we're
talking
about
all
these
educational
materials
that
we're
going
to
do
all
these
cool
things
with.
If
we
can't
organize
those
materials,
then
we
have
no
way
of
of
executing
on
the
rest
of
the
of
the
the
tasks.
So
what
we're
trying
to
do
on
the
spreadsheet
is
put
together
version,
1.0
of
a
way
for
us
to
organize
and
categorize
the
existing
materials
that
are
out
there
today,
what
they
contain,
who
they
apply
to
information
like
that
determine
you
know
what
these
categories
are.
E
The
personas
is
an
example
of
that
areas
of
of
coverage
or
domains
is
another
thing
that
we're
talking
about
basically
a
way
for
us
to
determine
okay.
This
is
this
is
how
this
is
what
we've
got
today
and
if
we
look
what
we
have
today,
based
on
this
categorization,
that
we've
done,
we
will
see
what
areas
we
have
covered
and
what
areas
that
there
are
gaps,
and
one
of
our
future
tasks
is
to
do
a
gap
analysis.
E
But
this
is
also
going
to
be
used
when
we're
putting
together
the
curriculum
for,
if
you're,
if
you're
a
QE
person,
here's
courses
that
would
apply
to
you
if
you're
a
developer.
Here's
course
that
apply
to
you.
If
you
are
a
new
security,
professional
here's
courses
that
would
apply
to
you
if
you're
just
interested
in
language
stuff,
here's
courses
that
would
apply
to
you
we're
trying
to
to
make
we're
trying
to
set
the
stage
for
us
to
be
able
to
break
this
information
down
from
a
couple
different
perspectives
and
group.
A
It's
awesome,
thank
you.
So
a
specific
example
would
be
Randall
wrote
a
lab
about
how
to
defend
against
cross-site
scripting
in
SKF,
so
we
have
this
artifact.
So
we
put
that
entry
into
the
tape
our
little
Matrix
and
we
say.
Oh,
this
is
a
lab
and
we
pick
that
box.
This
applies
to
these
types
of
people,
the
personas
that
might
be
interested
in
that,
and
then
we
say
this.
A
You
know
there's
the
theme
of
this
content,
the
security
domain
that
applies
to
is,
you
know,
actual
software
development
or
secure
coding
practices
we
figure
out
what
the
mean
implies
to
and
then
the
lab
is
designed
for
entry-level
beginner
people.
We
take
that
boxes,
we're
walking
across
the
Matrix
categorizing
everything
so
that
we
can
start
to
eventually
add
some
new
automation
that
hey
we
need
a,
we
need
a
SRE
class
class
and
we
hit
a
button
and
it
kind
of
barfs
out.
A
A
G
E
C
C
E
G
C
Yeah
that
sounds
good
and
I
guess
sort
of
on
a
broader
level
gym.
What's
his
last
name:
executive,
Linux,
Foundation,
everyone.
Yes,
thank
you.
Sorry.
He
was
in
London
on
Monday
and
we
talked
a
little
bit
about
this.
I
sent
him
an
email.
I
was
like
we
need
as
soon
as
we
get
this
gaps
analysis.
We
need
to
be
reaching
back
out
and
I
need,
like
Linux.
I
need
like
him
to
tell
everyone.
C
B
G
F
G
So
what
really
kind
of
happened
is
that
we
already
kind
of
have
an
SKF
team
that
kind
of
already
operates.
It's
not
like
super
big
or
anything,
but
basically
we
would
make
sure
that
it
like
still
stands
and
we
merge
things
and
stuff
like
that.
So
we
kind
of
so
there
are
parallels
with
certain
things
because,
like
in
a
way,
we
kind
of
feel
that
Glenn
already
curates
a
library
for
SKF.
G
B
F
Currently,
we
have
it
already
and
like
Randall,
says
I'm
doing
well,
also,
of
course,
for
all
the
SKF
material
that
we
currently
have
I
do
the
quality
and
assurance
and
making
sure
that
the
level
and
the
material
is
correct.
What
is
being
put
in
there
review
it
also
working
together
with
some
other
projects
right,
because
it's
yeah
not
only
our
material
that
we
use
and
have,
but
also
from
other
projects.
F
Basically,
it's
also
there
I
see
collaboration
and
well,
sometimes
even
help
the
projects
myself
to
add
the
missing
pieces
of
material
there
and
the
gaps.
So
for
us,
when
we,
you
know,
went
over
our
list
and
also
we
looked
a
bit
over
the
other
streams.
Then
we
well
actually
thought
like
the
1.2
yeah.
It
sounds
like
a
sort
of
a
duplicate,
or
at
least
I
think
it
should
be
in
string
number
two.
E
So
I
completely
understand
where
you
guys
are
coming
from
on
this
I'd
like
to
look
at
it
from
a
little
bit
of
a
different
perspective.
When
we
broke
down
this
sigs
mandate
or
how
we're
going
to
cover
stream
one
we
broke
into
the
three
sections
and
the
first
one
was
The
Collector
curate
content.
The
second
was
expanding
the
materials
and
the
thorough
was
rewards
and
incentivizing
and
I
think
for
us
to
to
actually
meet
what
stream
one
intends
to
do.
E
We
need
to
make
sure
that
we've
got
that
scoped
out
appropriately
across
the
sections
I
I.
If
we
want
to
move
this
section
two
and
and
we
all
decide
it's
the
best
way
to
go,
I
think
it's
fine,
but
I
believe
that
that's
a
core
tenant
of
what
sexual
moment
was
intended
to
to
accomplish
was
collecting
and
curating.
The
content,
if
SKF
is,
is
the
right
mechanism
for,
for
that
to
happen.
I
have
no
problem
with
that.
E
G
That
does
I
think
I.
Think
what
we
were
talking
about
more
is
that
librarian
role
I,
don't
think
that
it
should
impede
section.
One
collecting
and
curating
content
is
just
I
think
that
we
technically
kind
of
already
have
something
of
like
a
system
to
serve
that
library
and
role
within
SKF.
So
there's
no
problem
in
like
collecting
and
analyzing
what
we
have
and
adding
stuff
I,
just
think
that
we
kind
of
already
have
that
librarian
role
like
it's
not
necessary,
because
it
would
kind
of
create
a
friction
Point
within
SKF.
E
C
Want
to
highlight
an
engineering
anti-pattern
that
we're
falling
into
right
now,
so
no,
we
have
not
made
any
architectural
commitment
to
SKF
and
it
has
no
bearing
on
our
ability
to
move
forward
with
curation
at
this
time.
It
is
a
decision
that
we
can
make,
but
it's
not
a
road
blocking
decision
on
getting
a
basic
architecture.
Together
we
can
host
that
anywhere
and
we
can
host
that
multiple
places.
G
G
And
not
only
that
we
have
a
lot
of
capabilities
to
do
this.
Furthermore,
we've
discussed
things
like
you
know.
In
section
two,
we
have
things
like
videos,
blogs,
webinars.
All
of
that
stuff
can
be
used
to
enrich
the
content
that
we
have
in
SKF,
so
it
would
make
sense
that
that
API
would
get
you
know
like
expanded
in
SKF.
So
therefore,
we
can
like
even
the
labs
we've
been
talking
about
how
we
can
use
the
labs
to
enrich
sections
of
content.
G
C
G
Question
I
think
I
think
that
the
goal
from
when
I've
talked
to
like
Dave
David,
is
really
to
provide
an
experience
like
a
learning
experience
yeah,
because
the
information
is
free,
you
can
go
out,
you
can
read
it,
but
there's
not
really
a
way
to
engage
with
the
information
and
I
like
I
think
that's
to
a
sense.
The
problem
point
that
it's
very
dry.
G
C
So
we
are
going
to
need
a
platform
to
be
hosting
this
on
and
that
is
going
to
need,
like
ux,
UI
sort
of
design
around
it
and
I.
Don't
so
I,
don't
think
these
additional
personas
that
we've
budgeted
for
right,
the
librarian,
those
are
not
about
hosting
a
platform.
Those
are
about
curating
content,
so
I,
don't
think
that
it
yeah
I
think
that
those
are
still
incredibly
synergistic.
But
what
we
need
to
have
now
is
a
realistic
budget
about
what
it's
going
to
look
like.
C
We
need
to
have
a
realistic
idea
of
what
the
scope
is
that
we're
going
to
be
able
to
deliver
inside
of
year,
one
so
with
sko
I,
think
that
makes
the
most
sense
to
move
forward,
but
I'm,
not
the
only
one
on
this
call,
but
yeah
I
think
it's
a
non-limiting
factor
and
if
the
limiting
factor
is
human
bandwidth,
then
let's
budget
in
for
that.
So.
G
We
we
actually
have,
as
I
said,
an
SKF
team,
it's
not
big,
but
so
far
the
last
few
months
it's
been
working.
So
that's
really.
Why
also
for
us
to
align
our
resource
purchases
with
what
like
open
ssf.
So
that
way
we're
not
duplicating
work
yeah
because,
for
example,
there's
a
lot
of
things
and
we
actually
have
a
UI
ux
designer
in
SKF
as
well,
and
we're
actually
looking
to
expand
on
that.
We
have
two
other
volunteers
that
have
yet
to
show
up,
but
but.
B
C
A
A
One
of
our
goals,
in
section
one
I
believe,
is
to
get
our
corporate
membership
to
donate
content.
So
if
intel
gives
us
a
set
of
training,
we're
gonna
again
going
to
need
to
figure
out
how
to
Federate
that-
and
you
know,
if
we
have
a
single
presentation
layer
or
even
if
we
have
multiple
ways
to
tickle,
that
API
that's
fine,
but
we
just
need
to
understand
that
everything
isn't
going
to
be
existing
completely
within
the
the
SKF
system
itself.
A
F
Yeah
indeed,
and
I
think
also,
you
know
no
idea
of
making
it
the
structured
data
and
for
all
the
data
that
we
use
or
import
or
have
in
our
library,
basically
has
the
same
structure
the
same
format.
So
indeed
it
you
know
we
want
to
have
the
materials
on
edx
or
other
platforms.
There's
no
I
say
no
obstacles,
actually
there
right.
F
F
A
So
you
know
as
long
as
SKF
can
provide
if
equivalent
services
I,
don't
think
that
there's
really
a
debate,
but
you
know
if
somebody
felt
very,
very
strongly
enough
to
make
it
a
goal
that
we
need
to
have
some
place
to
go
without
so
Learners
could
see
all
this
information
and
if
SKS
can
serve
that
bill
great,
if
not
great,
there's
no
yeah
I,
let
the
group
does
anyone
have
any
personal
first
question?
Can
SKF
provide
those
similar
capabilities
like
the
LF,
a
certification
platform
and
the
oer
commons.
A
G
G
C
G
For
the
record,
guys,
I
can
come
to
the
next
meeting,
because
we've
been
like
and
I
can
give
you
a
better
rundown
of
like
Services.
If
anyone
is
so
interested,
I
will
I
do
I
am
working
on
a
page
that
breaks
all
that
down
so
you're
interested
you
could,
let
me
know-
and
you
could
know
how
it
actually.
G
C
Yeah,
like
what
I,
what
I
was
gonna
ask
for,
is,
like
I'd
love,
a
like
written
proposal
of
what
exactly
the
elements
we
want
to
highlight
within
this
for
me
personally
as
I'm,
starting
to
engineer
out
a
rewards
and
incentives
design.
It
would
be
very
nice
for
me
to
be
able
to
think
about
embedding
that,
in
whatever
platform,
correct.
G
Using
that
so
and
and
one
of
the
things
just
to
throw
this
out
there,
that
the
marketing
consultant
told
us
was
that
we
should
definitely
consider
you're
putting
more
value
to
the
data,
because
the
data
is
very,
very
good,
like
the
the
stuff
that
we
have
is
is
very
high
grade
stuff,
but
we
kind
of
give
it
out
so
openly
and
it
looks
so
dry
and
like
it's
also
written
not
in
a
very
easy
to
read
format.
So
all
the
combinations
don't
necessarily
work,
so
he
suggested.
G
C
A
But
basically
the
proposal
is,
we
will
adjust
1.2
and
where
it
talks
about
deciding
where
this
material
is
going
or
buying
a
platform,
we
will
explicitly
State.
This
will
be
housed
in
SKF.
We
will
refer
to
that
precise
goal,
number
and
Glenn's
part
of
the
plan
and
then
we'll
still
leave
it
open
that
the
librarian
will
and
the
team
will
provide
feedback
on
potential
services
or
UI
changes
or
whatever
yeah.
C
D
G
D
G
F
E
A
C
B
A
G
A
Sounds
good
and
maybe
we
would
do
some
homework
that
everyone
please
look
at
that
and
if
you
don't
have
feedback
at
least
say
you
know,
plus
one
on
the
search
or
whatever
give
give
something.
You
don't
have
to
write
a
dissertation
there
for
next
meeting.
So
we
at
least
can
move
the
glossary
forward.
C
Yeah
and
just
a
note
for
that,
just
like
little
statement
that
I
made
about
the
gaps
analysis
tomorrow
well,
I
think
right
after
this
meeting,
I
have
some
time
now.
I'm
gonna
write
in
a
little
bit
about
the
Linux
Foundation
jobs
report
for
beginning
and
end,
and
it
gives
us
a
beautiful
little
like
we
now
discreetly
know
what
data
points
we
have
to
tie
together
to
see.
If
we
did
this
well
in
a
year,
cool
that'll.