►
From YouTube: CDF - TOC Meeting - 2021-05-25
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
B
A
A
C
C
A
A
A
I
really
should
have
one
topic
before
all
of
these
that
right
tracy,
some
announcements.
Yes,.
A
C
Yes,
sorry
give
me
a
sec
okay,
so,
as
folks
may
or
may
not
be
aware,
we
are
currently
running
toc
elections
for
two
types
of
seats.
So
we
have
four
project
seats
and
two
general
seats
and
nominations
are
closed
for
all
these
seats.
So
the
project
seats
closed
a
couple
of
weeks
ago
and
the
general
seats
closed
as
of
yesterday.
C
So
the
first
thing
I
wanted
to
announce
is
that
for
the
project
seats
we
had
four
nominations
and
since
we
have
four
seats,
these
seats
are
uncontested,
so
we're
not
going
to
be
holding
an
election,
but
I
would
like
to
welcome
the
four
folks
to
take
on
the
seats
which
will
be
andrea,
fritoli,
oleg
nineshev,
justin
emanuel,
who
rejoins
the
duc
and
steve
taylor
so
I'll,
be
sending
out
an
announcement
after
later
today,
just
to
confirm
and
yeah
we've
had
confirmation
from
the
election
officers
that
we're
happy
to
proceed
in
this
way,
so
yeah.
D
C
And
just
on
the
yeah,
so
just
a
reminder:
the
official
term
will
be
as
of
first
july
but
yeah
happy
to
to
start
to
have
folks
working
already
here
and
we
will
be
going
ahead
with
a
general
election.
We've
had
a
lot
of
candidates
come
in
so
we're
hoping
to
post
those
to
the
governing
board
and
get
them
voting
on
them
over
the
next
few
weeks.
So
we'll
keep
you
posted
on
how
that
goes.
C
Okay
but
yeah,
unless
the
you
folks
want
to
say
anything.
I
is
that
I.
B
Have
one
question
about
voting
for
civicon,
so
yeah?
Sorry,
it's
not
the
elections,
but
yeah.
There
would
be
also
election
process
and
do
we
have
enough
candidates
for
positions
at
the
moment.
B
C
Yeah,
I
think
we
switched
that
one
to
a
form,
so
I
think
there
may
be
more
nominations
yeah
privately,
but
I'd
have
to
check
with
roxanne,
and
I,
like
your
tenuous
link
of
elections
and
elections,.
B
E
E
We
have
six
sorry,
we
got
six
slots,
we
have
six
projects
accepted.
I
think
the
students
are
signing
up.
Oleg's
been
very
active
for
the
jenkins
projects,
as
as,
as
one
would
expect,
thank
you
olek.
E
Looking
in,
I
believe
everybody
is
ready
to
kick
off.
I
was
gonna
follow
up
with
is,
let's
see.
E
I
don't
think
so.
All
right,
I
was
going
to
follow
up
with
spinnaker
to
make
sure
that
they
were
engaged
with
the
student.
Beyond
that,
I
don't
know
if
you
have
any
other
things
to
share
on
the
on
the
jenkins
side,.
B
So
we
had
a
complete
one
kickoff.
We
usually
organize
it
as
a
kind
of
recorded
video
call
with
somebody
for
accepted
and
rejected
students.
So
this
happened.
We've
got
quite
a
number
of
questions.
We
also
have
action.
I
think,
update
the
documentation
we
reached
out
to
the
spinnaker
team.
I
just
sent
them
all
links
related
jenkins.
They
are
welcome
to
follow
our
approach
and
follow
it's
totally
their
choice
but
yeah.
B
I
just
shared
the
information
we
had
having
the
jinx
community
and
currently
we
still
have
a
few
action
items,
including
sending
the
feedback
form
for
students,
the
other
participants
and
also
sending
job
sending
feedback
for
to
rejected
students.
I
am
halfway
through
that,
but
some
other
reasons
than
relation
to
gsoc.
B
B
E
A
B
No,
it
wasn't
me,
but
not
me,
oh
okay,
so
yeah
just
to
share
some
context.
We
have
quite
a
known
issue
with
naming
in
terms
of
agencies
was
created.
15
years
ago,
agents
used
to
be
called
slaves
before
controllers
used
to
be
called
masters
before
and
yeah.
They
were
battle
changes,
so
in
2016
they
changed
the
agent
technology
in
2020
we
changed
the
controller
technology.
There
is
ongoing
cleanup
and
actually
there
is
a
lot
of
activities.
B
We
also
developed
some
developer
tools
to
locate
misusages,
for
example,
when
you
have
a
wrong
word
being
used
in
a
screenshot
in
your
documentation,
and
you
want
to
discover
this
detecting
full
request
happening
there
and
during
one
of
the
investigations
in
twitter,
the
cncf
members
are
reaching
out
and
saying
that
hey
there
is
open,
inclusive
naming
initiative,
it
just
started.
It
happens
also
under
the
umbrella
of
the
links
foundation
to
some
extent,
so
priyanka,
sharma
and
stephen
augustus
are
two
main
co-founders
that
other
co-founders
and
yeah.
Basically,
this
initiative
is
just
starting.
B
We
from
several
contributors
from
the
junk
is
coming
to
join
the
student
meetings,
the
channels
and
so
far
the
collaboration
was
pretty
good
and
actually
we
are
invited
to
join
as
the
continuous
debater
foundation
as
participating
organization.
B
So
well,
there
is
no
strings
attached,
so
we
already
have
jenkins
project
working
on
that.
We
also
have
interoperability.
B
We
spent
considerable
time
reviewing
terminology
and
aligning
that,
so
it
would
be
natural
if
we
use
these
existing
activities,
kind
of
related
projects
and
during
the
inclusiveness
initiative
as
a
foundation
of
course,
cdf
talk
and
both
would
be
interested,
but.
A
Cool
yeah,
this
makes
perfect
sense
the
logistics
around
how
the
foundation
draws
your.
Why
I
assumed
it
was
crazy.
C
Yeah,
so
I
I
think
so
it's
a
great
initiative
and
it
will
be
great
to
align
like
what
the
projects
are
doing
with
what
they're
doing
there
like
to
me.
It's
not
clear
like
what
is
their
need
for
an
official
joining.
Do
we
not
just
jump
on
the
list
and
start
changing
things
or
is.
B
C
B
Why
is
there
need
to
be
jumped
on
the
list
so
why
it's
useful?
Firstly,
to
get
more
publicity,
because
there's
banners
and
participant
organizations
funding
organizations
there
will
be
some
representation
at
the
events.
So
currently
the
employee
naming
initiative
are
looking
for
their
fundraising
model,
but
they
all
look
at
hundreds.
Thousands
of
dollars
per
year
in
terms
of
funding
for
marketing
and
other
activities
and
being
a
member
of
this
foundation
would
also
help
to
promote
the
goals.
For
example,
inside
the
interpretability
seek
for
ineffective
technology
inside
jenkins,
we
could
share
experiences.
B
We
could
probably
facilitate
some
contributions
through
these
activities,
so
I
think
that
joining
the
foundation,
the
initiative
explicitly,
would
make
sense
as
long
as
we
are
committed
to
cleaning
up
terminology
and
at
least
on
behalf
of
jenkins,
I
can
say
that
we
are
committed
to
pick
up
the
terminology
and
I
believe
there
are
no
major
issues
in
other
projects.
Maybe
things
like
white
feast,
vectors
et
cetera,
but
yeah.
This
is
also
something
we
could
clean
up
on
the
interoperability
level,
since
it
reviews
terminology
already.
C
Okay,
yeah,
I
don't
see
anything
official
on
the
website.
It
just
says
sort
of
join
the
mailing
list,
so
I
can
reach
out
and
find
out
if
there's
more
to
it,
which
it
might
be.
B
C
C
Yeah,
no,
I
I
think
that
makes
sense
and
as
from
an
organization
level,
I
I
can
manage
that,
but
I
think
yeah
it
does
depend
on
the
toc
being
involved
and
making
that
connection
down
to
the
projects
and
and
figuring
out
a
way
we
can
yeah.
C
C
D
And
for
like
the
ortelius
project,
we
you
know
in
our
code
of
conduct
we
like
on
our
discord
channel.
We
monitor
that
and
you
know
if
somebody
phrases
something
wrong.
We
go
and
just
drop
a
hint
in
there
to
correct
it,
and
you
know
people
do
it
right
away.
As
part
of
that,
we
have
not
seen
the
issue
in
pull
requests
or
issues
that
type
of
inclusive
naming
concerns
at
that
level.
So
we've
been
self
monitoring.
C
B
E
That's
good,
I
think
so.
Some
of
the
google
projects
have
been
going
through
this.
I
can't
speak
for
all
them,
obviously,
because
there's
thousands
of
them,
which
is
a
whole
other
discussion,
but
there's
a
lot
of
stuff,
that's
getting
built
into
and
made
available
via
github.
Maybe
it
might
be
good
to
have
a
little
little
one
pager
for
here
are
the
easy
tools
to
use,
but
like,
above
and
beyond
this
inclusive
naming
that
people
have
already
built
out
so
make.
B
The
results
worker's
name
for
marketing
works
in
open
source
for
inner
source,
but
yet
tooling
is
one
of
the
upstreams.
We
already
have
one
of
jenkins
contributors
participating
there.
The
array
who
created
the
tool
for
analysis
before
so
yeah,
it's
already
within
this
initiative.
So
again
we
can
share
experiences
and
benefits
benefit
from
what
others
have
already
done.
A
All
right
next
topic
for
oleg
again
jenkins
infrastructure
account.
So
we
did
some
billing
transfers.
B
Yeah,
so
we
have
just
finished
the
transfer
of
the
asia
accounts
for
jenkins.
I
mean
we
transferred
them
quite
a
while
ago,
but
we
were
still
fighting
these
things,
like
billing
notifications,
etc,
to
ensure
that
everyone
is
informed
by
the
time
it
should
be
finished
on
the
logic
side,
and
we
also
have
support
from
budget
side
foundation
and
old
members,
so
they
continuously
the
foundation
offers
something
like
120
k
per
year
for
aging
infrastructure
as
a
part
of
sponsorship
and
yeah.
B
Of
course,
we
also
have
some
infrastructure
based
on
aws,
actually
quite
a
lot,
because
aws
is
sponsored
to
the
moment
by
amazon
and
by
cloudbees
and
what
it
means
that
there
is
no
additional
cost
applied,
but
at
the
same
time
the
current
ownership,
the
account
is
formerly
owned
by
employees,
prevents
us
from
onboarding
non-cloud-based
contributors
there
and
there
was
various
things
with
payments.
B
So
as
a
genghis
project,
we
would
like
to
transfer
this
aws
account
to
the
continuous
delivery
foundation,
so
that
billing
and
control
and
governance
of
this
account
happens
on
the
foundation
level.
But
again
it
doesn't
include
additional
costs.
So
this
account
is
fully
sponsored,
but
it
will
be
great
if
ownership
is
transferred
to
the
foundation.
C
Yeah,
it's
a
british
thing.
I
yeah,
I
think,
I'm
pretty
familiar
with
this.
Having
been
involved
on
on
that
site
from
cloudbees.
I
think
it's
something
we
just
need
to
figure
out
with
the
lf
team
and
I
think
we
have
an
existing
cdf
aws
account
primarily
used
by
spinnaker.
So
it's
just
something:
we
need
to
figure
out.
How
that
will
work
and
gail
is
not
in
this
week,
but
I
think
you
can
help
us
just
move
forward
on
that.
Just
a
warning.
C
I
think
it
will
take
time
and
especially
with
cdcon
coming
up,
but
it's
something
we
can.
B
Expect
so
we
basically
started
the
things
on
our
side.
Currently,
we
are
detaching
jenkins
account
to
a
separate
account
because
we
had
issues
with
sponsorship
from
amazon
go
into
other
accounts
because
of
how
aws
billing
works
yeah
and
it
might
be
the
same
concern
which
accounts
with
spinnaker.
So
it's
something
to
be
discussed,
and
I
didn't
expect
immediate
resolution,
but
yeah
if
there
is
a
general
agreement
from
the
toc
and
from
this
dm4
that
there
is
interest
in
this
account
we
can
initiate
the
discussion.
While
we
do
immediate
steps
on
the
jenkins
infrastructure
side.
C
Yeah
I
I
say
I
need
to
ask
that
I
love
events
team,
what
it
will
take,
so
no
commitments
until
I
get
a
better
understanding,
but.
A
You
all
right
time
for
something
exciting,
but
also
potentially
logistically
challenging,
giving
even
we're
in
our
lame
duck
period
to
call
it
that
of
talk
rotations.
We
have
a
new
project
proposal
to
move
shipwright
to
the
cdf
jason.
I
think
you're
still
here,
yeah
yeah,
do
you
want
to
take
over
screen,
sharing
and
walk
us
through
this
and
then
after
I
want
to
make
sure
we
figure
out
logistics
on
what
to
do
with
this.
Given
the
new
talk
doesn't
start
for
a
little
bit.
F
Sure
one
second,
I
just
closed
the
window.
I
meant
to
share
so
that's
how
today's
going
one
sec.
F
Let's
do
the
rendered
version,
so
shipwright
is
a
a
I'll
just
sort
of
quickly
go
through
the
the
document,
because
I
I
mostly
want
to
have
time
for
questions.
F
Shipwright
is
a
project
that
started
at
red
hat
that
got
that
has
gotten
a
lot
of
contribution
and
input
from
the
ibm
code
engine
the
ibm
cloud
code,
engine
d-
it's
basically
a
open
shift
for
a
long
time-
is
that
a
feature
called
openshift
builds
where
you
can
send
a
build
to
your
cluster
to
your
openshift
cluster
and
it'll
it'll
operate
that
build
and
then
give
you
an
image
which
you
can
then
deploy
and
do
whatever
else
you
want
with
shipwright
is
sort
of
a
reimagining
of
that
a
modernization
of
that
in
a
separate
external
project
that
is
not
deeply
tied
to
openshift.
F
So
red
hat
started
this
project
and
then
the
code
engine
team
said
hey.
We
we
could
use
this.
We
would.
We
would
like
to
use
this
and
they
chipped
in
and
have
done
a
lot
of
work
with
us
to
get
it
to
the
point
where
it
is
and
now
we
are
interested
in
in
contributing
it
as
a
project
to
the
cd
foundation.
F
If,
if
you'll
have
us,
I
haven't
like
prepared
any
demos
or
any
things,
but
there
is
a
there
is
a
talk
at
cdcon
that
I'm
that
I've
already
recorded
that
that
goes
over
sort
of
the
basics
of
shipwright.
I'm
happy
to
answer
any
questions
here
or
offline.
I
don't
know
whether
this
is
the
the
forum
for
q
a
but
I'm
happy
to
answer
anything
you
have.
I
also
think
a
couple
of
shipwright
people
at
least
two
shipwright
people
are
here
adam
and
shubik.
F
I
see
in
case
I
am
unable
to
answer
your
questions.
Those
two
who
know
much
more
than
me
will
be
able
to.
Hopefully.
E
So
I'm
taking
a
two
second
look
at
this.
This
is
also
hi
jason.
Nice
to
see
you
hey,
how's
it
going
like
the
facial
hair,
so
this
is
meant
to
be
a
wrapper
framework.
It
looks
like.
F
So
yeah
it
it
depends
on
tecton
it
actually
offloads
most
of
the
actual
work
detecton.
F
But
shipwright
does
one
specific
thing
as
simply
as
possible,
and
you
know
as
flex
the
highest
combination
of
flexible
and
simple
for
that
specific
goal,
as
opposed
to
techton,
which
is
obviously
great
but
can
do
way
more
and
therefore
is
more
complex
and
there's
plans
to
integrate
the
two
together
so
that
you
you
don't
have
to
choose.
You
know
the
the
flexible
complex
one
or
the
simple
single
purpose,
one
you
can
use
them
both
together.
E
Yeah
and
it
looks
like
there's
well
a
couple:
dozen
contributors
are
any
of
those
external
to
red
hat
ibm.
Is
there
like
a?
Is
there
an
external
community
as
such,
yet
or
is
it
still
kind
of
early
early
stages?
For
that.
F
I
think
mainly
all
of
the
the
contributors
are
red,
hat
or
ibm.
It
is
the
corporate
relationship
between
red
hat
and
ibm
is,
is
sort
of
I'm
still
learning
it
myself,
but
the
ibm
team
and
the
red
hat
team
are,
you
know,
distinct
for
all
intents
and
purposes.
So
so
we
don't
like
have
the
secret
cabal
meetings
where
we
discuss
things
and
then
go
up
to
the
community
like
I
never
talk
to
them.
E
Sorry,
I
I
think
I
may
have
asked
my
question
incorrectly.
It
was
more
like.
Is
there
an
extra
like?
Is
there
a
current
or
plans
for
us,
an
external
community
engagement,
you
think
about
jenkins,
for
example,
as
kind
of
our
showcase
as
the
oldest
project,
the
number
of
external
comm
community
members,
that's
kind
of
a
key
element
to
a
cdf
project
yeah,
and
so
that's
something
we
so
that.
Hence
my
questions
like
how
much
outreach
has
been
done
thus
far
or
are
there
plans
for
that?
E
Otherwise,
that's
something
we
could.
We
could
talk
through.
F
Right
we're
definitely
interested
in
in
welcoming
in
more
people
right.
I
guess
sorry
also,
I
didn't
mean
to
mischaracterize
your
question.
It's
also
like
we
have
these
public
community
meetings
in
which
anyone
is
welcome.
It
just
so
happens
that
red
hat
and
ibm
people
tend
to
be
the
ones
that
show
up
if
anybody.
F
We
would
welcome
them
and
love
to
have
them,
and
you
know,
assign
them
issues
and
send
them
prs
and
everything,
but
that's
definitely
part
of.
I
think
what
we
are
hoping.
What
shipbread
is
hoping
to
get
from
cdf
is:
is
community
outreach
community
building
neutral
home
like
really
start
ramping
up
that
effort
and
getting
more
contributors
from
all
corners.
E
So
there's
I
feel
like
I'm
speaking
a
lot
to
anybody
else,
feel
free
to
jump
in
here.
One
of
the
outstanding
questions
that
we've
had
is
sort
of-
and
I
guess
I'm
looking
at
dan
and
tracy
a
bit
here-
is
incubation
versus
what
was
the
other
category.
E
Yeah
and
I'm
just
remembering,
you
know
what
we
did
with
ortelius
and
spinnaker,
for
example,
as
I'm
just
wondering.
If
there's
because
there's
a
sorry,
I'm
gonna,
because
I
know
you
jason,
I'm
going
to
take
this
opportunity
to
nitpick
a
little
bit
procedurally,
because
I
know
that
you'll
take
it
in
in
the
spirit
given.
There
was
originally
an
idea
that
the
the
incoming
projects
for
incubation
have
that
community
more
strongly.
E
But
but
that
was
you
know
that
was
early
discussions.
I
don't
know
how
how
much
we
want
to
hold
to
that
or
if
we
want
to
take
this
opportunity
to
think
about
incubation
versus
sandbox
and
just
refining
these
project
intros.
So
this
is
more
of
a
governance.
A
A
Yeah
we've
talked
about
the
sandbox
a
bunch
of
times,
but
we
don't
actually
technically
have
a
sandbox
right
of
incubation,
which
is
kind
of
a
broader
range.
So
it's
for
things,
buds,
buddings
of
the
community
and
then
graduated
is
for
kind
of
full-fledged
projects.
E
H
So,
just
from
the
artelia's
perspective
in
terms
of
what
we
went
through,
we
have
the
opposite
problem.
That
jason
is
expressing
because
we
didn't
have
a
big
recognized
company
like
an
ibm
or
red
hat,
that
this
was
you
know,
was
created
under.
H
It
was
created
under
a
bunch
of
smaller
companies
and
when
we
decided
to
go
to
to
apply
to
become
part
of
the
cd
foundation
we
held
back
and
we
didn't
even
try
until
we
felt
we
had
a
large
enough
in
a
contributor
base
to
bring
to
the
cd
foundation,
but
at
the
same
time
we
weren't
able
to
bring
in
a
big
name.
H
So
you
know
it's
not
every
not
every
open
source
potential
is
equal.
I
guess
is
what
I'm
trying
to
say.
You
know
it's
great
to
have
the
big
names
come
in
with
some
of
their
with
the
technology
that
they
are
creating
and
it's
also
great
to
bring
in
the
smaller
companies
who
are
innovating
across
multiple
companies.
H
It's
kind
of
like
the
difference
between
backstage
and
deploy
hub,
right,
backstage
and
deploy
up
are
kind
of
similar
products.
Backstage
was
created
by
spotify
and,
as
inc
is,
I
think,
a
sandbox
in
the
cncf
we
had.
You
know
100
plus
people
in
our
community
with
about
20
contributors
and
that's
when
that
was
the
point
in
time
that
I
felt
confident
to
bring
it
to
the
the
the
toc.
But
I
think
if
I
was
a
bigger
company,
like
jason,
I
might
be
saying
hey.
H
E
Yeah,
I
totally
hear
what
you're
saying
I
think,
there's
if
I-
and
maybe
dan
remembers
this
conversation
better
than
I
do,
but
I
do
remember
having
a
conversation
about
making
sure
that
if
you
have
like
a
small,
a
a
small
group
of
of
heroic
fighters,
you
know
producing
their
their
open
source
project
and
the
bigger
companies
like
yeah.
You
know
that's
nice,
but
we
don't
care
that
much.
What
we
don't
want
is
is
for
that
project
to
basically
get
orphaned,
because
the
big
company
isn't
investing
the
value.
Now.
E
I
am
not
saying
that
this
is
the
case
for
red
hat
ibm
at
all.
In
fact,
I
suspect
it's
quite
the
opposite,
but
it's
something
I
just
want
to
make
sure
that
we're
mindful
of
and
that's
hence
the
community
question.
You
know
how
much
ongoing
investment
is
is
being
committed
from
that
large
company
say
like,
for
example,
verizon
media,
as
opposed
to
this
just
kind
of
being
a
dumping
ground,
and
we
inherit
a
project.
E
That's
not
going
to
get
a
lot
of
love
right
so
again,
not
not
to
to
pick
on
jason
and
and
and
the
shipwright
team,
but
I
do
think
it's
important
that
we're
consistent
in
this,
because
we,
you
know,
we
don't
bring
on
a
lot
of
new
projects.
I
just
want
to
make
sure
we're
doing
due
diligence
on
them.
F
Yeah,
that
makes
sense,
I
mean
I,
if
you
have,
if
you
have
concerns,
I
would
love
to
allay
those
concerns.
I
don't
know
if
there
are
any
specific
concerns
for
shipwright
or
if
this
is
just.
If
you
know
just
in
general,
we
should
make
sure
to
prioritize
this
for
all
projects,
including
this
one
yeah.
E
Well,
you
know,
like
I
said
in
previous
discussions,
one
of
the
first
things
that
was
asked.
I
think
spinnaker
was
the
last
time
we
had.
That
particular
conversation
is
how
many
external
contributors,
you
know,
and
what's
the
plans
for
that,
and
I
think
that
you
know
I'm
looking
at
cara
a
little
bit
here
because
are
you
still
a
reach
committee?
No,
you
switched
somebody
else's
outreach
committee.
Now
I
can't
remember
I'm
I'm
not.
E
Committee
right
you're,
not
on
the
average,
I'm
I'm
mistaking
you
for
okay.
Anyway,
we
should
have
a
a
plan.
I
think,
as
part
of
the
proposal
for
for
broadening
the
engagement,
because
we
want
to
make
sure
that
we're
developing
that
community
beyond
red
hat
right
right
at
ibm.
F
Yeah,
absolutely
that's
the.
That
is
definitely
one
of
the
things
we
also
want
to
get
out
of
this.
You
know,
relationship
and
partnership
is,
is
symbiosis
toward
the
goal
of
of
increasing
the
you
know
community
around
this
thing.
G
Yeah
and
jason
and
tara,
if
I'm
a
good
guy,
I'm
sure
big
boys.
I
was
one
of
the
first
committers
of
the
shipwright
project,
so
a
quick
history
on
this
would
actually,
you
know,
help
us
kind
of
think
in
that
direction.
So
when
we
started
out,
we
had
this
project
under
red
hat
event
under
red
hat
developer,
and
then
we
were
innovating
on
that
and
then
some
folks
from
ibm
came
and
said
hey.
We
want
to
contribute
to
this
because
we
want
to
use
this
as
well.
G
I
said
awesome
and
then
that's
when
we
thought
we
should
not
be
making
exceptions
because
ibm
reached
out
to
us.
G
So
from
that
perspective,
we
are
moving
in
that
direction
where
even
the
red
hat
started.
The
project,
any
other
contributor
who
joins
in
with
ibm
or
not,
is
just
another
contributor,
and
we
would
have
the
community
practices
set
up
accordingly.
F
Yeah,
I
think,
shubik.
I
think
that
that's
a
really
useful
context
that
that
it's
ibm
had
to
come
in
the
front
door,
like
red
hat,
had
to
build
a
front
door
for
ibm
to
come
into,
which,
which
was
a
good
investment,
because
now
it
means
there's
a
front
door
for
anybody
else
to
come
into
so
yeah
yeah.
A
Okay,
so
yeah
I
got
disconnected
for
a
moment,
but
I
found
the
actual
wording
in
our
project
life
cycle.
That's
just
for
on
this
exact
topic,
but
for
graduated
stage
we
require
a
healthy
number
of
committers
from
at
least
two
organizations.
So
that's
for
the
graduated
stage.
We
don't
stay
in
any
actual
numbers
for
the
incubating
stage.
We
do
just
said
it's
up
to
the
talks,
discretion
and
they're
supposed
to
demonstrate
a
substantial,
ongoing
flow
of
commits,
so
no
actual
numbers
at
this
stage,
so
cool
all
right.
So
everybody
review
this.
A
Take
your
time
on
the
talk.
What
I
now
kind
of
want
to
talk
about
is
tying
this
back
up
to
the
election
update
which
tracy
said
before,
which
is
that
we
have
a
new
talk,
that's
been
elected,
but
doesn't
start
for
a
little
bit,
so
I
don't
know
the
best
answer
on
how
to
do
this.
Logistically,
then
you
talk,
you
said
it
starts
july,
1st
tracy,
that's
right,
yeah!
A
So
it's
taken
us
on
the
order
of
you
know
two
talk
meetings
so
about
four
weeks
anyway,
to
you
know,
review
and
approve
these,
so
that
kind
of
puts
us
right
at
that
time
on.
I
think
it
would
feel
kind
of
weird
for
the
existing
talk
to
approve
something
a
week
before
the
new
talk
starts.
It's
also
weird,
to
tell
jason
to
sit
and
wait
and
potentially
revisit
this
decision
again
in
you
know
a
little
over
a
month
any
thoughts
here.
A
B
I
just
wanted
to
say
that
we
have
new
product
numbers
here,
so
they
can
still
put
their
non-binding
quotes
and
if
these
non-binary
quotes
are
aligned
with
binding
ones
that
there
is
no
problem
right,
you
might
be.
A
There
are
few
overlapping
and
I
guess
we
don't
know
the
full
range
yet
because
the
other
election
is
just
starting
and
now
you
see
how
the
same
thing
would
apply,
but
it
makes
sense
for
a
sponsor.
That's
no
longer
on
the
talk
in
three
days.
A
I
guess
I
I
kind
of
like
your
proposal
like
just
kind
of
let
the
new
talk
members
handle
this
non-binding
and
then
those
non-bindings
just
automatically
become
bindings
on
july
1st,
and
we
go
from
there.
I
kind
of
doubt
we're
going
to
get
this
wrapped
up
and
approved
before
then
anyway.
Actually,
given
that
our
talk,
members
are
likely
to
be
even
less
active
now
that
their
terms
are
up.
D
A
A
A
All
right
couple,
other
things
configuration
as
code,
sig,
yep
and.
B
Eso
engines,
we
have
a
jinx
configuration,
that's
called
some
project.
We
are
not
exactly
happy
about
the
current
structure,
because
the
area
moved
way
beyond
a
particular
plugin.
We
also
have
a
plugin
installation
managers
called.
We
have
official
docker
operations,
health
charts,
we
have
configuration
management
tool
integrations
like
ansible,
which
are
being
moved
under
the
jenkins
project
umbrella.
B
So
what
are?
We
thinking
is
converting
the
j
class
sub
project
which
the
computation
is
called
special
interest
group,
which
would
include
all
the
matters
in
jenkins
but
yeah.
There
is
an
open
question
whether
it
makes
sense
to
do
on
the
jenkins
level
or
whether
it
makes
sense
to
do
it
on
the
cdf
level,
so
that
the
same
practices
policies
could
be
applied
to
all
projects.
B
F
E
E
Spinnaker
and
probably
screwdriver
might
have
some
thoughts
here.
I
don't
know
if
we've
got
any
reps,
didn't
look
like
it,
but
I
guess
it
would
be
interesting
to
sort
of
see
the
scope
of
this
there's
a
lot
of
different
configurations.
One
could
be
talking
about,
so
I
guess
it's
what's
the
desired
outcome
on
this.
I
think
something
between
like
a
go
old
school.
A
little
bit
like
you
know,
jenkins
builder
configurations.
You
spin
up
your
your
new
master
is
a
very
different
mechanism
than
having
like
a
declarative
state,
kubernetes
style.
B
Well,
it's
if
you
talk
about
cdf
level,
it
would
be
rather
about
promoting
quest
practices,
for
example
from
looking
declarative
definitions,
promoting
practices
like
githubs,
etc.
I
believe
all
of
that
could
fall
into
this
domain.
Again.
The
configuration
is
called
sequence,
the
work
name,
it
can
be
changed,
but
yeah.
The
main
question
is
whether
there
is
enough
topics
on
a
high
level
to
have
for
this
special
interest
on
this
video,
because
everything
is
about
configurations
caught
at
the
moment.
E
Yeah,
I
can't
help
but
wonder
if
this
could
be
an
element
of
of
the
best
practices.
Sig,
for
example,
yeah
could
go
either
way,
so
it
might
be
worth
there's.
B
No,
it's
the
so
question
to
this.
If
there
is
no
one
pager
for
that,
because
I
just
brought
up
whether
there
would
be
interest
so
that
we
can
just.
E
B
So
enjoy
it
was
the
topic
for
a
long
time,
because,
basically,
our
continuous
configuration
project
it
has
stabilized
on
its
own.
So
there
are
not
that
many
activities
beyond
tenants
happening
right
now
there.
So
we
wanted
to
increase
the
scope
in
order
to
attract
more
contributors
and
to
revitalize
other
discussions,
but
yeah
it's
what
we
are
doing
on
the
agency
side.
E
Yeah
the
next
the
next
meeting
is
next
monday
might
be,
might
be
worth
a
topic
discussion.
E
A
All
right
last
couple
updates
the
cef
track
at
devops.
World
proposals
are
due
in
two
days.
I
I
So
yes,
please
submit
your
your
talk,
so
I
can
review
it
with
alyssa
from
cloudbees
and
then
the
next
update
we
have
is
the
kino
announcement
for
cdcon
is
now
available,
so
I've
included
the
link
to
the
blog
that
gives
an
overview
of
the
sessions.
So
take
a
look
at
that
and
then
registration
wise,
I
mean
we're
29
days
from
going
live
with
this
event,
we
have
443
folks
signed
up
for
the
jenkins
contributor
summit.
I
B
I
Yeah
one
one
month
left
and
yeah,
oh
and
then
the
other
really
cool
thing
is
so
we've
been
also
doing
some
fundraising
on
behalf
of
three
organizations
so
sheet
code,
africa,
women,
who
code
and
black
girls
code.
So
last
week
we
had
nicole
donate
a
thousand
dollars
to
that.
So
we
are
now
at
22.70
in
regards
to.
B
So
one
related
topic
on
june
25th,
we
will
have
jinx
contributor
summit,
as
jackie
said,
and
as
a
part
of
this
assignment.
We
want
to
cover
interoperability
topics,
so
we
already
had
some
discussions
with
dickton
project
about
having
electron
participants
there,
but
other
projects
are
also
invited
because
enjoying
this
we
want
to
integrate
with
all
ci
cd
and
other
automation
tools,
and
they
it
could
be
directional
integrations.
So,
for
example,
you
can
invoke
drinkers
from
tecton.
You
can
invoke
from
jenkins
like
it
was.
Posted.
Same
applies
to
all
other
tools.
B
B
B
A
All
right-
and
I
guess
we
have
two
devops
world
topics
here-
is
this.
A
B
Accorded
that,
because,
in
addition
to
the
sdf
track
to
which
you
should
definitely
apply,
there
is
also
a
community
track
and
actually
a
wide
community
agenda,
including
workshops,
ask
the
experts
boost.
We
also
want
to
have
a
contributor
some
in
there,
maybe
for
jenkins-
maybe
four
cdf
projects
yet
to
be
decided.
B
So
if
you're
interested
to
participate
in
widescope
but
the
devops
world,
please
let
me
know-
and
I
will
be
happy
to
help
so
at
the
moment
we
rather
focus
on
jenkins
agenda.
You
can
go
to
the
link.
You
can
see
a
lot
of
fancy
slides
a
lot
of
photos
of
face-to-face
events,
I'm
missing
so
much
but
yeah
this
year.
We
want
to
do
the
same
online
and
again,
all
projects
are
welcome.
B
Devops
fault
is
no
longer
about
jenkins
on
there,
so
it
started
as
jinx
wall,
but
our
tank
is
something
like
20
to
30
percent
of
its
agenda
and
all
other
cdf
projects
are
welcome
to
apply
to
the
community
track.
They
are
welcome
to
general
joint
activities
like
expert
schools
and
we
will
be
differentiable
from
them.
A
All
right
that
covers
it
for
today
welcome
to
all
the
new
talk
members
make
sure
to
get
jason's
proposal
reviewed
and
have
fun
with
these
upcoming
events.