►
From YouTube: CDF TOC meeting - 2020-11-10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
D
C
D
E
F
E
E
Changed
microphones,
that's
a
little
bit
better!
That's
a
little
louder!
I
don't
know
what
usually
you're
very
crisp
and
clear
and
there's
like
a
little
like
extra
noise
to
it
today,
but
you,
but
you
are
clearer
now.
E
G
Okay,
our
internet
was
doing
a
thing.
Yesterday
we
were
having
all
kinds
of
problems.
E
I
can
relate,
I
think,
just
everyone's
using
up
all
the
internet
on
their
zoom
calls.
At
the
same
time,
every
morning,
yeah.
G
E
Yeah,
where
I
live,
my
house
is
from
the
80s,
our
internet.
All
our
equipment
is
old,
but
it's
not
so
old
that
they're
going
to
replace
everything,
but
it's
not
new.
So
it's
kind
of
a
weird
stage
where,
like
these
kind
of
replace
little
things,
and
since
we
live
in
their
neighborhood,
where
everyone's
retired,
not
everyone
reports
issues,
so
we
were
kind
of
in
charge
of
that
getting
checked
out
to
repair
hardware.
H
F
G
E
C
I
I
J
I
don't
know
where
that
is.
I
live
in
west
lake,
so
it's
just
west
of
like
downtown.
K
J
Cool,
so
this
is
november
10th,
or
I
think
I
saw
somewhere
on
twitter
march
274th,
depending
on
how
you're
counting.
J
So
yeah
we've
got
a
couple
topics
today
on.
If
anything,
anybody
wants
to
address
anything
not
here
in
the
agenda,
go
ahead
and
add
it.
First
one
is
feedback
and
move
to
a
vote
on
the
ortelius
proposal.
J
There's
also
another
proposal
here
to
create
a
best
practices
sig,
with
the
pull
request
linked,
we
can
do
a
little
update
on
the
project
updates
that
were
just
included
in
the
newsletter.
I
think
tracy
has
some
cool
stats
and
discuss
how
to
keep
collecting
those
going
forward,
got
a
couple
white
papers
here
and
then
I
guess
just
I'm
hoping
have
a
little
bit
of
a
discussion
on
the
pending
docker
hub
changes
and
see
if
any
projects
are
word
they're
going
to
be
impacted
by
those.
J
J
J
So
here
is
the
proposal
it's
been
out
since
the
last
one
where
we
discussed
it
and
went
over
most
of
the
questions.
I
guess
so
is
there
anything
else
anybody
would
like
to
chat
about
here
before
we
move
to
a
vote.
J
J
J
C
C
Yeah,
so
I
think
if
you're
kicking
off
the
vote
and
allowing
at
least
a
couple
of
weeks,
I
think
one
of
the
things
I
noted
was
the
video
from
the
last
talk
meeting
where
they
had
the
discussion.
That's
we
haven't
made
that
available
yet
so
I
think
we
need
to
just
get
that
resolved.
C
So
if
we
leave
a
nice
a
decent
amount
of
time
for
for
folks
to
see
that
and
and
do
the
voting,
then
it
gives
us
time
as
well.
I
think
we
need
two
or
three
weeks
just
to
to
line
everything
up.
If
we're
going
to
be
announcing.
This.
C
So,
in
short,
if
you
want
to
go
ahead
and
kick
off
a
vote
yeah,
if
we
can
allow
at
least
two
weeks
for
folks
to
to
give
their
input
and
then
probably
just
another
week
behind
the
scenes
to
pull
things
together,.
J
All
right
I'll
kick
off
the
vote
right
after
this
meeting
great.
If
people
aren't
familiar,
the
vote
will
take
place
on
the
talk
mailing
list.
Anyone
is
welcome
to
participate,
but
the
votes
are
only
binding
from
talk
members,
so
you
should
see
that
fly
by
right
after
this
all
right.
Next
one
is
the
best
practices
proposal.
J
I
think
tara
had
a
couple
questions
about
this
in
slack
is
mauricio
here
who
submitted
this?
Yes
awesome.
Do
you
want
to
present
talk
through
this
or
I
can
keep
my
screen
sharing
and
you
can
talk?
It
doesn't
look
like
it's
too
long,
so
we
shouldn't
have
to
scroll.
K
So
the
main
idea
before
this
seed
is
just
to
collect
and
present
these
best
practices
and
just
call
to
a
broader
audience
and
a
brother,
like
you,
know,
people
participating
into
collecting
these
best
practices
and
create
material
around
it
to
make
sure
that
we
promote
you
know
whatever,
like
companies
or
members,
are
experiencing
out
there
in
the
field
just
to
collect
that
together
and
just
push
to
make
sure
that
we
all
share
this
knowledge
and
and
promote
that
knowledge
sharing
across
different
members.
So
yeah
I'm
super
interested
in
the
topic.
K
I
am
writing
some
stuff
around
it.
So
I
I
thought
okay,
this
might
be
a
good
idea
and
you
know
with
tracy.
We
think
that
it
might
be
like
good
to
kick
started
right
now,
so
we
need
to
find
some
sponsors
tracy.
I
think.
C
Yeah,
yes
and
yeah,
just
to
echo
what
marriage
is
saying
super
super
excited
about
this.
I
think
the
sig
is
almost
kind
of
the
reason
cdf
should
exist,
which
is
all
about
helping
people
figure
out.
You
know
best
practices
around
continuous
delivery
and
emerging
practices,
as
as
things
change
as
technology
shows
up
and
we've
got
really
good
support
at
the
board
level,
so,
like
michael
galloway
of
netflix,
has
agreed
to
be
the
the
kind
of
exact
sponsor
for
this
effort.
I
think
from
his
experience
at
netflix.
C
They
say
they
often
have
folks
coming
to
them.
Saying
you
know,
how
can
we
be
the
next
netflix?
What
does
it
take,
and-
and
sometimes
it's
important
for
folks
to
be
able
to
you-
know
either
understand
their
risk
profile
or
their
attitude
to
developers
or
the
size
of
their
teams.
So
just
trying
to
give
folks
a
framework
to
sort
of
evaluate
themselves
and
then
sort
of
say
what
do
they
need
to
do
to
continuously
improve
and
get
better
at
better
different
things.
C
So
yeah
we
are
looking
for
a
talk
sponsor,
who
will
kind
of
be
the
liaison
for
this
group
and
yeah.
Just
in
general
for
folks
to
get
involved
and
to
sign
up
and
attend
the
first
meeting.
B
So
I
have
a
lot
okay,
so,
first
of
all
love
the
idea.
I
had
been
kicking
around
an
idea.
Similarly
about
a
year
and
a
half
ago.
Here
is
my
concern,
and
maybe
we
can
try
and
figure
out
how
to
mitigate
it.
Stuff
like
this
can
one
be
super
political
in
the
broader
communities.
B
If
you
think
about
some
of
the
the
communities
around
like
resiliency
engineering
as
a
concept
or
the
whole
kerfuffle
that
tracy
you
and
christy
and
jez
have
kicked
off
around
the
whole
ci
part
of
ci
cd,
like
there's
a
lot
of
schools
of
thought
around
this
sort
of
thing,
and
so
for
us
to
come
in
and
say
that
we
are
defining
a
set
of
best
practices
that
are
sort
of
broadly
encompassing
industry
standards.
B
There's
there's
the
potential
for
negative
backlash,
first
of
all,
which
obviously
would
not
be
good
for
the
foundation
and
secondly,
the
you
know
I
there
was
the
reference
to
accelerate
as
part
of
that,
and
I
want
to
point
out
the
immense
amount
of
work
and
like
really
critical
research
and,
like
all
of
the
processes
around
that
that
went
into
that,
and
so
you
know,
are
we
going
to
hold
ourselves
to
the
same
or
even
approaching
similar
standards
for
how
we
collect
analyze
data
in
order
to
back
up
claims
like
like
accelerate,
did
that's
a
pretty
big
claim
and
would
be,
I
think,
hard
to
do
on
a
volunteer
basis,
and
then,
finally,
you
know
it
may
be
that
a
lot
of
really
interesting
best
practices
are
already
available.
B
Do
we
or-
or
you
know,
part
of
other
ongoing
discussions,
and
how
do
we
become
part
of
those
discussions
in
a
way
that
is
positive
and
well
received,
as
opposed
to
like?
No,
we,
you
know
we
want
to
have
our
versions
of
those
documents
that
we're
hosting
in
our
repository
kind
of
thing
right.
B
So
these
are
all
things
that
I
don't
think
are
deal
breakers,
but
the
sorts
of
things
that
I
was
thinking
about
heavily
when
the
the
last
time
this
this
idea
came
up
and
I
didn't
come
up
with
any
good
ideas.
It
was
a
lot
of
work,
so
I
I
feel
like
we
need
to
address
at
least
some
of
these
a
little
bit
more
thoroughly
as
part
of
this
because,
like
I
said,
I
love
the
idea,
but
this
is
definitely
one
where
the
devil
there's
a
big
devil.
In
these
details.
C
Yeah,
so
I'm
happy
to
to
kind
of
jump
in
and
answer
some
of
your
questions
or
address
some
of
the
concerns
or
just
tell
you
what
what
I
think
the
approach
is:
you're
the
boss,
yeah,
so
okay,
so
first
of
all,
like
you're
you're,
referring
to
the
the
cincd
and
and
kerfuffle
like.
C
So
so
totally
now,
I
think
some
of
those
discussions,
like
particularly
on
terminology,
which
I
think
is
independent
of
this
effort,
but
I'll
just
address
it,
because
I
think
we
could
end
up
in
in
similar
discussions.
So
I
think
it's
really
important
that
cdf
does
take
a
stance
in
terms
of
what
certain
terms
mean
and
how
we're
seeing
things
and
very
obvious
in
the
interoperability
group,
where
we'd
often
have
discussions
and
people
after
a
while
would
realize
that
they're
talking
at
cross
purposes,
because
we
didn't
have
a
shared
definition.
C
So
it's
not
so
much
that
cdf
will
be
looking
to
sort
of
you
know
dictate
to
the
industry
how
people
should
be
seeing
things,
but
we
should
certainly
internally
have
an
alignment
on
terms
so
that,
if
we
come
into
like
the
interoperability
group
and
we're
saying,
okay,
we're
discussing
this
level
of
integration
of
this
level
of
standardization.
Here
is
what
we
mean
by
x,
y
and
z.
So
that's
kind
of
where
all
the
the
things
we
we've
had
on
the
definition
front
come
out
now,
specifically
on
best
practices.
C
I
do
agree
that
you
know
we're
not
looking
to
do
kind
of
the
rigorous
data
collection
kind
of
that
standard
of
practices,
but
the
reality
is:
that's
already
been
done
by
the
accelerate
book
so
and
what
this
proposal
says
is
we
want
to
use
that
as
the
basis
the
the
folks
that
have
already
mapped
out
24
capabilities?
C
These
are
things
that
you
know
have
been
scientifically
proven,
but
the
reality
is
that
most
people,
one
don't
know
they
exist
and
two
don't
know
how
to
kind
of
measure
themselves
up
against
them,
and
they
we
had
someone
else
in
one
of
these
discussions.
I
was
hoping
he
could
be
here,
but
I
hope
he
will
get
involved
with
the
best
practices.
But,
for
example,
if
you
take
something
like
one
of
the
capabilities
is
use
version
control.
C
C
C
C
Actually
you
need
to
see
that
your
team
or
your
company
is
kind
of
behind
the
curve,
and
there
may
be
good
reasons
for
that.
So
this
is
not
about
kind
of
shaming
people,
but
it
is
about
a
way
of
saying.
Okay.
How
do
you
peg
yourself
against
each
of
these
24
things
and
as
people
you
know,
as
the
tooling
becomes
available
to
make
each
thing
easier?
How
do
you
know
how
do
you
get
to
a
continuous
improvement
cycle
and
bring
your
team
along
with
you.
B
Sure-
and
that
makes
total
sense,
but
my
point
is
like
there
is
a
wealth
of,
but
that's
a
great
example.
Actually
is
whether
or
not
you
should
use
version
control
right.
There
is
a
wealth
of
data
and
and
books
and
blog
posts
that
are
already
out
there
that
talk
about
this
kind
of
stuff.
So
I
guess
my
question:
is
you
know
what
are
we
bringing
through
this
effort?
That
is
unique
right
or
are
we
just
going?
Is
the
idea
that
we
just
want
to
have
some
kind
of
voice
in
the
discussion?
B
I
guess
that's.
I'm
really
trying
to
understand
like
what.
What
are
the
outcome
that
we're
hoping
to
get
through
this
so
put
another
way
like
do
we
want
to
say
if
we're
going
to
focus
on
accelerate
and
the
dora
research,
do
we
want
to
say
that
part
of
this
means
that
we
will
instrument
or
that
part
of
a
project
implementation
for
a
cdf
project
involves
dora
instrumentation
for
for
the
four
keys
measurements?
B
Do
we
want
to-
and
you
know
cloudbees
has
that
as
part
of
a
product,
my
team
actually
recently
released
a
a
small,
open
source
version
of
that,
for
example,
do
we
want
to
say
that
we
want
to
focus
on
here
is
how
you
do
best
practices
using
our
stuff
in
variations?
So,
for
example,
here
is
how
you
hook
up.
B
C
I
would
actually
say
it's
deliberately
not
prescriptive,
because
I
think
there's
three
or
four
different
ways.
We
could
go
with
this
and
it
almost
depends
who's
going
to
show
up
into
the
room
to
have
those
discussions.
So
you
know
this
could
be
a
what
is
the
best
way
to
implement
git
ops?
It
could
be
that
narrow
or
it
could
be.
C
You
mentioned
you
know
and
like
some
of
the
things
we're
hearing
from
our
members,
so
fidelity
joined
the
other
day
and
and
their
approach
is,
you
know
they
want
to
be
able
to
say
what
is
the
difference
in
how
you
approach
continuous
delivery
in
a
200
people
versus
a
20
000
people
company?
C
I
Yeah,
so
I
could
say
from
from
the
spinnaker
side,
you
know
tara.
You
were
mentioning.
I
think
that
there's
a
there's,
the
kind
of
what's
the
research
and
the
behaviors
and
processes
that
are
abstracted
like
and
you
know,
if
you
look
at
the
book,
accelerate
they
don't
talk
about
really
tools
very
much
in
that
book.
Right.
I
F
I
Gonna
be,
and,
and-
and
so
I
think,
I
think,
it'd
be
incredibly
helpful,
I
think-
for
the
industry-
it's
like,
okay,
good.
I
have
all
these
these
learnings
from
accelerate.
Now,
how
do
I
help?
How
do
I
implement
those
with
the
tools
in
in
the
world
today
right-
and
I
think
I
think,
that's
where
at
least
my
experience
is
that
a
lot
of
people
are
stumbling
where
they
want.
They
know
what
they
want
from
those
those
books
that
have
incredible
amount
of
fantastic
research-
tara,
as
you
pointed
out
it's
just
like
now.
I
How
do
I
make
this
a
reality
with
with
what's
out
there
in
the
world
today,
or
can
I
even
make
it
a
reality?
Right
like,
for
example,
spinnaker
doesn't
support
those
metrics,
the
the
four-door
metrics
that
that
are
in
there,
but
there
may
be
other
tools
that
do
and
and
if
those
metrics
are
the
things
that
you're
really
going
after
then,
then
you
should.
We
should
be
able
to
highlight
one
of
the
tools
in
our
foundation
that
helps
them
accomplish
that
goal,
or
maybe
it's
chaos,
engineering
or
maybe
it's
whatever.
I
That
practice
may
be
that
they're
after
or
that
is
their
top
priority,
because
I
think
that
that
book
sets
in
among
many
books,
not
just
that
book,
but
among
many
books
sets
a
kind
of
a
general
direction,
but
isn't
just
like
a
plan
of
action
right.
So
that's
where
I
think
we
can
fill
in
the
gap.
I
think
that's
where
our
role
is.
I
B
Right,
okay
and
to
be
clear,
like
I'm,
not
hostile
to
this,
but
I
just
I
want
us
to
be
very
thoughtful
about
the
approach
right.
So
let's
go
back
to
chaos,
engineering
and
best
practices.
So,
let's
take
that
as
an
example,
if
we
engage
in
some
form
of
assessment
around
resiliency
and
chaos,
engineering
and
nora
jones,
as
one
example
is
not
part
of
that
conversation
right
or
oh
god,
what
was
the
name
of
the
other
author
of
that
book,
I'm
totally
blocking
anyway.
B
You
know
what
sort
of
legitimacy
do
we
bring
to
it
in
a
general
sense
right,
I
agree,
but
if
we're
able
to
to
speak
to
it
in
maybe
if
the
focus
was
around
case
studies
like,
if
you
know
we
had
some
of
the
members
who
are
like
okay,
we're
going
to
take
a
take,
give
this
a
shot.
B
I
And
I
mean
that's
a
that's
an
excellent
point.
I
think
it
it
points
out
either
like
I
I
by
no
means
my
chaos
engineering
expert.
I
know
what
it
is
and
I
know
how
to
poke
a
few
buttons
in
a
couple
tools,
but
I'm
not
no
means
an
expert,
but
I
think
maybe
maybe
there's
two
ways
of
looking
at
this,
which
is
one
it
either
shows
that
there's
a
gap
in
the
in
experience
with
inside
of
the
cdf
that
we
need
to
bring
in
people
like
like
nora
and
casey
rosenthal,
who
also
thank.
I
Yeah
right,
so
we
need
to
bring
bring
those
those
folks
into
the
fold
so
that
they're
helping
us
produce
it
or
we
advise
with
them
and
in
a
kind
of
advisorship
capacity,
where
they're
kind
of
signing
off
on.
What's
here
right
so
like
there's,
I
think
you're
just
kind
of
bringing
up
like
other
kind
of
really
important
issues
that
we
have
to
address
as
a
group
as
a
foundation
really.
H
This
is
steve
from
deploy
hub
I've
seen
some
of
the
the
ways
this
is
handled
as,
like
your
centaur,
where
it's
a
a
series
of
case
studies
that
you
may
have
one
or
two.
You
know
maybe
three
case
studies
around
a
specific
topic,
so
you
can
kind
of
get
a
feel
for
what
a
git
ops
is
going
to
look
like,
or
you
know
how
to
use,
get
version,
control
for
a
small
team,
a
medium
team
and
a
large
team
and
they're
just
case
studies.
H
That
kind
of
give
you
the
lay
of
the
land
of
that
type
of
topic,
and
that
may
be
one
way
to
kind
of
back
up
what
you're
you're
talking
about,
because
I
don't
think
there's
gonna
be
one
one
size
fits
all
solution.
J
I
think
you
said
the
magic
word
there
that
I'm
interested
in
at
least
as
part
of
this
steve,
which
is
case
studies.
You
know
case
studies
by
definition,
are
non-controversial
they're
useful
to
everyone.
Every
every
conference
I've
been
to
the
busiest
rooms
or
the
companies
providing
case
studies
on
how
they're
doing
these
things
and
my
favorite
talk
every
year
at
kubecon
is
the
one
from
reddit
where
they
just
talk
about
what
they're
currently
doing
with
kubernetes
and
delivery
and
how
they've
put
all
these
pieces.
J
H
C
H
B
G
And
and
I'm
putting
my
open
source
hat
on,
I
I
want
to
put
out
there
that
we
have
and
I
keep
talking
about
them.
We
have
ambassadors
that
are
not
we're,
not
we're
not
leveraging,
and
I
would
very
much
like
to
see
a
way
to
do
that
now.
I
think
that
we
could
you
know
if
we
really
wanted
to
come
up
with
best
practices.
I
think
we
have
to
come
up
with
and
and
sort
of
from
a
from
a
you
know,
a
special
interest
group
at
work
effort.
G
My
suggestion
would
be
we
come
up
with
the
chapters
we
come
up
with
a
high
level.
You
know
what
what
areas
are
we
going
to
cover
and
we
allow
the
ambassadors
to
either
create
a
case
study
around
that,
or
we
also
could
have
them
create
a
poc,
a
standard
poc
that
outlines
for
this
particular
discipline,
whether
it
be
continuous
tests
or
continuous
integration
or
version
control,
we
build
a
common
poc
out.
I
know
we
started.
We
started
working
on
personas
in
our
the
artillious
project
and
that
made
a
logical.
It
was
like.
G
Oh
you
know,
we
have
these
personas.
What
how
are
these
personas
impacted
by
the
problem
set
that
we're
solving,
and
so
we
just
started
to
write
out
a
poc
for
the
problem
set.
So
I
feel
like,
if
we're
going
to
do
this,
we
should
give
it
some
structure
and
we
should
open
our
arms
and
get
the
ambassadors
involved,
because
there's
some
really
smart
people
out
there
and
they're
not
being
leveraged.
M
I
I
I
want
to
share
some
reflection
from
party
by
the
way
I
joined
ieee
conference
like
two
weeks
ago,
and
there
was
a
workshop,
the
industry
workshop
and
presented
cdf
and
focused
on
interoperability,
and
we
had
a
long
conversation
after
the
workshop
more
than
an
hour,
and
there
were
many
people
who
were
actually
asking
the
questions.
The
best
practices
seek
aims
to
address
partially,
like
there
were
questions
like
maturity
model
or
what
are
the
best
practices
when
it
comes
to
how
to
do
ci.
M
So
I
think
one
of
the
contributions
this
could
make
is
to
bring
those
people
to
one
place,
perhaps
cdf.
That
is
why
cdf
is
there
to
bring
people
together
and
collaborate
and
discuss
these
things
so
like,
even
though
we
forget
about
what
this
group
may
end
up,
achieving
just
bringing
those
people
to
one
forum
and
letting
them
talk
about
those
things.
It's
pretty
valuable
because
my
feeling
was
like
those
people,
even
though
they
were
pretty
competent
in
ci
cd
stuff.
M
They
didn't
know
who
else
is
working
with
these
things
so
yeah,
I
I
don't
know
if
tracy
I
don't
know
if
you
met
with
those
people,
but
that
was
my
feeling-
and
I
simply
pointed
them
to
cdf
and
having
best
practices.
Special
interest
group
would
allow
more
people
to
come
and
take
part
in
the
conversations.
J
B
Just
gonna
say
you
know,
obviously
I
have
opinions
and,
and
I
love
the
concept
I
will
be.
I
will
be
happy
just
to
volunteer
myself
as
a
sponsor.
C
J
All
right,
so
I
guess
at
a
minimum,
we've
got
to
fill
in
your
name
and
that
pull
request
and
I
think,
there's
probably
other
changes
and
tweaks
we
can
make
to
it.
Based
on
the
discussion
we've
had
so
far,
once
that's
ready,
do
you
want
to
send
an
email
to
the
talk
list?
Mauricio
and
then
we
can
do
another
wave
of
feedback
or
go
move
to
a
vote
yeah.
We.
C
So
I
was
gonna
add
I
think
I
don't
know
if
it
says
this
in
the
proposal
but
like
just
to
if
we
are
kicking
off
the
conversations,
I
think
we
had
a
proposal
that
we
we
would
start
that
next
monday
and
just
have
a
session
where,
like
this
conversation,
carries
on
when
we
talk
about,
you
know
what,
how
do
we
frame
it?
What
are
the
end
bits
and
outputs
outlets
yeah?
What
are
the
outputs
we
we
want
to
see
and
and
who
wants
to
to
help
drive
that
saving.
B
C
So
yeah,
if
anyone
wants
to
continue
this
discussion,
which
I
think
is,
is
really
good,
we'll
send
out
some
the
talk
and
put
it
in
the
cdf
calendar,
so
it
might
already
be
there.
J
C
I
do
not
actually
so
we
don't
have
them
yet,
but
I
do
have
the
archive
version
of
the
newsletter
is
up
on
the
website.
So
I
encourage
folks
to
check
that
out
and
we
should
have
some
stats
by
at
the
end
of
the
week.
So
in
time
for
the
next
meeting,
but
yeah
we
had
some
really
good
feedback
that
it
looked
really
good
and
lots
of
content
just
in
both
from
cdcon
and
also
from
project
update.
So
thanks
for
for
all
the
effort
folks
put
into
that.
J
Cool
yeah
so
based
on
rosalind's
suggestion,
I
reorganized
the
dock
to
collect,
updates
a
little
bit
so
added
a
december
section
here
with
the
same
project,
so
people
can
kind
of
add
things
in
here
each
week
or
whenever
they
think
of
them
to
keep
it
rolling.
So
it's
not
like
a
rush
at
the
last
minute.
J
The
december
newsletter
cut
off
is
the
26th
of
november,
so
we've
got
a
couple.
J
Out
recurring
reminders
to
add
things
in
here
as
people
think
of
them
a
great
way,
at
least
from
the
tech
town
side.
We
had
some
people
mention
they
call
that
updates
in
our
slack
and
come
up
and
try
out
some
of
the
new
stuff
we
mentioned.
Hopefully,
it
provides
some
value
to
the
other
projects
as
well,
and
then,
hopefully,
we'll
have
an
ortelius
section
in
here
soon
too.
J
Hub
again,
I
know
the
jenkins
community
was
testing
us
a
little
bit.
They
were
concerned.
Some
of
the
images
they
published
on
docker
up
are
going
to
be
affected
by
the
new
quota
changes.
J
I
don't
know
if
any
of
the
other
projects
were,
I
think
tekton
had
some
stuff
in
the
catalog,
some
of
the
community
images
catalog
hosted
on
docker
hub
and
we're
figuring
out
alternative
homes
for
them.
I
don't
really
have
any
great
answers
here.
If
people
aren't,
you
know,
familiar
docker
hub
is
kind
of
changing
their
quota
and
billing
model
so
that
people
have
to
be
logged
in
and
signed
up
in
order
to
download
things
with
high
enough
rate
limits.
J
So
a
bunch
of
ci
systems
are
going
to
start
falling
over
as
these
changes
roll
out
unless
projects
get
into
the
allow
list
for
docker
hub.
So
there
is
a
way
to
apply
as
an
open
source
project
to
get
your
images
unblocked
and
not
affected
by
the
rate
limiting.
But
I
don't
know
if
anybody
has
actually
successfully
gone
through
that
yet.
A
O
O
Sorry
about
that,
is
it
better
now
yeah,
I'm
actually
outside
oh
yeah,
so
I
was
saying
that
scooter
did
apply
for
that
source
except
application
and
it
did
go
through,
but
I
haven't
tried
it
out
yet
because
all
the
screwdriver
containers
are
published
in
docker
hub
and
I'm
not
quite
sure
what
does
it
mean
like?
Is
it
just?
You
were
on
containers
being
pulled
from
dr
herb,
or
is
it
when
you
are
logged
in
as
that
user?
Is
that?
O
J
Well,
so
it
sounds
like
at
least
people
are
hearing
back
on
the
application,
which
is
better
news
than
I
had
last
time.
I
looked
into
this
we
can
set
up
if
people
want
to
move
off
of
docker
hub
to
something
else
and
need
billing,
we
could
look
into
credits
and
moving
things
to
some
of
the
other
registries
tech
time
mostly
uses
gcr
paid
for
out
of
the
cdf
budget.
What
does
jenkins
x
do
while
you're
here
james.
A
Yeah,
so
it's
an
interesting
one
so
currently,
because
we,
I
think
we're
going
through
this
kind
of
a
big
effort
at
the
moment,
so
we're
close
to
a
beta
for
jenkins
x3,
which
is
quite
big.
It's
a
big
big
thing
deal
for
us.
We
quite
we
changed
the
way,
we're
actually
building
and
the
number
of
images
and
how
we're
actually
using
our
images
as
well
so
for
jenkins,
x2
we're
actually
using
cloud
views
are
paying
for
it
not
sure
how
much
they
know
about
it
yet,
but.
A
The
images
are
a
lot
smaller,
a
lot
less
as
well.
So
I
think
there
is
something
we
need
probably
going
to
need
to
look
at,
and,
incidentally,
we
actually
applied
to
go
to
the
docker
hub,
even
though
we're
not
using
it
at
the
moment
just
because,
if
as
an
open
source
project,
they
were
to
accept
it.
That
would
be
a
nice
quick
win
but
yeah
we're
certainly
looking
for
similar
for
helm,
charts
as
well
on
registries
as
well.
So.
J
J
Okay,
white
papers
tracy:
this
was
supposed
to
be
an
agenda
last
time,
but
we
ran
out
of
time.
M
Thanks
tracy,
I
think
we
are
pretty
close
to
finalize
the
first
draft.
We
lack,
I
think,
two
sections
which
we
plan
to
finalize
after
this
week's
meeting
and
then
by
end
of
november,
we
plan
to
send
the
draft
to
cdf
creative
team
and
the
target
is
mid-december
or
something
like
that
before
christmas
or
lace
start,
but
we'll
see
how
fast
we
will
be
with
this,
and
the
other
thing
is.
M
I
think
we
have
pretty
good
number
of
case
studies,
and
I
think
this
beginning
of
this
week
yesterday
oliver
contributed
a
case
study
from
sap,
and
that
is
great
to
see
because
we
want
to
ensure
we
have
representation
from
different
industries.
M
C
Yeah,
thank
you,
go
ahead
and
just
click
on
the
link.
It's
a
pretty
impressive
set
of
case
studies
and
fatty
and
the
interoperability
group
have
managed
to
really
work
together
very
effectively
to
bring
all
these
different
kind
of
view
points
onto
the
problem
together.
So
we've
got
jenkins
x
and
tacton.
Captain
zul
end
users
that
go
spot
check,
ericsson,
sap
and
I
think
I
think,
a
couple
of
others
in
the
works
still
30.
M
Yeah,
I
think
we
will
probably
get
one
from
car
manufacturer
using
a
different
cicd
tool
from
a
different
foundation.
So
that
is
also
great
because
then
we
have
no
different
projects
taking
part
in
a
white
paper
produced
by
cdf,
which
is
good
for
visibility
and
also
diversity.
M
C
Okay,
so
the
definition
stock
was
actually
a
spinner
from
that
white
paper,
where
we
sort
of
started
getting
into
the
what
does
the
each
term
mean
and,
and
then
that
turned
into
a
much
bigger
and
wider
conversation.
So
this
document
is
still
open
and
we're
still
happy
for
people
to
put
input
into
it.
The
current
thinking
here
and
christy
wilson
has
droven
some
thoughts.
There
is
one
of
the
things
that
we
thought
it
would
be
useful
for
cdf
to
do.
C
First
of
all
is
to
just
capture,
perhaps
some
of
the
history
of
the
terms
of
you
know
where,
where
they
emerge
from
and
how
they've
evolved
over
time,
so
christie
wilson.
C
She
did
that
talk
at
cdcon
kind
of
looking
at
some
of
that,
and
then
the
idea,
as
a
first
step,
was
to
put
that
kind
of
in
in
a
reference
repository
under
github
and
just
sort
of
say:
okay,
here's
where
these
terms
first
came
up
and
here's
how
the
different
usage
is
evolving
and
then
use
that
as
some
of
the
background
to
as
we
define
these
things,
we
talk
about
the
the
historical
context
and
where
we
think
the
future
is
going
and
and
that
kind
of
puts
it
in
a
good
perspective
and
also
because
I
think
these
things
seem
to
come
up
over
and
over
again
and
if
cdf
can.
C
If
we've
done
the
work-
and
we
can
be
that
centralized
authority,
then
why
not
just
make
things
simple
in
that
way.
So
in
the
meantime
yeah.
If
anyone
wants
to
have
a
look
and
weigh
in
check
out
that
document,
and
that's
all
on
this
one.
So
if
we
go
back
to
the
other
white
paper.
C
C
So
this
one
is
a
much
it's
the
we've
sort
of
got
the
structure,
but
this
is
a
focus
on
we're.
Looking
at
talking
about
the,
why
of
continuous
delivery?
Why
does
it
matter?
Why
is
it
important,
and
particularly
targeting
more
c-suite,
potentially
and
also
people
who
are
trying
to
convince
leadership,
to
invest
so
developers
trying
to
appeal
to
leadership
but
also
leadership
in
general,
having
an
appreciation
that
continuous
delivery
is
a
space
worth
investing
in?
C
So
it's
got
some
bits
written
out,
but
the
main
thing
here
we're
looking
for
is
review
on
the
structure.
So
the
first
bit
is
you
know
what
is
continuous
delivery
so
start
off
with
some
attempts
at
definition
there
and
then,
if
we
go
down
next
a
lot
on
the
benefits.
So
why
do
it
and
what
are
the
different
ways?
It
benefits
organization
processes
teams.
C
C
What
it's
aiming
to
do
is
then
sort
of
say:
okay,
what
are
the
different
things
that
come
together
to
build
up
to
continuous
delivery,
and
these
might
be
the
sets
of
practices
so
again
here,
and
this
is
something
it
might
be
worth
having
a
broader
discussion
at
the
talk
level,
it
seems
useful
to
provide
kind
of
a
trail
map
again
of
sort
of
saying:
how
do
you
break
down
what
are
all
the
different
things
like
testing
and
security
and
ci
and
automated
deployment,
and
how
do
we
give
people
a
way
to
think
about
that
like
a
mental
image?
C
So
that's
the
idea
behind
the
section,
but
I
think
this
bit
needs
a
lot
of
work.
Then
the
next
bit
is
the
landscape.
So
once
we
talk
about
the
practices,
how
do
we
connect
those
to
the
different
tools?
So
tracy
reagan
has
already
led
a
lot
of
work
in
this
place.
We
have
the
definitions.
We
just
need
to
connect
up
how
that
fits
it.
You
know
how
that
ties
into
the
narrative.
C
We
have
a
bit
on
continuous
delivery
and
open
source.
Like
john
mark
walker
of
capital,
one
pointed
out,
we
have
this
amazing
data
to
say
people
who
leverage
open
source
actually
there's
a
correlation
with
how
often
they
deploy
so
tying
in
that
element
of
why
you
should
be
leveraging
open
source
or
why
would
be
good
as
part
of
your
solution
and
then
we're
looking
for
case
studies
to
talk
about
it
in
action,
so
we'll
be
tapping
into
two
members
about
that.
C
So
if
anybody
does
have
a
case
study
and
they
want
to
go
ahead
and
put
that
in
about
the
benefits,
how
it's
made
an
impact,
how
it
allows
you
to
be
agile,
fill
those
in
and
then
the
last
section
we'll
be
looking
at
is:
where
does
cdf?
How
can
cdf
help
you
in
your
adoption
journey?
How
can
it
help
you
with
resources?
So
as
kind
of
your
your
next
steps,
if
you're
convinced
it's
the
right
way
to
go,
what
are
the
things
you
can
tap
into
to
find
help
or
yeah
resources.
B
So
I
I
kind
of
have
the
same
comment
here
that,
from
from
our
previous
discussion,
which
is
like
this
is
a
a
a
deeply
commented
upon
space
and
if
the
target
is
sort
of
c-suite
or
executive
types,
it
feels
like
there's
a
good,
maybe
a
good
opportunity
here
to
fortify
it
with
with
citations.
B
Right
we've
got.
You
know,
martin
fowler
and
jess
humble
and
the
whole
accelerate
book
covers
a
big
piece
of
this.
If
there's
a
way
that
we
could
tie
in
the
case,
studies
that
we
have
with
with
supporting
research
that
that's
already
out
there,
I
feel
like
that,
would
really
strengthen
the
the
credibility,
especially
if
this
is
meant
for
developers
to
be
able
to
pitch
investment
in
the
area
at
their
respective
companies.
C
Okay,
yeah
so
call
to
action.
If
anybody
wants
to
go
ahead
and
comment
on
the
document,
please
do
so
if
you
have
case
studies
or
if
your
company
would
like
to
provide
kind
of
almost
a
testimony
as
to
the
benefits
of
continuous
delivery.
I
think
that
would
be
well
well
received
and
appreciated,
so
either
reach
out
to
me
or
go
ahead
and
comment
on
the.
J
C
C
So
and
I'm
going
to
just
keep
talking
about
that
white
paper,
a
little
more
well
stan
tries
to
unfreeze
his
screen.
So
I
think,
like
one
of
the
things
the
folks
we
have
at
cdf,
you
know
tend
to
be
a
self-selecting
group
of
people
who
appreciate
ci
and
cd
and
why
it's
important
and
even
understand
how
to
implement
it.
But
in
most
of
the
conversations
a
vast
majority
of
people
don't
have
that
appreciation.
C
They
don't
have
those
insights
and
they
they've
often
just
set
up
some
ci
and
they've
been
pretty
pleased
with
themselves,
which
is
great,
but
I
think
when
we
talk
about
some
of
these
materials
and
and
the
working
groups
and
the
white
paper,
it's
just
saying:
okay,
there's
a
whole
set
of
folks
out
there
who
who
need,
help
and
need
that
support
in
kind
of
that
journey,
and
I
think
that's
from
the
cdf
perspective,
where
we
can
be
better
at
broadening
our
audience
and
bringing
in
more
people
and
helping
them
on
ramp
really
really
quickly
and
not
as
a
current
case.
C
I
think
like
to
do
cd.
Well,
you
really
have
to
be
in
it
in
a
very
specialized
way
and
yeah.
We
need
to
just
democratize
it
for
everybody.
B
I
I
think,
being
able
to
show
the
exact
steps
people
went
from
from
nothing
or
mostly
nothing
to
you
know.
Dora
levels
of
measurability,
I
think,
is
going
to
be
huge.
There's
a
lot
of
legacy
systems
out
there
that
are
probably
really
hard
to
retrofit,
so
giving
a
road
map
would
be
super
useful.
In
that
case,.
C
And
I
think
that's
a
great
point,
just
it's
almost
appreciating
that
it's
on
a
different
track,
if
you're
starting
from
scratch
versus
contending
with
something
existing
and
and
what
you
might
need
to
consider.
If
you
you
don't
have
that
luxury
which
I
think
sometimes
ends
up
being
ignored
with
new
projects
or
new
techniques.
It's
always
like
hey.
You
can
just
start
from
scratch
and
forget,
forget
all
those
people
dealing
with.
D
J
Awesome
well
thanks
for
the
updates
on
all
those
white
papers.
We
have
one
final
thing
here
on
the
back,
which
is
the
landscape
updates.
I
think
that's
just
kind
of
our
recurring
reminder
to
look
at
the
landscape
repo,
keep
that
up
to
date
with
prs
that
kind
of
thing.
B
Been
I've
been
terrible,
I'm
I
get
in
there
when
I
can.
It's
just
been
very
daunting
with
between
work
and
other
stuff.
I
would
love
for
anyone
else
to
come
in
here
and
help
out.
B
B
Like
have
like
a
little
mini
hacker
summit
on
the
landscape,
I
and
I
I
have
failed
to
organize
it,
but
I
I
would.
I
would
I'll
at
least
do
that.
Maybe
I'll
just
get
a
bunch
of
people
send
out
a
call
for
for
action.
B
P
Tara,
you
can
also
send
the
note
to
the
ambassador
group,
because
I
know
there's
a
few
folks
who
are
interested
in
helping
out.
P
I
think
owen
was
interested
in
helping
out
too.
D
J
Well
thanks:
everybody
good
meeting
see
everyone
in
two
weeks
or
sooner.