►
From YouTube: CDF TOC Meeting, October 11, 2022
Description
Regular CDF TOC Meeting. There we discussed the Tekton incubation status, and confirmed public voting. Then, the status of Pyrsia incubation was reviewd. We also discussed the TOC composition and the events in the projects: Hacktoberfest, CDF Summit.
A
A
Okay,
so
we
have
Tipton
deletion,
update,
TLC
composition,
discussion
to
follow
up
on
the
previous
meetings,
then
boarding
process,
Oktoberfest
status,
website
refresh
and
CD
pipeline
series.
So,
let's
start
from
the
first
item,
so
click
on
graduation
update
for
that
we
actually
had
a
number
of
items
last
week.
So
last
week
we
did
a
kind
of
out
of
order
meeting
for
the
TLC
where
we
discussed
what
needs
to
be
done
and
just
to
summarize
the
status
for
those
who
missed
the
meeting.
A
The
intent
is
to
reach
a
decision
by
kubecon
Detroit,
preferably
one
week
before
that,
so
that
the
CDF
and
the
stakeholders
can
do
all
the
marketing
things
to
make
it
happen.
Actually
there
is
a
number
of
things
that
needed
to
be
done
as
we
discussed
at
the
last
meeting.
So,
for
example,
there
was
some.
There
are
many
issues
in
governance,
documentation
also
in
adopters
listing
and
open
ssf
best
practices.
What
is
important
and
what
is
discussed?
A
We
discussed
last
meeting
that
we
don't
consider
openness
of
best
practices
as
a
show
stopper
to
start
the
graduation
process.
There
are
a
few
reasons
for
that,
so,
firstly,
all
key
components
of
techtone
are
already
addressed.
There
are
some
peripherals
and
deliverables,
but
none
of
them
is
considered
the
blocker,
as
we
discussed
at
the
previous
meeting
and
the
previous
items
like
governance,
documentation
and
adopters
they're,
quite
small
and
could
be
addressed.
So
this
is
where
we
basically
stopped
at
the
previous
meeting
and
I
guess
Andrea.
B
Then
we
have
the
list
of
criteria
here
in
the
pr
so
starting
with
the
first
one.
So
for
each
criteria.
Basically,
you
have
the
definition
of
the
criteria
and
the
evidence
for
why
I
think
this
is
met
so
governing
board.
This
we
discussed
already
last
week
and
so
just
put
the
list
and
link
to
the
documentation
in
terms
of
C2.
We
made
some
some
progress,
and
so
there
are
three
of
the
release
documents
that
are
still
in
progress
and
the
remaining
ones
have
been
merged.
B
So
I
hope
this
will
be
completed
well,
probably
not
today,
but
yeah,
and
then
today's.
Hopefully
we
will
finish
with
this
C3
committers
around
two
arcs.
This
was
already
discussed
and
agreed
governance
in
contributing
the
same
for
C5.
I
marked
these
as
completed
now
so
for
evidence.
In
terms
of
end
users,
I
put
the
link
to
solarwind
Keynote,
where
they
explain
how
they
use
stackton,
and
also
we
have
these
new
adopters
files
in
the
community
with
a
few
adopters,
several
open
source
projects
in
terms
of
vendors
and
and
users.
B
That
I
wanted
to
mention
that,
in
terms
of
end
users,
at
IBM,
tecton
is
used
as
a
basis
for
API
Cloud,
broadly
adopted
internal
desktop
pipelines.
So
this
is
used
by
a
number
of
development
teams
within
IPM,
and
so
it's
is
not
a
small
implementation
so
like
this
is
a
hopefully
together
with
the
solar
wind
enough
to
to
meet
the
requirement.
But
we
know
that
there
are
other
end
users
we're
just
going
to
the
process
of
it
having
them
added
to
to
this
list
yeah.
B
So
usually,
there
is
a
little
bit
of
legal
checks
and
process
that
company
have
to
do
before,
adding
the
their
name
in
the
list.
So
that's
why
it's
taking
a
bit
longer,
like
I,
said
from
my
point
of
view,
I
think
already
soloing
implementation,
IBM
implementation
would
be
enough,
but
yeah,
of
course,
I
remit
too.
B
What
the
DLC
says
in
terms
of
best
practices.
Also,
we
had
very
good
progress
now,
five
out
of
six
projects
they
are
passing
and
the
last
one
is
on
the
94
percent
yeah.
Sorry,
just
a
few
final
bits
that
I
couldn't
get
through
until
today's
presentation.
But
hopefully
this
will
be
finished
by
tomorrow.
C
B
Yeah,
so
these
are
the
two
that
we
discussed.
Sorry,
this
is
Martha's
work
in
progress,
but
I
need
to
update
the
pr
to
put
the
link
in
here
and
security
audit
as
well,
and
so
the
remaining
ones
just
to
summarize
is
the
last
bit
here
for
the
best
practices
and
the
last
three
previous
file,
documentation
for
trigger
chains
and
CLI
and,
of
course,
the
vote.
So,
as
you
mentioned
all
like
my
proposal
here
for
today
would
be
to
start
the
vote
today.
A
A
D
A
So
it's
generally
a
recommendation.
We
try
to
follow,
for
example,
for
Jenkins,
but
for
CDF
it's
not
a
requirement
which
is
I,
don't
want
to
create
additional
obstacles,
just
trying
to
understand
what
we
miss
if
we
start
devoting
right
now.
So
basically,
it
gives
one
week
approximately
to
make
a
decision
and
to
give
a
feedback.
A
E
A
Yeah
so
yeah,
basically
what
they
suggest.
So
we
set
an
explicit
deadline
for
any
public
commands
and
votes
next
Tuesday,
so
basically
well
October
17th,
so
it's
basically
next
Monday.
So
the
date
we
discussed
last
week
but
yeah.
Even
if
you
reach
super
majority,
let's
say
tomorrow
we
don't
call
a
decision
until
Monday.
D
C
D
A
You
know
it's
totally
have
at
least
a
whole
week,
so
for
me
it's
just
yeah.
We
all
have
to
expedite
the
decision,
but
to
fit
the
timeline
required
for
kubecon,
but
I
think
that
at
least
some
basic
time
frame
should
be
given,
because
even
if
you
were
vote
on
Thursday,
it's
48
hours
to
provide
feedback
which
is
in
open
source
decisions,
is
actually
really
really
short
time
frame.
D
A
B
A
B
E
B
They're
working
on
them,
and
so
clickers
is
the
pr
is
actually
up,
but
it's
not
merged
yet
in
Chains
and
CLI
and
they're
working
in
progress
and
the
yeah.
The
operator
is
also
a
prior
to
the
reaper
to
to
fix
yeah
something
but
yeah
that
should
be
hopefully
finished
at
the
end
of
tomorrow.
That's
my
current
Target.
E
A
B
E
A
F
Okay,
Tom
I'm,
still
relatively
new
I,
just
wanted
a
clarification
on
that.
How
often
does
that
happen?
How
often
do
we
get
I
I,
see
value
in
listening
and
and
certainly
being
inclusive
and
saying
hey.
We
do
want
to
hear
you
know,
criticism
and
thought,
but
in
in
your
experiences
this
happened
before.
A
F
A
Yeah
Moses,
okay
yeah,
so
given
that
stick
to
an
already
has
a
lot
of
vendors
participating
contributors.
So,
for
example,
one
of
expectations
would
be
that
when
we
started
this
threat
for
graduation
that
these
vendors
would
wait
in
and,
let's
say,
share
their
opinions,
statements
that
I
needed
for
data
anyway
or
maybe
if
there
are
vendors,
who
are
not
completely
happy
about
the
current
project,
State
and,
of
course,
you're,
going
to
see
some
big
changes
before
it's
graduated.
They
can
also
back
in
say
that
a
year
too
fast.
F
F
Thank
you
for
pushing
it
you're
battling.
Thank
you
very.
Very
much
I
had
a
wonderful
conversation
with
a
tecton
user
yesterday
and
showing
me
how
they
wired
it
up
with
liquid
base,
and
it
was
the
coolest
thing
and
they
just
wouldn't
shut
up
about
how
great
it
was.
How
great
tecton
was
like
trying
to
move
that
conversation
they
kept
talking
about
it.
I
also
pointed
them
at
adopters.md,
so
hopefully
they'll
add
themselves.
A
A
G
A
discussion,
as
you
know,
we
have
been
working
with
many
things
within
CDF
to
you,
know,
revive
the
community
like
make
increase
our
communities
usability
and
so
on
and
fix
some
of
the
things
that
cause
difficulties
for
our
communities
in
commit
in
the
past,
like
transparency
and
so
on.
And
while
we
are
working
with
these
things,
we
notice
there
are
some
gaps
within
our
Charter
like
when
it
comes
to
like
governing
board
chair
term
or
TLC
chair
term.
G
There
is
information
there,
but
they
are
not
very
clear
or
explicit,
and
they,
in
addition
to
that,
we
are
working
on
rebooting,
our
Outreach
committee
as
well,
to
allow
more
participation
in
our
Outreach
committee,
and
while
I
was
thinking
that
I
said
like,
maybe
we
should
look
at
Toc
composition
as
well,
because
when
this
Charter
was
written,
we
had
six
projects
in
CDF.
Why
I'm
not
mistaken
and
the
charter
states?
There
are
nine
C's
in
the
TOC,
but
in
two
weeks
we
will
have
our
ninth
project
joining
the
CDF
Persia.
G
So
from
six
to
nine,
that
may
require
us
to
have
a
conversation
around
a
number
of
seats.
We
have
within
the
TOC,
currently
nine
and
a
number
of
projects
is
currently
four
and
these
two
things
I
would
like
to
hear
your
opinion
about
it,
because
we
are
currently
working
with
the
legal
team
to
propose
some
updates
to
the
Charter
about,
like
Outreach
committee
and
governing
board,
and
if
Chelsea
things
we
can,
you
know,
think
of
increasing
number
of
assists
within
POC
or
increasing
number
of
projects
in
the
TOC.
G
Then
you
can
include
those
updates
into
Charter
as
well
and
last
third
point
there
is.
We
are
also
trying
to
bring
these
different
communities.
We
have
within
the
CDF
like
art,
which
Community
Tech,
Northside,
Community
and
muscle
program,
so
these
different
groups
could
work
closely
with
each
other
and
the
third
item
there
stays
that
ambassador
program
share
could
become
an
onwarding
member
to
the
TOC,
and
these
are
like
three
questions
from
our
side,
saying
with
the
TOC
like
to
discuss
increasing
a
number
of
the
seeds.
G
A
Secondly,
yeah
is
something
that,
for
me,
I
would
rather
say
it's
rather
insurance
that
there
is
some
continuity
in
the
role
so,
as
I
said
before,
I
will
step
down
next
August
and
yeah,
taking
the
current
situation
in
the
world
yeah.
So
last,
two
weeks
ago,
I
just
forgot.
There
is
a
meeting
at
all
because
I
was
occupied
with
other
things,
so
basically
having
a
kind
of
Coach
here
or
coaches
who
are
basically
studying
the
things
who
have
all
the
permissions
who
can
have
the
meetings
on
demand
would
be
quite
important
and
yeah.
A
It
doesn't
have
to
be
even
a
single
person,
it
might
be
every
TLC
number
one
kind
of
rotation
basis.
For
example,
there
is
no
need
to
just
me
share
the
meetings.
Everybody
can
do
that
everybody
can
take
meeting
notes
Etc.
So
basically,
this
is
the
topic.
I
would
definitely
suggest
to
discuss
so.
Firstly,
Insurance
everyone
has
permissions
and
ensuring
that
we
have
continuity
and
the
bus
Factor
bigger
than
one
at
the
moment.
D
Yeah
I
think
adding
a
a
co-chair
would
definitely
help
distribute
the
burden
of
managing
the
the
TOC
and,
like
you
said,
if
one
one
person
can't
make
it,
then
the
other
person
can
jump
in
and
stuff
like
that.
I
think
just
it's
going
to
give
overall
a
better
consistency
in
the
TOC
having
a
a
chair
and
a
co-chair.
F
G
A
question
about
this:
before
we
move
we
can,
and
we
should
perhaps
document
this
in
our
Charter.
It
says
talk
to
him.
Now
we
can
say
talk
to
another.
Chelsea
is
chaired
by
a
chair
and
a
co-chair
elected
from
within
qlc,
and
now
we
are
in
this
interim
period,
obviously,
and
thanks
Steve
for
stepping
up
maybe
next
time
this
could
be
an
election
as
well
like
to
see
chair
culture
election
together,
for
example,.
A
Yeah,
so
basically
it's
supported
that
you
see
to
sort
it
out.
You
can
define
a
new
process
as
we
wish.
So
it's
not
a
wide
election
in
the
community.
Yeah
yeah
yeah,
so
I
agree
that
we
need
a
chat
update.
So
basically
how
I
would
approach
it
so
submit
to
the
quest
is
Chatter.
I
can
probably
take
it
out
there
for
somebody.
Somebody
else
yeah.
G
G
A
A
F
I
would
hope
so
because
I
I
and
and
I
Steve
volunteered
and
now
I'm
gonna,
lay
out
my
expectations
you
might
want
to
unvolunteer.
I
would
hope
that
this
is
chair.
This
is
on
the
job.
Training.
I
would
hope
that
this
is.
Let's
understand
the
role
Let's
help
out
our
chair.
Let's
carry
the
you
know,
share
the
burden
with
the
intent
that
you
know
with
experience
that
it
would
be
a
shoe-in
for
chair
I
mean
certainly
up
for
election
and
those
sorts
of
things
I,
like
continuity,
I'm.
A
big
fan
of
that
so.
A
F
F
C
C
C
E
E
We
were
trying
to
stagger
the
transition
of
people
so
so
that
we
we
never
had
a
complete
change
at
one
point
and
then
that
loss
of
institutional
knowledge,
so
I'm
just
wondering
whether
this
is
one
of
those
examples
where
having
to
equal
co-chairs,
but
two
elections
at
different
periods
would
make
more
sense
from
a
from
a
risk
management
perspective
rather
than
electing
both.
At
the
same
time,.
G
Of
that
an
interesting
situation,
because
the
TLC
chair,
the
term,
is
for
one
year
and
that
you'll
see,
if
you
think
about
co-chairs
two
people.
For
example,
if
we
say
that
the
OC
chair
is
currently
elected
during
July
and
gets
seated
during
August
and
the
POC
elections
happen,
hiding
in
May
April,
depending
on
the
end
user
versus
project,
so
the
co-chair
may
not
get
re-elected
because
you
know
it's
one
year
term
that
may
make
that
co-chair.
Not
member
of
TLC.
C
C
A
Yeah
so
I
guess
that
brings
up
a
question
to
the
Linux
Foundation
legal
again,
because
while
every
Foundation
is
far
more
independent,
so
there
is
a
kind
of
legal
framework.
Another
foundational
who
didn't
be
happy
to
handle
40
different
chapters,
so
yeah
I
think
we
can
bring
up
ideas
and
see
what
they
say:
yeah
I'm
in
favor
of
having
to
coaches.
G
I
think
like,
if
you
look
at
the
charter,
it
doesn't
State
how
the
election
should
be
done.
It
just
says
Alex
annually,
so
the
election
process
is
like
TLC
can
say:
we
want
to
run
this
type
of
election
process
and
it
adheres
to
what
is
documented
in
the
charter.
So
as
long
as
that
chart
that
is
attaining
to
chartered
I
think
it
should
be
fine,
but
we
can
ask
this
question
to
Legal
people
to
see
if
they
have
any
issues
with
it.
A
G
C
A
We
have
several
topics
but
yeah.
We
can
just
finish
stock
composition
quickly.
Let's
say
10
bucks
it
to
five
minutes
and
then
once
through
other
topics,
Yeah.
So
basically,
two
question:
three
questions:
number
of
seeds,
number
of
project
seats,
a
number
to
the
program
share
so
phone
number
of
seats.
For
me,
one
of
the
biggest
concerns
and
number
of
project
seats,
because
we
have
only
four
and
right
now
we
already
have
potential
issues
so
more
projects.
A
A
A
B
And
also
I
think
I
mean
the
TOC
meetings
are
open.
If
people
from
protest
wants
to
to
join
in
and
contribute
their
votes,
I
think
they
I
mean
they
will
not
get
the
binding
vote
if
you're
not
on
the
DLC,
but
I
mean
as
we're
discussing
earlier
I
mean
we
listened
to
everyone,
opinion
and
ideas.
If
they
come
on
the
meeting,
so
I
yeah
I'm
not
sure
we
need
to
match
the
number
of
projects
to
the
number
of
seats.
G
Ignore
this
point:
until
we
do
the
you
know
the
chair,
coach,
everything
and
if
it
makes
sense,
I
can
open
up
an
issue
in
Toc
repo
we
kept.
We
can
have
conversation
there
like,
as
I
said,
we
don't
have
to
decide
or
come
up
with
a
number
right
now.
I
just
want
to
highlight
this.
We
are
doing
this
work
and
just
want
to
give
you
a
chance
to
start
thinking.
A
It's
a
bit
complicated
because
we
have
TSC
consisting
of
three
ways
for
getting
into
the
t0,
so
we
have
end
users,
which
is
not
exactly
well.
There
are
not
so
many
end
user
companies
in
the
CDF
right
now,
then
we
have
gone
important,
pointed
seats
and
then
we
have
project
seats,
so
we
can
perform
exists
but
I'm
not
sure
about
others.
E
But
for
each
of
those
we're
accepting
nominations
for
those
positions,
so
should
should
we
start
to
record
that
data
and
then
use
that
to
inform
this
decision
in
the
future?
So
so
we've
got
a
better
picture
of.
You
know
what
the
demand
is
in
which
areas
and
and
then
use
that
to
to
help
inform
the
decision.
G
A
And
there
is
one
another
bullet
remaining,
because
ambassador
program
chair
is
not
working
member.
So
basically
we
had
a
quick
conversation
before
he
was
fatigue.
So
for
that
my
feedback
that
we
have
two
c
contributors
and
again
right
now,
I,
don't
see
what
would
be
the
benefit
of
a
non-voted
member
entity
to
the
TOC.
Maybe
we
should
approach
in
another
way.
It's
updating,
chat
bombers,
the
program
chair
to
be
responsible
or
to
delegate
responsibility
to
participate
in
the
two
symmetic
as
TLC
contributor.
G
E
A
G
This
will
be
pretty
fast
because
we
are
nearly
done
with
onboarding,
so
the
you
know,
slack
Channel
and
Google
Calendar
meetings
listed
there
and
so
on
those
Community
things
have
been
done
quite
some
time
ago
and
as
of
yesterday,
the
project
contribution
agreement
was
sent
to
the
contributing
organization,
and
we
expect
that
to
be
signed
during
this
week
at
latest.
It
will
be
signed
before
CD
summary
and
we
are
working
on
at
press
release
in
collaboration
with
again
contributing
organization
and
Oleg
I
will
come
to
you
about
that
press
release.
G
A
G
Something
else
I
think
this
limited
liability,
company
or
LLC
formation.
That
is
what
is
taking
some
time.
This
person
will
be
admitted
as
this
LLC
entity,
and
there
is,
you
know
what
is
called
a
template
agreement
and
then
that
was
sent
to
the
contributing
organization
and
there
were
feedback
for
that
sole
update,
legal
updates.
You
know-
and
that
was
that's-
why
it
took
longer
than
usual.
G
So
it's
like
this
Delaware
Corporation,
whatever
things
you
know
yeah,
so
it's
and
also
Persia
project
is
adopting
a
QRC
chart.
Result
that
was
part
of
this
onboarding
I,
believe
sutindra
presented
this
to
Persia
project
Garland's
body
and
that
will
be
include
or
put
up
in
their
repo
story.
So
multiple
things.
G
A
C
A
A
Which
is
cool,
so
we
definitely
have
some
in
rankings,
though
it's
a
bit
difficult
to
track
across
the
organization
last
time
magic.
There
was
something
like
10
inch
pull
requests
explicitly
a
reference
in
Oktoberfest,
but
yeah.
You
never
know
because
for
participating
projects
you
need.
You
need
a
contributors
to
be
explicit.
B
But
so
the
question
is:
is
that
budget
still
there
to
span
and
also
I
mean
we?
We
have
the
idea,
but
we
don't
have
someone
to
actually
go
and
do
it.
So
is
that
something
that,
from
CDF
point
of
view,
do
we
have
some
channel
to
find
someone
who
would
be
able
to
do
that?
Or
is
that
something
that
we
need
to
drive
ourselves
as
a
project.
G
Please
reach
out
to
Liam's
Foundation
creative
team
to
see
if
they
like
could
help
with
that,
but
it
also
depends
on
the
budget
like
10K
if
I
am
correct,
so
we
have
this
that
are
like.
If
you
want
I
can
ask
this,
but
you
need
to
provide
input
like
how
it
should
look
like.
Then
they
can
scope
the
work
and
tell
us
this
costs
this
match,
or
this
can
be
done
this
in
this
period
of
time.
A
B
G
So
I
added
that
topic,
because
today
the
first
episode
of
the
new
series
got
published.
This
is
like
Lori,
Michelle
and
Roxanne
they've
been
working
a
lot
with
the
tech,
strong
TV,
and
this
complete
new
series.
Like
you
remember,
we
had
this
podcast
like
the
pipeline
podcast,
which
we
are
not
running
anymore,
and
this
conversation
started
around
August,
I.
Think
since
August
we
had
been
working
on
getting
this
making
this
a
reality,
and
now
it
happened.