►
From YouTube: OpenSSF Diagrammers Society (December 15, 2022)
Description
Meeting minutes: https://docs.google.com/document/d/14i9v7WuQcLzWpvLe9B0sl-kf90JLwxNwrZkRXLWmEdQ/edit#heading=h.9m0zi4b0wnne
A
B
A
A
E
D
A
D
E
A
A
B
C
D
B
B
Better
and
I
haven't
heard
back
from
him
since
then
so
I
think
he's
probably
out
still,
but
but
so
I
before
we
get
there.
I
had
two
topics
I
wanted
to
talk
about.
There
was
this
one
and
the
other
one
was
I
the
status
of
this
group.
The
last
time
we
talked
about
having
the
charter
ready
to
pick
for
vote
did
I
miss
this.
C
B
D
Had
a
long
list
of
things
to
talk
about
and
didn't
get
too
much
of
it,
so
I
always
put
it
on
the
backlog
for
a
future
call.
But
I
don't
know
when
we'll
officially
get
that,
but
when
I
spoke
to
them
they
were
all
in
agreeance.
We
just
wanted
to
see
the
paperwork
done
and
they
were
fine
adopting
us
as
kind
of
somebody
reporting
it.
B
All
right,
so,
okay,
thanks
thanks
for
allowing
me
to
get
back
on
the
same
page,
all
right.
So
regarding
the
Mind
map,
so
here's
you
know
and
it's
unfortunate,
because
I
went
to
to
talk
to
to
have
a
chance
to
talk
to
Matt
about
it.
Because
so
what
happened?
Is
he
worked
a
little
bit
more
on
it?
And
then
he
shared
it
with
me
and
of
course,
it's
a
bit
of
pain
because
you
need
to
install
some
tool
to
use
it.
I
mean
for
now
it's
free
in
evaluation
mode.
B
Have
the
map
in
front
of
you
and
stop
going
into
it
that
you
realize
how
much
information
there
is
there,
and
so,
unfortunately,
you
know
I
try
to
go
through
it
and
what
I
realized
is.
There
are
many
different
ways
you
can
represent
those
things
and
it's
not
clear.
You
know
what
is
the
right
way
you
know,
and
so
in
the
little
discussion
I
had
with
him,
I
I
shared
with
him
I
said
I
feel
like
you
know,
there
is
in
some
ways
the
the
tree
he
built
was
a
bit
too
deep.
B
There
is
too
much
details
trying
to
be
captured
in
that
in
that
map
and
I
took
an
approach.
I
actually
did
another
version.
I
was
hoping
I'd
be
able
to
share
that
with
them
and
be
able
to
have
a
discussion
see
how
he
felt
about
it,
because
his
initial
reaction
was
like
well.
This
is
how
my
mind
functions.
B
You
know
it's,
it's
a
mind,
kind
of
maps
it
out
in
that
way,
but
so
to
give
you
an
example,
you
know
it's
like
you
look
at
the
guides,
the
best
practices
working
group
which
we
all
know
quite
well.
You
know
there
is.
He
captures
the
fact
that
it's
producing
guides
and
then
it
creates
a
node
that
has
guide
and
then
deletes
the
guys.
But
then
it
says
oh,
but
there's
also
two
guys
that
are
concise
guides,
so
you
create
a
subsection,
concise
guides
and
another
section.
B
There
is
no,
it's
not
very
clear
where
you
draw
the
line
to
be
fair,
because
then
you
say
well:
working
groups
do
I,
need
a
node
that
says
working
groups
and
have
all
the
working
groups
underneath
or
can
I
just
put
the
working
groups.
You
know
one
by
one
underneath
best
practices
working
group,
you
know-
and
it's
like
well,
you
know
their
pros
and
cons
to
both
of
them
and
and
there's.
The
other
aspect
is:
is
this
notion
of
tags
that
he
started
having
where
you
can
add
attributes
to
things
by
saying?
B
Well,
these
maps
to
you
know
this
part
of
the
mobization
plan,
for
instance,
and
you
can
say
well,
you
know
so
a
lot
of
the
things
can
be
captured
in
different
ways,
either
as
inheritance
in
the
tree
or,
and
you
know,
to
be
fair.
All
that
I
have
actually
had
a
bit
of
experience
in
you
know,
building
taxonomies
and
schemas
and
stuff,
and
you
fall
into
the
same
kind
of
stuff.
There's
no,
you
know
there
isn't
a
single
way
to
map
those
things
out
and
you
you
fall
into
that
again
here.
So
it's
like.
B
Where
are
things
you
know,
nodes
that
you
need
to
read
from
or
these
attributes
that
you
add
to
it
so,
for
instance,
to
get
back
to
the
example
of
the
guides
I
figured
now.
We
just
need
one
category,
that's
guides,
and
if
you
want
you
can
have
an
attribute,
a
tag
that
says.
Oh,
this
is
a
concise
guy,
but
it's
it's
kind
of
or
you
know,
an
add-on
doesn't
have
to
be
part
of
the
tree.
I.
B
D
D
So
the
fact
we
have
salsa
and
s2c2,
we
need
to
figure
out
a
way
that
we
can
harmonize
those
two
projects
so
that
we
have
potentially
one
umbrella
and
they
might
have
two
sub
projects,
there's
a
desire,
so
the
attack
will
be
going
through
and
looking
at
the
working
groups,
the
initiatives
and
everything
the
sigs
and
understanding.
Does
this
fit
within
the
Strategic
direction
of
the
foundation?
D
B
F
B
D
And
where
Matt's
exercise
before
we
move
on
to
yours
is
useful
is
that
he
went
through
and
identified
like
the
fact
that
you
know
all
star
is
listed
as
a
project,
but
it's
not
in
the
document.
The
readme
documentation
correctly,
so
ideally
we'll
be
able
to
go
through
and
make
these
Corrections.
So
we
get
things
more
consistent,
I've.
A
Been
trying
to
do
this
throughout
open
ssf's
existence,
but
that
doesn't
mean
I
always
get
it
and
in
fact,
I
I've
been
trying
to
make
a
simple
rule.
There
must
always
be
a
link
up
and
Link
down
right.
So
if
you're
a
project
within
a
working
group,
The
working
group,
the
project
should
link
back
to
its
working
group
and
basically
all
the
way
up
and
down
so
that
there's
no,
you
know
you
should
be
able
to
start
at
any
one
place
and
end
up
at
any
other.
B
So
I
assume
you
guys,
can
see
this
right,
so
this
is
Matt's
diagram
I.
This
is
untouched.
It's
the
way
he
shared
it
with
me,
and
so
you
can
see
here
the
kind
of
levels
there
are
multiple
levels
right,
this
best
path.
This
is
working
group
and
then
projects
is
like
some
are
code
related
and
the
other
things
and
yeah,
and
so
on.
Right
and
you
can
see,
for
instance,
the
guys
I
was
talking
about
here
with
the
multiple
levels
and
so
on,
and
so
my
my
well.
B
So
this
is
my
version
of
it
and
you
know:
I
had
two
main
driving
factors.
The
first
one
was
like
I
said
trying
to
flatten
out
some
of
this
stuff,
so
you
can
see,
for
instance,
this
guide
stuff.
Now
it's
just
like
one
level
and
then
I
added
some
tags
to
say.
Okay,
this
is
a
concise
guide,
but
I
feel
like
this
is
kind
of
accessory
and
then
doesn't
have
to
be
brought
up
at
the
level
of
the
structure
itself.
B
B
I
try
to
map
this
as
much
as
possible,
so
you
know
I
know
for
a
fact
that
our
government
instructors-
you
know,
if
you're
doing
code,
you're
supposed
to
be
a
project.
So
this
is
how
I
I
kind
of
restructure
things
around
there's
working
groups
that
can
have
six
and
projects
that
do
code.
And
yes,
there
are
other
things
things
and
today
you
know
this
is
like
the
greater
method,
distribution
project.
We
all
know
today
with
a
decal
project
right
we
call
it
initially.
B
It
was
something
initiative,
yeah
and,
and
so
I
created
a
a
kind
of
fit
all
type
of
you
know:
node,
that's
called
other
activities.
So
essentially
these
are
the
main,
like
you
know,
sub
nodes
that
you
have
in
your
working
group.
It's
six
projects
that
do
code
and
other
activities,
and
then
you
can
add
variable
stuff
there,
and
so,
but
this
is
kind
of
the
gist
of
the
changes
I
made
and
you
know,
try
to
to
figure
things
out
a
little
bit
and
and
try
to
flatten
out
a
little
bit.
B
The
structure
and
I
also
put
all
the
working
groups
under
the
attack
and
try
to
you
know
clean
it
up
a
little
bit
building
on
what
he
had
done,
and
you
know
it's
a
bit
of
work
for
me
to
share
this
with
the
group
now,
because
I
wanted
to
have
a
chance
to
talk
to
him
first,
because
I
don't
want
to
look
like
I'm
hijacking
his
work,
but
you
know
this
I
spend
a
little
bit
of
time
on
this
and
I
thought
I.
For
me,
it's
an
improvement.
B
D
B
So
that's
I
think
he
did
this
because
he
it's
a
reminder
that
he
has
this
idea
that
everything
should
not,
for
instance,
an
mobilization
plan
or
if
they
don't
well,
maybe
there's
a
lag
I,
don't
know
if
he
intends
to
add
something,
and
he
just
put
that
as
a
reminder
that
he
needs
to
add
something
or
not.
I
honestly,
I,
don't
know
that,
but
it.
B
Yeah,
but
so
in
general,
the
way
it
works
and
I
kind
of
maybe
extended
for
it.
He
had
in
mind
on
that
front.
Is
you
know,
I
I
figured
everything
because
I
mean
you
also
have
to
deal
with
the
way
the
the
system
works.
There
isn't
that
many
ways
to
put
attributes
attached
to
a
node
and
tags
for
me
is
just
a
way
to
capture
okay,
this.
This
is
a
lot
like
sub
nodes.
They
are
just
attributes
related
to
the
node.
B
The
tags
is
attached
to,
and
I
kind
of
try
to
generalize
this
to
capture
all
the
different
attributes.
We
could
have
attached
to
a
node,
but
that's
a
bit
of
a
detail
why
we
have
tags
when
there
is
nothing
and
if
again,
this
I
think
it's
because
he
wanted
to
capture
the
fact
that
maybe
we
are
missing
some
information
I.
D
B
A
D
D
B
B
C
A
B
B
B
B
No
I
agree
with
that.
Okay,
but
you
see
so
it's
interesting
I
mean
I
also
found
quite
a
few
things.
You
know
he
had
wrong
because
you
know
he
tried
to
and
I'm
sure
collectively
once
we
can
start
going
a
bit
more
into
the
details,
we
can
probably
improve
a
lot.
There's
actually
another
few.
That
I
thought
was
interesting
this
if
I.
E
A
E
A
E
A
B
A
C
D
D
Like
if
we're
gonna
talk
about
today,
the
best
practices
working
group
with
attack,
this
might
be
useful
to
kind
of
show,
hey
we're
missing
this
in
the
readme
file,
and
this
isn't
classified
right.
You
know
the
MFA
project
isn't
a
project,
it
needs
to
change
initiatives.
We
can
go
through
tactically
and.
B
B
D
Well,
we
even
could
throw
it
into
a
different
diagramming
tool
if
we
wanted
to
go.
Talk
like
working
group
to
working
group,
I
think
is
where
this
probably
is
going
to
ultimately
end
up.
Is
we're
going
to
need
to
talk
to
the
working
groups,
the
leads
and
have
them
validate
what
we've
observed,
and
so
we
may
need
to
like
have
nine
littler
diagrams
that
just
show
a
working
group
or
Sif
or
Sig
yeah.
A
A
typical
organizational
hierarchy
diagram:
you
only
go
a
few
levels
and
stop
and
then
go
down
further
I,
just
I
I'm,
a
little
skeptical
that
the
tags
are
are
worth
it,
but
the
rest
of
it
showing
organizational
structure.
I
might
not
group
The
projects
and
sigs,
but
go
straight
down
to
the
projects.
But
you
know
what
a
little
subgrouping
is
not
insane.
C
B
Could
you
know
if
you
make
it
like
every
time?
There's
a
Sig,
you
add
sick
to
the
to
the
name
right,
okay,
then
you
don't
know,
then
you
have
a
specific
like
shape
and
pattern
or
color,
and
you
use
this
consistently.
You
could
just
get
rid
of
the
Sig
node
there
and
you
could
do
that
throughout.
That's
right
and
and
I
I
actually
did
some
of
this
and
then
I
I
was
unsure,
so
I
kind
of
stepped
back
I
had
been
balancing
back
and
forth
on
that
one.
B
To
be
honest,
I
was
like
yeah
I,
don't
know,
there
seems
to
be
some
value
in
grouping
there,
but
there
may
be
another
way
to
group
them
and
the
other
thing
is
you
know,
because
I
was
asking
him.
The
colors
I
mean
this
like
and
he
said
well
I.
He
also-
and
this
is
how
you
know
when
stopped
overnighting
too
many
layers
of
information,
it
becomes
impossible
to
have
a
very
consistent
way
of
representing
things
because
I
was
like.
Why
are
they
all
these
colors?
He
said
well,
yeah.
B
There
are
things
that
kind
of
I
wanted
to
put
in
red,
because
I
was
like
there's
a
problem
there,
I
want
I
need
or
I
need
more
information,
and
so
it
was
my
way
to
remind
myself
say
this:
is
an
area
I
need
to
go
back
to.
But
of
course,
this
you
know
derails
you
from
having
a
more
consistent
way
of
representing
all
the
projects,
for
instance,
but.
B
Yeah
so
I
think
there's
more
work.
That
could
be
done
like
this,
and
even
you
know,
even
when
you
talk
about
the
tags,
I
question
the
the
idea
that
you
know
you
need
like
mobilization
plan
and
then
underneath
there
are
different
types
of
you
know.
We
know
there's
like
the
different
streams
and
it's
like.
Well,
maybe
you
just
need
one
note
that
says
this
is
mobilization
plan,
slash
risk
assessment
and
you
can
simplify
the
view
by
adding
only
one
loan.
A
Right
that
that's
why?
What
right
now
I'm
looking
at
it
I'm
thinking
this
is
I,
think
having
it
all
in
one
place,
is
helpful.
I
think
it
looks
awful
complicated,
overly
overly
complicated,
but
if
we,
if
we
change
the
node,
you
know
if
we
change
the
nodes,
at
least
on
projects
versus
sigs
and
I,
don't
know
if
we
can
get
rid
of
the
tags
or
simplify
them
into
what
is
it
called
when
you
decorate
a
decorator.
B
A
B
Exactly
so,
okay,
but
so
this
is
useful,
because
I'm
happy
to
invest
a
little
bit
more
time.
If
you
it
seems,
like
you
know,
I
was
on
the
right
track.
You
guys
also
feel
that
yeah,
you
know
we
I
think
try
to
simplify
this,
so
that
it's
more
digestible.
That's
also
how
I
felt
and
I
was
trying
to
play
around
with
some
already
some
ways
to
simplify
it,
and
this
is
encouraging
me
to
go
even
further,
so
I'm
happy
to
try
to
do
that
and.
D
Again,
thinking
about
the
the
audience,
if
we
handed
an
executive-
something
that
is
you,
you
have
to
have
a
50
inch
monitor
and
it's
all
you
know
eight
point
font,
that's
not
going
to
be
a
good
experience
and
you're
going
to
spend
more
time
explaining
why
it
looks
like
this
and
zooming
in
and
out.
So
we
want
to
think
about
the
audiences
when
we
start
to
deliver
it.
B
Absolutely
you
know
I
agree
and
in
fact
I
mean
you
know
there
are
things
you
can
do.
That
would
makes
more
sense
if
you
have
fewer
layers,
for
instance,
so
because
when
you,
when
you
select
a
node
like
this,
you
can
choose
how
the
children,
the
child
nodes,
are
displayed,
whether
it's
in
a
tree
see
the
structure
there.
You.
B
Want
it
to
be
more
like
vertical,
of
course
it
doesn't
work.
Well,
if
you
have
too
many
layers,
but
if
you
only
have
three
nodes,
it
works
much
better
and
it
would
be
a
much
more
compact
result
right,
so
that
I
can
actually
show
you.
If
you
just
take
this
out
right,
yeah
I
mean
obviously
you've
lost
some
information.
Don't
get
me
wrong,
but
often
you
can
make
that
the
whole
thing
fit
in
a
much
more
compact
area.
Well,.
A
B
A
A
Well,
no,
no
yeah,
but
I
I
had
I
was
processing.
Some
gdpr
deletion
requests
and
I
want
to
make
sure
that
goes
away.
All
right,
I,
don't
want
to
see
that
I.
Don't
want
to
see
that
I
don't
want
to
show
it
I.
You
don't
want
to
see
it
so
okay.
So
where
are
we
going
here
with
this?
The
reason
I
was
I
wanted
to
do.
This
is
whoops
I've
lost
my
zoom
screen
there
we
go
all
right
share
screen,
share
the
universe.
A
A
I
show
you
know
governing
board
Tech
working
groups
and
then
there's
a
two
different
slides
I
show
depending
on
context,
but
you
know
here's
one
of
them,
which
is
for
each
of
those
colors
I
list
the
projects
and
sigs
underneath
which
is
a
little
bit
like
what
you're
showing
but
I
didn't
try
to
do
all
the
lines,
because
those
are
kind
of
painful
to
you
know
to
edit
on
basically
a
slide
deck.
Also
again,
the
size
is
the
problem.
A
B
B
B
There
is
some
inconsistency
in
what's
being
linked
because
in
some
cases
you
link
to
the
minutes
the
slash
dog
notes
right
because
that's
all
you
have
in
other
cases
you
have
a
GitHub
repo
and,
as
we
know,
sometimes
they
are
both,
but
it's
not
always
clear
that
they
are
linked
together.
So
go
ahead.
I.
A
D
D
D
D
So
we
have
the
different
kind
of
display
types:
we've
used,
okay,
and
so
what
I
anticipate
I
will
see
if
I
can
grab
Bob
before
the
holiday
I.
Imagine
that
will
be
working
with
some
or
all
of
the
tack,
we'll
need
to
do
kind
of
a
show
and
tell
so
we'll
want
to
make
sure
we've
got
all
these
things
refined
if
we
want
to
use
the
Mind
map
for,
like
the
conversation
with
the
TAC,
we'll
make
sure
that
it's
cleaned
up
and
it's
consistent
as
we
as
we
want
it
to
be
so
like.
D
If
we
want
to
hide
the
tag.
If
we
agree,
we
want
to
hide
the
tags,
let's
make
sure
that's
all
hidden,
make
sure
that
projects
or
squares
and
cigs
or
rhombuses
or
what
whatever
right.
So
it's
so
it's
all
consistent
and
then
I.
Imagine
we'll
have
probably
some
type
of
working
session
with
some
or
all
of
the
tech,
and
whoever
wants
to
show
up
here
and
kind
of
talk
through
what
we
found
to
start
to
plan
some
next
steps.
D
B
Absolutely
I
appreciate
the
input
I
mean
as
I
said:
I
was
myself
trained,
you
know,
and
some
of
those
I
was
like.
Okay,
what's
the
right
way,
what
are
people
going
to
think
and
I
think
you
know
in
all
fairness,
there's
also
two
different
possible
goals.
Right
I
mean
one
of
them
is
to
have
a
tool
and
I
think
this
is
what
Matt
was
drove.
B
Mostly
you
know
the
development
of
the
map
he
put
together
was
you
know,
a
tool
that
captures
as
much
information
as
possible,
so
you
can
work
with
it
and
and
figuring
out
a
lot
of
different
aspects
related
to
all
the
activities
around
openss.
Another
is
you
know
something
that
is
actually
digestible
by
the
mass
right,
the
community
at
large
and
people
who
are
new
to
open,
SF
and
say
what
the
hell
is
going
on.
B
D
I
think
yeah,
especially
like
when
we're
working
with
the
TAC
or
we
go
in
and
talk
to
a
working
group.
The
Mind
map
probably
be
a
better
thing
to
work
with,
just
because
it
might
have
more
information,
and
we
can
say
hey,
why
aren't
you
in
the
readme
or
why
is
this
called
that
or
you
know
what
phase
in
the
life
cycle?
Are
we
that's?
Another
thing
we'll
need
to
capture?
Is
you
know,
is
this
like
exception?
Is
it
mature?
Is
it
retired?
Yes,.
B
D
F
D
Right
so
again,
I'll
try
to
track
down
Bob
to
see
if
we
can
figure
out
how
we
want
to
take
this
work
output
and
share
with
attack
we'll
probably
want
to
put
together
like
a
short
deck,
to
kind
of
walk
the
tack
through
what
we've
been
doing,
what
data
we
found
and
then
maybe
dive
into
like
the
live
demo
section.
Here's
the
Mind
map,
let's
zoom
in
and
zoom
out,
and
explode
it
and
shrink
it.
D
D
D
B
B
A
D
Yeah
I'll
download
it
and
play
around.
Thank
you
again.
I
will
again
try
to
get
us
some
marching
orders
for
next
time,
so
keep
an
eye
on
the
slack
Channel
and
the
mailing
list.
If
you
have
any
other
ideas
or
views
or
viewpoints,
you
want
to
think
throughout
there
for
us
to
think
about.
Please
do
all.