►
From YouTube: CDF TOC Meeting - 2021-12-07
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
A
A
A
A
A
Yeah
yesterday
there
was
civ
events
meeting.
We
discussed
the
follow-up
action
items
because
there
were
some
agreements
reached
at
the
previous
meeting
like
having
roadmap
and
going
through
the
boston
boarding
checklist.
So
all
of
that
will
be
handled
and
as
we
discussed,
we
target
public
announcements
in
january
or
february.
A
B
A
Yes
of
public
cdf2c
roadmap
is
basically
done.
We
probably
need
to
do
some
announcements,
but
otherwise
it's
completed.
Icd
events
is
incubating
project.
It's
completed
on
the
cdf2c
side.
The
challenge
is
rather
these
cdf
sites
in
general,
because
you
need
to
have
the
website
updated
and
other
things,
but
it's
basically
nothing.
We
can
do
about
that
as
cdftvc.
A
I
think
we
can
handle
that
a
little
closer
the
ticket
later
so
joining
the
inclusive
naming
initiative.
I
joined
a
few
calls
last
week
this
week.
I
got
a
response
that
the
inclusiveness
initiative
board
would
take
a
look
at
the
issue,
but
so
far
there
is
no
feedback,
I'm
not
sure
whether
everyone
has
access
to
system.
When
we
submit
enrollment
lfx,
we
are
basically
stuck
there,
but
we
cannot
do
anything
on
our
side.
A
A
A
C
A
Detection
is
much
bigger
than
captain
in
terms
of
the
size
in
terms
of
adoption
and
community
impact.
So
let's
see
what
I
know
that
there
are
other
projects
like
open,
telemetry
waiting
in
the
queue
from
what
I
understood
from
the
cncftc
meeting
and
for
them
it
goes
already
over
here
in
terms
of
time.
A
C
A
A
A
C
A
C
A
A
A
We
briefly
discussed
it
and
then
basically
stayed
somewhere
on
the
future
on
the
roadmap.
So
I
was
just
thinking
about
budgets
and
remembered
about
this
item
so
yeah.
Basically,
we
can
do
many
things
we
can
just
designate.
The
project
needs,
invest
in
some
technical
programs,
donate
it
if
needed,
maybe
run
effects
mentorship
steep.
And
if
you
want
to
do
something
on
the
qc
level,
we
can
even
print
stickers
for
10k.
If.
A
A
A
If
there
are
any
expenses
like
that
in
our
other
projects,
for
example,
in
jenkins,
we
still
have
some
items
like
some
of
our
domains
are
not
owned
by
the
linux
foundation.
They
are
owned
by
individuals,
but
we
cover
these
costs
from
the
jenkins
project
budget,
basically
from
donations
we
receive,
but
if
there
are
examples
for
other
projects,
when
basically
individual
contributors
have
to
pay
and
for
me
it
seems
to
be
a
natural
first
step.
B
C
B
A
B
A
A
Another
thing
we
could
do
is
probably
lfx
mentorship.
So
let's
say
we
have
cd
events
as
a
new
project,
so
maybe,
as
you
see,
we
could
allocate,
let's
say
stipend
for
whatever
intern-
to
work
on
this
project.
Let's
see
on
documentation
basically
on
whatever,
but
the
question
is:
if
we
do
something
like
that,
would
we
have
somebody
to
mentor
and
whether
it
would
actually
help
this
project.
C
C
A
So
maybe
I
will
propose
it
in
the
same
voting
because
yeah
lampa
bonus
to
project
budgets,
it
kind
of
seems
interesting.
At
the
same
time,
not
all
projects
have
budgets
at
all,
so
it
wouldn't
be
a
kind
of
fair
distribution
and
how
to
distribute.
Failure
is
also
a
wide-open
question,
so
I
wouldn't
really
do
that
yeah.
We
could
also
dedicate
it
to
travel
grounds,
but
we
have
no
idea
whether
the
next
cd
will
be
in
person
or
not,
so
it
also
doesn't
seem
to
be
in
between.