►
From YouTube: SLSA Biweekly (July 6, 2023)
Description
Meeting notes: https://docs.google.com/document/d/1JbJZxeZOWE7rxT24iEozX35LIUl_Yoqd-DeSm6309GA/
A
Okay,
why
don't
we
get
started
hi
everyone
welcome
to
the
salsa
General
community
meeting
as
a
reminder,
if
you
could
record
your
attendance
in
the
meeting
notes,
which
also
has
a
convenience
Alias,
it's
also
the
slash
node
slash
community,
there's
an
attendee
list
right.
There
also
I,
see
other
folks
filling
in
the
Sig
updates.
Thank
you
very
much
for
that.
A
A
A
We
switched
hosting
of
the
website
to
netlify.
That
should
be
a
no-up,
but
if
you
see
any
website
issues,
let
me
know
in
the
spec
meetings
we've
had
I
think
there's
been
one
or
two
small
kind
of
editorial
pull
requests
that
have
been
submitted
and
we've
had
various
discussions
about
Clarity
to
the
spec
feedback
on
1.0,
and
we
kind
of
have
a
queue
of
things
to
work
on,
but
I
think
nothing
major,
that's
worth
bringing
up
here.
A
Unless
anyone
wants
to
chime
in
I
we
had
one
I
didn't
put
in
the
meeting
notes.
We
had
one
question
around
the
a
discrepancy
between
the
in
Toto
protocol
buffers
schema
and
the
salsa
like
our
copy,
because
there's
two
different
versions,
but
that's
been
resolved
on
the
in
Toto
side.
So
in
case
you
happen
to
see
that
that's
that's
being
resolved
and
because.
B
A
C
A
A
Okay,
I
quickly
commented
yeah
and,
and
we
should
update
the
the
pull
request-
titles
in
the
match.
Yeah,
it
was
not
I
think
the
full
request
was
not
intended
to
say
that
we're
doing
a
1.1
release.
It
was
not
I
think
intended
to
make
that
decision,
but
we
do
need
to
make
that
decision
whether
what
we're
going
to
do
all
right
thanks
USA.
A
B
E
Since
none
of
us
have
video
editing
capabilities,
at
least
on
the
call
for
positioning,
we
have
the
content
we
that
we
want
to
talk
about
is
just
how
do
you
get
it
to
a
larger
audience
and
in
terms
of
the
training
modules?
I
I
do
have
the
the
contact
now
for
the
training
module,
so
I'll
start
reaching
out
so
that
we
can
have
not
only
salsa
training
modules
but
for
s2c2
I
think
S2
c2f
already
has
but
potentially
guac
or
Fresca
Etc
anything
supply
chain.
Integrity
related!
F
Yeah,
so
on
the
tooling
side
we
canceled
the
meeting
there
didn't
seem
to
be
a
lot
of
interest
to
keep
participating,
at
least
at
this
time
and
I.
Think
it's
mostly
focused
around
the
actual
building
of
the
tools.
We.
We
got
a
lot
of
folks
who
seemed
interested
in
better
understanding
how
to
consume
tools,
but
without
those
tools
currently
existing
yeah.
That
I
think
there
seems
to
be.
You
know
not
really
a
whole
lot
of
interest
there
so
cancel
the
meeting.
F
But
with
that
said,
I
think
that
there's
you
know
a
couple
things
that
that
are
worth
at
least
highlighting
one.
Is
that
there's
a
lot
of
interest
in
in
obviously
consuming
tools,
but
not
so
much
in
the
building
of
salsa
tools?
So
a
lot
of
folks
are
like
Hey.
How
do
I?
How
do
I?
You
know,
I
have
Jenkins
how
do
I
use
salsa.
F
You
know
what
what
do
I
start
doing
and
and
on
that
end,
but
as
far
as
you
know,
creating,
let's
say,
plugins
or
or
best
practices
or
or
things
on
that
end.
There
didn't
seem
to
be
a
lot
of
interest
in
participating
there.
We
switched
to
being
more,
you
know
async,
so
if
folks
have
things
they
could
definitely
Post
in
the
chat.
F
F
So
there's
some
interest
there,
but
you
know
I,
think
at
this
point
you
know
gonna
put
most
of
the
tooling
stuff
on
on
on
the
back
burner,
at
least
in
the
open
source
space
I
know
there
seem
to
be
a
lot
of
folks
who
are
interested
in
the
salsa
side,
but
they
want
to
keep
that
closed
source
and
and
build
their
own
sort
of
stuff
that
they
can
sell
myself.
I
am
actually
also
working
on
a
bit
of
like
a
salsa
API.
F
Something
to
you
know,
one
of
the
big
things
that's
coming
out
of,
like
the
salsa.
The
sorry,
the
Sterling
tool
chain
from
the
open
ssf
side
is
some
of
the
stuff
that
was
discussed
is
stuff
like
building
kind
of
a
a
control
plane
or
building
an
a
set
of
apis
for
different
pieces
of
the
supply
chain,
and
one
of
the
things
is
hey.
F
If,
if
salsa
is
in
the
build
side-
and
you
might
imagine
that
one
of
the
you
know-
let's
say
the
build,
the
output
like
the
input
might
be
source
code
dependencies
and
the
output
would
be
a
salsa
attestation
and
the
idea
should
be
okay,
as
we
build
out
the
salsa
tool.
The
Sterling
Sterling
tool
chain,
or
whatever
it
ends
up
being
called
things
that
are
Downstream,
would
then
consume
salsa
at
some
level,
and
so
there's
some.
You
know
discussion
and
and
work
happening
on
that
end.
G
Yeah,
my
only
sort
of
massive
comments
is
on
the
tooling,
like
I,
wonder
how
much
but
I
know
there
are
some
people
implementing
salsar
and
I
wonder
if
we
should
be
trying
to
reach
out
to
other
projects
that
we
think
should
Implement
also,
but
that's
it
I
mean
it's
pretty
big.
Ask
doing
that
kind
of
Outreach
I'd
love
to
hear
how
useful
the
current
spec
is
for
the
people
doing
that
work,
though,
and
that'll
be
a
good
way
to
try
and
get
some
some
more
feedback
on
it.
F
There's
a
lot
of
there's
not
like
a
lot
of
interest,
because
when,
when
speaking
to
some
of
these
groups,
one
of
the
things
that
said,
hey
I,
have
you
know
here's
my
list
of
things.
I
need
to
get
done
for
this
project
and
adding
salsa
on.
There
is
a
whole
bunch
of
stuff
and
from
for
the
most
part,
even
even
though
in
in
I
think
walking
them
through
and
seeing
hey.
It's
only
just
a
handful
of
things.
It's
actually
not
that
bad!
It's
just
I
think
folks
are
looking
for
hey.
F
F
Well,
I
won't
say
because
it
seemed
to
be
I,
don't
say
completely
in
confidence,
but
it
seemed
like
a
couple
of
companies
were
like
we're:
building
a
closed,
Source,
salsa
Builder
and
that's
kind
of
going
to
be
our
thing.
We're
going
to
announce
it
at
some
point,
and
so
there
seemed
to
be
interest
on
on
that
front,
and
then
there
was
other
folks
who
were
interested
in
saying:
hey,
I
use
Jenkins.
How
do
I
prove
that
my
Jenkins
could
be
salsa
conformant?
F
What
are
the
practices
and
so
on
and
so
forth
and
I
think
that
there
is
interest
there.
But
as
far
as
a
contribution
standpoint,
there
didn't
seem
to
be
a
lot
of
interest.
There
seemed
to
be
a
lot
of
interest
in
hey.
This
is
a
thing
I
want,
because
I
don't
want
to
switch
off
of
Jenkins,
but
I
also
don't
have
the
time.
You
know
money
resources
Etc
to
to
actually
either.
G
F
F
G
F
F
F
You
know
Jenkins
whatever
it
doesn't
matter,
but
the
idea
is
the
API
itself
is
the
thing
that
calls
the
actual
Builder
and
that
the
idea
it
would
also
be
that
that
API
is
the
trusted
control
plane,
because
you
are
sort
of
running
you
know.
So
the
idea
is,
it's
not
necessarily
a
full-blown
CI
CD
and
then
you
know,
and
so
this
would
be
for
stuff-
that's,
maybe
not
so
much
SAS
side,
but
you
can
imagine
hey
I'm,
running
I,
don't
know
I'm
running,
you
know,
go
build
great
well.
F
This
thing
has
a
very
specific
thing
that
it
runs,
go
build
or
it
uses
an
intodo
layout
or,
however,
you
want
to
kind
of
have
that
set
up,
but
the
basic
idea
is
the
inputs.
Are
the
inputs
salsa
expects
and
the
outputs
are
salsa,
and
so
everything
else
is
sort
of
an
implementation
detail,
as
long
as
it
meets
the
source
of
conformance
requirements
for
the
implementation,
but
I
think
for
the
end
user.
F
F
You
know
I,
think
one
of
the
things
that
that
I've
been
talking
to
open
ssf
about
as
well
is
is
it
might
make
sense
to
do
something
like
here
is
a
salsa
implementation
guide
and
it's
a
case
study
based
on
an
actual
like
yeah.
We
worked
with
this
team
and
we
did
a
b
c
and
d,
and
this
is
salsa
and
it
could
be
just
a
simple
case
right
of
here's.
The
salsa
Builder
that's
baked
into
this
one,
and
in
fact
that
is
something
that
I
know.
Open.
F
Ssf
is
looking
at
to
actually
do
a
case
study
with
some
folks
on
that
and,
in
fact,
I
believe.
Open
ssf
is
willing
to
throw
some
money
to
help
that
make
that
happen
because
I
know,
for
you
know,
or
at
least
you
know,
for
for
certain
companies
where
it's
more
the
publicity.
That's
the
big
thing
you
know
help
work
with
folks.
G
F
F
The
the
this
latter
piece
it's
about
for
the
at
least
the
open
ssf
has
been
about.
How
do
you
drive
more
end
users
to
come
in
okay?
Well,
let's
build
some
end
user
guides
so
that
folks
better
understand
how
to
actually
adopt
what
openssf
is
building
out
and
then
with
that
said,
though,
I
think
that
there's
probably
is
probably
worthwhile
to
do
the
other
one
as
as
well,
though,
I
think
there's
going
to
be
a
lot
of
push
on.
F
G
Yeah,
but
there
aren't
quite
a
few
open
source
tools
that
that
you
could
do
that
work
with
right
and
provide
that
kind
of
story
of
how
what
changes
were
required
and
how
what
changes
you
made
to
get
to
that
point,
which
I
think
would
be
really
useful,
but
yeah
cool
thanks
for
the
thanks.
Thanks
for
the
discussion,
I,
don't
want
to
take
any
more
time
unless
anyone
else
has
anything.
We
want
to
add.
D
D
Questions
such
as
there
were
questions
at
the
last
meeting
about
oh,
should
the
steering
committee
be
more
transparent
or
should
members
be
more
active
and
there
was
even
a
a
higher
meta
level
question
which
is:
should
there
should
do?
We
even
need
the
steering
committee,
so
I
took
the
chance
to,
and
I
really
would
like
to
share
screen
now,
but
I'm
not
sure
why
Zoom
is
not
cooperating.
So
sorry
about
that.
D
Some
high
level
thoughts
of
mind
and
I'd
love
to
hear
discussion
from
everyone,
but
by
the
way,
I
need
I
need
help
from
one
of
the
steering
committee
members
to
make
a
copy
of
this
document,
because
I,
unfortunately
can't
make
this
public.
So
if
anyone
who
has
power
can
do
that,
please
make
a
copy
of
this,
make
it
public
and
share
it
with
the
rest
of
the
community
please
so
anyway.
What
I
want
to
make
a
little
argument
about
today
is
why
we
need
a
steering
committee.
D
One
thing
that
I
found
missing
is
that
we
don't
have
an
explicit
Charter,
so
if
you
go
to
a
governance
dot
right
now,
it
talks
about
what
the
steering
committee
members
are
supposed
to
do,
but
in
way
of
example,
so
it's
not
really
clear
whether
we're
missing
anything
here,
whether
they
are
minimum
requirements.
In
my
view,
a
steering
committee
should
do
important
things
like
one
of
the
things
that
we
do
in
other
communities,
such
as
in
Toto,
which
I'm
going
to
use
as
a
large
example.
D
Here
we
use
the
steering
committee
as
one
of
the
things
is
to
define
a
roadmap,
for
example,
so
things
like
what
are
we
going
to
do
next
for
salsa
2.0,
conformance
program,
testing
policy,
still
security
level
four,
or
do
we
focus
on
source
security?
There
are
all
these
questions
to
answer,
for
which
I
think
we
need
a
certain
committee
and
then,
of
course,
the
basic
things
like
conflict
resolution,
which
we
hope
doesn't
happen
too
often,
but
I
think
that's
also
an
important
function
and,
of
course,
whatever
the
next
steering
committee
does.
D
It
does
need
to
address
questions
feedback
from
the
community,
such
as
being
sufficiently
active.
What
does
that
mean?
We
need?
We
need
to
show
more
transparency,
even
if
we're
meeting
once
a
month,
we
need
to
take
maybe
make
the
meeting
public
take
public
notes,
at
least,
and
all
that
sort
of
stuff
we've
also
to
add
some
other
values.
D
That
I
think
we
need
neutrality,
fiduciary
responsibility
for
the
lack
of
a
better
term,
in
other
words,
trying
to
make
sure
you're
doing
the
best
for
the
community
as
opposed
to
just
whoever
you
happen
to
represent,
and
so
I
had
this
document
here,
I
highly
encourage
the
current
committee,
as
well
as
the
community,
to
take
a
look
at
it.
I've
included
things
like
the
mission
and
the
charter,
and,
as
part
of
all
of
this,
we
need
to
use
Bruno's
excellent
work
on
trying
to
nail
down
the
election
process
too.
D
There
are
some
specifics
now
that
we
don't
I,
think
we
don't
need
to
get
too
hung
up
about
I
copied
it
from
in
dodo,
so
accidentally
reduced
the
number
from
seven
to
five.
That
was
not
intentional.
This
was
just
copying,
someone
else's
good
work,
and
so
we
should
talk
about
all
of
this.
One
thing
that
I
personally
like
to
see
that
I
like
to
end
with
the
next
committee.
D
In
my
opinion,
something
that
we
haven't
really
considered
in
my
opinion
is
how
build
platforms-
proprietary
well,
not
entirely
proprietary,
but
self-hosted
build
platforms
such
as
those
used
by
say
the
districts
such
as
Debian,
how
they
would
be
able
to
use
also
anyway,
I
stopped
here.
I
hope
this
makes
sense
and
I
see
a
few
questions
in
the
chat.
Let's
see
yes,
yes
or
no
I
know
it's
right.
He
has
a
lot
of
the
feedback
here
that
we
saw
the
last
time.
Yes,
it
does
need
to
be
more
transparent.
D
E
C
C
C
This
group
to
define
the
roadmap
with
some
kind
of
you
know,
trying
to
be
more
collegial
and
and
I.
That's
why
I'm,
like
you
know,
I
and
I
did
say
it
was
being
provocative
of
me
to
say:
hey.
Do
we
even
need
an
AC
because
I'm
not
trying
to
kill
it
necessarily,
but
I
think
it
has
to
be
clearly
defined.
What
the
value
is
so
I
will
read
it
and
you
know
I
reserve.
My
final
opinion
on
that
I.
E
C
E
Yeah
the
road
map-
one
I
mean
it
was
me
Aaron
and
I-
can't
remember
who
else
that
created
the
road
map
and
we
presented
to
this
broader
community
and
we
said:
does
it
make
sense
right
and
we
did
agree
on
what
we
should
do
in
terms
of
not
defining
timelines,
because
we're
always
missing
them
right,
just
high
level?
This
is
what's
now,
but
this
is
what's
later,
so
we
don't
necessarily
need
a
steering
committee,
but
for
a
roadmap,
but
I
do
think.
D
Sure
yeah,
let
me
try
to
clarify
that
what
I
meant
to
yeah
look
excellent
points.
I
guess
I
should
clarify.
So
what
I
mean
is
yes,
even
if
the
roadmap
is
not
entirely
defined,
perhaps
not
even
largely
defined,
but
is
there
in
committee
at
all,
as
you
said,
I
still
think
it's
important
to
try
to
have
a
group
that,
like
I,
said
earlier,
values
such
as
being
neutral
and
the
fiduciary
the
responsibility
of
the
lack
of
a
better.
That
makes
any
sense
to
try
to
make
sure
that
we
capture
the
community
voters.
D
But
again,
maybe
steering
committee
is
not
the
not
the,
maybe
two
two
two:
what
do
you
call
two
burdensome
an
option?
So
that's
something
so
here's
what
I
recommend
right,
I
think
I
think
it's
very
important
for
the
steering
committee,
the
current
steering
committee
before
the
next
monthly
meeting
to
read
this
document
comment
on
it
and
we
should
have
another
meeting
where
we
should.
H
A
I
think
maybe
to
the
point
about
like
who
does
it
perhaps
it
it's
it's
correct
to
say
that
the
steering
committee
is
a
count
like
in
a
racy
sense,
responsible,
accountable,
something
informed.
So
I
can
remember
what
this
is
I
either.
The
steering
committee
is
accountable
for
the
roadmap,
but
is
not
necessarily
the
one
responsible
for
actually
doing
doing
it.
Oh
consulted
and
so
I
think
there
could
be
multiple
people
responsible
or
consulted,
but
I
think.
C
C
We
need
to
have
more
transparency
and,
in
fact,
I
think
you
know
part
of
the
reason
that
some
of
us
say
do
we
even
need
an
AC
is
because
there
is
currently
no
transparency,
so
I
highly
recommend
that
you,
you
stopped
being
transparent
right
now
and
and
so
that
people
can
appreciate
what's
being
done
by
DSC.
Then
people
are
not
going
to
question.
Why
do
we
need
one
in
the
first
place
and-
and
you
know
last
time,
I
raised
that
question
I
would
sell.
C
Well,
that's
because
we
haven't
really
been
doing
much
and
then
it
just
reinforces
this
feeling
that
well
then,
why
do
we
even
need
one
if
you
guys,
aren't
really
doing
anything
anyway?
So
it's
a
bit
officious
vicious
cycle
that
I
think
you
need
to
try
to
Break
by
being
more
transparent
and
and
show
what
the
value
is.
F
Yeah
I
think
I
I
agree
with
Arno
on
on
that.
I
think
that
if
we
take
a
step
back,
you
know
we
haven't
had
any
sort
of
official
meetings
and
and
more
or
less
the
steering
committee
was
more
or
less
used
as
it
previously.
As
a
sort
of
hey
here
are
members
of
the
community.
Who've
been
more
like,
they
were
actually
more
like
maintainers
than
necessarily
purely
steering
committee
members,
and
it
was
more
of
like
hey.
This
doesn't
sound
like
what
we
want
to
do
with
salsa.
F
B
For
some
reason,
I
have
issues
with
the
sound
on
the
on
the
box
here
so
steering
committees.
We
have
a
whole
working
group
that
sits
above
this
is
above
this
sig
right.
That's
where
your
steering
committee
should
live
the
steering
committee's
Drive
strategy.
They
don't
drive
road
maps,
they
drive
strategy.
B
That
being
the
case,
I
would
say
that
you
would
have
a
steering
committee
steering
committee
at
the
working
group
level
that
governs
all
of
the
work
being
done,
framework-wise
or
whatever
across
the
entire
working
group,
and
then
you
will
have
sub
committees
for
each
respective
framework
and
then
each
Sig
would
develop
their
own
road
maps
to
report
them
to
those
subcommittees.
That
reports
it
to
the
largest
steering
committee.
B
That
should
be
steering
strategy
across
the
entire
work
group,
with
respect
to
Frameworks
and
tools
that
are
being
developed
for
the
purpose
of
consumption
of
end
users
outside
of
that
environment.
This
is
just
a
hierarchical,
hierarchical
structure
that
could
be
developed.
That
would
take
a
lot
of
the
additional
thought
out
of
the
way
and
provide
that
racy
environment.
That
Mark
was
talking
about
earlier
right.
B
You
could
develop
a
solid
racy
structure
based
on
that
that
you
could
then
say
who's
responsible
for
what
who's
accountable
for
the
entire
situation,
who
should
be
consulted
and
then
who
should
be
informed
that
makes
that
linear
right
that
makes
that
well
understood,
well-defined
and
linear.
When
you
don't
just
try
to
bring
a
steering
committee
down
into
a
group
and
I
hear,
and
what
I
hear
here
with
respect
to
a
steering
committee
and
what
I
hear
about
about
the
the
the
the
the
the
yeses
and
no's
is
wrapped
around.
B
Well,
how
can
you
form
a
steering
committee
inside
of
a
Sig?
That's
been
going
I,
Won't,
Say
I'm,
not
going
to
say
aimlessly,
but
that
has
been
going
with
a
strategy
that
has
been
going
with
a
perceived
road
map
based
on
a
perceived
strategy
and
then
you're
going
to
form
a
steering
committee
out
of
all
of
that
for
what
purpose?
Now?
B
That
should
be
tossed
up
a
little
higher
so
that
it
could
be
formed
and
defined
in
such
a
way
that
can
now
provide
governance
down
to
the
Sig
rather
than
the
sick,
trying
to
govern
itself.
Hence
how
we
got
here
having
this
conversation
now
versus
when
Melba
and
Aaron
this
time
last
year
was
trying
to
provide
a
road
map
against
a
dare
I
say
a
non-strategy.
The
strategy
wasn't
even
formed
then,
but
Melbourne
Aaron
is
trying
to
form
a
road
map
against
what
you
form
a
road
map
against
the
strategy,
not
the
other
way
around.
G
Yeah
I
think
I
just
felt
the
need
to
point
out
that
historically,
the
the
steering
committee
predates
like
some
of
the
structure
in
the
open
ssf,
so
we
can
set
we.
We
should
consider
whether
the
steering
committee
makes
sense
within
the
within
the
current
and
established
structure
of
the
openness
of
a
yeah
we're
not
trying
to
form
a
steering
committee
now
like
in
contention
with
that
structure.
We
have
a
steering
committee
that
has
been
super
useful
at
times.
G
C
C
G
F
We
don't
really
have
a
road
map.
We
still
haven't
really
decided
on
what
we're
really
focused
on
next
there's
a
couple
of
things,
obviously,
that
we're
still
you
know,
that's
still
being
done
like
the
conformance
stuff
and
and
some
folks
are
still
working
on
some
tools,
but
I
I
think
it
is
probably
worthwhile
for
us
to
maybe
go
back
and
do
a
deep
dive
here
on
on
salsa,
just
to
kind
of
go
back
and
say
hey.
F
What
is
the
thing
that
that
salsa
is
going
to
be
focused
on
next?
What
is
the
thing
that
that
the
community
has
decided
on
and
and
so
on,
because
I
think
the
you
know,
a
lot
of
these
points
are
a
little
boot
when,
when,
as
far
as
what
is
salsa
working
on
in
the
future-
or
you
know
even
just
from
a
general
Community
consensus,
hasn't
been
built.
Yet
sorry,
Imelda.
E
E
I,
don't
know,
maybe
aprilish
time
frame
of
what
we
were
going
to
work
on
now,
all
right,
post,
1.0
versus
what's
coming
up
next,
was
if
we
get
to
it,
we
get
to
it,
but
we're
not
it's
not
going
to
be
a
priority,
but
this
is
what
we
decided
as
a
group
I
believe
it.
It
was
actually
in
one
of
these
meetings
in
the
bi-weekly
meetings
that
this
is
what
we
were
going
to
do
now.
E
B
F
F
A
Think
pretty
successful,
is
like
a
mission
statement
which
is
like
a
one
sentence,
a
very
short
one
sentence
thing
and
you
could
look
them
up
online.
Various
companies
have
ones
and
some
sort
of
like
Clear
Vision,
for
what
we
want
it
to
look
like
in
the
future
and
I.
Think
I've
had
a
lot
of
I've
heard
feedback
from
a
lot
of
people
that.
H
A
Nice
certainly
to
anyone
outside
of
people
like
in
this
meeting.
They
don't
really
know
where
it's
also
going.
They
don't
kind
of
have
a
picture
for
like
what
we
want,
salsa
to
become,
and
so
agreeing
on
that
which
is
much
higher
level.
Much
more
abstract.
Maybe
you
know
like
ideally
a
couple
paragraphs
or
something
maybe
a
picture
I
think
is
really
valuable
and
then
once
we
have
that
and
to
Jay's
point,
then
we
could
work
and
it'll
be
easier
for
us
to
work
toward
that
and
we
could
talk
about.
A
C
D
H
Yeah
I
on
the
roadmap
topic
as
well,
I
mean
knowing
what
we
know
from
the
1.0
process.
Right,
which
took
much
longer
I
mean
that
roadmap
has
a
lot
of
things
on
it
and
so
being
able
to
not
just
say
here
are
the
things
you
would
like
to
do,
but
here's
the
priority
I
think
is
something
that
we
could
probably
work
on.
H
D
D
I
think
we
should
read
this
document
as
soon
as
possible
and
then
meet
I
proposed
meet
as
early
as
next
week,
so
that
by
the
time
the
next
monthly
meeting
comes
along,
we
have
a
much
better
picture
and
a
story
to
tell
the
community
about
where
we
think
things
should
go
next
and
have
some
concrete
solution.
What
does
everyone
think.
F
Michael
yeah,
so
that
sounds
good
and
I
think
also
along
those
lines
is
I,
don't
want
to
go
the
full-blown
racy
thing
again,
but
I
do
think
that
it's
probably
worthwhile
to
even
just
sort
of
say,
maintainer
steering
committee
member,
whatever
you
want
to
call,
but
one
of
the
folks
who
is
who
is
being
core.
You
know
in
the
community
on
some
of
these
things
just
saying
that
they
are
sort
of
responsible
from
the
standpoint
of
just
keeping
Folks
up
to
date
on
what
the
status
is.
F
Even
if
the
status
is
nobody
seems
interested
or
there
hasn't
been
a
lot
of
work
on
it,
not
necessarily
saying
that
they're
doing
the
work
just
sort
of
driving
the
conversation
I
think
is
also
worthwhile,
because,
when
I
look
at
a
lot
of
the
different
things
on
the
roadmap,
one
of
the
things
that
kind
of
comes
to
mind
is
hey.
Who
is,
let's
say
the
one
who
is
just
saying:
yep
I
talked
to
the
community
about
doing
this
thing
and
I.
F
Couldn't
we
couldn't
find
folks,
because
even
that
I
think
is
helpful
rather
than
just
we
don't
know
so
so.
I
I
think
that
would
be
helpful
as
well
as
just
to
kind
of
say:
hey
who's
going
to
lead
up
at
least
the
conversation
on
you
know,
Chris
is
doing
conformance
and,
and
some
of
the
other
folks
are
doing
some
of
the
other
things.
F
But,
let's
say,
like
you
know,
I
could
take
like
the
tooling
pieces
and
say:
hey
I,
reached
out
to
these
folks
about
verification
tools,
and
here
there's
some
folks
working
on
it
or
I.
Don't
have
resources.
So
if
we
got
some
resources,
we'd
be
able
to
work
on
it,
but
I
think
even
that's
better
than
just
kind
of
where
we're
currently
at
which
is
just
it's
got
a
communication
silence
on
it.
A
End
and
other
things
begin
because
actually
this
is
probably
goes
a
long
way
to
what
we're
we're
talking
about
in
this
meeting.
I,
don't
know
if
other
folks
have
read
this
I've
not
seen
this
document
before
here
and
so
I
think
that
helps
a
lot,
but
thanks
trishank
for
getting
this.
This
going
I
look
forward
to
like
kind
of
resolving
this
and
making
the
org
work
more
effectively.