►
From YouTube: CDF TOC Meeting - 2021-11-23
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
E
Yeah
inclusivity,
just
like
we
have
the
code
of
conduct,
we
should
maybe
have
a.
D
Document
around
that,
speaking
of
that
yesterday
at
event,
we
discussed
updating
to
contributor
covenant
discussion
and
maybe
it's
something
we
could
just
put
on
the
agenda
because
it's
totally
aligned.
D
Sorry
so,
basically
yeah
what
we
can
discuss
it
when
we
reach
this
topic,
but
yeah
our
code
of
conduct
is
dated
and
it
doesn't
cover
the
entire
community
and
some
extent
it's
a
problem
because.
D
F
D
Okay,
let's
just
continue
now
so
for
that
yeah.
What
is
our
situation
that,
if
we
use
a
very
old
version
of
contributor
covenant?
Well
not
very
old,
but
it's
version
1.3,
I
believe,
and
the
modern
version
is
2.1
and
they
were
drastic
changes
between
the
version.
1.X
and
2dx
mostly
focused
on.
D
The
scope
of
conduct
so,
first
of
all
now
it
focuses
on
communities
not
on
projects
and
this
difference,
and
it
also
covers
all
community
channels
and
community
venues,
including
conferences,
meetups,
social
media,
etc,
and
it
includes
a
lot
of
changes
among
our
standards,
including,
for
example,
inclusivity
on
the
community
examples
of
an
acceptable
behavior.
It's
not
what
is
listed
in
the
contributor
covenant
officially
used
by
the
continuous
delivery
foundation
and
when
we
were
adopting.
D
When
we
were
updating
code
of
conduct
in
jenkins,
we
decided
that
we
actually
take
the
most
recent
version
at
this
time.
Version
2.0,
because
it
was
a
major
concern
of
our
for
us,
so
that
the
code
of
conduct
of
the
cdf
was
basically
a
bit
behind
the
industry.
And
now
it's
even
more
behind.
D
The
idea
would
be
to
just
upgrade
the
code
of
conduct,
and
then
there
was
a
question
who
actually
answered
that.
I
brought
it
up
about
tracy
yesterday
and
she
said
that
it's
up
to
toc
to
define
what
would
be
the
code
of
conduct
for
projects
and
for
the
cdf
in
general.
D
E
What
I
was
thinking
was
along
the
lines
on
the
inclusivity
statement.
You
know
where
that
other
project
kind
of
gives
some
guidelines
on
how
to
approach
inclusivity
and
that's
what
I
was
more
thinking
about
was
how
a
statement
saying
this
is
how
the
project's
going
to
address
inclusivity.
E
And
around
that
lines,
the
the
the
new
code
of
conduct,
I'm
all
about
the
2.1,
but
I'm
just
wondering
if
we
need
to
go
a
little
bit
deeper
on
the
inclusivity
side
on
that
side,
you
know
for
just
a
you
know,
a
statement,
that's
just
a
markdown
in
each
project.
D
Well,
it
makes
sense
in
principle
what
I
brought
up
a
few
times
on
twitter
when
talking
to
people
is
that
I
would
be
happy
to
see
a
values
md
file
in
parallel
with
call
of
conduct,
because
inclusivity
is
generally
one
of
areas
which
could
be
covered
there.
Also,
there
is
a
question
of
how
the
community
is
governed,
because
it
might
be
democracy
like
some
project
in
jenkins,
we
officially
have
mirrored
a
crisis
as
a
part
of
our
governance
model,
so
we
such
file
could
potentially
include
all
this
key
information.
E
Yeah,
even
if
it
was
just
a
link
to
the
includes
the
inclusivity
project
that
we're
going
to
be
a
part
of
our
part
of
now,
I.
D
Yeah,
it's
fair
point
so
for
inclusiveness
initiative.
So
obviously,
once
our
application
gets
accepted,
it's
stuck
somewhere.
I
haven't
checked
the
status
before
this
meeting.
I
need
to
ask
tracy
because
she
submitted
the
phone.
D
E
All
right,
so
it
would
be
nice,
since
we
had
the
code
of
conduct
at
the
project
level
that
having
it
at
the
inclusive
naming
initiative
or
some
inclusivity
statement
at
the
project
level,
I
think,
would
be
beneficial.
D
So
would
you
be
willing
to
draft
it?
I
mean
how
it
would
look
like,
for
example,
for
steelers
or
maybe
I'll
tell
you
somebody
has
it.
D
I
mean
so,
would
you
be
able
to
draft
it
for
one
of
the
projects,
for
example
for
steelers?
So
maybe
we
could
take
a
look
at
the
next
meeting
and
see
how
it
would
look
like.
D
Because
I
think
that
values
in
the
principle
would
be
a
nice
addition,
but
yeah
it's
not
a
kind
of
industry
standard.
I've
seen
only
a
couple
of
projects
trying
to
do
something
like
that.
Usually
they
put
it
as
a
part
of
code
of
conduct
and
here
contributor
covenant
doesn't
cover
all
bits
of
community
just
by
design.
D
So
yeah
for
inclusive
community.
I
believe
that
actually,
the
most
of
contributor
covenant
is
about
building
inclusive
community,
but
some
bits
might
be
still
missing.
E
Yeah,
I
don't,
I
think
it
the
the
code
of
conduct
is
covers,
like
you
know,
eighty
percent
of
it.
I
think
that
we
need
to
just
take
it
a
step
farther.
E
I'll,
I
will
push.
D
E
Yeah
put
me
down
as
an
action
item
for
doing
a
a
sample
one
for
artelias.
D
D
Okay,
then
I
guess
we
have
everyone
who
wanted
to
join
the
call,
so
I
would
propose
to
press
it
with
a
formal
presentation
for
cd
events.
D
D
E
Okay,
so
we
have
a
pull
request
out
there
under
the
cd
foundation,
toc
repo.
So
this
is
the
proposal
for
the
cd
events.
E
E
Now
the
project
won't
be
exclusively
tied
to
cloud
events,
and
we
may
have
some
new
technologies
come
out
or
better,
better
ways
to
do
it,
but
that's
where
we're
starting
with
at
that
level.
So
one
of
the
things.
Why
is
it
valuable?
Because
we
are
looking
to
help
minimize
the
friction
between
integrations
of
tools
and
steps
in
the
cicd
pipeline?
E
What
we
see
with
the
cd
events
is
the
ability
to
create
a
framework
in
a
spec
that
will
allow
people
to
plug
and
play
the
different
tools.
We
know
that
not
one
company
companies
don't
have
one
tool.
E
They
have
multiple
tools
that
they're
using
in
their
ci
cd
pipeline,
and
the
reach
of
the
cicd
pipeline
is
expanding
further
looking
into
security
scans
telemetry,
you
name
it.
You
know,
testing
that
is
being
broadened
every
day.
So
that's
where
the
the
events
is
trying
to
make
the
the
process
easier
for
everybody
quick
background,
the
cd
events
was
is
right.
Now
is
officially
a
sig
under
the
cdf
there's
weekly.
E
I
think
it's
weekly
meetings
that
happen
around
the
the
spec
itself
vocabulary
doing
proof
of
concept,
so
there's
work
or
group
working
group
around
the
proof
of
concept,
and
we
have
had
a
poc
that
has
been
put
together
and
delivered
and
presented
at
multiple
conferences
and
online
talks
has
been
well
received.
E
So
that's
where
some
of
the
background
history,
we
are
aligning
with
the
the
charter.
You
know
looking
at
a
way.
Cd
events
can
help
with
the
tool
agnostic
focus
of
the
cd
foundation,
the
code
of
conduct
right
now.
The
cd
events
is
working
under
the
cdf
code
of
conduct.
We
just
put
in
yesterday
the
code
of
conduct
for
the
2.1
code
of
conduct
that
we
were
just
talking
about.
E
I
just
didn't
bother
going
and
updating
this
this
document
because
I
figured
we
may
have
a
couple
other
little
changes
that
are
out
there.
The
sponsors
are
andrea
and
myself
and
oleg's
been
very
involved
as
well.
The
project
license
if
I
can
get
scrolled
back
up,
there
is
apache
too.
E
We
are
still
waiting
on
the
logo
to
come
from
the
linux
foundation.
More
than
likely
the
logo
will
be
a
creative
commons
life
license.
We
will
find
out
when
we
get
the
final
version
on
that
for
source
control.
We
actually
did.
We
were
able
to
get
the
the
cd
events
github
org.
E
E
E
Like
a
python
one
or
a
node.js
one
down
the
road,
but
right
now
just
focusing
on
golang
typical
release,
git
flow
following
along
with
like
ortillius
and
techton,
nothing
new
there.
We
do
have
a
wide
variety
of
people
that
are
involved.
E
The
governance
right
now
is
being
done
under
the
governance
that
was
structured
under
the
sig
events
project,
and
we
will
be
looking
to
either
bring
figure
out
how
to
bring
that
governance
structure
from
the
sig
events
into
this
project
or
we'll
just
go
ahead
and
do
a
bootstrap
initial
governance
for
starting
the
project
up
and
then
we'll
get
into
a
formal
governance
model
down.
The
road
are
requesting
an
incubation
status
and
because
everything
is
so
new,
we
will
be
right
now.
E
The
thought
is
use
github
pages
as
our
project
website
and
we're
waiting
on
the
linux
foundation
to
get
us
the
events.cd
domain.
I
don't
know
if
that's
happened,
we
do
have
the
slack
channel,
that
is
the
sig
events
channel
and
our
you
know,
email
emailing
list
right
now
is
off
of
a
google
group.
The
twitter
handle
right
now,
there's
no
external
financial
contributions
at
this
time
and
no
existing
infrastructure
other
than
like
a
the
github
repos.
E
So
we
can
have
where
the
end
user
can
pick,
which
version
of
the
spec
that
they
want
to
be
able
to
view
so
be
able
to
switch
the
the
view
of
the
website
on
demand,
depending
on
which
spec
that
they're,
which
version
of
the
spectre
they're
looking
at
so
that's
kind
of
a
quick
rundown
of
what
we
have
going
on
and
if
you
have
any
specific
questions,
let
andrea
and
myself
know.
D
Yeah,
maybe
one
question
which
makes
sense
to
discuss
here
is
expectation
for
1.0
version,
because
my
understanding
that,
even
if
it's
accepted
as
incompleting
project,
they
will
be
under
zero
version
in
short
term.
So
there
will
be
still
a
lot
of
place
period
so
that
potential
adopters
could
join
participate
in
the
specification
and
maybe
to
do
some
adjustments
and
the
reference
implementations
is
correct.
E
That
is
correct,
so
the
like,
I
said
we
have
the
the
poc
and
we
do
have
a
starting
vocabulary.
E
We
are
working
through
a
couple
technical
issues
around
the
events
such
as
authentication
and
history,
of
the
events
being
able
to
track
through
the
the
event
chain
as
per
that
process.
So
those
are
a
couple
of
the
outstanding
technical
issues
are
for
lack
of
a
better
word
go
to
market
is
to
find
and
work
with
a
couple
use
cases
three
to
four
use
cases
as
real
world
examples
that
we
want
to
focus
the
events
around
and
build
the
vocabulary
around,
and
that
will
give
us
a
concrete
path
to.
E
You
know
give
us
direction
which
events
which
part
of
the
vocabulary
we
need
to
focus
on
and
just
not
go
off
and
start
creating
events
for
creating
events
sake.
E
We
want
to
be
very
targeted
as
part
of
that
process,
so
some
of
the
things
along
those
lines
would
be
bringing
in
the
ambassadors,
the
cdf
ambassadors,
to
help
with
us
and
also
additional
end
user
members
to
give
us
an
insight,
and
maybe
a
couple
use
cases
that
we
can
work
through,
but
the
the
way
we
kind
of
envision.
It
is
more
of
a
functional
design
of
the
spec
based
on
real
world
cases.
A
E
Yeah,
that
was
one
of
the
the
interesting
things
is
the
what
what
would
happen
between
the
the
sig
events
and
the
project
itself,
and
that's
where
we'll
need
some.
E
Some
guidance
is
whether
we
continue
with
the
sig
events
and
because
that
could
be
rather
much
broader
than
the
project
itself,
where
the
project
will
be
focusing
on
more
narrow
parts
of
the
spec,
so
totally
open
to
ideas
on
that
front,
which
way
we
should
go
along
those
lines
and
as
far
as
a
road
map,
we
did
not
lay
out
a
road
map
because
it
it
wasn't
required
as
part
of
the
project
proposal,
and
that
may
be
something
that
we
need
to
add.
A
Yes,
the
reason
why
I
am
asking
is
like,
because
you
already
mentioned
few
things
that
is
coming
from
c
events
like
this
vocabulary.
I
I
think
they
are
like
part
of
roadmap
anyways,
but
yeah
again,
this
is
proposal
and
it's
not
a
requirement
under
the
proposal.
So
it's
general
question
about
how
do
you
envision
the
you
know,
working
between
sig
events
and
cdns
and
perhaps
broader
cd
f
community,
because
whatever
you
may
be
doing
in
both
of
these
things,
like
events
and
the
project
will
have
impacts
on
the
ecosystem
at
large.
E
Exactly
and
one
of
the
things
with
the
the
events
is
they
span,
you
know
into
everything,
so
they,
if
you
look
at
the
member
list,
if
I
can
get
down
there
like
dynatrace,
which
is
kept
in
that's
a
cncf
project,
harness
it's
over
in
the
cncf
or
ortilius,
is
a
cdf
project.
Same
type
of
jenkins
is
a
cdf
project,
so
it's
spanning
across
multiple
organizations
and
projects
in
the
linux
foundation.
E
E
You
know
what
what
should
be
the
focus
of
the
sig
events
and
what
should
be
the
focus
of
the
the
project
and
I
foresee
the
project
more
being
around
the
implementing
the
spec
and
the
sig
events
is
more
of
the
the
gathering
and
and
understanding
the
world
out
there.
Around
events.
B
Yes-
and
I
think
that
kind
of
matches
with
the
structure
that
we
have
today
so
we
have,
we
do
have
weekly
meeting
for
the
sikh
events
and
they
kind
of
alternate.
So
every
second
week
we
have
one
meeting
which
is
focused
on
the
spec,
it's
more
specifically
in
the
vocabulary,
and
then
we
have
a
meeting
which
is
more
focused
on
yeah,
describing
the
use
cases
inviting
people
to
present
their
work
around
events
to
try
to
get
a
better
feature
of
what
the
community
is
doing
with
events
today
and
what
other
use
cases.
A
Thanks-
and
I
have
another
comment-
actually
sorry
for
nitpicking,
if
you
go
down
to
the
end
of
the
proposal
steve
this
communication
channels,
like
list
email
lists
like
because
I
think
you
are
starting
new
fresh,
I'm
wondering
if
the
group
stop
io
is
an
option
to
use
for
no
the
seed
events
but
yeah.
This
is
a
very
small
thing.
Just
a
question.
E
Yeah,
so
we
we
chose
the
google
groups
because
it
was,
we
felt,
is
the
easiest
to
implement
and
it
gave
access
you
can
use.
The
google
groups
give
access
to
google
docs.
C
E
Part
of
the
shared
world,
but
the
that's
one
of
the
main
reasons
you
know
you
get
you
can
assign
like
a
shared
calendar
can
be
owned
by
and
I
would
say
own,
but
you
can.
You
can
have
a
a
shared
calendar
that
the
invitee
is
the
google
group.
So
when
somebody
comes
in
and
joins
the
joins,
the
group
that
they'll
have
access
to
the
calendar
invites
so
just
for
ease
of
implementation.
E
D
D
But
for
me,
it's
rather
a
separate
stage,
which
is
to
be
done
after
the
general
decision
is
made.
So
the
question
is
whether
we
able
to
initiate
the
vote
now
or
whether
we
need
additional.
D
D
So,
regarding
binding
votes,
it's
used
for
me,
andrea
milisa,
so
we
have
five
of
nine
right
yeah.
So
so,
theoretically
we
could
accept.
We
would
make
a
decision
even
on
this
call,
but
yeah.
D
I
would
rather
prefer
to
give
a
chance
to
anyone
who
is
not
on
the
call
to
contribute
to
the
decision
or
to
voice
concerns
if
anyone,
so
my
preference
would
be
to
just
agree
to
press
it
with
the
call,
if
you
agree
and
then
basically
set
a
decline,
something
like
one
week
and
then,
if
everything
is
a
key,
if
you
get
enough
votes,
then
just
press
it.
D
E
Yeah,
I
think
if
we
come
out
beginning
in
the
new
year
with
the
the
announcements
that
would
be
good
timing,
because
everybody'll
be
coming
back
to
work
and
so.
D
E
F
Know
only
that
I've
I'm
very
happy
to
help
support
the
marketing
promotion
for
cd
events
and
to
that
end
I've
started
some
discussions
with
people
who
could
help
us
with
that.
But
I'm
liaise
with
the
event
sake
and
the
project
leadership
governing
board
for
cd
events
regarding
that
and
regarding
the
timeline
of
when
we're
ready
to
do
that.
Promotion.
E
A
E
And
that's
part
of
the
the
things
that
we
are
working
on
is
looking
to
expand
the
poc
as
part
of
that
being
able
to
present
it
at
talks
like
the
cdcon.
E
And
also
there's
like
cube
cons
in
spain
that
we
may
be
able
to
get
into
as
well
that
that
call
for
papers
is
coming
up.
I
believe
it's
middle
of
december.
D
It's
so
short
with
regards
to
deadlines
this
year,
especially
for
fosdem,
because
everything
is
something
like
several
months
later
compared
to
usual
before
for
coronavirus.
D
E
On
this,
so
does
it
since
the
road
map
came
up,
does
it
make
sense
to
add
the
to
raise
an
issue
about
adding
a
road
map
to
the
proposal
document.
D
I
think
it
would
be
useful,
so
we
have
a
mandatory
requirement
for
having
roadmap
for
graduated
projects,
but
yet
to
be
honest,
I
think
that
should
be
even
more
important
for
incubating
projects,
especially
when
we
decide
whether
to
accept
them
or
not,
because
if
there
is
no
clear
vision
for
the
project,
it
becomes
much
more
difficult
right.
E
Yeah
I'll
create
the
issues,
so
we
can
and
tie
it
to
the
proposal
doc.
D
Yes,
so
what
else
did
we
use
so
yeah?
There
are
some.
There
will
be
some
items
in
the
checklist
for
december.
For
example,
I
think
cd
events
to
the
continuous
delivery
length
escape,
but
all
of
that
is
already
listed
in
our
important
checklist.
D
Thanks
a
lot
stephen,
andrea,
so
looking
forward
to
having
this
project
officially
accepted,
should
the
voting
go
fine
and
yeah
by
the
next
meeting
we
should
have
a
decision
about
that.
D
So,
let's
start
from
here
so
public
cdf.
From
up
it's
my
mistake:
we
agreed
that
it's
basically
radiant
for
some
incident.
You
might
need
to
announce
it,
but
yeah
implementation,
wise,
it's
trading.
So
at
cd
events,
we
discussed
it
already
joining
the
inclusive
naming
initiative.
Basically,
no
updates.
We
are
waiting
for
enrollment
to
be
processed
by
the
foundation
so
well.
Inclusive,
naming
initiative
is
also
a
part
of
the
linux
foundation
and
they
use
lfx
tools
and
it
looks
like
the
application
got
stuck
somewhere
there.
D
F
Yes,
maybe
I
don't
know
if
I'll
put
it
in
the
chat.
Actually,
let
me
there's
actually
a
couple
issues
that
I
would
love
feedback
on
so
since
you've
asked
I'm
going
to
ask
for
feedback
right
now.
F
Okay,
mostly
there's
this
issue
right.
If.
F
F
Is
I'm
really
trying
to
take
it
section
by
section
and
sort
of
work
up
a
prototype,
getting
feedback
as
we
go
with
different
involved
groups,
including
this
board,
but
say,
for
example,
the
events
egg
for
that
section
and
and
what
I'm
working
on
right
now
is
this
this,
but
actually
yeah
yeah
this
one
on
this
area
of
observability
and
analysis,
and
it's
really
a
question
right
now.
F
The
specific
point
I
want
feedback
on
is
where
we
should
put
messaging
protocols
but
also
cd
events
within
this
larger
box
and
I'm
just
looking
for
specific
feedback
so
that
it's
not
just
me
doing
it,
and
then
people
saying
no.
That's
not
what
it
should.
F
Look
like
like
I'd
like
feedback
as
I
go,
or
other
people
can
do
pr's
too,
but
just
starting
with
this
one
section,
there's
a
couple
more
sections
that
will
be
coming
up
like
security
and
on
testing
that
will
also
be
worked
up,
but
just
trying
to
take
it
piece
by
piece
and
then
I'll
put
in
these
spaces.
These
larger
blocks
that
are
reconfigured
into
the
landscape
overall,
so
this
one
relates
to
it
relates
to
this
pr
which,
if
I
go
here,
you
can
see
it
it's
pretty
much.
The
screenshot,
though,.
F
This
is
the
prototype,
so
this
is
just
moving
it
around.
I
had
to
move
a
section
out
in
order
to
build
this.
This
is
why
it's
not.
This
is
why
it's
a
wip
and
not
a
real
pr,
but
if
you
all
want
to
give
feedback
on
the
issues
or
on
this
prototype
pr,
please
do
there's
also
a
number
of
issues
within
the
within
the
repo.
F
And
all
of
these
please
jump
on
and
comment
and
comment
with
as
much
specificity
as
you
can.
So
a
lot
of
it
is
like.
Oh,
you
should
have
this
category,
but
I
would
like
more
detailed
information
or
input
than
that,
for
example,
these
are
the
sort
of
projects
that
could
fit
in
this
category.
Here's
why
I
think
they
group
together,
here's
where
we
can
move
projects
around.
F
E
Car,
did
you
see
the
one
that
I
found
on
the
cncs
side
about
the
members
where
they
took
the
members
and
reworked
it
to
a
separate
tab.
F
E
F
When
I
move
in
the
separate
sections,
we
will
grow
the
actual
shape
of
the
landscape
escape.
You
can
stretch
it,
so
it
goes
beyond
the
fold
and
you
can
scroll
around
a
larger
surface
area
and
that's
really
helpful,
and
I
think
this
this
subject,
you
brought
it
up
in
another
meeting
on
the
landscape.
Maybe
the
landscape
working
group
meeting
and
we
discussed
it
and
at
that
time
I
forget
who
commented?
Maybe
it
was
fatigue?
F
I
don't
want
to
put
you
on
the
spot,
but
it
was.
It
was
saying
that
actually,
at
this
moment,
we'll
leave
them
where
they
are
and
then,
when
we
reconfigure
the
landscape,
we'll
move
a
lot
of
pieces
around
and
grow
the
size
of
it.
So
where
the
members
fall
and
where
the
qr
code
section
falls,
things
like
that
will
definitely
change
and
it's
just
a
question
of
what
changes
where,
but
that's
a
little
bit
farther
down
the
line.
E
Okay,
this,
I
just
want
to
make
sure
you
saw
how
the
cncf
was
able
to
get
some
more
real
estate
for
you.
F
F
Yeah,
no,
no,
definitely
because
I
also
need
I,
I
think
it's
a
very
good
channel
to
engage
people
and
to
make
people
like
look
at
it
and
get
feedback,
because
otherwise
it
can
be
hard
to
get
the
feedback
that
I'm
looking
for.
So
yes,
we
will
be
convening
another
one
I
yeah
before
in
december.
Basically,
but
yes,
thank
you
for
your
interest,
that's
really
helpful.
All
the
input
is
is
really
really
helpful
and
making
it
as
specific
and
granular
as
possible
is
also
helpful.
F
Specificity
is
good,
so
so
this
is
just
a
call
to
action
to
all
of
you.
Please
please
give
feedback
on
any
of
these
issues
on
the
prototype
pr,
especially
because
I'd
love
to
have
a
working
sketch
on
that
that
we
have
some
agreement
on
and
then
move
on
to
different
sections,
like
the
testing
section
and
the
security
section
things
like
that,
that
is
it
for
landscape.
F
D
Thank
you
too,
so
the
next
one
and
the
last
one
we
have
in
progress
officially
is
new
project
onboarding.
So
this
one
is
definitely
not
ready
to
be
closed.
We
have
a
bunch
of
open
tickets,
plus
we
discussed
at
least
two
to
be
created
today.
D
Looks
like
at
some
point,
we
will
just
need
to
sit
together
and
maybe
get
some
tvc
meeting
and
get
it
over
the
line,
such
as
still
text,
so
that
we
mention
everything.
D
D
B
D
Okay
and
for
all
other
issues,
you
believe
no
updates.
So
first
bitcoin
jaclyn
announced
the
program
committee.
D
So
now
we
can
slowly
start
preparing
to
cdft
receipt
to
understand
what
exactly
is
needed
from
us
as
a
group,
maybe
some
updates
there
but
yeah.
I
don't
think
that
there
is
something
this
deadline
in
the
coming
two
months,
so
we
can
just
press
it
with
the
stories
we
have
in
the
flight,
get
to
see
the
events
over
the
line,
get
the
boarding
guidelines
and
then
see
what
else
we
need
to
do.
D
D
B
I
I
added
one
item
and
trying
to
find
out
who
can
help
me
with
that.
So
on
tagline
side,
our
infrastructure,
like
releases,
ci
and
so
forth,
they
run
on
gcp.
So
google
cloud
and
the
projects
were
originally
created
like
project
for
googlers,
because
their
project
was
initially
created
in
google.
Then
it
was
donated
to
the
cdf,
and
so
new
billing
accounts
were
created
to
move
some
of
the
projects
over
to
the
new
buick
account,
which
should
be
then
built
to
the
cef.
B
But
at
the
moment
the
status
is
that
we
have
a
couple
of
billing
accounts,
I'm
not
sure
which
one
of
them
is
built
to
the
cf
and
what
we
are
planning
to
do
in
the
december
time,
where
you
want
to
recreate
the
produce
from
scratch
so
that
they
are
created
like
regular
projects
and
then
like
people
from
the
technical
community
can
have
like
full
admin
access
and
then
we
can.
We
would
like
to
set
them
to
the
right
billing
account
that
is
visible,
so
the
one
that
the
cdf
has
actually
access
to.
B
C
I
think
you'll
probably
want
to
start
with
tracy
miranda
and
then
also
michelle
who's.
Our
new
pm,
I
think
they'll,
probably
be
be
able
to
help
you
with
all
that.
D
Okay,
so
if
that's
it
thank
you
so
the
next
meeting,
because
it's
usually
in
two
weeks,
so
it
will
be
december
7th
december
8th.
Are
you
then,
just
planned
for
these
days.
D
D
All
right
thanks
everyone.
Thank
you.
I
I
will
submit
voting
for
cd
events
tonight,
so
maybe
in
a
couple
of
hours
and
yep,
everyone
is
welcome
to
participate.