►
From YouTube: SLSA Positioning Meeting (October 4, 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).
B
I'm
sitting
here
watching
that
I
was
watching
a
YouTube
replay
of
the
reinforce
the
AWS
reinforced,
where
they
gave
a
a
an
elongated
one-hour
talk
on
oscow.
B
Send
me
no
Sydney
and
I'm
sitting
here
watching
it,
because
I
I've
read
some
I've
read
so
much
documentation
on
oscow
and
I'm
still
left
with
okay,
how
the
hell
do
you
operationalize
it,
but
I
get
I,
get
taking
the
controls
and
putting
them
in
language
either
you
do
XML,
Json
and
yaml
formats,
I
I
get
that
I
get
putting
all
the
controls
there.
I
get
the
the
the
implementation
models,
the
assessment
models,
the
profile
models,
I
get
all
of
that
I
get
ssps
I
get
everything
I
get
all
of
that
I'm!
Saying!
Okay!
B
After
that,
how
the
hell
do
you
often
tell
me
how
you
gen?
What
what
artifact
gets
generated
from
this
that
you
that
that's
so
it's
machine,
readable,
okay,
I
I,
get
the
premise,
but
what
gets
generated
that
says
that
gives
me
some
type
of
foot
a
warm
and
fuzzy
about
my
security
posture
or
about
my
under
my
my
understanding
of
of
risk
outside
of
what
I
normally
do.
A
B
B
A
Well,
I
I
would
still
like
that
that
link,
if
you
could
no
I'm,
not
going
to
promise
I'll,
listen
to
it,
but
it
sounds
like
it's
at
least
somewhat
informative
I'll.
A
A
I
am
trying
to
get
it
to.
Let
me
share
something
desktop
one
I
have
a
new
system.
A
C
A
Okay,
oh
it
wants
me
to
quit
so
I'm,
not
gonna
quit
so
I
just
won't
share
I'm
just
in
the
meeting
notes,
folks,
okay,
so
if
you
can
sign
in
I'll
repost
the
link
here
in
case
you
weren't
on
earlier
and
let's
see
I
know,
Mike
Lieberman
said
he
wasn't
going
to
be
able
to
join
and
I.
Forget
the
Josh
Joshua.
A
Mullikin
said
he
wouldn't
be
able
to
join
wow
another
man,
Bruno
I'm,
starting
to
realize
how
out
of
shape
I
am
in
comparison
to
you.
You
did
an
Iron
Man
like
about
a
month
ago,
you're
a
half
marathon.
This
last
weekend,
that's
I
I,
like
the
enthusiasm
I
like
the
athletic
athleticism,
but.
A
Oh
I,
yeah
I've,
been
trying
to
get
back
into
running
myself.
I
feel
like
I,
took
a
six-year
Hiatus,
but
it's
hard
to
find
a
consistent
time
for
for
myself,
so
I'm
trying
to
figure
that
out,
I,
don't
know
how
you
can
schedule
time
for
a
half
marathon.
A
Yeah
yeah,
let's
see
and
then
Jeff.
Oh,
are
you
doing
a
CPR
class
Jeff.
E
In
my
copious
amounts
of
spare
time,
I'm
an
EMT
and
a
CPR
instructor,
so
that's
that's
what
we're
gonna
be
doing.
Wow.
A
Yeah
well,
I,
don't
know
if
anybody
else
wants
to
share
any
anything
interesting
about
themselves
for
this
week
or
today.
A
If
not,
I
can
go
I'm,
I'm,
actually,
volunteering
for
the
first
time
as
a
Assistant
math
coach
for
kindergarteners.
It
should
be
interesting.
They
play
games,
it's
not
really
like
Edition
or
anything.
They
just
play
a
bunch
of
strategic
games
that
are
math
related,
so
it
should
be
interesting.
That's
going
to
be
my
my
little
hobby
for
the
rest
of
the
year,
so
we'll
we'll
see
how
that
goes.
A
A
Okay,
any
newcomers,
oh.
E
C
A
I
am
actually
on
Jay's
team
I've
been
crashing
a
bunch
of
the
the
open
SSS
meetings
in
general,
just
to
kind
of
get
a
feel
for
things.
Oh
well.
Welcome!
Welcome
thanks,
yeah
and
there's
no
such
thing
as
crashing
you're,
you're
learning,
you're
you're,
giving
back
I'm
not
giving
yet
but
I'm.
Definitely
learning
okay,
so
ask
I'll
talk,
so
Jay
was
just
giving
an
update
on
a
video
that
he
was
watching
and
that's
what
you
heard
at
the
beginning.
B
Thanks
for
that,
this
is
going
to
be
something
that's
going
to
be
used
across
the
board
right,
so
so
it
did
so
this.
This
is
a
everything.
I've
read
suggests
that
this
is
that
this
is
the
way
all
right
from
another
from
an
automation
standpoint,
so
I'm
I'm
right
in
line
with
the
idea
behind
oscow
behind
the
different
models.
B
B
What
I'm,
having
trouble
with
is
and
I.
Imagine
that
this
video
will
make
it
clear.
It's
operationalizing
operationalizing
it
once
you've
developed
a
catalog
and
you
you
can,
you
can
prove
you
can
develop
your
playbooks
Etc.
How,
then
do
you
operationalize,
and
what
other
artifacts
that
are
generated?
What
kind
of
deliverables
are
generated
from
it
that
that
that's
usable
right
I
mean
it's
told
that
it's
a
machine
and
a
machine
readable
language?
Excellent,
so
you
so
you're
able
to
automate
a
lot
of
your
you're
able
to
automate
your
assessments
outstanding.
B
What
does
that
deliverable
actually
look
like
right
and
then
and
then,
when
consider
considering
that
you're
automating
assessments
or
you're
automating
a
lot
of
the
stuff
is
documentation
based
right?
What
does
your
actual
written
policies?
Look
like
how
you
know
some
of
this
stuff
is
on
site.
When
were
they
last
reviewed,
when
when
were
they
last
updated
who's
whose
signature
is
on
that?
Okay,
you,
you
change
your
CSO
changed
or
or
whatever
and
you're
still
the
old
cso's
name
is
still
on
these
documents.
Right,
yeah,
I,
don't
care!
B
If
it's,
if
you
they
need
to
be
updated
every
year
per
this
control
you
you
should
be
updating
on
the
next
person.
You
know
I
mean
there's
a
lot
of
stuff,
that
I
think
and
in
this
particular
instance,
not
that
this
applies
I,
guess
more
or
less
to
what
we're
what
we
would
like
to
use
it
for.
All
that
is
to
say
is
there
are
still
some
things
that
can't
be
automated.
How
do
you
account
for
that?
B
Okay,
hold
on
a
second
that
so
I'm,
not
it
might
not
so
I
might
have
put
in
an
I
where
it
should
be
and
which
should
be
an
L
hold
on
a
second.
You
know
how
these
things
go
apologize
about
them.
B
Let
me
re-post,
let
me
repost
it
different
with
the
sort
of
the
eye
here
to
see
if
that
works,
so
so
I'm
I'm
watching
this,
it's
an
hour-long
session
talk
that
was
given
in
July
as
a
reinforced
by
what
appears
to
be
one
of
the
one
of
the
creators
of
the
of
the
language.
B
You
know,
I'm
gonna
I'll
continue
to
fight
the
fight
to
fight
the
good
fight
on
it,
do
a
deeper
dive
and
what
I'm
really
looking
for
here
is
artifacts
deliverables
and
then
how
how
how
it
exactly
gets
operationalized
from
there,
so
so
that
that's
that's
where
I'm
at
with
it
now
I
encourage
everyone
to
watch.
It's
good
information
for
all
and
yeah
yeah
onward,
I
I,
I
I
will
I
will
say
that
yes,
this
is
something
that
we
need
to
that.
B
A
I
and
I
just
updated
the
length
so
that
second
link
finally
works
for
folks.
Thank
you.
It
wasn't
working
for
me
for
a
while
for
some
reason
yeah
so.
B
I
just
to
let
you
guys
know
I
what
I'm
watching
it
on
my
other
on
my
other
I
got
two
other
computers
in
front
of
me,
so
I'm
watching
on
one
of
those
I
just
typed
the
the
link
in
to
the
chat.
So
there
was
a
confusion
between
the
what's
a
capital
I
versus
a
lowercase
L
I
shrug
right.
A
A
Yeah
I
I
have
beef
with
fonts
because
of
the
letter,
I
I,
don't
like
how
there's
only
like,
maybe
one
or
two
fonts,
that
properly
write
the
capital
letter
I
and
otherwise
it
looks
like
a
lowercase
L.
So
I'll
talk
about
that
some
other
day,
but
yeah
I
have
beef
with
the
fonts
because
of
that.
B
B
Any
any
suggestions
or
comments
or
thoughts
on
this
I
don't
want
to
write
I,
don't
want
to
write
multiple
multiple
blog
posts,
I
want
to
write
one.
B
B
My
my
vision
on
this
is
is
been
the
same
since
day.
One
I
think
this
I
think
as
a
consumption
framework
with
Salsa's
production
framework.
I
think
that
both
of
these
should
ride
together
into
the
iso,
Sunset
and
I
think
they're,
not
down
and
I'm
thinking
the
iso
standard
dash
one
and
dash
two.
That
being
said,
I
want
to
do
a
blog
post
with
the
both
of
these
right.
B
B
Under
the
CDF,
that's
that's
right
now
calling
itself
the
secure
supply
chain
maturity
model,
that's
also
from
Google.
That
says
what
happens
after
the
generation
of
artifacts.
So
it
talks
about
the
artifact
life
cycle.
The
deployment
deployment
management,
release
management,
what
it
doesn't
talk
about
its
end
of
life,
I've
joined
the
CDF
and
I've
joined
this
work
stream
for
the
sole
purpose
of
saying
hey
this.
This
is
a
piece
that
neither
one
of
us
are
talking
about.
That
I
think
needs
to
be
talking
about.
B
That
needs
to
be
talked
about
and
we're
talking
about
a
complete,
secure
supply
chain
framework
and
then
add
on
to
that
the
tooling
that's
involved,
I
think
we
really
got
something
here
so
so
now,
I'll
pause
for
any
comments
on
that.
But
before
I
start
writing
a
Blog
I
just
want
to
level
sit
here
and
say:
I
I
want
to
write
one
and
I
think
we
can
write
a
powerful
one.
If
we
include
all
of
the
above
go
ahead,
go
ahead.
A
So
I
I
agree
with
you
on
on
all
fronts:
I
think
the
original
idea
pre
Samba
was
how
do
you
apply
salsa
from
a
development
standpoint,
or
what
do
you
need
to
consider
from
a
development
standpoint
to
apply
salsa
so
that
one's
a
different
discussion
than
you
know,
unifying
the
two
Frameworks
and
now,
potentially
even
a
third
to
have
like
a
comprehensive?
This
is
more
focused
on
development.
B
Yeah
no
I,
I
yeah
I,
heard
that
so
I'll
tell
you
how
I
interpreted
that,
considering
what
to
do
from
a
development
standpoint,
I
I
think
I.
Don't
think
that
so
the
way
I
interpret
it
is
you
can't
just
start
with
can't
just
start
with
salsa,
because
salsa
catches
you
at
the
build
point?
If
we
say
what
does
the
company
need
to
do
from
a
development
standpoint,
I
think
there's
a
couple
of
there's
a
couple
of
steps
that
that
need
to
be
covered.
B
So
so
there's
there's
a
few
things
that
have
would
have
had
all
already
had
to
have
occurred
that
gets
addressed
elsewhere
and
and
then
I.
Don't
think
that
you
can
success
so
and
the
reason
why
I
brought
that
third
point
is
when
you
the
only
way
I
can
the
only
way
I
can
preface
this
and
not
and
I'm
sorry.
B
This
is
the
only
way.
This
is
the
only
analogy
I
can
give
for
this,
and
you
guys
may
or
may
not
get
it
but
I'm
in
the
bodybuilding
Community
right
so
I
so
I'm,
a
coach,
I,
coach
athletes
who
compete
on
stage
and
all
that
stuff
like
that
and
some
of
my
athletes
they
like
using
supplements
okay
before
they
use
supplements
before
they
use
any
supplement,
I
always
say
to
them.
Do
you
have
a
proper?
B
What's
what's
called
a
a
PCT,
a
post
cycle,
post,
Cycle
Therapy
right
so
before
you
use
any
substance
like
any
testosterone,
booster
or
anything
like
that?
Do
you
have
something
to
regulate
your
hormones
after
you're
done
with
that
eight
week
cycle
right?
B
The
reason
why
I
talked
about
that
third
piece
and
the
reason
why
we're
talking
about
the
development
angle
to
it?
What
do
you?
What
do
you
need
to
have
in
place
from
a
development
standpoint
in
order
to
properly
use
salsa,
I,
say
well,
since
salsa
sits
in
the
middle
there's
got
to
be
stuff.
B
That
has
that
that
would
have
to
have
been
done
in
the
beginning,
but
you
also
have
to
make
sure
you
have
a
piece
at
the
end
to
Archive,
maintain
and
and
and
so
archive
maintain,
share
or
or
use
or
whatever
it
is
the
artifacts
that
are
generating
right.
So
so,
when
I
consider
the
development
standpoint,
what
do
you
need
to
have
in
development,
I
I?
Think
all
of
these
pieces
should
be.
B
You
know
readily
understood
before
during
and
after
now,
I
that?
That's
that
that
was
when
I
interpreted.
That's
how
I
interpreted
it
unless
there's
a
there's
a
I'm
there's
some
going
too
far
right,
I'm
thinking
too
far
and
I'm.
Just
I
should
just
keep
my
scope
relative
to
to
to
salsa,
and
then
I
can
do
that
too.
B
But
I'm
thinking
about
what
will
be
more
of
a
of
a
more
of
a
robust
blog
or
a
better,
a
better
story
to
tell
around
around
salsa
and
it's
an
actual
impact
to
an
organization
and
how
all
those
other
pieces
can
work
together.
C
Yeah
I
guess
Jay.
Would
you
mind
explaining
a
little
bit
more
of
what
you
mean
by
end
of
life
cycle
like
essentially
what
this
third
piece
like
with
that
new
framework
actually
does,
because
this
is
the
first
time
I'm
hearing
of
it.
So,
oh.
B
Yeah
yeah,
so
you
somebody
somebody
asked
to
buy
the
link
too
and
let
me
let
me
see
if
I
can't
pop
up
one
here
yeah,
so
so
I
I,
originally
when
I,
when
it
first
came
across
me
I
said:
are
they
trying
to
pull
a
fast
one?
That's
what
I!
Originally
that's
why
I
originally
said
and
of
course
I
said
well,
no,
let
me
not
jump
to
conclusions.
B
Let
me
go
ahead
and
jump
on
to
their
to
the
GitHub
site
to
the
to
all
the
sites.
Let
me
read
up
and
what
I
found
was
very
interesting,
trying
to
find
it
here
so
I'm
trying
to
find
it
as
I'm
as
I'm.
Talking
to
you,
yeah.
B
B
I
got
so
many
links
up
here.
It's
not
even
funny.
This
is
this.
Is
this
this
isn't
it
I
got
I
got
so
many
links
up
here.
A
A
For
that
J,
so
just
a
quick,
I
guess
comment
and
again
you
can
feel
free
to
agree
disagree
right.
This
is
the
salsa
positioning
right
and
so,
when
I
think
social
positioning
I'm
just
focused
so
Focus
slowly
on
salsa.
Now
that
begs
the
question
now
that
we
have
the
Microsoft
right
framework
being
adopted
into
Sig
I.
Remember
last
time
in
last
week's
meeting
they
were
like
well,
maybe
we
should
bring
up
the
positioning
Sig
to
handle.
A
You
know
multiple
right
but
I
think
for
now
we
have
to
focus
on
salsa
and
only
salsa,
because
that's
what
we've
that's
the
charter,
that's
what
we
know
and
then
we
can
always
expand
on
it,
but
again
that
that's
just
my
point
of
view
based
off
what
we've
why
this
positioning
Sig
came
to
be
about.
B
B
I'm
fully
in
the
greens,
I
think
they
should
be
separate,
but
when
we
go
ahead
with
a
with
a
blog
post,
I'm
thinking
about
mentions
ultimately,
ultimately
I
I,
ultimately
I,
don't
what
so
I.
What
I
don't
want
to
have
happen
is
for.
A
I
would
agree
right
and
yeah
I
I
would
totally
agree
with
that
and
I
think.
Maybe
how
we
go
about
it.
It
could
be
an
offline
conversation
when
we're
writing
it.
Mentioning
of
other
Frameworks
I.
Think
that's
fine,
I
think
it's
more
of
the
the
focus
would
be
salsa
and
we
could
mention
the
other
ones,
but
we
could
leave
it
out
of
scope
or
we
could
say
it's
for
another
blog
post
right.
Instead.
B
Of
one,
yes,
absolutely,
my
general
thought
process
was
in
terms
of
development.
You
need
to
have
this
piece
in
place
that
piece
in
place.
So
in
order
for
us
to
do
this
this
this
this
this
and
this
or
respect
this
also
so-
and
we
could
say
those
other
pieces
are
out
of
scope
for
this
discussion,
but
we
have
but
you,
but
you
have
to
make
sure
you're
covering
down
on
this
end
in
the
beginning,
and
this
part
that
comes
at
the
end,
to
focus
on
this
right
here.
B
This
long
piece
right
here
in
the
middle
that
allows
us
to
be
able
to
flush
that
out
those
other
pieces
out
and
later
blog
posts,
which
would
not
be
double
work.
Yes,.
B
That
would
just
be
that
would
just
be
added
on
conversation
as,
as
time
goes
on.
B
A
E
E
Excuse
me
in
the
planning
phase
is
still
on
that
one
and
starting
to
to
do
a
very
basic
outline,
but
but
my
thought
with
it
is,
is
essentially
taking
you
know,
essentially
taking
that
whole
build
process
taking
all
the
all
of
the
salsa
components
and
then
kind
of
mapping
them
to
it
and
explaining
you
know
kind
of
kind
of
the
importance
of
of
salsa
throughout
the
build
process
and
explain
what
kind
of
the
the
importance
of
each
component.
E
Why
they're
all
there
and
really
just
kind
of
kind
of
tough
to
handling
off
of
that
piece?
So
that's
that's
my
initial
thinking,
I'm
definitely
gonna
need
some
help.
I
know
Jay
already
suggested
that
I
reach
out
to
him
so
I'll
be
doing
that
once
I
get
kind
of
an
initial
outline
put
together,
but
definitely
willing
to
to
have
anybody
else
jump
on
who
who
who
wants
to
stay
hard
in
it.
E
I've
really
just
started:
I
haven't
done
anything
so
far.
Okay,.
A
A
A
Let
me
look
I'm
looking
at
the
extra
to
Do's.
I
did
push
APR
this
morning
or
yeah
earlier
today
for
the
charter,
as
well
as
updates
to
some
of
the
governance
documents
around
the
Sig.
It
seemed
to
be
missing
from
various
places,
so
I
did
that
update.
So
if
you
want
to
view
that
I'm
trying
to
find
here
we
go,
this
is
the
pr
feel
free
to
comment
or,
if
you
see
anything,
that's
missing,
feel
free
to
add
it
submitted.
A
Oh,
oh,
okay,
and
so
now
that
you
found
that
link.
Did
you
want
to
answer
Marcella's
question
I?
Think.
C
It's
totally
fine
look.
My
question
was
just
if
you
had
more
details
on
what
this
scmm
framework
is
supposed
to
do,
simply
because
also
the
like
GitHub
doesn't
seem
to
have
a
whole
lot
of
extra
information,
although
we
do
understand
now.
Why
like?
Why
you're
saying
that
it's
that
the
salsa
sort
of
falls
in
the
middle,
because
yeah
this
is
salsa,
as
you
said,
is
about
build
now
that
we
have
the
artifact.
What
else
do
we
do
with
it
in
the
life
cycle?
A
B
And
so
I
have
there
was
a
meeting
that
was
supposed
to
happen
today.
I
was
ready
for,
but
but
it
got
moved
to
the
18th.
B
So
once
I
jump
into
that
meeting
on
the
18th
I'll
be
able
to
ask
more
questions
and
I'll
know
more.
But
what
what
we're
all
looking
at
right
here
is
what
I
got
and
then
of
course,
reading
a
lot
of
the
entries
on
the
slack
a
lot
of
the
slack
stuff
and
the
conversation
is
there,
you
know
I
was
able
to
get
on
their
slack
and
read
so
so
I
have
that.
B
But
this
right
here
is
there
is
a
GitHub
site
and-
and
that's
where
that
guy
here,
but
just
reading
it
and
understanding
where
all
of
these
different
Frameworks
sit
in
in
the
grand
Spectrum
I
can
clearly
see
a
you
know
the
the
lineage
or
the
or
the
the
line
you
know
the
bridging
on
all
of
them.
I
can
clearly
see
it
and
and
I
think
and
I
think
there's
there's
a
meat
here
for
us
to
chew.
On
my
ultimate
objective
and
I
always
say
this
is
ISO
specification.
B
I
think
we
can
do
it
and
I
think
this
is
not
a
piece
towards
that.
C
Yeah,
essentially,
it
looks
like
this
new
framework
would
be
a
consumer
of
salsa
at
the
stations
right.
If
we
were
thinking
about
the
sort
of
yeah
metadata
coming
out
of
a
salsa
aware,
build
yeah,
the
scmm
would
take
that
and
maybe
validate
or
not
but
yeah
cool.
Thank
you.
Yeah.
A
Okay
through
the
Google
group
s,
the
Google
or
the
groups.io
migration
Kim
from
the
steering
committee
said
that
she
was
going
to
reach
out
to
the
attack
to
see,
if
that's
true,
if
we
have
to
migrate
off
of
Google
Groups.
A
Obviously
Mike
in
the
last
meeting
said
he
doesn't
believe.
That's
true,
but
Kim
said
that
she
was
going
to
go
figure
out.
If
that
truly
is
a
requirement
or
not
so
we're
going
to
put
that
on
hold
for
now
and
I'm
looking
through
and
Jay
there's
another
one
I'm.
Looking
at
the
highlights
from
previous
meetings,
it
says
Jay
maybe
bring
in
Adrian
to
help
clarify
some
questions.
A
Deep
dive
on
the
I
think
on
the
the
new
framework,
so
I'm
not
sure
if
that's
still
going
to
happen
or
if
it's
going
to
happen
now
that
you're
part
of
the
supply
chain
Integrity
working
group,
maybe
if
that's
more
of
a
an
item
for
a
different
meeting.
B
Oh
no,
as
a
matter
of
fact,
I
I,
I,
I
I
believe
that
we
should
have
a
joint
meeting.
I
believe
this
should
be
a
joint
session
happening,
okay
and
and
not
and
Adrian's.
Actually
he
would
have.
He
would
have
been
here
today,
but
he's
actually
traveling
right
now,
so
that
my
plan
was
to
bring
him
to
this
meeting
today,
but
he's
actually
traveling.
So.
B
Okay,
yeah
there
that
is,
but
but
I
what
my,
what
there's
a
vision
here.
My
vision
is
is
for
us
to
have
our
our
individual
sessions
where
we
we're
both
building
and
we're
doing
things.
You
know
we're
we're
keeping
them
separate,
but
but
making
sure
that
we're
considering
one
another
and
then
a
joint
one
where
we
actually
build
those
bridges
right.
B
That's
the
that's,
the
the
the
the
the
long
tail
Vision,
but
yeah
he's.
He
would
have
been
here
today,
because
I
know
that
there
were
questions
and
I
and
I
wanted
him
to
come,
but
he's
traveling.
So
so
I
have
to
wait
for
our
next
meeting.
A
Okay
and
don't
worry,
I,
don't
see
anything
else
on
the
highlights
that
were
still
outstanding,
so
any
topics
questions
that
people
want
to
bring
up.
Otherwise,
we'll
repurposed
for
working
session.
A
Okay,
so
my
thinking
is
to
try
and
feel
free.
If
others
want
to
disagree
or
agree
I'm
thinking,
we
should
try
to
focus
on
the
blogs,
because
I
think
the
one
of
the
first
blogs
we
were
trying
to
Target
middle
of
this
month
and
it
has
not
happened
so
if
we
get
any
blog
out
by
this
month,
that
would
be
fantastic.
A
B
A
It
doesn't
look
like
I
can
do
that
here,
so
I'll
leave
it
up
to
the
the
folks
on
the
call.
What
would
you
like
to
do
with
the
remaining
time.
A
So
the
next
question
is:
how
do
we
want
to
do
this
because
there's
two
blogs
to
be
worked
on,
which
do
we
want
to
work
on
both
at
the
same
time,
just
in
different
in
different
docs?
Or
do
we
just
want
to
focus
on
one.
E
A
Okay,
so
development
one
it
is
Jay.
Do
you
have
a
place
for
that,
yet
that
you're
working
from
or
no.
B
B
A
B
A
Okay,
and
if
you
see
Anonymous-
oh
I,
don't
like
that
name,
it
says:
Anonymous
shrew,
that's
not
nice,
I,
I've
forgotten
my
password
to
my
Google
and
so
I
need
to
I
need
to
reset
it
and
I
haven't
had
a
chance
third
party.
A
So
feel,
free
folks
to
to
start
typing
and
suggesting
things
from
a
development
standpoint
right.
A
You
know
the
the
code
right,
whether
it's
proprietary
or
third
party,
and
given
that
we're
open
source
I,
would
think
that
we
would
want
to
talk
about
that
in
some
capacity,
because
there
are
specific
salsa
levels
currently
right
around
the
source.
I
know
we're
trying
to
postpone
it
for
1.0,
but
let
me
see
what
version
0.1.
A
C
So
actually,
this
sort
of
came
up
on
one
of
the
many
GitHub
issues
that
are
currently
open
around
the
specification,
and
there
are
some
requirements
that
do
have
a
developer
component,
even
though
they
are
related
to
build,
which
is
related
to
the
like
configuration
of
the
build.
So
if
you're
I
can
have
like
a
config
file
for
your
Builder,
which
happens
even
with
GitHub
actions
right
where
you
have
this
like
yaml
file,
for
example,
that
actually
is
still
something
that
the
project
owner
oops
Street
handle
right.
C
So,
at
least
from
the
specification
standpoint
we've
started
to
think
about.
You
know
who
is
responsible
for
meeting
certain
requirements.
A
A
C
Yeah
I
think
you're
right
that
it's
around
three,
but
if
you
look
at
the
current
hermetic
requirement,
for
example,
still
says
a
user
to
find
to
build
scripts
needs
to
a
due
part
of
the
Hermetic
needs
to
sort
of
set
up
the
dependencies,
and
then
the
build
service
also
has
some
responsibility
to
complete
the
sort
of
hermetic
requirement,
but
we're
actually
trying
to
split
this
apart.
This
requirement
apart.
So
it's
possible
that
yeah
after
level
three
everything
is
fully
automated.
C
A
A
This
is
where
it
gets
murky,
so
so
Jeff,
what's
your
thoughts
on
because
there's
the
build
blog
coming
up
right,
but
this
is
a
developer
blog.
So
at
what
point
do
we
say?
Okay?
Well,
a
developer
could
do
this,
or
do
we
just
focus
on
just
pure
development,
not
necessarily
having
anything
to
do
with
building
that
software.
E
Yeah,
that's
I
mean,
and-
and
this
is
this
can
be
totally
fluid.
Because
again,
my
my
idea
was
really
just
kind
of
initial
thinking.
E
A
D
Mama,
just
just
a
step
back
to
clarification,
the
intention
of
this
blog
is
to
teach
developers
the
benefits
or
how
to
use
or
how
to
deploy
a
salsa.
What
what
is
the
the
the
the
reintention?
So
we
can
try
to
tune
what
should
be
included
in
the
blog.
A
That's
a
good
question,
I
think.
Originally
it
was
just
derived
from
a
picture
and
J,
not
J.
Sorry,
Jeff
I,
don't
remember
the
intention
I
just
remember
it
being
derived
from
that
life
cycle
picture
and
that
we
wanted
to
write.
You
know
a
portion
about
the
development
piece
with
regards
to
salsa,
but
I.
Don't
remember
the
details.
E
E
Melba
I
was
looking
at
it
saying
you
know
if
we
could
show
how
and
where
and
why
salsa
plugs
into
these
at
each
of
these
areas
of
the
sdlc,
that
that
would
that
that
might
actually
really
be
helpful
to
show
kind
of
kind
of
where
it
belongs
and
and
how.
E
That's
yeah,
that's
a
great
question.
I
think
what
I
initially
saw
in
my
mind's
eye
was
a
little
more
like
a
medium
level
view.
Maybe
you
know
maybe,
like
the
5000
foot
view,
definitely
wasn't
like
30
000
foot
view
we're
not
We're,
not
gonna,
give
up
a
broad
overview
of
salsa,
but
it
would
really
get
into
what
you
would
be
doing.
Where
and
and
not
I
don't
know
I.
E
D
Yeah,
my
concern
is
that
you,
of
course
a
Blog:
it's
not
intended
to
be
a
very
long
tax
right.
So
it's
good.
If
you
can
answer
one
question
in
the
blog
like,
for
example,
why,
for
example,
if
you
focus
on
development,
why
should
you
consider
consider
salsa?
So
that's
the
only
thing
that
we
would
like
to
describe
and
they
came
out
with
okay,
I
I
buy
him
I
know
why
it
shouldn't.
You
know,
use
this
also.
D
B
B
That's
a
different,
that's
a
different
blog
than
than
what
we're
talking
about
here,
though
right
I
mean
what
I
mean
I
think
I
think
what
we're
talking
about
here
is
included
in
that
from
up
from
from
a
high
level,
but
I
think
I.
B
Not
disagreeing
I'm,
just
saying
like
we're
we're
talking
about
from
a
developer
from
a
developer
or
development
standpoint
which
covers
that
which
covers
a
you
know,
one
piece
of
salsa,
but
not
you
know
if
we're
talking
about
what
it
is,
what
it
isn't
Etc,
we
can
do
that
from
a
developer
standpoint
right
when
you
talk
about
whether
or
not
you
can
verify
that
the
build
was
done
using
using
packages.
You
know,
if
you're
rejecting
a
package
if
it
wasn't
built
using
a
source
repo
or
something
like
that
or
you
can.
B
You
know,
I
mean
like
we
I
mean
like
you,
you
can.
We
could
talk
about
those
things
and
then
that's
I
think
that
but
I
think
even
that's
that's
more
in
the
weeks
than
we
want
to
be.
If
we're
considering
what
it
is
or
whether
it
isn't,
then
we
come
up,
maybe
a
level
and
and
say
it
you
know,
could
be
used
to
understand.
B
What
the
requirements
are
for
for
for
package
registry
or
or
you
know,
like
I'm,
throwing
jaw
to
the
dartboard
with
that
one,
but
but
based
on
that
that
5
000
foot
maybe
sounds,
maybe
sounds
right,
maybe
maybe
maybe
somewhere
in
the
middle.
Maybe
that's
seven.
B
Seventy
five
hundred
foot
view
when
we
talk
about
what
it
is,
what
what
it
is
in
the
what
what
it
doesn't
cover
because
it
because
then,
because
then
I'll
go
back
to
my
original
we're
talking
about
it,
doesn't
cover
what
happens
from
in
ingestion
to
build
and
it
doesn't
happen
what
happens?
It
doesn't
cover
what
happens
after
artifacts
are
created
and
and
to
end
of
life
yeah
right.
So
so
now.
So
now
we're
back
to
if
going
by
what
Bruno
said.
B
If
we
do
that,
then
those
other
parts
now
become
even
more
relevant
to
include
in
the
in
the
blog
but
but
but
but
like
Melba
said
before
that
doesn't
cover
just
straight
on
salsa.
You
know
the
positioning
of
salsa
for
the
for
the
developer
right.
A
I,
like
the
question
approach
and
I'm
wondering
if
we
should
answer
all
of
those
in
one
blog
I
know
someone
mentioned
you
know.
Typically,
the
blogs
are
short,
but
if
we
can
say
okay,
this
is
not
covered
by
salsa,
but
you
know
we
may
put
you
know
or
release
other
blogs
with
regards
to
XYZ
right
and
we
can
mention
the
other
Frameworks,
and
then
we
can
go
into
like
how
right
so
I
feel
like
we
could
answer
all
three
like
you
know.
A
Why
should
they
care
that's
not
covered
and
then
how
they
can
go
about
it,
I
I'm,
not
sure
if
that's
too
long
of
a
Blog
but
I
feel
like
that
would
be
a
more
comprehensive
blog
that
maybe
developers
would
would
rather
read
versus
just
a
lot
just
answering
one
of
those
questions.
If
that
makes
any
sense.
D
I
think
that,
to
how
you'll
be
a
very
long
blog
but,
for
example,
one
thing
that
maybe
can
be
useful
with
so
what
it's
not
covering
the
social
levels
but
try
to
be
more
I
mean
educational
like,
for
example,
what
a
kind
of
problems
that
you
can
catch
with
the
salsa
level
one
and
well,
if
level
two
you
can
catch
those
problem.
You
can
solve
this
problem
three
and
four.
D
What
is
outside
the
debt
boundary,
for
example,
just
to
see
how
how
it
looks
like
if
I'm
going
to
implement
salsa,
but
not
how
yet.
But
it's
just
getting.
D
Or
otherwise,
I'm
going
to
have
well
some
doses
of
pages
easily.
Here.
B
Especially
if
you
expand
the
what
the
the
what
like
that
the,
how
would
be
oh,
how
would
be
all
you
could?
Almost
that's
almost
a
book.
That's.
D
C
A
C
A
B
I
think
we
could
I
think
we
could
even
include
that
I
think
that
might
even
be
a
like
a
like
a
this
phone
is
going
off
today.
I
think
that
might
even
be
a
a
short
you
know
down
at
the
bottom
of
the
blog.
What
no?
What
could
developer
do
today
and
then
give
a
couple
of
lines,
and
then
say
you
know
a
a
longer
version
of
this
will
be
covered
in
part
two
or
something
like
that
call
to
action.
Okay,.
C
And
I
think
one
important
question
to
answer
because
I'm
thinking
about
I
don't
know
if
you
heard
how
Pipi
tried
to
Institute
like
two-factor
authentication
for
top
projects
and
there's
actually
a
fair
amount
of
backlash
from
some
developers,
because
they
felt
it
was
an
undue
burden
on
their
like
development
life
cycle
to
start
using
Hardware
keys
for
tooth
Factor,
so
trying
to
yeah
I
think
really
motivate
developers,
especially
if
they,
if
this
isn't
their
full-time
job.
Why
salsa
matters
I
think
will
be
really
important.
A
Okay,
I
think
I
added
that
at
the
top
and
I
know
it
looks
like
a
bunch
of
different
edits,
because
I'm
not
signed
in
I
do
have
the
hard
stop
it
in
two
minutes,
so
just
kind
of
giving
people
a
heads
up
if
I
drop
all
of
a
sudden.
A
Okay,
so
I
think
now
that
we
have
a
place
where
this
outline
lives,
we
can
add
to
it
ad
hoc,
so
I'm,
guessing
by
next
week.
Next
Tuesday.
Maybe
we
can
have
a
little
bit
more
words
around
some
of
this
stuff.
B
Absolutely
this
is,
this
is
good.
This
is
a
this
is.
This
is
a
great
meat
for
me
to
chew,
on
I
mean
and
of
course,
yeah
do
a
session
like
this
I
mean
this
is
not
the
the
original
and
I
want
to
say
it's,
not
the
original
intent,
but
this
is
definitely
the
direction
that
that
we
that
we,
that
we
should
be
heading
with
this
yeah
yeah.
A
Well,
I'm
hoping
everybody
agrees
with
another
great
meeting
and
very
productive.