►
Description
Meeting notes: https://docs.google.com/document/d/1ttqkcYPmYZyqvtkaHs92bx2UeVUiXDhuzP-0WbP11Fw/edit#heading=h.7o2ubzl5z39r
C
B
C
D
D
D
B
E
E
E
E
B
Real
quick,
just
more
FYI
for
the
best
practices
badge
we're
doing
some
updates
to
the
various
libraries.
You
know:
updating
for
rails,
six
to
seven
that
sort
of
stuff
got
somebody
helping
out
and
for
the
security
fundamentals
course.
That
seems
you
know,
that's
it's
continually
used
and
we
have
a
very
small
updates
on
you:
can
I'm
going
to
put
a
link
to
various
poll
requests
to
to
see
to
see
some
of
those
things
that
are
being
either
discussed
or
actually
intended
for
merge
there?
F
E
B
Well,
let's
see
I
was
in
Japan
and
I
got
to
announce
that,
in
in
Japan
and
you'll,
be
shocked,
shocked
to
know
that
folks,
in
Japan
thought
it
was
pretty
nice
to
be
able
to
have
something
written
in
their
own
language
who
knew
so
I
I
think
I
I,
at
least
you
know
in
terms
of
just
interacting
personally
with
folks
I
think
it
was
very
exciting.
People
were
very
happy
about
it.
B
I
do
want
to
just
give
a
quick
heads
up
on
the
Japanese
translation
in
order
to
I
mean
many
of
you
who
are
familiar
translations
already
know
this.
They
froze
it
at
a
particular
version
in
order
to
do
the
translation,
so
they
have
a
slightly
older
version,
I
mean
not
hideously
out
of
date,
and
it's
and
it's
useful,
particularly
you
know,
if
you're
in
if
you're
Japanese
is
better
than
your
English.
B
You
don't
want
me
doing
translations.
That's
for
sure.
The
the
goal,
though,
is
just
to
make
sure
that
it's
available
the
current
plans
to
put
into
the
same
repo
I
guess
we
could
have
put
it
in
a
different
repo
I
thought
it
might
be
easier
just
to
put
it
all
in
one
place,
but
you
know
so
that's
that's
the
current
plan.
I.
Don't
think!
We've
actually
done
that,
yet
we
were
bumping
up
against
the
new
year
so
but
I
think
that
that's
that's
the
current
plan,
so
questions.
B
We
go
yeah
and
it
is
taken
that
way.
But
but
in
all
seriousness
you
know
we
would
certainly
be
interested
in
other
translations,
particularly
those
where
a
lot
of
folks
don't
I,
think
the
challenge
for
Japanese
in
particular
was
there's
a
lot
of
Japanese
speakers
who
are
technical
but
don't
speak
English.
So,
while
I
think
that's
true
for
many
many
cultures
in
some
English
knowledge
is
more
common
than
others,
so
I
think
we're
open
to
almost
anything,
but
especially
where
it
opens
up
situations
where
it
wasn't
even
possible
before.
A
E
E
G
Yeah,
let
me
do
a
quick
one
on
SKF
yay,
so
actually
around
all
the
boys
myself,
we're
currently
still
working
and
progressing
on
the
the
new
platform,
basically,
so
we're
still
brainstorming
and
building
some
features.
Etc.
Also,
together
with
some
of
my
colleagues
at
Ing,
we
fixed
around,
like
20
25
laps
and
for
the
Java
and
node.js
Labs.
We
actually
also
pushed
through
the
whole
new
styling
because
they
were
still
using
the
old
styling
of
all
the
labs.
B
G
B
G
It
will
come
but
yeah
it
was
also
a
holiday,
so
we
thought
you
know
what.
Let's
do
something
that
at
least
we
can
do
ourselves
without
the
help
of
anybody
else.
So
that's
why
we
we
worked
on
the
other
plan,
the
architecture
and
also
fixing
the
labs,
but
we
will
definitely
come
back
to
you
pretty
soon
to
have
that
discussion.
Yes,
well.
B
We
all
agree
that
that's
not
a
long-term
solution,
so
the
current
plan
is
that
the
fundamentals
course
we're
going
to
be
embedding
HTML
comments
to
make
it
easier
to
just
you
know:
yank
in
the
current
version
and
update
and
link
to
Labs
exactly
what
those
HTML
comments
will
look
like.
Don't
know
in
some
sense
it
doesn't
matter,
it's
whatever
is
convenient
for
them,
but
the
idea
is
to
make
it
easier
to
integrate
into
the
future.
B
B
E
B
Yeah
and
and
and
I
guess,
I'll
since
we're
all
here
together,
I
would
ask
hey
you
know.
Working
on
a
spec
is,
is
all
nice
as
a
starting
point,
but
I
would
encourage
as
soon
as
possible
to
go
sit
down
and
try
to
add
a
few
and
work
it
out
because
I've
seen
many
specs
written.
You
know
like
like
many
PL.
What's
the
the
plans?
Never
never,
let's
just
survive
after
first
contact
with
the
Enemy,
so
you
know,
plans
often
have
to
get
changed
after
you
try
to
actually
do.
H
B
H
E
All
right
did
Spyros
or
regime
or
Laurent.
Join
no
okay,
well
see
about
getting
an
update
on
where
we
are
with
inventory
and
scorecards
and
All-Star
for
the
team
for
the
education
Sig.
We
have
mostly
locked
down
the
plan
I
plan
on
presenting
it
to
the
TAC,
the
second
call
of
the
month,
which
would
be
the
24th.
E
So
we
have
a
little
bit
of
time
to
make
some
adjustments.
In
the
interim,
there
have
been
two
interesting
updates
from
the
education
Sig.
First
off
Jay
and
Christine
have
kicked
off
and
are
leading
a
Dei
sub
group.
That's
going
to
be
focusing
in
on
diversity,
equality
and
inclusion
topics,
particularly
in
the
plan.
They
had
a
really
great
first
meeting
what'd.
You
have
about
eight
folks
on
the
call
Jay.
I
Yeah
yeah
we
had
about
eight
folks
on
the
call
also
we
had
a
couple
of
news
folks
that
I,
don't
believe
were
even
members
right
or
or
even
attending
a
lot
of
the
working
group
meetings
or
so
of
some
groupings
across
the
entire
openness
and
stuff.
So
we've
had
a
couple
of
new
individuals
that
came
in
because
they
heard
about
what
we
were
doing
and
that
was
exciting
as
well.
Yeah.
E
I
You
are
a
part
of
it,
then
you
are
a
part
of
I.
Think
our
next
meeting
I
got
to
look
at
this.
We
actually
we
we
on
the
calendar
I
mean
I.
Think
you
just
update
the
calendar
somewhere
on
the
calendar.
Next
to
me
is
like
I,
do
have
to
look
at
the
spread
over
the
next
week
or
two
I'm
just
coming
back
myself,
but
yeah
at
the
next
meeting,
come
on
in
and
and
and
be
a
part.
I
Oh
yeah,
absolutely
so
what
we
identified
you
know,
especially
with
the
plan,
is
that
this
is
a
small
section
about
the
eni
and
across
the
openness
of
stuff
hell
across
the
latest
Foundation
trying
to
build
up
an
initiative
to
Target
underrepresented
communities,
talk
to
Fred,
more
inclusive
initiatives,
around
education
around
how
we
reach
out
and
educate.
But
now
we
get
those
resources
back
in
to
the
open
ssf
in
general.
I
What
we
said
was
hey:
maybe
this
snippet
needs
to
be
pulled
out,
blown
up
and
made
its
own
thing,
because
this
needs
to
be
spoken
out
louder
than
what
it
is,
so
that
these
underrepresented
communities
and
groups
you're
out
there.
For
instance,
we
had
one
individual
that
joined
the
group,
she's
phenomenal
right
and
she
came
out
of
nowhere,
but
she's
phenomenal,
been
in
security
been
in
supply
chain
been
in.
You
know,
she's
from
an
HBCU
and
she's,
like
I
heard
about
this
from
so
I
decided
to
join.
That's
the
whole
idea
behind
it.
I
Get
out
to
the
smaller
colleges
we
get
out
to
even
high
schools
and
submissions.
We
provide
Avenues
where
there's
educational
opportunities
are
discovered.
We
provide
Avenues
where
we're
identifying
a
lot
of
those
individuals
who
want
to
do
something
bigger
and
I've
apologizing,
because
I'm
going
to
talk
it
since
I'm,
actually
on
the
treadmill,
I
thought.
E
I
But
but
the
idea
is
that
we
take
this
initiative,
we
blow
it
up
and
we
kill
a
few
birds
with
one
stone
one
we
covered
down
on
the
Linux
Foundation,
the
broader
Linux
foundation
and
those
Deni
initiatives.
Two
we
bring
it
into
the
openness
of
stuff
and
those
Deni
initiatives
and
the
three
we
have
that
impact
that
we
want
to
have
inside
of
both
organizations
outward
externally
to
those
colleges
to
those
universities
to
those
other
institutions
and
then
across
all
of
our
many
different
organizations
where
we're
continuing
to
identify.
I
E
One
and
two
on
that
yeah
thank
you
Jay
and
Christina,
then
the
Jay
and
Christine,
and
the
group
identified
a
handful
of
topics.
We
want
to
try
to
fold
back
into
the
plan
in
the
short
term
so
before
the
24th,
when
I
pushed
that
up
to
the
tack
we're
going
to
be
working
on
this
comment
that
she
put
in
there
on
how
we
can
integrate
some
of
these
ideas
back
into
the
plan.
So,
if
anyone's
interested,
we
will
get
the
media
official
meeting
invite
out
for
that
sub
team.
E
E
E
All
right
and
the
second
awesome
piece
of
news
around
the
education
Sig
is
I,
have
a
task
forever
that
one
of
the
actions
of
the
plan
was.
We
were
going
to
talk
to
our
member
organizations
if
they
had
any
training
materials
they
wanted
to
donate
to
the
education
Sig
in
our
ongoing
education
efforts
and
Intel
got
back
to
me
and
on
the
day
before
I
stopped
working
I
got
an
inventory
of
all
the
available
content.
I
I
No
just
just
looking
around
and
poking
and
prodding
and
asking
you,
you
pull
out
a
lot
of
stuff
that
we
might
be
doing
internally
here
at
Microsoft,
even
as
well
that
we
can
bring
into
the
education
sync
and
see
what
we
can
do
with
maybe
marry
up
some
of
the
stuff
from
Intel
with
some
other
stuff
from
Microsoft
somewhere
else
and
kind
of
blow
that
up
a
little
bit.
So
it's
my
vision
is
always
about
that
collaborative
effort.
I
E
Yeah,
we
don't
have
that
list.
Yet
that
is
a
task
of
the
plan
is
to
start
to
go
and
review
our
existing
materials,
so
I'll
be
glad
to
make
I'll
make
sure
that
we
keep
you
in
the
loop
as
we
continue
that
conversation
Jay
and
you
know
any
organization
that
has
a
secure
development
content,
a
secure
supply
chain,
any
kind
of
good
devsec
Ops
devops
materials.
We
would
be
glad
we
would
love
to
have
contributions,
so
don't
just
make
it
about
the
big
guys.
A
E
E
Team
of
people
that
does
secure
development
training
within
Intel
has
for
like
a
decade
and
they
have
a
library
of
materials
that
they
are
interested.
They
are
able
to
share
so
I,
don't
I,
haven't
gotten
the
open
data
or
anything
like
that.
Yet,
okay
and
it'll
be
a
combination
of
like
job
AIDS,
PowerPoints
videos,
potentially
okay,
I.
H
E
H
E
And
what
we'll
do
is
you
know,
as
the
education
Sig
identifies
interesting
content
that
we'd
like
to
explore
more
we'll,
set
up
a
sharing
session
and
then
ultimately
like?
If
we
decide
we
want
all
the
C
compiler
stuff
to
be
donated,
we
have
to
go
through
and
scrub
out
like
Intel
trademarks
and
whatnot
before
that's
actually
passed
over,
but.
E
E
That
openssf
should
be
there
presenting
an
assortment
of
presentations
and
education
materials.
So
if
anyone
is
interested
in
submitting
a
paper
presentation
and
feel
free
to
do
that
on
your
own,
if
you
would
like
assistance,
I'm
glad
to
offer
myself
as
a
resource
I
do
a
lot
of
security
conferences.
So
I'd
be
glad
to
help.
You
refine
your
paper
and,
if
anyone's
interested
in
joint
collaboration,
doing
a
workshop
of
birds
of
a
feather
session
where
you
kind
of
come
in
and
talk
about
a
particular
topic
with
the
audience.
E
But
I
will
be
putting
something
together
around
I'm,
going
to
hit
up
wheeler,
because
I
think
I'd
like
to
talk
about
the
best
practices
badge
and
scorecard
how
maintainers
can
integrate
those
into
their
activities
as
a
more
practical
kind
of
Hands-On
session.
But
if
we're
interested
in
theory
or
whatever
else
I
think
it
may
be
an
SKF
session,
showing
developers
how
to
use
SPF
to
and
begin
their
training
expertise
and
skills.
That
might
be
another
great
session.
E
Awesome
that'd
be
great
I,
think
that
would
be
very
valuable,
yeah
and
I'll
be
saying
the
same
thing
in
every
working
group,
I'm,
a
part
of
so
but
this
one,
especially
because
we're
focused
in
on
helping
the
developers
and
education
I
think
I
feel
very
strongly.
This
group
needs
to
be
strongly
represented
there.
G
E
Okay,
all
right
and
if
you're
interested,
feel
free
to
talk
on
slack
shout
out
on
the
mailing
list,
make
comments
on
the
agenda,
however,
you're
interested
in
engaging
I'm
glad
to
help
coordinate
or
assist
or
co-present
or
whatever
you
guys
want
to
do
all
right
now
to
the
actual
work.
Let
us
talk
about
Issue
102.
E
We
have
agreed
that
we
would
like
to
work
on
source
code
management,
best
practices
guide,
as
our
next
group
task
and
our
let's
see
is
gnome
here
yeah
there
you
are
gnome
had
presented
last
year
that
his
organization
has
put
together
a
starter
and
they're
interested
in
contributing
that
and
how
we
can
build
from
that.
So
I
would
like
to
discuss
Issue
102
and
how
we
can
move
this
particular
little
project
forward.
C
F
E
So
what
we
would
do,
since
you
have
existing
material,
we
would
try
to
find
some
way,
probably
to
put
that
into
our
working
groups.
Repo
or
link
to
it
maybe
make
a
dedicated
like
we
did
with
the
vulnerability
disclosure
guides.
We
made
separate,
dedicated
repos
for
those
and
linked
to
it
off
the
working
group.
E
So
basically
we
would
want
to
get
the
content
into
a
medium
that
the
team
can
start
to
collaborate
on.
So
if
the
material
is
already
in
git,
we
would
make
a
clone
and
start
collaborating
there,
and
we
would
need
to
figure
out.
You
know
what
the
structure
is.
Do
we
want
to
do
a
lot
of
our
documents
aren't
super
long,
so
they
might
just
be
a
relatively
flat
file.
F
F
Haven't
one
concern
about
the
making
it
super
generic
I
know
we
talked
about
it
in
the
last
meeting,
just
if
we
can
raise
like
how
will
we
handle
like
a
aspects
of
the
sem
that
are
very
unique
for
each
company,
for
example
like
in
GitHub,
you
have
the
code
spaces,
it's
only
for
GitHub
and
the
GitHub
actions.
Configuration
and
gitlab
pipelines
are
very
different
and
I'm
afraid
we'll
have
a
document
with
with
different
sections
for
each
SCM,
eventually,
which
maybe
is
missing.
The
points.
D
D
Then
yes
right
and
we
all
do
then
I
mean
that's.
This
is
this
is
the
reason
I'm
picking?
This
is
because
it's
very
non-uh
controversial,
but
like
then
we
can
say
okay
in
order
to
set
this
up.
You
know,
multi-factor
authentication
is
really
good
because
of
xyzq
reasons.
Generally,
it
works
like
this.
D
A
F
E
H
E
Couple
people,
both
in
slack
and
on
the
issue
of
expressed
interest
in
participating
on
this,
so
what
I
will
do
is
I
will
set
up
a
doodle
so
that
we
can
have
a
dedicated
time
for
those
interested
to
get
together
and
kind
of
talk
through
some
of
these
issues
and
then
ultimately
kind
of
report.
Back
to
this,
the
larger
working
group
with
the
proposal
how
they
want
to
proceed,
and
we
can
try
to
hurt
all
the
cats
to
get
this
moved
forward.
J
A
Yeah
I
mean
this
is
something
that
was
worked
on
in
this
group
and
others
last
year
with
a
concise
guide
and
the
evaluating
open
source
software
and
other
documents.
So
some
some
of
the
groundwork
up
front
was
done
right
and
the
best
practices
badge
conversation
for
starting
to
think
about
how
you
know
your
file
is
your
application
following
best
practices.
As
far
as
this
group
is
concerned,
something
is
a
guideline
as
well,
but.
A
I
certainly
think,
if
we're
going
to
schedule
a
meeting
for
that
which
I
I
most
definitely
want
to
be
part
of,
we
should
make
sure
that
we
notify
and
there's
a
lot
of
the
same
people
in
this
group,
but
notify
those
in
the
repository
group
as
well
to
make
sure
that
they're
coming
in.
For
that.
That's
a
good
good.
E
B
E
I
B
E
H
E
E
J
B
I
I
will
say
that
we
moved
a
few.
We
found
some
problems,
We've
whined
and
complained
that
lfit
fix
those,
so
we're
hoping
to
deal
with
you
know
if
the
the
advantages
of
eating
your
own
dog
food
is
you
get
to
find
out
all
the
problems,
so
we
we
have
found
problems.
What
a
surprise
I
guess
so
you
know
so
we're
we
are.
We
we
have
wine
to
folks
to
fix
those,
hopefully
we'll
get
those
resolved
and
then
start
adding
a
few
more.
E
All
right
with
that
I
will
draw
to
a
close,
the
first
call
of
2023.
You
will
see
some
awesome
Communications
about
the
diversity,
equity
and
inclusion
committee
and
the
source
code
management,
best
practices
guide
and
then
I'll
send
a
general
email
about
the
call
for
papers
and
also
be
aware
that
the
LF
does
this
these
conferences
around
the
globe.
So
they
did
it
in
Europe.
E
A
E
Believe,
based
off
of
the
feedback
we've
gotten
at
each
one,
they've
been
very
popular,
and
the
foundation
would
like
to
do
that.
So
I
believe
there
will
be
a
also
dedicated
open
ssf
day,
but
again
the
conference
itself.
It
has
many
micro
conferences
like
a
supply
chain
conference.
They
have.
You
know
like
a.