►
From YouTube: OpenSSF TAC Meeting (April 5, 2022)
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
E
All
right,
I
think,
we've
we've
got
enough
to
go
ahead
and
get
going
all
right,
so
we've
got
just
a
couple
things
on
the
agenda
today.
E
The
life
cycle
document
that's
inside
of
the
tac
repo
lists
out
the
criteria
that
are
expected
in
order
to
formally
adopt
a
new
working
group,
and
so
one
of
those
requirements
is
having
five
meetings
with
appropriate
level
of
diversity
of
corporate
interest,
and
so
the
fifth
meeting
of
that
working
group
is
going
to
be
next
week.
So
once
that
threshold
is
set,
we'll
be
bringing
forward
a
motion
to
to
propose
review.
F
E
That's
okay,
so
it's
called
the
securing
software
repositories
working
group-
I
don't
know
if,
if
jacques
I'll
try
to
do
the
quick
tl
dr
on
it's
essentially
a
number
of
package
managers
across
many
of
the
the
programming
language
ecosystems
all
come
together.
So
it's
that
it's
that
one
yeah
cool
that
yeah.
E
Yep
sure
all
right
jory
I
apologize
for
putting
you
on
the
spot
here
I
didn't
want
to
follow
back
from
the
the
discussion
we
had
at
the
last
meeting,
where
you
were
graciously
agreed
to
put
together
the
table.
That's
at
the
top
of
the
meeting
notes.
I
just
wanted
to
give
you
a
minute
here
to
give
a
quick
shout
out
or
if
you
needed
to
yeah
or
poke
people
to
hey.
Let's
go
fill
out
or
address
gaps
in
this.
I
want
to
make
sure
we
kept
the
top
of
mind
so.
G
Okay,
quick
status,
update
on
that
particular
project.
You
can
see
that
the
table
is
there.
We
are
starting
to
convert
minutes
into.
This
is
sort
of
a
related
project
that
we
talked
about,
converting
the
the
notes
from
the
google
documents
into
a
minutes
folder
in
your
respective
working
group
repositories.
G
So
you
know
be
on
the
lookout
for
prs
from
me
for
your
for
your
minutes,
for
that
and
then
also
as
we're
doing
that
we're
updating
the
notes
documents
to
live
in
a
the
a
shared
google
drive
folder
for
your
working
group,
so
that
if
you
want
to
have
working
documents
that
are
shared
across
your
project,
including
your
notes,
documents
that
that
lives
in
a
space
that
the
community
can
access
really
easily
without
hitting
that
hitting
a
like
a
you
know,
not
a
loud
wall
that
kind
of
thing,
so
it's
a
little
bit
of
a
chore,
but
it's
actually
not
a
not
a
bad
chore.
G
So
let
me
know
if
you're
running
into
any
problems
or
if
you
have
any
questions
but
we're
trying
to
do
this
fairly
methodically,
so
that
you
don't
hit
dead
links
so
that
you
know,
for
example,
if
you're
going
to
the
calendar
event
to
grab
the
notes
document
that
that's
the
right
notes,
document
that
you're
grabbing
the
right
notes,
documents
from
slack
and
other
places
that
we've
we've
we've
pointed
that
to
so
anyway
happy
to
keep
this
going.
G
Additionally,
we
added
the
charter
template
as
the
foundation
had
been
using
it
to
the
project,
template
repo.
So
that's
the
the
charter
document
that
the
new,
the
new
working
group
that
bob
just
was
mentioning
the
securing
software
repo
repositories
group
will
use,
and
you
know
the
attack
can
totally
take
a
look
at
that
document
and
say
you
know
we'd
like
to
to
change
this,
because
it's
not
exactly
the
right
right
fit
for
us.
But
for
now
everyone
is
on
the
same
charter,
template
questions
or
like
concerns
or
anything
of
that
sort.
H
I
have
a
question
so
with
the
new
groups
that
are
being
created,
should
we
ask
people
to
start
joining
those
ones
to
get
updates.
G
Yes,
so
those
are
have
been
created
for
for
some
time
and
most
of
the
with
a
couple
of
exceptions.
Some
groups
had
started
to
use
google
groups
and
there
was
like
one
group
that
was
still
on
google
groups
that
started
on
google
groups.
G
We
do
want
everybody
to
be
using
the
same
tool
because
you
can
manage
your
subscriptions
across
multiple
groups
a
lot
more
easily
and
subscribe
to
say,
like
the
announcements
list,
the
tac
mailing
list,
your
whichever
working
groups
and
projects
you're
interested
in
and
and
you
can
manage
that
really
easily
in
one
spot,
as
opposed
to
having
to
go
to
into
separate
like
google
groups
to
go,
manage
your
settings
and
subscriptions.
G
You
know
one
by
one
by
one
so
and
that's
at
lists.openssf.org,
and
I
will
type
that
into
the
chat
for
you.
You
don't
have
to
if
you're.
If
you
don't
want
to
do
this
and
you
want
help,
you
can
say
dory
help
me
and
I
will
be
happy
to
add
you
manually
to
anything
that
you
would
like.
But
you
can
also
manage
your
subscriptions
there
at
that
at
that
domain.
F
F
E
All
right,
awesome,
yeah,
thanks
all
right
last
item
on
the
agenda.
I
know
you
put
this
in
here,
but
there
was.
This
is
a
it's
a
continuation
of
the
discussion
around
project
donation,
kind
of
formalizing
that
process
and
getting
that
ironed
out.
I
think
there
was
a
suggestion
at
the
last
meeting
to
essentially
use
the
cncf
documents
as
a
template
to
copy.
Well,
let's
make
the
changes
that
we
see
relevant,
let's
edit
out
what
isn't
applicable
for
our
particular
scenario.
I
Thanks
bob
and
thank
george
and
josh
for
reviewing
and
adding
comments
I
copied
most
of
it
over.
I
I
did
a
english
reading
of
all
of
it
and
it
sounds
good,
but
there
are
some
links
that
refer
directly
to
cncf
stuff.
One
of
them
is
actually
a
form
that
allows
people
to
sign
up
or
send
projects
open
ssf
way,
so
we
need
to
create
that
form
so
jori
I
have
thing.
I
I
have
marked
you
as
somebody
who
can
help
me
on
that,
and
basically
most
of
the
conversation
is
also
on
the
tag
channel.
So
if
you're
interested
join
the
slack
channel
there
or
discussion
there,
but
what
I
was
going
to
do
and
if
it
is
okay
with
the
group
here,
is
that
merge
merge
the
pr
as
it
exists
right
now,
with
with
the
open
questions
and
address
the
open
questions
as
a
separate
pr.
That
way
we
have.
C
Yeah,
I
think,
there's
a
lot
to
iterate
on
in
there.
Thank
you
very
much
for
getting
that
started
cedendra.
It's
it's
a
great
pass
at
the
baseline
for
us
to
work
from
there's
a
lot
of
little
things
and
you've
got
all
the
spots.
I
think
where
it
you
know
references
cncf
directly,
but
there's
a
lot
of
process
that
we
don't
have
yet
such
as
using
forms
to
apply
for
things
that
you
know
the
cncf
has
evolved
over
several
years.
C
Folks,
who
aren't
familiar
with
either
of
the
foundations
that
are,
you
know,
kind
of
coming
in
new
to
the
open
ssf.
One
of
my
concerns
with
merging
the
whole
thing
as
it
is
is
it
presents
a
picture
that
is
inaccurate
today
and
isn't
necessarily
the
one
we
want
to
reach
it's
close,
but
the
as
they
say
the
devil's
in
the
details.
Some
of
the
specifics
of
the
cncf
process
might
not
apply
here.
C
For
example,
nothing
in
those
documents
describes
working
groups
and
a
lot
of
that
process
doesn't
apply
to
the
majority
of
the
work
we
do
today
in
the
open
ssf.
So
I
would
love
to
discuss
among
the
group
here
how
to
efficiently
iterate
from
what's
there
do
we
merge
it
with
a
big,
bold
banner,
saying
hey.
This
is
a
work
in
progress.
Do
not
trust
this
yet
or
something
else.
C
How
do
we
approach
this
so
that
we
can
effectively
collaborate
to
go
from
the
starting
point
that
we
have
it's
a
good
one
to
converge
to
reflect
the
actual
state
we
have
today
with
the
aspirational
changes
we
all
want
to
achieve,
but
aren't
yet
implemented.
B
Yes-
and
I
can
push
the
unmute
button
too
so
yeah
I
just
wanted
to-
I
violently
agree
with
ava's
point.
You
know
the
you
know
yeah.
If,
if
it's
me,
the
attack
can
choose
what
it
wants
to
do,
but
whatever
the
tac
site
shows,
it
should
be
clear,
what's
active
and
what's
in
draft
either,
don't
accept
it
or
accept
this
change,
but
mark
it
with
draft
all
over
everything.
That's
not
official,
but
I
think
it's
just
important
that
it
be
clear
from
the
website.
What's
real.
B
B
A
B
Everybody
can
handle
it
in
one
big
swoop.
That's
fantastic!
My
my
brain
is
not
that
big,
so
I
think
it
would
be
better
just
to
do
it
in
increments
and
do
it
well,
because
I
think
really
the
issue
right
now
is
things
like
handling
requests
like
persias
and
the
working
group?
Maybe
I
don't
think
you
need
a
lot
of
process
for
the
next
steps.
Thanks.
J
Yeah,
thank
you,
yeah.
I
would
like
to
second
the
the
motion
on
holding
off
on
merging
everything,
as
is
because
I
mean
I
actually
spent
quite
a
bit
of
time
earlier
to
review
as
much
as
I
could,
and
it's
true
that
it's
it's
so
long
that
it's
hard
to
stay
focused
the
whole
way,
but
I
mean,
for
instance,
there
are
still
occurrences
of
the
word
kubernetes
in
some
of
the
docs.
J
So
at
the
very
least
there
is
some
basic
cleanup
that
still
needs
to
be
done,
and
there
is
a
bigger
question
that
I
wanted
to
also
raise.
I
mean
in
my
opinion,
I
mean
there
is
definitely
some
benefit
to
integrating
some.
J
You
know
process
we
borrow
from
other
projects,
but,
for
instance,
I
think
there
is
better
practices
now
to
do
some
of
the
work
there
and
in
particular
I
put
that
in
with
some
of
my
comments
instead
of
relying
on
on
google
forms,
I
actually
find
it
much
more
effective
nowadays
to
use
pull
requests
so
that
you
can
use
templates
and
people
can
simply.
You
know,
submit
a
pull
request
to
basically
submit
information
to
the
tag
for
review.
J
For
instance,
there
is
a
notion
of
annual
review
and
it
doesn't
really
say
how
you
do
the
review,
how
you
submit
your
data
and,
in
my
opinion,
it's
very
effective,
to
do
a
pull
request.
That
would
add
a
document
in
a
folder,
and
so
I'm
not
going
to
get
into
the
detail
of
that
particular
case.
I
just.
I
think
it
would
be
good
if
the
attack
had
some
kind
of
like
broad
policy
on
how
to
deal
with
this
kind
of
stuff.
J
Like
you
know,
submitting
a
change
of
status
for
your
project,
going
from
incubation
to
graduated
state,
you
can
do
that
with
a
pull
request
that
actually
mark
your
change
of
state
and
then
the
attack
can
review
the
pull
request
and
say
yes
or
no,
and
neither
you
merge
or
you
don't,
and
that
effectively
immediately
reflects
the
state
of
the
the
change
of
state.
So
I
have
actually
used
this
process.
J
We
use
that
instead,
I
mean
projects
often
use
that
also
for
like
maintainers,
in
projects
where
you
have
a
file
maintainers
and
the
best
way
to
propose
somebody
to
be
added
as
a
maintainer
is
to
do
a
pull
request.
That
actually
adds
the
line
that
has
that
person
and
the
maintainers
can
vote
on
that
or
not.
I
find
this
process
much
more
effective
than
relying
on
something
like
google,
docs
and
google
forms
that,
unfortunately,
I
have
to
remind
people
is
not
usable
by
everybody,
including
people
in
china.
A
Thanks
josh,
so
no
one's
going
to
disagree.
We
should
do
it
in
smaller
chunks,
but
it's
we.
We
need
to
produce
something
like
it's
just
a
giant
pull
request
today
and-
and
I
think,
if
it
was
up
to
me,
we
should
merge
this
into
a
branch
and
then
we
can
comment
on
it
and
submit
smaller
prs,
because
it
I
mean
it's
easy
to
say
we
should
do
it
in
small
pieces,
but
like
what
the
hell
does
that
even
mean
in
this
context,
right,
like
those
documents,
are
so
intertwined
with
one
another?
A
F
F
We
need
something
in
draft
to
work
on
together
and
we
need
to
be
able
to
also
peel
apart
some
of
the
complexities
that
the
cns
have
put
in
place
to
well,
not
the
cncf,
the
cnc
community
put
in
place
to
get
around
limitations
in
github
five
years
ago
and
give
limitations
and
notifications,
so
there's
definitely
more
to
be
done
or
more.
That
could
be
done
differently.
E
That's
okay,
no
worries.
I
I
was
gonna
say
the
same
thing
you
said,
which
was
essentially.
I
love
the
branch
idea.
E
I
think
the
other
thing
that
I
guess
would
be
helpful
for
me
selfishly,
would
be
a
what
are
the
three
or
four
other
bullet
points
that
we
need
to
get
closure
on
before
we
consider
this
work
minimally
violently
done
right.
This
is
always
going
to
be
something
we
evolve
over
time,
but
is?
Is
it
literally
just
you
know?
Maybe
this
question
is
back
to
you
sahindra?
E
I
So
there
are
two
things:
one
is
the
pr
that
I
created,
and
then
there
was
one
area
where
eva
was
working
on
where
they
had
the
there
was
there's
some
other
document.
It
is
also
in
the
slack
thread,
so
those
two
things
at
least
need
to
be
added.
As.
C
C
Well,
a
whole
different
github
repo
and
that
sort
of
is
looking
from
there's
a
couple
different
levels
here
that
we're
all
looking
at
at
the
cncf
level.
They
have
the
idea
of
projects,
but
then
within
kubernetes
they
have
the
idea
of
working
groups
and
the
openssf
has
borrowed
both
of
those
but
those
those
organizational
concepts
map
to
different
different
layers
of
sort
of
nesting,
governance,
structures
of
the
cncf
and
we're
trying
to
map
them
into
a
different
structure
here.
C
So
we
can't
just
lift
everything
wholesale
and
that's
was
sort
of
my
closing
point
on
the
github
pr
91,
just
a
few
minutes
before
this
meeting.
C
What
I'd
like
to
suggest
or
ask
is,
I
think,
a
branch
idea
is
great.
I
think
the
idea
of
iterating
rapidly
in
a
branch
to
find
the
parts
we
can
agree
on
and
pull
into.
You
know
the
main
branch
I
like
that.
I
I'm
not
confident
yet
that
that
will
work,
because
these
documents
are
very
intertwined.
C
We
might
find
10
percent
of
them
that
are
like
a
high-level
mission
statement
that
we
can
all
agree
and
just
pull
over
but
to
pull
over,
say
the
project
submission
template
without
the
review
documents
attached
to
it
without
the
guidelines
for
what
those
levels
mean
doesn't
make
any
sense.
So
we
have
three
or
four
different
documents
that
are
very
interdependent:
the
specific
process
of
how
a
submission
happens.
Is
it
a
forum
or
a
pr?
C
I
think
we
can
work
those
things
out
later
down
the
road.
That's
a
pretty
clean
line
to
draw,
but
I
want
to
ask,
is
if
we
do
this
work
in
a
dev
branch,
I
would
like
to
propose
that
a
few
members
of
the
tac
and
those
who
want
to
help
be
sort
of
given
told
you
know,
go
forth
and
iterate
as
fast
as
you
want.
Don't
wait
for
the
next
tac
meeting
to
merge
changes
on
that
branch,
come
back
in
two
weeks
with
the
branch
as
evolved
as
possible
to
review.
A
E
Yeah,
I
I
agree
as
well.
It
was
a
little
leery.
You've
been
have
it
on
the
agenda.
I
want
to
make
sure
that
we're
making
progress
but
spending
the
next
37
minutes
as
a
group
staring
at
a
gift
hub
page,
isn't
probably
the
most
productive
use
of
everyone's
time.
H
E
F
I
would
love
to
ask
that
a
couple
of
people
a
couple
of
groups
commit
to
working
with
ava
and
jay,
who
I've
said,
will
happily
work
on
this
from
microsoft.
I'd
like
to
make
sure
that
this
does
not
appear
as
if
microsoft,
you
know,
built
it
and
then
said:
hey
y'all,
so
I'd
love
josh!
You
are
very
engaged.
I
presume
you'll
want
to
participate
in
this.
I
Yeah
I'll
help
you
may
I
make
a
suggestion
to
move
this
along
yeah,
even
though
it
sounds
like
there
are
a
lot
of
files
together
in
that
folder.
If
all
of
us
take
like
10
minutes
reviewing
one
file
each,
I
think
we
could
get
a
lot
done
whatever
time
we
saved
from
this
meeting
could
be
put
to
that
use.
F
F
We
need
that
will
do
great
for
saying
if
we
lifted
and
shifted
this
governance,
where
everywhere
it
says,
cncf,
we
say
open,
ssf
everywhere
it
says
kubernetes,
we
say
the
project,
that's
pretty
straightforward,
but
this
is
a
different
picture.
We're
trying
to
do
different
things
with
it,
so
there
will
be
some
wholesale
changes
that
need
to
be
thought
through
for
this
organization,
and
that
needs
the
corpus
of
the
documents,
not
just
one
by
one
as
well.
So
there's
a
little
bit
of
both
it
goes
to
ava's.
F
C
Bob
could
I
jump
in
the
queue
ahead
of
you.
Yeah
go
ahead.
What
I'd
I'd
like
to
propose
to
facilitate
this
and
and
suddenly
you're
welcome
to
join,
is,
is
the
the
core
of
us,
whatever
we're
going
to
agree
at
the
end
of
today's
meeting?
C
Is
that
core
sets
up
a
recurring
like
I
can
carve
off
a
little
bit
of
time
every
day
pick
an
hour
a
day
that
we're
all
going
to
sit
on
zoom
together
as
a
forcing
function
to
work
on
this,
even
if
we're
on
zoom
but
silent
just
doing
our
own
thing
or
something
the
equivalent
of
that
and
we
set
up.
We
give
ourselves
a
deadline
of
one
week
from
tomorrow,
probably
so
mid.
C
E
Yeah
cause
I
like
I
said
I
don't
want
to
litigate
a
a
pr
on
zoom
with
10
people,
but
we
also
need
to
make
sure
that
we're
making
progress.
Here
I
mean
I'd
like
to
target
that
we
could
ultimately
get
a
vote
on
the
minimally
viable
governance
at
the
next
meeting.
I
don't
know
if
that's
too
aggressive,
but
again,
I'm
like.
Let's
do
the
right
thing
and
let's
have
the
right
discussions.
I
don't
want
to
put
an
arbitrary
deadline
just
to
force.
E
However,
I
think
we
have
to
we
have
to
have
some
sort
of
a
forcing
function.
To
keep
everybody
honest,
so
I
would,
I
would
plus
one
let's
set
up-
maybe
a
couple
one-hour
sessions
over
the
next
week
and
have
called
them
attack
office
hours
and
as
many
people
that
can
contribute
to
that,
can
show
up
we'll
continue
to
work
on
that
and
then
the
agenda
item
I
would
see
for
the
next
tac
meeting
would
be
any
points
of
contention
that
we
weren't
able
to
resolve.
E
That
need
to
be
surfaced
to
the
broader
group
for
discussion
or
if
we
do
get
this
consensus
and
we
have
enough
plus
ones
on
that
to
generally
call
for
a
motion,
then
then
we
could
certainly
do
that
as
well.
So
putting
that
out
as
a
proposal
any
any
thoughts
or
feedback.
C
C
D
I
E
All
right,
so
I
guess
jewelry
is
that,
is
that
something
you
could
help
with
sending
out
the
invites
to
the
attack
list
just
to
rinse.
I
don't
know
whether
it's
the
same
exact,
zoom
link
or
not,
but
if
you
could
help
with
that,
that
would
be
awesome.
E
Appreciate
it
all
right,
I
see
someone
has
added
open
ssf
day
fyi
or
I'm
sorry
ava.
It
was
that
last
item
there
something
you
wanted
to
call
out.
C
In
in
the
context
of
the
last
conversation
I
want
to
please
call
attention
to
this
joy
and
I
had
started
two
weeks
back
on
a
community
repo
instead
of
attack
repo.
C
You
know
we'll
figure
out
if
you
know
squash
them
together
or
not,
but
please
take
a
look
at
that
pull
request,
as
it
has
some
of
the
content
on
working
groups.
Six
projects
that
the
differentiation
there
that
I
lifted
out
of
kubernetes.
I
would
love
to
get
some
feedback
on
that
before
tomorrow's
meeting.
G
Yes,
that
was
me
sorry.
I
will
put
my
name
in
front
of
those
things
moving
forward.
I
just
wanted
to
share
an
fyi,
because
the
the
page
is
live,
that
we
have
open
ssf
day,
which
is
june
20th
ahead
of
the
open
source
summit,
north
america,
events
that
are
happening
in
austin
texas
this
june.
This
is
a
free
event
and
we
are
really
excited
to
be
just
sort
of
pulling
together
folks
from
the
community
to
come
and
tell
stories
to
new
audiences
about
what
openssf
are
doing.
G
So
please,
please
register
again
complimentary
registration
and,
if
you're
going
to
be
there,
let
us
know
because
we'd
like
to
get
everybody
together
and
so
let
let
operations
add
open,
ssf,
no
or
just
poke
us
in
slack
or
something
like
that.
But
if
you're
going
to
be
down
there
for
for
the
summit,
come
a
day
early
and
come
hang
out
with
us,
we'd
love
to
love.
To
do
that.
G
That
is
a
great
question
ava.
I
know
that
we
have
a
a
virtual
component
for
those
events
in
texas
for
as
sort
of
an
lf
events
policy.
So
let
me
find
out
how
that's
applying
to
open
ssf
day
and
get
back
with
you.
E
I
guess
one
other
quick
question
on
that.
I
know.
Reading
the
website
here,
real
quick,
it's
just
it
looks
like
it's
working
group
leads,
would
be
offered
the
opportunity
to
present
is
there,
I
guess.
Has
there
been
any
communication
to
the
working
group
leads
yet
so
make
sure
that
they've
got
enough
runway
to
know
that
they're
they're
being
asked
to
do
that.
G
Yeah,
I
know
that's
a
great
question:
we
don't
have
a
set
agenda,
yet
brian
was
going
to
reach
out
to
people
about
presenting,
for
example,
on
the
fuzzing
tool
on
salsa,
on
some
of
like
the
big
projects,
we
wanted
to
kind
of
avoid
something
that
just
felt
like
a
status
update
day,
more
or
less
and
and
kind
of
try
and
put
focus
on
like
the
impact
of
the
projects
that
you
all
are
driving.
G
So
if
you
are,
if
you've
got
an
idea
for
a
session,
if
there's
something
you'd
really
think
that
ought
to
be
highlighted,
there's
absolutely
room
for
that.
G
I
think
you
know
the
panel
with
the
tac
or
you
know
something
like
that
would
be
great
we're,
also
not
wanting
to
ask
people
to
travel
if
they
aren't
comfortable
doing
so
if
they
weren't
planning
to
so
this
is
a
little
bit
of
a
figure
out
who
was
already
sort
of
planning
to
be
there
and
like
see
if
they
can
come
early
and
do
it
do
do
a
session.
G
It's
not
a
lot
it's
in
a
long
time
it's
a
day,
and
these
sessions
are
going
to
be
like
30
minutes
to
make
for
lots
of
hallway
time,
and
that
kind
of
thing.
So
not
a
big
lift,
is
what
I'm
trying
to
get
at.
We
don't
want
anybody
stressing
out
that
they
need
to,
like
you
know,
put
together
a
keynote
presentation
or
something
like
that.
So
yeah
that
that's.
E
Got
it
makes
sense?
Sarah,
you
had
your
hand
up,
but
I
think
you
took
it
down
so.
F
I
did
I
dropped
it
in
chat.
Jewelry
is
where
is
the
marketing
working
group
working
on
all
of
this,
because
that's
another
lever
for
all
of
us
to
use
if
we
want
to
participate.
G
Yeah
so
and
the
marketing
working
the
marketing
committee
and
just
to
oh,
thank
you
for.
G
You
marketing
committee
and
has
just
started
meeting
and
they
will
be
taking
this
up
from
a
you
know:
content
and
social
media
promotion,
and
that
kind
of
thing
I'll
say
one
of
the
ideas
that
the
lf
marketing
team
has
and
which
I'm
really
excited
about
is
that
they've
got
someone
who's
coming
with
quite
a
bit
of
like
high
quality,
video
production
equipment
and
they'd
love
to
interview
as
many
people
from
our
community
as
possible
for
about
15
minutes
to
just
start
telling
more
of
the
security
story
and
open
source
story,
and
so
definitely,
if
you're
going
to
be
there.
G
Let's
get
you
in
front
of
let's
get
you
camera
ready
and
get
you
interviewed,
because
that
that's
an
that's
a
great
you
know,
forum
for
us
and
yeah.
F
That's
yeah
the
the
challenge
in
on-site.
Videos
is
also
the
the
remote
participation
oddly
enough,
but
we
can
do
that
differently,
so
cool.
Thank
you,
yeah,
there's,
there's
going
to
be
ava
points.
This
the
anti-inclusive
policies
and
changes
like
literally
texas,
is
a
challenge
this
year.
So
we
will
figure
that
out
over
time,
yeah.
G
You
know,
stance
against
those
policies
and,
regrettably,
are
sort
of
backed
into
a
corner
for
this
particular
event
and
are
promising
that
we're
not
going
back
to
texas
or
any
other
state
for
that
matter
that
that
that
continues
this
type
of
of
activity
in
their
legislative
body.
But
it's
it's
a
very
unfortunate
situation
for.
C
C
Remotely
to
to
my
knowledge
from
I
couldn't
speak
for
myself,
for
what
I've
read,
the
the
petition
simply
asked
for
ensuring
the
event
was
fully
engageable
remotely,
so
that
suggests
people
wouldn't
would
attend,
speak,
etc,
virtually
just
not
go
in
person.
Okay,
thanks.
E
All
right
we're
at
the
end
of
the
agenda
items
that
we
had
on
the
list.
I
guess
one,
maybe
final
call
for
any
other
topics.
Folks
want
to
raise
today.
K
Thanks,
sarah
thanks
bob
just
really
quick
one
to
reiterate
the
idea
that
things
are
moving
very
quickly.
K
I
know
that
it's
a
great
opportunity
to
have
the
open
ssf
day
the
day
prior
to
the
main
austin
summit
event,
but
it
now's
the
time
to
really
emphasize
that
we
need
to
work
with
the
governing
board
and
the
lf
management
to
really
put
a
stake
in
the
ground
to
make
sure
that
day
is
successful,
because
I'm
just
concerned
that
things
are
moving
quickly.
The
various
committees
like
the
marketing
committee
and
some
of
the
other.
K
Committees
are
are
actually
lagging
the
working
groups
in
this
2.0
reboot.
So
if
we
don't
take
full
advantage
of
the
day,
it's
going
to
be
a
missed
opportunity.
I
was
glad
to
hear
from
jorie
that
there's
going
to
be
quality
video
capture
there,
but
I
would
just
encourage
us
all
that
you've
got
the
opportunity
to
participate
to
make
sure
that
you
advocate
for
your
working
group
or
your
project
to
take
advantage
of
the
opportunity.
K
I
mean
I'd
hate
to
see
this
come
off
less
than
optimal,
because
it's
just
coming
up
so
quickly.
E
Yeah
through
my
two
cents
and
jeff,
I
I
generally
agree.
I
think
it
is
a
great
opportunity.
More
broadly
and
it's
good
to
see
the
marketing
committee
coming
together.
I
think
it's
we've
got
great
stories
to
tell
so
making
sure
that
we
use
the
most
of
the
opportunities
we
have
to
to
have.
The
impact
that
we
want
to
have
more
broadly
for
the
community
is
super
important,
so.
K
I
would
just
say
that
the
marketing
committee
is
probably
only
going
to
be
able
to
be
supportive
in
terms
of
you
know:
outbound,
communication
and
broadcast,
and
it's
up
to
the
attack
and
the
governing
board
to
put
a
firm
hand
on
the
tiller
and
say
this
is
these
are
some
of
the
primary
messages
we
want
to
get
out,
because
the
lf
will
do
it
for
us
and
it's
I'm
glad
they're
being
proactive
to
set
up
this
day.
K
E
So
I
guess
to
that
end
jory,
I
guess,
do.
Is
there
a
timeline
in
terms
of
getting
the
agenda
firmed
up?
Is
this
something?
It
sounds
like
a
topic
that
we
need
to
bring
back
up
at
the
next
hack
meeting.
But
again
I
don't
want
to
make
sure
we
slot
things
appropriately
from
a
just
a
sequencing
perspective.
G
So,
obviously,
as
soon
as
we
can
get
the
schedule
and
and
things
on
the
site,
like
the
the
sooner
the
better
right
and
to
be
honest
like
this,
is
we
were
already
at
the
point
that
the
marketing
department
and
you
know,
and
the
events
team
decided.
G
Okay,
we
can
make
this
space
available
to
open
ssf
for
the
day
we
were
already
a
little
behind
the
eight
ball,
because,
frankly,
these
events
take-
you
know
at
least
six
plus
months
to
plan,
and
we
started
doing
it
like
you
know
last
last
month
or
within
the
last
month.
So
it's
it
is
something
that
we
are
trying
to
play
catch
up
to.
So
the
sooner
we
get
a
schedule
identified
the
better,
and
so
if
this
is
something
we
can
actually
develop,
asynchronously
that'd
be
cool.
G
You
know
we
can
just
kind
of
go.
Have
that
in
in
slack
we
can.
You
know
we
can
have
those
conversations
on
the
working
group
calls
throughout
the
rest
of
this
week
as
well.
You
know
we
we
can.
We
can
be
pretty
flexible
to
try
and
you
know,
get
get
this
done.
E
Okay,
I
would
say
I'll
I'll
go
ahead
and
add
an
item
just
to
hey,
so
my
memory
doesn't
fail
us
at
the
next
meeting,
just
to
bring
it
up
and
make
sure
that
we
talk
about
it
because
again,
as
several
folks
have
pointed
out,
I
think
it
is
important
just
to
get
the
awareness
out
and
around
it.
I'm
vague,
just
curious.
K
Bob,
a
quick,
maybe
a
quick
show
of
hands
or
something
how
many
of
the
you
know,
18,
plus
or
minus
of
us
here,
either
submitted
a
session
for
the
main
event
related
to
the
open,
ssf
or
did
something
specifically
for
the
open
ssf
day.
K
I'm
curious
just
a
quick
show
of
hands
if
anyone
proactively
put
a
session
submitted
a
session,
because
I
believe
that
call
for
papers
is
closed
on
the
open
summit
itself
and
I
know
just
of
a
small
handful.
So
it
looks
like
there's
plenty
of
opportunity
to
take
advantage
of
the
getting
some
content
out
there
for
either
your
project
or
your
working
group
on
the
open
ssf
day,
because
the
call
for
papers
for
the
summit
itself
is
closed.
E
Yeah,
I
briefly
crawled
me
mentioned,
maybe
at
the
last
meeting
or
even
the
meeting
before
just
in
passing,
but
in
terms
of
you
know,
like
you
said,
a
formal
cfp
and
a
more
of
a
a
documented
plan,
an
engagement
to
the
working
groups.
I
think
it
would
be
great
to
continue
to
push
that
forward.
So
joria
happy
to
work
with
you
offline
with
brian
as
well,
to
make
sure
that
we've
got
that
all
buttoned
up.
E
G
We
have
we
don't.
We
were
not
part
of,
like
the
the
other
other
than
sort
of
as
a
promotional
partner,
the
other
co-located
events
that
are
happening
so.
G
And
yeah
david,
I
think,
was
helping
with
review
cfps
for
one
of
those
david
wheeler,
but
but
other
than
that,
like
we're,
those
are
separate
events
from
us
and
so
as
soon
as
we
were
aware
that
the
cfps
for
those
were
closing,
we
did
try
and
get
a
message
out
to
y'all,
but
I
I
didn't
know
about
it
beforehand:
I'll
try
and
get
the
scoop
sooner
next
time.
Maya
culpa
on
that.
G
Oh
linux
summit
security
summit.
E
Yeah
another
several
co-located
events.
Several
of
us,
I
think,
were
on
the
program
committees
for
that,
and
I
know
for
the
supply
chain
security
con.
I
was
a
reviewer
and
there's,
I
think,
great
at
least
great
proposals
that
came
across
many
of
the
working
groups,
which
was
awesome
to
see,
but
in
terms
of
what
actually
gets
accepted,
obviously
with
tbd
but
but
yeah.
E
B
E
Part
of
openssf-
and
you
know
what
put
my
code
anywhere.
Why
would
I
not
do
it
here?
I
think
it's
a
broader
thing,
david.
C
C
I
don't
I,
I
don't
see
a
a
link
for
a
cfp
or
you
know
how
to
join
a
review
committee.
So
if
it
like
help
us
understand
so
that
the
community
understands
how
this
is
a
participatory,
open
event.
E
E
All
right
last
call
for
any
other
topics.
Folks
would
like
to
discuss.
E
Once
twice
sold
all
right
thanks
everyone
and
as
a
reminder,
please
please
take
the
time
to
go
review
sandra's
pr
around
the
process,
the
more
people
that
get
eyes
on
it,
the
better
it
will
ultimately
be
and
the
faster
that
these
meetings
can
ultimately
go.
If
we
do
the
majority
of
the
work
out
of
the
out
of
the
session,
so
thanks
everybody
see
you
soon.