►
From YouTube: End Users Working Group (August 18, 2022)
Description
Meeting notes: https://docs.google.com/document/d/1KQalBRzfRBvsqh73JUYfp1KG-AJdXcv2Z8LTIFoQP8c
E
F
A
D
A
B
D
A
A
All
right,
let's
kick
off,
so
doesn't
currently
look
like.
We
have
any
new
friends
on
the
group
today,
one
of
the
things
that
I
think
we
should
be
doing
as
we're
getting
a
bit
closer
to
being
made
a
a
fully
fledged
group
is
getting
sort
of
additional
members.
I
know
I'm
in
touch
with
a
lot
of
other
people
and
I'll
be
inviting
people
to
the
group
too.
A
A
E
A
D
A
D
D
The
project
made
a
little
presentation.
They
had
a
have
weekly,
no,
not
weekly,
regular.
Let's
go
with
that
community
meetings
they
will
be
having
they
will
be
trying
to
get
into
open
ssf
under
some
working
group
or
other
at
the
moment
of
the
existing
working
groups.
The
best
fit
for
that
is
the
best
practices
working
group,
but
I
believe
that's
just
because
we're
not
official
yet
because
really.
D
D
That
document
includes
links
to
the
specification
itself
and
their
github
repo,
which
is
where
it
lives.
So
I
just
wanted
to
mention
it
to
you
all
in
case
you
wanted
to
have
a
look.
They
will
be
presenting
officially
to
open
ssf
people.
Let
me
drop
a
link
to
that.
If
someone
hasn't
there,
we
go,
they
will
be
presenting
officially
to
open
ssf
working
group,
one
or
more,
I
believe
krobe
is
helping
to
coordinate
that,
so
they
can
figure
out
where
they
want
to
live
under
the
open
ssf.
D
So
I
made
sure
that
they
knew
that
we
were
a
going
concern,
we're
soon
to
become
an
official
working
group
and
prognose
to
make
sure
that
this
working
group
is
a
part
of
that
scheduling.
So
we
can
try
to
have
only
one
demo
from
them
for
multiple
working
groups
rather
than
having
them
do
the
same
demo
three
plus
times.
G
Actually,
looking
for
because
there's
actually
another
part
of
this
vicky
that
I
was
actually
going
to,
let
you
in
on
from
michael,
so
I
don't
know
if
you
want
to
I'll
send
it,
but
I
don't
know
if
you
want
to
get
michael
in
touch
with
chris,
because
there
is
another
part
of
this
that
was
presented
yesterday
by
michael
in
the
security
integrity
meeting.
So
he
wanted
to
present
to
a
few
different
places.
G
D
D
C
D
G
G
H
G
This
is
actually
so
from
my
understanding.
This
is
part
of
their
implementation
at
microsoft
that
they're
trying
to
move
out
yeah.
This
is
why
it's
so
azure
focused,
but
I
know
that
that's
not
like
a
huge
thing,
that's
just
an
idea,
and
I
know
that's
based
on
the
fact
that
openssf
has
azure
credits,
but
but
from
my
understanding
this
is
one
of
the
ways
that
they
take
that
framework
and
implement
it
at
microsoft.
C
G
H
G
And
that's
the
thing
real
quick.
Let
me
point
out
so
the
big
thing
with
this,
because
they
have
a
part
there
where
they
can
compare
frameworks.
The
big
difference
with
this
framework
is
that
it
covers
end
users
like
most
of
our
other
frameworks,
are
more
on
the
producer
side
of
things,
so
this
is
one
that
actually
covers
both
sides
of
the
argument.
F
A
G
A
G
H
It
doesn't
have
some
of
the
risk
and
compliance
use
cases
that
would
be,
you
know,
make
it
completely
relevant,
say
for
a
highly
regulated
industry,
given
the
fact
that
it
came
from
microsoft,
but
there's
there
are
a
lot
of
steps
in
this
process
here
that
would
be
useful,
be
under
like
definitely
have
to
understand
the
implementation.
From
a
tooling
perspective,
better.
H
G
A
D
B
G
Thank
you,
I
do
think
vicky.
They
need
a
little
bit.
The
whole
microsoft
team,
including
adrian,
needs
a
little
bit
of
orientation
about
how
open
ssf
works,
because
I
don't
think
that
they're
necessarily
clear
on
like
where
what
goes
where,
because
I
know
that
yesterday,
we
kind
of
hijacked
the
meeting
with
this
presentation.
I'm
not
trying
to
be
like
that
about
it,
but
it
is
true.
D
Yeah,
no,
I
I
understand
which
is,
I
know
that
both
michael
and
ava
were
in
the
the
call
on
tuesday.
So
it's
not
like
they're
lacking
for
open
ssf
experience
in
their
group.
It
just
could
be
that
there
wasn't
enough
communication
in
advance
and
that
sort
of
stuff,
when
you
know
we're
people
communication
is
hard.
That's
fine,
fair.
D
G
A
Very
cool
all
right,
so
if
we
can
move
on
the
agenda,
then
I
think
that's
that
has
that
one
covered
next
one
we
have
is
meeting
frequency.
So
we've
had
a
few
suggestions
about
timing
and
we've
settled
on
seven
pdt,
but
in
terms
of
meeting
frequency.
Any
suggestions
on
how
often
to
me
I
I'd
suggest,
like
biweekly,
but
any
any
thoughts,
otherwise.
B
A
H
A
Excellent
sounds
good
to
me
so
noted.
Thank
you
very
much
so
next
gender
item,
so
great
news
becoming
a
real
working
group
right,
so
this
this
formed
some
time
ago
a
loose
band
of
people
right,
but
I
think
we're
now
getting
to
the
point
where
I
believe
this
is
the
fifth
meeting.
We've
got
in
there
the
the
list
of
steps
to
go
to
become
an
official
working
group.
A
I
think
if
we
open
that
up,
I
think
we
need
to
start
talking
to
a
tech
sponsor,
but
I
think
we've
we've
hit
the
other
goals.
So
if
you
look
at
it
become
incubating,
we
need
to
have
met
at
least
five
times
at
least
five
interested
individuals
from
at
least
three
different
organizations
attending
regularly.
A
A
H
C
F
F
Yeah,
I
I
see
one
of
the
purposes
of
the
group
is
continuing
to
lobby
for
the
view
that
the
needs
and
interests
and
perspectives
of
end
users
are
distinct,
that
we,
we
just
have
different
dna
when
it
comes
to
thinking
about
these
problems
from
from
vendors
who,
who
necessarily
have
a
different
view.
So
it's
important
to
have
both
sides
of
the
coin
represented.
A
A
F
H
A
B
F
A
D
A
H
A
B
One
thing
I
wanna,
so
we
have
robert
because
we
missed
kind
of
introducing
him
at
the
beginning
of
the
caucus
he
jumped
a
bit
late.
He
he's
recovering
from
being
sick,
so
I'm
not
gonna
put
you
on
the
spot,
but
kind
of
wanted
to
highlight
that
he'll
be
joining
a
lot
of
the
upcoming
conversations
on
my
behalf.
B
B
A
Excellent
excellent,
really
look
forward
to
your
support
and,
as
we're
saying
I
think
now
is
the
time
we
can
start
to
bring
in
additional
members
to
the
team
and
the
working
group
sort
of
advertise
a
bit
as
we
start
to
make
a
a
formal
working
group
from
it
very
good
and
hope.
You
feel
better.
Robert.
D
A
G
D
A
A
H
F
I'm
in
favor,
I
think
the
main
objection
that
folks
had
was
that
it
may
cause
confusion
about
whether
we
mean
end
users,
the
human
beings
or
end
users,
the
the
organizations.
And
so
when
we
wrote
the
mission
and
the
vision
we
made
sure
to
mention
organizations
to
tamp
down
on
the
confusion
so
yep.
I
think
your
next
acceptable
cost
for
the
otherwise.
You
know
simplicity
and
obviousness.
A
A
So
next
to
gender
item,
where
to
start
so
I
think
it's
useful
to
sort
of
put
together,
maybe
a
roadmap.
We
already
have
effectively
our
outline
our
mission
statement,
but
I
think
it
would
be
useful
to
start
to
pull
some
of
those
threads
and
try
and
figure
out.
You
know
what
are
the
steps
and
milestones
or
roadmap
to
start
to
make
that
happen.
D
H
Yeah,
I
updated
that
this
morning,
just
added
a
couple,
a
couple
of
items
to
it.
I
think
there
are
two
that
are
important
we
want
to,
or
it
behooves
us
to
to
get
a
couple
more
traditional
end
user
consumers
on
the
working
group.
So
I
I
think
putting
together
a
list
of
folks
would
be
helpful
and
then
the
other
is
creating
collateral.
That's
relevant
for
end
users,
because
so
much
of
the
open,
ssf
collateral
collateral
is
focused
on
producers.
H
H
H
B
And
my
in
my
experience,
it's
been
more
like
there's,
not
there's
nothing
like
on
the
technical
side
of
what
you
would
get
out
of
it
outside
of,
of
course,
all
of
the
products
that
openness
is
doing,
but
there's
nothing
like
a
group
or
forum
or
something
that
you
can
be
a
part
of
and
which
is
a
lot
of
what
we
are
trying
to
get
out
of
this
group.
So
I
think
it's.
B
It
would
be
really
great
if
we
start
adding
that
to
the
marketing
material
as
it
would
get
us
get
people
interested,
because
it
was
a
struggle
for
me
to
see
okay.
So
what
do
I
get
out
of
this?
Like?
Is
there
some
forum
a
lot
of
those
people
that
they're
marketing
to
or
organizations
they're
in
other
organizations
as
well,
that
do
have
indies
or
forums?