►
From YouTube: CDF TOC Meeting - 2021-10-26
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
E
B
E
B
Okay,
well
remind
me
not
to
move
to
sweden.
B
G
G
Okay
and
then
I'll
share
my
screen.
I
think
I
need
to
close
this
one.
Okay,
so
ready
to
go
so
today
is
october
26th.
G
So
we
have
a
few
topics
if
you
see
something
missing,
please
just
head
to
the
list,
so
just
quick
news
from
me
yeah,
you
may
have
seen
that
I
left
cloudbees,
so
it's
just
for
your
information
and
nothing
really
changes
in
terms
of
cdf
technical
oversight
committee,
because
I
will
be
still
present
basically
in
the
same
role.
G
My
next
employer
will
also
bucket
with
working
time
and
yeah.
There
will
be
no
change
in
terms
of
well.
My
next
company
is
not
represented
in
cdftc
at
the
moment,
so
we
should
be
fine.
G
So
it's
just
a
very
quick
update,
stay
tuned
for
announcements.
On
november
1st.
B
You're
bringing
in
your
new
employer
as
a
member
right,
no
I'm
kidding,
I
can
neither
can
film
nor
deny
well
you
better
start
working
on
it.
Then.
G
Yeah
yeah,
let's
see
but
yeah,
it's
going
to
be
fun.
F
Yeah
sure,
well,
we
we
are
working
on
the
logo
for
the
cd
events,
so
we
submitted
the
creative
brief
and
we
already
got
back
an
initial
selection
of
logos,
which
is
which
is
great,
so
we're
working
very
iterating
towards
that
and
what
else
we
set
up,
the
as
you
were,
showing
we
set
up
the
the
gita
organization
and
started
creating
some
initial
repos,
but
it's
yeah,
that's
about
it.
G
Yeah
and
for
the
log,
the
task
is
in
the
cd
foundation
github.
This
is
the
foundation
foundation
right.
Yes,.
G
H
I'm
gonna
be
starting
the
working
on
the
proposal
document
and
I'll
do
do
that
as
at
the
same
time
with
creating
a
like
a
template
for
the
proposal,
because
that's
on
my
to-do
list
as
well.
So
those.
G
Yeah
thanks
a
lot,
and
yes
speaking
of
the
on-boarding
flow,
it's
not
in
the
agenda,
but
yeah.
There
is
a
pull
request
from
tracy
about
a
checklist
for
projects
after
the
unimportant,
so
basically
list
of
actions
which
is
expected
to
happen
shortly
after
the
project
is
accepted
to
the
cdf.
E
G
I
No
nothing's
changed
since
then.
I
think
I
accepted
some
of
your
suggestions.
The
only
question
is
whether
you
want
to
get
a
first
version
merged
and
I
can
do
each
one
separately.
Some
of
the
things
will
take
longer
than
others,
but
there's
a
bunch
of
other
bits.
We
can
add
in.
G
Well,
regarding
my
comments,
I'm
perfectly
fine
if
this
checklist
gets
merged,
maybe
with
a
disclaimer
on
the
top
that
it's
work
in
progress
and
yeah.
After
that,
we
can
create
a
github
issues
for
the
remaining
items
because
yeah.
I
understand
that,
for
example,
patent
transfer
topic,
it
might
be
a
few
years
for
linux
foundation
legal
to
make
a
call
on
that.
I
G
If
you
want,
we
can
just
exclude
this
step.
Yeah.
G
Okay,
so
anything
else
to
discuss
regarding
project
onboarding.
G
Then
I
guess
moving
call
so
cdf2c
roadmap.
I
made
a
few
changes
since
the
last
meetings
and
thanks
a
lot
to
cara
for
all
suggesting
the
topics.
G
I'm
getting
I
have
from
somebody
yeah
so
question:
do
we
want
to
formally
accept
it
to
remove
poc
status,
or
do
you
want
to
wait
a
bit
more.
G
Okay,
then,
I
will
just
remove
the
poc
status
and
submit
a
follow-up
request
to
reference
it.
Well,
it
has
been
done
already
so
yeah,
so
basically
we
can
consider
it
as
roadmap,
but
it's
also
a
living
document.
So
anytime
we
see
something
missing.
We
can
just
update
and
I
believe
that
all
tlc
members
have
access
to
this
dashboard,
so
you
can
modify
it.
G
H
You
can
put
me
and
andre
on
it.
G
G
What's
next
ip
policy
for
new
projects,
I
basically
put
it
from
the
backlog,
because
there
is
open
question
whether
we
expected
to
comply
with
ip
policy.
It
was
opened
a
long
long
ago
and
yeah.
Maybe
it's
a
question
to
tracy
and
the
linux
foundation
is
whether
you
want
to
align
or
not.
I
With
cncf,
once
yes
yeah
assign
this
to
me,
oh,
I
will
yeah.
I
recall
this
one
lying
around
in
the
backlog
I
can
take.
It.
G
Yeah,
so
it's
old
tisha.
So
basically
there
are
a
few
particularly
concerning
topics,
for
example:
apache
license
et
cetera.
Well,
it
might
be
reasonable
for
new
projects
but,
for
example,
jenkins
uses
mit.
G
So
if
we
needed
to
change
the
license,
it's
definitely
a
very
long
discussion.
We
need
to
have.
G
Okay,
so
I
have
a
brief
question
yeah.
I
know
that
I
was
supposed
to
start
a
mailing
list
discussion
first,
I
didn't
so.
Basically
the
question
is
about
projects
which
are
currently
not
represented
in
the
technical
oversight
committee,
so,
for
example,
jenkins,
x,
spinnaker
and
who
else
screwdriver
is
not
represented
right
now
to
write
no
screwdrivers.
J
G
Okay,
so
yeah.
Basically,
we
have
two
projects,
plus
there
might
be
projects
outside
of
the
continuous
delivery
foundation
that
would
like
to
have
some
representation,
especially
since
there
will
be
a
lot
of
collaboration
between
projects,
for
example,
open,
telemetry,
cd
events
and
cloud
events,
et
cetera,
et
cetera.
So,
basically,
the
idea
was
to
introduce
a
kind
of
role.
G
Basically,
a
representative
is
more
or
less
nominal
role,
and
this
role
would
be
a
point
of
contact
for
the
cdf2ece
so
that
we
could
reach
out
to
this
point
of
contact
to
discuss
various
project
related
matters
and
vice
versa.
G
They
can
represent
their
projects
in
the
cdf
and
the
in
the
toc,
so
it
would
basically
just
for
communication
purposes,
and
actually
we
have
a
foundation
for
that,
for
example
in
contributors.
I
believe
so.
We
briefly
discussed
it
with
trace.
No,
not
here.
G
G
I'm
not
100
so
somewhere
we
have
a
list
of
tlc
contributors
who
are
not
actually
talk.
Members
I
can
find
the
page
later,
but
yeah.
I
think
that
it
would
be
nice
to
have
something
more
or
less
formal.
So,
firstly,
it
would
highlight
these
representatives
that
we
can
also
easily
find
home
to
contact.
If
there
are
discussions
related
to
projects
we
are
working
on.
I
So,
if
I
can
add
as
well
like
oh,
like
a
alludes
to
it,
was
an
initial
discussion
and
particularly
as
we
set
up
things
looking
a
lot
to
how
cncf
set
them
up.
This
is
also
a
a
borrowed
idea
from
cncf
and
you'll
see.
If
you
go
to
the
cncf
talk
page,
they
explicitly
list
out
the
top
contributors
on
the
website,
and
I
think
it's
been
a
very
effective
kind
of
pool
of
contributors
as
well
as
a
pipeline
of
potential
future
tfc
members.
I
So
I
think
a
couple
of
things
they
do.
They
encourage
like
the
members
to
have
a
talk
contributor
to
to
stay
involved
with
what
the
toc
is
doing.
I
think
there
might
be
some
restrictions
on
kind
of
one
top
contributor
per
company
just
to
make
sure
there's
a
mix
of
different
perspectives,
there's
a
just
how
they've
done
it.
I
G
Yes,
so
if
you
have
a
link,
it
would
be
nice
and
I'm
pretty
sure
that
we
have
it
listed
somewhere,
yeah
toc
contributor,
so
we
even
have
it
documented.
Actually,
we
would
encourage
you
to
pull
the
request
to
tlc
contributors,
which
is
where
oh
yeah
do
you
see
contributors?
So
basically
it
was
the
document
I
was
showing.
I
just
missed
this
text
so
yeah
we
have
this
list.
G
Probably
we
need
to
do
some
update
yeah,
I'm
not
sure
whether
ramen
and
sundeep
are
actively
in
the
community
at
the
moment,
but
he
is
a
member
of
toc,
so
yeah
we
can
do
some
cleanup
but
yeah.
Actually,
our
framework
is
there
yeah.
I
G
H
The
only
thing
I
would
say
is
it
would
like
we're
on
the
ortelia
side,
we're
just
in
the
process
of
creating
our
governance
board
and
it
would
have
been
nice
if
we
would
have
known
that
we
would
have
needed
another
position
as
the
toc
contributor,
if
we
weren't,
if
I
wasn't
there
to
represent
the
ortelius
project,
so
that'll
be
the
only
thing
in
the
onboarding
process
that
we
may
want
to
put
in
there.
H
G
G
Okay,
so
the
moving
corner,
unless
there
are
other
commands
questions.
C
G
G
I
mean
tracy
mentioned
that
there
is
expectation
that
the
linux
foundation
account
would
be
that
as
admin
to
project
organizations
on
github.
So
I
just
wanted
to
know
whether
there
is
any
documentation
for
that.
We
had
a
briefing.
I
F
G
Yeah
because
yeah
I
discussed
the
jinx
governance
meeting,
people
were
not
particularly
happy
about
this
proposal,
so
we
have
something
to
be
discussed.
Plus
the
scope
needs
to
be
understood
because
yeah
we
have
github
organizations,
but
we
also
have,
for
example,
docker
hub
organization
and
zillions
other
accounts,
mailing
lists
etc,
which
are
not
controlled
by
the
linux
foundation
and
assuming
that
something
really
bad
happens
in
the
project
and
everyone
loses
access,
linux
foundation
won't
be
able
to
take
it
over.
G
I
G
G
Us
yeah,
fourth
and
think
it's
somewhat
problematic,
because
we
have
sensitive
information,
for
example,
private
repositories
for
security
fix
security
advisories,
including
pending
fixes
under
testing,
sometimes
for
high
severity
issues.
So
if
we
grant
an
arbitrary
number
of
people,
access
to
this
information,
yeah.
G
C
A
How
are
you
doing?
Yes?
Surprisingly,
it's
me
yeah,
so
just
a
bit,
I
get
a
bit
of
context,
so
I've
since
also
left
cloudbees
hobbies
were
paying
for
the
build
infrastructure
before
I
left
made
sure
that
the
running
costs
were
reduced
to
zero
for
jenkins
x,
ie
yeah.
We
can
take
down
all
of
the
build
infrastructure
and
it
won't
be
affected
jenkins
x.
A
So
all
images
are
hosted
on
github,
that's
free,
because
they're
public
images,
all
helm
charts,
are
posted
publicly
for
free,
but
the
run
it
to
actually
pay
for
the
infrastructure
for
producing
releases.
I've
I'm
now
currently
paying
for
that.
So
the
hope
was
that
maybe
that
could
be
incorporated
somewhat.
I
think
it's.
A
The
running
costs
are
about
four
to
500,
sorry,
three
to
four
hundred
dollars
a
month
at
the
moment,
although
I
still
think
there's
some
optimizations
around
that
that
can
be
made,
and
so
I
just
wondered
what
the
process
might
be
to
start,
maybe
up
or
rolling
if
it's
possible
at
those
kind
of
things.
So
I
don't
know
if
that's
a
suitable
conversation
to
have
here.
I
Yeah
we
have
been
trying
to
just
do
an
audit
of
all
the
infrastructure
side.
That's
been
a
bit
slow
and
just
tracking
down
folks
who
are
involved
with
running
it.
So
it
has
been
a
bit
ongoing
and
I
know
there's
a
few
requests
that
we
haven't
been
able
to
get
back
to
yeah.
I
might
have
to
follow
up
with
you
just
to
get
some
details,
so
we
can
put
that
in
with
the
requests
and
yeah
just
understand
cloud
and
who's
who's
gonna.
I
think.
A
Gcp,
so
google
container
engine
well
there's
actually
two
gcp
projects,
one
for
just
a
bit
of
isolation,
one
to
host
the
infrastructure
and
the
other
one
is
for
testing.
So
we
there's
some
automation.
That's
insert
cluster,
runs
some
tests
and
then
takes
it
down.
So
there's
one
one
cluster
running
in
the
infra.
I
think
that
could
be
optimized
again.
I
looked
at
some
optimizations
earlier
and
they
said
that
this
cpu
that
we
reduced
but
yeah.
I
And
yeah,
I
think
I
was
interested
in
some
of
the
things
you
did
to
save
money.
We
want
to
apply
this
to
the
spinnaker
project,
where,
if
they
can
move
the
downloads
to
github,
that's
a
lot
of
our
current
costs
saved
and
then
yeah
move
those
over
to
other
projects
which.
A
Just
for
a
bit
the
context
there
as
well,
so
we
introduced
with
chatting
before
this,
we
were.
The
costs
were
around
about
five
thousand
dollars:
six
thousand
dollars,
seven
thousand
dollars
a
month
and
the
main
part
of
that
was
because
we
were
hosting
our
images
and
google
container
registry
and
the
main
cost
around
that
was
egress.
So
when
users
are
putting
down
those
images,
we've
been
charged
and
so
by
shifting
over
to
github,
then
that
effect
is
effectively
free
on
that
for
the
hosting.
So
it's
it's
a
massive
saving.
H
Yeah
for
the
artelias
project
and
for
deploy
hub,
we
use
a
quay
if
it's
a
public
image,
it's
free.
So
that's
another
one
to
look
at
and
they're
pretty
stable.
I
like
that
registry
yeah.
C
I
will
say
I
like,
I
think
we
should
use
this
as
an
opportunity
to
document
these
best
practices
to
lower
your
ci
costs.
I
think
that
would
be
a
great
like
you
know.
Blog
post
talk
something
that,
because
yeah
we
are
experts,
these
are
best
practices.
This
is
a
way
to
make
it
cheaper.
I
do
want
to
point
out
that
there
is
no
guarantee
that
ghcr
will
remain
free,
like
docker
hub
was
free.
E
C
It's
not
and
gcr
is,
you
know,
was
cheap,
and
now
it
isn't
so
I
I
would
say
the
the
best
practice
we
should
document
is:
make
it
easy
to
move
your
image
somewhere
else.
Less
less.
To
that,
you
know,
move
to
gcr,
it's
free
because
then.
C
Now
there's
another
fire:
you
know
a
fire
drill
to
move
everything
off
of
ghcr
to
somewhere
else,
but
yeah
aside
from
all
of
that,
I
definitely
think
we
should
cdf
should
take
put
the
bill
on
this
and
not
make
you
personally
pay
for
it
james.
So
if
there's,
I
think,
I
think,
we're
all
in
agreement
that
you
shouldn't
pay
for
this
personally,
and
we
also
I'm
not
sure
what
the
tactical
process
is
for
moving
that
to
something
that
cdf
pays
for,
but.
I
Yeah
and
one
of
there's
a
couple
of
ways
I
know
like.
Let
me
follow
up
with
you,
because
the
the
board
recently
approved
a
like
a
a
general
bucket
of
funds
for
projects,
and
I
think
that's
something.
J
I
Let
you
know
what
that
is.
The
toc
just
needs
to
put
some
guidelines
around
how
projects
can
request
those
funds,
so
this
is
a
short-term
solution
as
well.
You
could
just
reimburse
james
through
that,
but
it
just
needs
some
guidelines
around
making
it
open
and
transparent
for
different
projects
to
be
able
to
put
in
requests
and
account
for
how
they
use
the
funds.
I
G
Oh
looks
like
we
have
another
roadmap,
I
think
okay,
no,
it's
quite
important.
We
actually
have
reducing
infrastructure
costs
or
whatever
on
the
roadmap
already
and
yeah
for
projects.
It's
definitely
important
and
mitigating
project
infrastructure
course.
G
G
Okay,
so
tracy,
if
you
could
add
some
information
about
what
was
discussed
to
this
ticket,
it
would
be
awesome.
I
Yeah
and
just
to
be
clear,
the
the
that
bucket
is
it's
not
necessary
for
infrastructure
cost.
It's
for
anything
like
I
know
a
while
back.
Tecton
wanted
to
create
some
awards
for
the
community,
so
it's
it's
kind
of
a
discretionary
fund,
so
the
trc
just
has
to
decide
what
are
legit
activities
and
what
are
not
or
provide
some
guidelines
to
projects.
G
Yeah,
so
basically
it's
well
a
budget
controlled
by
toc,
for
whatever
project
needs
exactly.
I
G
G
H
Oh,
could
could
you
put
in
a
project
board
just
a
card
for
tracking
the
request
from
james,
so
it
doesn't
get
lost.
G
Okay,
we'll
update
it
later,
but
you
have
one
placeholder.
I
E
E
E
So
we've
cleaned
up
the
landscape
quite
a
quite
a
bit,
but
there's
still
more
to
be
done.
We've
added
a
number
of
projects
and
just
checked
the
data
on
some
of
the
projects,
and
the
goal
of
this
is
to
to
make
the
landscape
a
little
more
thorough,
a
little
more
encompassing.
E
But
now
what
we
would
like
to
do
is
we'd
like
to
re-examine
the
categories
that
are
on
the
landscape.
We
feel
that
they
either
could
be
further
refined
or
edited
in
some
way
that
fits
how
the
cicd
ecosystem
has
evolved
and
also
how
we're
considering
it,
and
so
this
process
of
categorization
of
re-categorization
is
actually
ongoing
right
now,
so
you
can
open
an
issue
on
the
repo
for
the
landscape,
saying
a
category
that
you
think
anything.
E
You
want
change
with
categories,
one
that
to
add
one
to
rename
one
to
take
out,
although
that
is
fair
game.
If
you
would
like
to
add
a
project
to
the
landscape,
you
may
do
so
by
pr.
You
can
just
you
don't
have
to
raise
an
issue
for
that.
Just
directly
raise
the
pr
and
in
the
category
you
think
it
should
be
in,
but
the
the
ongoing
category
discussion,
I
think,
is
quite
interesting
because
it
really
will
relate
to
how
the
cdf
sees
the
ecosystem
and
how
we're
presenting
it
to
the
wider
community.
E
So
we
definitely
want
to
get
it
right
and
we
definitely
want
a
lot
of
projects
represented.
Currently,
we
are,
as
with
the
cncf
landscape,
enabling
one
card
on
the
on
the
landscape
per
project
or
company,
but
that
too
may
evolve.
That,
too,
is
up
for
discussion,
but
that
will
color
a
little
bit,
how
we
think
about
the
categories
but
feel
free
to
weigh
in
on
that
and
for
refining
the
categories.
E
You
know
in
all
of
the
same
mind
and
have
a
very
good
sense
of
how
this
should
evolve,
and
it
will
only
be
one
or
two
meetings
so
I'll
be
sending
around
a
doodle
poll
for
setting
up
the
best
time
and
anyone
who
would
like
to
be
involved
we'll
be
announcing
it
more
details
and
by
all
means
you
all
are
invited
to
be
involved.
I
would
like
all
of
your
input
so
look
forward
to
that
next
month.
I
Yeah
and
if
I
can
just
add
some
things
as
well,
so
I
was
super
thrilled
to
have
cara
coming
in
and
just
refreshing.
It
and
she's
done
a
lot
of
work
on
the
guidelines
as
well.
To
just
make
sure
it's
clean
and
up-to-date
and
just
getting
a
refresh
cdf
is
seeing
the
landscape
as
as
a
strategic
asset,
and
we
want
to
grow
it
and
evolve
it.
I
So
that
being
said,
this
group
that
cara
will
spin
out
as
a
working
group,
we
expect
that
will
be
landscape
contributors
and
folks
involved
in
the
discussion,
and
I
guess
I
want
to
be
explicit
that
we're
not
seeing
the
landscape
as
a
direct
thing
that
the
talk
looks
after
and
maintains,
but
it's
more
focused
on
the
talk
or
the
end
user
council
or
anywhere
can
like,
can
evolve
to
to
be
contributors,
but
for
now
cdf
stuff
will
be
doing
that
along
with
folks
who
have
traditionally
contributed.
I
So
I'd
say
you
know:
steve
taylor,
tracy
reagan,
tara,
hernandez
and
marky
jackson,
but
we'll
try
to
set
up
a
path
for
people
to
review
and
contribute
and
grow
as
contributors.
If
that
makes
sense
and
a
key
thing,
we
want
to
work
on
as
well.
I
don't
know
if
folks
have
seen
the
recent
cncf
landscape
and
I'm
pretty
keen
to
get
this
in
is
they've,
provided
a
new
guide
element
and
it
also
links
to
each
category,
and
I
think,
that's
key-
that
we
document
the
landscape
and
particularly
for
new
folks
to
the
community.
I
G
For
instance,
here,
for
example,
there
is
serverless
members,
so
they
started
breaking
down
the
landscape
at
least
a
bit.
So
do
you
plan
to
do
similar
things
yeah,
so.
I
We
do
we
do
have
members
already
and
for
the
other
landscapes,
for
instance,
our
steve
chin
started
a
conversation
with
cncf
about
like,
should
we
consider
the
cdf
landscape
as
something
that
could
replace
the
cicd
box
on
the
cncf
landscape,
the
early
stages
of
that
we
just
did
a
reciprocation,
so
they
put
our
landscape
on
their
one
and
we
put
their
landscape,
but
we're.
I
So
it's
a
bit
lost
there,
but
we're
trying
to
find
a
path
to
its
closer
collaboration
with
not
just
cncf
but
potentially
other
foundations,
because
there's
a
a
whole
world
of
them.
But
for
now
there's
been
no
talk
of
serverless.
I
know
cncf
have
that
little
serverless
one
but
yeah
open
to
ideas
and
suggestions
for
this.
I
I
D
I
But
yes
steve
if
you're
interested
we
can.
I
can
point
you
at
just
the
issues
with
you
and
see
if
I've
done
it
and
cara
for
the
let's
spin
up
that
working
group,
so
we
can
deep
dive
into
those
things.
E
In
terms
of
the
cut
the
guide
write
up
that
we
have
so
far
by
tracy
reagan,
which
is
great,
but
the
categories
don't
exactly
map
to
the
ones
we
have
from
what
I
could
see
so
that
might
need
a
little
refining.
E
Basically,
it
might
need
a
little
work
on
the
wording,
and
then
we
can
put
the
certainly
put
the
guide
up
steve
if
you
want
to
be
involved
in
that,
I
would
love
that
and
for
anyone
else
actually
do
you
all
think
that
we
can
make
it
quite
public
we
could
make.
You
know
we
could
put
it
up
as
a
doc
on
the
repo
and
or
an
issue
or
a
discussion
board
and
discuss
it
really
openly
and
people
could
add
what
they
think
or
may
pr's
to.
That.
I
I
think
you
have
to
set
up
the
if
we
do
that
working
group.
Let's
get
folks
in
the
room
and.
H
I
Yeah
yeah,
I
think
I
think
like
even
though
the
categories
might,
I
think,
there's
a
good
amount
there
and
there's
also
complementary
work.
That's
happened
in
the
best
practices
group,
a
lot
kind
of
tying
in
the
y.
So
if
we
just
pull
those
together,
I
think
we
should
have
a
good
first
version
to
put
a
stake
in
the
ground
and
then
just
let
people
come
in
and
yeah
just
we
can
yeah
just
open
up
discussions
or
prs.
E
I'll
I'll
forward
you,
the
write-up
by
tracy,
that
that
we
have
so
far
you
probably
have
it,
but
just
to
make
it
easy
to
hand
for
you.
G
Okay-
so
I
guess
that's
it
for
today,
or
would
you
like
to
discuss
anything
else.
G
H
I
I
But
so
north
america
changes
what
on
the
31st
and
on
the
first
and
europe
on
the
seventh.
So
we
should
be
fine
by
then.