►
From YouTube: CDF TOC Meeting - July 19, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
Okay,
hello,
hello,
so
today
is
july.
19Th
thanks
everyone
for
joining
the
cdfg
meeting.
Let's
take
a
look
at
our
agenda.
A
A
Yeah
the
list
looks
good,
so
let's
check
what
we
have
from
the
previous
week,
so
yeah
babies,
the
budget,
I'm
waiting
for
the
governing
board
meeting
changing
the
meeting
time.
I
guess
selection
item
is
to
create
a
doodle.
If
anyone
wants
to
change
it.
Well,
maybe
I
wanted
to
run
it
and
yeah
jenkins
sex
topics
we
discussed
yesterday.
I
believe
so.
Yeah
legend
for
today
is
quite
short
and
yeah.
The
first
item
was
to
share
election
so,
but
you
would
be
alright.
Yes,.
C
So,
as
you
see
the
timeline
that
this
is
based
on
like
criticism
to
last
year's
election
timeline,
so
the
first
thing
is
basically
presenting
timeline,
which
is
what
I
am
doing
right
now
and
the
plan
is
to
start
the
nomination
periods
for
those
this
year
on
cdf2lc
mail
list
tomorrow
and
the
rest
of
the
dates.
Key
dates.
Are
there
like?
C
So
we
added
that
as
an
exclusive
item
and
tomorrow
morning,
tomorrow
morning,
I
think,
eastern
time
morning
michelle
will
send
an
email
to
your
email
list
and
post
a
message
to
slack
channel
officially
kicking
off
the
nomination
period
and
as
you
see
there,
there
is
a
link.
We
will
collect
the
nominations
on
an
issue
on
foundation
repo
because
some
people
ask
where
they
can
see
nomination
statements
and
so
on
for
earlier
elections,
and
we
want
to
make
this
transparent.
So
the
nominations
will
be
collected
on
the
issue.
B
So,
just
on
the
issue
just
put
a
a
a
new
comment
on
the
issue.
If
yeah
for
the
nomination.
C
A
Yeah,
so
the
next
item
is
about
coming
into
dogs.
A
A
C
And
just
so,
you
know
like
if
we
identify
some
other
missing
documents
or
if
we
find
some
information
is
missing
in
the
documents
we
will
submit,
then
we
can
always
go
and
make
them
better
because
some
of
these
things
we
came
up
with
this
list
based
on
the
conversations
we
have
been
in
the
last
couple
of
weeks
and
we
want
to
make
them
documented.
So
everyone
can
learn
more
about
how
things
are
running
within
cdf.
How
do
you
request.
E
C
I
can
share
my
screen
and
terry,
would
you
like
to
start.
F
Yeah
sure,
so
what
we're
looking
at
here
really
is
a
sort
of
bigger
picture
view
about
where
we
think
we
should
be
focusing
our
attention
next,
within
the
cdf.
F
Now,
as
as
part
of
the
work
that
we've
we've
been
doing
with
best
practices,
I've
been
interviewing
a
lot
of
people
out
there.
You
know
in
in
small
and
large
organizations,
and
it's
been
become
pretty
clear-
that
there
are
really
two
categories
of
consumers
of
of
continuous
delivery
out
there.
All
of
this
hinges
around
the
you
know
the
fundamental
reality
that
continuous
delivery
is
is
just
part
of
a
business
methodology
to
optimize
product
commercialization
and
so
for
those
organizations
that
are
already
heavily
inoculated
with
that
culture.
F
Continuous
delivery
is
actually
proving
to
be
a
really
hard
problem
because
they're
they
haven't,
got
the
basic
cultural
understanding
of
you
know.
What's
driving
these
behaviors
and
therefore
they're,
not
understanding
what
the
benefits
are
or
what
the
tools
are
doing
for
them,
and
so
you've
got
this
fundamental
challenge.
That
implementing
continuous
delivery
is
really
hard.
When
you
don't
know
what
you
don't
know.
F
And
at
a
project
level,
many
of
these
continuous
delivery
tools
are
actually
only
focusing
on
small
parts
of
of
the
engineering
bit
of
the
problem,
not
addressing
the
the
bigger
picture
which
is
you
know?
How
do
you
make
this
work
for
an
organization
so
that
they
realize
the
value
that's
inherent
in
those
dora
metrics,
you
know
how
do
you
get
people
to
the
point
where
they
can
actually
get
to
that
top
twenty
percent,
where
they're
performing
a
thousand
times
better
than
their
competitors.
F
So
if,
if
we're
really
going
to
spread
the
adoption
of
continuous
delivery
and
get
a
much
bigger
audience
for
it,
then
we
we
need
to
be
looking
at
ways
in
which
we
can
address
those
issues.
F
And
a
lot
of
that
is
how
do
we
actually
reach
out
to
those
you
know,
people
who
would
benefit,
but
not
yet
deeply
invested
in
this
as
a
way
of
working
and
not
seeing
how
how
they
can
use
those
technologies?
Those
methodologies
now
the
challenge
is
that
most
of
those
organizations,
whilst
they're
building
technology
they're,
not
free
to
mix
and
match
the
build
tools
that
they're
they're
using
you
know
in
the
in
the
vast
majority,
they're
constrained
to
using
whatever's
available
from
their
cloud
vendor.
F
So
one
of
the
things
that
we
should
be
looking
at
is
moving
away
from
js,
focusing
on
the
local
engineering
problems
within
individual
projects
and
start
thinking
about
the
bigger
picture
of
how
the
cdf
can
help
to
span
that
gap
between
project
teams,
the
vendors
that
are
benefiting
from
those
projects
and
and
then
the
end
users
that
that
we
and
they
are
both
servicing
with
the
things
that
we're
building.
F
D
F
Own
problems
in
their
own
delivery
space-
now,
obviously,
we've
got
a
bunch
of
the
parts
of
this
recipe
are
already
in
place.
You
know,
we've
we've
done
a
lot
of
work
over
the
f
past
few
years,
with
best
practices
with
sick
events,
interoperability
and
and
now
with
the
the
new
developing
areas
of
ml,
ops
and
software
supply
chain.
F
F
So
as
a
result-
and
I
think
we
can
skimp
ahead
here-
to
what
we're
proposing
here-
is
to
take
the
learnings
that
we've
got
from
all
these
pieces
of
work
and
use
that
to
spell
out
a
reference
architecture
for
continuous
delivery.
So
here's
the
simple
map
of
all
the
pieces
that
you
need
to
think
about
from
a
practical
perspective,
to
be
able
to
do
this
within
your
team
or
your
organization.
F
Here
are
the
here's
this
the
bigger
picture
of
how
all
this
stuff
needs
to
tie
together,
and
then
here
are
some
places
that
you
can
go
to
get
a
starting
point.
That
says
you
know
if
you
work
with
this
reference
implementation
you'll
be
able
to
get
up
and
running
and
have
your
learning
experience
in
a
hands-on
way
within
a
structure.
That's
already
helping
to
guide
you
down
the
right
path,
and
certainly
from
my
previous
experience,
the
leading
teams
on
on
that
cd
journey.
F
So
what
you
need
to
do
is
give
them
a
set
of
tools
that
are
already
pre-configured
in
a
way
that
they
can
have
their
learning
experience
in
a
more
guided
fashion.
So
you
put
them
on
rails
to
an
extent
you
allow
them
to
start
using
the
process
and
the
methodology
and
then,
as
they
start
to
find
individual
problems
where
they
need
to
diverge
from
that
on
rails
path.
They've
got
the
opportunity
to
learn
in
more
depth
about
you
know
a
particular
challenge
within
kubernetes
or
a
particular.
F
B
F
So
we
we
already
have
some
of
that
planned
into
the
best
practices
roadmap,
but
the
the
idea
really
is
to
help
to
provide
a
conduit
for
the
individual
projects
to
to
reach
their
end
customers
by
providing
things
like
that
through
the
the
umbrella
of
of
the
cdf.
F
So
so
the
idea
really
is
to
set
set
some
basic
guidelines
around
you
know
these
are
the
bits
that
you
need
within
an
architecture
to
be
doing
continuous
delivery
in
in
a
you,
know,
consistent
and
reliable
way
and
then
facilitate
individual
projects
to
come
forward
and
say
well
and
here's
how
you
can
implement
that
using
you
know
this
tool
set
or
this
combination
of
projects,
and
I
think
the
the
key
recipe
here
is.
F
You
know
the
interoperability
and
the
the
sig
event
standards
that
will,
you
know,
make
it
easy
for
people
to
pick
and
mix
from
any
of
those
individual
projects
that
are
using
those
standards
but
still
operate
within.
You
know
an
overarching
set
of
guidelines
that
will
help
people
to
understand
and
be
comfortable
that
they're
going
in
the
right
direction.
B
Got
it
and
then
to
kind
of
follow
up
on
that,
would
would
you
envision
down
the
road
that
we
would
do
some
sort
of
like
certification
process
like
they
have
for,
like
you
know,
like
a
kubernetes,
you
know
application
developer
certification.
B
F
F
I
think
what
would
probably
be
more
useful
to
focus
on
in
in
the
early
days
is
how
we
can
actually
improve
the
continuous
delivery
experience
through
the
cloud
vendors.
So
how
can
we?
How
can
we
ensure
that,
when
a
cloud
vendor
is
selling
you
something
that
is
badged
as
a
as
a
continuous
delivery
solution
that
it's
actually
doing
all
of
the
things
you
actually
need
to
be
able
to
do
in
that
space
got
it?
I
think
that's
that's
particularly
needed
at
this
stage
in
the
ml
ops,
space
right.
B
F
There
are,
there
are
many
tools
out
there
now,
which
are
ml,
ops
tools
that
are
solving
one
out
of
a
couple
of
hundred
problems
that
exist
in
that
space,
and
so
there's
there's
no
one.
You
can
go
to
today
and
get
an
end
end-to-end
mlap
solution
that
will
actually
solve
all
the
problems.
You've
got
so
there's
a
lot
of
value
for
us
to
add
to
help
the
cloud
vendors
get
better
products
in
that
space
that
are
more
connected
and
covering
more
of
the
requirements
in
that
space.
C
So,
just
to
we
have
one
more
slide
here
like
again
this
thanks
terry
for
presenting
this
now.
The
timing
is
actually
pretty
good
to
bring
this
topic
up
and
toc
must,
you
know,
share
his
feedback,
their
feedback
about
this,
but
we
have
a
going
board
strategy
session
planned
for
next
week
and
this
topic
feels
like
a
good
fit
for
that
session.
C
G
Hey
fati,
I've
got
a
question
for
you.
Do
you
see
this
helping
to
support
for
support
renewals
in
october,
because
I
can
imagine
if
I
was
a
cloud
vendor
and
saying
hey,
something
is
coming
here,
this
reference
architecture,
I'd
very
much
like
to
be
a
part
of
that
and
set
help
guide
standards.
Here
I
mean:
do
you
see
this
helping
your
case
with
renewals.
C
Well,
probably,
but
I
think
the
key
thing
here
is
like
as
terry
summers
like
we
have
all
these
really
cool
work
happening
within
cdf,
both
within
the
groups
different
special
telescopes,
as
well
as
the
projects.
C
I
think,
if
you
could
have
this
type
of
effort,
bringing
all
these
developments
in
a
lump
in
one
place,
giving
people
a
you
know
golden
path
or
pivot
road,
while
they
are
moving
to
cd.
That
would
in
turn,
help
the
cloud
providers
or
vendors.
You
know
build
solutions
for.
C
Their
customers
requirements
which,
in
turn
those
organizations,
take
part
in
this
effort.
I
think
this
is
like,
regardless
of
that
topic.
I
think
this
is
a
good
thing
for
communities
both
within
cdf
and
outside
and
projects,
and
you
know
all
types
of
different
participating
organizations
because,
like
even
if
ourselves,
when
we
look
at
what
is
happening
within
cdf,
it
is
sometimes
very
difficult
to
wrap
our
head
around,
because
interop
is
doing
many
things.
Events
is
doing
many
things.
C
Envelopes
has
a
roadmap,
we
are
starting
discussions
in
a
software
supply
chain,
but
it's
very
difficult
to
see
how
these
pieces
could
fit
each
other
well
helping
the
organization.
So,
in
summary,
I
think
this
would
benefit
those
conversations,
but,
more
importantly,
it
would
benefit
us
improving
our
lives.
G
Yeah,
no,
no
doubt
no
doubt
it's
needed.
You
know
I
was
just
you
know.
Terry
just
seen
your
presentation,
I
immediately
thought
of
like
well
hey.
If
I
was
a
a
vendor
of
these
solutions,
I
would
very
much
want
to
seat
at
the
table
for
building
that
reference
architecture,
yeah
and
I
think
that's.
F
H
H
I
only
got
to
see
a
portion
of
it,
so
I'm
coming
in
a
little
bit.
I
guess
you
say
half
knowledgeable
exactly
about
what
we're
talking
about
in
this.
My
biggest
concern,
however,
is
that
we
have
to.
I
think
we
have
to
choose
the
message
we're
going
to
take
to
potential
vendors
and
our
existing
members.
H
We've
been
talking
about
cd
events
being
that
that,
basically,
that
way
for
for
us
to
solve
the
the
old
problem
of
plug-ins
and
interoperability,
and
I'm
I'm
a
little
concerned
about
splitting
that
message,
so
I
feel
like
we
have
to
choose
one
or
the
other
initially
to
get
it
going,
because
I
don't
know
if
we
can,
if
we,
if
we
have
that
strong
of
a
a
messaging
engine
to
try
to
message
around
both
of
these
a
reference
architecture
versus
a
cd
events
where
everybody
is
starting
to
create
an
event-based
cd
process
around
some
some
level
of
cd
event
a
listener.
H
I
know
we
have
standards
out
there
that
we've
been
working
on
in
vocabulary.
We've
been
working
on
it
for
quite
some
time,
so
I'm
just
going
to
put
it
out
there
that
that
that
is
my
biggest
concern
about
your
reference
architect
architecture.
Now,
I'm
not
saying
that
we
shouldn't
do
it,
I'm
just
saying
we
should
choose
which
one
we're
going
to
move
forward
with
and
be
and
have
a
clear
direct
message
from
the
toc.
F
Yeah-
and
I
think
we
we
have
some
pieces
of
work
that
have
you
know,
moved
on
so
we're
freeing
up
some
people's
resources.
So
we
we
will
have
a
little
bit
more
capacity
again
now,
but
also,
I
think,
an
important
part
of
this
is
actually
having
a
conversation
with
a
slightly
different
audience,
so
that
we're
attracting
a
slightly
different
group
to
come
and
contribute
to
the
work
that
we're
doing,
because
right
now,
we've
been
doing
a
lot
of
very,
very
focused
detailed
engineering
work
in
the
conventional
software
pipeline
side
of
things.
F
But
now
what
we're
trying
to
do
is
tie
together
a
lot
more
disparate
pieces
across
software
supply
chain,
conventional
ci,
cd,
machine
learning,
based
ci
cd,
and
that's
that's
focused
on
a
very
different
audience.
So
I
would
expect
that
the
the
bulk
of
what
we've
been
doing-
yes,
very,
very.
F
F
Up
in
the
stack,
which
is
you
know,
how
do
we
deliver
product
assets
in
a
consistent
and
reliable
way
at
the
cadence
that
we
need
to
to
keep
up
with
the
marketplace
as
it's
moving
today,
so
it's
starting
to
engage
with
a
a
new
audience
and
bring
in
people
who
have
a
slightly
different
focus,
and
so
I
don't
think
this
would
detract
at
all
from
the
the
key
work
that's
going
on
on
on
the
engineering
side
there.
Instead,
I
think
it.
H
And
that
the
reference
library-
and
I
I
I
when
I
finally
was
able
to
get
back
on
you
were
talking
about-
is
there
a
reference
to
specific
tools
in
that
reference
architecture.
F
F
F
You
know
the
following
bits
of
the
architecture,
and
so
it
then
becomes
more
of
a
translation
from
that
landscape
view
of
the
projects
to
a
roadmap.
View
of
you
know.
F
Are
today
here's
where
each
of
these
projects
is
intending
to
evolve
to
solve?
You
know
a
broader
set
of
of
challenges
in
that
space
and
and
that
should
help
to
feed
back
into
those
projects
to
help
guide
them
as
to
where
there's
demand
for
different
features,
and
you
know
what
customers
actually
need
coming
next.
H
And
wouldn't
we
be
able
to
do
that
with
defining
events
where
you
fit
where
your
tool
fit
in
from
an
event
perspective.
H
So
that-
and
this
will
be
my
last
question
then-
and
I
know
we
have
other
things
we
have
to
talk
about
so
that
reference
architecture,
then
is-
is
that
a
set
of
data
that
we
can
do
some
level
of
data
science
against?
Is
that
what
you're
suggesting
is
that
reference
architecture.
F
So
really,
what
it's
going
to
be
is
a
set
of
the
the
the
difficult
challenges
that
exist
within
the
continuous
delivery
problem
space.
So
it
it
it's
going
to
be
a
here.
Are
the
patterns
that
you
are
going
to
encounter
at
some
point
in
your
journey
with
continuous
delivery?
F
And
here
are.
The
here
are
the
ways
in
which
people
have
successfully
mitigated.
H
F
H
In
that
in
that
is
that,
if
we,
if
that
reference
architecture
specifically
reference
tools,
we
are
going
to
have
membership
issues.
We,
just
if
we
go
down
that
road,
it
can't
we
can't.
We
have
to
remember
that
we're
trying
to
be
a
vendor
neutral
place
for
cd
of
city
members.
H
So
whatever
that
reference,
you
know
whatever
those
symptoms
are
spitting
out
results
for
particular
tools,
may
not
be
a
good
idea.
It
may
be.
These
are
the
particular
spaces
that
you
should
look
at
to
solve
these
particular
issues,
but
we,
I
would
be.
I
would
push
against
having
anything
that
spit
out
particular
tools
and
vendors
names.
F
So
this
is
this
is
where
what
we've
tried
to
do,
and
we
do
the
same
in
best
practices-
is
that
we
we
have
the
see
the
cdf
view,
which
is
the
technology
agnostic
view,
and
then
we
have
the
the
viewpoint
which
is
based
on
white
papers
or
reference
implementations
that
says,
and
here's
how
x
has
addressed
this
problem
with
their
technology.
F
So
it's
an
opportunity
for
the
the
members
in
the
space
to
show
the
challenges
that
they've
come
up
against
and
how
they've
used
particular
technologies
to
to
address
those.
But
it's
a
it's
that's
equally
available
and
everyone
is
free
to
provide
their
own.
You
know
reference
implementation,
views
of
how
to
leverage
their
tools
and
technologies
or
approaches
to
solve
that
wider
picture
of.
How
do
you
follow
best
practice?.
I
She's
going
to
jump
in
and
say
that,
for
both
what
terry
said
and
some
of
the
concerns
that
tracy
raised,
I
actually
there's
so
much
in
both
that
I
agree
with.
I
think
that,
having
realizing
this
is
really
for
two
different
audiences
and
that,
from
the
cdf
perspective,
like
the
fact
that
we
are
working
on
this
reference
architecture
in
no
way
is
going
to
take
away
from
our
commitment
to
see
the
events
at
all.
I
I
I
wouldn't
see
that
and
that
in
fact,
the
two
can
work
well
because,
as
we
discuss
the
different
problem,
spaces
in
the
reference
architecture
and
some
potential
tools
that
you
can
use
in
those
spaces,
I
think
emphasizing
how
cd
events
can
help
you
write
less
glue
code
and
bring
your
pipeline
together.
Is
a
really
nice
way
to
bring
cd
events
into
that
as
well.
D
J
C
Well,
since
this
is
like
kind
of
a
brain
dump
of
a
few
of
the
community
members,
I
guess
like,
as
noted
on
the
last
slide,
this
topic
could
be
brought
up
to
governing
board
as
a
strategic
topic
which
will
take
place
next
week,
and
then
we
can
gather
feedback
from
governing
board
as
well-
and
I
see
steve
here.
J
So
yeah,
I
think
it
will
be
a
great
topic
to
bring
up
to
the
governing
award.
I
think
robert
actually
raised
a
great
point,
which
is
this
is
something
I
think
which
will
be
really
interesting
to
the
members
as
well,
because
once
we
we
have
a
reference
architecture,
then
that
kind
of
gives
us
something
where
we
can
anchor
and
talk
about
how
we
add
value
to
the
the
continuous
delivery
pipeline,
and
I
think
this
is
something
which
is
much
needed
from
a
thought
leadership
piece.
E
And
I
think
the
only
thing
that,
from
what
I
heard
that
might
be
missing,
is
just
a
good
comparison
and
contrast
between
the
to
tracy's
points
to
what
the
other
sid
groups
are
doing,
so
that
this
kind
of
makes
sense
in
the
overall
scheme
of
things
so
that
there
isn't.
I
think
that
was
a
really
good
sort
of
discussion
and
like
how
is
this
different?
How
does
this
make
sense
and
how
is
it
still
vendor
neutral?
E
B
And-
and
I
one
thing
when
terry
was
cloud-
vendors
came
up
a
lot
and
right
now
I
don't
think
we
have
any
representation
in
the
cdf
from
cloud
vendors,
especially
folks
that
are
working
on
that
are
actually
like
product
managers
for
the
pipeline
tools
like
there,
we
don't
have
somebody
from
google.
That's
representing
you,
know,
google
cloud
somebody
from
github
with
github
actions.
B
I
think,
if
you're
able
to
get
those
cloud
vendors
of
those
product
managers
on
board,
I
think
it'll
give
us
a
lot
more
insight
into
their
direct
and
how
we
can
help
them
with
the
from
from
our
reference
architecture,
standpoint
being
able
to
merge
together.
I
don't
know
how
we
reach
out
to
those
folks,
but
I
think
that's
going
to
be
a
pivotal
part
of
of
what
terry's
been
talking
about.
G
Presenting
them
an
opportunity
to
have
a
seat
at
the
table,
I
I
don't
see
that
thing.
A
tough
ask
my
recommendation
for
the
the
governing
board
governing
board
governance
board.
What
what?
What?
What
for?
What
form
of
the.
G
Governing
okay,
terry,
the
the
challenges
and
the
opportunities
that
that's
that's,
a
solid
slide,
just
laying
it
out
what
what
we're
missing
out.
How
is
this
different
from
the
what
the
six
are
doing
and
just
letting
them
know
that
this
is
an
opportunity
to
bring
it
all
together?
I
imagine
the
gb
would
be.
G
I
don't
know
I've
never
been
to
one
of
those
meetings
you
know,
but
I
imagine
they
would
be
excited
about
that.
To
just
say:
oh
hey,
we've
got
a
project
here
that
that's
in
in
essence,
a
meta
project
and
gonna
tie
all
these
things
together.
I
also
see
it
identifying
areas
that
cdf
is
lacking
and
that
would
be
exciting
for
either
new
open
source
projects,
new
companies
or
for
people
to
add
things
to
their
existing,
offering.
G
I
think
that's
strong
and
and
this
both
of
those
things
encourage
more
people
to
join,
and
I
think
that's
what
we
all
want.
C
C
Assuming
both
toc
and
governing
board
approve
this
initiative.
It
could
be
a
working
group,
for
example.
It
could
be
something
else
and
then
from
there
we
can
start
reaching
out
to.
You
know
commit
members
or
cdf
members
and
highlight
this
being,
kicked
off
and
come
and
join
us.
Would
that
be
a
good
plan
and
also
lori?
Would
that
answer
your
question
about
next
steps.
E
I
think
so
I
think
that's
a
solid
way
to
move
forward,
because
the
discussion
really
pointed
out
some
highs
and
some
some
holes,
and
I
think,
if
you
could
just
update
the
deck
to
kind
of
like
robert
was
saying
show
what's
missing,
like
steven
said,
show
how
this
is
a
thought
leadership
position
for
the
cdf
and
then
also
how
this
works
with
the
sigs
and
not
opposed
to
con
conflicting
with
what
they're
doing
it
brings
it
all
together.
C
F
A
Yeah
so
the
remaining
item
for
us
so
pearson
proposal.
B
Two
weeks
ago
the
pr
was
created
with
the
proposal
there
weren't
any
less
there
weren't
any
comments
directly
on
the
pr,
but
there
was
some.
B
J
So
I'm
here
and
happy
to
answer
any
questions
about
the
the
persia
proposal.
It's
it's
a
vendor
neutral
effort
which
jfrog
is
doing
in
collaboration
with
huawei
who's,
also,
a
cd
member
cd
foundation
member
on
deploy
hub
who's,
also
involved
in
cd
foundation,
docker
oracle.
And
who
am
I
forgetting,
of
course,
we're
open
to
other
companies
contributing
as
well
so
and.
A
J
The
basic
goal
for
what
we
want
to
do
is
improve
software
supply
chain.
So
I
think
this
is
a
really
important
opportunity
for
the
cd
foundation
to
kind
of
leave
a
a
big
mark
in
the
software
supply
chain
security
area,
which,
which
is
something
which
we've
wanted
to
expand
as
a
foundation
into
our
goal,
as
a
project
is
specifically
to
provide
a
a
build
from
source
tool
chain.
J
So
we're
building
that,
on
top
of
other
cd
foundation,
technologies
like
cd
events,
tekton
and
other
technologies,
which
are
part
of
the
cd
foundation,
and
then
on
top
of
that,
we're
we're
building
a
immutable
transaction
ledger
which
will
you
know,
store
all
of
the
different
packages
and
binaries
available
in
the
network.
J
And
the
first
version
of
this
is
targeted
at
the
container
ecosystem.
So,
in
collaboration
with
docker,
we
have
a
prototype
which
allows
you
to
download
images
from
the
docker
official
image
set
so
happy
to
answer
any
questions
about
it.
But
I
think
this
is
a
a
project
which
we're
excited
to
propose
to
the
cd
foundation
and
would
would
welcome
having
a
a
vendor-neutral
governing
body
like
the
cdf,
be
the
permanent
home
for
persian.
J
So
you
mean
in
terms
of
the
the
governance
of
the
persia
project.
Oh
look
yes
yeah!
So
we
we
have
a
draft
for
this
steve
taylor
put
us
together
for
the
for
the
governance
draft,
but
I
think
I
think
it
makes
sense
for
us
to
fit
in
line
with
with
what
other
cd
foundation
projects
are
doing.
So
that's
why
we're
proposing
it
first
and
then
upon
acceptance.
We
would
create
the
similar
sort
of
governance
and
oversight
for
the
project
to
to
meet
the
standards
for
like
what
other
projects
are
doing.
A
B
B
So
is
there
a
way
we
can
move
forward
with
the
vote
on
the
project.
B
That
works
yeah.
If
you
want
to
start
a
vote
thread
on
the
mailing
group.
A
A
J
Then
rushing
the
process
so
doing
doing
a
good
vote
by
the
mailing
list
is.
Is
awesome
we'd
like
to
hear
from
folks
if
there
are
any
questions
here
in
the
meeting
or
or
later
we're
happy
to
answer
them
about
the
the
project
or
or
kind
of
our
goals?
And
what
we're
trying
to
accomplish,
and
I
think
also
it
should
be
some
good
rolling
thunder
as
we
get
towards
the
end
of
the
year
for
more
announcements
and
things
we
can
talk
about
from
a
cd
foundation
perspective.
B
Did
the
new
members
of
the
board
get
added
to
the
toc
mailing
list.
A
H
C
H
C
D
D
C
D
B
A
A
So
the
last
item,
at
our
legend,
the
is
in
your
meeting
time.
So
basically
I
postponed
it
until
the
end
of
the
vacation
period
I
created
doodle.
You
can
find
a
link
in
the
meeting
codes.
I
will
duplicate
it
to
the
chat,
so
the
idea
here
is
so
that
since
we
still
have
some
qc
members
that
are
going
to
join
so
we
can
revise
the
meeting
time
and
if
there
is
no
strong
consensus
for
another
meeting
time,
we
just
keep
the
current
meeting
time.
A
Yeah,
actually,
it
also
raises
the
question
we
had
a
lot
go.
Should
we
start
doing
something
in
the
apac
friendly
time
zone,
maybe
not
every
two
weeks,
but
once
months
or
so,
and
if
someone
is
interested,
let's
talk
about
it
but
yeah
I
created
in
the
poll.
I
also
did
some
morning
european
morning
slots.
C
A
J
A
Hopefully,
we
will
have
some
progress
for
reference
design
for
the
next
week
and
if
any
reviews
needed
just
drop
the
slides
etc
to
the
slack
channel,
so
that
many
maybe
people
could
jump
in
because
even
in
the
current
state
it
should
be
good
enough
to
drop
in
general
so
that
everyone
could
take
a
look.