►
From YouTube: SLSA Positioning Meeting (December 13, 2022)
Description
Meeting notes: https://docs.google.com/document/d/1tpPOXVzNSwtpWA7cXhTPLAO6HIP50obUvoP85XqgVHM/edit#heading=h.yfiy9b23vayj
SLSA repo: https://github.com/slsa-framework/slsa
A
B
B
B
So
I
guess
let
me
ask
you
a
question
because
it
could
be
just
Just.
Me,
Myself
and
I
I
feel,
like
I,
have
partly
to
blame
not
been
as
productive
as
we
could
have
been
given
like
all
the
canceled
sessions
Etc,
and
given
that
obviously
I
don't
dedicate
a
lot
of
time
to
this
so
trying
to
get
a
feel
from
the
group
on
you
know:
how
can
we
improve
next
year?
B
D
A
D
D
Like
friends,
I'll
give
you
an
example
of
it,
we're
writing
a
positioning
doc.
At
the
same
time,
they
made
a
decision
to
break
off
source
and
build
oh
by
the
way,
they've
also
broken
off
Providence.
Now
yep
right
with
that,
that's
like
we!
How?
How
are
we
like?
Let's,
let's
say
we
got
that
done
fast-
it
would
have
been
wrong.
D
Yeah,
the
the
part
that
the
part
that
I
said
I
don't
know
that
it
that
it
so
the
part,
that's
that
will
conflict
with
this
right,
it'll
be
a
competing
priority
thing.
Do
we
tell
them
to
slow
down
right,
I
mean
it's
like
you
don't
be
like
hey
hold
on
a
second.
Let
us
get
that
part
out
before
we
can
do
you
know
or
or
do
we
or
do
we
base
what
we
do
on
forecasting
right
so
so
is.
It
is
the
way
that
we
position
now
something
that's
future
State,
rather
than
current.
B
C
A
B
D
Yeah,
that's
what
I
meant
by
a
smaller
Target
right
like
like
we,
we
small
a
target
with
a
with
an
even
smaller
shock
group
right.
You
know
one
thing
at
a
time
focusing
on
that
and
then
yeah
that
that
that's
a
that's
a
huge,
huge
plus
one
for
me,
I
mean
at
least
that
way
and
and
then,
if
we
we
did
that
and
then
I
I
guess
I
said
focused
on
on
future
State
stuff
right.
D
But
if
we,
if
we
did
that
and
then
made
it
above
a
future
state,
it
might
be
something
that
we
can
that
we
can
dig
into,
and
it
still
has
relevance
like
a
like
a
couple
of
weeks
from
now,
rather
than
we
dig
into
it,
and
then
we
look
up
and
then
like
well,
we
did
a
whole
bunch
of
work
yep
for
almost
nothing.
You
know,
I
mean.
B
D
We
really
got
our
our
Minds
Twisted
when
we
look
back
at
the
spec
as
it
was
from
when
we
started
it
and
to
when
we
were
working
on
the
in
the
middle
and
we
look
back
at
the
spec
and
we
saw
the
split
that
really
and
and
then
when
we
saw
the
split
and
then
and
then
the
fact
that
the
split
didn't
take
hold
across
all
of
the
the
different
media,
Outlets
or
different
Outlets,
that
were
the
blogs
that
were
being
used
across
the
Spectrum.
Then
there
was
confusion,
I.
D
The
the
big,
the
the
big
that
the
head
got
a
little
ahead
of
itself
and
that
really
that
really
drove
a
drove
away.
We
had
we
asked
questions
that
required
answers
that
weren't
really
like
for,
like,
for
instance,
right
now.
We
asked
questions
that
require
answers,
that
we
still
have
to
wait
to
get
I.
Think
I,
think
you
you,
you
know
having
having
the
the
the
other
Sig
leads
attend.
D
A
D
Know
just
or
at
least
a
representative
right,
maybe
it
doesn't
have
to
be
the
the
leads.
Maybe
it
could
be
a
representative
I
I
either
way
us
having
being
able
to
ask
a
question
real
time
or
or
or
that
or
the
whatever
the
the
answer
might
be,
or
whatever
you
know
whatever
that
variable
or
parameter
is
we're
able
to
address
it
right
then,
and
there,
rather
than
having
to
go
back
based
on
something
we
see
to
get
something
clarified
before
we
can
before
we
can
push
on
yeah.
B
Yeah
we
could
potentially
even
revisit
the
schedule.
I
know
there
were
some
assumptions
made
at
the
beginning
when
we
were
figuring
out
the
schedule
for
this
call
that
they
wanted
certain
people
to
be
part
of
this
call,
but
they've
only
ever
attended
to
meetings
at
the
beginning,
and
so
that
shifted
what
actually
the
majority
was.
So
potentially
we
need
to
revisit
also
the
schedule
so
that
other
people
could
potentially
join
from
the
other
six
I
know.
B
Mike
does
a
good
job
and
I
know
he's
been
on
conferences
and
things
like
that,
and
he
said
he
was
going
to
step
away
for
a
little
while
right.
So
that's
an
example
of
the
tooling
thing
right.
He
he
holds
that,
but
for
the
specification,
Mike
is
the
closest
thing,
but
he's
not
necessarily
a
lead
right,
so
it'd
be
good
to
get
Josh
Orr
mark
because
they're
driving
a
lot
of
the
background
stuff.
Well.
D
So
that
that's
what
I
was
going
to
say
too,
they
have
to
be
somebody.
That's
that's
not
that's!
On
the
the
the
ugly
well
I
say
internal
internal
to
to
to
them
external
to
us
right.
Somebody
on
the
side
where
some
of
the
conversations
are
happening
off.
You
know
off
mic.
I
guess
you
know,
they'd
have
to
be
privy
to
a
lot
of
that
stuff
too.
B
Yeah
correct
and
that's
where
I
think
the
the
two
leads
come
in
for
specification
at
the
very
least
I
know:
Mark
drives
a
lot
of
it.
Yeah
and
I
know
there's
other
Google
employees
that
also
drive
a
lot
of
it
behind
the
scenes
and
then
I
know
Josh
is
at
the
VMware
side
and
I'm
sure
he
has
conversations
with
Mark
all
the
time,
so
either
one
of
those
I
think
would
be
more
clued
in
I.
B
A
D
D
D
B
B
B
D
D
B
B
D
B
A
D
B
B
B
B
B
B
B
Yeah
there
is
so
depending
on
what
happens
right
might
start
getting
working
on
on
the
other
stuff.
So
if
you're
all
are
here,
I'll
see
you
next
week.
If
not,
then
I'll
see
you
next
year,
okay,
going
once
going
twice:
okay!
Well
thanks
everyone
for
joining,
and
hopefully
we
can
get
some
answers
from
the
larger
Community
about
how
to
improve
next
year.
Yeah.