►
From YouTube: Sigstore Community Meeting Nov 1, 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).
A
B
Okay,
welcome
everybody
to
this
week's
six-star
community
meeting
in
a
world
where
Sixto
is
now
in
GA
and
yeah
had
a
great
week
last
week
for
those
who
made
it
to
six.com
so
we'll
be
covering
all
of
that
in
the
course
of
the
meeting,
but
as
phenomenal,
we'll
start
off
with
the
project
round
robin
so
anyone
here
any
updates
on
the
RICO
side.
C
Foreign
Bob
did
you
want
to
comment
on
rolling
back
zero,
zero,
two
change.
A
A
Unfortunately,
the
way
that
the
current
type
is
written,
we
copy
the
double
encoded
version
over
for
the
signature
value,
so
that
essentially
means
in
order
to
have
backward
compatibility.
We
need
to
yet
again
route
the
entire
type.
So
it's
a
trivial
change,
but
unfortunately,
we've
got
to
do
that
to
get
backward
compatibility
so
that
change
was
committed
and
rolled
back
that
never
actually
pushed
into
production.
A
So
we
don't
have
any
entries
in
the
log
that
we
need
to
worry
about
a
backwards,
combat
issue
with
it's
just
a
matter
of
rolling
that
out
as
a
new
type.
A
So
the
change
is
a
little
bit
more
complicated,
just
because
there's
a
little
more
Plumbing
that
has
to
get
done,
but
I've
got
the
pr
mostly
done
and
as
soon
as
I
get
out
of
meetings.
I
will
hopefully
push
that
up
either
today
or
tomorrow.
B
C
Yesterday,
myself,
Milan
Kenny
completed
the
CT
log
sharding,
so
this
is
the
certificate
transparency
log
that
records
all
issued.
Folsio
certificates
it
for
Best
Practices,
it's
best
to
Shard
the
log
to
keep
it
smaller
yearly,
and
so
we
started
from
the
previous
law
called
test
to
a
new
law
called
2022.
We'll
do
the
same
in
2023.
C
went
very
well,
it's
all
done.
Hopefully
you
didn't
notice
if
you
use
any
client
that
uses
tough,
the
new
verification
key
was
pulled
in
automatically.
If
you
are
verifying
not
using
tough
or
certain
clients,
you
may
have
had
to
update.
B
Seamless
to
me,
yeah
thanks,
Hayden,
all
right
time
to
go
sign
and
Zach.
Do
you
want
to
cover
this?
What
are
our
versioning
guarantees?
Yeah.
C
So
in
LinkedIn
the
doc
is
a
GitHub
discussion,
basically
with
a
bunch
of
different
questions
around
like
what
are
our
versioning
guarantees,
there's
some
documentation
on
the
six
door
docs
about
this,
and
it
is
not
nearly
as
detailed
as
I
would
like,
especially
now
that
we're
ga
so
questions
in
here
include
like.
Are
we
versioning
the
API
in
the
CLI
in
cosine
the
exact
same
way?
Implicitly,
it
seems
like
we're
doing
that.
Should
we
be?
C
What
are
the
guarantees
on
backwards?
Compatibility
in
the
CLI
I
am
of
the
opinion
through
hard.
One
experience
that,
like
strict
semantic
versioning,
isn't
a
realistic
goal
for
clis,
just
because
what's
a
breaking
change,
if
I
change,
like
some
output
to
standard
error,
is
that
a
breaking
change,
people
will
complain
at
you
about
that.
C
I've
learned
from
experience,
so
I
don't
think
we
can
cover
nearly
all
of
these
in
a
meeting
like
this,
but
I
would
strongly
strongly
encourage
people
to
raise
versioning
issues
of
their
own
and
discuss
with
me
and
then
here's
my
proposal
on
version
and
stuff
is
I'll.
Let
this
sit
for
the
rest
of
the
week.
I
would
love
as
much
feedback
as
and
arguing
and
whatever,
as
anyone
wants
to
do
during
that
time
period.
C
At
that
point,
I'm
gonna
try
to
make
a
proposal
about
a
versioning
policy,
including
resolutions
to
most
of
these
questions
based
on
kind
of,
hopefully,
a
consensus
opinion,
but
all
tiebreak
consensus
in
in
my
favor
and
then
and
then
I'll
circulate
ahead
of
the
next
community
meeting.
Basically,
a
rough
proposal
try
to
solicit
a
bunch
of
feedback.
C
I
yeah,
my
hope,
is
to
articulate
a
coherent
strategy
that
covers
most
of
the
questions,
so
that
might
mean
that
the
versioning
proposal,
like
the
thing
that
the
text
that
we
would
ultimately
publish,
isn't
necessarily
structured
like
this
discussion.
But
hopefully
it
will
give
you
answers
to
most
of
the
issues
raised
in
this
discussion
or
all
Pont
on
things
that
are
particularly
controversial
and
in
the
hope
of
getting.
You
know,
an
easy
win,
and
then
we
can
resolve
those
those
things
later.
C
C
I
just
wanted
to
mention
that
this
tracking
issue
is
here
we're
starting
to
think
through.
What's
going
to
be
a
part
of
the
next
major
release
of
cosine,
the
primary
motivation
for
this
is
we
need
to
drop
the
cosine
experimental
flag.
It's
going
to
require
a
whole
bunch
of
changes
on
whole
bunch
of
places,
so
we
should
take
advantage
of
this
and
get
in
any
other
changes
that
we
want.
C
There's
some
discussion
in
here
about
you
know
not
making
the
scope
massive
for
this,
but
if
there's
something
that
is
a
breaking
change
that
you'd,
like
included,
please
comment
it
here,
so
we
can
discuss
more
if
there's
a
non-breaking
change
that
you
think
would
be
really
important
to
get
into
feel
free
to
add
that
in
also.
C
We
Pro,
we
should
chat
about
that.
I
I
I'm
not
going
to
come
into
timeline
now,
because
we
haven't
really
discussed
I
I
think
we
all
want
it
to
be
done
as
soon
as
possible,
since
we
no
longer
need
the
experimental
flag.
But
there's
there's
a
lot
of
work
to
be
done.
I
think
we
just
need
to
split
up
work
figure
out
what
actually
needs
to
change
be
nice
to
have
it
done
by
in
the
year
but
yeah.
C
Maybe
that's
a
good
topic
for
our
next
week's
GA.
Sync.
B
Thanks
I
didn't
right
anything
from
git
sign.
C
We
released
a
0.1
release
of
the
timestamp
authority.
Thank
you
to
Meredith,
Carlos
and
Hector
for
helping
out
with
this.
Please
give
it
a
try.
It's
a
pretty
simple
service.
We
provide
a
client,
a
server.
You
can
also
use
openssl
instead
of
the
client
that
we've
written
and
the
instructions
are
all
in
the
readme
of
how
to
operate
it
and
how
to
fetch,
signed
timestamp
so
give
it
a
try.
C
C
F
Sure
I
can
go
over
some
details,
so
there
is
a
new
repository
for
capturing
protocol
buffer
specifications
for
the
new
bundle
format
and
the
plan
is
to
continue
to
add
in
new
versions
of
the
API
as
well
here.
So
we
have
everything
in
a
single
place
to
have,
for
instance,
reusability
being
easier
to
use
and
yeah
the
first
pull
request
got
merged
yesterday,
which
is
the
new
bundle,
format
and
sort
of
as
a
consequence
of
the
discussions
we
had
last
week
on
six
Recon.
F
We
are
starting
to
mess
around
right
now
with
structures
for
capturing
various
details
that
are
going
to
be
used
for
verification
flows,
so
yeah
feel
free
to
jump
in
and
take
a
look
and
see
what's
happening.
So
it's
not
super
much
there
right
now,
but
definitely
it
will
continue
to
grow
as
time
passes
by.
C
Yeah,
no,
the
only
the
only
thing
I
wanna,
I,
wanna
call
out
specifically,
which
is
that
Ezra
mentions
that
it's
very,
very
interesting
to
implementers
of
all
six
store
clients
so
cosine,
yes,
but
all
the
language,
implementations
and
so
on.
Policy,
controller,
Etc,
so
I
just
dropped.
A
link
and
I
pinned
this
in
the
pound.
Cosine
slack
Channel.
E
B
C
You
want
to
talk
about
yeah
back
back
to
me,
the
the
so
in
the
wake
of
ga
we're
gonna
pick
back
up
an
effort
that
had
been
underway
a
little
while
ago,
which
is
basically
writing
writing
down
what
six
door
is
and
does
and
looks
like
so
also
known
as
specifications.
C
This
is
I
think
actually
really
important
work,
especially
as
we
have
more
client
libraries
because,
while
I'm
more
than
happy
to
like
sit
down
and
help
out
a
client
for
a
new
language,
reverse
engineer
the
exact
behavior
of
falsio
and
and
so
on-
that's
not
infinitely
scalable
and
so,
and
so
we
really
want
to
write
down
basically
what
it
takes
to
be
a
compliance.
Sig
store
client
how
to
do
verification
securely.
C
All
these
things,
there's
a
bunch
of
other
benefits,
I
think
to
having
having
this
stuff
written
down.
So
this
is
pretty
unglamorous.
But
important
work
involves
a
lot
of
like
writing
and
not
a
lot
of
writing
code.
C
I
encourage
everyone
to
join
the
discussion
in
the
architecture,
docs
channel
on
slack
and
then
I
just
dropped
a
link
to
yeah
so
so,
or
you
can
contribute
I.
Think.
There's
a
pinned
Link
in
that
architecture,
docs
channel
to
this
landing
page
and
then
from
that
landing
page
you're,
gonna,
you're,
gonna,
see
all
the
in
progress
documentation
that
we're
working
on
so
comments.
C
Welcome
if
you'd
like
to
help
out
and
write
a
section,
that's
welcome
as
well,
and
ultimately
these
are
going
to
land
in
that
GitHub,
repo,
but
I.
Think
while
they're,
you
know
moving
really
fast,
which
they
still
are.
We're
gonna
keep
them
in
Google
Docs
for
for
just
a
little
while
longer
so
we're
gonna
have
a
planning
meeting.
If,
if
everything
works
out
towards
the
end
of
this
week,
I
just
dropped
a
doodle
poll
in
the
meeting
notes
for
this
meeting.
C
So
if
you're
interested
in
coming
check
that
out,
if
not
we're,
probably
just
going
to
try
to
psych
ourselves
up
to
do
some
writing
and
if,
if
you'd
like
to
participate
asynchronously,
that's
that's
fine
as
well.
Just
let
us
know
on
that
channel.
We
can
find
something
for
you
to
help
out
with.
B
Great
thanks,
Zach,
and
just
maybe
a
quick
mention
on
the
singular
Community
specification
model.
I
did
note
this.
Maybe
a
webinar
coming
up
this
month
that
jury
person
is
running
kind
of
a
like
everything
you
want
to
know
about
next
steps
on
that.
So
I'll
dig
up
the
details
and
send
it
around
if
anyone's
interested.
B
B
Effects
it
doesn't
sound
like
it,
okay,
so
on
to
sigs.ga,
put
a
little
bit
stuff
on
the
pr
effort
there,
but
yeah
I.
Think
in
general
we
had
the
announcement
go
out
at
six
o'conn
last
Tuesday,
as
you
can
see
the
blog
post
there,
which
details
kind
of
the
highlights
of
it,
and
then
we
worked
with
openssf
on
the
pr
and
I've
copied
in
some
of
the
the
reporting
from
that
it
was
really
well
received
by
pressing
media.
B
So
you
can
see
links
to
all
the
Articles
folks
wrote,
including
you
may
or
may
not
have
heard
of
TechCrunch
and
a
few
others.
B
So
yeah,
it's
a
really
good
coverage,
nice
to
see
people
excited
about
Security,
Solutions
and
then
the
second
section
I
wouldn't
really
go
through
it,
but
it's
just
a
set
of
the
the
links
to
like
the
press
releases
and
the
blog
posts
written
by
the
community
and
yeah.
No,
so
thanks
to
everybody
who
was
involved
with
that,
and
also
the
folks
who
did
interviews
and
contributed
to
those
articles
and
also
to
tie
in
with
GA
there's
also
I
want
to
highlight
a
new
landing
page
on
the
openssf
around
six
store.
B
This
sort
of
talks
about
it
high
level
in
links
to
a
playlist,
highlight
some
case
studies
and
just
kind
of
nice
ctas
call
to
actions
in
there.
B
B
Or
maybe
anyone
else,
Hayden
Priya.
B
Great
and
we'll
jump
into
six.com
a
little
bit
more
later,
but
I'm
gonna
stick
with
the
agenda
on
here
ducks
some
notes,
some
fixes
and
updates
coming
up
and.
G
Yeah,
that's
all
I
I
was
talking
to
a
few
people
on
slack
and
in
issues
about
some
link
issues
and
I'm
planning
on
fixing
them.
But
if
anybody
has
any
feedback
on
my
proposed
solution,
let
me
know
it's
in
the
docs
Channel
and
Slack.
B
Yeah
I
don't
know
if
Eric
smalling's
on
the
call
so
he'd
been
looking
around
and
stuff
so
yeah.
Thanks
appreciate
the
extra
eyes
and
hands
on
that
so
okay
and
to
outreach
an
event
so
hacktoberfest
I
guess
it's
officially
over
now
that
we're
into
November
yeah
I
think
we,
this
kind
of
ended
up
overlapping
with
a
lot
of
kubecon
and
other
things.
So,
while
we
I
think
we
gave
it
a
bit
of
a
a
stab
I'm,
not
sure
how
far
it
went,
did
anybody
see
any
significant
activity
or
any
PRS
come
in.
G
B
No
spam
and
yeah,
we
just
got
folks
into
the
process
a
bit
so
but
yeah
fair
enough
with
all
the
ga
activity
going
on,
it's
good,
all
right
and
six.com,
so
yeah
that
was
last
Tuesday
thanks
for
everybody
who
was
able
to
make
it
in
this
big.
Thanks
to
all
the
speakers,
yeah
I
thought
there
was
some
really
great
talks
and
I
do
encourage
folks
to
check
them
out.
B
They
are
already
up
on
a
playlist
on
YouTube,
so
really
happy
that
even
those
who
couldn't
be
there
can
catch
the
talks
yeah
so
super
great
to
meet.
Folks
I
was
wondering
if
we
could
do
like
a
quick
retro.
If
anybody
had
feedback
on
the
event
on
stuff
that
went
well
or
stuff
that
we
could
do
better
with
yeah
happy
to
have
a
discussion
or
take
any
feedback.
B
If
you
want
to
do
it
here,
that's
great
too
yeah
after
as
well.
But
anyone
with
any
comments.
D
I'll
go
I'll,
take
a
stab
Tracy,
I
I
believe
it
was
my
first
time
to
be
able
to
meet
many
of
you
face
to
face
and
I
really
enjoyed
that.
So
thank
you
very
much.
I
think
for
myself.
The
Retro
would
be
I
need
to
show
up
a
little
bit
earlier,
so
I
can
introduce
myself
before
going
on
stage,
but
thank
you
very
much
for
the
opportunity.
Autodesk
really
appreciates
it.
I
really
appreciate
it.
B
B
All
right,
yeah
but
feel
free
to
hit
me
up
if
there's
any
other
feedback.
Just
a
couple
of
follow-ups
will
be
just
following
up
with
some
announcements
around
the
community.
Awards,
maybe
get
a
blog
post
out
and
I'll
be
reaching
out
to
the
folks
who
weren't
able
to
be
there
to
receive
their
Awards
just
to
coordinate,
getting
them
sent
sent
to
you,
but
yeah.
Congratulations
to
developer,
guy
and
Ezra,
and
the
salsa
GitHub
generators
who
are
kind
of
our
three
Award
winners.
B
Thank
you:
okay,
six
dollar,
landscape,
yeah.
So
one
of
the
things
we
sort
of
casually
highlighted
at
six.com
and
I
just
wanted
to
call
to
people's
attention
is
we
have
a
little
landscape
tab
which
is
as
part
of
the
open
ssf.
The
open
ssf
has
this
main
landscape,
which
sort
of
shows
their
members,
but
we
have
a
a
sub
tab
under
that
which
I
don't
know.
B
Folks,
remember
it
kind
of
highlighted
a
sketch
for
this
many
many
many
months
ago,
and
the
main
motivation
was
really
helping
people
to
navigate
the
ecosystem,
especially
as
it
grows.
It's
helping
them
just
get
some
awareness
of
the
projects,
as
well
as
the
public
deployment,
so
highlighting
the
public
instance
as
well
as
we
have
this
link
which
links
out
to
the
repo
Zach
highlighted,
which
eventually
should
you
know,
be
an
overview
of
the
architecture
and
and
the
spec.
B
We
also
have
sections
in
there
for
Integrations,
so
anything
that
allows
you
to
sign
with
cosine
of
C.
If
things
are
signed
and
if
you
click
on
them,
you
will
see
there
should
be
a
details,
tab
which
takes
you
to
a
link
to
talk
about
what
is
the
specific
integration
or
how?
How
do
they
fit
in
together.
B
The
language
clients
are
all
featured
there
as
well,
so
again,
links
to
the
repos,
so
folks
can
see
awareness
of
what's
existing
and
then
signed
with
includes
a
section
where
you
can
see
which
things
are
signing
with
cosine
and
how
you
would
go
about
verifying
them.
So,
for
example,
see
python.
Has
this
how
to
verify
Link
at
the
end
there,
which
talks
about
where
it's
being
used
and
how
to
verify?
B
And
finally,
for
the
case
studies
we've
been
doing
on
the
blog
we've
also
put
in
links
there,
so
those
link
out
to
the
blog
post,
but
again
just
a
discovery
mechanism,
so
folks,
new
to
the
ecosystem,
can
come
in
and
start
to
get
a
quick
visual
picture.
B
So
it
is
all
open,
source
and
I.
Think
we'll
try
to
put
some
guidelines
if
anybody
wants
to
help
out
adding
features
or
adding
PR's
yeah
happy
to
do
that
and
yeah
welcome
open
to
any
ideas.
E
Tracy,
how
do
I
add
someone
to
that
list?
We
have
psyllium
signing
now,
so
how
do
I
get
them?
Yeah
reflected
there.
B
So
if
you
go
ahead
and
open
a
pull
request,
so
if
you
click
on
that,
what
it
is
is
it's
a
bunch
of
XML
and
an
SVG,
so
I'm
going
to
take
maybe
an
example
of
the
kyvono
one.
B
So
you'll
be
oops.
Sorry
I'm
not
sharing
this
here's
an
example
of
Carbono,
so
you
just
add
in
the
right
section,
the
name
URL
Twitter
and
a
LinkedIn.
How
to
verify-
and
maybe
the
only
tricky
bit
is
that
you
need
to
have
an
SVG,
but
the
psyllium
is
already
in
the
cncf
landscape.
We
can
just
like
copy
copy
that
SVG.
B
Yeah
happy
to
take
a
pull
request
and
sync
with
you
on
that
and
congratulations
to
silly
I'm
gonna
go
ahead.
Deciding
that's
awesome
to
hear.
B
Moving
on
so
for
stem
first
time,
it's
like
the
big
event
in
Europe,
which
will
be
in
February
next
year.
I
know:
there's
a
few
folks,
I've
been
speaking
to
who
are
interested
in
having
a
presence
there.
So
one
option
is
that
we
could
have
a
six-star
booth.
B
We
do
have
to
submit
something
by
15
November,
but
the
boots
are
free
and
either
set
up
as
tables
where
we
can
give
away
swag
and
just
have
conversations
with
all
the
open
source
folks
who
go
to
fosdem,
but
the
other
thing
we're
thinking
of
like
some
feedback
I
had
from
sigster
con
is
folks
would
love
some
space
where
we
could
get
contributors
together,
get
our
laptops
out
and
pack
on
some
stuff,
so
we're
thinking.
Maybe
we
could
also
do
a
contributor,
Summit,
AT
fosdem.
B
It
would
have
to
be
something
we
organize
as
ourselves
like
just
get
a
room
and
set
up
a
way
for
people
to
register
and
show
up,
but
I'd
be
willing
to
look
into
something
like
that.
If
there's
enough
interest
from
folks
so
yeah,
let
me
know
I
might
set
up
a
document
or
throw
something
up
in
slack.
Just
to
kind
of
test
the
waters
and
see
see
who
wants
to
be
involved.
B
Okay,
moving
on
on
blog
posts,
I
wanted
to
highlight
case
studies.
We've
been
working
with
Jesse
and
Autodesk
on
an
upcoming
case
study.
That's
now
ready
for
review,
so
folks
can
take
a
look
at
that
I'm,
hoping
to
maybe
get
that
up
later
this
week
or
early
next
week,
and
we've
got
a
bunch
of
folks
in
progress.
So
there's
one
I'm
from
Verizon
and
one
kubernetes
folks
and
a
couple
of
things
coming
out
of
sigster
con
as
well.
C
C
It
doesn't
really
it
sort
of
requires
a
certificate
which
we
do
create,
but
a
certificate
with
a
like,
maliciously
chosen,
email
address
in
it
and
we
don't
let
people
choose
their
email
addresses
we
we
sort
of
get
those
from
our
oidc
providers,
so
this
this
shouldn't
be
relevant
to
any
Sig
store
clients
in
theory
again,
as
Hayden
points
out,
if
you're
doing
something
private
and
custom
and
weird
you
know
like
if
you
have,
if
you
had
your
own
version
of
this,
it
could
maybe
yeah
yeah.
C
Sorry,
it's
not
going
to
affect
cosine,
but
oh
yeah,
so
it's
not
going
to
affect
cosine
or
what
I
worry
about
it
or
what
I
was
worried
about
for
a
moment.
Was
we
issue
certificates
that
are
bad
for
people
to
verify,
using
open,
SSL
and
cause
like
a
buffer,
overflow
and
stuff
and
again,
it
seems,
like
that's
extremely
unlikely,
it's
possible
in
like
a
private
deployment,
but
also
even
if
I
have
in
cosine,
isn't
affected
and
and
so
we're
all
in
pretty
good
shape,
but
just
wanted
to
make
it
make
a
note
of
that.
C
Instead
of
and
it's
possibly
worth
I,
don't
know
filing
an
issue
somewhere
or
having
a
the
document
somewhere.
That's
just
like
is
six
door
affected.
No,
just
because
I
know
people
are
going
to
be
thinking
about
it
and
asking
about
it
for
the
next
couple
days.
C
There's
a
there's,
a
good
comment
on
Hacker
News
that
I
liked
that
in
practice,
the
way
that
you
know
this
would
be
most
critical
would
be
if
you
somehow
were
able
to
get
a
CA
to
issue
you
a
certificate
for
TLs,
but
also
for
email
to
trigger
this.
This
email
name
constraint
well
and
that's
unlikely,
if
not
improbable
it.
You
know
I
I,
think
here,
given
that
we
do
talk
about
emails,
somebody
might
think
about
it.
C
You
know
potentially
affecting
us,
but
given
we
yeah,
so
we
can
say
something
but
I
mean
I'm
not
worried
about
this
I
think
this
was
overhyped
by
a
lot.
F
C
C
If
you
look
at
the
open,
SSL
website,
one
of
their
essay
FAQs
is:
is
this
branded
no,
but
yeah
I
would
appreciate
if
anyone
has
like
a
good
way,
I
don't
know.
Maybe
we
should
tweet
about
it
or
something
like
what's
the
best
way
of
communicating
something,
that's
like
lighter
weight
than
doing
a
full
blog
post,
I
guess
that
would
be
a
tweet,
so
maybe
I'll
I'll
make
a
suggestion
in
the
six
door
slack
immediately
after
this
meeting
saying
like
we
should
just
tweet
and
say
it
doesn't
affect
six
of
our
users.
B
C
Yeah,
that's
a
great
idea,
true
sharks,
so
yeah
so
also
you
see
and
Hayden
Hayden
and
I
can
draft
very
quickly
because
we
have
200
characters
to
work
with
or
whatever,
but
a
tweet
and
then
and
then
get
that
out.
B
Okay,
thanks
sick,
all
right
anything
else
that
was
moving
on
to
introductions,
and
this
is
a
section
where
we
like
to
welcome
anyone
new
to
the
community
new
to
these
meetings
or
someone
would
just
like
to
reintroduce
themselves
or
say
hi.
B
So
yeah
Flora
is
open.
Anybody
want
to
say
a
few
words.
B
I
think
you've
had
enough
time
to
fiddle
with
the
mute
button,
so
doesn't
sound
like
anyone
new
so
yeah
they
let
you
all
recover
from
the
travels
those
who've
been
traveling
in
time
zone
changes
for
those
in
Europe
and
I'll
see
you
next
week
next
week
is
the
office
hours
have
a
talk
from
Folks
at
DB
Schenker,
who
will
be
talking
about
the
use
of
six
store
for
and
that's
a
supply
chain
company,
so
supply
chain
company
talking
about
the
supply
chain
security,
so
that
should
be
pretty
fun
and
yeah.
B
We
do
have
slots
as
well.
If
anybody
wants
to
talk
or
demo
at
office
hours,
let
me
know
or
just
drop
something
into
the
agenda.
Otherwise,
we'll
see
you
all
next
week
or
whenever,
but
thank
you
all
for
joining
bye.