►
Description
Meeting minutes: https://docs.google.com/document/d/1Lt8uGpiMFfgws8VF36xtTMaJAeHufha-7Dqz1tjrPGY/edit#heading=h.naeeah7jeanr
A
A
A
The
categories
have
been
defined,
it
is
available
and
open
for
for
input
site.
There's
only
been
a
couple
things
added
since
then,
but
everyone
has
information
they'd
like
to
start
adding
to
that
spreadsheet.
Please
feel
free
to
go
ahead
and
do
so
any
changes
to
that
spreadsheet.
Any
requests
or
suggestions
for
adjustments
for
changes.
A
Please
open
up
an
issue
in
in
the
city
repo,
so
we
can
discuss
any
of
those
changes
and
determine
if
you
want
to
do
it
any
changes
we
make
you're
going
to
have
a
ripple
effect,
because
this
spreadsheet
is
a
source
of
information
for
all
three
of
the
section
groups.
So
I
want
to
try
and
be
judicious
as
we
make
any
adjustments
or
changes
moving
forward.
A
All
right,
a
couple
takeaways
from
the
recent,
the
spreadsheet
working
meeting
and
the
work
group
call
we're
going
to
adjust
our
goal.
1.2
to
say
that
we're
going
to
centralize
materials
on
SKF
I
need
to
get
a
link
to
the
appropriate
goal
with
Glenn
and
I'll.
Take
care
of
that
offline.
We're
leaving
the
budget
items
for
the
tooling
and
librarian
role
in
there.
A
But
we
want
to
align
with
what
the
section
2
group
is
doing
and
again
centralizing
things
around
SKF
does
not
mean
that
SKF
is
the
sole
platform
we
need
to
determine
if
additional
resources
are
needed
and
and
how
to
address
those.
But
that's
what
we're
going
to
start
with.
That's
a
good
place
to
to
begin
this,
because
they've
already
got
some
maturity
on
there
and
they've
already
got
a
lot
of
content
from
a
lab
perspective
on
their
random.
B
Well,
there
was
basically
so
SKF
originally
wasn't
like
a
education
platform.
Originally
it
was
like
a
requirements
platform
and
there
are
some
people
that
actually
use
those
those
tools
in
Europe
quite
extensively
and
had
pledged
to
donate
money
and
and
set
up
a
quote-unquote
SKF
foundation
in
Belgium.
So,
basically
like
we're
kind
of
splitting
things
up
and
we're
splitting
up
like
the
education
and
like
the
knowledge
and
all
in
the
labs
and
all
of
that
into
its
own
thing
that
we're
calling
skg
but
that's
kind
of
something,
that's
being
organized.
A
B
A
A
B
Really
hard,
that's
kind
of
the
problem
for
me,
because
I
I
am
supposed
to
be
the
architect
of
SKF,
and
it's
really
hard
for
me
to
like
confirm
budgets
and
be
like
this
is
how
it's
going
to
work,
because,
like
before
I,
was
working
on
trying
to
establish
a
workflow
between
SKF
and
openssf.
But
it
was
really
hard
for
me
to
work
with
that
flask
system
that
we
currently
have.
So
this
actually
really
helps
things
and.
B
Things
so
it
actually
helps
me,
do
my
job
a
whole
lot
better.
So
I
actually
think
that
this
is
going
to
help
me
get
those
workflows
together.
So
I
can
give
you
guys
workflows
on
how
the
information
is
structured
on
SKF
and
what
I
would
need
in
order
for
me
in
the
SKF
team
to
basically
like
take
content
and
archive
it
and
add
it
to
the
graph
in
SKF
and
add
it
to
all
of
the
information
there.
D
A
D
A
For
the
content
pieces
of
it,
it's
it's
basically
open
for
anybody
to
add
information
to
it.
We're
asking
people
put
their
names
next
to
what
they
they
add
in
there.
So
we
have
someone
to
go
talk
with
if
we
have
any
questions
or
concerns
about.
You
know
what
what
the
information
has
been
entered,
where
we
are
more
concerned
about
any
change
to
the
spreadsheets
along
the
lines
of
the
categories
that
we're
using
to
organize
the
information.
So
training
can
be
freely
added
and
it
will.
A
A
D
A
B
So
this
kind
of
becomes
an
issue
when
you
start
dealing
with
things
like
David
Wheeler's
course,
which
is
currently
what
we're
on
like
how
we're
going
to
break
that
down,
because
if
we
can
break
it
down
to
Core,
Concepts
it'd
be
easier
to
link
other
things
to
that
and
make
it
all
work
as
one
so
I
think.
That's
where
the
librarian
would
actually
be
very
very
handy
would
be
to
help
with
that
breaking
down
of
content,
because
I
don't
think
that's
necessarily
about
being
Optimum.
It's
also
about
being
consistent.
A
B
A
All
right,
I'm
gonna
go
ahead
and
move
on.
The
second
point
for
the
takeaway
is:
do
we
need
to
add
a
section
one
goal
around
creating
a
curriculum
framework?
This
is
a
more
open
question,
not
specific
to
Gathering
the
content
or
organizing
the
content.
This
is
more
along
the
lines
of
once
we
have
the
content
in
place.
How
do
we
build
that
information
into
some
sort
of
curriculum
and
I?
Don't
think
we
have
that
distinctly
called
out
under
any
of
the
goals
that
we
have
at
the
moment.
Any
thoughts
on.
B
A
All
right
and
then
the
third
takeaway
was
around
writing
a
primer
for
how
to
use
the
categories
on
the
spreadsheet.
So
this
is
more
of
a
little
bit
of
context
around
the
different
types
of
categories
we
have
there,
the
domains,
the
personas
ETC,
so
people
can
translate
what
Our
intention
is
without
trying
to
figure
that
out
themselves
based
on
the
name
or
the
words
that
we
used
I
know
Sal
had
expressed
some
interest
and
started
to
work
on
this.
A
D
A
Thank
you
very
much
if
I
could
ask
Randall
and
Eric
if
you
could
touch
base
with
Sal,
whether
it's
on
slack
or
over
email,
I,
don't
know
if
she's
had
an
opportunity
to
make
any
progress
on
this,
but
get
the
three
she
mentioned,
she'd
be
interested
in
in
working
on
it,
but
I.
Don't
necessarily
think
that
translates
into
she
has
time
to
work
on
it,
but
I,
don't
wanna
I,
just
don't
want
to
duplicate
any
effort.
A
A
A
A
I
think
that
goal
1.1
we've
been
through
this
number
of
times.
Well,
I,
don't
think
it's
necessarily
perfect
I
think
it's
pretty
good.
So
if
anyone
has
any
suggestions
to
any
of
these
goals,
my
intent
is
after
I
get
back
from
from
my
conference,
probably
not
going
to
be
until
Sunday
on
Monday
or
Tuesday
I'll
go
in
and
I'll
make
any
updates.
We
talk
about
this
meetings,
but
please
put
pull
requests
in
on
the
on
the
repo
for
any
suggestions
you
have
for
any
changes
to
this
part
of
the
plan.
A
So
that
way,
people
have
a
chance
to
look
at
them
and
consider
them
before
we
talk
about
it
again,
but
anything
that
we
do
in
this
meeting
today.
I'll
take
care
of
making
those
updates
prior
to
the
Education
meeting
next
Wednesday
goal,
1.2
I
I
changed
the
wording
around
the
second
milestone
there
around
centralizing
materials
on
SKF
I
need
to
link
it
to
the
appropriate
goal.
A
In
that
section,
Randall
based
on
the
earlier
conversation
I,
will
await
the
chat
between
you
and
me
and
Crow
and
Glenn
about
what's
what's
happening
there.
We
can.
We
can
add
that
verbage
in
there
to
make
this
clear.
The
third
Milestone
on
here
is
talking
about
services
and
tooling
needs.
We
need
to
come
up
with.
So
if
you
look
under
the
budget,
you'll
see
that
we
have
the
librarian
role
and
we
also
have
an
estimated
100K
U.S
for
for
tooling
Services
hosting
costs.
That's
a
very
ambiguous
line
item
and
we're.
B
A
A
Again,
this
is
not
our
final
answer,
but
this
is
the
kind
of
thing
we
need
to
think
about.
How
do
we
accomplish
the
goal
and
what
steps
we
need
to
take
to
get
to
that
goal?
I
know
a
lot
of
this
is
still
going
to
be
fuzzy.
Even
after
you
put
the
plan
together,
we
need
to
try
and
at
least
put
together
some
ideas
on
how
to
achieve
these
things.
D
A
That
and
again
prior
to
next
Wednesday's
Sig
meeting,
if
you
have
any
ideas
or
thoughts,
please
go
ahead
and
add
them
to
a
pull
request
to
the
to
the
plan
itself:
1.3,
1.4
and
1.5.
We
have
not
talked
about
a
great
deal.
These
are
very,
very
thin.
We
need
to
make
these
much
much
more
robust,
so
goal
1.3
is
determined
venues
and
personas
that
content
will
be
created
for
or
delivered
to.
A
So
this
is
somewhat
of
a
dependency
for
section
two
since
they're
the
ones
that
are
going
to
be
looking
at
creating
content.
We
need
to
let
them
know
what
kind
of
content
We
Believe
needs
to
be
created.
Based
on
the
information
that
we
have
so
I
think
the
dependencies
on
this.
Not
only
do
we
need
to
have
the
materials
Matrix,
but
I
think
the
survey
we
talked
about
doing
to
look
for
gaps
should
probably
be
finished,
or
at
least
in
in
progress.
Would
would
you
all
agree
with
that
survey?
Is.
A
I
would
say:
yeah
I,
understand
what
you
mean.
The
personas
I
believe
is
something
that
that
would
be
our
responsibility
to
identify
and
curate
again,
there's
gonna
be
overlap,
I
think
amongst
all
three
of
the
sections
on
some
of
these
things
and
we're
trying
to
make
sure
that
no
one
section
is
just
getting
all
the
work,
we're
trying
to
spread
it
out
as
best
we
can
so
I
think
the
personas
is
definitely
within
our
realm,
a
responsibility
to
to
identify
and
curate
again
with
the
input
from
the
other
sections
as
necessary.
A
A
I
think
it
would
be
helpful
since
section
two
is
going
to
be
focused
on
creating
content,
primarily
there's
other
things,
but
that's
their
primary
focus
in
section
three
is
going
to
be
focused
on
incentivizing
and
engaging
the
communities
I
think
it's
probably
an
area
that
we
can
help
with
to
put
together
a
list
of
places
or
types
of
events
or
venues,
or
you
know,
platforms
online
to
to
help
deliver
the
content.
I,
don't
think
it's
necessarily
solely
our
decision,
but
I
think
by
us.
B
I
I
have
a
comment
for
when
we
have
our
re
or
regroup
session
that
yeah
about,
because
I
think
curating
is
also
already
something
that
SKF
already
does
and
something
Glenn
takes
very
seriously
so
I
just
wanna
when
we
actually
have
our
conversation
about
that.
I.
Just
think
that
that's
something
that
we
should
definitely
iron
out
and
figure
out.
A
A
All
right
so
I'm
going
to
leave
this
on
here
again.
If
anyone
has
suggestions
on
how
to
change
this
or
adjust
it
or
add
stuff
or
whatever
I
invite
you
to
put
some
pull
requests
in
and
suggestions,
we
can
talk
about
and
discuss
amongst
us
amongst
us,
and,
let
me
see
I'll
say
it
on
here,
formerly
documented
personas
I
think
this
might
be
done,
I
think
between
mostly
the
personas
that
we
have
in
the
spreadsheets
and
putting
some
context
around
them.
C
A
And
yeah,
and
and
if,
if
we're
all
good
with
that,
then
I
absolutely
say
we
should
cross
it
off
for
now
and
maybe
maybe
change
that
to
a
you
know:
revisit
the
personas
on
some
kind
of
regular
basis.
We're
gonna
need
to
keep
this
stuff.
You
know
updated,
so
we
need
to
put
a
a
Cadence
in
the
place
to
review
all
the
all
these
categorizations
personas
and
such
to
make
sure
that
they're
still
relevant
and
need
to
be
changed.
So
thank
you,
Christine
for
that.
A
All
right
so
again
as
above
suggestions,
thoughts
on
1.3,
please
feel
free
provide
feedback.
You
probably
feedback
in
this
document,
suggestions
and
PRS
moving
down
to
1.4.
This
is
defining
training,
areas
of
focus
and
I.
I
think
that
this
is
I'll
see
how
we
have
this
defined.
Thus
far,
this
really
isn't
a
milestone.
This
is
more
of
a.
How
are
we
going
to
do
this,
so
we
need
to
put
some
milestones
in
here,
but
the
general
approach
that
we
talked
about
taking
was
focusing
not
just
on
development
skills
techniques
associated
skills.
A
Modern
developers
have
access
control,
testing
validation.
You
guys
need
to
read
this
to
you,
but
basically
it's
looking
at
looking
at
this
from
a
couple,
different
perspectives
and
determining
how
to
focus
some
of
these
areas
to
reach
the
target
audiences
that
the
personas
that
we're
talking
about.
A
A
Okay
so
for
homework
this
week
between
now
and
Wednesday's,
meeting
I
am
going
to
ask
and
I'll
send
an
email
out
to
the
to
the
group.
You
know
please
review
this,
the
stuff
in
the
plan.
Please
provide
feedback,
comments
and
session
drop
in
this
document.
Here
any
changes
and
like
I,
said
put
in
the
pr
we're
gonna
need
to
do
some
work.
Ac
work
offline
to
get
this
information
into
shape,
so
so
we're
ready
by
the
end
of
the
month,
Randall
first
and
then
Christine.
B
The
diagram
will
have
guidance
on
this
because
the
nodes
will
be
identified.
The
types
of
nodes
will
be
identified,
so
we
have
most
of
the
educational
material
right
now
is
identified
as
Concepts,
so
we
could
use
those
as
like
pillars.
I
mean,
as
I
said.
The
diagram
should
have
some
focus
on
this
next
week.
Just
okay,
throwing.
C
A
I,
don't
think
this
is
necessarily
prerequisites.
I
think
this
is.
How
are
we
going
to
attack
the
problem?
You
know
Beyond
beyond
the
types
of
educational
materials
that
we
were
looking
at.
How
is
how
are
we
going
to
get
information
into
the
developers
hands
that
they
need,
and
it's
not
just
coding
information?
It's
information
that
hover
all
aspects
of
their
responsibilities.
It's
compilers
its
supply
chain,
testing,
that
sort
of
thing
and
yeah
we
mentioned
devops
snares
in
here,
open
source.
You
know
web
API,
I
think
this
is
really
you
know.
E
I
think
it's
beyond
that.
It's
it's
also
setting
up
an
actual.
You
know
not
just
the
how
but
actually
setting
up
the
phased
approach
to
what
mediums
are
going
to
be
the
most
impactful
and
how
we
can
give
that
out
the
door,
because
we've
talked
a
lot
about
getting
this
information
out
via
conferences
or
what
you
know
webinars
or
other
things,
but
you
know
to
what
degree
does
this
need
to
be
more
of
a
publicized?
You
know
Partnerships
with,
like
you
know,
arguably
the
most.
C
D
E
The
free
avenues
like
the
githubs,
everybody
knows
if
you
touch
technology,
you
know
what
GitHub
is
so
I
mean
those
are
the
types
of
things
that
I
think
are
are
going
to
be
key
and
not
just
not
just
the
personas,
but
also
you
know.
What
is
the
you
know
somewhat
marketing
aspect
of
how
we
get
this
out
the
door.
A
E
A
A
Again
we
do
not
have
nearly
the
the
the
degree
of
Milestones
here
that
we
need
to
we
identified
as
a
team
that
we
wanted
to
do
this
in
year,
one
we
wanted
to
localize
some
training
to
five
human
non-english
languages.
That's
a
very
Broad
and
open
statement.
We
need
to
to
make
that
much
more
granular
determine
how
to
get.
You
know
which
training
needs
to
be
localized,
determine
which
languages
need
to
translate
into
Source
people
who
are
skilled
in
this
area
and
would
be
able
to
actually
do
this.
A
We
do
have
a
budget
ask
on
here,
which
is
I,
think
just
a
shot
in
the
dark,
for
perhaps
something
like
this
might
cost
I've
never
done
localization
in
any
way,
shape
or
form.
That's
always
been
outsourced
in
areas
that
I've
worked,
so
I
do
not
know
what
the
cost
might
be,
but
we
definitely
need
to
do
some
significant
work
on
on
this
goal.
C
So
the
in
terms
of
like
localization,
you
kind
of
seem
to
have
mentioned
some
of
the
Milestones,
because
you
talked
about
identifying
the
actual
languages.
It's
like
a
key,
and
also
just
finding
like
the
Partnerships
for
those
who
can
actually
do
the
localization
and
it
can
be
very
expensive,
yep
and
I'm
I'm,
not
even
sure,
even
around
a
localization
I.
A
I
agree:
it's
more
than
just
dropping
this:
the
battle
fish,
making
the
words
different
there.
There
are
meanings
and
contexts,
and,
and
all
that
sort
of
thing
that,
especially
when
you're
talking
about
topics
like
these,
we
need
to
ensure
that
we're
trying
to
cover
as
much
as
possible.
This
is
not
easy
work
by
any
stretch.
I
agree.
A
A
A
Yeah
I
think
Amy's
on
the
table.
I
I,
don't
know
what
kind
of
access
different
organizations
or
groups
might
have
for
this
sort
of
skill.
The
latest
Foundation
might
have
people
that
they've
worked
with
before
that.
We
can
leverage
that,
but
at
this
point
for
something
like
this
I
think
you
need
to
consider
professional
people
who
do
this,
as
as
their
child.
C
Yeah
because
I
had
to
do
some
localization
or
translation
once
and
it
was
like
a
combination
of
there
was
you
needed
the
person
who
actually
did
the
translation,
but
you
also
needed
like
an
engineer
or
somebody,
because
it
was
a
technical
document.
You
needed
an
engineer
who
knew
that
language
to
verify
it
and
say:
okay,
this
does
not
sound
right
and
it
also
again
it
depended
on
the
translation
company.
D
C
D
C
A
A
Any
any
resources
anybody's
aware
of
you
know
absolutely
we'll
talk
about
that.
Once
we
get
once
we
once
we
get
to
the
point
where
we're
starting
to
work
on
this,
but
we
just
need
to
lay
out
the
the
structure
of
how
we're
going
to
go
about
it
first,
before
the
end
of
the
month
for
the
end
of
November,.
A
All
right,
I'll
talk
briefly
about
1.6.
Now
this
is
a
year
two
goal,
so
I
am
not
oh
I'm,
not
as
concerned
about
this
one
as
the
other
ones,
although
we
do
need
to
have
some
information
in
here,
this
was
around
identifying
different
areas:
systems
where
developers
are
going
to
get
advice
on
how
to
code
and
our
copying
and
pasting
solutions
for
for
various
coding
needs.
Often
these
things
are
insecure.
A
Stack
Overflow
is,
is
probably
the
one
I'm
most
familiar
with
on
this,
but
I
have
no
doubt
that
there's
others
out
there
as
well.
So
the
intention
here
is
to
identify
these
systems
and
put
together
a
plan
to
help
them
I'm,
not
sure
whether
we
want
to
try
and
clean
up
the
code
or,
if
we're
just
going
to
identify
and
say
these
are
area.
These
are
systems
that
you
need
to
be
very
careful
of
when
you're
grabbing
information
from
them.
A
Personally,
as
as
a
person
who's
developed
for
a
long
time,
I
I
don't
think
that's
going
to
dissuade
developers
from
going
to
these
areas.
Hopefully,
they'll
make
them
think
twice
about
just
copying,
pasting
and
moving
on
when
they
find
a
solution.
I
think
we
need
to
put
a
little
bit
more
scope
around
this
one,
a
little
bit
more
clarity
around
what
it
actually
is.
We're
trying
to
accomplish
with
this
one.
B
If
I
can
offer
something,
so
SKF
actually
had
a
tool
that
was
going
to
be
a
command
line
tool
that
would
actually
check
all
of
the
stuff.
That's
in
SKF,
like
all
the
the
asvs
and
wstg
now
the
problem
that
we
ran
into
from
my
understanding,
because
I
was
not
a
part
of
the
team
at
that
point-
was
that
the
tool
lacked
context.
However,
now
with
the
new
graph
database
that
we're
working
on
that
might
change,
so
there's
a
possibility
that
maybe
that
can
be
used
for
this.
B
So
you
would
install
it
in
your
in
your
CI
CD
and
it
would
just
basically
run
the
code
and
if
it
finds
anything
in
asvs
like
if
it
tests
for,
for
example,
cross-site
scripting,
it
would
flag
it
now.
The
way
that
what
was
going
on,
though,
is
that
it
would
flag
a
lot
of
things
that
might
have
been
correct,
because
when
I
say
the
tool
lock
context,
there's
sometimes
when
like
it
would
just
pick
up
a
certain
coding
pattern.
B
That
was
not
correct
and
it
would
require
manual
intervention
to
see
it
which
had
some
opinions
of
the
people
of
SKF
at
the
time
were
that's
not
a
bad
thing,
because
you
just
have
to
manually
check
it
which
it's
still
doing
its
job.
However,
what
I'm
saying
is
now
with
the
graph
database
that
might
be
an
interesting
tool
to
come
back
to,
because
it
would
be
able
to
identify
context
a
little
bit
better.
A
We
need
to
figure
out
how
to
do
something
is
I
jump
out
to
stack
Overflow
and
I
I.
Do
a
search
and
I
find
someone
who's
able
to
do
what
I'm
trying
to
do
or
make
or
something
close
enough
I
copy
and
paste
their
code
into
mine,
and
if
it
works,
I
just
move
on
and
do
other
things
and
some
of
the
code
They're
copying
is
not
secure.
A
A
Find
yeah,
I
I
agree.
Those
types
of
things
are
very
useful
and-
and
you
know,
publicizing
that
and
trying
to
engage
the
community
so
so
they're
aware
of
these,
these
types
of
tools
and
things
I
think,
is
very,
very
helpful.
You
know
it
gives
them
another,
a
quiver
error
in
the
quiver
when
it
comes
to
you
know,
trying
to
secure
their
code
and
if
we
have
them
in
the
mindset
of
at
least
considering
the
security
of
the
code,
that
they're
writing
I
think
that's
already
a
win.
D
B
A
I
agree
very
difficult,
I
think
so,
I
I
think
for
this
one.
We
really
need
to
clarify
what
the
objective
is.
We
know
that
this
happens.
We
know
that
there's
poor
examples
of
code
on
a
number
of
platforms
or
systems
that
developers
frequently
go
to
when
they're
when
they're
doing
their
coding,
and
we
want
to
to
do
something
about
that.
But
let's
what's
something
what's
the
end
effect
we
want
to
have?
Is
it
just
alerting
them?
A
Is
it
actually
trying
to
engage
with
these
systems
to
improve
things
or
or
something
else
entirely
so
I
think
that's
that's
a
something
for
us
to
consider
and
and
make
an
adjustment
to
this
one
just
to
make
sure
that
this
is
very
broad.
This
is
like
we're
going
to
go
out
we're
going
to
find
these
systems
where
developers
get
stuff
and
we're
going
to
make
it
better,
which
is
great
making
it
better.
But
but
how
are
we
going
to
make
it
better
and
what's
the
what's,
the
definition
of
success.
B
I
would
say
that
awareness
around
the
risks
of
using
that
code,
I
think
is
probably
about
as
good
as
we
can
do,
because
we
can't
prevent
people
from
using
in
maybe
some
recommendations
of
what
you
can
do
about
it.
I
guess,
if
you're,
not
sure
but
I
would
say,
awareness
around
the
risks
would
be
primary.
A
A
But
you
know
we
we
do
need
to
to
start
making
some
significant
progress
on
this
AC
version.
So
we
have
four
weeks
left
to
get
this
wrapped
up
in
in
probe's
hands.
So
he
can
then
combine
them.
Combine
our
goals
with
the
goals
from
sections
two
and
sections
three
put
that
in
a
cohesive
format
to
present
to
the
TAC.
So
we've
got
our
work
cut
out
for
us
here
and
and
it's
going
to
take
contributions
from
everybody
and
we're
not
gonna,
be
able
to
do
it
during
just
these
meetings.
A
We
have
to
do
all
this
work
offline.
So
please,
as
you
have
some
time
go
through
it
and-
and
you
know,
feel
free
to
add
whatever
you
think
makes
sense.
If
there's
a
an
item
that
we
would
like
to
have
an
offline
discussion
on
email
works,
slack
is
available.
It's
a
great
place
to
do
that
sort
of
thing,
but
we
definitely
need
to
focus
on
this
over
the
next
several
weeks.
A
I'm
not
I'm
at
the
Cleveland
information
security,
Summit
I'm,
not
a
coupon,
unfortunately
alrighty,
but
if
you
see
Sal
tell
her
I
said:
hi
will
do
appreciate
that
all
right!
Well,
hey
thanks!
Everybody
I'm
gonna
go
over
there
and
hunt
down
Chrome
and
let
them
know
about
the
SKF
stuff
and
Randall,
we'll
we'll
be
in
touch
as
far
as
we
can
have
a
conversation
about.
That
sounds
good.